Luckily I broke the boot sequence for opensuse

[johndough]

Hi all

Well hour after hour of fruitless pi-ing.

Tried several versions and all give the following error on reboot

Net: Net Initialization Skipped
No ethernet found

Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device

Scanning mmc 0:1...
Found U-boot script /boot.scr
113 bytes read in 15ms (6.8 kb/s)

##Executing script at 00000000
2718 bytes read in 45ms (58.6kb/s)

##Executing script at 00000200
Switch to partitions #0, OK
mmc0 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##

##Error “bootcmd_firstboot” not defined##
##Error “bootcmd_firstboot” not defined##
##Error “bootcmd_firstboot” not defined##

U-Boot>

as I mentioned earlier.

However by tampering with the UEFI partition u-boot.bin I then get a different result...

A Rainbow rectangle, and onboard the RED LED shows and the GREEN LED flashes 7 times, then repeats. Which is a step in some direction, it might even be backwards.

So I assume that the Boot part with .elf files etc is either redundant or is bypassed.

Any theories anyone on the sequence or what I can try next.

Just to confirm that initial use gives a login and I can zypper in all sorts of stuff and on reboot FAILS each and time I re-image the card.

[Joe Schmoe]

Does the Pi have UEFI?

[johndough]

Does the Pi have UEFI?

Hi

Probably not, but it doesn't have vmx either, which is a virtual machine file.

So for now I have to go with what is bundled in the .raw.xz file that i expand onto the SD card.

[Burngate]

A Rainbow rectangle, and onboard the RED LED shows and the GREEN LED flashes 7 times, then repeats. Which is a step in some direction, it might even be backwards..

http://elinux.org/R-Pi_Troubleshooting# ... ic_pattern says

7 flashes: kernel.img not found

and

With current firmware, a coloured splash screen (actually its just four pixels "blown up" by the GPU to full screen) is displayed after GPU firmware (start.elf) is loaded. This should be replaced by linux console a second later. However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

[johndough]

Thanks.