r. I was able to get a lights out disk made by customizing the image and putting the e1000.o module in 2 places. I originally used just the module in the modules.conf file, didn't work, then just in /tmp, didn't work. Placed it in both locations, and whoopie it worked. I had to re-create the initrd.img file so it would fit on the floppy, but then in the syslinux.cfg file I changed default to ks and then put ks=floppy on the ks line. What will bite you is when the system re-boots it will load the UP module and I would suggest you load a newer package when you are going through the kickstart. Once I did that, my problems went away after the new package installation. Scott On Mon, 2002-04-29 at 13:31, Raymond Prach wrote: > Hi all, > > I am having a similar problem. I am trying to create a lights-out > installation environment for RH 7.1 on some Dell PE-1650 servers, dual > CPU machines with Intel e1000 Pro network adapters. Unfortunately, the > suggestion below does not appear to work for me. I am using a boot > floppy based on the standard bootnet.img. I have added the e1000.o > module to the /tmp directory in the initial ramdisk, as well as adding > the appropriate lines to pcitable and modules.conf. When I boot with the > command line "ks", it first presents me with a menu of drivers to try; > when I choose the Intel 1000/PRO Gigabit driver, insmod fails with the > incredibly enlightening error message "%m". :P > > Having to use the supplemental driver disk sort of defeats the purpose > of the lights-out installation. Has anyone got an e1000-based machine to > perform a succesful network install from a single floppy, and if so, > how? > > I was thinking it might be worth it to try to make a new bootnet > installation disk based on a more recent kernel, say the 2.4.9-31BOOT > errata kernel. Is this likely to work? > > r. > > > > > > > Cool idea !! > > > > Can you sidestep any of those other steps below ? > > > > Cheers, Andy! > > > > On Thu, 28 Feb 2002, Frans Lawaetz wrote: > > > > > If you put the e1000 module in the tmp directory *beforehand* (i.e., > > > during the creation of the custom initrd.img) you are able to sidestep > > > the extraction problems. > > > > > > I imagine this might solve other module issues. > > > > > > -----Original Message----- > > > From: Frans Lawaetz [mailto:frans.lawaetz@xxxxxxxxxxxxxxxxxxxxxxx] > > > > > To get the e1000 module onto the regular bootnet.img disk I did the > > > following... > > > > > > First, the usual routine of gunzipping initrd.img, and then > > > gunzip&cpio the modules.cgz included within. I removed a few > > > networking modules that I didn't need, and added e1000.o that I took > > > from the supplemental network driver disk. > > > > > I carefully copied and pasted the definitions from modinfo on the NIC > > > driver disk to module-info on the bootnet.img disk .. and did the same > > > for the pcitab file. > > > > > I then cpio'd, gzip'd everything back together and made myself > > > a new boot floppy. > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list
