To set some minds right in terms of relations between Debian and Devuan: The small Devuan team just replaces a minimum set of packages related to systemd by packages that support init freedom. The Devuan web page (accessible by a link on the top of this page) amongst other information also shows a list of banned packages. Only these are modified or replaced.

All the rest is a 1:1 copy of the Debian repo.

This is also true for Firefox. What isn't in the Debian repo can't be found in the Devuan repo, no matter if on cli e.g. by apt or in graphics mode e.g. by Synaptic.

This libhcrypto.so.4 has something to do with Heimdahl stuff. Maybe that's a hint ...

Can't exactly remember what I did several months ago when reading in some W98SE floppies with an USB floppy drive.

Some ideas:

Make sure you are in the floppy group.
Install mtools and dosfstools.

Then reboot and give it another try.

You should install fuse3. But you will have to remove jmtpfs, that conflicts with fuse3.

Yes it can.

Size: my suggestion is 1024 MiB to avoid any issues with strange EFI bios implementations that would like to use the ESP as storage for firmware updates. Minimalists call this way too large. The size is an insurance against the unforeseen.

Filesystem: FAT32/vfat is a must.

If no other ESP is present, create a new one.

If there is an ESP in place already, no need to create a second one. It will not be overwritten or getting damaged. You need to make sure its added in the list of partitions as ESP to tell the installer to use it.

There is one stumbling stone though. Debian and Devuan and if I am not mistaken at least Ubuntu/Mint do add a generic directory into the ESP for their distributions. E.g. Stretch, Buster, Bullseye or Bookworm all add a directory called "debian". Older Devuan releases do the same. You see the problem?

If you want a dual boot for Chimaera and Daedalus you have to do some post processing, or only the later installation is bootable. The solution is to do another grub-install from the booted system with the option --bootloader-id=devuan4 as I am using it. Use efibootmgr to set the boot order as you like.

This rework is not to 100% update safe. I have been through grub updates that did re-establish the generic directory. So I had to redo my specific grub-install.

HTH,

Will work perfectly fine.

When you are running with Secure Boot set to "Other OS" = Disabled in the Bios, you do not need this package. I do not use SB, I remove grub-efi-amd64-signed on all my efi installations. grub still works alright.

I am on Daedalus with backports kernel 6.6 currently.

Sure, should work. Have you rebooted?

If that doesn't solve the problem, please post the output of inxi -F

I done that on all my latest Devuan installations including Daedalus to be able to set up the graphical desktop my way. I use netinstalls and disable anything else but the standard system utilities in the sw selection, and do a reboot past the final steps including the grub install. Never had any issues, it simply worked. Independent from if I have network or not, on real HW or in a VM. The console should come up, sometimes when firmware is missing with not so nice graphics, but still readable. No Intel or NVidea involved though, pure AMD stuff.
Have you left out something, skipped an important step during expert install? What kind of PC we are talking about? efi or legacy install? What did you modify versus the procedure described here: https://www.devuan.org/os/documentation … all-devuan ?

I have something back in my mind that this problem maybe due to generating the file system with a brandnew kernel, and then trying to use it on an older distribution.

Before doing that make sure the cdrom entry is out of the way. Put a # in front of the line to uncomment it, or remove the cdrom entry completely.

Alternative on my Daedalus:

# apt list darktable
Auflistung… Fertig
darktable/stable 4.2.1-4 amd64

Anyhow, have a look at the right top of this web page. There are 5 links. Use Devuan.org and scan through the available information, it might be helpful for a beginner.

Can't imagine that POS does an installation without this essential package.

Maybe you simply need to use su - to get root access instead of simply su. The difference is the path.