ALSA is part of the kernel. The user space utilities are already installed.

If you need help configuring it see https://wiki.archlinux.org/title/Advanc … sound_card

Sorry OP, my posts in this thread are irrelevant — I failed to read through the thread properly before answering and didn't appreciate that you're trying to boot a USB stick rather than an installed system.

Apologies for the noise.

How are you starting Synaptic?

Which password are you entering? I think pkexec will expect the user's password so if you're entering the root password (as you would for the su command) then it won't work.

If the behaviour has changed recently then we should probably check your sources so please also post the output of

apt policy

That is the expected behaviour. UEFI systems use the EFI system partition to store GRUB's core.img (grubx64.efi) and the motherboard NVRAM to store the boot entries so there is no need to specify the target drive. The UEFI grub-install command does not expect a block device as an argument and will not recognise it if it is provided; the equivalent option for UEFI systems would be --efi-directory (pointing to the EFI system partition).

Did you try disabling Secure Boot? Devuan chimaera should support it but some motherboards require that .efi loaders be authorised in the firmware ("BIOS") settings first.

Other potential causes of a lack of UEFI variable support and ways to fix them are listed here:

https://wiki.archlinux.org/title/Unifie … le_support

What does that mean, exactly? What actually happens when you try? What do you see in the installer? Are there any errors? If so did you check TTY4 for the full message?

If the installer proceeds without error then what happens when you start the machine up afterwards? What do you see?

mutt

Check the logs.

Debian now runs on the M1:

https://twitter.com/alyssarzg/status/14 … 1058194436

The display driver works and will be added to the mainline kernel in due course.

EDIT: and the developer runs a dwm desktop. Nice.

Isn't their kernel installable in Devuan?

Remember to use their hardened malloc implementation too:

https://www.whonix.org/wiki/Hardened_Malloc

@Jakoline: I've just tested the Debian bullseye netinstall image and that doesn't seem to install rfkill if no desktop is selected in tasksel. Have you considered reporting this to Debian?

And for general reference:

The Devuan beowulf netinstall ISO includes a "Rescue Mode" available from the "Advanced Options" boot sub-menu — this can be used to open a shell in an installed system without needing to mess around with chroot (or arch-chroot(8)).

More details on this here: https://www.debian.org/releases/stable/ … 06.en.html

Is it wise to use wicd now that Python2 is obsolete? https://packages.debian.org/experimental/python3-wicd might be a better idea even if it's from experimental.

The error message is from insserv(8) so I think it's referring to a script in /etc/init.d/ (called "cgroups"). Do you have such a script and if so does it contain the LSB headers? See the first code block on this page for an example.

And note that your changes to /etc/os-release will be overwritten if the base-files package is updated. EDIT: actually APT might ask a confusing question about it instead. That's always fun when you're in a hurry...