Problems with ethernet - Slackware

This is a discussion on Problems with ethernet - Slackware ; Hi. I've been a Linux user for a long time and recently switched from Debian Sid to Slackware 12.0 (just for the hell of it). Everything about this transition has gone rather smoothly... everything except for the setup of my ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Problems with ethernet

  1. Problems with ethernet

    Hi. I've been a Linux user for a long time and recently switched from
    Debian Sid to Slackware 12.0 (just for the hell of it). Everything
    about this transition has gone rather smoothly... everything except
    for the setup of my ethernet card. Basically, I've read the manual
    and tried what is said there, but I can't seem to find the correct
    driver, or the correct driver doesn't seem to work properly. I have
    attempted to load many different kernel modules but none of them have
    worked. This is really a last resort; I am assuming that this is a
    pretty mundane thing to be bothered with.

    Here is some info:

    themoth@chaplas ~ $ /sbin/lspci |grep -i ethernet
    08:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network
    Connection (rev 01)

    themoth@chaplas ~ $ dmesg |grep eth
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    eth0: no IPv6 routers present
    eth0: no IPv6 routers present

    (My wireless card works fine.)

    themoth@chaplas ~ $ sudo modprobe eepro100
    themoth@chaplas ~ $ dmesg| tail
    ipw3945: ERROR: No TX rate available.
    ipw3945: tx cmd rate scale failed.
    ipw3945: ERROR: No TX rate available.
    ipw3945: tx cmd rate scale failed.
    ipw3945: ERROR: No TX rate available.
    ipw3945: tx cmd rate scale failed.
    ipw3945: ERROR: No TX rate available.
    ipw3945: tx cmd rate scale failed.
    eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
    eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V.
    Savochkin and others

    (I'm almost positive that is the correct module. Alas...)

    themoth@chaplas ~ $ ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:13:02:45:82:02
    inet addr:209.222.194.177 Bcast:209.222.194.255 Mask:
    255.255.255.0
    inet6 addr: fe80::213:2ff:fe45:8202/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:907 errors:4 dropped:34252 overruns:0 frame:0
    TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:10120897 (9.6 MiB) TX bytes:1126676 (1.0 MiB)
    Interrupt:19 Base address:0xe000 Memory:54000000-54000fff

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:2016 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2016 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:176953 (172.8 KiB) TX bytes:176953 (172.8 KiB)


    Does anyone have any idea what is going on here? I would really like
    to connect to my college's LAN without resorting to the wireless,
    which is ungodly slow here.

    Thanks,
    Nori

  2. Re: Problems with ethernet

    On Apr 29, 12:33 am, Nori wrote:
    > Hi. I've been a Linux user for a long time and recently switched from
    > Debian Sid to Slackware 12.0 (just for the hell of it). Everything
    > about this transition has gone rather smoothly... everything except
    > for the setup of my ethernet card. Basically, I've read the manual
    > and tried what is said there, but I can't seem to find the correct
    > driver, or the correct driver doesn't seem to work properly. I have
    > attempted to load many different kernel modules but none of them have
    > worked. This is really a last resort; I am assuming that this is a
    > pretty mundane thing to be bothered with.
    >
    > Here is some info:
    >
    > themoth@chaplas ~ $ /sbin/lspci |grep -i ethernet
    > 08:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network
    > Connection (rev 01)
    >
    > themoth@chaplas ~ $ dmesg |grep eth
    > ADDRCONF(NETDEV_UP): eth0: link is not ready
    > eth0: no IPv6 routers present
    > eth0: no IPv6 routers present
    >
    > (My wireless card works fine.)
    >
    > themoth@chaplas ~ $ sudo modprobe eepro100
    > themoth@chaplas ~ $ dmesg| tail
    > ipw3945: ERROR: No TX rate available.
    > ipw3945: tx cmd rate scale failed.
    > ipw3945: ERROR: No TX rate available.
    > ipw3945: tx cmd rate scale failed.
    > ipw3945: ERROR: No TX rate available.
    > ipw3945: tx cmd rate scale failed.
    > ipw3945: ERROR: No TX rate available.
    > ipw3945: tx cmd rate scale failed.
    > eepro100.c:v1.09j-t 9/29/99 Donald Beckerhttp://www.scyld.com/network/eepro100.html
    > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V.
    > Savochkin and others
    >
    > (I'm almost positive that is the correct module. Alas...)
    >
    > themoth@chaplas ~ $ ifconfig -a
    > eth0 Link encap:Ethernet HWaddr 00:13:02:45:82:02
    > inet addr:209.222.194.177 Bcast:209.222.194.255 Mask:
    > 255.255.255.0
    > inet6 addr: fe80::213:2ff:fe45:8202/64 Scope:Link
    > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    > RX packets:907 errors:4 dropped:34252 overruns:0 frame:0
    > TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:1000
    > RX bytes:10120897 (9.6 MiB) TX bytes:1126676 (1.0 MiB)
    > Interrupt:19 Base address:0xe000 Memory:54000000-54000fff
    >
    > lo Link encap:Local Loopback
    > inet addr:127.0.0.1 Mask:255.0.0.0
    > inet6 addr: ::1/128 Scope:Host
    > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > RX packets:2016 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:2016 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:0
    > RX bytes:176953 (172.8 KiB) TX bytes:176953 (172.8 KiB)
    >
    > Does anyone have any idea what is going on here? I would really like
    > to connect to my college's LAN without resorting to the wireless,
    > which is ungodly slow here.
    >
    > Thanks,
    > Nori


    I also failed to include this (for what it is worth):

    themoth@chaplas ~ $ uname -a
    Linux chaplas 2.6.21.5-smp #2 SMP Tue Jun 19 14:58:11 CDT 2007 i686
    Genuine Intel(R) CPU T2050 @ 1.60GHz GenuineIntel GNU/Linux

    Thanks again,
    Nori

  3. Re: Problems with ethernet

    noridotjabi@gmail.com wrote:
    > Hi. I've been a Linux user for a long time and recently switched from
    > Debian Sid to Slackware 12.0 (just for the hell of it). Everything
    > about this transition has gone rather smoothly... everything except
    > for the setup of my ethernet card. Basically, I've read the manual
    > and tried what is said there, but I can't seem to find the correct
    > driver, or the correct driver doesn't seem to work properly. I have
    > attempted to load many different kernel modules but none of them have
    > worked. This is really a last resort; I am assuming that this is a
    > pretty mundane thing to be bothered with.
    >
    > Here is some info:
    >
    > themoth@chaplas ~ $ /sbin/lspci |grep -i ethernet
    > 08:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network
    > Connection (rev 01)
    >
    > themoth@chaplas ~ $ dmesg |grep eth
    > ADDRCONF(NETDEV_UP): eth0: link is not ready
    > eth0: no IPv6 routers present
    > eth0: no IPv6 routers present
    >
    > (My wireless card works fine.)
    >
    > themoth@chaplas ~ $ sudo modprobe eepro100

    ....
    > (I'm almost positive that is the correct module. Alas...)


    I am pretty sure you have the wrong module. Try e100, which is the
    Intel-written and supported module for their PRO/100 chips.
    (Not sure why it isn't auto-loading this for you.)

  4. Re: Problems with ethernet

    On Apr 29, 12:53 am, ljb wrote:
    > noridotj...@gmail.com wrote:
    > > Hi. I've been a Linux user for a long time and recently switched from
    > > Debian Sid to Slackware 12.0 (just for the hell of it). Everything
    > > about this transition has gone rather smoothly... everything except
    > > for the setup of my ethernet card. Basically, I've read the manual
    > > and tried what is said there, but I can't seem to find the correct
    > > driver, or the correct driver doesn't seem to work properly. I have
    > > attempted to load many different kernel modules but none of them have
    > > worked. This is really a last resort; I am assuming that this is a
    > > pretty mundane thing to be bothered with.

    >
    > > Here is some info:

    >
    > > themoth@chaplas ~ $ /sbin/lspci |grep -i ethernet
    > > 08:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network
    > > Connection (rev 01)

    >
    > > themoth@chaplas ~ $ dmesg |grep eth
    > > ADDRCONF(NETDEV_UP): eth0: link is not ready
    > > eth0: no IPv6 routers present
    > > eth0: no IPv6 routers present

    >
    > > (My wireless card works fine.)

    >
    > > themoth@chaplas ~ $ sudo modprobe eepro100

    > ...
    > > (I'm almost positive that is the correct module. Alas...)

    >
    > I am pretty sure you have the wrong module. Try e100, which is the
    > Intel-written and supported module for their PRO/100 chips.
    > (Not sure why it isn't auto-loading this for you.)


    Thank you so much! It works now, it was e100. I guess I didn't find
    it since it wasn't even in rc.modules... In any event, thanks a
    bunch. I'm going to go plug my computer into a wall!

  5. Re: Problems with ethernet

    On 2008-04-29, Nori wrote:
    > On Apr 29, 12:53 am, ljb wrote:
    >> noridotj...@gmail.com wrote:
    >>
    >> > themoth@chaplas ~ $ /sbin/lspci |grep -i ethernet
    >> > 08:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network
    >> > Connection (rev 01)
    >> >
    >> > themoth@chaplas ~ $ sudo modprobe eepro100
    >> > (I'm almost positive that is the correct module. Alas...)

    >>
    >> I am pretty sure you have the wrong module. Try e100, which is the
    >> Intel-written and supported module for their PRO/100 chips.
    >> (Not sure why it isn't auto-loading this for you.)

    >
    > Thank you so much! It works now, it was e100. I guess I didn't find
    > it since it wasn't even in rc.modules... In any event, thanks a
    > bunch. I'm going to go plug my computer into a wall!



    Do you have udev disabled or something, or did you upgrade from a
    previous Slackware release? In a stock "out of the box" unmolested
    fresh installation, the e100 module will be automatically loaded.

    -RW

+ Reply to Thread