Messages in this thread | | | Date | Tue, 15 Jan 2002 11:47:34 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | initrd FAILURE on linux-2.4.17 |
| |
Hello, As previously reported, Linux-2.4.17 fails to mount a ram-disk upon boot so it is impossible to use a kernel that does not have the root file-system drivers built-in.
The attached file contains the previously-used script that has made successful RAM-Disks since version 2.0.n and/or even before. Within that directory is a new/modified script 'try', that attempts to follow the changed documentation in linux-2.4.17/Documentation/initrd.txt This attached file also contains the kernel configuration.
No matter what I do, the RAM disk is "found", but it is never mounted so /linuxrc never is executed:
Hand copied:
Based upon Swansea Computer Society NET3.039 Initializing RT netlink socket Starting kswapd VFS: Diskquotas version dquot_6.4.0 initialized Detected PS/2 Mouse Port pty: 256 Unix/98 ptys configured block: 128 slots per queue, batch=32 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 loop: loaded (max 8 devices) Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximumm main memory to use for agp memory: 262M agpgart: Detected Intel 440BX chipset agpgart: AGP aperture is 64M @ 0xe4000000 NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 32767 bind 32768) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0 RAMDISK: Compressed image found at block 0 Freeing initrd memory: 581k freed kernel panic: VFS: Unable to mount root fs on 01:00
Following advice, I also re-compiled the kernel non-SMP. This did not help.
Cheers, Dick Johnson
Penguin : Linux version 2.2.4 on an i686 machine (400.59 BogoMips).
I was going to compile a list of innovations that could be attributed to Microsoft. Once I realized that Ctrl-Alt-Del was handled in the BIOS, I found that there aren't any.
[unhandled content-type:application/octet-stream] | |