Red Hat Bugzilla – Bug 14444
boot.net + kickstart problem
Last modified: 2008-05-01 11:37:56 EDT
Anaconda developers, keep up the great work! I put a kickstart file on the beta4 bootnet.img file, and called it with 'expert ks=floppy'. The /proc/cmdline showed up as: expert ks=floppy initrd=initrd.img devfs=nomount BOOT_IMAGE=vmlinuz auto The installer gave me the "No Drives Found" message. Strange, I thought. It did the NFS mount properly. Messages on VT3 say: * unknown module aic7xxx * unexpected arguments to device probe command (note, I didn't specify deviceprobe command) * forcing device probe * kickstarting through device eth0 * sending dhcp request through device eth0 * nodns is 0 * revers name lookup failed * going to insmod sunrpc.o (path is NULL) * going to insmod lockd.o (path is NULL) * going to insmod nfs.o (path is NULL) * mounting nfs path ..... * found information on module eepro100 (specified in the ks.cfg) * unknown module aacraid (specified in the ks.cfg) * unknown module aic7xxx (specified in the ks.cfg) * unexpected arguments to deviceprobe command * forcing device probe * getting ready to spawn shell now * going to insmod raid[015].o,ext3.o (path is NULL) * looking for USB mouse... * no IDE floppy devices found It's the unknown module {aacraid, aic7xxx} that concern me. At this point I get the "No Drives Found" message, which is unexpected because the NFS instimage has already been mounted, and the modules.cgz file is at /modules/modules.cgz -> ../mnt/runtime/modules/modules.cgz. When I uncpio that into the /tmp directory, the aacraid and aic7xxx drivers *are* there. If I do this: cd /tmp/ uncpio < /mnt/runtime/modules/modules.cgz I get the error: cpio filaed on 2.2.16-12BOOT/dgrs.o: Success. My guess is this is innocent, as I ran out of room on the initrd. In any case, then in the 2.2.16-12BOOT directory, aic7xxx and aacraid are both there. So, why didn't this work? ks.cfg attached.
Created attachment 1447 [details] kickstart file
Fails the same way with beta 3. Cannot go back to beta 2, as the aacraid driver wasn't on the CD then. Note, using the bootnet.img and an hand expert GUI install, I can select the aacraid and aic7xxx drivers myself and it works just fine. It's only with kickstart that it doesn't load the driver.
Same with pinstripe. Note that plain 'linux ks=floppy' with the same ks.cfg works just fine. What we lose (it seems) is the ability to use the noprobe. Since 'linux ks=floppy' works, and 'expert ks=floppy' doesn't, I'm dropping the severity on this to low.
I'd like to have the noprobe option back, if at all possible. Can you revert out the deviceprobe code?
This defect is considered MUST-FIX for Winston Gold release
Fix sent to Matt Domsch
Indeed, the provided boot.img works with noprobe nicely. Thanks!