Messages in this thread | | | Date | Fri, 26 Feb 1999 00:21:45 -0800 (PST) | From | "David B. Rees" <> | Subject | Re: 2.2.1 and Tulip weirdness |
| |
On 25-Feb-99 Guenter L. Wolf wrote: > Hi again, > > Just remembered another thing I wanted to write earlier. When booting the > machine after the incident (just halting and pressing the reset-button), > it came up with: > > eth0: Digital DC21041 Tulip at 0x8100, 21040 compatible mode, EEPROM not > present, 00 4c 69 6e 75 79, IRQ 0. > eth1: Digital DC21041 Tulip at 0x8200, 21041 mode, 00 00 f8 30 6f 4f, IRQ > 17. > eth1:21041 Media information at 65, default media 0800 (Autosense). > eth1: 21041 media #0, 10baseT. > > But an pciscan already resolved to the 0:0:0:0:0:ff HW-address.... > > After power-cycling the machine it reported this HW-address but the > correct IRQ...
I noted the same thing on my Tulip DC21140 on 2.2.2 the other day. I got the EEPROM not present problem. A reboot did not fix it. Powercycling did not work either. Taking the card out and swapping PCI slots did work, though. I attribute the flakiness to the momentary loss of blue smoke. FWIW, I'm using a Shuttle-569 motherboard.
System info can be found at http://spoke.nols.com Here's the relevant info from the system logs:
Feb 20 00:18:56 spoke kernel: eth1: Digital DS21140 Tulip at 0x6400, EEPROM not present, 00 4c 69 6e 75 79, IRQ 0. Feb 20 00:18:56 spoke kernel: eth1: Missing EEPROM, this interface may not work correctly! Feb 20 00:18:56 spoke kernel: eth1: MII transceiver found at MDIO address 22, c onfig ffff status fbff.
And another:
Feb 20 00:24:52 spoke kernel: eth1: Digital DS21140 Tulip at 0x6400, ff 7f ff ff ff ff, IRQ 9. Feb 20 00:24:52 spoke kernel: eth1: Missing EEPROM, this interface may not work correctly!
-Dave
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |