ERROR: Unable to load the kernel module ‘nvidia.ko’
OpenSUSE Tumbleweed, kernel 4.10.1-1. После обновки ядра переустанавливаю драйвер nvidia. Драйвер компилируется нормально, nouveau забанен, как и rivafb и nvidiafb. После компиляции драйвера появляется следующее сообщение
Не смотрел, что там за сообщение появляется, просто факт — блоб невидии на 4.10 у меня не работает, экран в сосноли начинает моргать как припадочный, даже залогиниться не удаётся.
Откатился, сижу на 4.9.11, жду когда неаидия выкатит новый драйвер или тролльвардс — новое ведро. Интересно, это как-то связано с этим? http://www.opennet.ru/opennews/art.shtml?num=46107
Не благодари. Но ТСу этот патч не поможет.
PS: А хотя хз, может, и поможет.
А у меня работает.
Работает он только после патча. Без патча даже не компилируется.
Это я уже без понятия, этим мантейнеры дистрибутива занимаются.
уже патчил им я ж говорю: все компилируется, но почему-то не может загрузить модуль
У меня работает именно с этим патчем и драйвером 378.13.
Secure Boot случайно не включен?
нет, обычная загрузка
На форуме nvidia получил решение
Make sure nomodeset is in your /etc/default/grub at the end of the GRUB_CMDLINE_LINUX_DEFAULT options
grub2-mkconfig -o /boot/grub2/grub.cfg
to update your grub, and reboot.
Also need to add nv_unregister_procfs in kernel/nv.c
right after line 1041:
This worked succesful for me using (last updated) OpenSuSE Tumbleweed 20170303 kernel 4.10.1-1-default x86_64
Corrupted screen: «Six screens» Problem
For some users, using GeForce GT 100M’s, the screen gets corrupted after X starts, divided into 6 sections with a resolution limited to 640×480. The same problem has been recently reported with Quadro 2000 and hi-res displays.
To solve this problem, enable the Validation Mode NoTotalSizeCheck in section Device :
‘/dev/nvidia0’ input/output error
The factual accuracy of this article or section is disputed.
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:
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. 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:
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, add nopat 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 :
- If fullscreen applications are freezing or crashing, try enabling Display Compositing and Direct fullscreen rendering options in your desktop environment’s settings.
Bad performance after installing a new driver version
If FPS have dropped in comparison with older drivers, check if direct rendering is enabled ( glxinfo is included in mesa-utils ):
If the command prints:
A possible solution could be to regress to the previously installed driver version and rebooting afterwards.
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, run:
Or click on the Advanced button that is available on the X Server Display Configuration menu option. Select either Force Composition Pipeline or Force Full Composition Pipeline and click on Apply.
In order to make the change permanent, it must be added to the «Screen» section of the 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:
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 .
For multi-monitor setup you will need to specify ForceCompositionPipeline=On for each display. For example:
Without doing this, the nvidia-settings command will disable your secondary display.
You can get the current screen names and offsets using —query :
The above line is for two 3840×2160 monitors connected to DP-2 and DP-4. You will need to read the correct CurrentMetaMode by exporting xorg.conf and append ForceCompositionPipeline to each of your displays. Setting ForceCompositionPipeline only affects the targeted display.
/.nvidia-settings-rc as 0/XVideoSyncToDisplayID= or by installing nvidia-settings and using the graphical configuration options.
=4.8″>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:
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.
Screen corruption after resuming from suspend or hibernation
A corruption after suspend bug when using GDM service was solved as of driver version 515.43.04 .
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:
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 :
One user had luck with this instead, but it makes performance drop significantly for others:
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.
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 out. 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:
- Prepend «xrandr —auto» to your xinitrc
- Use the rcutree.rcu_idle_gp_delay=1 kernel parameter.
- You can also try to add the nvidia module directly to your mkinitcpio.conf.
- If the screen still stays black with both the rcutree.rcu_idle_gp_delay=1 kernel parameter and the nvidia module directly in the mkinitcpio.conf, try re-installing nvidia and nvidia-utils in that order, and finally reload the driver:
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:
Alternatively, xrandr is able to disable and re-enable monitor outputs without requiring root.
Driver 415: HardDPMS
This article or section needs expansion.
Proprietary driver 415 includes a new feature called HardDPMS. This is reported by some users to solve the issues with suspending monitors connected over DisplayPort. It is reported to become the default in a future driver version, but for now, the HardDPMS option can be set in the Device or Screen sections. For example:
HardDPMS will trigger on screensaver settings like BlankTime . The following ServerFlags will set your monitor(s) to suspend after 10 minutes of inactivity:
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 integrated GPU
If you have a system with an integrated GPU (e.g. Intel HD 4000, VIA VX820 Chrome 9 or AMD Cezanne) 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 relevant GPU modules. Create the file /etc/modprobe.d/blacklist.conf and prevent the relevant modules from loading on boot:
No audio over HDMI
Sometimes NVIDIA HDMI audio devices are not shown when you do
On some new machines, the audio chip on the NVIDIA GPU is disabled at boot. Read more on NVIDIA’s website and a forum post.
You need to reload the NVIDIA device with audio enabled. In order to do that make sure that your GPU is on (in case of laptops/Bumblebee) and that you are not running X on it, because it is going to reset:
If you are running your TTY on NVIDIA, put the lines in a script so you do not end up with no screen.
X fails with «no screens found» when using Multiple GPUs
In situations where you might have multiple GPUs on a system and X fails to start with:
then you need to add your discrete card’s BusID to your X configuration. This can happen on systems with an Intel CPU and an integrated GPU or if you have more than one NVIDIA card connected. Find your BusID:
Then you fix it by adding it to the card’s Device section in your X configuration. In my case:
In the example above 01:00.0 is stripped to be written as 1:0:0 , however some conversions can be more complicated. lspci output is in hex format, but in configuration files the BusID’s are in decimal format! This means that in cases where the BusID is greater than 9 you will need to convert it to decimal!
ie: 5e:00.0 from lspci becomes PCI:94: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.
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.
Then create dependencies from the display manager to the device(s).
If you have additional cards needed for the desktop then list them in Wants and After seperated by spaces.
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.
Another reason could be that by default current NVIDIA drivers will only allow modes explicitly reported by EDID, but sometimes refresh rates and/or resolutions are desired which are not reported by the monitor (although the EDID information is correct; it is just that current NVIDIA drivers are too restrictive).
If this happens, you may want to add an option to xorg.conf to allow non-EDID modes:
This can be set per-output. See NVidia driver readme (Appendix B. X Config Options) for more information.
Overclocking with nvidia-settings GUI not working
This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.
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, see nvidia-settings(1) for more information).
Example to query all variables:
Example to set PowerMizerMode to prefer performance mode:
Example to set fan speed to fixed 21%:
Example to set multiple variables at once (overclock GPU by 50MHz, overclock video memory by 50MHz, increase GPU voltage by 100mV):
Overclocking not working with Unknown Error
If you are running Xorg as a non-root user and trying to overclock your NVIDIA GPU, you will get an error similar to this one:
To avoid this issue, Xorg has to be run as the root user. See Xorg#Rootless Xorg for details.
System will not boot after driver was installed
If after installing the NVIDIA driver your system becomes stuck before reaching the display manager, try to disable kernel mode setting.
X fails with «Failing initialization of X screen»
If /var/log/Xorg.0.log says X server fails to initialize screen
and nvidia-smi says No running processes found
The solution is at first reinstall latest nvidia-utils , and then copy /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf to /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf , and then edit /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf and add the line Option «PrimaryGPU» «yes» . Restart the computer. The problem will be fixed.
System does not return from suspend
What you see in the log:
A possible solution based on :
Run this command to get the version string:
Add the acpi_osi=! «acpi_osi=version» kernel parameter to your boot loader configuration.
Vulkan error on applications start
The factual accuracy of this article or section is disputed.
On executing an application that require Vulkan acceleration, if you get this error
try to delete the
Extreme lag on Xorg
The factual accuracy of this article or section is disputed.
This should resolve this issue, however if it did not, you are most likely out of luck. One way you can remedy this issue is by adding these options:
turning Sync to VBlank and Allow flipping off within NVIDIA Settings, and configuring NVIDIA Settings to launch on startup using the flag —load-config-only . This will still result in a laggy desktop behavior, in particular on an eventual second (or third) monitor, but it should be much better.