[-- Attachment #1.1: Type: text/plain, Size: 359 bytes --] Virtualbox ain't working for quite some time now. Last time it worked was when I booted with 3.19.8.1. Currently on up to date 4.1.6.1 force reconfigure fails against all kernels. xbps-query -l | grep header shows I have 3.19.8.1, 4.0.9.1 and 4.1.6.1 installed. Is this a conflict and shall I just leave the latest version in order to sort it out ? [-- Attachment #1.2: Type: text/html, Size: 431 bytes --]
[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --] Could you provide the output or an error message? For me its working with all installed kernel versions: Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.0.9_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.0.9_1... done. Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.3_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.3_1... done. Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.4_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.4_1... done. Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.5_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.5_1... done. Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.6_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.6_1... done. Am Montag, 24. August 2015 14:26:57 UTC+2 schrieb Frankie Wild: > > Virtualbox ain't working for quite some time now. Last time it worked was > when I booted with 3.19.8.1. > > Currently on up to date 4.1.6.1 force reconfigure fails against all > kernels. > > xbps-query -l | grep header shows I have 3.19.8.1, 4.0.9.1 and 4.1.6.1 > installed. Is this a conflict and shall I just leave the latest version in > order to sort it out ? > [-- Attachment #1.2: Type: text/html, Size: 1603 bytes --]
[-- Attachment #1.1: Type: text/plain, Size: 2565 bytes --] Building DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.2_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.2_1... FAILED! DKMS module 'virtualbox-ose-5.0.2' failed to install, please do this manually and check for errors in the log file. Building DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.3_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.3_1... FAILED! DKMS module 'virtualbox-ose-5.0.2' failed to install, please do this manually and check for errors in the log file. Building DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.4_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.4_1... FAILED! DKMS module 'virtualbox-ose-5.0.2' failed to install, please do this manually and check for errors in the log file. Building DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.5_1... done. Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-3.19.5_1... FAILED! DKMS module 'virtualbox-ose-5.0.2' failed to install, please do this manually and check for errors in the log file. Unsure how to do it manually and where eventually the log file would be. There is no vbox folder in var/log. On Monday, August 24, 2015 at 3:30:48 PM UTC+3, Duncaen wrote: > > Could you provide the output or an error message? > For me its working with all installed kernel versions: > > Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.0.9_1... done. > Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.0.9_1... done. > Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.3_1... done. > Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.3_1... done. > Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.4_1... done. > Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.4_1... done. > Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.5_1... done. > Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.5_1... done. > Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.6_1... done. > Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.6_1... done. > > Am Montag, 24. August 2015 14:26:57 UTC+2 schrieb Frankie Wild: >> >> Virtualbox ain't working for quite some time now. Last time it worked >> was when I booted with 3.19.8.1. >> >> Currently on up to date 4.1.6.1 force reconfigure fails against all >> kernels. >> >> xbps-query -l | grep header shows I have 3.19.8.1, 4.0.9.1 and 4.1.6.1 >> installed. Is this a conflict and shall I just leave the latest version in >> order to sort it out ? >> > [-- Attachment #1.2: Type: text/html, Size: 3268 bytes --]
[-- Attachment #1.1: Type: text/plain, Size: 546 bytes --] Sounds like another side effect of the /usr/sbin transition. Juan's suggestion helped with my nvidia problem <https://groups.google.com/forum/#!topic/voidlinux/iZXamHmohQ4>, it might work for you as well. Make sure your /usr/sbin directory is a symlink to /usr/bin before you do anything else. - dkms build -m virtualbox-ose -v 5.0.2 -k $(uname -r) > - dkms install -m virtualbox-ose -v 5.0.2 -k $(uname -r) > - xbps-reconfigure -f virtualbox-ose > Before running xbps-reconfigure, make sure the kmods are built and > installed correctly. [-- Attachment #1.2: Type: text/html, Size: 782 bytes --]
[-- Attachment #1.1: Type: text/plain, Size: 862 bytes --] Thanks so much to all who gave feedback in both threads, that fixed it. I somehow missed following the nvidia thread till it's very end, Virtualbox working, might as well try to make nvidia work :) On Tuesday, August 25, 2015 at 4:34:10 PM UTC+3, Stefan Mühlinghaus wrote: > > Sounds like another side effect of the /usr/sbin transition. Juan's > suggestion helped with my nvidia problem > <https://groups.google.com/forum/#!topic/voidlinux/iZXamHmohQ4>, it might > work for you as well. Make sure your /usr/sbin directory is a symlink to > /usr/bin before you do anything else. > > - dkms build -m virtualbox-ose -v 5.0.2 -k $(uname -r) >> - dkms install -m virtualbox-ose -v 5.0.2 -k $(uname -r) >> - xbps-reconfigure -f virtualbox-ose >> Before running xbps-reconfigure, make sure the kmods are built and >> installed correctly. > > [-- Attachment #1.2: Type: text/html, Size: 1449 bytes --]