From: gabriel <gabriel.j@telia.com>
To: linux-kernel@vger.kernel.org
Subject: Sv: RE: Booting from USB with initrd
Date: Fri, 15 Apr 2005 09:34:49 +0200 (MEST) [thread overview]
Message-ID: <33007639.1113550489129.JavaMail.tomcat@pne-ps4-sn1> (raw)
Um yes it is.
How could I otherwise have booted far enough to get the panic?
My boot partition is on the usb I cant boot from hard drive.
----Ursprungligt meddelande----
Från: Jason.Jones@monteith2.areur.army.mil
Datum: Apr 15, 2005 9:29:06 AM
Till: gabriel <gabriel.j@telia.com>
Ärende: RE: Booting from USB with initrd
Is USB even an option to boot off of in the BIOS? How could the OS boot to
something that isn't detected in the bios? IMHO.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of gabriel
Sent: Friday, April 15, 2005 9:28 AM
To: linux-kernel@vger.kernel.org
Subject: Booting from USB with initrd
Hi Im trying to boot an encrypted file system using an initrd on a USB.
I use syslinux for the actual boot process as I couldnt get Grub to boot
of it for some reason. This is the .cfg
default vmlinuz
timeout 100
prompt 1
label linux
kernel vmlinuz
append initrd=/initrd.gz root=/dev/ram0 rootfstype=minix init=/linuxrc
As far as I can tell this should load the initrd but that never happens.
Everything seems to boot fine. Syslinux loads the kernel and I get to
the point where initrd should be mounted only to get this error.
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(1,0)
followed by the USB information and stop.
<5> Vendor SWISSBIT Mode: Victorinox 2.0 Rev 2.00
Type Direct-Access ANSI SCSI Revision: 02
SCSI device sdb: 1022720 512 byte hdwr sectors (524mb)
sdb: Write Protect is off
sdb: asuming driver cache: write-through
I have support for minix, vfat, ext2 and ext3 in the kernel. I have
recompiled the
kernel
like 20 times to test different things. So what Im thinking is that the
USB device doesn't
get realized before syslinux tries to load it?
Oh I do have the ramdisk in the kernel and everything.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2005-04-15 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 7:34 gabriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 9:25 Sv: Re: Booting from USB with initrd gabriel
2005-04-15 12:54 ` Bernhard Schauer
2005-04-16 19:45 gabriel
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=33007639.1113550489129.JavaMail.tomcat@pne-ps4-sn1 \
--to=gabriel.j@telia.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.