Jeff Lunde wrote:
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.
Make a custom stage2.img with the adaptec module in it. Then be sure
to install either the adaptec driver rpm, or the module in your %post.
Be sure to use the latest adaptec driver from Gibbs.
http://people.freebsd.org/~gibbs/linux/
Here is what you do for redhat AS. The exact commands will be
slightly different for 7.3.
Open the drivers disk:
-mount -o loop aic79xx-1.3.10-i686-rhas21.img m2
-mkdir aic79xx
-cd aic79xx
-zcat ../m2/modules.cgz |cpio -vdi
Now the correct modules for the installer should be in 2.4.9-e.10BOOT
Make a new cramfs image
-cp stage2.img stage2.img.old
-mount -oloop stage2.img m1
-cp -a m1 cramfs
-cd cramfs/modules
-zcat modules.gz |cpio -ivd
-mkdir mymods
-mv 2.4.9-e.10BOOT mymods
-cd mymods
-cp (where the drivers disk's modules were)/2.4.9-e.10BOOT/aic79xx.o
2.4.9-e.10BOOT
-find . -type f | cpio -H crc -o | gzip -9 > ../modules.cgz
-cd ..
-rm -rf mymods
-edit modules.dep and add the following:
aic79xx: scsi_mod
-edit modinfo and add the contents of modinfo from the drivers disk
-edit pcitable and add the contents of modinfo from the drivers disk
-cd ../..
-mkcramfs tree stage2.img
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@xxxxxxxxxxxx>
