[nflug] Making Red Hat driver disks.

[Mark T. Valites]

I have notes from when I created a custom initrd back in RH 7.2 when the 
default kickstart image didn't include some modules I needed for a 
kickstart. The driver was in included on a supplemental disk, so it's not 
exactly the same problem, but it's in the same ballpark, so perhaps it 
will be helpfull.

You may be able to wedge your manually compiled module into it.

Creating custom RedHat kickstart floppies:
(eepro1000 with kickstart on poweredge 1650)
(http://lists.us.dell.com/pipermail/linux-poweredge/2002-July/020438.html)

With some help from John <jcouncilman - at - knology.net> in former 
threads, I was able to get my kickstart going.  John pointed me to a 
google cache page at the following url:

http://216.239.35.100/search?q=cache:vp3G_lH2k4cC:www.dulug.duke.edu/~mstenner/kickstart/add-driver+bootnet+img+add+driver+7.2&hl=en&ie=UTF-8

It's a little out of date & perhaps a little confusing, but it has all the 
info you need to get it done.  Here's exactly what I needed to do to get 
it working for a 1650 in 7.2.

-Make Bootdisks
         dd if=bootnet.img of=/dev/fd0
         dd if=drvnet.img of=/dev/fd0

-Create base directory to work out of
         mkdir base && cd base

-Grab relevant drivers from drvnet bootdisk (put correct disk in...)
         mount /dev/fd0 /mnt/floppy
         mkdir drvnet && cd drvnet
         cp /mnt/floppy/modules.cgz ./modules.cgz
         cp /mnt/floppy/modinfo ./modinfo
         cp /mnt/floppy/modules.dep ./modules.dep
         cp /mnt/floppy/pcitable ./pcitable
         umount /mnt/floppy
         gzip -d < modules.cgz | cpio -i --make-directories
         cd ../

-Work with bootnet.img bootdisk
         mount /dev/fd0 /mnt/floppy
         mkdir initrd-mod
         cp /mnt/floppy/initrd.img ./initrd.img.orig.gz
         gzip -d < initrd.img.orig.gz > initrd.img.change_me
         mkdir loop
         mount -t ext2 -o loop initrd.img.change_me loop
         cd loop/modules
         mkdir ../../modules-change_me
         cp * ../../modules-change_me
         cd ../../modules-change_me
         for file in *; do cp $file $file-orig; done
         gzip -d < modules.cgz | cpio -i --make-directories

         # 2.4.7-10BOOT gets created
         cd 2.4.7-10BOOT
         rm tulip.o pcnet32.o
         cp $base_dir/drvnet/2.4.7-10BOOT/eeproo1000.o .
         cd ../

         # edit module-info
         # (removed stanzas for pcnet32 & tulip)
         # (added stanza for  eepro1000)
         # (can be found in base/drvnet/module_info

         # edit pcitable

         # edit modules.dep
         # (not needed for me)

         rm modules.cgz
         find 2.4.7-10BOOT | cpio -o -H crc | gzip -9 > modules.cgz
         cd ../../
         umount loop
         # new initrd to floppy
         gzip -9 < initrd.img-change_me > initrd.img.new.gz
         cp -f initrd.img.new.gz /mnt/floppy/initrd.img
         umount /mnt/floppy

Then add the line below in your kickstart.

> device scsi aacraid --opts aacraid_pciid=0x1028,0x0A,0x1028,0x011B

to get it to pick up the hard disks.





On Wed, 13 Feb 2008, Dennis Ruzeski wrote:

> In a perfect world, it would be to complete the installation and then
> to use devices attached to boot from.
>
> I'll check those links.
>
> Thanks!
>
> --Dennis
>
>
>
> On Feb 13, 2008 12:36 PM, Darin Perusich
> <Darin.Perusich at cognigencorp.com> wrote:
>> Does the system need this controller to complete the installation or is
>> it a nice to have? Normally you'll just create an RPM of the driver and
>> add it to your installation sources and it can be included during the
>> install. This would be the case if it wasn't required for the
>> installation. If it's required for the installation then things start
>> getting a little more custom, i.e. custom installation cd's and initrd
>> images.
>>
>> I wasn't able to find anything RH specific but these references may be
>> helpful.
>>
>> http://www.suse.de/~ug/
>> http://wiki.openssi.org/go/Third_party_drivers
>> http://lists.centos.org/pipermail/centos/2004-June/042716.html
>>
>>
>> Dennis Ruzeski wrote:
>>> Greetings, group-
>>>
>>> I'm in a position where I need to be able to create a driver disk for
>>> RHEL 4 and 5 so that a controller without a driver in the kernel can
>>> get installed and boot. I'm having a hell of a hard time finding
>>> anything about creation of these disks. Does anyone have any insight
>>> or a link to a website that outlines this process?
>>>
>>
>> --
>> Darin Perusich
>> Unix Systems Administrator
>> Cognigen Corporation
>> 395 Youngs Rd.
>> Williamsville, NY 14221
>> Phone: 716-633-3463
>> Email: darinper at cognigencorp.com
>>
>> _______________________________________________
>> nflug mailing list
>> nflug at nflug.org
>> http://www.nflug.org/mailman/listinfo/nflug
>>
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
>