Re: eth0 problems all of a sudden
Hello petong,
If you can, try another network card. Looks like its bios may be fried
- I don't like the look of all those ff's and it looks like it may be
mis-reporting itself - the product code, revision and date aren't right,
the ram, Rx/Tx split and transceiver settings have all changed.
If you can't try another NIC, try this NIC in another system. Have you
actually powered the system down since this happened? Try shutting down
and then pulling the plug for a couple of minutes.
I'm not a NIC scientist though;-)
LeeE
petong wrote:
>
> Hi list,
>
> I am running unstable and yesterday I was attempting to shut down from kdm
> and my machine froze. Upon rebooting, I had problems with eth0. This is what
> I used to get on boot:
>
> PCI: Found IRQ 11 for device 00:0a.0
> 3c59x.c:LK1.1.15 6 June 2001 Donald Becker and others.
> http://www.scyld.com/network/vortex.html
> See Documentation/networking/vortex.txt
> 00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0x6c00, 00:10:4b:12:1c:6a, IRQ
> 11
> product code 4e4b rev 00.9 date 10-29-98
> 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
> MII transceiver found at address 24, status 786d.
> Enabling bus-master transmits and whole-frame receives.
> 00:0a.0: scatter/gather enabled. h/w checksums enabled
>
> I now get this:
> PCI: Enabling device 00:0a.0 (0000 -> 0003)
> PCI: Found IRQ 11 for device 00:0a.0
> 3c59x.c:LK1.1.15 6 June 2001 Donald Becker and others.
> http://www.scyld.com/network/vortex.html
> See Documentation/networking/vortex.txt
> 00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0x6c00, PCI: Setting latency
> timer of device 00:0a.0 to 64 ff:ff:ff:ff:ff:ff, IRQ 11
> product code ffff rev ffff.15 date 15-31-127 Full duplex capable
> 1024K word-wide RAM 3:5 Rx:Tx split, autoselect/<invalid transceiver>
> interface.
> Enabling bus-master transmits and early receives.
>
> I then get the error
> NETDEV WATCHDOG: eth0: transmit timed out
>
> can anyone shed some light for me on this problem?
>
> TIA
>
> -pete
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
http://www.spatial.freeserve.co.uk
...or something
Reply to: