Bug 87943 - (NET E100) e100 fail to work with Intel 82557/8/9
(NET E100) e100 fail to work with Intel 82557/8/9
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Garzik
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-04-03 16:54 EST by Marek Kassur
Modified: 2013-07-02 22:10 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-17 20:23:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
lspci -vv (6.05 KB, text/plain)
2003-04-03 16:56 EST, Marek Kassur
no flags Details
Output of dmesg (kernel: 2.4.22-1.2174.nptl) (8.31 KB, text/plain)
2004-03-17 10:40 EST, Marek Kassur
no flags Details

  None (edit)
Description Marek Kassur 2003-04-03 16:54:39 EST
Description of problem:
e100 driver output:

kernel: Intel(R) PRO/100 Network Driver - version 2.1.29-k2
kernel: Copyright (c) 2002 Intel Corporation
kernel: e100: hw init failed
kernel: e100: Failed to initialize, instance #0

However eepro100 works just fine:

kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@saw.sw.com.sg> and others
kernel: eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:B6:DB:6B, IRQ 10.
kernel:   Board assembly 000000-000, Physical connectors present: RJ45
kernel:   Primary interface chip i82555 PHY #1.
kernel:   General self-test: passed.
kernel:   Serial sub-system self-test: passed.
kernel:   Internal registers self-test: passed.
kernel:   ROM checksum self-test: passed (0x04f4518b).

How reproducible:

Steps to Reproduce:
Setup network using default e100 driver.

Additional info:
e100 driver works with RedHat 7.3
Comment 1 Marek Kassur 2003-04-03 16:56:39 EST
Created attachment 90885 [details]
lspci -vv
Comment 2 Scott Feldman 2004-03-03 23:03:05 EST
The failure to load was probably caused by the nic not having a valid 
eeprom checksum, but I can't be sure because 2.2.21 didn't print the 
exact reason why it failed (sorry).

A newer e100 driver would print the exact failure.  This doesn't fix 
the eeprom, but does give us exact cause for the failure of the 
driver to load.  Newer e100 drivers are here: 
http://sf.net/projects/e1000.  Please try a newer version and post 
output of dmesg.

The eeprom checksum check is necessary to detect 1) manufacturing 
problems, 2) user tampering, 3) counterfeit nics.
Comment 3 Marek Kassur 2004-03-17 10:38:41 EST
Newer driver from Fedora Core 1 works for me, maybe it was driver
problem. Output of dmesg attached.
Comment 4 Marek Kassur 2004-03-17 10:40:37 EST
Created attachment 98607 [details]
Output of dmesg (kernel: 2.4.22-1.2174.nptl)
Comment 5 Scott Feldman 2004-03-17 14:04:05 EST
Looks like issue can be closed.

Note You need to log in before you can comment on or make changes to this bug.