[Bug 1848247] Re: 3A+ boot failure on Eoan

[Dave Jones]

Can confirm that the test kernel from LP: #1848790 comment #11 fixes
boot on 3A+ (remove vc4-fkms-v3d overlay from config.txt too, and boot
operates correctly with framebuffer working). Tested on arm64 3A+ (and
3B, 3B+, 4B); need to test on armhf too.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848247

Title:
  3A+ boot failure on Eoan

Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-firmware-raspi2 source package in Eoan:
  Triaged

Bug description:
  The current Eoan image hits a kernel panic when booting on a Raspberry
  Pi 3A+. Unfortunately it does so before the serial console has been
  enabled so there's no useful output beyond what scrolls by rapidly on
  the framebuffer console.

  It is notable that the start.elf bootloader (prior to u-boot), loads
  the device-tree for the 3B+ because no device-tree specific to the 3A+
  exists (in the 27*.dtb set; there is one in the 28*.dtb set but I'm
  not convinced those are used by anything); u-boot proceeds
  successfully but then the kernel panics.

  This occurs on both the armhf and arm64 architectures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1848247/+subscriptions