Nvidia module arch linux

Nouveau

This article covers the open-source Nouveau driver for NVIDIA graphics cards. For information about the proprietary driver, see NVIDIA.

Find your card’s code name (a more detailed list is available on Wikipedia), and compare it with the feature matrix for supported features.

Installation

Install the mesa package, which provides the DRI driver for 3D acceleration.

• For 32-bit application support, also install the lib32-mesa package from the multilib repository.
• For the DDX driver (which provides 2D acceleration in Xorg), install the xf86-video-nouveau package.

Note: It has been suggested that not installing the xf86-video-nouveau driver, and instead falling back on the modesetting driver for NV50 (G80) and newer hardware is beneficial. For example see a user report from 2021.

Loading

The Nouveau kernel module should load automatically on system boot. If it does not happen, then:

• Make sure you do not have nomodeset or vga= as a kernel parameter, since Nouveau requires kernel mode-setting.
• Also, check that you do not have Nouveau disabled using any modprobe blacklisting technique within /etc/modprobe.d/ or /usr/lib/modprobe.d/ .
• If everything above still fails to load nouveau, check dmesg for an opcode error. Add nouveau.config=NvBios=PRAMIN to your Kernel parameters to prevent module unloading.[1]
• Check if /etc/X11/xorg.conf or any file in /etc/X11/xorg.conf.d/ exists and is referencing the nvidia driver. It is probably a good idea to rename the file.

Enable early KMS

This article or section is being considered for removal.

Reason: Since mkinitcpio v32, the kms hook is included by default, therefore most setups will have early loading enabled by default. (Discuss in Talk:Nouveau)

Kernel mode setting (KMS) is required by the Nouveau driver. By default, the KMS is done after the other kernel modules are loaded. You will see the text «Loading modules» and the size of the text may change, possibly with an undesirable flicker. See the Nouveau KernelModeSetting page for more details.

It is also possible to start the KMS as early as possible in the boot process, when the initramfs is loaded.

To do this, add nouveau to the MODULES array in /etc/mkinitcpio.conf (module names are separated by spaces):

If you are using a custom EDID file, you should embed it into initramfs as well:

FILES="/lib/firmware/edid/your_edid.bin"

Tips and tricks

Keep NVIDIA driver installed

If you want to keep the proprietary NVIDIA driver installed (and are not using OpenGL), but want to use the Nouveau driver, comment out nouveau blacklisting in /etc/modprobe.d/nouveau_blacklist.conf , /usr/lib/modprobe.d/nvidia.conf , or /usr/lib/modprobe.d/nvidia-dkms.conf modifying it as follows:

And tell Xorg to load nouveau instead of nvidia by creating the file /etc/X11/xorg.conf.d/20-nouveau.conf with the following content:

Section "Device" Identifier "Nvidia card" Driver "nouveau" EndSection

If you already used the NVIDIA driver, and want to test Nouveau without reboot, make sure the ‘nvidia’ module is no longer loaded:

Then load the ‘nouveau’ module:

And check that it loaded fine by looking at kernel messages:

Installing the latest development packages

To get the latest Nouveau improvements

Dual head

See Multihead#RandR how to setup multiple monitors by using RandR.

Setting console resolution

You can pass the resolution to nouveau with the video= kernel line option (see KMS).

Power management

The lack of proper power management in the nouveau driver is one of the most important causes of performance issues, since most cards will remain in their lower power state with lower clocks during their use. Experimental support for GPU reclocking is available for some cards (see the Nouveau PowerManagement page) and since kernel 4.5 can be controlled through a debugfs interface located at /sys/kernel/debug/dri/*/pstate .

For example, to check the available power states and the current setting for the first card in your system, run:

# cat /sys/kernel/debug/dri/0/pstate

It is also possible to manually set/force a certain power state by writing to said interface:

# echo pstate > /sys/kernel/debug/dri/0/pstate

Warning: The support for reclocking is highly experimental. Manually setting the power state may hang your system, cause corruption or overheat your card.

Fan control

If it is implemented for your card, you can configure fan control via /sys .

$ find /sys -name pwm1_enable /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/hwmon/hwmon1/pwm1_enable $ readlink /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/driver ../../../../bus/pci/drivers/nouveau

pwm1_enable can be set to 0, 1 or 2 meaning NONE, MANUAL and AUTO fan control. If set to manual fan control, you can set pwm1 manually, for example to 40 for 40%.

You can also set it by udev rule:

$ cat /etc/udev/rules.d/50-nouveau-hwmon.rules ACTION=="add", SUBSYSTEM=="hwmon", DRIVERS=="nouveau", ATTR="2"

Optimus

You have two solutions to use Optimus on a laptop (aka hybrid graphics, when you have two GPUs on your laptop): bumblebee and PRIME

Vertical Sync

Xorg compositors are prone to show issues with Nouveau. Unlike most of them, Picom offers lots of options to tweak for a smoother and tearing free result. A configuration which is expected to deliver a good result would be the following:

$ picom -b --unredir-if-possible --backend xr_glx_hybrid --vsync --use-damage --glx-no-stencil

Tip: Do not forget to turn off compositing of your DE’s window manager like KWin when using a different compositor.

Troubleshooting

Add drm.debug=14 and log_buf_len=16M to your kernel parameters to turn on video debugging:

$ startx -- -logverbose 9 -verbose 9

View loaded video module parameters and values:

Disable MSI

If you are still having problems loading the module or starting the X server, append nouveau.config=NvMSI=0 to your Kernel parameters.

Phantom output issue

It is possible for the nouveau driver to detect «phantom» outputs. For example, both VGA-1 and LVDS-1 are shown as connected but only LVDS-1 is present.

This causes display problems and/or prevent suspending on lid closure.

Kernel parameters

The problem can be overcome by disabling the phantom output (VGA-1 in the examples given) with Kernel parameters:

The nouveau kernel module also has an option to disable TV-out detection [2]:

Xorg configuration

The phantom output can be disabled in Xorg by adding the following to /etc/X11/xorg.conf.d/20-nouveau.conf :

Section "Monitor" Identifier "VGA-1" Option "Ignore" "1" EndSection

Xrandr

This can be added to the xinit configuration.

Random lockups with kernel error messages

Specific Nvidia chips with Nouveau may give random system lockups and more commonly throw many kernel messages, seen with dmesg. Try adding the nouveau.noaccel=1 kernel parameter. See Fedora:Common kernel problems#Systems with nVidia adapters using the nouveau driver lock up randomly for more information.

As an alternative, you can also use the QT_XCB_FORCE_SOFTWARE_OPENGL=1 environment variable to disable OpenGL acceleration in Qt applications.

Flat Panel Table Invalid

NVIDIA graphics cards with recent chipsets can cause startup issues — this includes X11 being unable to start and lspci freezing indefinitely[3][4][5][6][7].

This can break live distributions/installation media. This can be detected either by running lspci, or checking the systemd journal for the error:

nouveau E[ DRM]Pointer to flat panel table invalid

The system may start if the Nouveau driver is disabled by passing the following kernel parameters:

The Nouveau driver can then be loaded using

The system should then function correctly. If you have another Nvidia graphics card, or just want to be safe, you can disable the offending card using:

$ echo 1 > /sys/bus/pci/devices/[card device id]/remove

Источник

NAME

nvidia-modprobe — Load the NVIDIA kernel module and create NVIDIA character device files.

SYNOPSIS

nvidia-modprobe [options]
nvidia-modprobe [options] —create-nvidia-device-file=MINOR-NUMBER
nvidia-modprobe [options] —module-instance=MODULE-INSTANCE

DESCRIPTION

The nvidia-modprobe utility is used by user-space NVIDIA driver components to make sure the NVIDIA kernel module is loaded and that the NVIDIA character device files are present. These facilities are normally provided by Linux distribution configuration systems such as udev. When possible, it is recommended to use your Linux distribution’s native mechanisms for managing kernel module loading and device file creation. This utility is provided as a fallback to work out-of-the-box in a distribution-independent way.

When installed by nvidia-installer , nvidia-modprobe is installed setuid root.

Users should not normally need to run nvidia-modprobe by hand: the NVIDIA user-space driver components will fork(2)/exec(3) it when needed.

When run without any options, nvidia-modprobe will load the NVIDIA kernel module and then exit. When the —module-instance option is specified on systems with multiple NVIDIA kernel modules, nvidia-modprobe will load the corresponding NVIDIA kernel module and then exit. When the —create-nvidia-device-file option is specified, nvidia-modprobe will also create the requested device file.

OPTIONS

-v, —version Print the utility version and exit. -h, —help Print usage information for the command line options and exit. -c MINOR-NUMBER, —create-nvidia-device-file=MINOR-NUMBER Create the NVIDIA device file with the given minor number; this option can be specified multiple times to create multiple NVIDIA device files.

ADVANCED OPTIONS

-u, —unified-memory Load the NVIDIA Unified Memory kernel module or create device files for it, instead of the NVIDIA kernel module. -m, —modeset Load the NVIDIA modeset kernel module and create its device file. -s, —nvswitch Load the NVIDIA kernel module and create the NVSwitch device files for each minor number specified using the -c flag. -l, —nvlink Load the NVIDIA kernel module and create the NVLink control device file. -f NVIDIA-CAPABILITY-DEVICE-FILE, —nvidia-capability-device-file=NVIDIA-CAPABILITY-DEVICE-FILE Create the NVIDIA capability device files with the given capability /proc file path. This option can be specified multiple times to create multiple NVIDIA capability device files.

EXAMPLES

nvidia-modprobe Run `/sbin/modprobe nvidia` nvidia-modprobe -c 0 -c 1 Run `/sbin/modprobe nvidia` and create /dev/nvidia0 and /dev/nvidia1 nvidia-modprobe -i 0 Run `/sbin/modprobe nvidia0`

AUTHOR

Andy Ritger
NVIDIA Corporation

COPYRIGHT

Copyright © 2013 NVIDIA Corporation.

Package name: extra/nvidia-utils Version: 535.54.03-1 Upstream: http://www.nvidia.com/ Licenses: custom Manuals: /listing/extra/nvidia-utils/ Table of contents

Powered by archmanweb, using mandoc for the conversion of manual pages.

The website is available under the terms of the GPL-3.0 license, except for the contents of the manual pages, which have their own license specified in the corresponding Arch Linux package.

Источник