Huh -- I thought PipeWire was an audio-only thing, a replacement for PulseAudio.

HardSun:  When you wrote above, "is this check correct", what are you checking for?

HardSun:  Those are the binaries which are expected to be running.  Is your audio not working?

OT:  I didn't so much "choose" GitHub as "defaulted" to it.

• It's familiar, and I already had it set up.

• I didn't notice any Microsoft branding (nor was I looking for any).

• GitHub didn't force me to insert any Microsoft-specific code, or force me to use Windows or Edge.

• If they're paying for GitHub to exist and are hosting OSS without forcing authors to "bend to their will", isn't that good for OSS?

That's why using GitHib wasn't a big deal for me.  But, since this is arguably a Devuan-specific issue, the repo has been moved from GitHub to "https://git.devuan.org/davesp/start_user_pipewire".

For a semi-manual way of changing the kernel for the next boot, from a running system (not from a boot menu), Git can be used.

I successfully used this approach to test a new kernel built from "rpi-image-builder".

With a system running from a Rasp Pi 4 image (from "https://arm-files.devuan.org/"), I created a Git repo in "/boot", checked-in the current files on a "6.1.93" branch, created a new branch for "6.12.55", installed the new kernel image package, then checked-in that branch.

The new kernel booted; if it hadn't, the SD card would be moved to another box (with Git installed) so Git could be used to switch the SD card boot dir to the earlier, working branch.

(Repos could also be created in the other dirs touched by a kernel install, "/etc", "/usr/lib", and "/usr/share/doc", with kernel-specific branches.)

This approach doesn't provide a boot menu, but it does provide a simple-ish way to get a Rasp Pi booting again while experimenting with new kernel versions.