[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re:RE: not quite happy with RH9 kickstart

Thanks Rob, a USB CD drive is another option.
However, I have now managed to get my install kickstarting from a single floppy!!
The problem I was having was in specifying the device driver to use.
I was trying to use the line: 'device ethernet e100' in my ks.cfg file (to use the e100 driver)
This would cause the installation to abort with this error message: "install exited abnormally -- received signal 11"
The line I had to use to make it work was: 'device eth e100 --opts=0'. The 'opts' part is important - I don't know exactly what it does, but without it the installation still breaks!
FYI, here's my dummies guide to getting the appropriate network drivers onto my single boot disk:

Get a copy of bootdisk.img and drvnet.img for RedHat9.0 from the images directory of the first CD.

Insert a floppy disk.

Copy the drivers disk image onto a floppy disk:


dd if=drvnet.img of=/dev/fd0 bs=72k


Mount the floppy disk to a partition, and copy all of the files off it into a directory on the hard drive, then unmount the disk again:


mount /dev/fd0 /mnt/floppy

mkdir /root/rh9drivers

cp /mnt/floppy/* /root/rh9drivers

umount /mnt/floppy


In the directory, unpack the ?modules.cgz? file containing the drivers. This will create a sub-directory called 2.4.20-8BOOT:


cd /root/rh9drivers

zcat modules.cgz | cpio ?id, this will create a new directory: 2.4.20-8BOOT.


Now copy the boot disk image onto your floppy disk:


dd if=bootdisk.img of=/mnt/floppy bs=72k


Mount the disk to a partition and copy the initrd image into a directory on the hard drive:


mount /dev/fd0 /mnt/floppy

mkdir /root/rh9boot

cp /mnt/floppy/initrd.img /root/rh9boot/initrd.data.gz


Unzip the initrd image and mount it onto a partition:


cd /root/rh9boot

gunzip initrd.data.gz

mkdir /mnt/image

mount ?o loop initrd.data /mnt/image


Copy the ?modules.cgz? file containing the drivers onto the hard drive and unpack it:


cp /mnt/image/modules/modules.cgz /root/rh9boot

zcat modules.cgz | cpio ?id, creates a new directory 2.4.20-8BOOT


Now you can remove any drivers from the boot disk that you don't need, and copy any network drivers you do need. I removed the scsi and usb drivers, and added e100 and e1000 drivers.


cd 2.4.20-8BOOT

rm scsi_mod.o, usb-storage.o, sr_mod.o and sd_mod.o

cp /root/rh9drivers/2.4.20-8BOOT/e100* /root/rh9boot/2.4.20-8BOOT


Remove the old copy of the modules file and create a new one:


rm /root/rh9boot/modules.cgz

find /root/rh9boot/2.4.20-8BOOT/*.* | cpio ?o -?format=crc | gzip ?9 > /root/rh9boot/modules.cgz


Fill the free space on the mounted initrd image with 0?s (this makes it compress much more efficiently), then remove the old ?modules.cgz? file, and replace it with the new one:


dd if=/dev/zero of=/mnt/image/modules/modules.cgz bs=1

rm /mnt/images/modules/modules.cgz

cp /root/rh9boot/modules.cgz /mnt/image/modules/modules.cgz


Put information about the e100 and e1000 drivers into the module-info file:


vi /root/rh9drivers/modinfo

Highlight the section for e100 and e100 and copy it.

Exit vi

vi /mnt/image/modules/module-info

Paste the e100 and e100 lines at the end of the file. Delete the files pertaining to the usb-storage driver.

Save and exit.


Copy all lines from /root/rh9drivers/pcitable describing e100 or e1000 into /mnt/image/modules/pcitable ? I?m not sure which lines are applicable to the cards we?ll be using so just copy them all.

Delete the lines about Sound Fusion Audio Accelerator and AMI Megaraid from /mnt/image/modules/pcitable.

Remove the lines about scsi_mod, sd_mod and sr_mod from /mnt/image/modules/modules.dep.



Unmount the image, rezip it, clear free space on the floppy disk and copy the new initrd image onto it:


umount /mnt/image

gzip ?9 /root/rh9boot/initrd.data

dd if=/dev/zero of=/mnt/floppy/initrd.img bs=1

rm /mnt/floppy/initrd.img

cp /root/rh9boot/initrd.data.gz /mnt/floppy/initrd.img

umount /mnt/floppy


And that was my finished floppy disk.



And here's my completed kickstart file. It doesn't do anything clever at the moment, just a basic install, but it works!



lang en_US.UTF-8

langsupport --default en_GB.UTF-8 en_GB.UTF-8

keyboard uk

mouse genericps/2 --device psaux --emulthree


device eth e100 --opts=0

network --device eth0 --bootproto static --ip <my_ip> --netmask <my_netmask> --gateway <my_gateway> --nameserver <my_dns> --hostname <my_hostname>

nfs --server <my_nfsserver> --dir <my_nfsdirectory>

rootpw --iscrypted <encrypted_password>

firewall --disabled

authconfig --enableshadow --enablemd5

timezone Europe/London

bootloader --location=mbr

# The following is the partition information you requested

# Note that any partitions you deleted are not expressed

# here so unless you clear all partitions first, this is

# not guaranteed to work

clearpart --linux

part /boot --fstype ext2 --size=200

part swap --size=512

part / --fstype ext2 --size=100 --grow



@ Administration Tools

@ British Support

@ Development Tools

@ Dialup Networking Support

@ Editors

@ Server Configuration Tools

@ System Tools

@ Text-based Internet

@ Web Server

@ Windows File Server




I hope this helps somebody. If anybody knows what the 'opts=0' flag does I'd be interested to know.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]