Steam for Linux > NVidia Graphics Cards > Détails du sujet
664a5b35f8c297b3fb89137866970705 2 fév 2013 à 19h22
[SOLVED]Primusrun fake launch?
Linux 3.7.5-1-ARCH #1 SMP PREEMPT x86_64 GNU/Linux

Running ArchLinux, using Bumblebee & bbswitch on the GeForce GT 630M

When using primusrun to launch Steam or any Steam game, the following information is known:
- The application launches without an issue.
- The output of /proc/acpi/bbswitch remains "OFF"
- The performance of the application remains the same as if it were launched normally, i.e. it is running on Intel HD integrated graphics.

When primusrun is used to launch glxspheres:
- The performance is significantly better than the integrated graphics card.
- glxspheres acknowledges the the Nvidia card as its openGL renderer.
- The output of /proc/acpi/bbswitch is "ON"

No matter what I do to try to launch TF2 using primusrun, it does not appear to use the dedicated card. It always appears to use the integrated graphics.

1) Is there any way to determine from within TF2 what card is being used? (Probably not)
2) Should I disregard the /proc/acpi/bbswitch reading? (It is substantiated by the performance levels, so it's probably right)
3) Is there something I'm missing about using primusrun?

Note: I installed Bumblebee by following the ArchLinux Bumblebee wiki page *to a T*. This is likely the reason I cannot use optirun to start TF2 and instead encounter 'glGetError() not implemented, update your OpenGL' or similar.
https://wiki.archlinux.org/index.php/Bumblebee#Installation
Dernière modification de 664a5b35f8c297b3fb89137866970705; 4 fév 2013 à 13h26
Affichage des commentaires 1 à 2 sur 2
< >
kwahoo 4 fév 2013 à 9h21 
glxspheres is 64-bit, while Team Fortress 2 is 32-bit. Have you lib32-primus-git installed?

Primusrun works fine on my system (645m, U12.10 x86-64) both in TF2 and SS3. The output of /proc/acpi/bbswitch is "ON".

I'm using string
LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 primusrun %command%
664a5b35f8c297b3fb89137866970705 4 fév 2013 à 13h26 
Adding the string you use to my own launch commands fixed the issue; /proc/acpi/bbswitch now shows "ON". Thank you!
Not sure how I would have found/figured that out myself, though.
Affichage des commentaires 1 à 2 sur 2
< >
Par page : 15 30 50