[Bug 1150408] New: wrong location of raspberry pi 1b firmware files in rpm
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408 Bug ID: 1150408 Summary: wrong location of raspberry pi 1b firmware files in rpm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv5 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: freek@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After "zypper dup --no-r" on a recent installed Raspberry Pi 1B system, the system did not boot anymore. It turned out that the files in the rpm packet raspberrypi-firmware use the wrong location for storage. They are stored in /boot/vc/ but should be stored in /boot/efi/ . -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c2
Freek de Kruijf
Could you try to: 1. remove it, and check /boot/vc and /boot/efi 2. re-install it, and check both folders again
This did what you said it would do, even more files entered in /boot/efi/ than were present before the remove. Probably because the remove of raspberrypi-firmware also removed two other packages, which were also added with the install. The script has a condition, so I wonder if this condition is met when upgrading the system from the previous version. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c3
--- Comment #3 from Guillaume GARDET
The script has a condition, so I wonder if this condition is met when upgrading the system from the previous version.
It should be ok as an upgrade is just a remove of old rpm followed by the installation of the new rpm. At next upgrade, could you monitor this closely to check what happens, please? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c4
--- Comment #4 from Freek de Kruijf
(In reply to Freek de Kruijf from comment #2)
The script has a condition, so I wonder if this condition is met when upgrading the system from the previous version.
It should be ok as an upgrade is just a remove of old rpm followed by the installation of the new rpm.
At next upgrade, could you monitor this closely to check what happens, please?
Waiting for a spare SD card to install the previous image and do the upgrade after that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c5
Andreas Färber
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c6
--- Comment #6 from Guillaume GARDET
Maybe it should've been %postun instead of %preun?
Not sure how it could change the behabior. It works fine on manual installation/desinstallation. I wonder what is different on upgrade path. I need to reproduce it locally.
However, even after extracting the latest hardware:boot .rpm's files back onto the partition, TF-A is no longer booting for me, it executes BL1 but gets stuck at "INFO: BL1: Loading BL2". I guess a blob regression in raspberrypi-firmware package in addition to the cp/rm problems.
Could you open a separate bug for this one please ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c7
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c8
--- Comment #8 from Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408
http://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c9
Guillaume GARDET
participants (1)
-
bugzilla_noreply@novell.com