Thank you Scott, putting the module in /tmp of the ram disk worked, the module can be loaded. Though I was still prompted to select this from a list. Anyone know how to make the installer automatically load the right module? I'm trying for a completely automatic installation, no humans, no keyboard, this is a must! -Chad- On Thu, 2002-04-25 at 23:23, Scott Croft wrote: > There was a hint about the e1000.o module in another thread that you > might try. > Take the module and place it in the /tmp directory within the initrd.img > file. I did the same as mentioned in the other thread and it solved my > issues. If you run into a space issue on the disk after re-building the > initrd.img then remove unneeded files, create another img filesystem > that is smaller with dd, and put the data in that image file. > > As a side note, I have edited the ks.cfg file on a non-linux, non-pc > system, and a pc. Once I touched the file with something non-linux, it > ceased to function. I intentionally tried it with both after noticing > issues and asking Jeremy about it. > > Scott > > > On Thu, 2002-04-25 at 19:58, Chad M. Stewart wrote: > > > > I'm moving one step at time to my fully automatic install. > > > > I added the 8139too.o module from the 2.4.7-10BOOT kernel. I then > > edited module-info. I did not add anything to pcitable. I looked but > > did not see anything that looked similar for say a 3c5x9 ethernet card. > > > > I then created a bootable cdrom using this new image. It boots, > > /sbin/loader gets run, and then I get a screen asking for me to chose a > > ethernet interface, I can see the text I added, I select that and then > > get "Failed to insert 8139too module." If I switch to virtual console > > 3 I see "going to insmod 8139too.o (path is null)" > > > > I double checked the ISO image to be sure that the 8139too.o file is > > actually in modules.cgz and it is. > > > > Two questions > > > > Any idea how to fix the path is null problem? > > > > If the above is solved will I still be prompted to select my NIC? My > > goal is to have a NO KEYBOARD required install. While selecting a NIC is > > trival it does require human intervention and I'm trying very hard to > > avoid that. :) Once the above is solved, if I'm still prompted to > > select a NIC is there anyway to get around that? > > > > btw - Linux on the desktop ROCKS!! :) > > > > > > Thanks, > > Chad > > > > > > > > > > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/kickstart-list > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list
