[U-Boot-Users] Problems loading ramdisk
mike_sprauve at yahoo.com
Sun Jun 11 06:36:43 CEST 2006
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
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
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)"
--- Wolfgang Denk <wd at denx.de> wrote:
> In message
<20060609221556.35601.qmail at web37110.mail.mud.yahoo.com>
> you wrote:
> > I have a very simple and somewhat embarassing
> > regarding u-boot and loading a ramdisk. I am
> trying to
> > 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.
> > Kernel command line: console=ttyS0,115200
> > root=/dev/ram0 initrd=0x00800000,8M me
> > m=64M at 0x00000000 hdc=noprobe hdd=noprobe
> ...thus you should not pass any initrd= and mem=
> options on the
> commandline unless you know *exactly* what you are
> Best regards,
> Wolfgang Denk
> 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
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
More information about the U-Boot