Description of problem: With Red Hat 9 changing the boot disks, I've had to modify the bootdisk.img to allow for network drivers. Simple enough tear down the initrd.img and modules.cgz then put it all back together after adding the drivers and updating pcitable, module-info and modules.dep. Ok so I boot with 'linux ks=floppy'. With the following line in the ks.cfg, the installer bombes out. device eth 3c59x However if I remove the line, then I get prompted to select the driver and the install continues on and works fine. Not sure what else I can provide. Here's the contents of ks.cfg. install lang en_US.UTF-8 langsupport --default en_US.UTF-8 en_US.UTF-8 keyboard us mouse genericwheelps/2 --device psaux skipx device eth 3c59x network --device eth0 --bootproto=static --ip=192.168.1.242 -- netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=192.168.1.1 url --url ftp://192.168.1.39/redhat/linux/9/en/os/i386 rootpw --iscrypted $1$ThisIsNotMyRealCryptedPW/ authconfig --enableshadow --enablemd5 timezone America/Chicago bootloader --location=mbr # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --linux part /boot --fstype ext3 --size=100 part / --fstype ext3 --size=700 --grow part swap --size=256 %packages @ Development Tools @ Dialup Networking Support @ FTP Server @ System Tools @ Text-based Internet %post How reproducible: Every Time Steps to Reproduce: 1. Rebuild initrd.img to include your network driver and update the pcitable, modules.dep, and module-info 2. add 'device eth 3c59x' or whatever you driver is to ks.cfg 3. watch it crash when it attempts to load drivers Actual results: Installer exits abnormally with signal 11 received. Expected results: Load the driver and continue the install Additional info: This is a show stopper for me and I know a lot of other people. What good is a kickstart function if you can't automate with net drivers? Please let me know what else I should provide. -Mike
Update on this....If you add --opts=0 to the device line, then all works well. I'm still not sure why the installer isn't picking up the nic card on a probe. After the build, it has NO problem seeing the card and the module is loaded just fine.
Go ahead and close this if ya like. There is still a problem I believe with the lack of --opts on the device line causing a complete bail out. I don't need the device line any more. Can you say TABS instead of SPACES in pcitable :)
Ok good to hear its working. Jeremy - shouldnt our parsing be more robust against this type of failure?
Fixed in CVS
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be fixed). If any of these are still a problem, please reopen or file a new bug against the release which they're occurring in so they can be properly tracked.