You are not logged in.
I have no experience with machines with two graphics engines like your laptop. Can you switch to the AMD card in the bios by chance?
No missing firmware messages during the update-initramfs any more?
Have you got firmware-misc-nonfree installed?
# apt list firmware-misc-nonfree
Oh, copy & paste problem, sorry for that. When having a very close look to my command I saw that for some reason the first "–" before the "u" is a long hyphen instead of a normal dash "-". Some damn auto-correction mechanism ...
Just replace the long hyphen by a dash. Then it should work.
I would say forget about the old fglrx driver. Its outdated, no more maintained and won't work with current kernels and xorg versions.
Which release are we talking about? Daedalus? Based on the kernel that should be correct. Which graphics card is involved?
Make sure that you have non-free and non-free-firmware enabled in your sources.list. Then:
# apt update
# apt install firmware-amd-graphics xserver-xorg-video-amdgpu
# update-initramfs -u -k all
Use the Download link on the top of this page. Select devuan_daedalus. Then select installer_iso.
There you got the choice. The 4G one is the Desktop DVD.
No idea about Gnome, I am a Cinnamon user. Can't stand Gnome.
Well, if you don't want to listen to other users advise, you could use the forum's search function. Here is a thread that might help you: https://dev1galaxy.org/viewtopic.php?id=5407 that bring some other mixers into the game ...
Have a look at geany
Thats normal. Without a mixer the dialogue in the control center is incomplete.
Your problem is that Gnome like other DEs does not supply a mixer on its own.
pavucontrol, alsamixer-gui are valid options to solve the issue.
RE: netinstall and upgrades, I was assuming the kernel and infrastructure that would be initially installed was whatever was on the netinstall iso? And since there's been a kernel upgrade since I first downloaded and installed Daedalus I thought that might be the case with the netinstall as well.
So basically the netinstall is just the vehicle, and all the files you will install on the machine will come not from it but directly from the repo?
All depends on how you install.
If you do an offline install or deny using a mirror, you can just install whats on the iso, and the versions that are available when the iso was being built.
When you have a network connection and you have selected a mirror, you can install everything thats in the repo, and you are getting an update of the files installed from the iso free of charge.
I own a small wireless mouse by Trust, item no. 20322-09. It runs on 2 AAA cells. The Bluetooth? dongle is stored inside the mouse when its not used. This mouse has an on/off switch.
I am mainly using it on my laptop. It worked out of the box with Chimaera and Daedalus, in both cases LightDM/Cinnamon as DE. No special action required. I can start the laptop, and plug in the mouse when I am logged in. It works.
120 GB easily is enough.
VBox works fine for me, currently I am on Daedalus/kernel 6.5 with 7.0.12 from virtualbox.org's repository. Every now and then there are teething problems with new kernels or graphics, but I would claim its perfect for my production use, i.e. pass through of USB devices and shared folders.
I started using VBox with Squeeze if I remember correctly, and I haven't got any issues with "disk full" or access problems to USB drives.
Well, I have always avoided the default of using my home drive to store the VMs. From the beginning I have had a separate partition or drive for them. Its easy to configure in the options of the Virtualbox Manager.
It's tricky when you install debian's packages into devuan. Might work, but might not also.
There is nothing tricky about Debian packages in Devuan. What is offered in /deb.devuan.org/merged coming from Debian works in Devuan.
Devuan is Debian minus systemd, refer to the list of banned packages. The rest is pure Debian! Devuan just makes sure that systemd init is fully replaced by sysvinit and all the others offered, replacing what is required as base for the rest.
How about users and groups? Should the normal_user belong to some group in order to be able to use usb-devices?
Yes. The user needs to be in the vboxusers group. This normally is established during installation of the main package.
And attention to the extension package. Its version has to match the main packages version.
The normal installer can. I never use the live media for installation.
Can't tell you how exactly the Debian build works, I'm not using it. In any case under depends there is a reference to virtualbox-dkms or similar, I think this might do the job in the background.
What I always do nowadays: I use the netinstall just to install the basic system utilities, I do not install any DE, they are getting ticked off, or I do not use a mirror or pull the LAN cable, all the same effect.
Then I go and install xorg, lightdm and mate or cinnamon with the option --no-install-recommends. This bring a bare desktop. Then I add what I think I will need with apt.
Its enough to install the Virtualbox package. Mostly everything required is installed automagically. Exception: you will need build-essential, dkms and headers to build the VBox modules, and you have to add 3 lines to /etc/modules.
You are right, there are VBox scripts in /etc/init.d. In my long experience I never had to fool with these scripts in any way.
To make sure the latest version is on the stick finally? And that does not change the issue with the Daedalus media?
Updated my Ventoj to 1.0.96 and also tried the server and the desktop iso, all the same.
I guess distros with systemd work in a sense that i can run firefox and vlc and virtualbox and stuff like that.
But i'm not fully convinced it is a way to go. On the other hand i sometimes wonder if all those scripts related to sysvinit are absolutely necessary, could you do things another way instead? Make init or inittab do the jobs of those rc-scripts somehow?
There is no need for any init script for simple applications like firefox(-esr), libreoffice, vlc, virtualbox ....
Virtualbox requires systemd, if I recall correctly... that I know of...
That is not correct. I am using VBox now for so many years, I can't really tell how long. And I have always used the package supplied by https://www.virtualbox.org/wiki/Downloads. On Devuan no issues with systemd all along from ASCII to Excalibur.
LightDM is a good choice. I am using it on Mate or Cinnamon since many years now.
May I add a few lines (on Ventoj 1.0.94 from July this year):
What snork describes is what happens with legacy boot of Ventoj/Devuan.
All in efi mode, netinstalls:
5.0.0 normal mode I just get an _ and have to use the Reset button.
5.0.0 grub mode: no bootfile found for efi
5.0.1 normal mode: the first menu comes up ok, can select expert install, end in the mount cdrom scenario described before.
5.0.1 grub mode: have to repeat the test, can't decipher my scribbling no bootfile found for efi
Strangely enough grub mode produces an efi error.
An old preview dated 220523 in normal mode boots to the Choose Language screen, same as older releases. Same for Debian 12.1. Others like gparted life 1.5.0-1, mint 21.1 ... work fine.
Edith: added the 5.0.1 grub mode test
Well, currently neither Bookworm nor Daedalus (5.0.0 and 5.0.1) will run from a Ventoj stick ok. There have been changes in the graphics that are incompatible with Ventoj.
I have seen a claim that using the grub-mode might be a workaround, haven't tried it yet.
Older versions are fine.
Edith: My mistake, confused Bookworm behaviour on Ventoj with boot issue in Virtual Box and efi mode. Bookworm works fine from Ventoj.