Does your nvidia card support driver versions above 570.xxx.xxx? If so this is what I do.

sudo apt install linux-headers-amd64

wget https://developer.download.nvidia.com/c … -1_all.deb

sudo dpkg -i cuda-keyring_1.1-1_all.deb

sudo apt-get update

sudo apt-get install cuda-drivers

sudo reboot

instead of rebooting check auto-mute in alsamixer. It should be set to enabled. To open alsamixer just type alsamixer in a terminal.

That's great greenjeans. Isn't it amazing how alsa already has everything yet they spend years and lots of $$$$ on fixing sound in linux. Have you considered adding an option to use surround sound? maybe in the special version?

Tried this it worked well. Only bug I had was changing the brightness, if that's what the icon next to the speaker is. I tried lowering it and it crashed the panel. Everything else sound, browser etc worked no problems.

Thanks mate, I tried ya commands  SDL_AUDIODRIVER=alsa or STEAM_RUNTIME=0 and still no luck. Everything I've searched and tried so far has failed. It seems that it use to work with only ALSA systems but not anymore.

@Matlib Did you do any more work on this?

@brday I install from the base system and can't get anywhere near 160 MiB. Must be all the bloat I added.

Bummer. I haven't got any amd stuff on old or new hardware.

I install devuan with no desktop environment so there's no xorg. Then I install ntpsec, curl and gnupg. After that I install xlibre. This way you could try apt-mark hold xorg then install mate-desktop or mate-desktop-environment.

As for mesa-libgallium maybe you could try installing that before mate or apt mark-hold mate-desktop-environment if mates already installed then install mesa-libgallium.

I only ended up with no amd hardware by chance not choice and have had only good results using xlibre.

For wpa_gui I had to do this in /etc/network/interfaces

auto wlan0
iface wlan0 inet dhcp
             wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

then sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev
update_config=1
p2p_disabled=1

@fsmithred  If you ran the install-packages.sh it has grub-pc included in it, if you didn't I'm not sure. I've finished with this now. It was good fun. I've added the updated tar file on sourceforge and there's a build-readme as well. https://sourceforge.net/projects/unoffi … box/files/

I set it up to use the username and password of the machine taking the snapshot. So for example I can setup a system the way I want with a username live password live (it uses place_holder for whatever anyone wants to use), install the required packages for refracta and calamares, then from refracta-calamares-setup run scripts/install-config.sh, then run scripts/build-iso.sh and it's all done.

Calamares removes itself once it's finished the installation from the live usb. I also configured calamares to keep home/$USER/.config and home/$USER/.local, this can be added to or removed.

Anyone can change the logo, images for slideshow, number of images used, name of the installer or iso etc. And again CHAT BOTS have been used to write the scripts.

Refracta snapshot made this really easy so thanks again.

@greenjeans Possibly, they tried installing on a new desktop and an old laptop. I did tell them this and to look in the bios for options to disable anything UEFI boot, secure boot. If you used something simple like calamares, with a good cleanup script all the crap it installs could be removed leaving vuudo just the way you intended it to be.

@fsmithred When I used refractasnapshot I had the user set to human and EFI enabled. When I used the live usb the user name and password were the same as the user name and password from the machine that took the snapshot. Starting calamares it always asked for user name and password and that was the one from the machine that took the snapshot. I tried getting the chat bots to make calamares start with out putting in a user name and password but it didn't work so I just moved on using the one from the machine that took the snapshot.

During the install process with the calamares gui I put in user name test and password 1234 and when booting into the installed system it logged in with test and 1234. I did not install any of these  cracklib_runtime and reinstall libcrack2. I am not a dev but I'm sure you don't have to do this "I would need to rearrange the build process of the iso to do it the debian-live way". All i know is it works with what you already have.

Grub was the final hurdle I had before the installer finished with out error. If you look at the bootloader.conf I used it's in the tar file on sourceforge I will not post it here given the love for ai slop. But this worked. I would suggest looking at all the module files in refracta-calamares-setup/config/etc/calamares they follow what the calamares source code says. When I boot the installed system I get a blue screen with the Devuan logo Devuan GNU/Linux, Advanced options for Devuan GNU/Linux and booting in countdown.
.
You guys make great stuff and with windows 11 people are trying out your work and want to use it. If you want people to use your work try and think like them and not a dev

.Edit. I only checked the user name and password I used in the Calamares installer and the installed system logs in with both that and the user name and password from the machine that created the snapshot

There's a readme here on what I'm doing https://sourceforge.net/projects/unoffi … box/files/ I just made it to show you and It does not work yet, but i'll get there. Also like fsmithred said it's bloated but I think it would be good for vuudo