We have a kernel dedicated to the RaspberryPi boards (linux-raspi2), why do you want to use the generic-lpae kernel instead?
Besides, you can't mix dtb and kernels from different arches / branches - they won't work together. Someone mentioned that it was able to install the generic arm64 server img on RaspberryPi, you might give that a try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795869 Title: Generic-lpae unbootable on raspberry pi 3 Status in linux package in Ubuntu: Triaged Bug description: I've been trying to boot the generic-lpae kernel on my pi 3B. I've tried via U-boot and the pi's built in bootloader, but without success. There seems to be something inherently missing from the kernel. There are no bcm dtb files under armhf, but they are there for arm64. Using the one from arm64 with generic-lpae still fails to boot. Without the use of generic-lpae it is very hard to use the mini/netboot installer. It also means there is no hardware enablement stack on raspberry pi. Debian has had the ability to boot generic-lpae on the pi2 since 2015 I think! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
