protonscr

Fedora 18 x86_64 primusrun game black screen

steamclosed NVIDIA driversreviewedbumblebee
ValveSoftware/steam-for-linux#2571 · opened 2013-06-07 by Sammidysam · updated 2013-06-07 · 3 comments · github
1 matching comments, n / p to jump
SSammidysam 2013-06-07 github

Situation:

  • I have Bumblebee and Primus set up. When I run glxspheres via primusrun I get a nice consistent 60 fps. Also, if I run Minecraft with primusrun I again get a nice consistent 60 fps. However, if I set a launch configuration for a game such as Osmos or Cogs to primusrun %command%, the game results in a black screen. If I don't and it uses my integrated graphics, it runs normally. For Osmos it can run under integrated graphics, but I want to be able to run other games with my NVIDIA card, when it is needed. I use the proprietary drivers.

Specs:

  • Processor: 8-core Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
    • Steam Information:
      • Vendor:  GenuineIntel
        Speed: 2001 Mhz
        8 logical processors
        4 physical processors
        HyperThreading:  Supported
        FCMOV:  Supported
        SSE2:  Supported
        SSE3:  Supported
        SSSE3:  Supported
        SSE4a:  Unsupported
        SSE41:  Supported
        SSE42:  Supported
        
  • Memory: 5.8 GB RAM, 5.8 GB swap (though I'm pretty sure swap has not been used at all in my time with Fedora 18)
  • Distro: Fedora 18 x86_64 (64-bit)
    • Steam Information:
      • Linux (64 bit)
        Kernel Name:  Linux
        Kernel Version:  3.9.4-200.fc18.x86_64
        X Server Vendor:  Fedora Project
        X Server Release:  11303000
        X Window Manager:  GNOME Shell
        Steam Runtime Version:  steam-runtime-release-i386_2013-05-08
        
  • GPU: NVIDIA GeForce GT 555M (primusrun glxspheres listed OpenGL Renderer: GeForce GT 555M/PCIe/SSE2) and integrated graphics
    • Steam Information (when running via command steam):
      • Driver:  Intel Open Source Technology Center Mesa DRI Intel(R) Sandybridge Mobile
        Driver Version:  3.0 Mesa 9.2.0
        Desktop Color Depth: 24 bits per pixel
        Monitor Refresh Rate: 59 Hz
        VendorID:  0x10de
        DeviceID:  0xdcd
        Number of Monitors:  1
        Number of Logical Video Cards:  2
        Primary Display Resolution:  1366 x 768
        Desktop Resolution: 1366 x 768
        Primary Display Size: 12.17" x 6.85"  (13.94" diag)
                                        30.9cm x 17.4cm  (35.4cm diag)
        Primary VRAM Not Detected
        
    • Steam Information (when running via command primusrun steam):
      • When I run Steam via command primusrun steam I get the error message OpenGL GLX context is not using direct rendering, which may cause performance problems.
      • Driver:  Intel Open Source Technology Center Mesa DRI Intel(R) Sandybridge Mobile 
        Driver Version:  1.4 (3.0 Mesa 9.2.0)
        Desktop Color Depth: 24 bits per pixel
        Monitor Refresh Rate: 59 Hz
        VendorID:  0x10de
        DeviceID:  0xdcd
        Number of Monitors:  1
        Number of Logical Video Cards:  2
        Primary Display Resolution:  1366 x 768
        Desktop Resolution: 1366 x 768
        Primary Display Size: 12.17" x 6.85"  (13.94" diag)
                                        30.9cm x 17.4cm  (35.4cm diag)
        Primary VRAM Not Detected
        
      • That definitely looks like a problem. It seems to be using my Intel driver when in primusrun, or at least it detects the Intel driver as being used.

Logs:

  • Steam launched with command steam thus using my integrated graphics. Launch Osmos with no special launch configuration, all goes well, exit, then edit launch configuration to primusrun %command% and terminate game due to black screen after a wait.
  • Steam launched with command primusrun steam thus using the NVIDIA driver. Launch Osmos with no special launch configuration, and after awhile terminate game due to black screen.

Please help! Thanks!

Ggdrewb-valve maintainer 2013-06-07 github

It sounds like you have a configuration issue as the "not using direct rendering" message usually means that OpenGL is confused and not able to make a good connection between the app and the driver. Note that Steam is a 32-bit app so you need to have all of your 32-bit binaries set up properly for things to work. When you run glxspheres you're probably running the 64-bit version and so you're not going through the same path as Steam or a 32-bit game.

As for what exactly your configuration is I can't say, so all the advice I can give is double-check your 32-bit setup and try running 32-bit apps.

SSammidysam 2013-06-07 github

Good point! I had not installed the necessary packages for 32-bit support. Will do now and will test.

SSammidysam 2013-06-07 github

It works! Installing the 32-bit version of VirtualGL and primus fixed the issue. I was able to confirm this as with Cogs the menu was way faster than before as it was incredibly slow on integrated graphics and when I used the command primusrun steam it had the correct driver name.

Thanks very much! I will definitely need to read the tutorial more thoroughly next time.

Nothing extracted yet.