[eepro100] should i be worried about my eepro cards

[Joe Radinger]

--=-E2MvXSyTYtp3/5a7zrqN
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2002-06-13 at 21:17, Donald Becker wrote:=20
> On 13 Jun 2002, Joe Radinger wrote:
>=20
> > Subject: [eepro100] should i be worried about my eepro cards
>=20
> Yes.
>=20
> > 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 <becker@scyld.com>
> >   http://www.scyld.com/network/eepro100.html
> > divert: allocating divert_blk for eth0
>=20
> Presumably you are running a patched kernel to have the divert code...
i took your netdrivers-package.=20

> > eth0: Intel PCI EtherExpress Pro100 at 0xa0042000, 00:09:6B:B0:21:55,
> >   Board assembly ffffff-255, Physical connectors present: RJ45
>=20
> This must be the on-board NIC?  Usually that's at the end of bus 0
>=20
> > 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
>=20
> One pair, good detection.
>=20
> > 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
>=20
> Same type of board
>=20
> > eth5: Invalid EEPROM checksum 0x5773, check settings before activating
> > this device!
>=20
> Ohhh, bad news.
>=20
> > eth5: Intel PCI EtherExpress Pro100 at 0xa004c000, FF:FF:B3:A9:FF:FF,
>=20
> Bad station address.  All other information is suspect.
> Do not activate this device.
>=20
> >   Board assembly ffff31-002, Physical connectors present: RJ45
> >   Primary interface chip unknown-15 PHY #31.
>=20
> This will prevent the NIC from working correctly.
>=20
> > 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,
>=20
> > attached is the output from eepro100-diag -a -e -m -f
>=20
> Hmmm, the diag program didn't have a problem reading the EEPROM.
>=20
> 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.
>=20
> Try compiling the driver with the additional flag
>     -DUSE_IO_OPS
now i have a heavily patched kernel with netdrivers 3.1.1 AND the latest
eepro100.c v1.23=20
note that this output came from an older driver. v1.17a=20
without -DUSE_IO_OPS, its the same, but -DUSE_IO_OPS solved my problem
and arises an new one:
lack of knowledge: what does this option mean?


i tried the e100 driver from intel, seems to work, too.=20

thanks=20
josef

--=-E2MvXSyTYtp3/5a7zrqN
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA9DYy4yOLl//lX6PMRAqceAKCGnQ2Yv2QwvEhSB3y2IaPuXdZG9wCg30kk
RUJkJJcL38duLZ+LMFTRIIg=
=faeb
-----END PGP SIGNATURE-----

--=-E2MvXSyTYtp3/5a7zrqN--