Updating / packages for Patchbox OS

Hi there!

I installed the 2022 image of Patchbox OS (latest available from Patchbox OS – Raspberry Pi OS for Audio Projects) and I’m a Linux newbie but know some basic scripting and C++. I have a PiSound and rpi 3b+.

I’m trying to get miracast ability working but get this error.

flatpak install flathub org.gnome.NetworkDisplays
Looking for matches…
error: Nothing matches org.gnome.NetworkDisplays in remote flathub

I downloaded the .flatpakref file for NetworkDisplays and tried to install by running it, but it also has an error. I first followed this and rebooted. https://flathub.org/en/setup/Debian

flatpak install org.gnome.NetworkDisplays.flatpakref
error: No such ref 'app/org.gnome.NetworkDisplays/arm/stable' in remote flathub

I also tried to get my USB DisplayLink display working (I have a portable monitor that doesnt have HDMI), but had errors with the public keys being expired in the debian repos. evdi-dkms dependency is an issue.

$ sudo apt update
Get:1 http://ftp.ca.debian.org/debian sid InRelease [193 kB]
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Get:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Get:4 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages [13.2 MB]
Err:1 http://ftp.ca.debian.org/debian sid InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY 78DBA3BC47EF2265
Hit:5 http://apt.blokas.io rpi InRelease
Reading package lists... Done
W: GPG error: http://ftp.ca.debian.org/debian sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY 78DBA3BC47EF2265
E: The repository 'http://ftp.ca.debian.org/debian sid 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.

And with just evdi-dkms

sudo apt install evdi-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  evdi-dkms
0 upgraded, 1 newly installed, 0 to remove and 423 not upgraded.
Need to get 0 B/28.9 kB of archives.
After this operation, 160 kB of additional disk space will be used.
Selecting previously unselected package evdi-dkms.
(Reading database ... 163389 files and directories currently installed.)
Preparing to unpack .../evdi-dkms_1.9.0+dfsg-1_all.deb ...
Unpacking evdi-dkms (1.9.0+dfsg-1) ...
Setting up evdi-dkms (1.9.0+dfsg-1) ...
Loading new evdi-1.9.0+dfsg DKMS files...
It is likely that 5.15.36-rt41-v7+ belongs to a chroot's host
Building for 5.15.36-rt41+, 5.15.36-rt41-v7+, 5.15.36-rt41-v7l+, 5.15.36-rt41-v8+, 6.1.21+, 6.1.21-v7+ and 6.1.21-v7l+
Module build for kernel 5.15.36-rt41+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel 5.15.36-rt41-v7+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel 5.15.36-rt41-v7l+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel 5.15.36-rt41-v8+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Building initial module for 6.1.21+
Error! Bad return status for module build on kernel: 6.1.21+ (armv7l)
Consult /var/lib/dkms/evdi/1.9.0+dfsg/build/make.log for more information.
dpkg: error processing package evdi-dkms (--configure):
 installed evdi-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 evdi-dkms

E: Sub-process /usr/bin/dpkg returned an error code (1)

The log shows

DKMS make.log for evdi-1.9.0+dfsg for kernel 6.1.21+ (armv7l)
Sun 30 Aug 18:19:53 BST 2026
make: Entering directory '/usr/src/linux-headers-6.1.21+'
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_drv.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_dev.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_sysfs.o
  CC [M]  /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_modeset.o
In file included from /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_dev.c:30:
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.h:23:10: fatal error: drm/drm_irq.h: No such file or directory
   23 | #include <drm/drm_irq.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [scripts/Makefile.build:250: /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_platform_dev.o] Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_modeset.c:25:
/var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_drm_drv.h:23:10: fatal error: drm/drm_irq.h: No such file or directory
   23 | #include <drm/drm_irq.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [scripts/Makefile.build:250: /var/lib/dkms/evdi/1.9.0+dfsg/build/evdi_modeset.o] Error 1
make: *** [Makefile:2012: /var/lib/dkms/evdi/1.9.0+dfsg/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.1.21+'

For now I just bought a cheap capture card, and can use my laptop as a portable HDMI display via capture card / viewing the rpi’s HDMI output as a webcam feed on the laptop.

Would I be better off just trying to use the latest Raspberry Pi OS instead of Patchbox from 2022, for the packages to work? The Patchbox OS config description I dont fully understand but seems to be what I want; realtime kernel, jack audio, configured for audio and midi applications. Are the Patchbox OS settings something I can apply with a few commands in the terminal, or a script, on top of a newer rpiOS image? I saw a lot of notes in the github about building PatchboxOS but I think that’s beyond me right now.

Or perhaps there’s a newer PatchboxOS image somewhere I can download to fix these package issues? I saw reference to a 2024 build? And I see some activity on the pisound github?

Thanks for any help!

Try using this Patchbox OS build as your starting point: [Beta] Patchbox OS Bookworm ARM64 2024-04-04

Thanks so much, will give that a try. I’m remembering now that I grabbed the 2022 build after reading that thread, because of the realtime kernel not working on 3B+. I think though I’ll take the other packages working, and see if I notice any latency issues. Will post back how it goes.

the real time kernel build we created currently does not boot on Pi Zero, Pi 2, Pi 3 (including B+).

Cheers!

Looking better already… I think the 32 bit OS in the 2022 image was part of the issue; the 2024 image has a 64 bit OS, so more packages are available these days.

flatpak install flathub org.gnome.NetworkDisplays
Looking for matches…
Required runtime for org.gnome.NetworkDisplays/aarch64/stable (runtime/org.gnome.Platform/aarch64/49) found in remote flathub
Do you want to install it? [Y/n]: y

gnome-network-displays is not working, and I suspect its because it’s only for either Gnome or KDE desktop environments, and not for Patchbox’s lightweight GUI but that’s fine. It starts to link (my sink display sees the attempt) and throws this error:

(gnome-network-displays:2): Gnd-WARNING **: 04:56:51.008: Failed to create screencast session: Screencast SelectSources() failed

It was more an issue that packages were generally failing from the repos, so I’m glad we’re past that! I can work with this :slight_smile: Cheers, thanks again for the help!

You could try uninstalling (or just switching the environment) and installing another desktop manager software. You can follow any Debian based software guide (not exclusively locked to Patchbox OS or Raspberry Pi OS) for how to do it. Keep in mind that the latest Patchbox OS release is using bookworm Debian release. The latest is trixie. We’ll get around to updating the OS, but first we have to finish our current stuff we’re working on. :slightly_smiling_face: