initrd.img module loading

[Peter Eisch]

The order you pass them to mkinitrd is the order in which they'll be loaded.
By the time kickstart gets around to doing anything, the kernel has already
laid out how devices are mapped.

Or are you looking for this in the ks.cfg:

  bootloader --driveorder=cciss/c0d0,sda,hda --location=mbr

peter

On 2/8/05 10:04 AM, "Ronald Reed" <rreed at ops.sgp.arm.gov> wrote:

> That is an interesting ideal, but I need the modules to load in a
> certain order during the kickstart. If the megaraid driver gets loaded
> first, then the external drive array gets setup as /dev/sda and the
> kickstart installs the external array as the main boot device. The boot
> prompt command scsihosts= is supposed to let you do that, but it doesn't
> seem to work.
> 
> Ron
> 
> On Mon, 2005-02-07 at 15:51, Peter Eisch wrote:
>> I'm not sure what your scope is, but maybe this helps...
>> 
>> I had an issue where I needed to forceload drivers where I knew the PCI info
>> was up to date for the devices we were loading on, so I forceloaded the
>> drivers in the initrd.img just as the kernel was being installed.  This, of
>> course, had to be done manually on the install cd's initrd.  But for the
>> various kernels I ended up with something like this in the spec files for
>> each platform:
>> 
>> %post bigmem
>> [ -x /usr/sbin/module_upgrade ] && /usr/sbin/module_upgrade
>> [ -x /sbin/mkkerneldoth ] && /sbin/mkkerneldoth
>> if [ -x /sbin/new-kernel-pkg ] ; then
>>         /sbin/new-kernel-pkg --mkinitrd --depmod --install %{KVERREL}bigmem
>> fi
>> /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with cciss \
>>        /boot/ninitrd-%{KVERREL}bigmem.img %{KVERREL}bigmem
>> /bin/mv /boot/initrd-%{KVERREL}bigmem.img /boot/oinitrd-%{KVERREL}bigmem.img
>> /bin/mv /boot/ninitrd-%{KVERREL}bigmem.img /boot/initrd-%{KVERREL}bigmem.img
>> 
>> 
>> Maybe do the --preloads in the order you need them loaded.  Hope this helps,
>> 
>> peter
>> 
>> 
>> On 2/7/05 2:31 PM, "Ronald Reed" <rreed at ops.sgp.arm.gov> wrote:
>> 
>>> I really don't want to rewrite anaconda, just to get one scsi module to
>>> load before another one.
>>> 
>>> I have tried the scsihosts= boot option, but the installer just seems to
>>> ignore it. I have also tried the expert noprobe boot options with device
>>> commands in the kickstart config file (Which worked in 7.1 - 7.3), and
>>> the system can not find any drives at that point.
>>> 
>>> What I need to do, is make sure that the aacraid driver is setup as
>>> /dev/sda and that the megaraid driver is setup as /dev/sdb during the
>>> install.
>>> 
>>> On Thu, 2005-02-03 at 22:40, johnpaul wrote:
>>>> Hi
>>>> 
>>>>     Have a look at the loader.c file in the loader2 directory of the
>>>> anaconda source
>>>> 
>>>> Regards
>>>> John
>>>> ----- Original Message -----
>>>> From: "Ronald Reed" <rreed at ops.sgp.arm.gov>
>>>> To: "Discussion list about Kickstart" <kickstart-list at redhat.com>
>>>> Sent: Thursday, February 03, 2005 10:49 PM
>>>> Subject: initrd.img module loading
>>>> 
>>>> 
>>>>> Where does the standard initrd.img get the order to load modules into
>>>>> the kernel?
>>>>> 
>>>>> I need to create a new initrd for a boot that loads some scsi raid
>>>>> modules in a specific order.
>>>>> -- 
>>>>> ===========================
>>>>> Ron Reed
>>>>> RedHat Certified Engineer
>>>>> SGP Computer Department Manager
>>>>> Unix Systems Administrator
>>>>> ARM SGP CART Site
>>>>> (580)388-4053
>>>>> ron.reed at arm.gov
>>>>> 
>>>>> _______________________________________________
>>>>> Kickstart-list mailing list
>>>>> Kickstart-list at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/kickstart-list
>>>> 
>>>> _______________________________________________
>>>> Kickstart-list mailing list
>>>> Kickstart-list at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/kickstart-list
>> 
>> _______________________________________________
>> Kickstart-list mailing list
>> Kickstart-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/kickstart-list