Bug 1203803 - Leap Micro 5.2 not booting after install on RPi4
Leap Micro 5.2 not booting after install on RPi4
Status: NEW
Classification: openSUSE
Product: PUBLIC SUSE Linux Enterprise Micro 5.3
Classification: openSUSE
Component: Installation
unspecified
aarch64 Other
: P2 - High : Major
: ---
Assigned To: Lubos Kocman
Jiri Srain
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-09-27 14:46 UTC by Felix Niederwanger
Modified: 2022-10-05 12:17 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Screenshot of RPi in stuck boot state (292.76 KB, image/jpeg)
2022-09-27 14:46 UTC, Felix Niederwanger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Niederwanger 2022-09-27 14:46:41 UTC
Created attachment 861778 [details]
Screenshot of RPi in stuck boot state

Installing Leap Micro 5.2 on a Raspberry Pi 4 results in a non-bootable system with the error message "Firmware not found" (See screenshot).

I used the "Offline Image" for UEFI Arm 64-bit servers, `dd` it to a USB stick. The installer works fine and by using the provided default values I could install the system on a 64 GB SD-Card.

After finishing the installation and rebooting into the system, the internal bootloader complains about "Firmware not found" - See attached screenshot.

I updated the RPi bootloader to the most current version but still no bootable system. The system is stuck at the boot state, visible in the screenshot.

## Reproducer

* Use the "Offline image" for UEFI Arm 64-bit servers and dd it to any USB stick:

> dd if=openSUSE-Leap-Micro-5.2-DVD-aarch64-Build41.9-Media.iso of=/dev/sda bs=4M iflag=fullblock oflag=sync status=progress

* Disconnect the network to avoid https://bugzilla.opensuse.org/show_bug.cgi?id=1203795
* Boot the Raspberry Pi from this image, run the installation
* Install Leap Micro 5.2 using the default settings
* Reboot
* System cannot be booted
Comment 1 Jiri Srain 2022-09-27 18:07:49 UTC
The problem is: raspberry-firmware packages are not part of 5.2, not even the on-line repositories. There is a maintenance update in progress.

5.3 GMC candidate build has those packages included, please, make sure that they are installed.
Comment 2 Jiri Srain 2022-09-27 18:09:07 UTC
I mean SLE Micro 5.3 GMC candidate build; Leap Micro should get them as well.

Lubos, since I had a bug in the package list, please, check that....
Comment 3 Lubos Kocman 2022-10-05 12:14:34 UTC
Ack, I did use self-install image for 5.2 install on my rpi4, which is what we advertise to use.

Let's address this in 5.3 which will be out soon

Lubos