From: Paulo Marques <pmarques@grupopie.com>
To: William Park <opengeometry@yahoo.ca>
Cc: Jesper Juhl <juhl-lkml@dif.dk>,
linux-kernel@vger.kernel.org,
Andreas Unterkircher <unki@netshadow.at>
Subject: Re: waiting 10s before mounting root filesystem?
Date: Wed, 29 Dec 2004 12:49:02 +0000 [thread overview]
Message-ID: <41D2A7BE.2030806@grupopie.com> (raw)
In-Reply-To: <20041229015622.GA2817@node1.opengeometry.net>
William Park wrote:
>[...]
>
> Ideally, motherboard should support booting from USB key drive directly.
> I'm told that most modern motherboards do support usbboot, but my
> machine doesn't. So, I trying to load the kernel from floppy (harddisk
> for testing purpose). This is part of my attempt to build Linux
> thin-client out of mini-ITX type of computer (Via CLE266 chipset, Via C3
> cpu).
>
> Now, I need to find a machine that actually can do usbboot...
You will have the same problem even if the BIOS supports booting from
USB. The BIOS will load the bootloader and map the USB drive as if it
were a regular disk, so that the INTxx calls (can't say the number from
memory) that LILO (or another bootloader) uses to load the kernel and
initrd into memory will work.
After that, the kernel boots the same way as if it were loaded from a
floppy. It still needs to discover the USB drive to mount the root
filesystem, and that will still take the 5 seconds you were complaining
about.
As Trent Lloyd already mentioned, you could solve this using a small
initrd and a "nash" script, instead of patching the kernel, although I'm
in favor of a patch of this sort getting into mainline.
After all, what is the use of kernel saying "Panic, can not mount the
root filesystem" instead of saying "humm... no root file system there.
Let me try again in a second or so and see if anything as come up..."?
--
Paulo Marques - www.grupopie.com
"A journey of a thousand miles begins with a single step."
Lao-tzu, The Way of Lao-tzu
next prev parent reply other threads:[~2004-12-29 12:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 19:56 waiting 10s before mounting root filesystem? William Park
2004-12-27 20:10 ` Trent Lloyd
2004-12-27 21:23 ` Andreas Unterkircher
2004-12-28 1:54 ` Eric Lammerts
2004-12-29 0:59 ` William Park
2004-12-29 1:38 ` Jesper Juhl
2004-12-29 1:56 ` William Park
2004-12-29 12:49 ` Paulo Marques [this message]
2004-12-29 19:15 ` William Park
2004-12-29 19:34 ` Paulo Marques
2004-12-29 20:59 ` William Park
2004-12-29 21:26 ` Andreas Steinmetz
2004-12-31 19:32 ` Willy Tarreau
2004-12-29 21:53 ` Bernd Eckenfels
2004-12-29 22:56 ` Jesper Juhl
2004-12-30 15:25 ` Marcelo Tosatti
2004-12-30 23:45 ` Jesper Juhl
2004-12-31 1:45 ` Jesper Juhl
2004-12-31 3:58 ` William Park
2004-12-31 4:41 ` Jesper Juhl
2004-12-31 11:31 ` Paulo Marques
2004-12-31 9:49 ` Andrew Morton
2004-12-31 8:28 ` Marcelo Tosatti
2004-12-31 11:40 ` Andrew Morton
2004-12-31 11:26 ` Paulo Marques
2004-12-31 8:58 ` Marcelo Tosatti
2004-12-31 11:42 ` Andrew Morton
2004-12-31 12:04 ` Paulo Marques
2004-12-31 17:36 ` William Park
2004-12-31 17:48 ` Tomasz Torcz
2004-12-31 18:18 ` William Park
2004-12-31 0:22 ` William Park
[not found] <fa.nc4oh06.1j1872e@ifi.uio.no>
[not found] ` <fa.nalafoa.1ih25aa@ifi.uio.no>
2004-12-31 12:33 ` Bodo Eggert
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=41D2A7BE.2030806@grupopie.com \
--to=pmarques@grupopie.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=opengeometry@yahoo.ca \
--cc=unki@netshadow.at \
/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