[SOLVED] Slackware -current :- Is hardware acceleration working or not on my machine?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware -current :- Is hardware acceleration working or not on my machine?
Continuing from this thread - confused-at-opengl-version-in-current, I removed the 3.17.0-rc2 completely from my Slackware -current machine. Ran xorgsetup. Still the openGL appears to be :-
Code:
bash-4.3$ glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits)
OpenGL version string: 3.0 Mesa 10.2.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
Restarted without an xorg.conf too, no effect.
Direct rendering is enabled though :-
Code:
bash-4.3$ glxinfo | grep -i direct
direct rendering: Yes
The LIBGL_DEBUG=verbose glxinfo>/dev/null test sheds some light but what should I interpret from this?:-
Code:
libGL: screen 0 does not appear to be DRI3 capable
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/swrast_dri.so
libGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib64/xorg/modules/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast
libGL: Can't open configuration file /home/cruise/.drirc: No such file or directory.
libGL: Can't open configuration file /home/cruise/.drirc: No such file or directory.
Continuing from this thread - confused-at-opengl-version-in-current, I removed the 3.17.0-rc2 completely from my Slackware -current machine. Ran xorgsetup. Still the openGL appears to be :-
Code:
bash-4.3$ glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits)
OpenGL version string: 3.0 Mesa 10.2.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
Restarted without an xorg.conf too, no effect.
Direct rendering is enabled though :-
Code:
bash-4.3$ glxinfo | grep -i direct
direct rendering: Yes
The LIBGL_DEBUG=verbose glxinfo>/dev/null test sheds some light but what should I interpret from this?:-
Code:
libGL: screen 0 does not appear to be DRI3 capable
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/xorg/modules/dri/swrast_dri.so
libGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib64/xorg/modules/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast
libGL: Can't open configuration file /home/cruise/.drirc: No such file or directory.
libGL: Can't open configuration file /home/cruise/.drirc: No such file or directory.
The below is Xorg.0.log and Xorg.1.log for dri2 :-
Code:
bash-4.3# grep -i dri2 /var/log/Xorg.1.log
[ 95.496] Initializing built-in extension DRI2
[ 95.496] (II) LoadModule: "dri2"
[ 95.496] (II) Module "dri2" already built-in
[ 95.506] (II) Loading sub module "dri2"
[ 95.506] (II) LoadModule: "dri2"
[ 95.506] (II) Module "dri2" already built-in
[ 95.617] (II) intel(0): [DRI2] Setup complete
[ 95.617] (II) intel(0): [DRI2] DRI driver: i965
[ 95.617] (II) intel(0): [DRI2] VDPAU driver: i965
[ 95.617] (II) intel(0): direct rendering: DRI2 enabled
[ 95.634] (II) GLX: Initialized DRI2 GL provider for screen 0
Code:
bash-4.3# grep -i dri2 /var/log/Xorg.0.log
[ 52.291] Initializing built-in extension DRI2
[ 52.694] (II) AIGLX: Screen 0 is not DRI2 capable
The user is in video group.
My query is, IS hardware acceleration NOT really working or I'm just freaking out for no reason?
No. You do not have hardware acceleration right now. Your system got the software fallback, in this case, llvmpipe, which is an software rasterizer similar with the classic swrast, but with better performances.
Last edited by Darth Vader; 09-18-2014 at 02:23 PM.
No. You do not have hardware acceleration right now. Your system got the software fallback, in this case, llvmpipe, which is an software rasterizer similar with the classic swrast, but with better performances.
Yup, looking at the llvmpipe. How can I enable it, the way it used to be errr....I don't know when.
Why does Direct rendering say YES, could you please explain?
Yup, looking at the llvmpipe. How can I enable it, the way it used to be errr....I don't know when.
Why does Direct rendering say YES, could you please explain?
Regards.
Technically, yes, you have direct rendering, because the llvmpipe is a special software rasterizer which use the LLVM to emulate the 3D instructions executed by videocard, but using just and only the CPU power. Of course, the performance is low, even still it is much better that the classic swrast. Think about something similar with Windows's VGA Save Driver, capable to drive the desktop, but not the games.
So, with an powerful CPU you can expect from llvmpipe on working the 3D effects of KDE(4), but for gaming, is too slow.
In other hand, will be nice to show the entire content of /var/log/Xorg.log and /var/log/dmesg, also the output of "lspci -vvv", to be able to comment further.
Last edited by Darth Vader; 09-18-2014 at 02:59 PM.
Technically, yes, you have direct rendering, because the llvmpipe is a special software rasterizer which use the LLVM to emulate the 3D instructions executed by videocard, but using just and only the CPU power. Of course, the performance is low, even still it is much better that the classic swrast. Think about something similar with Windows's VGA Save Driver, capable to drive the desktop, but not the games.
So, with an powerful CPU you can expect from llvmpipe on working the 3D effects of KDE(4), but for gaming, is too slow.
In other hand, will be nice to show the entire content of /var/log/Xorg.log and /var/log/dmesg, also the output of "lspci -vvv", to be able to comment further.
Did you try to check the xorg.conf for the correct driver?
If you have an Intel chipset it should be using the "intel" driver.
Hi Reaper, I have two files in my /etc/X11/ - xorg.conf and xorg.conf-vesa. None of which has any entry of Intel driver in any section.
The xorg.conf.d/ folder is empty.
Go to xorg.conf, find the driver section (should down near the bottom) look for the first device listed, and change the "driver" to "intel", and restart your X-Session.
Go to xorg.conf, find the driver section (should down near the bottom) look for the first device listed, and change the "driver" to "intel", and restart your X-Session.
Hey Reaper, did you mean the "Device" section, because there's no driver section.
I removed modesetting and added intel in the device section for Driver. Rebooted and voila :-
Code:
bash-4.3$ glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 10.2.6
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 10.2.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:
Further checked by running glxgears in one terminal window and running intel_gpu_top in other terminal. While the glxgears test runs, the Render Busy shows in percentage. Previously it was 0 which was because the CPU was in use, not GPU. So it looks good now I think.
Much thanks to Reaper for this. Anything else can be verified here?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.