First thing I would do is look behind the furniture for an ethernet outlet.

If you tried the minimal-live iso, it has firmware already installed. Run setnet.sh to configure wireless.

I don't know anything about your model of laptop, but you might want to take a look at this to see if you have any of the same problems: https://dev1galaxy.org/viewtopic.php?id=15

XFCE gets pulseaudio through a chain of Recommends. It's not a hard dependency, and it's easy to avoid it. Just install without recommends. I haven't checked, but it's probably the same for the other desktops.

You would still need a /devuan repo to get the packages we modified, and you would probably need to pin all those packages to the devuan repo. I hope you're just thinking of this as an experiment.

You either need to install elogind or edit Xwrapper.config to allow X to run as root. See the section on startiing X from console in the release notes:
https://files.devuan.org/devuan_ascii/Release_notes.txt

The fix appears to be the same, but the file is not. The last diff I posted was between the copy
of cryptdisks-functions in the mx package, which is named same as the original file in beowulf, against the cryptdisks.functions file from ascii. I didn't notice the different filenames when I ran the diff because I used tab-completion.

The diff between the mx version of the file and the original file in beowulf, looks a lot different. I haven't examined it closely, but it's obviously not the same file. It's too big to copy the whole thing from a terminal, so I pasted it here:
https://termbin.com/xle7
This is really the diff between cryptdisks-functions in beowulf and cryptdisks.functions+patch in ascii
Unless antix or mx is still using cryptsetup 1.7, they should update their package to use the file from cryptsetup 2.1. for buster.

They also didn't include the fix for lvm. Here's what I changed in beowulf:

diff -u cryptdisks-functions.orig-2.1.0-5  cryptdisks-functions.patched 
--- cryptdisks-functions.orig-2.1.0-5	2019-08-01 22:24:09.400000000 +0000
+++ cryptdisks-functions.patched	2019-07-19 02:03:11.972000000 +0000
@@ -179,7 +179,18 @@
 
 # Removes all mappings in crypttab
 do_stop() {
+
+    local vgs vg
+
     dmsetup mknodes
+       if [ -x /sbin/lvm ]; then
+        vgs="$(/sbin/lvm vgscan | sed -n '/"/s/^.*"\([^'\'']*\)".*$/\1/p')"
+         if [ -n "${vgs}" ]; then
+          for vg in ${vgs}; do
+           /sbin/lvm vgchange -a n ${vg} >/dev/null 2>&1 
+          done 
+         fi
+        fi
     log_action_begin_msg "Stopping $INITSTATE crypto disks"
 
     crypttab_foreach_entry _do_stop_callback
@@ -187,7 +198,7 @@
 }
 _do_stop_callback() {
     local i rv=0
-    for i in 1 2 4 8 16 32; do
+    for i in 1 2 ; do
         remove_mapping "$CRYPTTAB_NAME" 3<&- && break || rv=$?
         if [ $rv -eq 1 ] || [ $rv -eq 2 -a $i -gt 16 ]; then
             log_action_end_msg $rv

I tried it with a small install (just standard system utilities) and a big install (kde). Neither one was easy, but it is possible. I won't attempt to give you instructions. Even if I looked at my command history, I wouldn't be able to tell you what worked and what didn't.

Don't try it on a system you care about. Not now, anyway.

Confirmed. No boot menu in uefi boot. Must be a grub.cfg missing. Next iso should be better.

The TDE wiki has a page for installing on devuan:
https://wiki.trinitydesktop.org/Devuan_ … structions

Looks like ascii has both of those versions. Am I looking at the wrong package?

$ apt-cache policy emacs25
emacs25:
  Installed: (none)
  Candidate: 25.1+1-4+deb9u1
  Version table:
     25.1+1-4+deb9u1 500
        500 http://deb.devuan.org/merged ascii/main amd64 Packages
        500 http://deb.devuan.org/merged ascii-security/main amd64 Packages

$ apt-cache policy emacs24
emacs24:
  Installed: (none)
  Candidate: 24.5+1-11+deb9u1
  Version table:
     24.5+1-11+deb9u1 500
        500 http://deb.devuan.org/merged ascii/main amd64 Packages
        500 http://deb.devuan.org/merged ascii-security/main amd64 Package

If you're getting a grub prompt instead of a normal boot menu, the easiest thing to do is use that command line to boot the installed system. Then you can run update-grub to generate a new boot menu.

grub prompt looks like this:

grub>

If you iinstalled the system on /dev/sda1, you would use the following commands:

set root=(hd0,msdos1)
linux /vmlinux ro root=/dev/sda1
initrd /initrd.img
boot

Note: it's possible your computer will see the usb as the first drive. In that case, (hd0,msdos1) would need to be changed to (hd1,msdos1). You can use tab-completion to figure it out. Type set root=(hd0 and press TAB (maybe twice) and it will show you the partitions on that drive.

Once you've booted the system run update-grub

I used the one on this page, but I think it's the same one.
http://pkgmaster.devuan.org/devuan/dist … s/netboot/

The kernel in my beowulf is dated July 19. The mini.iso is dated June 27. It might not work now. Normally when that happens, you can get part way through the installation and then get a message about kernel modules being wrong. You didn't get that.

for the Jun 27 amd64 mini.iso I get the following. Check yours to see if it was a bad download.

$ sha256sum mini.iso 
85a227cb9bdf79352851195ed7e8c78c3e649dbc4b5f59a8d6232da62ef2fed9  mini.iso

Yes, devuan mounts the efi partition at /boot/efi. The problem is that grub is looking for efi/EFI/debian but efi/EFI/devuan was created. If someone wants to keep the -signed package, they need to run grub-install --bootloader-id=debian in chroot or with whatever option grub uses now to point to another target. (--boot-directory or --root-directory?)

And you don't need to specify /dev/sda when running grub-install on uefi. It knows to put the bootloader in the efi partition.

Also, someone is working on a fix for this in devuan.