Description of problem: On a system build with standard RH7.3 then with the kernel upgraded to 2.4.18- 24.7.x, certain Intel Pro 100 NICs are no longer correctly identified. Version-Release number of selected component (if applicable): kernel-2.4.18-24.7.x.i686.rpm How reproducible: Every time Steps to Reproduce: (Requires an Intel Pro/100 NIC verdorid:8086, deviceid:1229, subvendorid:8086, subdeviceid:0040 or 1015) 1. Install normal RH7.3 with only "Anonymous FTP" and "Web Server" packages. 2. Execute /usr/sbin/kudzu -p 3. Page-up to see the correctly identified Intel Pro 100 NIC. 4. Copy "kernel-2.4.18-24.7.x.i686.rpm" and "modutils-2.4.18-3.7x.i386.rpm" to the local disk. 5. Execute rpm -Fvh kernel-2.4.18-24.7.x.i686.rpm modutils-2.4.18-3.7x.i386.rpm 6. Reboot 7. Execute /usr/sbin/kudzu -p 8. Page-up to see the previously identified Intel Pro 100 NIC is no longer correctly identified. Actual results: System no longer correctly identifies Intel Pro 100 NIC with the following device and vendor IDs: verdorid:8086 subvendorid:8086 deviceid:1229 subdeviceid:0040 or 1015 Expected results: Intel Pro 100 NICs would continue to be correctly identified. Additional info: Diagnosis performed on COMPAQ Deskpro, CPQ Number: 368961-001 A system built with RH7.3 which has had ONLY its modutils upgraded to "modutils- 2.4.18-3.7x.i386.rpm" does NOT exhibit the problem.
what exact kernel was the last known good ?
The last known good kernel was 2.4.18-4. This is the kernel included with my RedHat 7.3 distribution. Although I can no longer test it, I am sure that things were working well as recent as kernel 2.4.18-18.7.x.
8086:1229 is the most common PRO/100 ven:device ID pair out there, so it's unlikely this is caused by a missing entry in the driver's device table, be it with eepro100 or e100. Is this caused by eepro100 being replaced by e100 in the newer kernel? Maybe /etc/modules.conf needs to be updated to replace the old eepro100 alias with e100?
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/