From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Avant Browser [avantbrowser.com]; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Description of problem: I've upgraded the kickstart installation to use the latest boot kernel: kernel- 2.4.20-18BOOT.i386.rpm. I've replaced the netstg1.img, bootnet.img, and stage2.img. When booting the bootnet.img the installed notices and tries to load the eepro100.o driver, which failed with unresolved symbols. Looking at the modules.dep in the initrd image, there is a missing entry for the eepro100 depending on the mii module. I believe this is a new dependency as of the 2.4.20 kernel, which now makes mii calls. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Rebuild kickstart image as described at: http://www.puschitz.com/Kickstart.shtml This can probably be replicated by simply trying to boot the 2.4.20-18BOOT image. Actual Results: kickstart halts Expected Results: eepro100 driver would load, and kickstart continue Additional info:
When you replaced everything did you also regenerate the modules.dep ?
I wasn't aware there was a standard process to regenerate the modules.dep. I used the modules.dep that came with the 2.4.20-18BOOT kernel, so I didn't figure it needed regenerating. Am I missing something?
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/