It says you're missing free firmware. Make sure firmware-linux-free is installed. If you need non-free firmware, you won't be able to use a libre kernel. Have you tried booting the daedalus kernel? It should still be there.

The alsa error has a fix somewhere else on this forum. Search for alsa_restore and I think you'll find it. It's an easy fix.

Also make sure the video drivers are installed. I'm not sure which you need but there's xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-radeon

Yes, follow the instructions on the linux-libre site. Install their key, add their sources file, update, install.
You'll still have the devuan sources active and can upgrade packages. The kernel will come from the freesh sources.

Note: I pasted the 'modernized' sources below. It's possible to use the modernized source for freesh along with the older sources.list for the devuan sources. I just tested it and 'apt update' didn't complain.

Here's an example iso of 32-bit devuan with the linux-libre kernel. Refracta is just devuan with some tweaks and different set of packages. This one is old. I need to make new isos and stop calling them Testing.
https://get.refracta.org/files/testing/ … 5_1010.iso

/etc/apt/sources.list.d/devuan.sources (generated by running 'modernize-sources')

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur excalibur-security excalibur-updates
Components: main 
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

/etc/apt/sources.list.d/freesh.sources

X-Repolib-Name: GNU Linux-libre Freesh Repository
Enabled: yes
Types: deb
URIs: mirror://linux-libre.fsfla.org/pub/linux-libre/freesh/mirrors.txt
Suites: freesh
Components: main
Signed-By: /usr/share/keyrings/freesh-archive-keyring.gpg

That screenshot might be NSFW for some people.

If you're going from bookworm to excalibur, you're doing an upgrade at the same time as the migration, so it's probably a good idea to look over the upgrade instructions. One gotcha on upgrade is that you must install the usrmerge package before you upgrade.  I don't think it matters if your sources are pointed to bookworm or excalibur for that package. (I've done it both ways.)

Upgrade to Excalibur
https://www.devuan.org/os/documentation … -excalibur

Next paragraph in the release notes starts with:

Installer isos and live CDs for amd64 are available for download

And this section:

### Reduced support for i386

There is no i386 installer iso for Devuan 6 Excalibur, following Debian's
choice to remove their official i386 kernel and installer.

And if you look at the debian release notes it explains that you can run 32-bit in chroot or container.

I believe it's still possible to upgrade a 32-bit system. You won't get a new kernel, so if you have the kernel metapackage linux-image-686-pae you might need to remove it first. I'm not sure about that.

You can use a linux-libre kernel if you don't need proprietary (non-free) firmware.
see: https://dev1galaxy.org/viewtopic.php?id=7208

I gave up using fstab to mount nfs shares a few years ago. I think it was because of problems if the server or the client rebooted. I use autofs now. It auto-mounts the share when you access the share. Simple config desribed here: https://dev1galaxy.org/viewtopic.php?pid=58917#p58917

I use these options in /etc/export. It looks like I added 'sync' either in daedalus or excalibur. (I don't have a daedalus to check right now.)

(rw,sync,no_subtree_check,crossmnt)

You can use autofs to automount nfs.

Add this at the bottom of /etc/auto.master:

/mnt	/etc/auto.nfs

Create /etc/auto.nfs containing something like:

<share-name>    /path/to/<your-symlink-name>

Make the symlink and restart autofs:

ln -s /mnt/<share-name> /path/to/<your-symlink-name>
service autofs restart

- your-symlink-name can be the same or different from share-name.
- If you're already using /mnt for something else, you can mount the share somewhere else. Just make an empty directory to be used as the mountpoint.
- Don't use fstab for any part of this.

We no longer fork upower. The version you have installed is for ascii. One or more of the following should work.

apt install upower/daedalus

If that doesn't work, download the deb package and install it with dpkg.

apt download upower    #if you get the ascii version with this, then you need to remove ascii from sources.list or sources.list.d/

#you could also do this to download the right version:
apt download upower/daedalus

dpkg --force-downgrade -i upower_0.99.20-2_amd64.deb

We all know it's not really a downgrade, but apt thinks the one with the epoch is newer.

Try using qemu-system-x86_84. If you really have qemu-system-amd64, where did you get it from? I can't find it.

You might be able to sort it out by running

dpkg-reconfigure lightdm

as root. You'll also see if there's another display manager installed, and it will give you a choice of which one to use.

If it still doesn't work, make sure the lightdm service is set up to run. Either install and run sysv-rc-conf and make sure lightdm is set to run in runlevels 2-5 or run

update-rc.d lightdm defaults

Does startx work for unprivileged user?

Thanks once again for your test report. There are different sources.

Without a deb-src line for excalibur-proposed-updates, 'apt source slim' gives me slim_1.4.1-1devuan1.debian.tar.xz
and with that source I get slim_1.4.1-1devuan1+excalibur1.debian.tar.xz

deb http://deb.devuan.org/merged excalibur-proposed-updates main
deb-src http://deb.devuan.org/merged excalibur-proposed-updates main

More info: The upstream dev thinks we have the wrong solution, but he is currently unavailable to give us more info.

Here's the relevant commit: https://git.devuan.org/devuan/slim/comm … 86db1173ff

All better now.