Op maandag 4 september 2017 14:28:24 CEST schreef u:
> On 04.09.17 11:49, Freek de Kruijf wrote:
> > I used the latest JeOS image 2017.05.23-Build1.1 for the RPi1 (armv6l) on
> > a SD card and booted the system, which went OK.
> >
> > After that I did a "zypper dup --no-recommends" on that system
On 04.09.17 11:49, Freek de Kruijf wrote:
I used the latest JeOS image 2017.05.23-Build1.1 for the RPi1 (armv6l) on a SD
card and booted the system, which went OK.
After that I did a "zypper dup --no-recommends" on that system which, at the
end, shows the following message:
Output of grub2-arm
After some time, the ethernet leds begin to blink, but no requests to
dhcp. something is alive inside still...
2017-09-04 11:17 GMT+03:00 Matwey V. Kornilov :
> Hm, console=ttyS2,150 supposed to work, but it doesnt...
>
> 2017-09-04 11:00 GMT+03:00 Matwey V. Kornilov :
>> Booti
I used the latest JeOS image 2017.05.23-Build1.1 for the RPi1 (armv6l) on a SD
card and booted the system, which went OK.
After that I did a "zypper dup --no-recommends" on that system which, at the
end, shows the following message:
Output of grub2-arm-uboot-2.02-6.1.armv6hl.rpm %posttrans scrip
Hi,
kernel 4.12 does not include the rpi3 DTB update. It is in 4.13 only.
See:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts?h=v4.13&id=738f859f520862e51a5662b03fb162524e09307b
If all the other pieces are in 4.12, maybe
Hm, console=ttyS2,150 supposed to work, but it doesnt...
2017-09-04 11:00 GMT+03:00 Matwey V. Kornilov :
> Booting a command list
>
> Loading linux.vmx...
> Loading initrd.vmx...
> EFI stub: Booting Linux Kernel...
> EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplie
Booting a command list
Loading linux.vmx...
Loading initrd.vmx...
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: ERROR: Could not determine UEFI Secure Boot status.
EFI stub: Using DTB from configuration table
EFI stub: Ex
