RE: eepro100

"Mroczek, Joseph T" <[email protected]> Fri, 3 Mar 2006 13:22:44 -0800
Newsgroups gmane.linux.drivers.eepro100.devel
Message-ID <C1B7430B33A4B14F80D29B5126C5E94709F02ADE@orsmsx401.amr.corp.intel.com>
Tony:

Most likely there is a new device ID on your adapter that is not recogniz=
ed by the drivers on your system. A driver update will likely resolve the=
 issue. You can get the latest eepro100 and e100 drivers at the URLs belo=
w. If the driver updates do not resolve the issue, please send the output=
 of the command: lcpsi -vvn (That is 2 Vs not a W).=20

eepro100:
http://www.scyld.com/driver_updates.html

e100:
http://downloadfinder.intel.com/scripts-df-external/Detail_Desc.aspx?strS=
tate=3DLIVE&ProductID=3D407&DwnldID=3D2896&agr=3DY&lang=3Deng

Regards,

Joe M.

________________________________________
From: [email protected] [mailto:[email protected]] On B=
ehalf Of [email protected]
Sent: Thursday, March 02, 2006 1:09 PM
To: [email protected]
Subject: [eepro100] eepro100

Hi

We have a Dell Power Edge running Red Hat 9.0 (2.4.20-8 kernel) with an I=
ntel Pro/100 VE ethernet adapter.
According to everything I have read, the driver should be e100.=A0 Well I=
 tried both e100 and eepro100 drivers
(/sbin/insmod <module>) but neither one worked.=A0 They both gave that er=
ror:

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 init_module: No such device
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Hint: insmod errors can be caused by=
 incorrect module parameters, including invalid IO or IRQ parameters.
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 You may find more information in sys=
log or the output from dmesg

Anyone have any idea what I should be using?


Thanks

Tony