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.
What makes you think so? I think you are wrong.
Yes - I was wrong - I misinterpreted the definition of the command line option
## 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
Given a compressed size of 1.4 MB, the contents of the ramdisk will be probably in the range of 3...4 MB. Did you really create a ramdisk 16 MB big?
Yes - stupid mistake
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
Again, I see no indication that you really have a good, working ramdisk image. I think you should ask MV support for help.
Alternmatively, you could try using a known-to-work ramdisk image for a start, for example one from here: ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/
Okay - I downloaded pRamdisk and I now have the following error:
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Tracer: Initialization complete RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (ramdisk too small?) (-28 != 32768)
So now it has found a valid ramdisk image - and it was not before, however I still get the other error.
Kindest Regards,
Jerry Walden
Entire Boot Log is Below:
U-Boot 0.2.0 (Apr 2 2003 - 11:42:33)
CPU: IBM PowerPC 405GPr Rev. A at 266.666 MHz (PLB=133, OPB=66, EBC=26 MHz) PCI async ext clock used, internal PCI arbiter enabled 16 kB I-Cache 16 kB D-Cache
Board: ### No HW ID - assuming WALNUT405 I2C: ready DRAM: 64 MB Now running in RAM - U-Boot at: 03fcf000 FLASH: 512 kB *** Warning - bad CRC, using default environment
PCI: Bus Dev VenId DevId Class In PCI Autoconfig: Memory region: [20000000-27ffffff] PCI Autoconfig: I/O region: [800000-3ffffff] PCI Scan: Found Bus 0, Device 0, Function 0 PCI Scan: Found Bus 0, Device 7, Function 0 PCI Autoconfig: BAR 0, Mem, size=0x1000000, address=0x20000000 PCI Autoconfig: BAR 1, I/O, size=0xffffff04, No room in resource PCI Autoconfig: BAR 2, I/O, size=0x1000000, address=0x1000000 00 07 1394 0978 0200 1c
In: serial Out: serial Err: serial
U-Boot relocated to 03fcf000 Bus 0: port = c OK Device 0: Model: SanDisk SDCFB-32 Firm: Vdg 1.23. Ser#: 003917A2203F2620 Type: Removable Hard Disk Capacity: 30.6 MB = 0.0 GB (62720 x 512) => => imi 0x100000
## Checking Image at 00100000 ... Image Name: Linux-2.4.18_mvl30-walnut Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 300107 Bytes = 293.1 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK
=> imi 0x200000
## Checking Image at 00200000 ... Image Name: Simple Embedded Linux Framework Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 1476478 Bytes = 1.4 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK => 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: 300107 Bytes = 293.1 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 = 0x0003100 ramstart = 0x00000000 ramsize = 0x00000000 bootflags = 0x001E8480 procfreq = 266.666 MHz lb_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: Simple Embedded Linux Framework Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 1476478 Bytes = 1.4 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK
## initrd at 0x00200040 ... 0x003687BD (len=1476478=0x16877E)
Loading Ramdisk to 03e35000, end 03f9d77e ... OK
## Transferring control to Linux (at address 00000000) ... Linux version 2.4.18_mvl30-walnut (root@hhl) (gcc version 3.2.1 20020930 (MontaVista)) #34 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 serial_out UART_LCR 176 Calibrating delay loop... 266.24 BogoMIPS Memory: 62296k available (516k 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: Compressed image found at block 0 RAMDISK: incomplete write (ramdisk too small?) (-28 != 32768)
Jerry Walden Program Manager Digital Atlantic Inc http://www.digitalatlantic.com jwalden@digitalatlantic.com 1-877-494-6073 x407 cell - 703-431-2413
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of Wolfgang Denk Sent: Wednesday, April 02, 2003 3:13 PM To: jwalden@digitalatlantic.com Cc: U-Boot-Users@Lists. Sourceforge. Net Subject: Re: [U-Boot-Users] RE: start / load addresses for initrd
Jerry,
in message EGEGIJHKDKJGAJMGIDPNEEGNCKAA.jwalden@digitalatlantic.com you wrote:
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.
What makes you think so? I think you are wrong.
## 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
Given a compressed size of 1.4 MB, the contents of the ramdisk will be probably in the range of 3...4 MB. Did you really create a ramdisk 16 MB big?
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
Again, I see no indication that you really have a good, working ramdisk image. I think you should ask MV support for help.
Alternmatively, you could try using a known-to-work ramdisk image for a start, for example one from here: ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de I don't know if it's what you want, but it's what you get. :-) - Larry Wall in 10502@jpl-devvax.JPL.NASA.GOV
------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users