First of all, introductions: I'm Dave Jones. Some of you will know me from things like picamera, piwheels, pisense, gpio-zero and so forth (he says, sounding like Troy McClure
). Nowadays, I'm also on the Canonical Foundations team, with responsibility for Ubuntu on the Pi which means:
- You can blame me for a lot of the things mentioned on this thread!
- This is probably the wrong place to discuss a lot of this; there's absolutely no point complaining to the fine folks at the Pi Foundation about Ubuntu. Bug me instead (see below for more information on how to bug Dave)!
- As already mentioned by others, https://ubuntuforums.org/ and https://askubuntu.com/ are good places to ask about things like this. In particular, I trawl the "raspberrypi" tag on the latter in spare moments (which are few and far between in the run-up to a release, but will be a bit more plentiful now).
There's three issues I'm currently aware of with the current Eoan Ermine release, which were discovered very late in the testing cycle (which others have diligently pointed out, but I may as well summarise with some links here):
- USB not working under arm64 on Pi4 -- this applies specifically to the arm64 variant; the armhf variant is fine. A test kernel with a fix has been built; testers much appreciated! A workaround for now (mentioned ealier) is to stick "total_mem=3072" in "usercfg.txt" on the boot partition (this will lop 1Gb off your RAM, but things will work).
- 3A+ boot failure on Eoan -- this one is more complex and has partly to do with Ubuntu's reliance on u-boot. That in itself is a complex topic which, for the sake of brevity, I won't delve into here. We do have a work-around but it's not ideal (no framebuffer console); the kernel team are looking into a more complete fix (the issue ultimately seems to be in the bcm2708_fb driver).
- login available before cloud-init completed -- a long-standing issue, and one which I do have a pi-specific fix for, but which unfortunately got lost in the rush to get Pi4 support into Eoan. I'll make sure it's implemented for Focal (20.04).
And one thing which isn't a bug:
- Bluetooth: we don't support bluetooth out of the box. Ubuntu on Pi is primarily a server distro and thus a stable serial console was prioritized over out-of-the-box Bluetooth support (note: I don't work on Ubuntu MATE; that's something separate).
Bluetooth can be enabled by installing the "pi-bluetooth" package and switching a line in "syscfg.txt" on the boot partition from "include nobtcfg.txt" to "include "btcfg.txt". A tool to manage the hardware configuration on the Pi (including Bluetooth) is being developed, but I didn't have time to finish it for Eoan.
I've noted one other issue which I wasn't aware of in this thread:
I also noticed the wifi in Ubuntu 19.10 does not support 5Ghz band. [...]
If I can reproduce locally, I'll file a bug for that (if someone hasn't already) and update this post with the link.
If you want to know the state of fixes for these things, subscribe to those bugs. If you've got additional information, please feel free to add it to those bugs but do read them (and their comments) first; duplicated information doesn't really add anything (just takes time to read). Which is all to say: launchpad is generally the right place to notify us about issues with Ubuntu on Pi.
For more immediate purposes, I'm usually on Freenode as "waveform" on the #raspberrypi, and #ubuntu-server channels. Free free to ping me questions about Ubuntu on Pi on any of those channels, but bear in mind that I'm in the UK's timezone, and that I'm one guy: if I don't respond quickly ... well, I'm probably swamped (or dealing with a 4 y/o child!), sorry!
In the meantime, thanks for your patience!