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.
Mesa 10.2.5 and 10.2.6 have been released since then and has some bug fixes. You could always download the source and use the SlackBuild scripts to rebuild MesaLib.
-Current uses version 2.99.914 of xf86-video-intel and mesa-10.2.4... so it should be up to date. Otherwise, it's a bug with Mesa displaying the incorrect versioning numbers.
Wed Jul 16 05:31:30 UTC 2014
x/xf86-video-intel-2.99.912-x86_64-1.txz: Upgraded.
Looks like the stable driver won't compile with the new xorg-server, so
we'll try this one.
Maybe this is the reason? I may be off base here and no help at all to your question, especially since I use Nvidia.
I hat a look at the git history of mesa and this is what happened. In Mesa 9.1, the intel dri code for i915 and i965 had a shared source tree under src/mesa/drivers/dri/intel. The OpenGL version is defined in that shared part. In Mesa 10.2 this is now no longer shared. i965 still support OpenGL >= 3.0, but i915 tops out at OpenGL 2.1. So either this was a false value to begin with (ie. i915 doesn't support anything higher than OpenGL 2.1) or this is an upstream bug.
I had a similar problem with AMD radeon hardware but the latest mesa update to 10.2.6 made it look as it should and also added OpenGL ES, maybe it also made changes for intel hardware.
I had some OpenGL problems with wine and so on but the latest update seems to have sort them all out.
Before update
Code:
$ glxinfo |grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD ARUBA
OpenGL version string: 2.1 Mesa 10.2.4
OpenGL shading language version string: 1.30
OpenGL extensions:
After update
Code:
$ glxinfo|grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD ARUBA
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.2.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.2.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0
OpenGL ES profile extensions:
The latest mesa update enables support for floating point textures for all drivers. Before only the intel driver had it enabled because it ignores the ./configure parameter.
Floating point textures are a requirement for OpenGL 3.0, so that's why some drivers might show support for a newer version now.
This should indeed also be the case for the i915 driver
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.