This is the old SliTaz forum - Please use the main forum.slitaz.org

Additional ethernet modules needed ie. realtek 8139 netcard driver
  • PeterPeter February 2010
    hi all.

    shoud'nt all of the older netcard drivers be added, as slitaz is so great on older hardware. i cannot use slitaz on my compaq evo n1020v, as there is no module for the realtek 8139.

    the optimal solution would to make an extra taz pakage with additional drivers for ethernet, and just add as many as possible (or more:) to this package. then there is no bloat for the linux kernel package, but via usb you could add the older drivers using this new linux-alt-ethernet.tazpkg.

    thanks for a great system. hop you like the idea.

    peter.
  • mojomojo February 2010
    peter

    Driver support for realtek 8139 is compiled into the kernel as module 8139too

    root@slitaz:/home/tux# lshw -C network
    *-network
    description: Ethernet interface
    product: RTL-8139/8139C/8139C+
    vendor: Realtek Semiconductor Co., Ltd.
    physical id: 0
    bus info: pci@0000:04:00.0
    logical name: eth0
    version: 10
    serial: 00:c0:26:63:2d:44
    size: 100MB/s
    capacity: 100MB/s
    width: 32 bits
    clock: 33MHz
    capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-f
    d 100bt 100bt-fd autonegotiation
    configuration: autonegotiation=on broadcast=yes driver=8139too driververs
    ion=0.9.28 duplex=full ip=192.168.123.4 latency=64 link=yes maxlatency=64 mingnt
    =32 module=8139too multicast=yes port=MII speed=100MB/s


    root@slitaz:/home/tux# lspci | grep Ethernet
    04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10


    tux@slitaz:~$ sudo find / -iname *8139too*
    /sys/bus/pci/drivers/8139too
    /sys/module/8139too
    /sys/module/8139too/drivers/pci:8139too


    Try as root

    ifconfig eth0 up

    then ifconfig

    if the interface eth0 shows up

    then udhcpc -i eth0


  • PeterPeter March 2010
    hi mojo

    thank you very much for your in depth reply.

    i've tried running the machine with the 8139 ehternet with slitaz 2.0 and it works out of the box.

    it seems that slitaz cooking 20091104 was missing the module files:

    tux@slitaz:~$ sudo find / -iname *8139too*
    /sys/bus/pci/drivers/8139too


    i've tried the new 20100221 cooking and the two module files are missing here also:

    /sys/module/8139too
    /sys/module/8139too/drivers/pci:8139too

    are they coming back?
  • jozeejozee March 2010
    8139too is built into kernel (and not as a module). No change since Stable 2.0. From kernel config:

     CONFIG_8139TOO=y


    Its strange its not working for u out of the box. Something else may not be right. Can you post your "dmesg|tail "
  • PeterPeter March 2010
    some where in dmesg it says :

    8139too Fast Ethernet driver 0.9.28
    8139too 0000:00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip, use 8139cp


    could this be the problem? 8139cp not compiled in kernel or as module?

    Here are the info from the compaq n1020v p180x430vc250

    this is from cooking 20091104:

    lspci:
    00:00.0 Host bridge: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP 340M] (rev 02)
    00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M]
    00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
    00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 02)
    00:07.0 ISA bridge: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
    00:0a.0 CardBus bridge: Texas Instruments PCI4410 PC card Cardbus Controller (rev 02)
    00:0a.1 FireWire (IEEE 1394): Texas Instruments PCI4410 FireWire Controller (rev 02)
    00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20)
    00:0c.0 Communication controller: Conexant Systems, Inc. HSF 56k HSFi Modem (rev 01)
    00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
    00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
    00:13.0 USB Controller: NEC Corporation USB (rev 41)
    00:13.1 USB Controller: NEC Corporation USB (rev 41)
    00:13.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
    01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 330M/340M/350M


    lsmod:
    Module                  Size  Used by    Not tainted
    battery 9952 0
    yenta_socket 20988 0
    rsrc_nonstatic 9136 1 yenta_socket
    pcmcia_core 27628 2 yenta_socket,rsrc_nonstatic
    snd_ali5451 16108 1
    snd_ac97_codec 88736 1 snd_ali5451
    ac97_bus 1308 1 snd_ac97_codec
    snd_pcm 51780 2 snd_ali5451,snd_ac97_codec
    snd_timer 16344 1 snd_pcm
    snd 43584 6 snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
    soundcore 5180 1 snd
    snd_page_alloc 7256 1 snd_pcm

  • PeterPeter March 2010
    ...continued
    this is from cooking 20091104:

    some of dmesg:
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 13 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:07: ioport range 0x40b-0x40b has been reserved
    system 00:07: ioport range 0x480-0x48f has been reserved
    system 00:07: ioport range 0x4d0-0x4d1 has been reserved
    system 00:07: ioport range 0x4d6-0x4d6 has been reserved
    system 00:07: ioport range 0x8000-0x807f could not be reserved
    system 00:07: ioport range 0xf500-0xf503 has been reserved
    system 00:07: ioport range 0xf510-0xf513 has been reserved
    system 00:08: iomem range 0x0-0x9ffff could not be reserved
    system 00:08: iomem range 0xdc000-0xdffff could not be reserved
    system 00:08: iomem range 0xe0000-0xfffff could not be reserved
    system 00:08: iomem range 0x100000-0x1dffffff could not be reserved
    system 00:08: iomem range 0xfff80000-0xffffffff has been reserved
    pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:01.0: IO window: 0xa000-0xafff
    pci 0000:00:01.0: MEM window: 0xf0300000-0xf03fffff
    pci 0000:00:01.0: PREFETCH window: 0x000000f8000000-0x000000fbffffff
    pci 0000:00:0a.0: CardBus bridge, secondary bus 0000:02
    pci 0000:00:0a.0: IO window: 0x001000-0x0010ff
    pci 0000:00:0a.0: IO window: 0x001400-0x0014ff
    pci 0000:00:0a.0: PREFETCH window: 0x30000000-0x33ffffff
    pci 0000:00:0a.0: MEM window: 0x34000000-0x37ffffff
    ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 10
    PCI: setting IRQ 10 as level-triggered
    pci 0000:00:0a.0: PCI INT A -> Link[LNK2] -> GSI 10 (level, low) -> IRQ 10
    pci_bus 0000:00: resource 0 io: [0x00-0xffff]
    pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
    pci_bus 0000:01: resource 0 io: [0xa000-0xafff]
    pci_bus 0000:01: resource 1 mem: [0xf0300000-0xf03fffff]
    pci_bus 0000:01: resource 2 pref mem [0xf8000000-0xfbffffff]
    pci_bus 0000:02: resource 0 io: [0x1000-0x10ff]
    pci_bus 0000:02: resource 1 io: [0x1400-0x14ff]
    pci_bus 0000:02: resource 2 pref mem [0x30000000-0x33ffffff]
    pci_bus 0000:02: resource 3 mem: [0x34000000-0x37ffffff]
    ...
    ide-cd driver 5.00
    ide-cd: hdc: ATAPI 24X DVD-ROM drive, 512kB Cache
    Uniform CD-ROM driver Revision: 3.20
    Driver 'sd' needs updating - please use bus_type methods
    Driver 'sr' needs updating - please use bus_type methods
    e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.4-k4
    e1000e: Copyright (c) 1999-2008 Intel Corporation.
    pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de
    e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
    e100: Copyright(c) 1999-2006 Intel Corporation
    ThunderLAN driver v1.15a
    TLAN: 0 devices installed, PCI: 0 EISA: 0
    ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
    PPP generic driver version 2.4.2
    PPP Deflate Compression module registered
    PPP BSD Compression module registered
    PPP MPPE Compression module registered
    NET: Registered protocol family 24
    8139too Fast Ethernet driver 0.9.28
    8139too 0000:00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip, use 8139cp
    tun: Universal TUN/TAP device driver, 1.6
    tun: (C) 1999-2004 Max Krasnyansky
    dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
    winbond-840.c:v1.01-e (2.4 port) Sep-11-2006 Donald Becker
    http://www.scyld.com/network/drivers.html
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
    PCI: setting IRQ 11 as level-triggered
    ehci_hcd 0000:00:13.2: PCI INT C -> Link[LNK3] -> GSI 11 (level, low) -> IRQ 11
    ehci_hcd 0000:00:13.2: EHCI Host Controller
    ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:13.2: irq 11, io mem 0xf0019c00
    ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 0.95
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 5 ports detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ACPI: PCI Interrupt Link [LNK8] enabled at IRQ 5
    PCI: setting IRQ 5 as level-triggered
    ohci_hcd 0000:00:02.0: PCI INT A -> Link[LNK8] -> GSI 5 (level, low) -> IRQ 5
    ohci_hcd 0000:00:02.0: OHCI Host Controller
    ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:02.0: irq 5, io mem 0xf0014000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    ohci_hcd 0000:00:13.0: PCI INT A -> Link[LNK3] -> GSI 11 (level, low) -> IRQ 11
    ohci_hcd 0000:00:13.0: OHCI Host Controller
    ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 3
    ohci_hcd 0000:00:13.0: irq 11, io mem 0xf0017000
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 3 ports detected
    ohci_hcd 0000:00:13.1: PCI INT B -> Link[LNK3] -> GSI 11 (level, low) -> IRQ 11
    ohci_hcd 0000:00:13.1: OHCI Host Controller
    ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 4
    ohci_hcd 0000:00:13.1: irq 11, io mem 0xf0018000
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    uhci_hcd: USB Universal Host Controller Interface driver
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    input: PC Speaker as /devices/platform/pcspkr/input/input0
    cpuidle: using governor ladder
    cpuidle: using governor menu
    usbcore: registered new interface driver hiddev
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    TCP cubic registered
    NET: Registered protocol family 17
    NET: Registered protocol family 15
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    Using IPI No-Shortcut mode
    Freeing unused kernel memory: 336k freed
    input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
    atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
    Synaptics Touchpad, model: 1, fw: 5.8, id: 0x9d48b1, caps: 0x904713/0x4006
    input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2
    ACPI: PCI Interrupt Link [LNK7] enabled at IRQ 5
    ALI 5451 0000:00:06.0: PCI INT A -> Link[LNK7] -> GSI 5 (level, low) -> IRQ 5
    Clocksource tsc unstable (delta = -120698971 ns)
    AC'97 1 does not respond - RESET
    AC'97 1 access is not valid [0xffffffff], removing mixer.
    ali mixer 1 creating error.
    yenta_cardbus 0000:00:0a.0: CardBus bridge found [0e11:0056]
    yenta_cardbus 0000:00:0a.0: Enabling burst memory read transactions
    yenta_cardbus 0000:00:0a.0: Using CSCINT to route CSC interrupts to PCI
    yenta_cardbus 0000:00:0a.0: Routing CardBus interrupts to PCI
    yenta_cardbus 0000:00:0a.0: TI: mfunc 0x01001c00, devctl 0x64
    yenta_cardbus 0000:00:0a.0: ISA IRQ mask 0x0098, PCI irq 10
    yenta_cardbus 0000:00:0a.0: Socket status: 30000006
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
    pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
    ACPI: Battery Slot [BAT0] (battery present)
  • jozeejozee March 2010
    Yes, you are right.8139cp is not included. From Kernel configs:

    # CONFIG_8139CP is not set 


    As we are preparing for Slitaz 3.0 release, I don't think Slitaz team will change the linux kernel config. Its frozen right now. We will include this after 3.0 release.

    For now, what you can do at your end is to change this line in kernel linux-2.6.30.6-slitaz.config file to
    CONFIG_8139CP=y 


    then recook the kernel.
     tazwok cook linux 


    Reinstall. It should be ok.

  • PeterPeter March 2010
    super. will do. thanks.

    maybe is it a good idea to make a tazpkg with extra modules for newbie slitaz users.

    especially with ethernet is important to have as many modules as possible, as you are dead in the water without it.
  • @Peter,
    I need to cook my kernel. As I understood, you are going to do the same as well.

    But before cooking, firstly I should clone the wok (right??). And it does not work for me, as stated here:

    http://forum.slitaz.org/index.php/discussion/676/can-not-clone-the-wok/#Item_1

    Would you mind giving me a hand?
    Please write down the list of all console operations needed to cook kernel with new option (8139cp for example). I mean the ones you are using.
    It may help me to figure out what I am doing wrong.

    Thank you in advance for your help.
    Stephane
  • ckmckm October 2010
    I know this is an older thread, but I've got the exact same issue. Since I don't have a spare computer to install Slitaz on and compile a new kernel, and networking doesn't work on the machine where I have Slitaz installed, I'm completely stuck.

    It would be really nice if someone made the .ko available, even just as a download, although a package would be much nicer. ATM, I've resorted to emailing one guy who blogged about this issue in the hopes he will email me his .ko.... While I'm waiting, I'm going to install Tiny Core in the hopes it doesn't have this issue...

    Chris.
  • mojomojo October 2010
    Post your Kernel version from:
    tux@slitaz: uname -r

    The 8139cp module will have to be compiled against your kernel version or it will not work.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

SliTaz Social