Hello:
I was getting the error: (RAMDISK: incomplete write (ramdisk too small?) (-28!= 32768) and then I discovered the my command line option ramdisk_size=8192 needs to be changed to ramdisk_size=16384.
Now I am past the ramdisk too small error, and I am getting the following error (see complete trace below):
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Tracer: Initialization complete RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 1473k freed Kernel panic: VFS: Unable to mount root fs on 01:00
In the below trace I see the two following lines: Loading RAMDisk Image at 00200000 ... Loading Ramdisk to 03e2d000, end 03f9d7e8 ... OK
The "error" above seems to suggest that the loader is looking for a ramdisk at 0 - however the two above lines (which appear to be conflicting) suggest that the image is at 0x200000 or 0x03e2d00.
Any suggestions?
Thanks
Jerry Walden
bootm 0x100000 0x200000 ## Booting image at 00100000 ... Image Name: Linux-2.4.18_mvl30-walnut Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 298672 Bytes = 291.7 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x03F9EBE8 => set upper limit to 0x00800000 ## cmdline at 0x007FFF00 ... 0x007FFF45 memstart = 0x00000000 memsize = 0x04000000 flashstart = 0xFFF80000 flashsize = 0x00080000 flashoffset = 0x00031000 sramstart = 0x00000000 sramsize = 0x00000000 bootflags = 0x001E8480 procfreq = 266.666 MHz b_busfreq = 133.333 MHz pci_busfreq = 33.333 MHz ethaddr = 00:00:00:00:00:00 IP addr = 0.0.0.0 baudrate = 9600 bps ## Loading RAMDisk Image at 00200000 ... Image Name: DA Ramdisk Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 1509352 Bytes = 1.4 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## initrd at 0x00200040 ... 0x00370827 (len=1509352=0x1707E8) Loading Ramdisk to 03e2d000, end 03f9d7e8 ... OK ## Transferring control to Linux (at address 00000000) ... Linux version 2.4.18_mvl30-walnut (root@hhl) (gcc version 3.2.1 20020930 (MontaVista)) #33 Tue Mar 25 15:30:00 <6>IBM Sycamore (IBM405GPr) Platform On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/ram rw ramdisk_size=16384 console=ttyS0,9600n8 console=tty0 Calibrating delay loop... 266.24 BogoMIPS[1;29r[29;1H Memory: 62268k available (512k kernel code, 212k data, 32k init, 0k
highmem)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) Mount-cache hash table entries: 1024 (order: 1, 8192 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 OCP uart ver 1.2 init complete Starting kswapd Disabling the Out Of Memory Killer Serial driver version 5.05c (2001-07-08) with no serial options enabled ttyS00 at 0x0000 (irq = 0) is a 16550A ttyS01 at 0x0000 (irq = 1) is a 16550A block: 128 slots per queue, batch=32 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Tracer: Initialization complete RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 1473k freed Kernel panic: VFS: Unable to mount root fs on 01:00
Jerry Walden
-----Original Message----- From: wd@denx.de [mailto:wd@denx.de] Sent: Tuesday, April 01, 2003 6:11 PM To: jwalden@digitalatlantic.com Cc: U-Boot-Users@Lists. Sourceforge. Net Subject: Re: [U-Boot-Users] RE: start / load addresses for initrd
In message EGEGIJHKDKJGAJMGIDPNGEFHCKAA.jwalden@digitalatlantic.com you wrote:
Where did you get this ramdisk image from?
I made the ramdisk image using the following procedure:
dd if=/dev/zero of=ramdisk bs=1k count=16384 /sbin/mke2fs -q -F -m0 ramdisk mount -o loop ramdisk mountpoint cd mountpoint tar xf ../fsimage.tar
Where did you get "fsimage.tar" from? What does it contain.
What makes you think it is working at all?
I performed the following procedure to verify it.
[root@hhl initrd]# dd if=initrd of=ramdisk.gz bs=64 skip=1 23583+1 records in 23583+1 records out [root@hhl initrd]# gzip -d ramdisk.gz [root@hhl initrd]# mount -o loop ramdisk mountpoint [root@hhl initrd]# ls -al mountpoint total 26 drwxr-xr-x 10 root root 1024 Mar 20 15:34 drwxr-xr-x 3 root root 4096 Apr 1 16:31 drwxr-xr-x 2 root root 1024 Mar 20 15:34 drwxr-xr-x 2 root root 2048 Mar 20 15:34 drwxr-xr-x 6 root root 1024 Mar 20 15:34 drwxr-xr-x 2 root root 2048 Mar 20 15:34 drwxr-xr-x 2 root root 12288 Mar 20 15:34 drwxr-xr-x 2 root root 1024 Mar 20 15:34 drwxr-xr-x 5 root root 1024 Mar 20 15:34 drwxr-xr-x 4 root root 1024 Mar 20 15:34
Ummm... I don't even see a filename here. I don;t see if there is an "init" binary or a shell or any library or any device.
Which sort of output do you expect when providing such input? GIGO...
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de This is an unauthorized cybernetic announcement.