NVIDIA/Troubleshooting (Русский)
Смотрите главную статью NVIDIA (Русский).
Contents
- 1 Wayland (gdm) рушится после установки nvidia-libgl
- 2 Поврежденный экран: проблема "Шести экранов"
- 3 Ошибка ввода/вывода '/dev/nvidia0'
- 4 Crashing in general
- 5 Bad performance after installing a new driver version
- 6 CPU spikes with 400 series cards
- 7 Laptops: X hangs on login/out, worked around with Ctrl+Alt+Backspace
- 8 No screens found on a laptop/NVIDIA Optimus
- 9 Screen(s) found, but none have a usable configuration
- 10 Blackscreen at X startup / Machine poweroff at X shutdown
- 11 Backlight is not turning off in some occasions
- 12 Full system freeze using Flash
- 13 Xorg fails to load or Red Screen of Death
- 14 Black screen on systems with Intel integrated GPU
- 15 Black screen on systems with VIA integrated GPU
- 16 X fails with "no screens found" with Intel iGPU
- 17 Xorg fails during boot, but otherwise starts fine
- 18 Flash video players crashes
- 19 xrandr BadMatch
- 20 Override EDID
- 21 Overclocking with nvidia-settings GUI not working
- 22 Avoid screen tearing
- 23 Modprobe Error: "Could not insert 'nvidia': No such device" on linux >=4.8
Wayland (gdm) рушится после установки nvidia-libgl
В некоторых процессорах Intel устаревший микрокод может привести к нестабильности работы с Wayland когда установлен драйвер nvidia, вызывая крах gdm.
Обновление микрокода должно решить проблему.
Поврежденный экран: проблема "Шести экранов"
Некоторые пользователи, использующие GeForce GT 100M, могут столкнуться с повреждением экрана при запуске X, разделенным на 6 секций с ограниченным разрешением в 640x480. Похожая проблема недавно была замечена с Quadro 2000 и мониторами высокого разрешения.
Для решения проблемы, укажите значение NoTotalSizeCheck
режима проверки в разделе Device
:
Section "Device" ... Option "ModeValidation" "NoTotalSizeCheck" ... EndSection
Ошибка ввода/вывода '/dev/nvidia0'
This error can occur for several different reasons, and the most common solution given for this error is to check for group/file permissions, which in almost every case is not the problem. The NVIDIA documentation does not talk in detail on what you should do to correct this problem but there are a few things that have worked for some people. The problem can be a IRQ conflict with another device or bad routing by either the kernel or your BIOS.
First thing to try is to remove other video devices such as video capture cards and see if the problem goes away. If there are too many video processors on the same system it can lead into the kernel being unable to start them because of memory allocation problems with the video controller. In particular on systems with low video memory this can occur even if there is only one video processor. In such case you should find out the amount of your system's video memory (e.g. with lspci -v
) and pass allocation parameters to the kernel, e.g. for a 32-bit kernel:
vmalloc=384M
If running a 64bit kernel, a driver defect can cause the NVIDIA module to fail initializing when IOMMU is on. Turning it off in the BIOS has been confirmed to work for some users. [1]User:Clickthem#nvidia module
Another thing to try is to change your BIOS IRQ routing from Operating system controlled
to BIOS controlled
or the other way around. The first one can be passed as a kernel parameter:
PCI=biosirq
The noacpi
kernel parameter has also been suggested as a solution but since it disables ACPI completely it should be used with caution. Some hardware are easily damaged by overheating.
Crashing in general
- Try disabling
RenderAccel
in xorg.conf. - If Xorg outputs an error about
"conflicting memory type"
or"failed to allocate primary buffer: out of memory"
, or crashes with a "Signal 11" while using nvidia-96xx drivers, addnopat
to your kernel parameters. - If the NVIDIA compiler complains about different versions of GCC between the current one and the one used for compiling the kernel, add in
/etc/profile
:
export IGNORE_CC_MISMATCH=1
- If Xorg is crashing , try disabling PAT. Pass the argument
nopat
to kernel parameters.
More information about troubleshooting the driver can be found in the NVIDIA forums.
Bad performance after installing a new driver version
If FPS have dropped in comparison with older drivers, first check if direct rendering is turned on (glxinfo is included in mesa-demos):
$ glxinfo | grep direct
If the command prints:
direct rendering: No
then that could be an indication for the sudden FPS drop.
A possible solution could be to regress to the previously installed driver version and rebooting afterwards.
CPU spikes with 400 series cards
If you are experiencing intermittent CPU spikes with a 400 series card, it may be caused by PowerMizer constantly changing the GPU's clock frequency. Switching PowerMizer's setting from Adaptive to Performance, add the following to the Device
section of your Xorg configuration:
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"
Laptops: X hangs on login/out, worked around with Ctrl+Alt+Backspace
If, while using the legacy NVIDIA drivers, Xorg hangs on login and logout (particularly with an odd screen split into two black and white/gray pieces), but logging in is still possible via Ctrl+Alt+Backspace
(or whatever the new "kill X" key binding is), try adding this in /etc/modprobe.d/modprobe.conf
:
options nvidia NVreg_Mobile=1
One user had luck with this instead, but it makes performance drop significantly for others:
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660 NVreg_SoftEDIDs=0 NVreg_Mobile=1
Note that NVreg_Mobile
needs to be changed according to the laptop:
- 1 for Dell laptops.
- 2 for non-Compal Toshiba laptops.
- 3 for other laptops.
- 4 for Compal Toshiba laptops.
- 5 for Gateway laptops.
See NVIDIA Driver's README: Appendix K for more information.
No screens found on a laptop/NVIDIA Optimus
On a laptop, if the NVIDIA driver cannot find any screens, you may have an NVIDIA Optimus setup : an Intel chipset connected to the screen and the video outputs, and a NVIDIA card that does all the hard work and writes to the chipset's video memory.
Check if $ lspci | grep VGA
outputs something similar to:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation Device 0df4 (rev a1)
NVIDIA drivers now offer Optimus support since 319.12 Beta [2] with kernels above and including 3.9.
Another solution is to install the Intel driver to handle the screens, then if you want 3D software you should run them through Bumblebee to tell them to use the NVIDIA card.
Possible Workaround
Enter the BIOS and changed the default graphics setting from 'Optimus' to 'Discrete' and the install NVIDIA drivers (295.20-1 at time of writing) recognized the screens.
Steps:
- Enter BIOS.
- Find Graphics Settings (should be in tab Config > Display).
- Change 'Graphics Device' to 'Discrete Graphics' (Disables Intel integrated graphics).
- Change OS Detection for Nvidia Optimus to "Disabled".
- Save and exit.
Tested on a Lenovo W520 with a Quadro 1000M and Nvidia Optimus
Screen(s) found, but none have a usable configuration
Sometimes NVIDIA and X have trouble finding the active screen. If your graphics card has multiple outputs try plugging your monitor into the other ones. On a laptop it may be because your graphics card has vga/tv outs. Xorg.0.log will provide more info.
Another thing to try is adding invalid "ConnectedMonitor" Option
to Section "Device"
to force Xorg throws error and shows you how correct it.
Here
more about ConnectedMonitor setting.
After re-run X see Xorg.0.log to get valid CRT-x,DFP-x,TV-x values.
nvidia-xconfig --query-gpu-info
could be helpful.
Blackscreen at X startup / Machine poweroff at X shutdown
If you have installed an update of Nvidia and your screen stays black after launching Xorg, or if shutting down Xorg causes a machine poweroff, try the below workarounds. Alternatively, use the Nouveau driver.
- Use the
rcutree.rcu_idle_gp_delay=1
kernel parameter.
- You can also try to add the
nvidia
module directly to your mkinitcpio config file.
- If the screen still stays black with both the
rcutree.rcu_idle_gp_delay=1
kernel parameter and thenvidia
module directly in the mkinitcpio config file, try re-installing nvidia and nvidia-libgl[ссылка недействительна: replaced by nvidia-utils] in that order, and finally reload the driver:
# modprobe nvidia
Backlight is not turning off in some occasions
By default, DPMS should turn off backlight with the timeouts set or by running xset. However, probably due to a bug in the proprietary Nvidia drivers the result is a blank screen with no powersaving whatsoever. To workaround it, until the bug has been fixed you can use the vbetool
as root.
Install the vbetool package.
Turn off your screen on demand and then by pressing a random key backlight turns on again:
vbetool dpms off && read -n1; vbetool dpms on
Alternatively, xrandr is able to disable and re-enable monitor outputs without requiring root.
xrandr --output DP-1 --off; read -n1; xrandr --output DP-1 --auto
Full system freeze using Flash
If you experience occasional full system freezes (only the mouse is moving) using flashplugin and get:
/var/log/errors.log
NVRM: Xid (0000:01:00): 31, Ch 00000007, engmask 00000120, intr 10000000
A possible workaround is to switch off Hardware Acceleration in Flash, setting
/etc/adobe/mms.cfg
EnableLinuxHWVideoDecode=0
Or, if you want to keep Hardware acceleration enabled, you may try to::
export VDPAU_NVIDIA_NO_OVERLAY=1
...before starting the browser. Note that this may introduce tearing.
Xorg fails to load or Red Screen of Death
If you get a red screen and use GRUB, disable the GRUB framebuffer by editing /etc/default/grub
and uncomment GRUB_TERMINAL_OUTPUT=console
. For more information see GRUB/Tips and tricks#Disable framebuffer.
Black screen on systems with Intel integrated GPU
If you have an Intel CPU with an integrated GPU (e.g. Intel HD 4000) and have installed the nvidia package, you may experience a black screen on boot, when changing virtual terminal, or when exiting an X session. This may be caused by a conflict between the graphics modules. This is solved by blacklisting the Intel GPU modules. Create the file /etc/modprobe.d/blacklist.conf
and prevent the i915 and intel_agp modules from loading on boot:
/etc/modprobe.d/blacklist.conf
install i915 /usr/bin/false install intel_agp /usr/bin/false
Black screen on systems with VIA integrated GPU
As above, blacklisting the viafb module may resolve conflicts with NVIDIA drivers:
/etc/modprobe.d/blacklist.conf
install viafb /usr/bin/false
X fails with "no screens found" with Intel iGPU
Like above, if you have an Intel CPU with an integrated GPU and X fails to start with
[ 76.633] (EE) No devices detected. [ 76.633] Fatal server error: [ 76.633] no screens found
then you need to add your discrete card's BusID to your X configuration. Find it:
# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1)
then you fix it by adding it to the card's Device section in your X configuration. In my case:
/etc/X11/xorg.conf.d/10-nvidia.conf
Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BusID "PCI:1:0:0" EndSection
Note how 01:00.0
is written as 1:0:0
.
Xorg fails during boot, but otherwise starts fine
On very fast booting systems, systemd may attempt to start the display manager before the NVIDIA driver has fully initialized. You will see a message like the following in your logs only when Xorg runs during boot.
/var/log/Xorg.0.log
[ 1.807] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the [ 1.807] (EE) NVIDIA(0): system's kernel log for additional error messages and [ 1.808] (EE) NVIDIA(0): consult the NVIDIA README for details. [ 1.808] (EE) NVIDIA(0): *** Aborting ***
In this case you will need to establish an ordering dependency from the display manager to the DRI device. First create device units for DRI devices by creating a new udev rules file.
/etc/udev/rules.d/99-systemd-dri-devices.rules
ACTION=="add", KERNEL=="card*", SUBSYSTEM=="drm", TAG+="systemd"
Then create dependencies from the display manager to the device(s).
/etc/systemd/system/display-manager.service.d/10-wait-for-dri-devices.conf
[Unit] Wants=dev-dri-card0.device After=dev-dri-card0.device
If you have additional cards needed for the desktop then list them in Wants and After seperated by spaces.
Flash video players crashes
If you are getting frequent crashes of Flash video players, try to switch off Hardware Acceleration:
/etc/adobe/mms.cfg
EnableLinuxHWVideoDecode=0
(This problem appeared after installing the proprietary nvidia driver, and was fixed by changing this setting.)
xrandr BadMatch
If you are trying to configure a WQHD monitor such as DELL U2515H using xrandr and xrandr --addmode
gives you the error X Error of failed request: BadMatch
, it might be because the proprietary NVIDIA driver clips the pixel clock maximum frequency of HDMI output to 225 MHz or lower. To set the monitor to maximum resolution you have to install nouveau drivers. You can force nouveau to use a specific pixel clock frequency by setting nouveau.hdmimhz=297
(or 330
) in your Kernel parameters.
Alternatively, it may be that your monitor's EDID is incorrect. See #Override EDID.
Override EDID
If your monitor is providing wrong EDID information, the nvidia-driver will pick a very small solution. Nvidia's driver options change, this guide refers to nvidia 346.47-11.
Aside from manually setting modelines in the xorg config, you have to allow non-edid modes and disable edid in the device section:
/etc/X11/xorg.conf.d/10-monitor.conf
Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 30-94 VertRefresh 56-76 DisplaySize 518.4 324.0 Option "DPMS" # 1920x1200 59.95 Hz (CVT 2.30MA-R) hsync: 74.04 kHz; pclk: 154.00 MHz Modeline "1920x1200R" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" Option "UseEdidFreqs" "FALSE" Option "UseEDID" "FALSE" Option "ModeValidation" "AllowNonEdidModes" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1920x1200R" EndSubSection EndSection
Alternatively, it may be that your monitor's EDID is actually correct and the driver does not trust it. To force it to use the EDID anyway, set the IgnoreEDIDChecksum
option for the X11 Device.
Section "Device" Identifier "Device0" Driver "nvidia" Option "IgnoreEDIDChecksum" "displayName" EndSection
where displayName
is the name of the display device e.g. DFP-4
. You can find the display device name in your Xorg log; it is not the same as the output name (e.g. DVI-I-0
) that you would see in Xrandr output.
Overclocking with nvidia-settings GUI not working
Workaround is to use nvidia-settings CLI to query and set certain variables after enabling overclocking(as explained in NVIDIA/Tips and tricks#Enabling overclocking. nvidia-settings(1) for more information.
Example to query all variables:
nvidia-settings -q all
Example to set PowerMizerMode to prefer performance mode:
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1
Example to set multiple variables at once(Overclock on performance level [3] by 50Mhz, overclock MemoryTransferRate by 50Mhz, Over Voltage by 100 microvolts)
nvidia-setting -a GPUGraphicsClockOffset[3]=50 -a GPUMemoryTransferRateOffset[3]=50 -a GPUOverVoltageOffset=100
Avoid screen tearing
Tearing can be avoided by forcing a full composition pipeline, regardless of the compositor you are using. To test whether this option will work, type
nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
This however has been reported to reduce the performance of some OpenGL applications and may produce issues in WebGL.
In order to make the change permanent, it must be added to the "Screen"
section of your Xorg configuration file. When making this change, TripleBuffering
should be enabled and AllowIndirectGLXProtocol
should be disabled in the driver configuration as well. See example configuration below:
/etc/X11/xorg.conf.d/20-nvidia.conf
Section "Screen" Identifier "Screen0" Option "metamodes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }" Option "AllowIndirectGLXProtocol" "off" Option "TripleBuffer" "on" EndSection
If you do not have an Xorg configuration file, you can create one for your present hardware using nvidia-xconfig
(see NVIDIA#Automatic configuration) and move it from /etc/X11/xorg.conf
to the preferred location /etc/X11/xorg.conf.d/20-nvidia.conf
.
20-nvidia.conf
by using nvidia-xconfig
are set automatically by the driver and are not needed. To only use this file for enabling composition pipeline, only the section "Screen"
containing lines with values for Identifier
and Option
are necessary. Other sections may be removed from this file.~/.nvidia-settings-rc
as 0/XVideoSyncToDisplayID=
or by installing nvidia-settings and using the graphical configuration options.Avoid screen tearing in KDE (KWin)
/etc/profile.d/kwin.sh
export __GL_YIELD="USLEEP"
Also if the above does not help, then try this:
/etc/profile.d/kwin.sh
export KWIN_TRIPLE_BUFFER=1
If you enable triple buffering make sure to enable TripleBuffering
for the driver itself.
/etc/X11/xorg.conf or /etc/X11/xorg.conf.d/20-nvidia.conf
Section "Device" [...] Option "TripleBuffer" "True" [...] EndSection
Also make sure to select OpenGL >= 2.0 as rendering backend under Systemsettings > Display and Monitor > Compositor.
In some cases neither of the above fixes work. A possible fix is to configure ForceFullCompositionPipeline.
Source: https://bugs.kde.org/show_bug.cgi?id=322060
Modprobe Error: "Could not insert 'nvidia': No such device" on linux >=4.8
With linux 4.8, one can get the following errors when trying to use the discrete card:
$ modprobe nvidia -vv
modprobe: INFO: custom logging function 0x409c10 registered modprobe: INFO: Failed to insert module '/lib/modules/4.8.6-1-ARCH/extramodules/nvidia.ko.gz': No such device modprobe: ERROR: could not insert 'nvidia': No such device modprobe: INFO: context 0x24481e0 released insmod /lib/modules/4.8.6-1-ARCH/extramodules/nvidia.ko.gz
$ dmesg
... NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:139b) NVRM: installed in this system is not supported by the 370.28 NVRM: NVIDIA Linux driver release. Please see 'Appendix NVRM: A - Supported NVIDIA GPU Products' in this release's NVRM: README, available on the Linux driver download page NVRM: at www.nvidia.com. ...
This problem is caused by bad commits pertaining to PCIe power management in the Linux Kernel (as documented in this NVIDIA DevTalk thread).
The workaround is to add pcie_port_pm=off
to your kernel parameters. Note that this disables PCIe power management for all devices.