Re: should i be worried about my eepro cards
Donald Becker <[email protected]>
| Newsgroups | gmane.linux.drivers.eepro100.devel |
|---|---|
| Message-ID | <Pine.LNX.4.33.0206131507370.1828-100000@presario> |
On 13 Jun 2002, Joe Radinger wrote: > Subject: [eepro100] should i be worried about my eepro cards Yes. > 33Mhz pci + 66Mhz pci > 4*dualport eepro100 cards (two on 33Mhz, two on 66Mhz) > 1 onboard eepro100 > > eepro100.c:v1.17a 8/7/2001 Donald Becker <[email protected]> > http://www.scyld.com/network/eepro100.html > divert: allocating divert_blk for eth0 Presumably you are running a patched kernel to have the divert code... > eth0: Intel PCI EtherExpress Pro100 at 0xa0042000, 00:09:6B:B0:21:55, > Board assembly ffffff-255, Physical connectors present: RJ45 This must be the on-board NIC? Usually that's at the end of bus 0 > eth1: Intel PCI EtherExpress Pro100 at 0xa0044000, 00:02:B3:A9:A2:F9, > Board assembly a56831-002, Physical connectors present: RJ45 > eth2: Intel PCI EtherExpress Pro100 at 0xa0046000, 00:02:B3:A9:A2:FA, > Board assembly a56831-002, Physical connectors present: RJ45 One pair, good detection. > eth3: Intel PCI EtherExpress Pro100 at 0xa0048000, 00:02:B3:A9:A5:E7, > Board assembly a56831-002, Physical connectors present: RJ45 > eth4: Intel PCI EtherExpress Pro100 at 0xa004a000, 00:02:B3:A9:A5:E8, > Board assembly a56831-002, Physical connectors present: RJ45 Same type of board > eth5: Invalid EEPROM checksum 0x5773, check settings before activating > this device! Ohhh, bad news. > eth5: Intel PCI EtherExpress Pro100 at 0xa004c000, FF:FF:B3:A9:FF:FF, Bad station address. All other information is suspect. Do not activate this device. > Board assembly ffff31-002, Physical connectors present: RJ45 > Primary interface chip unknown-15 PHY #31. This will prevent the NIC from working correctly. > eth6: Invalid EEPROM checksum 0x5673, check settings before activating > this device! > eth6: Intel PCI EtherExpress Pro100 at 0xa004e000, FF:FF:B3:A9:FF:FF, > IRQ 15. > eth7: Invalid EEPROM checksum 0x1d72, check settings before activating > this device! > eth7: Intel PCI EtherExpress Pro100 at 0xa0050000, FF:FF:B3:A9:FF:FF, > eth8: Invalid EEPROM checksum 0x1c72, check settings before activating > this device! > eth8: Intel PCI EtherExpress Pro100 at 0xa0052000, FF:FF:B3:A9:FF:FF, > attached is the output from eepro100-diag -a -e -m -f Hmmm, the diag program didn't have a problem reading the EEPROM. Which interfaces are on the 66Mhz bus? I've tested the driver with a 66Mhz PCI bus, but there might be some timing issue. Or this might just be a bus bridge issue. Try compiling the driver with the additional flag -DUSE_IO_OPS -- Donald Becker [email protected] Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993