No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

jokkebk · 2015-03-10 22:13:24

I've been using Arch happily in 64 bit VirtualBox setup for a few months (under 64bit Win7), but after installing cool-retro-term, realized I have no 3D acceleration. glxinfo shows I'm using unaccelerated Gallium instead of Chromium:

OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)

I've googled about 100 different bug reports and solution suggestions, but to no avail. Virtualbox forums say that a similar bug was fixed last June, and after that the glxinfo should give a dozen warnings about being unable to load stuff, but report the Chromium drivers. I have the latest version of virtualbox-guest-modules (4.3.24-1) which should contain the fix, but that doesn't help.

I installed Debian today to test things out, and indeed, I had 3D acceleration out of the box. This was likely because the initial install was Debian stable, and the latest Mesa versions (around early 2014) initially broke the 3D acceleration, so probably Mesa was too stable... Upgrading to Debian Jessie broke the 3D acceleration to same state as my Arch install (Gallium renderer instead of Chromium), which seems to support this hypothesis. HOWEVER, re-compiling the latest guest additions seemed to have the effect the Virtualbox forums suggested there should be -- 3D support was restored, and Chromium once again the renderer in glxinfo.

Has someone successfully gotten Arch under Virtualbox working with 3D acceleration without downgrading Mesa libraries? The Cinnamon desktop nags me about not having HW acceleration, and cool-retro-term uses 100 % CPU due to software rendering, so I'd rather have acceleration than not.

jokkebk · 2015-03-10 22:16:44

Alternatively, does someone have info on how to recompile guest additions myself, as it seemed to fix things under Debian. The arch pacman package SHOULD be the latest, but I have a nagging doubt that if I could recompile myself, there would be at least 50 % probability of things working like the should. However, I couldn't find any bug reports in the latest virtualbox-guest-modules repository package (4.3.24-1) or even anything in recent version history. Why is there nothing in Wiki about manual compiling of guest additions?

Xabre · 2015-03-10 23:20:40

https://wiki.archlinux.org/index.php/Arch_Build_System

Scimmia · 2015-03-11 02:10:15

What kernel are you running? There are 4 different ones in the official repos alone.

fijam · 2015-03-19 23:32:16

Same issue here, Arch as guest under W7 x64, virtualbox 4.3.26 on the host and virtualbox-guest-modules and -utils 4.3.26-1 on the guest. Kernel 3.19.2-1. Running glxinfo, I get Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits) instead of Chromium.

I suspect we are running a bleeding-edge mesa and it trips something up in vbox as used to happen in the past. Can anyone file an upstream bug?

Last edited by fijam (2015-03-19 23:43:47)

UncleSlug · 2015-03-28 03:45:23

I have the same problem (with standard 3.19.2-1 kernel, vbox 4.3.26).

I tried grabbing an older mesa and mesa-libgl from the arch rollback machine (which worked the last time it stopped working) but version 10.4.6 just crashed my machine when gnome was starting. I'm guessing there are more packages required for that approach to work but i don't know what they are. A complete rollback would be clean but would probably be more annoying lol.

andrzej1_1 · 2017-09-07 20:50:00

jokkebk wrote:

I've been using Arch happily in 64 bit VirtualBox setup for a few months (under 64bit Win7), but after installing cool-retro-term, realized I have no 3D acceleration. glxinfo shows I'm using unaccelerated Gallium instead of Chromium:
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
I've googled about 100 different bug reports and solution suggestions, but to no avail. Virtualbox forums say that a similar bug was fixed last June, and after that the glxinfo should give a dozen warnings about being unable to load stuff, but report the Chromium drivers. I have the latest version of virtualbox-guest-modules (4.3.24-1) which should contain the fix, but that doesn't help.
I installed Debian today to test things out, and indeed, I had 3D acceleration out of the box. This was likely because the initial install was Debian stable, and the latest Mesa versions (around early 2014) initially broke the 3D acceleration, so probably Mesa was too stable... Upgrading to Debian Jessie broke the 3D acceleration to same state as my Arch install (Gallium renderer instead of Chromium), which seems to support this hypothesis. HOWEVER, re-compiling the latest guest additions seemed to have the effect the Virtualbox forums suggested there should be -- 3D support was restored, and Chromium once again the renderer in glxinfo.
Has someone successfully gotten Arch under Virtualbox working with 3D acceleration without downgrading Mesa libraries? The Cinnamon desktop nags me about not having HW acceleration, and cool-retro-term uses 100 % CPU due to software rendering, so I'd rather have acceleration than not.

Did you find solution?

WorMzy · 2017-09-07 21:14:24

Please do not necrobump, andrzej1_1.

https://wiki.archlinux.org/index.php/Co … bumping.22

Closing.

Arch Linux

#1 2015-03-10 22:13:24

No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

#2 2015-03-10 22:16:44

Re: No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

#3 2015-03-10 23:20:40

Re: No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

#4 2015-03-11 02:10:15

Re: No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

#5 2015-03-19 23:32:16

Re: No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

#6 2015-03-28 03:45:23

Re: No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

#7 2017-09-07 20:50:00

Re: No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

#8 2017-09-07 21:14:24

Re: No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

Board footer