Hey there,
I didn’t know if it would be better putting this into the OS or Rock 5 category but as it seems like an issue related to the Rock Pi 5B directly it went here.
My current software-“setup”:
Ubuntu Build from Radxa Wiki
Kept it at 20.04, just updated
Ubuntu Desktop with xfce4 installed
What am I trying to do: Emulate x86. I am familiar with box86 and I am hoping I can get it running on this beauty of a board. But I get issues when trying to install pi-apps (I guess that is still the easiest way to install box86):
rock@rock-5b:~$ sudo wget -qO- https raw githubusercontent com/Botspot/pi-apps/master/install | bash
[sudo] password for rock:
Hit:1 http ports ubuntu com/ubuntu-ports focal InRelease
Hit:2 http ports ubuntu com/ubuntu-ports focal-security InRelease
Hit:3 http ports ubuntu com/ubuntu-ports focal-updates InRelease
Hit:4 http ports ubuntu com/ubuntu-ports focal-backports InRelease
Get:5 http apt radxa com/focal-stable focal InRelease [2359 B]
Err:5 http apt radxa com/focal-stable focal InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9B98116C9AA302C7
Reading package lists… Done
W: GPG error: http apt radxa com/focal-stable focal InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9B98116C9AA302C7
E: The repository ‘http apt radxa com/focal-stable focal InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
The command ‘sudo apt update’ failed. Before Pi-Apps will work, you must fix your apt package-management system.
– Removed links because of link limitation –
I tried to fix broken packages - No broken packages. I tried to reinstall apt and wget - Nothing changed. I tried to allow unsigned packages in apt-update. I can’t think of any issues that would lead to a broken package-management system.
If someone has a clue what could have lead to this error and maybe even think of a solution other than another distro you would make my day.
I tried the “official” Debian build as well - with different issues (I already forgot what caused the issues in Debian after troubleshooting and rewriting images over and over).