Using initrd and ramdisks, when the kernel (2.4.0-pre7-test2) was configured,
mounting root=/dev/RAM0 no longer works.
Only change was a kernel change from 2.2.14
And have checked the .config file 3 times for support is correct.
What is (is there?) the/a new identifiers for ram0?
In the Documentation/ramdisk.txt (Dated?) there is no mention to it but I
guess it could be a change to the /dev/ram0 system that I haven't heard
about?? Old mentions in the list around 2.3.34 about something but ntohing
lately.
Someone steer me in the right direction here to search why it isn't working
now.
Looking at ./linux/fs/super.c I see somthing that looks strange?
The only reference to CONFIG_BLK_DEV_RAM
seems to be in super.c (and arch/<arch>/kernel/setup.c) which is immediately
followed by a floppy_eject (That would be BAD if I read it right? It is
almost as if it expects to use a root/boot disk method, so you can see I am
having trouble following what is happeing now with initrd and ram devices)
Getting a VFS: Cannot open root device "ram0" or 01:00 after booting with new
kernel (vs prev 2.2.14 kernel)
Problem when selecting PTY's to 24 instead of 256
CONFIG_UNIX98_PTY_COUNT=24
Still creates 256 PTY's
-- -------------------------------------------------------- Michael Peddemors - Senior Consultant Unix Administration - WebSite Hosting Network Services - Programming Wizard Internet Services http://www.wizard.ca Linux Support Specialist - http://www.linuxmagic.com -------------------------------------------------------- (604) 589-0037 Beautiful British Columbia, Canada --------------------------------------------------------- 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/
This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:28 EST