The debian people use not only a kernel to boot, but also an initrd image. I can't remember if also fedora uses it. As the kernel, you have to load that image into memory, and then pass that address as a second parameter to bootm. The first parameter is the memory address of the kernel. If the fedora people provide also an initrd, pass its memory address as the second parameter to bootm. Btw, why you have an apostrophe between "bootm" and the memory address 0x6400000 ? Regards, Lluís. 2009/8/25 Steve Grubb <sgrubb@xxxxxxxxxx>: > On Tuesday 25 August 2009 11:12:47 am Lluís Batlle wrote: >> Create a linux fs in the usb disk as a new partition, and untar in it >> the f11 root contents you can download from the web. > > Tried that. > >> Then set up uboot to load the kernel from the usb device partition, >> setting the root= kernel parameter pointing to the proper scsi device >> (as usb disks are seen as scsi devices). I haven't tried, but this >> should be enough. > > I found this page: > > http://www.cyrius.com/debian/kirkwood/sheevaplug/unpack.html > > And made some changes. Let's just assume /dev/sda1 for the usb. > > setenv bootargs_root 'root=/dev/sda1 rootdelay=10' > setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x0800000 /boot/uInitrd; ext2load usb 0:1 0x6400000 /boot/uImage-2.6.30-sheevaplug' > setenv bootcmd 'setenv bootargs $(console) $(bootargs_root); run bootcmd_usb; bootm ' 0x6400000 > > When I boot, I get Bad Magic. I also noticed that the instructions > use something called uInitrd. I have no idea where that came from. > Wonder if that is the missing piece? > > -Steve > > _______________________________________________ > fedora-arm mailing list > fedora-arm@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-arm > _______________________________________________ fedora-arm mailing list fedora-arm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-arm
