** Changed in: snapd
Status: Triaged => Fix Released
** Changed in: snapd
Milestone: None => 2.48.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888691
Title:
[uc20] rpi4 does not
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888691
Title:
[uc20] rpi4 does not boot
I've confirmed that this is the case. The Pi refreshes the kernel to
179, reboots and tries to run the 179 kernel with the 156 DTBs. We're
not maintaining DTB backwards compatibility, so not a kernel problem.
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Invalid
--
You
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888691
Title:
[uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps
To
5.4.0-1015-raspi works just fine on armhf classic so there's nothing
wrong per se with the kernel and DTBs. The fact that this works on a
different Pi makes be believe that it's a DTB issue. Is this the
gadget/kernel out-of-sync refresh issue? Is the Pi trying to boot the
1015 kernel using the
** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)
** Also affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888691
Title:
[uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps
To
