Just tried it on my Chimaera box (Arch and Beowulf in parallel installations): Adding that line to /etc/default/grub does not make any difference on efi installations.

rolfie

Libreoffice has dropped Type1 font support a while ago. You need to find replacements, like ErlerDingbats.ttf instead off ZapfDingbats.

rolfie

Addition to my remark in post #7: The Secure Boot mechanism in Debian & Devuan is fixed to support Debian with a fixed entry called debian in the efi-variables called efivars. The installer (no matter if Debian or Devuan) installs 5 files in this directory, two of them being the already mentioned shimx64 and the grubx64. As explained shimx64 is meant to be starting the SB mode but also can start the non SB mode, grubx64 the normal mode. Per default, shimx64 is written into the starter for the efi mode. shimx64 seems to have issues when the base directory isn't called debian.

These boundary conditions cause problems when you want to set up an efi multi distribution setup as you have. I been through all the problems with this, here is my cook book. I have set up my current workstation (AMD X570, Ryzen 3700X, Sapphire xt5500 graphics) 18 months ago with Arch, Beowulf and Chimaera. Initially Beowulf was the main working spot, early summer this year I moved to Chimaera for daily work.

1.) Disable Secure Boot in the Bios and delete all signing keys.
2.) No CSM, pure EFI setup.
3.) Install the distro, reboot, setup sources.list ....
4.) Remove SB files: apt remove grub-efi-amd64-signed
5.) Reinstall bootloader into individual directory (only installs grubx64), example for Beowulf: grub-install --bootloader-id=devuan3 --no-uefi-secure-boot
6.) Check setup with efibootmgr: efibootmgr -v
7.) Cleanup /boot/efi/EFI: remove residual files from directories called debian and devuan.
8.) Cleanup efivars with efibootmgr: efibootmgr -b 000x -B

Set the boot order to the desired option with efibootmgr, or use the Bios Boot Override to boot one of the other possible options. All my 3 options are clean, os-prober never gave me such an option. I like it this way, since I normally boot one distro for working purposes.

My opinion to the automatic partitioning: when I read about all the issues with /boot being too small /root being to small in various Debian/Devuan forums and see what the SW is doing there, I must say: Forget it, that was ok 10 15 years ago, and has not been adapted in any way to today's disk sizes. It sets up sort of a bare minimum size that very often struggels when you add a kernel or a bit more than the bare minimum SW. I am used to use only manual partitioning, even in a VM, even if it is a bit more cumbersome. I usually get what I want and never ran into partition too small type of problems.

HTH, rolfie

Very simple: firefox-esr is not a genuine Devuan package, it is a Debian inheritance.

Also SLIM is no more maintained since 7 or 8 years now. Its sort of deprecated. Lightdm is working fine (for me at least).

rolfie

Well, different approach. I first want to try if I can get my approach to work. Thank you anyway.

rolfie

What for? Your approach isn't useful. Delete that line(s) and you're done.

rolfie

Try to replace slim (no more developed) with lightdm. I am running that on a 3700X.

rolfie

I am using openrc since ASCII. Works fine.

My first encounter with runit in a virtual machine a while ago was frustrating. Didn't realy work. Though there are people that are using it with success now. Maybe its time for another try.

rolfie

You have to define the shared folder in the VBox Manager and then you need to mount it within Devuan. Refer to VBox manual.