Followup: I figured I'd try a sato build, since that's what the example on the BSP page uses. But core-image-sato-cedartrail-nopvr panics in the same way as core-image-base-cedartrail-nopvr. For sato, I surmised maybe 1GB wasn't enough, so I put in a second stick. This time, instead of spewing out a lot of kernel startup stuff ending in a panic, it gave me a SYSLINUX signon on the top of the screen, sat there for about 10 seconds, then rebooted into the BIOS, repeatedly. So I put back core-image-base-cedartrail-nopvr, and it also gave me the SYSLINUX signon, and rebooted after 10 seconds.
The fact that it behaves differently with 2GB suggests that maybe 1GB isn't enough, but that seems hard to imagine even for sato, let alone the base console version. I've run Ubuntu on these particular RAM modules, on a different motherboard, so I don't think I've got bad RAM. Any help figuring this out would be appreciated. For all my work, and apparently successful builds, I haven't managed to boot anything yet. -- Ciao, Paul D. DeRocco Paul mailto:pdero...@ix.netcom.com > From: Paul D. DeRocco > > I've successfully built core-image-base-cedartrail-nopvr, with NO > modifications, no meta-oe layer to pull in Samba, no attempt > to partition > the flash drive, just the .hddimg file dd'ed to /dev/sdb, to > see if I can > get something, anything to boot out of the box. > > I get a kernel panic when it tries to boot on my Intel > DN2800MT mobo, with > 1GB of RAM. The error messages, which appear on the attached > VGA monitor, > are: > > VFS: Cannot open root device "ram0" or unknown-block(0,0) > 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 > > Here is the syslinux.cfg file that is controlling the boot: > > # Automatically created by OE > serial 0 115200 > ALLOWOPTIONS 1 > DEFAULT boot > TIMEOUT 10 > PROMPT 1 > LABEL boot > KERNEL /vmlinuz > APPEND initrd=/initrd LABEL=boot root=/dev/ram0 > console=ttyS0,115200 > console=tty0 video=vesafb vga=0x318 > LABEL install > KERNEL /vmlinuz > APPEND initrd=/initrd LABEL=install root=/dev/ram0 > console=ttyS0,115200 > console=tty0 video=vesafb vga=0x318 > > This is a live-image boot, and the flash drive contains the usual five > files. As far as I can tell, a live-image boot is a two-stage > boot beginning > with a really stripped down vmlinuz and a small RAM-disk read > from initrd, > which then reads the big rootfs.img into another RAM-disk and > tries to boot > the real kernel from that. I don't know which kernel is > panicking, because > it all flies by so fast. > > Any ideas, or am I cursed? _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
