Modify or create the post-install driver, Diskette image – McDATA 8832 User Manual

Page 48

IBM BladeCenter Deployment Guide

22.

Copy the initrd.img file to the bootnet.img image.
# mv initrd.img mnt/boot

23.

Unmount the bootnet.img.
# umount mnt/boot

At this point the bootnet.img file should be ready for use in remote deployments.

8.1 Modify or Create the Post-install Driver Diskette Image

Create the supplemental driver disk containing drivers that will be used in the post-install
environment.

Up to this point, we have only been concerned with the drivers that will be used during installation
(the BOOT environment) to access storage and network devices. Since we are only updating the
ServeRAID drivers in this example, this step is easy – we simply make the driver diskette image file
(26k4970.img) available to the Red Hat installer by placing it on an accessible storage device (local or
remote) and specify the location in the kickstart file (see the Kickstart File Modification section below).

If we were adding the ServeRAID adapter to an existing driver diskette image, then we would have to
follow a process similar to that described in Section I, but instead of adding the device driver and
diskette image files to the boot image, we would add them to an already existing driver diskette image
file.

Kickstart File Modification

You must specify the location of the supplemental driver diskette image create in step II by placing
the following keyword and parameters in the Red Hat kickstart file:

If we are installing via FTP --

driverdisk

--source=ftp://path/to/26k4970.img

If we are installing via HTTP --

driverdisk

--source=http://path/to/26k4970.img

If we are installing via NFS --

driverdisk

--source=nfs:host:/path/to/26k4970.img

When adding a network device driver (such as bcm5700 and e1000) to the Red Hat installation initial
ramdisk image you must perform the following steps:

Create the following script (update_modules.sh) and place it in the rh3 directory of the NFS share.
Please note that, by default, it is assumed that the driver diskette image you created in section I has
the filename ‘dd.img’ and is located in the root directory of the NFS share.
#!/bin/sh
# constants
IMAGE_FILE=/dd.img
DEPMOD=/sbin/depmod

# save current directory
CWD=`pwd`
# create temporary directories
mkdir /tmp/mnt-$$
mkdir /tmp/modules-$$
mount -o loop $IMAGE_FILE /tmp/mnt-$$
cd /tmp/modules-$$
if [ ! -e /tmp/mnt-$$/modules.cgz ]; then
echo "malformed driver diskette image: $IMAGE_FILE"
exit 1

http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564

The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for

guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.