Andrea Archangeli posted a temp fix here about a week ago.
Regards,
Brad
----- Original Message -----
From: Richard B. Johnson <root@chaos.analogic.com>
To: Linux kernel <linux-kernel@vger.rutgers.edu>
Sent: Thursday, August 26, 1999 1:44 PM
Subject: RAMDISK (initrd) booting in 2.3.13
>
> Hello,
>
> I am making an embedded kernel, booted from NVRAM. Initial tests fail
> so I am emulating it with a floppy. In the emulation, I simply boot using
> initrd using a compressed root image located on the floppy. This works
> fine and executes /linuxrc okay.
>
> According to the documentation in ../linux/Documentation/initrd.txt,
> line 206, in order to stay on the ramdisk mounted root file-system, I
> should specify the new root to be the RAM disk.
>
> This doesn't work. /dev/ram (on the boot image ramdisk) is a symlink to
> /dev/ram1, a block-special device, major 1, minor 1.
> When the machine boots, the resulting panic is:
>
> Unable to mount root fs on 01:01.
>
> This shows that lilo has properly interpreted what I told it, but that
> /dev/ram1 isn't what is currently mounted as the initial RAM disk.
> /dev/ram1 probably contains the compressed ramdisk image, not the
> uncompressed file-system.
>
> The question is; What is the name of the current root file-system when
> a ramdisk is mounted? The documentation is probably not too up to date.
> I guessed that it was /initrd, but that didn't work either.
>
> Cheers,
> Dick Johnson
> **** FILE SYSTEM WAS MODIFIED ****
> Penguin : Linux version 2.3.13 on an i686 machine (400.59 BogoMips).
> Warning : It's hard to remain at the trailing edge of technology.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/