This is more info than an issue
I'm new to PINN so bare with.
1st install of PINN was done with rpi-imager. It installs an older version and it never offered to upgrade. Ended up downloading the latest build from repo and installing v3.9.8 (to NVME drive)
Noticed Ubuntu builds for 24.10 and 25.04 but not the latest 26.04, which a fair enough
Decided to have a go at building my own /os for Ubuntu 26.04 using the downloadable image here: https://ubuntu.com/download/raspberry-pi.
I used the docs here and also this 24.04 build as a template: https://sourceforge.net/projects/pinn/files/os/ubuntu2404/ Managed to build the partition .tar.xz files and associated .json files and put it all on USB drive under /os
I used the raw preinstalled Ubuntu image with no changes as the base. I got Ubuntu 26.04 to install and boot through PINN. It starts up takes you through the guided setup and to the desktop but then froze. Had to power off PI-5. I had a look at the system logs on the root partition and couldn't see any errors, seems Pi just froze.
Decided to install 26.04 to an SD-card and boot as a standalone OS, just to test it works without PINN. All good. Setup completes, no freeze, stable with the limited number of installed apps working ok.
Thought I would test this post setup version as a base for the PINN install. This works. With Ubuntu booting and remaining stable. However some weirdness. Snapd apps don't start with this error:
snap-confine is packaged without necessary permissions and cannot continue
required permitted capability cap_dac_override not found in current capabilities:
=: Argument list too long
However a "sudo apt install --reinstall snapd" got it working again. Is this some permissions issue in creating the partition tars?
These are the commands I'm using to image from the sd-card mounted to linux filesystem:
sudo bsdtar --numeric-owner --format gnutar --one-file-system -cpvf ~/pinn/os/ubuntu2604/system-boot.tar .
sudo find . -type s -delete
sudo getfacl -s -R . | sudo tee acl_permissions.pinn
sudo bsdtar --numeric-owner --format gnutar --one-file-system -cpf ~/pinn/os/ubuntu2604/writable.tar .
cd ~/pinn/os/ubuntu2604
sudo chown user:user ./system-boot.tar
sudo chown user:user ./writable.tar
xz -9 -e system-boot.tar
xz -9 -e writable.tar
Other things I noticed that seem to just be Ubuntu weirdness:
Locales were not installed properly, had to "sudo dpkg-reconfigure locales"
The Pi eeprom package seems out of date and just reinstalling it doesn't work. This means when you edit firmware settings with "sudo rpi-eeprom-config --edit" it reports an old version. Ended up doing a "sudo git clone https://github.com/raspberrypi/rpi-eeprom" and replacing the files in "/usr/lib/firmware/raspberrypi/bootloader-2712" which doesn't seem the right thing to do, but works.
Any advice, experience, signpost to Ubuntu/PINN build docs welcome.
This is more info than an issue
I'm new to PINN so bare with.
1st install of PINN was done with rpi-imager. It installs an older version and it never offered to upgrade. Ended up downloading the latest build from repo and installing v3.9.8 (to NVME drive)
Noticed Ubuntu builds for 24.10 and 25.04 but not the latest 26.04, which a fair enough
Decided to have a go at building my own /os for Ubuntu 26.04 using the downloadable image here: https://ubuntu.com/download/raspberry-pi.
I used the docs here and also this 24.04 build as a template: https://sourceforge.net/projects/pinn/files/os/ubuntu2404/ Managed to build the partition .tar.xz files and associated .json files and put it all on USB drive under /os
I used the raw preinstalled Ubuntu image with no changes as the base. I got Ubuntu 26.04 to install and boot through PINN. It starts up takes you through the guided setup and to the desktop but then froze. Had to power off PI-5. I had a look at the system logs on the root partition and couldn't see any errors, seems Pi just froze.
Decided to install 26.04 to an SD-card and boot as a standalone OS, just to test it works without PINN. All good. Setup completes, no freeze, stable with the limited number of installed apps working ok.
Thought I would test this post setup version as a base for the PINN install. This works. With Ubuntu booting and remaining stable. However some weirdness. Snapd apps don't start with this error:
snap-confine is packaged without necessary permissions and cannot continue
required permitted capability cap_dac_override not found in current capabilities:
=: Argument list too long
However a "sudo apt install --reinstall snapd" got it working again. Is this some permissions issue in creating the partition tars?
These are the commands I'm using to image from the sd-card mounted to linux filesystem:
sudo bsdtar --numeric-owner --format gnutar --one-file-system -cpvf ~/pinn/os/ubuntu2604/system-boot.tar .
sudo find . -type s -delete
sudo getfacl -s -R . | sudo tee acl_permissions.pinn
sudo bsdtar --numeric-owner --format gnutar --one-file-system -cpf ~/pinn/os/ubuntu2604/writable.tar .
cd ~/pinn/os/ubuntu2604
sudo chown user:user ./system-boot.tar
sudo chown user:user ./writable.tar
xz -9 -e system-boot.tar
xz -9 -e writable.tar
Other things I noticed that seem to just be Ubuntu weirdness:
Locales were not installed properly, had to "sudo dpkg-reconfigure locales"
The Pi eeprom package seems out of date and just reinstalling it doesn't work. This means when you edit firmware settings with "sudo rpi-eeprom-config --edit" it reports an old version. Ended up doing a "sudo git clone https://github.com/raspberrypi/rpi-eeprom" and replacing the files in "/usr/lib/firmware/raspberrypi/bootloader-2712" which doesn't seem the right thing to do, but works.
Any advice, experience, signpost to Ubuntu/PINN build docs welcome.