I missed you in IRC by a few minutes. There's a 5.3 kernel in beowulf-backports. And there's a refracta live-iso I made with that kernel for testing purposes. It's here: https://get.refracta.org/files/experime … 5_0440.iso

To install a backports kernel:
Add this line to /etc/apt/sources.list, apt-update, find the kernel you want and install it.
deb http://deb.devuan.org/merged beowulf-backports main

Run:

apt -t beowulf-backports install linux-image-5.whatever

reboot. The highest version kernel will be the first choice in the boot menu.

Yes.

Yes, I added a subvolume option. This should not affect grub. I used subvolid, but you could also use the path to the subvolume.

To get the subvolid, run btrfs subvolume list <path> where path is the path to the mounted luks volume.

# btrfs subvolume list /mnt 
ID 257 gen 37 top level 5 path devuan/rootfs.subvol
ID 258 gen 20 top level 5 path devuan/homefs.subvol

On or around line 1137 of /usr/bin/refractainstaller:
mount -o subvolid=257 "$install_part" /target ; check_exit

Line 1163:
mount -o subvolid=258 "$home_part" /target ; check_exit

I did it in the middle of the installation. There's a pause when it's ready to install the bootloader, so that you can go to another terminal and modify files on the target or even chroot the target. Then go back and tell the installer to do the bootloader. All I did was add the subvol option. You might use more or different options.

/dev/mapper/sda3_crypt	/	btrfs	defaults,noatime,subvolid=257	0	1
/dev/mapper/sda3_crypt	/home	btrfs	defaults,noatime,subvolid=258	0	2
/dev/sda2	/boot	ext2	defaults,noatime	0	1
/swapfile	none	swap	sw	0	0

I got it to install with the live installer if I do a lot of manual fiddling with it. But I can't get it to boot, even with a separate /boot partition.

See if you can get the regular installer to work without formatting as I described above. If that doesn't work, we can come back to a more manual approach.

Edit/Update: I can't get it to work with the installer isos, either. I tried ascii-2.1. Expert install, check cyptsetup at the extra installer components list, drop to a shell when it reaches partitioning, try to open the encrypted volume with cryptsetup, and the command is not found. (the debs are on the media, but they haven't been installed at this point.)

If I try to select the btrfs partition to use as btrfs, it tells me that no root has been selected. Looks like you have to do it the way it was described in the other thread (install to a temp dir and then rsync it all into place.)

When you get to the partitioning phase in the installer, if your subvolumes are listed, you should be able to highlight one, press enter, and get to a screen that shows options for that parititon - use as (filesystem type), format, mountpoint, etc. If you highlight a line and press enter, you can edit that line. For the format line, pressing enter will toggle yes/no.

When you're at the screen that lists your partitions, there may be an upper-case F or K on each line. F means the partition will be formatted, K means keep the current filesystem (don't format).

Meanwhile, I will try to reproduce your configuration and see if I can do it with the live installer.

Yup. As soon as we get the installer isos right, we'll let you play with them. Meanwhile, I switched my main box to beowulf.  (Bye bye Jessie. I'm sorry it didn't work out as we first expected, but I had nothing to do with that. I kept you as pure as I could.)

These isos were made with refractasnapshot, which has a pretty extensive rsync excludes list and a high compression on the squashfs. Before that, most of the packages are installed without Recommends. The initrd is xz compressed - that saves a few MB.

I started with the no-X isos I made with live-sdk, installed onto virtual disks, added software and customized some stuff and then made a snapshot. Until ascii, these things fit on a CD.

I added haveged to Refracta isos so that it wouldn't take five minutes to boot while new ssh host keys were being made. The live iso makes new keys on every boot so we all don't have the same host keys. I didn't think it was needed for an installed system, but I could be wrong.

If you do nothing at the boot menu, you will get the first item, which is desktop-live i386. The system is set for automatic login, so if you got a login screen, something is wrong.

What kind of instructions would you like? There's not much to say. Just dd the image to a usb stick, boot the stick and choose a system. If you want to install one of those systems, it's probably better to download one of the 2.1 isos, because they are newer.

I don't forsee any immediate changes. Yesterday's vote leaves us in a slightly better position than before. There was no commitment at all to work with us. Now there is.

It wasn't my favorite proposal, but it's something we can work with. It could have been worse.

I think the first thing to try would be the backports kernel. That's easy to do or undo, and it won't hurt anything. I'd try it with the ascii version of the xserver package.

The only difference I can find between the jessie version and ceres version of xserver-xorg-input-wacom is in the wacom.conf file. There's no difference between the ascii and ceres versions of 70-wacom.conf.

The udev rules file is the same (jessie/ceres), and the pkgconfig file was moved and is only different in the version listed within.

(jessie) -xserver-xorg-input-wacom: /usr/share/X11/xorg.conf.d/50-wacom.conf
(ceres) +xserver-xorg-input-wacom: /usr/share/X11/xorg.conf.d/70-wacom.conf

Sorry I don't know what to do with this information, but here are the diffs.

$ diff -u 50-wacom.conf 70-wacom.conf 
--- 50-wacom.conf	2019-12-26 11:19:49.159183000 -0500
+++ 70-wacom.conf	2019-12-26 11:21:26.183183000 -0500
@@ -1,24 +1,69 @@
+# Some of the below input classes appear 3x times, once for each of
+# "tablet", "touchscreen", and "touchpad" to ensure that the Wacom
+# driver is not accidentally bound to other types of hardware that
+# Wacom has made which are not handled by the wacom driver (e.g the
+# Wacom Bluetooth Keyboard)
+#
+# https://sourceforge.net/p/linuxwacom/bugs/294/
+
 Section "InputClass"
-        Identifier "Wacom USB device class"
+        Identifier "Wacom USB tablet class"
         MatchUSBID "056a:*"
         MatchDevicePath "/dev/input/event*"
+        MatchIsTablet "true"
         Driver "wacom"
 EndSection
 
 Section "InputClass"
-        Identifier "Wacom PnP device class"
-        MatchPnPID "WACf*|WCOM*|WACM*|FUJ02e5|FUJ02e7|FUJ02e9"
+        Identifier "Wacom USB touchscreen class"
+        MatchUSBID "056a:*"
         MatchDevicePath "/dev/input/event*"
+        MatchIsTouchscreen "true"
         Driver "wacom"
 EndSection
 
 Section "InputClass"
-	Identifier "Wacom class"
+        Identifier "Wacom USB touchpad class"
+        MatchUSBID "056a:*"
+        MatchDevicePath "/dev/input/event*"
+        MatchIsTouchpad "true"
+        Driver "wacom"
+EndSection
+
+Section "InputClass"
+	Identifier "Wacom tablet class"
+	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
+	MatchDevicePath "/dev/input/event*"
+	MatchIsTablet "true"
+	Driver "wacom"
+EndSection
+
+Section "InputClass"
+	Identifier "Wacom touchscreen class"
+	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
+	MatchDevicePath "/dev/input/event*"
+	MatchIsTouchscreen "true"
+	Driver "wacom"
+EndSection
+
+Section "InputClass"
+	Identifier "Wacom touchpad class"
 	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
 	MatchDevicePath "/dev/input/event*"
+	MatchIsTouchpad "true"
 	Driver "wacom"
 EndSection
 
+# Serial Wacom devices should always be one of tablet, touchscreen, or
+# touchpad so we can safely get away with just one match section in
+# these cases
+Section "InputClass"
+        Identifier "Wacom PnP device class"
+        MatchPnPID "WACf*|WCOM*|WACM*|FUJ02e5|FUJ02e7|FUJ02e9"
+        MatchDevicePath "/dev/input/event*"
+        Driver "wacom"
+EndSection
+
 Section "InputClass"
 	Identifier "Wacom serial class"
 	MatchProduct "Serial Wacom Tablet"
@@ -56,4 +101,3 @@
 	Driver "wacom"
 	Option "Button2" "3"
 EndSection
-

"Install bootloader" would have been the right choice.
https://devuan.org/os/documentation/ins … dl18.2.png

You can either reinstall or else boot the live, chroot the installed system and run grub-install && update-grub

Here's the link to the full install guide:
https://devuan.org/os/documentation/ins … e-gui.html

My recommendation is not impartial, and I won't try to debug unetbootin. Use my software to make a multi-boot usb.
refracta2usb download - https://sourceforge.net/projects/refrac … b/download
Instructions (at least read the Quick Start!) - https://refracta.org/docs/readme.refracta2usb.txt

It uses isolinux/syslinux. If you want grub bootloader on it, we can change it to that later.