public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Benjamen R. Meyer" <bm_witness@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Creating an initrd for loading...
Date: Thu, 27 Mar 2008 17:22:08 -0400	[thread overview]
Message-ID: <47EC1000.6090304@yahoo.com> (raw)
In-Reply-To: <1206649381.30987.115.camel@NOTE_GENTOO64.PHHEIMNETZ>

Florian Philipp wrote:
> On Thu, 2008-03-27 at 14:31 -0400, Benjamen R. Meyer wrote:
>> Florian Philipp wrote:
>>> On Thu, 2008-03-27 at 12:35 -0400, Benjamen R. Meyer wrote:
>>>>  How can 
>>>> I mount the initrd image to verify it has the modules, etc. and verify 
>>>> it is a valid image?
>>> There is a wiki-entry about it: http://gentoo-wiki.com/HOWTO_Initramfs
>> Ok, so I used zcat to decompress the image, and then cpio to extract the 
>> data to a temporary folder. (The instructions on the wiki didn't work 
>> for some reason...complaints about finding cpio and zcat complaining 
>> about arguments). Any how...
>>
>> I snooped around the extracted files and was unable to find either the 
>> qla2xxx module (or the qla2200 modules, or any modules for that matter) 
>> or the qla2200 firmware. The firmware is on the hard drive (/dev/sda1 -> 
>> /lib/firmward/qla2200_fw.bin), and so is the module - 
>> /lib/modules/2.6.24-gentoo-r3/kernel/drivers/scsi/qla2xxx/qla2xxx.ko. Is 
>> the initrd image invalid?? Or are they stored somehow in the files 
>> non-obviously?
>> How could I easily add them to the initrd image? (This is really my 
>> first time playing with initrd images...)
> They are in lib/modules. I think it should work if you just copy the
> modules to their respective folder and add their names to the respective
> file in etc/modules.

Okay, I tried this two ways:

1) touched files in /etc/modules with the module names. (Probably not 
right) - didn't work.

2) added all the files in 
/lib/modules/2.6.24-gentoo-r3/kernel/drivers/scsi and sub-directories to 
/etc/modules/scsi - didn't work. Perhaps I need to add the information 
for the firmware???

> To create a initrd new initrd, use the following command:
> find . | cpio --quiet --dereference -o -H newc | gzip -9 >/boot/initrd

Okay, used this instead of the lengthy process I was doing before:

find ./ | cpio -H newc -o > /boot/initrd.bmeyer.cpio
gzip /boot/initrd.bmeyer.cpio
mv /boot/initrd.bmeyer.cpio.gz /boot/initrd.bmeyer

Any how...still stuck. Think I'm further along..but don't know.

FYI - right after it runs 'mdev' there is a line saying it can't find 
'ls'...not sure if that is an error with mdev, or an error after mdev. 
Either way, I can't find out since the system goes unusable until I 
reboot manually (cycle power).

TIA,

Ben

-- 
gentoo-user@lists.gentoo.org mailing list



      reply	other threads:[~2008-03-27 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 16:35 [gentoo-user] Creating an initrd for loading Benjamen R. Meyer
2008-03-27 17:27 ` Florian Philipp
2008-03-27 18:31   ` Benjamen R. Meyer
2008-03-27 20:23     ` Florian Philipp
2008-03-27 21:22       ` Benjamen R. Meyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47EC1000.6090304@yahoo.com \
    --to=bm_witness@yahoo.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox