Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
12-27-2012, 06:11 PM
|
#151
|
|
Member
Registered: Apr 2011
Posts: 65
Rep:
|
Quote:
Originally Posted by jtsn
Intel GPUs need Mesa 9.0, otherwise Steam will crash.
|
I can attest to that.
In order to make Steam work in my machine (intel graphic card) I had to update libdrm and mesa.
Also worth mentioning it would be wise to remove the old versions (removepkg libdrm and mesa)
To update libdrm I just downloaded the .tar.gz and built it (configure, make, make install).
To update mesa I downloaded the mesa-9 tar.gz and used a slackbuild made for mesa-8, which worked perfectly (remember to edit the VERSION variable from the slackbuild). I had to use a slackbuild because just building it without any custom flags it was not recognizing glx anymore.
|
|
|
1 members found this post helpful.
|
12-28-2012, 01:51 AM
|
#152
|
|
Member
Registered: Apr 2011
Distribution: Slackware 14, Linux 3.2.29 x86_64
Posts: 141
Rep:
|
Quote:
Originally Posted by beder
To update libdrm I just downloaded the .tar.gz
|
Where'd you find it?
Quote:
Originally Posted by beder
To update mesa I downloaded the mesa-9 tar.gz
|
Could you please provide that link, too?
Quote:
Originally Posted by beder
I had to use a slackbuild because just building it without any custom flags it was not recognizing glx anymore.
|
Where'd you find a slackbuild for it?
Thanks
|
|
|
|
12-28-2012, 05:01 PM
|
#154
|
|
Member
Registered: Apr 2011
Posts: 65
Rep:
|
So trying to launch TF2 now in a machine with an Intel Graphic Card
Updated libdrm and Mesa-9
First I got the error:
Code:
Required OpenGL extension "GL_EXT_texture_compression_s3tc" is not supported. Please install S3TC texture support
Which was solved by launching steam with:
Code:
force_s3tc_enable=true steam
But then when launching TF2 all I get is a black screen
Looking in the console, I see errors such as those:
Code:
ompile of "vertexlit_and_unlit_generic_vs20" Failed:
//GLSLvp
#version 130
//ATTRIBMAP-00-10-20-30-A0-50-51-01-31-xx-xx-xx-xx-xx-xx-xx
attribute vec4 v0; // 80000000 900f0000
attribute vec4 v1; // 80000001 900f0001
attribute vec4 v2; // 80000002 900f0002
attribute vec4 v3; // 80000003 900f0003
attribute vec4 v4; // 8000000a 900f0004
attribute vec4 v5; // 80000005 900f0005
attribute vec4 v6; // 80010005 900f0006
attribute vec4 v7; // 80010000 900f0007
attribute vec4 v8; // 80010003 900f0008
//SAMPLERMASK-0
//SAMPLERTYPES-ffffffff
//HIGHWATER-50
//HIGHWATERBONE-161
Code:
Compile of "shadowmodel_ps20" Failed:
//GLSLfp
#version 130
varying vec4 oT0;
varying vec4 oT1;
varying vec4 oT2;
varying vec4 oT3;
//SAMPLERMASK-0
//SAMPLERTYPES-ffffffff
//HIGHWATER-1
|
|
|
|
12-28-2012, 05:14 PM
|
#155
|
|
Member
Registered: Mar 2012
Location: California
Distribution: Slackware64-current
Posts: 73
Rep: 
|
Quote:
Originally Posted by beder
So trying to launch TF2 now in a machine with an Intel Graphic Card
Updated libdrm and Mesa-9
First I got the error:
Code:
Required OpenGL extension "GL_EXT_texture_compression_s3tc" is not supported. Please install S3TC texture support
Which was solved by launching steam with:
Code:
force_s3tc_enable=true steam
But then when launching TF2 all I get is a black screen
Looking in the console, I see errors such as those:
Code:
ompile of "vertexlit_and_unlit_generic_vs20" Failed:
//GLSLvp
#version 130
//ATTRIBMAP-00-10-20-30-A0-50-51-01-31-xx-xx-xx-xx-xx-xx-xx
attribute vec4 v0; // 80000000 900f0000
attribute vec4 v1; // 80000001 900f0001
attribute vec4 v2; // 80000002 900f0002
attribute vec4 v3; // 80000003 900f0003
attribute vec4 v4; // 8000000a 900f0004
attribute vec4 v5; // 80000005 900f0005
attribute vec4 v6; // 80010005 900f0006
attribute vec4 v7; // 80010000 900f0007
attribute vec4 v8; // 80010003 900f0008
//SAMPLERMASK-0
//SAMPLERTYPES-ffffffff
//HIGHWATER-50
//HIGHWATERBONE-161
Code:
Compile of "shadowmodel_ps20" Failed:
//GLSLfp
#version 130
varying vec4 oT0;
varying vec4 oT1;
varying vec4 oT2;
varying vec4 oT3;
//SAMPLERMASK-0
//SAMPLERTYPES-ffffffff
//HIGHWATER-1
|
I get an error trying to launch TF2 on slackware 64 current using AMD proprietary drivers 9.002 (catalyst 12.10)
Says I may need to reinstall driver but it was just compiled right after I built all the deps, just before installing steamclient
|
|
|
|
12-28-2012, 06:29 PM
|
#156
|
|
Member
Registered: Apr 2011
Distribution: Slackware 14, Linux 3.2.29 x86_64
Posts: 141
Rep:
|
Quote:
Originally Posted by Alien Bob
|
Thanks for the links
Last edited by Geremia; 12-28-2012 at 06:32 PM.
|
|
|
|
12-28-2012, 08:27 PM
|
#157
|
|
Member
Registered: Mar 2012
Location: California
Distribution: Slackware64-current
Posts: 73
Rep: 
|
Quote:
Originally Posted by buradd
I get an error trying to launch TF2 on slackware 64 current using AMD proprietary drivers 9.002 (catalyst 12.10)
Says I may need to reinstall driver but it was just compiled right after I built all the deps, just before installing steamclient
|
the error i'm getting is
Code:
Could not find required OpenGL entry point 'glColorMaskIndexedEXT'! Either your video card is unsupported, or your OpenGL driver needs to be updated.
|
|
|
|
12-29-2012, 01:50 AM
|
#158
|
|
Member
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 276
Rep:
|
Quote:
Originally Posted by beder
So trying to launch TF2 now in a machine with an Intel Graphic Card
Updated libdrm and Mesa-9
|
First you have to find out, if your GPU/driver actually supports the minimum requirements:
Code:
glxinfo | grep ^OpenGL
|
|
|
|
12-29-2012, 02:21 AM
|
#159
|
|
Member
Registered: Sep 2011
Location: Italy
Distribution: Slackware
Posts: 597
Rep: 
|
Quote:
Originally Posted by beder
So trying to launch TF2 now in a machine with an Intel Graphic Card
Updated libdrm and Mesa-9
First I got the error:
Code:
Required OpenGL extension "GL_EXT_texture_compression_s3tc" is not supported. Please install S3TC texture support
Which was solved by launching steam with:
Code:
force_s3tc_enable=true steam
|
That's not the way to solve it, but only a workaround for the s3tc check.
You should install the libtxc-dxtn library (there's a SlackBuild on SBo), because mainline mesa lacks a way to decompress S3-compressed textures.
Be aware of the US patent restrictions, though...
@buradd: it seems like you'll have to install the Catalyst Beta drivers to make TF2 run. They probably "overlooked" that extension (it requires OpenGL 2 so it's not that new...) and are implementing it right now because TF2 requires it 
|
|
|
|
12-29-2012, 03:40 AM
|
#160
|
|
Member
Registered: Apr 2011
Distribution: Slackware 14, Linux 3.2.29 x86_64
Posts: 141
Rep:
|
Quote:
Originally Posted by beder
I can attest to that.
In order to make Steam work in my machine (intel graphic card) I had to update libdrm and mesa.
Also worth mentioning it would be wise to remove the old versions (removepkg libdrm and mesa)
To update libdrm I just downloaded the .tar.gz and built it (configure, make, make install).
To update mesa I downloaded the mesa-9 tar.gz and used a slackbuild made for mesa-8, which worked perfectly (remember to edit the VERSION variable from the slackbuild). I had to use a slackbuild because just building it without any custom flags it was not recognizing glx anymore.
|
Okay, I did all this, but now I get the segfault error mentioned earlier in this thread…
UPDATE: Wait, I was supposed to build 32 bit packages of mesa and libdrmb, no? That's probably why, then… I built and installed 64 bit packages.
Last edited by Geremia; 12-29-2012 at 04:10 AM.
|
|
|
|
12-29-2012, 04:13 AM
|
#161
|
|
Member
Registered: Apr 2010
Distribution: Slackware
Posts: 309
Rep:
|
Quote:
Originally Posted by Alien Bob
|
Good info. What I'd like to add: users of intel graphics should regularly check the intel recommendations on http://intellinuxgraphics.org/ . The page links to the download sites via http://intellinuxgraphics.org/download.html and gives a recommendation of components, currently http://intellinuxgraphics.org/2012Q4.html .
Of course, myself I've given up on intel some time ago when I went through the craziness of compiling everything myself including the xorg server in the elusive hunt for stable graphics. 
|
|
|
|
12-29-2012, 04:13 AM
|
#162
|
|
Member
Registered: Sep 2011
Location: Italy
Distribution: Slackware
Posts: 597
Rep: 
|
Quote:
Originally Posted by Geremia
UPDATE: Wait, I was supposed to build 32 bit packages of mesa and libdrmb, no?
|
Precisely.
|
|
|
|
12-29-2012, 04:41 AM
|
#163
|
|
Senior Member
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 1,933
|
I think it's not a mistake to have installed the x86_64 versions of those packages if steam needs 32 bit stuff, mesa and libdrm will be needed by the 64bit X.
You just have, in addition, to build also the 32bit versions of those, run convertpkg-compat32 on them and install the resulting *-compat32-* packages.
Last edited by ponce; 12-29-2012 at 04:42 AM.
|
|
|
1 members found this post helpful.
|
12-29-2012, 05:01 AM
|
#164
|
|
Member
Registered: Sep 2011
Location: Italy
Distribution: Slackware
Posts: 597
Rep: 
|
For building compat32 packages from "scratch" you can try using my build32.sh script which, given a SlackBuild script as input, modifies a copy of it on-the-fly and runs it to compile/build a compat32 package.
It works ok for most packages (like libdrm).
It relies on the /etc/profile.d/32dev.sh file to set the proper 32-bit environment variables, so make sure it's present in your multilib setup.
Mesa is just one of those packages that need some tuning to build as 32-bit and, therefore, you'll probably be better using a dedicated compat32-SlackBuild file because build32.sh will fail miserably.
One need to force the compilation to 32 bit using 2 configure flags (--enable-32-bit --disable-64-bit), otherwise the build system picks up 64-bit asm files and tries to compile them as 32-bit code.
I guess this is due to the "as" assembler being 64 bit only on a "normal" Slackware64 multilib system, but I need to check on that before other assumptions.
Last edited by 414N; 12-30-2012 at 02:04 AM.
Reason: Added some info
|
|
|
1 members found this post helpful.
|
12-29-2012, 07:57 PM
|
#165
|
|
Member
Registered: Apr 2011
Distribution: Slackware 14, Linux 3.2.29 x86_64
Posts: 141
Rep:
|
Quote:
Originally Posted by ponce
You just have, in addition, to build also the 32bit versions of those, run convertpkg-compat32 on them and install the resulting *-compat32-* packages.
|
Excellent
Thanks
I didn't know about convertpkg-compat32.
What's the difference between a simple 32 bit package and a '32-bit compatibility' package?
Last edited by Geremia; 12-29-2012 at 07:59 PM.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:31 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|