Alex Armstrong wrote:
Andreas Färber wrote:
Am 14.09.2014 um 02:27 schrieb Alex Armstrong:
Greetings,
I had a chance to test JeOS Factory Build 207.2 (13-Sep-14) on the Pi this weekend and found it didn't boot.
U-boot loads. It looks for /uEnv.txt, fails to find it. U-boot next looks for, and finds /boot.scr. It reads and executes the scrip.
Then this happens: ----- switch to partitions #0, OK mmc is current device ** File not found boot/linux.vmx ** SCRIPT FAILED: continuing... ** Bad Partition specification mmc 0:0:2 ** ** Bad Partition specification mmc 0:0:2 ** ** Bad Partition specification mmc 0:0:2 ** These should be 0:2, so maybe a variable mixup in the script?
Regards, Andreas
I haven't yet found what's causing this, but I'm a bit confused by something else too.
I think that the boot script is looking to boot 'boot/linux.vmx' with initrd 'boot/initrd.uboot' on the Second Partition (if I'm reading it right). But when I look at the directory structure I see this:
<First Partition> BOOT/boot/ - linux.vmx - initrd.uboot
<Second Partition> /boot/ - zImage -> zImage-3.11.4-3-raspberrypi - vmlinux-3.11.4-3-raspberrypi - initrd -> [broken link]
What am I missing?
-A Once at the u-boot prompt it's possible to load a kernel and initrd by hand with these commands:
<To load the kernel in the BOOT partition>
load mmc 0:1 ${kerneladdr} ${kernel}