BL465c and RHEL4U3 - supported, but no drivers??? (driver disks & ICLE)

[Don Vanco - Linux Ninja]

I don't know that this is purely an ICLE issue, but the fact is that I cannot install via ICLE for my customer so....

Due to a SAN requirement I need to load RHEL4U3. It's in the BL465c support matrix.

However, starting the install chain leaves the system siting, waiting for a correct device driver for the NICs. This is obviously a show stopper.

So - is there a way to "feed" a driver disk to the ICLE install chain process? Has someone built an initrd to support this???

[Don Vanco - Linux Ninja]

So, this was pointed out to me:

To use a driver disk you should be able to use the following line in your kickstart file:

driverdisk --source=http://host/path/to/dd.img

Store the driver disk on Control Tower under /var/rct/export/public/.......
And modify the above http line to match. Remember to set file permissions correctly and also verify that the driver disk image is downloadable by checking with your browser. Other options that the kickstart will accept (Control Tower only does the http method) are:

driverdisk --source=ftp://host/path/to/dd.img
driverdisk --source=http://host/path/to/dd.img
driverdisk --source=nfs:host:/path/to/img



Thanks for Richard Black from the ICLE team.
I kinda forgot that ICLE is using HTTP for the install and this was a KS option in RHEL 4

[Don Vanco - Linux Ninja]

Closed. See above.