Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Fedora User (http://www.linux-archive.org/fedora-user/)
-   -   Initrd and bootup issue (http://www.linux-archive.org/fedora-user/630471-initrd-bootup-issue.html)

Dan Track 02-08-2012 08:39 PM

Initrd and bootup issue
 
Hi,

I need to load a kernel on my system but I've got a raid device which
needs a new driver added to initrd in order for it to be picked on
bootup when the kernel loads.

I've created the initrd by placing the module in a directory I created
in the initrd filesystem under: "/lib/modules/`uname
-r`/mydriver/mega.ko"

My problem is that when the kernel boots I get an error similar to

finding /dev/sda1 ....

It then fails and drops me to a shell, which I gather is the initrd
filesystem shell. Inside there if I issue the command modprobe mega.ko
the system finds the raid card, I then exit the shell and the server
boots up fine normally using the new kernel. My question is why does
this happen? I've added the module entry to the modules.dep file in
the initrd filesystem under: "/lib/modules/`uname -r`/modules.dep" and
running "modpobe -l" under teh initrd shell correctly shows this.

I must be missing a step, can someone please help me fix this?

Many thanks
Dan
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Rick Stevens 02-09-2012 04:37 PM

Initrd and bootup issue
 
On 02/08/2012 01:39 PM, Dan Track wrote:

Hi,

I need to load a kernel on my system but I've got a raid device which
needs a new driver added to initrd in order for it to be picked on
bootup when the kernel loads.

I've created the initrd by placing the module in a directory I created
in the initrd filesystem under: "/lib/modules/`uname
-r`/mydriver/mega.ko"

My problem is that when the kernel boots I get an error similar to

finding /dev/sda1 ....

It then fails and drops me to a shell, which I gather is the initrd
filesystem shell. Inside there if I issue the command modprobe mega.ko
the system finds the raid card, I then exit the shell and the server
boots up fine normally using the new kernel. My question is why does
this happen? I've added the module entry to the modules.dep file in
the initrd filesystem under: "/lib/modules/`uname -r`/modules.dep" and
running "modpobe -l" under teh initrd shell correctly shows this.

I must be missing a step, can someone please help me fix this?


You need to either have the driver built into the kernel or have it
stuffed into the initrd ramdisk image if it's a loadable module. See
the man pages for dracut and grubby for more info.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- You possess a mind not merely twisted, but actually sprained. -
----------------------------------------------------------------------
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


All times are GMT. The time now is 03:35 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.