Yes I wrote the instructions on the raspberry pi wiki about how to boot arm64. But I'm not talking about that here.
Raspberry pi is now supposedly fully supported in the Linux kernel - https://www.omgubuntu.co.uk/2018/08/linux-4-18-kernel-release-features - but I don't want to have to go through the pain of compiling this. I would like generic-lpae support for the reasons I outlined in the first post. Currently Ubuntu only provides one install media for the pi which is the server image (which doesn't work on the pi3 anyway). I would like to get armhf fully working (or closer to) in the debian- installer/ubiquity. I'm willing to work on patches, but I only have a pi3 to work with. It is also very hard to get changes/patches accepted in raspi2 packages. Generic-lpae seems better supported. -- 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
