Hello, My 2nd partition on the mmc is linux ext3. This is what I have been using to transfer the rootfs to my mmc tar jxvf beagleboard/core-image-minimal-beagleboard-20131024171447.rootfs.tar.bz2
Did something change since the 21 st of last month. Testing dora which was not part of dylan? No matter what I do when i the kernel to start it is always is looking for UBIFS my mmcrootfstype=ext3 rootwait and mmcroot/dev/mmcblk0p2 rw bootcmd="mmc rescan 0 ; fatload mmc 0:1 0x80008000 zImage; bootz 0x80008000" when I execute manually it does seem to like mmc rescan 0 sometimes mmc rescan 0 mmc - MMC sub system Usage: mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc rescan works okay. ThumbEE CPU extension supported. VDVI: incomplete constraints, leaving on VDAC: incomplete constraints, leaving on UBI error: ubi_init: UBI error: cannot initialize UBI, error -19 console [netcon0] enabled netconsole: network logging started twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) ALSA device list: #0: omap3beagle VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error -19 Please append a correct "root=" boot option; here are the available partitions: VFS: Unable to mount root fs on unknown-block(0,0) User configuration error - no valid root filesystem found Kernel panic - not syncing: Invalid configuration from end user prevents continu ing Thanks On Wed, Oct 23, 2013 at 10:09 AM, Rudolf Streif <rstr...@linuxfoundation.org > wrote: > Hi Edward, > > > This is what I have in the uEnv.txt file >> >> >> bootcmd="" >> bootfile="zImage" >> ethact="" >> loadaddr="" >> nandboot="" >> nandroot="" >> nandrootfstype="" >> nandargs="" >> loaduimage="" >> loaduimagefat="" >> nandboot="" >> mpurate="auto" >> bootcmd="mmc rescan ; fatload mmc 0:1 0x80300000 zImage; bootz 0x80300000" >> >> Why are you setting all the variables to "". You really only have to > overwrite the ones you need to change. > > > >> dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M" >> optargs="consoleblank=0" >> console="ttyO2 console=tty0,115200n8" >> vram=16M >> saveenv >> printenv >> >> It appears that some of variable get written with other data ie vram I am >> setting to 16M but sometimes I see it set to 12M see at the end >> I have tried setting the variables manually and executing saveenv >> All the ones I don't want set setenv name and then saveenv >> still see the same values >> when I was using uImage and no >> this is what I used for my uEnv.txt >> >> mpurate=auto >> >> Are you still trying to solve the problem with the rootfs or is that > another problem? > > > >> mmcroot=/dev/mmcblk0p2 rw >> mmcrootfstype=ext3 rootwait >> > > According to these settings your kernel is passed information to look for > an ext3 root file system on the second partition of the an SD card on > /dev/mmcblk0. Are you booting from an SD card? However, in your first boot > it seems to look for an ubifs. > > I am not sure what you are looking for. Maybe you can attach an new boot > log. > > :rjs >
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto