Re: Enabling the Intel 82562ET Nic
- From: Greg Tracy <greg.tracy@xxxxxxx>
- Date: Tue, 26 Sep 2006 14:00:12 GMT
I got it working. I did two things last night, and I'm not sure if one or both helped solve the problem.
First, I upgraded the e100 driver to 3.5.14. I got this from Intel's support page. After compiling and loading it, the problem was not resolved, however.
Second, I unplugged the unit and put it in the basement next to my router, and plugged it into the router with a new cable. Botta-bing, botta-boom. It worked. It's possible that there was a cabling problem. But I discount this since the same cable was used for a windows box. It's also possible that the router was just confused when the cable was moved back and forth, but still on the same port in the router itself. I did try clearing the DHCP list, and even moved the cable to another jack without success. The most likely solution - and I read this somewhere else (linux forums perhaps?) - was removing all power from the machine. Actually pulling the cable out of the back.
The reason I believe there is more to the story is that I tried this early on. Like I said the solution was some combination of the following....
1. upgrading the driver to 3.5.14
2. using different cabling
3. removing power from the pc
Good luck to anyone reading this down the road....
Greg
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
.
- Prev by Date: Re: ping problem ...
- Next by Date: help connecting to my linux machine with verizon dsl via ssh
- Previous by thread: Re: Enabling the Intel 82562ET Nic
- Next by thread: Reliability of SOCK_DGRAM Unix-Domain sockets
- Index(es):
Relevant Pages
|
