Ubuntu 20.04 (Focal Fossa)

[cjan]

this is what i'm talking about llvmpipe is being used instead of the graphics driver.

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies, driver?

[kerry_s]

this is what i'm talking about llvmpipe is being used instead of the graphics driver.

This seems a bit too good to be true but...

Would this improve the graphical performance of the desktop?

I might consider ubuntu for the Pi...

it seem to run okay, but the v3d drivers in 19 ran much better. the llvmpipe seems to use more cpu, which increased the temp. i run just heat sinks, no fan. anyways it's slow enough to me i booted right back into raspbian after that overclock test.

[kerry_s]

this is what i'm talking about llvmpipe is being used instead of the graphics driver.

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies, driver?

its supposed to work like the fkms in raspbian, but its not there yet

[pierro78]

so I understand the v3d drivers are not there yet in 20.04 ?

does somebody know if v3d drivers make a difference if I only use my rpi4 through remote desktop ??

thanks !

[kerry_s]

so I understand the v3d drivers are not there yet in 20.04 ?

does somebody know if v3d drivers make a difference if I only use my rpi4 through remote desktop ??

thanks !

it's not using it at all, there switching to llvmpipe as the standard graphics.
should make no difference in your case.

[petro]

my pi 4b 4Gb, why there is no bluetooth?

[senpaidev]

Hi all,

I have installed and updated Focal Fossa (20.04 LTE) on my RPI 4 (4mb ram) using the Ubuntu Desktop. After some "hacking/Google" all works fine e.g. WiFi, LAN, Bluetooth, Sound etc. The only thing I have not yet managed to fix is overclocking. When I add the parameters to "/boot/firmware/config.txt" and reboot, the system will not start at all. Only after removing the parameters it will boot as normal. Has anyone experienced the same or have a solution? I am using exactly the same parameters I used in 18.04 and/or 19.10 where it all worked well.

So I was finally able to use the ubuntu desktop via xrdp. However all the things you mentioned are broken for me too. I tried a couple of fixes mentioned for bluetooth / wifi / network but none seem to work. Main issue with doing stuff is that I am running it headless (I don't have a HDMI monitor / TV). Somehow I have managed to get it connect to my wifi so that I can ssh / rdp it but beyond that I am lost. It would be great if you could list out the fixes for network or wifi as they are critical for docker. Thanks in advance.

[RodDev]

I've installed Ubuntu Server 20.04 on my raspberry pi 4 4GB and it's flying... it does not only boot up and run faster but also it makes a great deal on the temperature, way cooler as well. Doing between 37 to 39 Degrees Celsius running NGINX Web Server with SanDisk Ultra 200GB Micro SDXC Memory Card (SDSDQUAN-200G-G4A) on a miniature v5 cooling fan

raspi4temp.jpg (113.1 KiB) Viewed 1116 times

[esbeeb]

I finally got 2.4GHZ-only wifi working from the CLI (no desktop environment). Please see here:
https://ubuntuforums.org/showthread.php ... st13952620

[kerry_s]

my pi 4b 4Gb, why there is no bluetooth?

if it's like 19, then you have to install and enable it.

[kerry_s]

I finally got 2.4GHZ-only wifi working from the CLI (no desktop environment). Please see here:
https://ubuntuforums.org/showthread.php ... st13952620

how does that help, you still need ethernet?
my router is down the hall and then up to second floor. 50ft of ethernet just reaches it and i don't have that any more.

[waveform80]

does upgrade from daily build, its the same?

That depends when your daily build dates from. At some point in the development cycle (checks ... 1 month ago apparently), some contents of the boot partition were changed (merging nobtcmd/btcmd.txt back into cmdline.txt for example) and those things are non-package-managed files so an update won't touch them. In other words, if you started from a fairly recent daily an upgrade will bring to the full "released" state. Otherwise a full refresh would be required.

[waveform80]

is that "renderer: networkd" needed now? it's not in the how to.
everything else is pretty much what i got.
i removed the "dhcp4: true" cause it just kept throwing errors in "sudo netplan --debug try"

No, "renderer: networkd" was suggested as a work-around for a still-existing issue that wifi won't be activated by cloud-init on first boot (works fine on subsequent boots). That issue is being tracked in LP: #1870346 and at the moment looks as though it may not be cloud-init, but netplan (I'm not 100% sure either way yet).

There was an issue that cropped in netplan towards the end of the development cycle (right at the end in fact; it resulted in us re-spinning the images just before release) which prevented netplan apply from working. So, if you were working from a daily and didn't upgrade immediately before release you may have run into that (LP: #1874377).

Then there's the issue that in some jurisdictions, no 5GHz wifi bands are available until the regulatory domain is properly set, but I didn't manage to get "iw" included in the image by default (too many other things breaking last minute!). Generally this doesn't matter because 2GHz bands are still available so in the vast majority of cases it still "just works", albeit sub-optimally. Still, to set the regulatory domain:

Code: Select all

$ sudo apt install iw
$ sudo iw reg set GB

(substitute your location for GB accordingly)

Hope that helps!

Dave.

[waveform80]

does upgrade from daily build, its the same?

after upgrade to 20.04, sway/wayland broken.
system dead even Ctrl+Alt+F2, maybe mesa issue not sure?

ps. Rpi2-armhf, before upgrade all good.

Sorry to hear that - I did briefly test a wayland desktop (from ubuntu-desktop as I recall) on a Pi4 4Gb with a daily image towards the end of the cycle which operated ... somewhat jerkily, and managed to launch a few simple applications. Unfortunately a wayland desktop isn't something we officially support yet on the Pi, so this was purely a test to satisfy my curiosity.

Did you have any pieces from PPAs installed to get wayland working previously? If so, they may not have been refreshed for Focal yet (or things may need rebuilding for it, or may have been superseded by the main archive).

[waveform80]

it's suppose to go in /boot/firmware/usercfg.txt

just curious in your about it it using llvmpipe for video?

also are you 32 or 64 bit? i was 32bit in my testing.

Just to clear up confusion around this:

• You can put stuff in config.txt or usercfg.txt (or syscfg.txt) - it shouldn't make any difference (the latter are simply included from the former
• However, the split exists because we consider config.txt "distro-controlled" - in other words, we're free to modify it or overwrite it on upgrade - if you've put modifications in there we may or may not maintain those
• usercfg.txt is yours: put whatever you like in it, we won't touch it (on the other hand, put stuff in there that breaks the boot: you get to keep the pieces :)
• syscfg.txt is between these two: the package manager won't touch it; it's intended for a system tool to modify (pibootctl or stuff build on top of it) at your direction
• But other than these intentions (and they are just that), functionally, there's no difference where you stick your modifications

[waveform80]

my pi 4b 4Gb, why there is no bluetooth?

Install the pi-bluetooth package:

Code: Select all

$ sudo apt install pi-bluetooth
$ sudo reboot

There's some bits that run on startup - I can't remember if the reboot is absolutely required after installation so I've just included that as a precaution.

[cjan]

Did you have any pieces from PPAs installed to get wayland working previously? If so, they may not have been refreshed for Focal yet (or things may need rebuilding for it, or may have been superseded by the main archive).

NO, sway/wayland install by default repos.
and, test mir-shell/wayland from PPA, went good.

[tgwaste]

Just doesnt work because Ubuntu + Pi + Wifi NEVER EVER WORKS RIGHT.
I can SSH in to the pi just fine and wifi is enabled (on 2.4 not 5Gz.. that never works either).
But the desktop environment thinks there is no network connection.

I mean... does anyone even TEST these official releases?

[B.Goode]

Just doesnt work because Ubuntu + Pi + Wifi NEVER EVER WORKS RIGHT.
I can SSH in to the pi just fine and wifi is enabled (on 2.4 not 5Gz.. that never works either).
But the desktop environment thinks there is no network connection.

I mean... does anyone even TEST these official releases?

From the initial post in this thread, written by a spokesperson for Canonical whose software product you are commenting on -

Do feel free to report any general experiences here, but if you have specific issues it's probably best to open a new thread or open a bug on Launchpad.

The bit about telling Canonical you think there is a bug seems good advice.

Raspberry Pi have their own quite functional Operating System - RasPiOS. https://www.raspberrypi.org/downloads/raspberry-pi-os/

[saxonpaul92]

Ubuntu 20.04 on Raspberry Pi 4 is totally useless. The font in the command line is enormous and I have not been able to lower it.

I have 24 inch Samsung Monitor that works perfectly but it does not appear that the pi can sense the screen size.

Tried installing ubuntu-desktop and the resolution is stuck on 640x480.

Any ideas?

[kerry_s]

Ubuntu 20.04 on Raspberry Pi 4 is totally useless. The font in the command line is enormous and I have not been able to lower it.

I have 24 inch Samsung Monitor that works perfectly but it does not appear that the pi can sense the screen size.

Tried installing ubuntu-desktop and the resolution is stuck on 640x480.

Any ideas?

does it work in standard raspberry pi os? if not, it's your monitor, not all work out of the box.
ubuntu is geared towards server so desktop is not there priority, if you have lan & run headless, ubuntu would work out of the box.

[pyavitz]

I can SSH in to the pi just fine and wifi is enabled (on 2.4 not 5Gz.. that never works either).

I'm not using the official Ubuntu 20.04, but have noticed if using Network Manager with the Pi4, you need to add your country code to the crda file.

Code: Select all

sudo nano /etc/default/crda 
REGDOMAIN=US    # Your country code

In my case this fixes the 5GHz issue.

[kerry_s]

alright, tried ubuntu again.
it seems it can no longer properly detect the display. so it's not your monitor it's ubuntu.
it just gets worse & worse, not even worth trying to fix the many issues just to use.

unless they come out with a raspberry desktop version, i'm done with them.