Op dinsdag 12 september 2017 11:32:13 CEST schreef Freek de Kruijf:
Op maandag 11 september 2017 23:16:23 CEST schreef Freek de Kruijf:
Op maandag 11 september 2017 18:26:28 CEST schreef Freek de Kruijf:
All seems well. Will try to update all software.
The resulting system fails to boot after the upgrade. Will investigate further. At least /boot/grub2/grub.cfg did change quite a lot.
It looks like u-boot starts, I get about 15 lines on the screen, but after that the system starts again, showing very fast these lines again.
I am lost here.
Not completely lost. I moved the whole content of the FAT32 partition aside and copied the original content from a freshly copied image to that partition. In /boot , where the updated kernel resides with symbolic links initrd and zImage, which are pointing to the updated (latest kernel, 4.12), I made symbolic links initrd.vmx and linux.vmx to these symbolic links. After booting with this SD card, I now got back the Grub boot screen showing the name of the newest kernel. After that Tux appears on the screen, but shortly after that the screen becomes black and the network is not activated. Inspecting the SD card afterwards I don't see any log entry when I use journalctl -D pointing to /var/log/journal on the SD card after the time I updated the system with zypper dup the previous day. So the system does not start properly. I will connect my USB serial cable to the proper pins of the RPi-card to see if any message appears on the console. -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org