You are not logged in.
I just installed a new Arch VM yesterday, and updated the kernel this morning, so all packages are current. I can't get the vboxvideo module to load. I installed the virtualbox-guest-utils package, and the vboxsf and vboxguest modules load fine. When I do `modprobe vboxguest`, I get the following error to the console:
modprobe: ERROR: could not insert 'vboxvideo': Invalid argument
And in dmesg, I get these errors:
[ 1277.138805] vboxvideo: disagrees about version of symbol drm_pci_init
[ 1277.138826] vboxvideo: Unknown symbol drm_pci_init (err -22)
[ 1277.138847] vboxvideo: disagrees about version of symbol drm_vblank_init
[ 1277.138859] vboxvideo: Unknown symbol drm_vblank_init (err -22)
[ 1277.138876] vboxvideo: disagrees about version of symbol drm_pci_exit
[ 1277.138888] vboxvideo: Unknown symbol drm_pci_exit (err -22)
The only additional info I can think to give is when I first installed the virtualbox-guest-utils package, I hadn't yet installed the xorg-server group. I did remove and re-install the virtualbox-guest-utils package afterward, but it made no difference. I've also (yesterday and again after kernel update) run `dkms install vboxguest/4.2.6` and that builds the modules successfully.
Any ideas?
Offline
Did you reboot after the kernel upgrade?
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Yes, I did reboot. After posting this, and some more searching within site, I found this which looks like it may be the culprit:
https://bugs.archlinux.org/index.php?do … k_id=33229
It seems to still not be (permanently) resolved, unfortunately.
Offline
I'm having exactly the same problem. Unfortunately, Benjamin Robin's xorg-server patch in that bug report does not seem to help with this problem.
Offline
Same problem here. Also tried the xorg-server patch and it had no effect.
However, I did try the dkms method:
pacman -R virtualbox-guest-modules (req'd as it puts the modules in a different place than dkms, and depmod will keep pointing to it unless it is uninstalled)
pacman -S virtualbox-guest-dkms
dkms install vboxguest/4.2.6
When I reboot the vboxvideo symbol errors go away:
[ 1.908994] vboxguest: major 0, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
[ 1.908996] vboxguest: Successfully loaded version 4.2.6_OSE (interface 0x00010004)
[ 1.915247] vboxsf: Successfully loaded version 4.2.6_OSE (interface 0x00010004)
[ 1.927216] [drm] Initialized vboxvideo 1.0.0 20090303 for 0000:00:02.0 on minor 0
However if I try starting X, then it dumps errors (I boot into multi-user text mode, then "startx >& xlog"), and I get stuff like this (note I am using Compiz + XFCE):
Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
OpenGL Warning: XDamage: Can't connect to display :0.0
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 191 requests (191 known processed) with 2 events remaining.
fusion-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
(polkit-gnome-authentication-agent-1:407): Gdk-WARNING **: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
* Detected Session: xfce
* Searching for installed applications...
* Setting window manager to Compiz
* Using the GTK Interface
* Starting Compiz
... executing: compiz --replace --sm-disable --ignore-desktop-hints ccp
xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
xinit: connection to X server lost
I've spent several hours trying different things, but ultimately I either get the vboxvideo symbol error or the fatal IO error 11. Now that I think of it however I haven't tried the dkms recompile in combination with the xorg patch.
Edit: Tried the dkms and xorg patch combination, no change, still get error 11 from X.
Last edited by nox771 (2013-01-27 19:35:28)
Offline
Found that the Error 11 that I get from X above only happens when I use Compiz. Using dkms to recompile the modules, reboot, and then starting straight XFCE does not have an error. If I do that I get this (from inside XFCE):
glxinfo | grep renderer
...
OpenGL renderer string: Chromium
However if I then start Compiz (compiz --replace ccp &) it will freeze the screen and dump out the same errors as above.
Offline
Interesting. Is 3D acceleration working for you?
Edit: I just tried the virtualbox-guest-dkms method, and 3D performance is better, but it's pretty broken. For example, I can run glxgears, and it runs smoothly, but if I try to move another window over it, then the spinning gears still appear over the other window.
Last edited by Lux Perpetua (2013-01-28 00:24:35)
Offline
I'm able to get glxgears to run without problem under just XFCE. However in an odd twist I do see the problem you describe on an older VM I have running Virtualbox 4.1.22 and Compiz+XFCE.
I was able to test out the 3D by installing and running extremetuxracer. It defaults to fullscreen mode though which screws up the mouse (stuck in the upper-left corner). I was able to get it to run windowed as follows
pacman -S extremetuxracer
etracer (starts fullscreen - just quit)
Inside ~/.etracer/options change "set fullscreen false"
etracer (now windowed - goto config and disable joystick and remap keys)
I was able to get that to run fine at 60fps (guessing v'sync limits it to 60). However it doesn't help the Compiz problem (for myself I use Compiz because I use compiz-boxmenu from AUR since it allows me to get a sane right-click menu - something every "modern" GUI screws up these days).
Offline
I'm able to get glxgears to run without problem under just XFCE. However in an odd twist I do see the problem you describe on an older VM I have running Virtualbox 4.1.22 and Compiz+XFCE.
I'm also using XFCE (with the default xfwm), but I realized that I had compositing enabled. Disabling it does improve that problem, but moving windows over OpenGL windows is still glitchy.
Offline
An update:
- installed virtualbox-guest-modules 4.2.6-5 (released today)
- removed virtualbox-guest-dkms
- did a full update (pacman -Syu) - reason, the new guest modules are built against kernel 3.7.5-1
Now when I reboot the symbol errors in the original post are gone, but Compiz is still not working correctly (same as earlier post - error 11's in xorg log).
Last edited by nox771 (2013-01-30 20:48:36)
Offline