@fchk, if a 5.0.2 ISO with proper GPT saw the light of day, would you prefer it being netinstall, server or desktop?

I'd prefer desktop.

Thanks.

fchk

fchk: The supermicro case is particularly curious. Same make and model USB stick for both Debian and Devuan images? Booting from same USB port?

These servers have an Aspeed IPMI controller for remote KVM (basically hardware VNC), and you can upload an virtual Floppy or CDROM image. The IPMI processor is an USB device to the PC and then acts as an USB Floppy or an USB CDROM drive.

Devuan 5 is the only distro I've ever had problems with. Neither Debian or Devuan 3 and 4 had any problems.

Frank-Christian

fchk: The supermicro case is particularly curious. Same make and model USB stick for both Debian and Devuan images? Booting from same USB port?

hellou1: For the i5 with intel sound and video drivers - on a similarily old laptop I've had to manually mess with firmware to get things to work with Debian 11 and prior - but if your issue is similar that case would probably be an issue outside of the scope of the installer.  Daedalus worked right away but this was a different install method. I will double check a full Deadalus ISO install though to see.

I will report back.

It may be something to do with the above security 'features' - maybe try removing 'secure boot', or possibly that TPM module(?).

Secure Boot is disabled. Debian 12.1 just installs fine.

Frank-Christian

Security
Hardware    

    Trusted Platform Module (TPM) 2.0
    Silicon Root of Trust (RoT) – NIST 800-193 Compliant

Features    

    Cryptographically Signed Firmware
    Secure Boot
    Secure Firmware Updates
    Automatic Firmware Recovery
    System Lockdown

It may be something to do with the above security 'features' - maybe try removing 'secure boot', or possibly that TPM module(?).

What's worse: I've got now the first batch of servers on my desk that don't have BIOS boot at all any more. These machines are pure UEFI machines that don't even have legacy option roms or CSM support any more. They absolutely need a proper GPT partition map in order to boot at all. I'm totally screwed there.
Example: https://www.supermicro.com/en/products/ … 0d-8c-fn6p

I wonder why there is a problem anyway. Debian Bookworm does it right, so Devuan could just copy the Debian procedures verbatimly 1:1, without having to fix Syslinux etc. Or just do it like the 4.0.0 release media - they do work.

Frank-Christian

Successful efi installation with Acceleration - Paravirtualisation = none.

2) use partition UUID or filesystem labels.

Alsa on boot with dmesg |egrep -i "alsa | snd :
[    1.550730] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    1.550951] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver

and kernel modules loaded by Alsa with lsmod | grep "^snd" | cut -d " " -f 1 :
  snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
snd_soc_dmic
snd_sof_pci_intel_tgl
snd_sof_intel_hda_common
snd_sof_intel_hda
snd_sof_pci
snd_sof_xtensa_dsp
snd_sof
snd_sof_utils
snd_soc_hdac_hda
snd_hda_ext_core
snd_soc_acpi_intel_match
snd_soc_acpi
snd_soc_core
snd_compress
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
snd_hda_codec
snd_hda_core
snd_hwdep
snd_pcm
snd_timer
snd

On Debian 12 sound worksfine.

2)
On intel i5 7th generation machine:
I think delgado is right with his assumption and the nvme has a sata  interface, laptop is about 7 years old. Model name is HFS128210A

Again, Debian 12 has no problem with naming, nor does Devuan 2, 3, 4.
I use Devuan since Vs 1 on that laptop

Best regards hellou

2. How come your nvme drive is not named /dev/nvmen0?

2. on an intel i5 7th generation machine, the installation stops right at the beginning with "kernel panic".
The laptop has 2 hard drives. one nvme with 128gb and one ssd with 1tb.
According to the bios, the following naming:
HDD0 = SSD
HDD1 = nvme

in the installation programme the following naming:
/dev/sda = SSD
   /dev/sda1 = /home
/dev/sdb = nvme
   /dev/sdb1 = /boot/efi
   etc.

in the running system with lsblk the following naming:
/dev/sda = nvme
   /dev/sda1 = /boot/efi
      etc
/dev/sdb = SSD
   /dev/sdb1 = /home

Devuan 2,3,4 had no problems with this naming, neither did Debian12.
I have no idea what is going wrong.
could you help please?

Note that the updated Devuan daedalus installer ISO set 5.0.1 now also handles the use case of booting from CDROM on UEFI.

The issue indeed was that the boot loader got confused about the iso9660 block size (2k) differing from the expected block size (512) for the EFI filesystem. To fix that we forked syslinux, added a corrective patch and published to Devuan experimental. The patched software was next used for building the updated ISO set.

Very cool! Thank you for the heads-up, Ralph.

The issue indeed was that the boot loader got confused about the iso9660 block size (2k) differing from the expected block size (512) for the EFI filesystem. To fix that we forked syslinux, added a corrective patch and published to Devuan experimental. The patched software was next used for building the updated ISO set.