1. On devuan you have to edit /etc/pulse/client.conf.d/00-disable-autospawn to get sound.
On Refracta, that's not an option because pulseaudio is not installed. Sound works out of the box in most cases.  What does aplay -l show? Is the hardware too new for the debian kernel?

2. Not enough info to diagnose the problem. Check the log. Maybe delete the work directory if you're saving it between runs. Maybe something got mangled there and it's not getting cleard on subsequent runs.

In English, the name changed from Preferred Applications to Default Applications, and in the Settings manager, it got moved from the Personal section to the System section.

I had to upgrade my ceres to get 4.16 and xfce4-settings was held back to 4.14. At that point, Preferred applications was missing, but I don't know if Default applications was there. I upgraded xfce4-settings to 4.16 and restarted the destkop before I noticed it.

Here's one with backports kernel (kinda old one now) and wireless firmware already installed for testing new hardware. It's not the full mix - openbox, lxpanel, not a lot else.
https://get.refracta.org/files/experime … 5_1323.iso

Update: Here's a newer one with 5.9 kernel.
https://get.refracta.org/files/experime … 9_0205.iso

You got this output for the line that says losetup ${LOOPDEV} $img but there's nothing for $LOOPDEV in the output. "No such device." The error also shows up in the first lines of the output where it shows that cat failed and LOOPDEV is empty.

+ losetup test.img
losetup: test.img: failed to use device: No such device

I think you need to define LOOPDEV after you run 'losetup -f'.

crypt_create () {
        losetup -f > /tmp/nextloop
        LOOPDEV=$(cat /tmp/nextloop)
        losetup ${LOOPDEV} $img
        cryptsetup luksFormat $img
        cryptsetup open $img cryptfs
        mkfs.ext4 /dev/mapper/cryptfs
}

Thinking about how that will expand is making my head hurt. Wouldn't $1 = 'if=/dev/urandom'? And so on...

I like to redefine positional paramaters at the beginning of the script to give them meaningful names and to make sure I know what they really are.

outfile="$1"
blocksize="$2"
blockcount="$3"

dd if=/dev/urandom of=$outfile bs=$blocksize count=$blockcount iflag=fullblock

Then call the script with

myscript.sh value.img 100M 1

You only need one line. There's no chimaera-updates or chimaera-security until it goes stable. Leave those commented out for now. Also comment the third-party repo for the upgrade. The deb-src lines are only needed if you want to rebuild source packages.

I did an upgrade from beowulf to chimaera back in July. There were a few tricky spots. I'll leave you my notes. You will probably run into some different tricky spots, so do not follow these directions exactly. They are only here as an example. Also, search this forum for other accounts of upgrading to chimaera.

HoaS: I was referring to this part of the man page:

Your example worked. I was not putting the command inside a file. Isn't there a way to run the command from the command line?
This works:

at now + 1 minute -f testfile

This does not work:

at now + 1 minute echo "hello"

Maybe. I just did 'apt-cache search IWL4965' and it showed firmware-iwlwifi.

grep for just 'iwl' and they can all show up.

I'd like to rule out eudev as the source of the problem before anything else is changed. If so, there's a fix in beowulf-proposed-updates. https://bugs.devuan.org/cgi/bugreport.cgi?bug=483

That version is no longer in the repo. Run apt update to update your package cache and try again. You should see linux-libc-dev_4.19.160-2

Yes, that's what I remember, and it stopped doing that for me earlier this year. I modified refractainstaller to account for that. The modification involved uncommenting one line which I had commented out in the past because the user was being asked twice where to put the bootloader.  Today, it's asking me again.

The problem with the 3.0.0 iso is that the boot partition isn't getting mounted correctly for grub-install. I was able to get it to work by manually mounting it right before installing the grub-pc package. But that does not explain why the attempts to fix it in chroot didn't work for OP. Everything was mounted correctly there. I'd have to go back and read everything again to be sure, but maybe there was a problem with mis-match of grub packages between the iso and the repo.

I just did a successful install with a preliminary 3.1.0 iso I made for testing before actual point-release. It works. I do get asked twice where to put the bootloader. I also get a warning before the boot menu, because it can't find the theme. Press any key to continue, and it works.
Here's the link for the test iso.
https://get.refracta.org/files/experime … p-live.iso
sha256sum: bf477a3c0dc27866509407fde670d8fa0b903296effef7f67c2222a48fd9eb2a

You can either remove the live-tools package or use the modified name for the command.

update-initramfs.orig.initramfs-tools -u -k all

Instead of mkinitramfs, you can use update-initramfs -u in the chroot. It will rebuild the initrd.img for the running kernel. If you want to build for a different kernel, use update-initramfs -u -k <kernel-version> or update-initramfs -u -k all