Problems loading ramdisk
Hi,
I have a very simple and somewhat embarassing question regarding u-boot and loading a ramdisk. I am trying to boot my IXP425 board using a kernel and ramdisk that has been flashed on the board. I have tried following the many suggestions that I have found both on the web, and inside the documentation but still have not had any success. I know the kernel and ramdisk image are good, since I used the same images for booting from Redboot. Below is a snippet of my boot sequence, including the error when trying to mount the ramdisk(initrd)
Thanks,
Mike
******************************************************
bootm 50040000 50180000
## Booting image at 50040000 ...
Image Name: Snapgear Kernel Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1295376 Bytes = 1.2 MB
Load Address: 01600000
Entry Point: 01600000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 50180000 ...
Image Name: Snapgear Ramdisk
Image Type: ARM Linux RAMDisk Image (gzip
compressed)
Data Size: 2264374 Bytes = 2.2 MB
Load Address: 00800000
Entry Point: 00800000
Verifying Checksum ... OK
Starting kernel ...
Uncompressing Linux............................................................. ................................. done, booting the kernel.
Linux version 2.6.13.5 (msprauve at Sebring) (gcc version 3.3.2) #34 Tue Jun 6 14:0
3:35 PDT 2006
CPU: XScale-IXP42x Family [690541f1] revision 1 (ARMv5TE)
Machine: Intel IXDP425 Development Platform
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT undefined 5 cache
CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
Built 1 zonelists
Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x00800000,8M me
m=64M at 0x00000000 hdc=noprobe hdd=noprobe
.
.
.
RAMDISK: Couldn't find valid RAM disk image starting
at 0.
Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(1,0)
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Quoted 3 lines · In message <[email protected]> you wrote:
I have a very simple and somewhat embarassing question regarding u-boot and loading a ramdisk. I am trying to
...
Quoted 1 line
bootm 50040000 50180000
...
## Loading Ramdisk Image at 50180000 ...
^^^^^^^^
The bootm command will pass the address of the ramdisk to the Linux kernel using the appropriate ATAGS for this. It also passes the correct memory size to use.
Quoted 2 lines
Kernel command line: console=ttyS0,115200
root=/dev/ram0 initrd=0x00800000,8M me
^^^^^^^^
Quoted 1 line
m=64M at
0x00000000hdc=noprobe hdd=noprobe
...thus you should not pass any initrd= and mem= options on the commandline unless you know *exactly* what you are doing.
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de No problem is insoluble. -- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4
Hi,
So just make sure I understand your response 1)The 50180000 address that I pass to the bootloader is the location of where I stored my ramdisk image in flash
2)When I create the ramdisk.bin using mkimage, the load address I used (using the -a option) is pass to the kernel using the ATAG method along the size of the ramdisk
3)Because of that, I won't need to use the "initrd" parameter in my bootargs
If I understand all of that is correct, then I must be missing something else, since after setting my bootargs to "console=ttyS0,115200 root=/dev/ram0 mem=16M" I still the same error, where it seems the kernel can't find the ramdisk location
"Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"
Quoted 2 lines · --- Wolfgang Denk
In message
Quoted 23 lines
Quoted 2 lines · you
I have a very simple and somewhat embarassing
question
Quoted 1 line
regarding u-boot and loading a ramdisk. I am
trying to
...Quoted 1 line
bootm 50040000 50180000
...
## Loading Ramdisk Image at 50180000 ...^^^^^^^^The bootm command will pass the address of the ramdisk to the Linux
kernel using the appropriate ATAGS for this. It also passes the
correct memory size to use.Quoted 2 lines
Kernel command line: console=ttyS0,115200
root=/dev/ram0 initrd=0x00800000,8M me^^^^^^^^Quoted 1 line
m=64M at
0x00000000hdc=noprobe hdd=noprobe
Quoted 18 lines
...thus you should not pass any initrd= and mem= options on the
commandline unless you know *exactly* what you are doing.Best regards,
Wolfgang Denk
Signature · 7 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de No problem is insoluble. -- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Hello Michael,
See my comments below...
Quoted 6 lines · Michael Sprauve
Hi,
So just make sure I understand your response 1)The 50180000 address that I pass to the bootloader is the location of where I stored my ramdisk image in flash
Correct.
Quoted 5 lines
2)When I create the ramdisk.bin using mkimage, the load address I used (using the -a option) is pass to the kernel using the ATAG method along the size of the ramdisk
I'm not familiar with the load address option since I've never had to use it. Perhaps Wolfgang or others will elaborate.
Quoted 3 lines
3)Because of that, I won't need to use the "initrd" parameter in my bootargs
Correct. Though not so sure about the reasoning behind the conclusion...see below.
Quoted 6 lines
If I understand all of that is correct, then I must be missing something else, since after setting my bootargs to "console=ttyS0,115200 root=/dev/ram0 mem=16M" I still the same error, where it seems the kernel can't find the ramdisk location
Try using just "console=ttyS0, 115200" without the root= stuff. It is my understanding that when you use bootm addr1 addr2, that u-boot will pass whatever information the kernel needs to find its root device automatically (ATAGS?).
-Randy Smith
Software Engineer,
ImageMap, Inc.