From: Brian Gerst <bgerst@didntduck.org>
To: rol@as2917.net
Cc: linux-kernel@vger.kernel.org, rol@witbe.net
Subject: Re: Linux and Initrd used to access disk : how does it work ?
Date: Tue, 24 May 2005 11:18:45 -0400 [thread overview]
Message-ID: <429345D5.7070406@didntduck.org> (raw)
In-Reply-To: <200505241356.j4ODuaR07145@tag.witbe.net>
Paul Rolland wrote:
> Hello,
>
> I've been fighting for a few days with binary modules from some manufacturer
> for hardware support of disk controler, and I'm at a point where I need
> some more understanding.
>
> 1 - My machine contains an Adaptec SATA Raid based on Marvel 88SX60xx
> so I need to used the aar81xxx binary module,
>
> 2 - This module is presented as required to access the disk (when
> installing a RH kernel, it says that no disk is present unless the
> module is loaded),
>
> 3 - When booting the kernel from disk after installation, the module is
> loaded so the machine can access the disk...
>
> ... BUT ... how can the machine /
> - boot the kernel,
> - access the initrd image and uncompress it,
> - read the binary module inside and load it
> BEFORE loading the module itself, if it is mandatory to access the disk.
>
> And if it is not, then how can I do the installation ?
>
> I suspect this should be fairly trivial, but I've been thinking about
> for long, and it looks like chicken and egg to me...
>
> Any help ?
The kernel and initrd images are loaded by the bootloader (grub, lilo,
etc.), which uses the BIOS to read from the disk. So as long as your
controller has BIOS support you should be ok.
--
Brian Gerst
prev parent reply other threads:[~2005-05-24 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 13:56 Linux and Initrd used to access disk : how does it work ? Paul Rolland
2005-05-24 14:50 ` Richard B. Johnson
2005-05-24 15:19 ` Paul Rolland
2005-05-24 15:30 ` Richard B. Johnson
2005-05-24 19:30 ` Karl Essinger
2005-05-24 15:18 ` Brian Gerst [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=429345D5.7070406@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
--cc=rol@witbe.net \
/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