eth0 timing out
 

Hi :),

I've just successfully downloaded and compiled the source for my Ethernet card! It is now installed.

But (there's always a but isn't there), I'm experiencing problems with connecting to our LAN and hence the net.

We have three computers connected to ADSL through a router. Two of the machines are Win XP and mine is a dual-boot box with Win XP and Linux Red Hat 9.

When installing my ethernet card I copied the setting from the Win XP, which is: the card automatically gets its IP, IRQ 18 and a memory address. This info I copied into the network configuration on Linux.

Alas, Linux can't get an IP it seems. When booting it installs/recognizes the eth0 interface, but it fails with getting an IP.

In a terminal I tried to run 'dmesg | grep eth' and got:


--------------------------------------------------------------------------------

eth0: Broadcom BCM4401 100 Base-T found at mem ed8000, IRQ 10, node address 00e18
bcm440: eth0 NIC Link is up, 100 Mbps full duplex
NETDEV WATCHDOG: eth0: transmit timed out

--------------------------------------------------------------------------------


One thing about this puzzles me: At Windows my card is IRQ 18 and not 10 (which I've also entered into the Linux RH network configuration tool).

Some ideas?

I've been searching the net but so far none of the proposed solutions has hepled me. :cry:

I assume that by "get an IP" you're trying to use DHCP?

It's more work but you might want to try configuring a local, static IP address on the linux box to make sure that eth0 can be made to work on your system.

Alternatively, if you have three computers try loading ethereal (http://www.ethereal.com/) on one of the windows boxes to see what traffic is coming out of your linux box. I'm at that stage with a problem that I'm having right now, and it did help to focus the research somewhat.

Thanks for the reply :)

Yes, I'm using DHCP. Funny thing is when I booted for the umpteenth time it got an IP. That, of course, is great. But the problem do still exist which means that eny time the connection could go down. It's very puzzling indeed.

Anyway I've just downloaded all the updates from RHN and updated the kernel et. al - maybe that helps!!!

I will continue my search for the root of this problem :rolleyes: :rolleyes: