Hide Forgot
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: 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 http://www.scyld.com/network/eepro100.html 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: Always Steps to Reproduce: Setup network using default e100 driver. Additional info: e100 driver works with RedHat 7.3
Created attachment 90885 [details] lspci -vv
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.
Newer driver from Fedora Core 1 works for me, maybe it was driver problem. Output of dmesg attached.
Created attachment 98607 [details] Output of dmesg (kernel: 2.4.22-1.2174.nptl)
Looks like issue can be closed.