Enabling the Intel 82562ET Nic

I've been struggling through a new Suse 10.1 install. Actually,
everything has gone well accept for my network configuration.

I'm running the following...

NIC: "HP 82562ET/EZ/GT/GZ - PRO/100 VE (LOM)
Kernel: 2.6.16.13-4

During the standard YaST install procedure, the card is detected, and
seemingly correctly configures the module name to e100. I have it
configured to use DHCP to acquire an address. However, during the
internet connection test, it fails to get out (no IP address is
obtained). The log displayed during this workflow says,

"DHCP client is already running on eth0"

1. After completing the installation, the card does appear to be working
partially. The loopback interface is up and I can ping localhost.

2. /var/log/messages has the following repeatedly...

"ifstatus-dhcp : eth0 dhcpd is still waiting for data
** this seems to be at odds with the log message during the internet
test, no?

3. dmesg produces the following during boot up...

"e100 : eth0 : e100_probe : addr 0xcfffe000, irq 209, MAC addr
00:17:31:A5:40:9E"
** no errors

4. lsmod lists the following for the e100 module...

"mii 5120 1 e100"
** what is mii? is this another interface that is stealing access?

I tried running 'modprobe e100', and then the lsmod lists both...

"e100 32264 0"
"mii 5120 1 e100"

5. i've tried adding an alias to the /etc/modprobe.conf file...

"alias eth0 e100" with no success.

6. i've tried using the eepro100 driver, but in that case, ifconfig
won't even find the eth0 interface.

7. there are no limitations (mac filtering, dhcp client limitations,
etc.) in my linksys router configuration that would explain the lack of
an IP address being served up.


This has been frustrating. Google tells me that others have struggled
with this problem using this network chipset, but there really is no
record of resolutions. Any thoughts would be appreciated.

Thanks.

Greg

btw, i've tried manually assigning an ip address without success...

[suse]: ifconfig eth0 192.168.1.111 broadcast 192.168.1.255 netmask
255.255.255.0 up
[suse]: route add -net 192.168.1.0 netmask 255.255.255.0 eth0


greg


Greg Tracy wrote:
>
> I've been struggling through a new Suse 10.1 install. Actually,
> everything has gone well accept for my network configuration.
>
> I'm running the following...
>
> NIC: "HP 82562ET/EZ/GT/GZ - PRO/100 VE (LOM)
> Kernel: 2.6.16.13-4
>
> During the standard YaST install procedure, the card is detected, and
> seemingly correctly configures the module name to e100. I have it
> configured to use DHCP to acquire an address. However, during the
> internet connection test, it fails to get out (no IP address is
> obtained). The log displayed during this workflow says,
>
> "DHCP client is already running on eth0"
>
> 1. After completing the installation, the card does appear to be working
> partially. The loopback interface is up and I can ping localhost.
>
> 2. /var/log/messages has the following repeatedly...
>
> "ifstatus-dhcp : eth0 dhcpd is still waiting for data
> ** this seems to be at odds with the log message during the internet
> test, no?
>
> 3. dmesg produces the following during boot up...
>
> "e100 : eth0 : e100_probe : addr 0xcfffe000, irq 209, MAC addr
> 00:17:31:A5:40:9E"
> ** no errors
>
> 4. lsmod lists the following for the e100 module...
>
> "mii 5120 1 e100"
> ** what is mii? is this another interface that is stealing access?
>
> I tried running 'modprobe e100', and then the lsmod lists both...
>
> "e100 32264 0"
> "mii 5120 1 e100"
>
> 5. i've tried adding an alias to the /etc/modprobe.conf file...
>
> "alias eth0 e100" with no success.
>
> 6. i've tried using the eepro100 driver, but in that case, ifconfig
> won't even find the eth0 interface.
>
> 7. there are no limitations (mac filtering, dhcp client limitations,
> etc.) in my linksys router configuration that would explain the lack of
> an IP address being served up.
>
>
> This has been frustrating. Google tells me that others have struggled
> with this problem using this network chipset, but there really is no
> record of resolutions. Any thoughts would be appreciated.
>
> Thanks.
>
> Greg

Greg Tracy wrote:
>
> I've been struggling through a new Suse 10.1 install. Actually,
> everything has gone well accept for my network configuration.
>
> I'm running the following...
>
> NIC: "HP 82562ET/EZ/GT/GZ - PRO/100 VE (LOM)
> Kernel: 2.6.16.13-4
>
> During the standard YaST install procedure, the card is detected, and
> seemingly correctly configures the module name to e100. I have it
> configured to use DHCP to acquire an address. However, during the
> internet connection test, it fails to get out (no IP address is
> obtained). The log displayed during this workflow says,
>
> "DHCP client is already running on eth0"
>
> 1. After completing the installation, the card does appear to be working
> partially. The loopback interface is up and I can ping localhost.

This *does not* prove anything about the NIC - the IP stack
is smart enough to route accesses to *any* of the local IP
addresses via the loopback interface.

Please verify the presence of the interface with

ifconfig -a

Do the cable link LEDs light at the NIC and the box at
the other end?

> 2. /var/log/messages has the following repeatedly...
>
> "ifstatus-dhcp : eth0 dhcpd is still waiting for data
> ** this seems to be at odds with the log message during the internet
> test, no?

It seems that your interface in there, but the thingy at the
other end of the cable does not understand to serve your
DHCP requests.

> 3. dmesg produces the following during boot up...
>
> "e100 : eth0 : e100_probe : addr 0xcfffe000, irq 209, MAC addr
> 00:17:31:A5:40:9E"
> ** no errors
>
> 4. lsmod lists the following for the e100 module...
>
> "mii 5120 1 e100"
> ** what is mii? is this another interface that is stealing access?

MII (Media Independent Interface) is a specification for the
connection between the Ethernet protocol engine and the media
access unit inside the modern Ethernet chips. It needs to be
set up by the NIC driver to enable the medium (means CAT-5 cable)
access properly. The module is OK and necessary here.


> 7. there are no limitations (mac filtering, dhcp client limitations,
> etc.) in my linksys router configuration that would explain the lack of
> an IP address being served up.

Very possible. If the box is providing a NAT service to the
internal network, it should provide DHCP also.

HTH

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio wrote:
> Greg Tracy wrote:
>>
>> I've been struggling through a new Suse 10.1 install. Actually,
>> everything has gone well accept for my network configuration.
>>
>> I'm running the following...
>>
>> NIC: "HP 82562ET/EZ/GT/GZ - PRO/100 VE (LOM)
>> Kernel: 2.6.16.13-4
>>
>> During the standard YaST install procedure, the card is detected, and
>> seemingly correctly configures the module name to e100. I have it
>> configured to use DHCP to acquire an address. However, during the
>> internet connection test, it fails to get out (no IP address is
>> obtained). The log displayed during this workflow says,
>>
>> "DHCP client is already running on eth0"
>>
>> 1. After completing the installation, the card does appear to be
>> working partially. The loopback interface is up and I can ping localhost.
>
> This *does not* prove anything about the NIC - the IP stack
> is smart enough to route accesses to *any* of the local IP
> addresses via the loopback interface.
>

I've since learned that the loopback works even without a NIC card
physically present...

> Please verify the presence of the interface with
>
> ifconfig -a
>

I'd print it here if it were easy, but you'll have to trust me that the
interface is present.

> Do the cable link LEDs light at the NIC and the box at
> the other end?
>

No lights at the other end of the tunnel....

>> 2. /var/log/messages has the following repeatedly...
>>
>> "ifstatus-dhcp : eth0 dhcpd is still waiting for data
>> ** this seems to be at odds with the log message during the internet
>> test, no?
>
> It seems that your interface in there, but the thingy at the
> other end of the cable does not understand to serve your
> DHCP requests.
>
>> 3. dmesg produces the following during boot up...
>>
>> "e100 : eth0 : e100_probe : addr 0xcfffe000, irq 209, MAC addr
>> 00:17:31:A5:40:9E"
>> ** no errors
>>
>> 4. lsmod lists the following for the e100 module...
>>
>> "mii 5120 1 e100"
>> ** what is mii? is this another interface that is stealing access?
>
> MII (Media Independent Interface) is a specification for the
> connection between the Ethernet protocol engine and the media
> access unit inside the modern Ethernet chips. It needs to be
> set up by the NIC driver to enable the medium (means CAT-5 cable)
> access properly. The module is OK and necessary here.
>
>

Thanks.


>> 7. there are no limitations (mac filtering, dhcp client limitations,
>> etc.) in my linksys router configuration that would explain the lack
>> of an IP address being served up.
>
> Very possible. If the box is providing a NAT service to the
> internal network, it should provide DHCP also.
>

I was thinking about trying a newer version of the e100 driver, but
there is nothing in the documentation that indicates the current one
would not work. Furthermore, Intel has nothing on their support site to
help troubleshoot this.

Thanks.

Greg

Tauno Voipio wrote:
> Greg Tracy wrote:
>>
>> I've been struggling through a new Suse 10.1 install. Actually,
>> everything has gone well accept for my network configuration.
>>
>> I'm running the following...
>>
>> NIC: "HP 82562ET/EZ/GT/GZ - PRO/100 VE (LOM)
>> Kernel: 2.6.16.13-4
>>
>> During the standard YaST install procedure, the card is detected, and
>> seemingly correctly configures the module name to e100. I have it
>> configured to use DHCP to acquire an address. However, during the
>> internet connection test, it fails to get out (no IP address is
>> obtained). The log displayed during this workflow says,
>>
>> "DHCP client is already running on eth0"
>>
>> 1. After completing the installation, the card does appear to be
>> working partially. The loopback interface is up and I can ping localhost.
>
> This *does not* prove anything about the NIC - the IP stack
> is smart enough to route accesses to *any* of the local IP
> addresses via the loopback interface.
>

I've since learned that the loopback works even without a NIC card
physically present...

> Please verify the presence of the interface with
>
> ifconfig -a
>

I'd print it here if it were easy, but you'll have to trust me that the
interface is present.

> Do the cable link LEDs light at the NIC and the box at
> the other end?
>

No lights at the other end of the tunnel....

>> 2. /var/log/messages has the following repeatedly...
>>
>> "ifstatus-dhcp : eth0 dhcpd is still waiting for data
>> ** this seems to be at odds with the log message during the internet
>> test, no?
>
> It seems that your interface in there, but the thingy at the
> other end of the cable does not understand to serve your
> DHCP requests.
>
>> 3. dmesg produces the following during boot up...
>>
>> "e100 : eth0 : e100_probe : addr 0xcfffe000, irq 209, MAC addr
>> 00:17:31:A5:40:9E"
>> ** no errors
>>
>> 4. lsmod lists the following for the e100 module...
>>
>> "mii 5120 1 e100"
>> ** what is mii? is this another interface that is stealing access?
>
> MII (Media Independent Interface) is a specification for the
> connection between the Ethernet protocol engine and the media
> access unit inside the modern Ethernet chips. It needs to be
> set up by the NIC driver to enable the medium (means CAT-5 cable)
> access properly. The module is OK and necessary here.
>
>

Thanks.


>> 7. there are no limitations (mac filtering, dhcp client limitations,
>> etc.) in my linksys router configuration that would explain the lack
>> of an IP address being served up.
>
> Very possible. If the box is providing a NAT service to the
> internal network, it should provide DHCP also.
>

I was thinking about trying a newer version of the e100 driver, but
there is nothing in the documentation that indicates the current one
would not work. Furthermore, Intel has nothing on their support site to
help troubleshoot this.

Thanks.

Greg

Greg Tracy wrote:
> Tauno Voipio wrote:
>
>> Greg Tracy wrote:
>>
>>>
>>> I've been struggling through a new Suse 10.1 install. Actually,
>>> everything has gone well accept for my network configuration.
>>>
>>> I'm running the following...
>>>
>>> NIC: "HP 82562ET/EZ/GT/GZ - PRO/100 VE (LOM)
>>> Kernel: 2.6.16.13-4
>>>
>>> During the standard YaST install procedure, the card is detected, and
>>> seemingly correctly configures the module name to e100. I have it
>>> configured to use DHCP to acquire an address. However, during the
>>> internet connection test, it fails to get out (no IP address is
>>> obtained). The log displayed during this workflow says,
>>>
>>> "DHCP client is already running on eth0"
>>>
>>> 1. After completing the installation, the card does appear to be
>>> working partially. The loopback interface is up and I can ping
>>> localhost.
>>
>>
>> This *does not* prove anything about the NIC - the IP stack
>> is smart enough to route accesses to *any* of the local IP
>> addresses via the loopback interface.
>>
>
> I've since learned that the loopback works even without a NIC card
> physically present...
>
>> Please verify the presence of the interface with
>>
>> ifconfig -a
>>
>
> I'd print it here if it were easy, but you'll have to trust me that the
> interface is present.

This means that the driver is probably OK, let's bark
at other trees in the meantime.

>> Do the cable link LEDs light at the NIC and the box at
>> the other end?
>>
>
> No lights at the other end of the tunnel....

If there are link LEDs which do not light, you do have
cabling problems. Maybe you need a crossed Ethernet cable
instead of the straight one.

--

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio wrote:
> Greg Tracy wrote:
>> Tauno Voipio wrote:
>>
>>> Greg Tracy wrote:
>>>
>>>>
>>>> I've been struggling through a new Suse 10.1 install. Actually,
>>>> everything has gone well accept for my network configuration.
>>>>
>>>> I'm running the following...
>>>>
>>>> NIC: "HP 82562ET/EZ/GT/GZ - PRO/100 VE (LOM)
>>>> Kernel: 2.6.16.13-4
>>>>
>>>> During the standard YaST install procedure, the card is detected,
>>>> and seemingly correctly configures the module name to e100. I have
>>>> it configured to use DHCP to acquire an address. However, during the
>>>> internet connection test, it fails to get out (no IP address is
>>>> obtained). The log displayed during this workflow says,
>>>>
>>>> "DHCP client is already running on eth0"
>>>>
>>>> 1. After completing the installation, the card does appear to be
>>>> working partially. The loopback interface is up and I can ping
>>>> localhost.
>>>
>>>
>>> This *does not* prove anything about the NIC - the IP stack
>>> is smart enough to route accesses to *any* of the local IP
>>> addresses via the loopback interface.
>>>
>>
>> I've since learned that the loopback works even without a NIC card
>> physically present...
>>
>>> Please verify the presence of the interface with
>>>
>>> ifconfig -a
>>>
>>
>> I'd print it here if it were easy, but you'll have to trust me that
>> the interface is present.
>
> This means that the driver is probably OK, let's bark
> at other trees in the meantime.
>
>>> Do the cable link LEDs light at the NIC and the box at
>>> the other end?
>>>
>>
>> No lights at the other end of the tunnel....
>
> If there are link LEDs which do not light, you do have
> cabling problems. Maybe you need a crossed Ethernet cable
> instead of the straight one.
>

I have been taking the same, physical cable and putting it in my windows
box with success. I switch it back and forth to give my wife her email.

I have this cable running from the basement and into a wall jack. I will
try moving the machine down to the router and using a new cable...

Greg