This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug was fixed in the package linux-raspi-5.4 -
5.4.0-1042.46~18.04.3
---
linux-raspi-5.4 (5.4.0-1042.46~18.04.3) bionic; urgency=medium
* bionic/linux-raspi-5.4: 5.4.0-1042.46~18.04.3 -proposed tracker
(LP: #1938917)
* Bad Linux ARM64 Image magic (LP: #1938912)
- [Pa
This appears to be fixed in the current beta kernel for 18-pi -
5.4.0-1042.46~18.04.3 r337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938912
Title:
Bad Linux ARM64 Image magic
To manage notific
** Also affects: linux-raspi-5.4 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-raspi-5.4 (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-raspi-5.4 (Ubuntu)
Status: New => Invalid
** Changed in: linux-raspi-5.4 (Ubuntu Bionic)
** Description changed:
[Impact]
On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the failed boot from one of those
devices:
Hit any key to stop autoboot:
** Description changed:
- on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
+ [Impact]
+
+ On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the faile
I also noticed just now that this kernel from the 20 track does seem to work
fine on uc20 systems:
pi-kernel5.4.0-1042.46 33120/beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938912
