With the steam beta release for Linux, I am pretty excited about playing games under Linux again. However, it would appear to require the newer nvidia 310 drivers. Are there any plans to update these for Fedora 17 from rpmfusion? Michael

On Thu, Jan 3, 2013 at 4:37 PM, Sérgio Basto <sergio(a)serjux.com&gt; wrote: On Qui, 2013-01-03 at 16:24 -0700, Michael Smith wrote: > With the steam beta release for Linux, I am pretty excited about > playing games under Linux again. > > However, it would appear to require the newer nvidia 310 drivers. > > Are there any plans to update these for Fedora 17 from rpmfusion? > > Michael Hi, yeah , I also upgrade all my graphics drives, X11, Mesa, etc to try steam, but after other announcement, I find out that is not necessary (I do a yum distribution-synchronization) and works with F17 drives but I have an Intel, see if is the same in your case: http://software.opensuse.org/download.html?project=games&package=steam cd /etc/yum.repos.d/ wget http://download.opensuse.org/repositories/games/Fedora_17/games.repo yum install steam Thanks Sergio for the response. I also have used the opensuse packages to install Steam. When I try to run steam I get the following error: PROBLEM: You appear to have OpenGL 1.4.0, but we need at least 2.0.0! Could not find required OpenGL entry point 'glGetError'! Either your video card is unsupported, or your OpenGL driver needs to be updated. Looking on line, these appear to be offered by the nvidia 310.19 or never version. rpmfusion is currently providing 304.

Am 04.01.2013 03:16, schrieb Sérgio Basto: >> When I try to run steam I get the following error: >> >> PROBLEM: You appear to have OpenGL 1.4.0, but we need at least 2.0.0! >> Could not find required OpenGL entry point 'glGetError'! Either your >> video card is unsupported, or your OpenGL driver needs to be updated. >> >> >> Looking on line, these appear to be offered by the nvidia 310.19 or >> never version. rpmfusion is currently providing 304. >> > On my nvidia test computer which have F18, I got OpenGL 2.1.2 with > NVIDIA 304 > > glxinfo | grep -i opengl > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce 6500/PCIe/SSE2 > OpenGL version string: 2.1.2 NVIDIA 304.64 > OpenGL shading language version string: 1.20 NVIDIA via Cg compiler > OpenGL extensions: > > I going test it now, I will write something if can't install it F17 has also opengl 2.1 1.4 is the GLX version OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop OpenGL version string: 2.1 Mesa 8.0.4 client glx version string: 1.4

On Thu, Jan 3, 2013 at 8:11 PM, Sérgio Basto <sergio(a)serjux.com&gt; wrote: On Sex, 2013-01-04 at 03:21 +0100, Reindl Harald wrote: > > Am 04.01.2013 03:16, schrieb Sérgio Basto: > >> When I try to run steam I get the following error: > >> > >> PROBLEM: You appear to have OpenGL 1.4.0, but we need at least 2.0.0! > >> Could not find required OpenGL entry point 'glGetError'! Either your > >> video card is unsupported, or your OpenGL driver needs to be updated. > >> > >> > >> Looking on line, these appear to be offered by the nvidia 310.19 or > >> never version. rpmfusion is currently providing 304. > >> > > On my nvidia test computer which have F18, I got OpenGL 2.1.2 with > > NVIDIA 304 > > > > glxinfo | grep -i opengl > > OpenGL vendor string: NVIDIA Corporation > > OpenGL renderer string: GeForce 6500/PCIe/SSE2 > > OpenGL version string: 2.1.2 NVIDIA 304.64 > > OpenGL shading language version string: 1.20 NVIDIA via Cg compiler > > OpenGL extensions: > > > > I going test it now, I will write something if can't install it > > F17 has also opengl 2.1 > 1.4 is the GLX version > > OpenGL vendor string: Tungsten Graphics, Inc > OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop > OpenGL version string: 2.1 Mesa 8.0.4 > > client glx version string: 1.4 glxinfo | grep -i version server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 OpenGL version string: 2.1.2 NVIDIA 304.64 OpenGL shading language version string: 1.20 NVIDIA via Cg compile and steam is running without problems , I already played "world of goo demo". Have you nvidia installed correctly ? rpm -qa | grep nvidia nvidia-settings-1.0-26.fc18.x86_64 kmod-nvidia-3.6.7-4.fc17.x86_64-304.64-1.fc18.2.x86_64 kmod-nvidia-3.6.7-5.fc18.x86_64-304.64-1.fc18.2.x86_64 xorg-x11-drv-nvidia-libs-304.64-3.fc18.i686 xorg-x11-drv-nvidia-304.64-3.fc18.x86_64 nvidia-xconfig-1.0-25.fc18.x86_64 kmod-nvidia-3.6.10-4.fc18.x86_64-304.64-1.fc18.3.x86_64 xorg-x11-drv-nvidia-libs-304.64-3.fc18.x86_64 akmod-nvidia-304.64-1.fc18.3.x86_64 Hello again, Well, I was able to get it working with the 304 drivers. The missing component was the 32bit Nvidia libraries. Once those were installed, I am able to play cogs, Team Fortress 2, etc.

Sorry for the noise.

On Fri, 2013-01-04 at 02:16 +0000, Sérgio Basto wrote: > On my nvidia test computer which have F18, I got OpenGL 2.1.2 with > NVIDIA 304 > > glxinfo | grep -i opengl > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce 6500/PCIe/SSE2 > OpenGL version string: 2.1.2 NVIDIA 304.64 > OpenGL shading language version string: 1.20 NVIDIA via Cg compiler > OpenGL extensions: > > I going test it now, I will write something if can't install it. [mike@scrappy ~]$ glxinfo | grep -i opengl OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 550 Ti/PCIe/SSE2 OpenGL version string: 4.2.0 NVIDIA 304.64 OpenGL shading language version string: 4.20 NVIDIA via Cg compiler -- Mike Chambers Madisonville, KY "Best little town on Earth!"

On Sat, Jan 05, 2013 at 03:43:28PM -0500, George Galt wrote: > Mike: > > FWIW, I grabbed the src.rpms for 310.19 from here: > http://download1.rpmfusion.org/nonfree/fedora/development/rawhide/source/... > > They appear to be in rawhide, but nowhere else. I'm not really sure why. > > I grabbed nvidia-kmod-310.19, xorg-x11-drv-nvidia-310.19 and built them > using rpmbuild. I also had to build and install buildsys from here: > http://download1.rpmfusion.org/free/fedora/development/rawhide/source/SRP... > them to build properly. They installed just fine. I'm interested in trying out 310, as I read elsewhere that they improve performance (lower the CPU usage) of xorg, and having bad problems with xorg cpu usage (it spikes after my system is up for more than about 12 hours, even when I'm doing nothing other than running htop). I downloaded and built the OK, but: Did you have any problems with libnvcuvid.so? I see: rpm -q -l -p ./xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64.rpm | grep libnvcuvid.so /usr/lib64/nvidia/libnvcuvid.so /usr/lib64/nvidia/libnvcuvid.so.1 /usr/lib64/nvidia/libnvcuvid.so.310.19 But on install I get a missing dependency for libnvcuvid.so, this: # yum localinstall ./xorg-x11-drv-nvidia-310.19-1.fc17.x86_64.rpm ./xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64.rpm Loaded plugins: langpacks, presto, refresh-packagekit Examining ./xorg-x11-drv-nvidia-310.19-1.fc17.x86_64.rpm: 1:xorg-x11-drv-nvidia-310.19-1.fc17.x86_64 Marking ./xorg-x11-drv-nvidia-310.19-1.fc17.x86_64.rpm as an update to 1:xorg-x11-drv-nvidia-304.64-3.fc17.x86_64 Examining ./xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64.rpm: 1:xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64 Marking ./xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64.rpm as an update to 1:xorg-x11-drv-nvidia-libs-304.64-3.fc17.x86_64 Resolving Dependencies --> Running transaction check ---> Package xorg-x11-drv-nvidia.x86_64 1:304.64-3.fc17 will be updated ---> Package xorg-x11-drv-nvidia.x86_64 1:310.19-1.fc17 will be an update ---> Package xorg-x11-drv-nvidia-libs.x86_64 1:304.64-3.fc17 will be updated ---> Package xorg-x11-drv-nvidia-libs.x86_64 1:310.19-1.fc17 will be an update --> Processing Dependency: libnvcuvid.so()(64bit) for package: 1:xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64 --> Finished Dependency Resolution Error: Package: 1:xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64 (/xorg-x11-drv-nvidia-libs-310.19-1.fc17.x86_64) Requires: libnvcuvid.so()(64bit) You could try using --skip-broken to work around the problem Thanks ... -- Patrick

On Mon, Jan 07, 2013 at 09:39:16AM -0500, George Galt wrote: > On Sun, Jan 6, 2013 at 9:36 PM, Patrick <patman(a)aracnet.com&gt; wrote: > > > Did you have any problems with libnvcuvid.so? > > > ATrpms had this same issue last month. The issue is that rpm inspects the > binaries and builds a list of things required and things that the package > provides. For some reason, it generates a dependency of > libnvcuvid.so()(64-bit) but builds a list of the things provided of > libnvcuvid.so.1(64-bit) (IIRC). > > Look at the ATrpms dev list for how to fix this in the .spec file: > http://lists.atrpms.net/pipermail/atrpms-devel/2012-December/thread.html > > In particular, I believe the suggestion here: > http://lists.atrpms.net/pipermail/atrpms-devel/2012-December/002931.htmlwas > the ultimate fix. You could also look at the spec file in ATrpms for > ideas: > http://dl.atrpms.net/src/f17-x86_64/atrpms/stable/nvidia-graphics310.19-3... > > FYI, I had no problem building this for F18 without applying the above fix, > so I'm not sure if there is something that is different with Fedora <= 17 > that is causing this problem. I tried adding "Autoreq: 0" to the spec file, and it made no difference. I also tried adding another filter (though the existing one looks like it should work correctly too) to the spec file, like this: %filter_from_requires /^libnvcuvid\.so/d; That also made no difference. I finally just installed using rpm with --nodeps, and it's booted and working fine so far. Hopefully my xorg execessive cpu usage problem will be solved, I won't know until the system has been up for a while. -- Patrick