linux-kernel - Re: Initial ramdisk support does not work (for me) on 2.6.17.13

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 16 Nov 2006 13:00:06 +0000
From:	Oleg Verych <olecom@...wer.upol.cz>
To:	Heiko Gerstung <heiko.gerstung@...nberg.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Oleg Verych <olecom@...wer.upol.cz>
Subject: Re: Initial ramdisk support does not work (for me) on 2.6.17.13

In gmane.linux.kernel, you wrote:
> Hi!

Hallo.

> We are building embedded devices based on Linux and we use a ramdisk as
> our root device in order to avoid problems with people switching off the
> unit without a proper shutdown and to save write-cycles on our flash disc.
>
> Using a 2.6.12 kernel it was no problem to boot the system by using this
> kernel parameters:
> load_ramdisk=1 console=tty0 initrd=initrd.gz rw  vga=769
> ramdisk_size=32768 root=/dev/ram0
>
> Today I tried to test run a 2.6.17.12 kernel using the same parameters
> but I get this error message:
> VFS: Cannot open root device "ram0" or unknown-block(1,0)
> Please append a correct "root=" boot option

In subject you've wrote "2.6.17.13", but anyway in such cases one must
include full dmesg (boot output) and (sometimes) ".config".

Also, if you are using some kind of embedded hardware, f.e. ARM,
please, use arm-user mailing list for such questions.
____
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/