Just an FYI for those doing the Raspberry Pi aarch64 distribution maintenance and those contemplating a similar update: I just did a “zypper dup” to update Tumbleweed 4.16.? to 4.17.1 on a Raspberry Pi-3B, and after downloading and installing 2200+ packages, with no error messages, the system won’t reboot.
This is not a request for help, just an FYI. I’ve been burned like this by enough TW updates to decide to abandon using it and stick with Leap (now Leap15). While I really liked TW aarch64 on my Pi-3’s and enjoyed exploring its new features, the ongoing investment in debugging complete failures in major system upgrades, in which I might well lose my accumulated work, just isn’t justified any more.
Just an FYI for those doing the Raspberry Pi aarch64 distribution
maintenance and those contemplating a similar update: I just did a
“zypper dup” to update Tumbleweed 4.16.? to 4.17.1 on a Raspberry Pi-3B,
and after downloading and installing 2200+ packages, with no error
messages, the system won’t reboot.
This is not a request for help, just an FYI. I’ve been burned like this
by enough TW updates to decide to abandon using it and stick with Leap
(now Leap15). While I really liked TW aarch64 on my Pi-3’s and enjoyed
exploring its new features, the ongoing investment in debugging complete
failures in major system upgrades, in which I might well lose my
accumulated work, just isn’t justified any more.
Hi
A missing file…
<afaerber> agraf, malcolmlewis: the ubootconfig.txt is still missing
<agraf> zbenjamin: fvogt changed the logic in the config file to split the 64bit payload setting into a file that now is provided by u-boot
<afaerber> malcolmlewis, zbenjamin: You can create an extraconfig.txt with the required contents
<agraf> zbenjamin: maybe that file doesn't exist
<afaerber> agraf, yep, it does not
<agraf> afaerber:so where should the file come from? i don't see it in the u-boot package either
<afaerber> agraf, I thought that's where he added it?
<agraf> oh, it generates it on the fly
<agraf> awesome
<afaerber> malcolmlewis, zbenjamin: arm_control=0x200 is the magic line
<agraf> https://build.opensuse.org/package/view_file/hardware:boot:staging/u-boot/u-boot-rpi3.spec?expand=1
<agraf> line 240
<zbenjamin> agraf: afaerber: so creating a file extraconfig.txt with arm_control=0x200 will fix it?
<afaerber> zbenjamin, on the FAT partition, yes
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
For those preparing to do the upgrade of Tumbleweed to 4.17.1, you can avoid this reboot problem by preparing the boot volume ahead of the “zypper dup” and reboot. While you’re still running 4.16.?, connect to the /boot/efi directory and issue ‘echo “arm_control=0x200” >> extraconfig.txt’ to create (or append to) this extra configuration file. If you forget to do this ahead of the reboot, you’ll need to mount your boot volume on some other system, find that partition (the first on the drive, and FAT format), and create that extraconfig.txt file. Boots just fine with this addition, on the Raspberry Pi-3B.