Thanks for your quick reply. I did this
and see the following:
Using the command prompt: The mount
command shows the device /tmp/cdrom mounted on /mnt/source and I can see all
the files from the CD there.
What is the difference between putting the
dd= command into the file isolinux.cfg vs. ks.cfg?
Would it be possible to have a
subdirectory on the instillation CD e.g. called Intel, that includes all the
drivers? Can you give me an idea how the dd= command would look
like then? (E.g. dd=//hdb/intel ??)
kickstart-list-bounces redhat com [mailto:kickstart-list-bounces redhat com] On Behalf Of Shabazian, Chip
Sent: Monday, April 09, 2007 10:25
To: Discussion list about
Subject: RE: Intel megasr RAID
driver not included with RHEL4
put the following in your %pre:
When the server is kickstarted, it will
stop in the pre environment, waiting for you to kill the sleep process.
Simply open a console session (alt-f2), see how the CD is seen by the system,
and use that device/path to load the driver using driverdisk in the kickstart
From: kickstart-list-bounces redhat com
[mailto:kickstart-list-bounces redhat com] On
Behalf Of Martin Steinmann
Sent: Sunday, April 08, 2007 4:28
To: kickstart-list redhat com
Subject: Intel megasr RAID driver
not included with RHEL4
We are using
a new Intel server S5000PAL that requires a RAID driver "megasr" not
included with RHEL4. We use kickstart installation and therefore cannot shuffle
CDs during the installation process to add a driver disk.
I am trying to modify the RHEL4 installation CD so that this driver is included
on the CD.
Can anyone point me to some documentation on how this can be
accomplished? Is kickstart able to automatically load a driver from a
directory on the same CD?
I now have a CD (RHEL4u4 CD1 with a ks.cfg file in the root of the CD. I copied
the content of the Intel driver disk for the megasr driver into the root of the
I then started experimenting with different settings in the file isolinux.cfg,
The kickstart file does not include any statements like dd or driverdisk (would
that be needed?).
None of this yields the desired result of an automated install where the
missing megasr driver is installed automatically. Looking on tty3 it seems the
system installs the libata driver and then sees two SATA disks (sda and sdb)
instead of the RAID 1 that is configured.
What I would like to do is have one CD that includes everything needed for a
RHEL4 minimum installation including the Intel megasr driver required for the
RAID controller of this Intel server.
I see another path creating a custom initrd.img and stage2.img file, but would
like to avoid this if possible.