Installer Steam
Logg inn
|
språk
简体中文 (forenklet kinesisk)
繁體中文 (tradisjonell kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tsjekkisk)
Dansk (dansk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spania)
Español – Latinoamérica (spansk – Latin-Amerika)
Ελληνικά (gresk)
Français (fransk)
Italiano (italiensk)
Bahasa Indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (nederlandsk)
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasil)
Română (rumensk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (vietnamesisk)
Українська (ukrainsk)
Rapporter et problem med oversettelse
Diskusjonsregler og retningslinjer
2 
Rapporter dette innlegget
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 460 SE/PCIe/SSE2
OpenGL version string: 4.2.0 NVIDIA 304.88
OpenGL shading language version string: 4.20 NVIDIA via Cg compiler
OpenGL extensions:
version 319.17 at this moment
1.) In /usr/lib, there is a directory called something like nvidia-304 or nvidia-304-updates or nvidia-319 etc., which holds the nvidia OpenGL libraries.
If that directory is called nvidia-304, for instance, you'd want to, as root, edit the file /usr/lib/nvidia-304/alt_ld.so.conf (which you'll notice is currently blank) and add the lines:
If that directory is something else, like /usr/lib/nvidia-304-updates you'd want to edit the file /usr/lib/nvidia-304-updates/alt_ld.so.conf as root and add the lines:
And if your directory is /usr/lib/nvidia-<something else>, you'd want to edit /usr/lib/nvidia-<something else>/alt_ld.so.conf as root and add the lines:
You get the idea...
2.) In the linux terminal, run the command:
Then type in your password for your linux user account (you need to be an administrator, of course (in the sudo group, in other words)).
3.) Restart steam. You'll notice that there's no warning about not using direct rendering anymore. You'll also be able to play games like tf2 again.
Of course, this is a bug with the nvidia driver packages in Ubuntu 13.04 (Raring) 64-bit. And as such, I've filed a bug report: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1181651
If you have this problem, too, and it was fixed with these directions please go to the bug report and say it affects you, too. The more people who confirm the bug, the more likely the nvidia driver packages will be fixed by the people who maintain them. :)
Wierd. Well, first I'd check to make sure your kernel drivers are correctly installed. You should first run this comand to make sure you have the required packages for dkms to run:
Then (assuming you're using the nvidia-319 package and you've already installed it) you need to run this command:
Which will give you output looking somewhat like this:
Now, when it says "Building initial module for <your linux kernel version>", MAKE SURE it says "Done." after it. If it doesn't, then something is seriously messed up. Anyway, assuming that it says "Done.", you then want to reboot your computer to load up the new kernel module. Once that's done, follow the instructions from my previous post to fix ldconfig again since dpkg-reconfigure might have un-fixed that... You shouldn't have to reboot a second time assuming you've run sudo ldconfig. Just rebooting Steam after running ldconfig will be enough to load the correct nvidia libGL.so library.
If you're still getting that error message, then you should probably check to see which library steam is loading. While it's difficult to do it directly on steam, you can do it on another 32-bit program that uses libGL.so (which should be the same libGL.so that Steam is loading). Such a program is the 32-bit version of glxinfo. To install the 32-bit version (you probably have the 64-bit version installed currently), run the command:
The :i386 specifies you want the 32-bit version of mesa-utils (which contains glxinfo). To see what version of libGL.so glxinfo and Steam are using, just run the command:
This will output a list of various .so libraries that glxinfo is using. One of them is libGL.so, so find it and look to the right of the entry to see the full path of the libGL.so glxinfo is actually using. If you see something like:
Then everything should be working properly and you shouldn't get the error message any longer. Notice that the path is in the form /usr/lib32/nvidia-<something>/libGL.so.<version #>, the lib32 and the nvidia-<something> are the important bits to look for.
If it points to anywhere else, then something is still screwed up. Please send me the output of that command and the output of dpkg-reconfigure and I'll see if I can help you.
It shows this, not nvidia. So is this maybe the error?
Full output:
ldd /usr/bin/glxinfo
linux-gate.so.1 => (0xf77bd000)
libGL.so.1 => /usr/lib/i386-linux-gnu/mesa/libGL.so.1 (0xf773f000)
libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf7609000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7455000)
libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xf743e000)
libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf742c000)
libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xf7428000)
libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf7421000)
libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xf741d000)
libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xf7405000)
libxcb-dri2.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri2.so.0 (0xf7400000)
libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf73de000)
libXxf86vm.so.1 => /usr/lib/i386-linux-gnu/libXxf86vm.so.1 (0xf73d8000)
libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xf73ca000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf73af000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf73aa000)
/lib/ld-linux.so.2 (0xf77be000)
libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf73a6000)
libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf739f000)
This will take a while as it will run dpkg-reconfigure on your driver so I can see if there was any sort of problem with the driver installation (and that's why the script needs super-user priviledges). The script will not output anything to your shell, as all the output is redirected to a file. Once it finishes, post the contents of the file ldconfig-settings-dumper-output.txt which will appear in the same directory you saved the script into. I've tested the script on my own computer, so it _should_ work.
The script:
One thing to add:
*****/etc/ld.so.conf.d/steam.conf*****
/usr/lib32/nvidia-310-updates
/usr/lib/i386-linux-gnu/mesa
I changed this .conf as it was on a forum as a solution for the problem. I just changed the "/usr/lib32/" to "/usr/lib32/nvidia-310-updates" but it didn't work eitherway. So i can change it back if needed.
I did the script again, output:
This will definitively tell us which library steam is using (so please post the output of the command). You should also start Steam by running the command:
In a terminal so you can get the output of Steam's startup process. This will also give us some more clues as to what is going wrong. Again, please post the output.
Anyway, I'm fairly certain that the output will say that Steam is loading the correct libraries (and if it doesn't then I've got a lot more to learn about how linux decides which library a program will load). Starting steam in a terminal will just help me confirm what I think is happening: that Steam is loading the correct library but that library cannot access the nvidia graphics hardware because something is wrong with the kernel driver.
Since Steam should be loading the proper libraries (if ldd /usr/bin/glxinfo is anything to go by), I'd bet that it's a problem related to the nvidia kernel driver. If the kernel driver is not properly loaded, Steam will say it's not using direct rendering because it can't access the nvidia graphics hardware. So, I want you to install the latest nvidia-319 driver because I know it works:
You'll need to restart your computer after this to reload the module. Then you'll need to follow the instructions from my very first post again because installing a new driver version will most likely erase the old configuration. After you run sudo ldconfig after editing the alt_ld.so.conf file, make sure to run ldd /usr/bin/glxinfo (the 32-bit version) to make sure that it's using the nvidia-319 libGL.so library. If it is, then we can safely assume that steam is using it, too. Go ahead and start up Steam in a terminal. Hopefully, the error message will go away after this. If not, then post the terminal output of Steam plus the output of the following commands:
Also, post the information given in Steam by going to the drop-down menu Help and then System Information. All I need is the information under "Video Card".
While you wait for my reply again, some steps you can try to take to fix it yourself is going to the Nvidia X Server Settings program and looking at OpenGL/GLX Information and tweaking the OpenGL Settings and the Antialiasing Settings. The mere act of changing some of these settings (which will regenerate configuration settings for the graphics card) might just fix something. This might be a long shot, but it's certainly worth a try. On top of that, if there's a problem with the driver, on the OpenGL/GLX Information page, the very first entry in the list is Direct Rendering, and it will be set to off. And if there is no problem and everything is working fine, it will be set to on.
P.S.: Sorry about my long-winded posts. I sometimes can talk a lot...