MX Linux Forum

as I said
do not install nvidia before installing vbox
works fine.

This means nothing to me.

Critically read the error message that was presented.

Are the VirtualBox kernel modules loaded? If not, why one? To check:
lsmod | grep vbox
You should see:
$ lsmod | grep vbox
vboxnetadp 28672 0
vboxnetflt 32768 0
vboxdrv 450560 2 vboxnetadp,vboxnetflt
If you don't, look for error messages ...

kris@mx:~
$ sudo /sbin/vboxconfig
[sudo] password for kris:
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems ...

new build - why does everything not work??? :bagoverhead:

Screenshot_2023-08-30_22-53-22.png

System:
Kernel: 6.4.12-1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1
BOOT_IMAGE=/boot/vmlinuz-6.4.12-1 ...

content deleted by me.

content deleted by me

This post has been redone.

At some point in the process, the "normal" sound of a .wav played may change - no idea why. I don't think it affects the following. For example, mine used to be scratchy. Then it changed to playing quickly twice. That was true before, or after, I had installed ...

I came home after letting it sit for a while in sleep mode and it sounded different - more scratchy, so adjusted up to 80.

remember, pulseaudio supposedly isn't installed per MX Package Installer...

Change the pulseaudio config file /etc/pulse/default.pa, changing this line:
file doesn't exist.

In /etc/pulse/daemon.conf set the following:
file doesn't exist.

env PULSE_LATENCY_MSEC=60 env WINEPREFIX=/location/of ...