From Gentoo Wiki
Jump to: navigation, search

Laptops with Nvidia graphics cards using Nvidia Optimus can be configured to render scenes on the discrete Nvidia GPU (Graphics Processing Unit) card using x11-drivers/nvidia-drivers and copy the rendered scenes to the Intel GPU using XRandR.

This article is about native Optimus support using the official Nvidia drivers (x11-drivers/nvidia-drivers) – it is not about bumblebee; bumblebee is not used in the following configuration.



Since Nvidia Optimus will be using the integrated Intel graphics for modesetting, the following kernel options will need to be enabled:

KERNEL Linux kernel 4.3.3+
Device Drivers  --->
   Graphics Support  --->
      Direct Rendering Manager (Xfree86 4.1.0 and higher DRI support)   --->
         [*]   Enable legacy fbdev support for your modesetting driver 
      <*> Intel 8xx/9xx/G3x/G4x/HD Graphics
         [*]   Enable preliminary support for prerelease Intel hardware by default
In the case that something should go wrong, it is recommended to have live media to assist in reverting any changes. Having a Gentoo Minimal Install CD, SystemRescueCD (which is a Gentoo based recovery image), or a LiveUSB around work nicely for this purpose. If you choose to proceed without having a "just in case" alternative boot method proceed with extreme caution!
At the time this article was written version 343.36 of x11-drivers/nvidia-drivers was the most recent (stable) version of the driver in the Portage tree, therefore examples that reference a specific version will presume version 343.36 is being used. When a newer version of the driver is released, or if an older version is selected, simply substitute 343.36 for the desired version.

USE flags

USE flags for x11-drivers/nvidia-drivers NVIDIA Accelerated Graphics Driver

X Install the X.org driver, OpenGL libraries, XvMC libraries, and VDPAU libraries local
acpi Add support for Advanced Configuration and Power Interface global
compat Install non-GLVND libGL for backwards compatibility local
driver Install the kernel driver module local
gtk3 Install nvidia-settings with support for GTK+ 3 local
kms Enable support for kernel mode setting (KMS) local
multilib On 64bit systems, if you want to be able to compile 32bit and 64bit binaries global
pax_kernel PaX patches from the PaX project local
static-libs Build static versions of dynamic libraries as well global
tools Install additional tools such as nvidia-settings local
uvm Install the Unified Memory kernel module (nvidia-uvm) for sharing memory between CPU and GPU in CUDA programs local
wayland Enable dev-libs/wayland backend global


Installing Nvidia drivers is easy, run the following:

root #emerge --ask x11-drivers/nvidia-drivers
Since xorg 1.18 if the intel screen is always disabled enable glamor USE flag on xorg-server


Configuring a system to use Nvidia's proprietary driver is not easy as the installation. There are several configuration files that will need to be modified in order for a system to work properly.

Kernel modules

If the user has chosen to not use built-in modules, then the init system should load the necessary modules on system boot. If /proc/config.gz is available, this can verified by running the following command:

user $zgrep "CONFIG_MODULES=" /proc/config.gz

If the output returns CONFIG_MODULES set to N, then the kernel will need recompiled with support to load modules. Information about that can be found over here. After module loading support has been added, return to this article and continue reading.

Create a new file called nvidia.conf in the /etc/modules-load.d directory. It should contain the nvidia module name:

FILE /etc/modules-load.d/nvidia.conf


Verify the modules-load init script has been added to the boot runlevel (it should be by default, but double check):

root #rc-update add modules-load boot


Check the status of the systemd-modules-load.service to verify things are running smoothly. If issues arise this service unit will be the place to check:

root #systemctl start systemd-modules-load.service


The best way to set the system's xorg.conf correctly would be to read the documentation Nvidia has provided. The documentation can be found in a couple of locations. To save time, consider reading only the pages on Optimus and XRandR, as they are vital to correct configuration. If the driver has already been emerged (done in the installation step above), the documentation can be found locally at /usr/share/doc/nvidia-drivers-343.36/README.bz2.

Example: Use the less command to read the local documentation:

user $less /usr/share/doc/nvidia-drivers-343.36/README.bz2

It is also possible to read the documentation at Nvidia's website by following these (external) links:



For a quick example here on the wiki, view this xorg.conf file.

xorg server 1.17.2 or higher

If X.Org X server version 1.17.2 or higher is installed ([1])

FILE /etc/X11/xorg.conf.d/20-nvidia.conf
Section "Module"
    Load "modesetting"

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "<BusID for NVIDIA device here>"
    Option "AllowEmptyInitialConfiguration"

How to find the busid

Using a specific monitor via EDID

It is probably best to first try a simple configuration first like described in the Nvidia driver manual:


Saving the monitor's EDID

Ensure the currently running kernel has CONFIG_I2C_CHARDEV enabled and the resulting i2c-dev module loaded or compiled monolithically for read-edid to work.

Some laptops/notebooks may benefit from saving the EDID screen information to a file so it can be passed to the Intel modesetting driver. The EDID information can be saved using the read-edid utility.

root #emerge --ask x11-misc/read-edid
root #get-edid > /lib/firmware/edid/1920x1080_Clevo_W670SR.bin

The EDID information is provided to the Intel GPU (Graphics Processing Unit) by specifying its location in the kernel boot parameter:


If the GRUB2 bootloader is being used, this can be configured in the file /etc/default/grub

FILE /etc/default/grub

Note: If using Sabayon Linux, the kernel boot parameters should be specified in the /etc/default/sabayon-grub file instead of /etc/default/grub file.

Example xorg.conf for EDID

See EDID xorg.conf Example to view an example xorg.conf using an EDID for a specific monitor.

Before starting X

Per Nvidia's instructions, the following commands are required before starting X:

CODE XRandR commands:
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto

This is to say any Display Manager that starts X-Windows then asks the user to log in will result in a black screen unless the above xrandr commands are run before asking the user to log in.

The xrandr commands must be added to the system's X session start up scripts (such as ~/.xinitrc) in order for the X display to start using modesetting. Failure to do so will result in a black screen.

NOTE: If you get a black screen with no back-lighting from the previous steps, creating .xsessionrc and placing the xinitrc commands in there COULD fix it.

Use the xrandr command to find the appropriate graphics device:

root #xrandr --listproviders

Display manager configuration

The following shows a list of where to add the required xrandr commands, sorted by desktop.

For some window managers, the config files are not located under /etc. In case of updates of these window managers, your edits may get lost causing black screens. In order to get warned by emerge if it wants to override your changes, config-protect the corresponding files to your /etc/portage/make.conf like, e.g. in case of SDDM:
FILE /etc/portage/make.confProtect your changes from updates


root #emerge --ask sys-apps/qingy
For menu option (A) KDE-4

Add the xrandr commands to the end of the /etc/X11/Sessions/KDE-4 file:

FILE /etc/X11/Sessions/KDE-4KDE-4's X session file
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
For menu option (B) your .xsession

Add the xrandr commands to the end of the ~/.xsession file.

Qingy DirectFB

In the /etc/directfbrc configuration file. It is necessary to set the busid variable to the BusID of the Intel graphics card as reported by the lspci command:

root #lspci

For example, if lspci says the Intel graphics card is on BusID 00:02.0, then add the following line to {{Path}/etc/directfbrc}}

FILE /etc/directfbrc

The Console Display Manager (CDM)

root #emerge --ask x11-misc/cdm

Add the xrandr commands to ~/.xinitrc file:

KDE Display Manager (KDM)

root #emerge --ask kde-base/kdm

Add the xrandr commands to the /usr/share/config/kdm/Xsetup file and protect them like described above.

Simple Desktop Display Manager (SDDM)

Add the xrandr commands to the /usr/share/sddm/scripts/Xsetup file and protect them like described above.

Mint Desktop Manager (MDM)

For Mint Desktop Manager fetch the ebuild and install gnome-base/mdm:

root #emerge --ask gnome-base/mdm

Add the xrandr commands to the /etc/X11/mdm/Init/Default file:

X Display Manager (XDM)

Add the xrandr commands to the /usr/lib/X11/xdm/Xsetup_0 file and protect them like described above.

NOTE: if the system is a 32-bit system, add the commands to the /usr/lib64/X11/xdm/Xsetup_0 file.

If using a 64-bit system, edit the /etc/X11/xdm/xdm-config configuration file and change the following line to point to the Xsetup_0 file created above:

CODE X Display Manager Example
DisplayManager._0.setup: /usr/lib/X11/xdm/Xsetup_0

Gnome Display Manager (GDM)

For GDM to work with Optimus, add the xrandr commands to /etc/gdm/Init/Default:

FILE /etc/gdm/Init/DefaultExample
# Stolen from the debian kdm setup, aren't I sneaky
# Plus a lot of fun stuff added
#  -George


exec xrandr --setprovideroutputsource modesetting NVIDIA-0
exec xrandr --auto


Since there are many files to configure and because the Nvidia's proprietary support for Optimus in Linux is buggy, it is rather easy to create a faulty Optimus configuration. It is possible something was typed incorrectly, or a certain configuration was not compatible with the hardware being used. Whatever the case, a broken configuration means that debugging is required.

To debug, carefully read the logs from dmesg (/var/log/dmesg) and Xorg (/var/log/Xorg.0.log) with a favorite text editor; they are the best indicators to find issues. If something irregular is discovered, make changes to the respective configuration files. Other areas to inspect for debugging include any of the configuration files that were modified through the course of this article (the kernel's {Path|.config}}, kernel boot parameters passed at /etc/default/grub, the Xorg's /etc/X11/xorg.conf file, etc.). Continue checking the files as necessary then reboot the system and try again. Many attempts may be required in order to obtain a working configuration! It is not exciting process; time could be spent on something more interesting, but if debugging is required in order to get Optimus working then it needs to happen.

In a shell to quickly find warnings and errors: grep -E 'WW|EE' /var/log/Xorg.0.log
When viewing /var/log/Xorg.0.log using a text editor such as app-editors/vim, search for (WW) or (EE) to quickly find warnings and errors. This will speed up debugging time considerably.

To aid in distinguishing between important and unimportant messages in /var/log/dmesg and /var/log/Xorg.0.log files, working examples have been provided at these sub-articles:

Specific models

  • Lenovo Thinkpad W530 - In short, for all the screens to work, set the configuration to discrete mode in the motherboard firmware.



See also

External resources