Cheers!
Everythings up and running now. It had nothing to do with the kernel and
all to do with a wrong word in syslinux.cfg.
I had the wrong default set so it defaulted to running the kernel
without options. Which is no good idea when booting an initrd =)
Thanks for the help anyhow.
-
To unsubsc
On Sat, 2005-04-16 at 22:15 +0200, gabriel wrote:
> Yeah.. but it shouldn't matter much since I've not been able to load the
> initrd
> yet?
>
I had just a look at all those things... It simply was a question coming
into my mind...
> My kernel never complains about root= bla it only says unabl
>Have you edit the build-initrd.sh script to fit your needs?
Yeah.. but it shouldn't matter much since I've not been able to load the initrd
yet?
>Does
> http://featherlinux.berlios.de/usb-instructions.htm or
> http://www.ussg.iu.edu/hypermail/linux/kernel/0211.1/0551.html help?)
I thought
>I don't think syslinux digs the "/" in the initrd filename. Did you try
>it with initrd=initrd.gz?
Yep no difference.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majord
gabriel wrote:
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
append initrd=/initrd.gz root=/dev/ram0 rootfstype=minix init=/linuxrc
I don't think syslinux di
Have you edit the build-initrd.sh script to fit your needs?
Does
http://featherlinux.berlios.de/usb-instructions.htm or
http://www.ussg.iu.edu/hypermail/linux/kernel/0211.1/0551.html help?)
Totally different Q's:
Have you called syslinux with the correct parameter to find your
initrd.gz?
On Fri, 2005-04-15 at 09:27 +0200, gabriel wrote:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
(1,0)
>Hi Gabriel!
Hi!
>It looks like initrd.gz could not be mounted. The unknown-block(1,0)
>is /dev/ram0 (and has normally initrd attached to it) as specified on
>kerne
On Fri, 2005-04-15 at 09:27 +0200, gabriel wrote:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Hi Gabriel!
It looks like initrd.gz could not be mounted. The unknown-block(1,0)
is /dev/ram0 (and has normally initrd attached to it) as specified on
kernel command
> 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 Protec
> gabriel <[EMAIL PROTECTED]> writes:
> 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
> ...
> ...
> ...
> Kernel panic - not syncing: VFS: Unable t
.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
ker
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 ro
12 matches
Mail list logo
