GRUB module query

[Tod Merley]

On 8/15/06, Dave S <ubuntu at pusspaws.net> wrote:
> I have a raid array which needs the IT821X kernel module. My hda / hdc HDDs
> are plugged into the raid controller and so the IT821X has to be directly
> compiled into the kernel since it needs it to boot :)
>
> This is a pain since I have to make my own kernel & recompile it when kernel
> updates occur.
>
> Is there a way to load the kernel with modules right from boot ? I tried
> editing grub menu/lst with ...
>
> kernel  /boot/vmlinuz-2.6.15-26-386 root=/dev/md0 IT821X ro quiet splash
>
> but no luck
>
> all help gratefully received
>
> thanks in advance
>
> Dave
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>

Hi Dave!

I think I would first try my edits from the GRUB boot menu.  Press a
key during the countdown and follow the prompts on the screen to edit.

I found this:

Generally, GRUB can boot any Multiboot-compliant OS in the following steps:

   1. Set GRUB's root device to the drive where the OS images are
stored by the command @command{root} (see section root).
   2. Load the kernel image by the command @command{kernel} (see
section kernel).Generally, GRUB can boot any Multiboot-compliant OS in
the following steps:

   1. Set GRUB's root device to the drive where the OS images are
stored by the command @command{root} (see section root).
   2. Load the kernel image by the command @command{kernel} (see
section kernel).
   3. If you need modules, load them with the command @command{module}
(see section module) or @command{modulenounzip} (see section
modulenounzip).
   4. Run the command @command{boot} (see section boot).

module

Command: module file ...
    Load a boot module file for a Multiboot format boot image (no
interpretation of the file contents are made, so that user of this
command must know what the kernel in question expects). The rest of
the line is passed as the module command-line, like the
@command{kernel} command. You must load a Multiboot kernel image
before loading any module. See also section modulenounzip.

modulenounzip

Command: modulenounzip file ...
    The same as @command{module} (see section module), except that
automatic decompression is disabled.

Here:

http://www.linuxselfhelp.com/gnu/grub/html_chapter/grub_4.html

http://www.linuxselfhelp.com/gnu/grub/html_chapter/grub_12.html#SEC87

It is part of the GRUB Manual - better accessed here:

http://www.gnu.org/software/grub/manual/

My menu.lst file's default kernel boot section looks like:


title           Ubuntu, kernel 2.6.15-26-386
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.15-26-386 root=/dev/hda1 ro quiet splash
initrd          /boot/initrd.img-2.6.15-26-386
savedefault
boot

I think adding the module command might look something like this:


title           Ubuntu, kernel 2.6.15-26-386
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.15-26-386 root=/dev/hda1 ro quiet splash
module      /lib/modules/2.6.15-26-386/kernel/drivers/ide/pci/it821x.ko
initrd          /boot/initrd.img-2.6.15-26-386
savedefault
boot

Dave, please help me in that I am putting together a "Boot Camp"
presentation for a LUG or two I am involved with and need to
understand this myself.  Please tell me what you find.

I also note with interest this:

tod at tod-desktop:~$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
psmouse
tod at tod-desktop:~$

Good Hunting - hope to hear from you!

Tod