Le 09/03/2016 22:41, Alexander Graf a écrit :
Le 09/03/2016 18:19, Alexander Graf a écrit :
Am 09.03.2016 um 18:02 schrieb Freek de Kruijf
: I need more guidance here. I assume printenv needs to given on the RPi2 system. How can I give that command on a system that does not boot. U-boot comes up, right? In U-boot, press space to get a command prompt. On that prompt, type "printenv" :) Alex, for RPi1, u-boot.bin differs between 1st boot and 2nd boot! Maybe it is the same here. How is it possible?
Replacing broken u-boot by working one fixed the boot for me. Can you dig out of rpm where the different versions come from? Maybe
On 09.03.16 22:38, Guillaume Gardet wrote: there's a typo in the efi enablement patches.
Well, in fact it was a 2016.03-rc2 (working) and a 2016.03-rc3 (broken). I think the problem is u-boot tries to boot EFI partition for Raspberry Pi. On 1st boot, 1st partition is hidden and after, 1st parition is labelled EFI. Upstream u-boot (latest GIT) is working, so I guess it is a problem with your EFI patches. ;) Could have a look, please? Guillaume
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org