Wiki Table of Contents

2 graphics drivers


If your system has both a discrete graphics card, typically Intel and an nVidia graphics card, you can install the nvidia driver using the Nvidia Graphics Installer found in MX Tools. Your card will be detected and the app will offer to install the driver including Bumblebee. The process may take some time. Upon completion reboot.


To run an application using the nVidia card issue the command “primusrun <app name>” in a user terminal. The application will open and use the nvidia card.

If you want to check if properly installed issue the command “primusrun inxi -G” in a user terminal. It will show the GlX Renderer with your nvidia card designation. If run as “inxi -G” GLX Renderer will show the Intel card.

Alternately the command “optirun <app name>” can be used. optirun can be run with options. Issue the command “optirun -h” in a user terminal for help.


Enable NVIDIA card after waking from suspend (from Arch WIki)

The bumblebee daemon may fail to activate the graphics card after suspending. A possible fix involves setting bbswitch as the default method for power management:

  • open /etc/bumblebee/bumblebee.conf in Leafpad as root
  • Find the section with and change the PM Method; currently lines 58 or 69:


  • Save and close

Project Bumblebee wiki

For more information refer to the Bumblebee wiki. However use the installation procedure detailed above.

9 thoughts on “2 graphics drivers”

  1. If:
    1. optirun works on your machine (test with optirun glxgears) but primusrun has issues locating
    2. you are using non-free NVIDIA drivers, not noveau drivers (check this using optirun inxi -Gx, where NVIDIA drivers will look like OpenGL: renderer: GeForce GTX 950M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.116 direct render: Yes)
    then you may be able to fix primusrun by appending `:/usr/lib/x86_64-linux-gnu` to LibraryPath in /etc/bumblebee/bumblebee.conf. (If not the path /usr/lib/x86_64-linux-gnu, you can try to find with sudo find . -name “” and use this path instead.)
    Once doing this, if primusrun starts, but displays a black window (with primusrun glxgears for example), you may be able to fix this by prefixing primusrun with __GLVND_DISALLOW_PATCHING=1. That is, you’d call __GLVND_DISALLOW_PATCHING=1 primusrun glxgears instead of primusrun glxgears.

    I have been able to reproduce this issue on a fresh live USB (with persist_static) of MX 18.3. I’m not sure what causes it, but serves as a fix.

    • This has been very helpful.

      In my case, I have Geforce GT 950M, using primus-vk-nvidia from ahs repo.

      pvkrun was _broken_ with Steam, until I (actually prepended) /usr/lib/x86_64-linux-gnu to LibraryPath in /etc/bumblebee/bumbleebee.conf. This should be documented even more prominently I think.

      Thanks a lot for the solution.

    • This was probably posted some time ago – but, I was having a hell of a time with this even with the above fixes noted. I wound up installing all the primus stuff under debian backports (letting it overwrite the bumblebee.conf) and was then able primusrun glxspheres64. For my steam games I just add “primusrun %command%” to the launch options and everything works as expected. Hope this helps anyone fighting with this.

      MX 19.2 – Oct 2020.
      Lenovo T440p Nvidia 730m

  2. Hi There,
    I’m about to install MX Linux on a PC with a Gigabyte Motherboard GA-H61M-S2PV which has 8GB of RAM and an Intel i3 processor. (I’m just about to ditch Windows ! )
    I have two graphics cards available:-
    1. A Radeon HD 6570
    or 2. An Nvidia GTX 550Ti

    My question is: which one of the above Graphics Cards will be “seen” or installed by MX Linux without drama?


Leave a Comment

MX Linux