How about building a customzied syslinux boot disk that includes the necessary drivers? Here is a url I came across when doing something similar with the bcm57xx gigabit network driver. http://lists.us.dell.com/pipermail/linux-poweredge/2003-August/014774.html * Jeff Lunde (Jeff_Lunde@xxxxxxx) on [030902 12:19] thus spake: > First off, many thanks to all on board for help in the past. > > With your help, I successfully created a ks.cfg for Redhat 7.3 on Intel > server w/Coosbay M/B. Everything is working great, and we have moved the > process to the field. > > Now, we are moving from the Intel Coosbay M/B server to the Intel Westville > II M/B server. What is the difference besides faster this and more powerful > that, lack of Intel support for Redhat 7.3. Intel is supporting Redhat 8.0 > with that server, basically I need to manually load the driver for Adapter > SCSI control and ethernet, otherwise everything else is the same as it > pertains to my ks.cfg. > > My problem is as follows: > > I need to use the Linux DD command to get things going, insert my diskette > with Adaptec SCSI controller driver, so the sfw. can find the hdd to > install. The problem is that I want combine the Linux DD step with my > kickstart script, which is modifying the install to meet our tested > parameters (users, defaults IP addresses, partition sizes, modules, etc...). > > > Is there a way to do this, to start my ks.cfg, so it loads the Adaptec SCSI > driver (otherwise the install will bomb out), and pick up my ks.cfg script. > Right now, if I do it manually, it skips the ks.cfg or doesn't prompt for > it? > > I cannot change the Redhat version, so I am stuck there. Also, I cannot use > a network install as we need to have this process mobile, and usable in the > field. > > Any advice would be greatly appreciated. > > Thx, > > JJL > > > > -------------------------------------------------------------------------- > Personal Motto: If you are going to jump in a grave, do it with both feet > > Jeffrey Joneal Lunde > Product Certification Engineer > > Cell: 762-242-1555 > Email: jeff_lunde@xxxxxxx > Office: 763.268.6891 > > CNT > 6000 Nathan Lane > Plymouth, MN 55442 > USA > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list -- ####[ Linux One Stanza Tip (LOST) ]########################### --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Sub LILO on boot sector of root partition LOST #298 --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Placing LILO on root partition instead of MBR maybe needed for a dual boot system where the other OS is at MBR.After checking /etc/lilo.conf, do '#lilo -v -v -C /etc/lilo.conf -r /' .. If /boot is the bootable partition change / to /boot. --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- ####<bish@xxxxxxxxxxxxxxx>#################################### _ _ \|/ o' \,=./ `o @-@ http://www.jak8us.org/~sam/ (o o) --ooO--(_)--Ooo---=--=---=--=---=---=---=--=---ooO--(_)--Ooo-- work: slmingol@xxxxxxxxxxx home: sam@xxxxxxxxxxx \ / GPG Pub. Key: http://www.jake8us.org/~sam/pubkey.asc --..---..---..---..---..---..---..---...---..---..---..---..--
