Gentoo Archives: gentoo-user

From: "Benjamen R. Meyer" <bm_witness@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Creating an initrd for loading...
Date: Thu, 27 Mar 2008 23:24:55
Message-Id: 47EC1000.6090304@yahoo.com
In Reply to: Re: [gentoo-user] Creating an initrd for loading... by Florian Philipp
1 Florian Philipp wrote:
2 > On Thu, 2008-03-27 at 14:31 -0400, Benjamen R. Meyer wrote:
3 >> Florian Philipp wrote:
4 >>> On Thu, 2008-03-27 at 12:35 -0400, Benjamen R. Meyer wrote:
5 >>>> How can
6 >>>> I mount the initrd image to verify it has the modules, etc. and verify
7 >>>> it is a valid image?
8 >>> There is a wiki-entry about it: http://gentoo-wiki.com/HOWTO_Initramfs
9 >> Ok, so I used zcat to decompress the image, and then cpio to extract the
10 >> data to a temporary folder. (The instructions on the wiki didn't work
11 >> for some reason...complaints about finding cpio and zcat complaining
12 >> about arguments). Any how...
13 >>
14 >> I snooped around the extracted files and was unable to find either the
15 >> qla2xxx module (or the qla2200 modules, or any modules for that matter)
16 >> or the qla2200 firmware. The firmware is on the hard drive (/dev/sda1 ->
17 >> /lib/firmward/qla2200_fw.bin), and so is the module -
18 >> /lib/modules/2.6.24-gentoo-r3/kernel/drivers/scsi/qla2xxx/qla2xxx.ko. Is
19 >> the initrd image invalid?? Or are they stored somehow in the files
20 >> non-obviously?
21 >> How could I easily add them to the initrd image? (This is really my
22 >> first time playing with initrd images...)
23 > They are in lib/modules. I think it should work if you just copy the
24 > modules to their respective folder and add their names to the respective
25 > file in etc/modules.
26
27 Okay, I tried this two ways:
28
29 1) touched files in /etc/modules with the module names. (Probably not
30 right) - didn't work.
31
32 2) added all the files in
33 /lib/modules/2.6.24-gentoo-r3/kernel/drivers/scsi and sub-directories to
34 /etc/modules/scsi - didn't work. Perhaps I need to add the information
35 for the firmware???
36
37 > To create a initrd new initrd, use the following command:
38 > find . | cpio --quiet --dereference -o -H newc | gzip -9 >/boot/initrd
39
40 Okay, used this instead of the lengthy process I was doing before:
41
42 find ./ | cpio -H newc -o > /boot/initrd.bmeyer.cpio
43 gzip /boot/initrd.bmeyer.cpio
44 mv /boot/initrd.bmeyer.cpio.gz /boot/initrd.bmeyer
45
46 Any how...still stuck. Think I'm further along..but don't know.
47
48 FYI - right after it runs 'mdev' there is a line saying it can't find
49 'ls'...not sure if that is an error with mdev, or an error after mdev.
50 Either way, I can't find out since the system goes unusable until I
51 reboot manually (cycle power).
52
53 TIA,
54
55 Ben
56
57 --
58 gentoo-user@l.g.o mailing list