i'm using Linux Mint. I recently updated my workstation, and from this moment, my drivers went nuts. I was working fine before, with the nvidia-361 drivers, and, when i finished my updates, and after rebooting the PC, il was running in "software rendering mode". I finally get to have a correct desktop, but now, i'm quite sure the card isn't fonctionning properly, because i can't launch any simple game with 3D (like blazeRush for example, wich was running fine before). This is the result of a lspci -vnnn 01:00.0 VGA compatible controller : NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GF104 [GeForce GTX 460] [1458:34fc] Flags: bus master, fast devsel, latency 0, IRQ 124 Memory at dc000000 (32-bit, non-prefetchable) [size=32M] Memory at d0000000 (64-bit, prefetchable) [size=128M] Memory at d8000000 (64-bit, prefetchable) [size=64M] I/O ports at e000 [size=128] Expansion ROM at de000000 [disabled] [size=512K] Capabilities: Power Management version 3 Capabilities: MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 Capabilities: Virtual Channel Capabilities: Power Budgeting Capabilities: Vendor Specific Information: ID=0001 Rev=1 Len=024 Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375 As you can see, the kernel driver in use is "nouveau", but i would like to use nvidia_375 instead. I already tried to purge with apt like this sudo apt purge *nvidia* xserver-xorg*nouveau* bbswitch* but when i do that, after a reboot, "nouveau" is still here ... i can try to install again the proprietary drivers, but i will be back in the same situation as before the purge. I'm running out of options.

I'm using ArchLinux and when I run vlc or mplayer, I used to get the error Failed to open VDPAU backend libvdpau_nouveau.so: cannot open shared object file: No such file or directory This doesn't seem to cause any error as far as video playback is concerned, but I want to know the reason for this problem. I referred to this post in UbuntuForums and one of the suggestions to solve the problem was to install nouveau-fw. Looking at the installed files by the nouveau-fw package, I couldn't find libvdpau_nouveau.so at all in the list, but surprisingly mplayer stopped showing the error after installing the package. But vlc still continues to show the error. The only other solution given in the post was to install official nvidia drivers. I'm hoping to avoid this and just use the open-source drivers. Hoping someone can provide a solution to this.

**Moved this question over from AskUbuntu.** I've looked everywhere online for a solution. I've tried multiple times to install the appropriate Nvidia drivers for my graphics card (**which is a GTX 680**). I've also tried blacklisting Nouveau, to no avail. I'm desperate for a solution, especially considering how a lot of games don't work properly with Nouveau. The only results that I got from attempting to install the appropriate Nvidia drivers were... bad, at best. Upon reboot, systemd would apparently works as intended. But, upon reaching a certain part in the init (around "Reaching target Bluetooth/Swap"), the upper part of the display is corrupted like crazy and the part below remains frozen. (see image below) Side note: this happens even when booting into multi-user mode. Also, **the card is flashed to work with macOS Mojave**, so I suspect that might be the reason why. All help will be greatly appreciated. Thanks in advance, as well.

I want to install Ubuntu 16.04.3 LTS from a usb stick but during booting I get the following errors: https://ibb.co/kopx1R fifo: read fault at ...engine 1f nouveau write fault HOST_CPU_NB REGION_VIOLATION on channel 1 ...reason 0d gr init failed, -110 There is something wrong with nouveau. I have GeForce 970 GTX but some time ago I have installed Ubuntu 16.04.1 LTS without problems. How to fix that ?

I'm having a problem after installing Fedora 36. I keep getting a half white screen while using an external monitor. I'm using my laptop and a monitor, but my monitor is only showing a white screen. When I hover my mouse to the monitor, it starts showing half screen. I dont get the message error anymore but the screen still half blank. --- My laptop has an Nvidia RTX 2060 and a AMD Ryzen7 3750

When I try to start my Debian 9 xserver, it shows a black screen. Xorg -configure outputs > Number of created screens does not match number of detected devices and outputs a non-working xorg.conf. glxinfo | grep -i vendor outputs: > unable to open display I have a nVidia GeForce GTX 745 with 4GB and I am using the nouveau drivers, because Nvidia's own drivers output the same error and I wanted to set my drivers back to default. This happened after I tried to install the nVidia nvidia-driver packages to have better performance.

After my machine (Fedora 35) goes to sleep and wakes, my second monitor won't turn on again. I can reproduce the same problem by running

xrandr --output HDMI-1-1 --off 
xrandr --output HDMI-1-1 --auto

The second command will output

: Configure crtc 3 failed

, without turning on the monitor. For some time now, my Problem Reporting shows a system failure "xorg-x11-drv-nouveau". I do not know if there is a link. My system journal shows the following:

Feb 13 18:33:46 fedora kernel: nouveau 0000:01:00.0: acr: AHESASC binary failed
Feb 13 18:33:46 fedora kernel: nouveau 0000:01:00.0: acr: init failed, -110
Feb 13 18:33:46 fedora kernel: nouveau 0000:01:00.0: init failed with -110
Feb 13 18:33:46 fedora kernel: nouveau: systemd-logind:00000000:00000080: init failed with -110
Feb 13 18:33:46 fedora kernel: nouveau: DRM-master:00000000:00000000: init failed with -110
Feb 13 18:33:46 fedora kernel: nouveau: DRM-master:00000000:00000000: init failed with -110
Feb 13 18:33:46 fedora kernel: nouveau 0000:01:00.0: DRM: Client resume failed with error: -110
Feb 13 18:33:46 fedora kernel: nouveau 0000:01:00.0: DRM: resume failed with: -110
Feb 13 18:33:47 fedora kernel: nouveau 0000:01:00.0: DRM: Dropped ACPI reprobe event due to RPM error: -22
Feb 13 18:33:47 fedora kernel: nouveau 0000:01:00.0: DRM: Dropped ACPI reprobe event due to RPM error: -22
Feb 13 18:33:48 fedora abrt-server: Oops looks like a problem in kernel module, new component xorg-x11-drv-nouveau

Thank you!

In my past experience, Fedora's Nouveau driver worked splendidly by default. In fact I would have try and disable it to get the proprietary NVIDIA to take over. However the Nvidia driver is a lot of maintenance, and its hard to get it to run with secure-boot, and I am tired of it tainting my kernel. So I wanted to give the Mesa, Nouveau, and NVK a try. My primary need right now is compute with OpenCL. I have a dual setup with a integrated radeon GPU, and an RTX 3000 series Nvidia GPU. I started by removing all things Nvidia

dnf remove \*nvidia\*
dnf remove \*cuda\*

I installed the drivers, but some issues, got a tip to install the Nvidia firmware

dnf install nvidia-gpu-firmware

I did that, it got rid of some errors in journalctl but I still had problems, I reinstalled the drivers but the problems persisted, here are some of the issues I am having: clinfo gives the following errors:

nvc0_screen_create:1002 - Base screen init failed: -19

and

=== CL_PROGRAM_BUILD_LOG ===
:1:10: fatal error: 'clc/clc.h' file not found

It looks like it is trying to query the nvidia device but failing, I get the first error when I compile and run my own OpenCL Programs. vulkaninfo hangs and journalctl gives

fedora abrt-dump-journal-oops: abrt-dump-journal-oops: Creating problem directories
fedora abrt-dump-journal-oops: abrt-dump-journal-oops: Found oopses: 1
fedora kernel: note: vulkaninfo exited with irqs disabled

When it runs, along with what looks like some sort of call stack/dump. glxgears and inxi -Gx also hang though inxi does work, but it does not show the nvidia gpu (just my AMD integrated one). I don't know if these journalctl messages are relevant

fedora gnome-shell: Added device '/dev/dri/card1' (nouveau) using non-atomic mode setting.
fedora gnome-shell: Device '/dev/dri/card1' prefers shadow buffer

nouveau [REDACTED]: fb: VPR locked, but no scrubber binary!

Somewhat at a loss, I don't know the next step to debug or solve the problem, *can anyone please help me to get open source OpenCL drivers to work on my Nvidia GPU (along possibly with NVK) please?* :) Thanks! **UPDATE** (occurred after P.s) After a system update vulkaninfo started working and showing the nvidia driver, however OpenCL programs seem to still struggle (clinfo still does not recognize it) or crash when retrieving the Nvidia GPU info. clinfo no longer gets

nvc0_screen_create:1002 - Base screen init failed: -19

but still gets

=== CL_PROGRAM_BUILD_LOG ===
:1:10: fatal error: 'clc/clc.h' file not found

and does not display info about the Nvidia GPU. inxi -Gx now displays (with redaction)

Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
    driver: nouveau v: kernel arch: Ampere bus-ID: REDACT
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 bus-ID: REDACT

I did a fresh reinstall of the drivers + reboot and this persisted. I have a slight issue with the firmware update tool, unsure if its related

FuUsbDevice          failed to parse platform BOS descriptor: failed to parse: no supported platform version: did not find magic

P.s I have a memory of doing something to disable the Nouveau driver a while back, so that my second monitor could be displayed via a direct graphics card connection (because nouveau didn't seem to do that). I already reversed configurations and boot parameters in grub blacklisting Nouveau (I think), but there may have been something else, I don't know if it would have anything to do with it... trying to figure it out if there is any configuration left, I think it may have had to do with GDM. **UPDATE**: Thanks to a chat with the developers in the freedesktop chat room I actually did get this working, had something to do with Clover if I recall. I have to go back and check what I did, but I may post it here after I do that

I try to install Parrot OS on an old windows PC that has GPU of Nvidia GeForce 710. When I boot it in the default mode, It seems like it renders but then I get an error saying: nouveau 0000:01:00.0: DRM [DRM/000000001: kmsOutp] [HDMI head:0 enable: 1 max_ac_packet:15 ... Then, I tried to boot while selecting disable nouveau and nvidia GPU and it boots ok. Later, I tried to do: sudo apt install nvidia-driver But I got an error saying: "The system has a graphic card which is no longer handled by NVIDIA driver..." I tried to download manually the driver and install it (had to stop and start lightdm for it) but I got errors. Currently, I'm stuck with no nvidia and nouveau which makes the resolution huge. When I try to use xrandr, it keeps failing. I tried to use cvt to add a new resolution but it won't add. How can I continue here? I feel like I'm completely stuck. Thank you! **SOLUTION:** So after a while the following solution did the thing: 1. Make sure to add nouveau to blacklist-nouveau.conf. blacklist nouveau options nouveau modeset=0 alias nouveau off 2. sudo apt install nvidia-tesla-470-driver.

Good day everyone. My laptop has a RTX 4080 Nvidia dGPU with HDMI and DisplayPort directly connected to it. Video works perfectly, but I have no audio. I wonder if it’s fixable or just not supported with the open drivers. I use Tumbleweed, with Plasma (Wayland session). ~> aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 3: HDMI 0 [GP01] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sofhdadsp [sof-hda-dsp], device 31: HDA Analog Deep Buffer (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 If I use alsamixer or simply the KDE's settings, I can clearly see that I can either select the laptop's audio output, or my HDMI's. If I use the latter, I can change the volume (lower or higher), but actually no sound is reproduced. Happens actually on any distro. Audio works good with Windows or any other device connected to the monitor (Android, ChromeOS, Fire TV stick, Nintendo Switch). ~> sudo lspci -nnk |grep -E "3D|VGA" [sudo] password di root: 0000:00:02.0 VGA compatible controller : Intel Corporation Raptor Lake-S UHD Graphics [8086:a788] (rev 04) 0000:01:00.0 VGA compatible controller : NVIDIA Corporation AD104M [GeForce RTX 4080 Max-Q / Mobile] [10de:27a0] (rev a1)

Is it possible to monitor VRAM usage when running nouveau drivers? I know this is possible with nvidia drivers, but here I'm talking about nouveau.

I've got a monitor which can do 3840x2160 & NVidia Quadro P400 GPU. OS: Debian testing. When I try using the official NVidia driver (v. 525.147.95), everything works, but the top resolution is not detected ( in the list in NVIDIA Settings, the highest detected resolution is 1920x1080 and that's what the driver uses) When I try using the Nouveau driver - if I connect the whole setup to a monitor which can only do 1920x1080, it works all right. If I connect it to my main one which can do 3840x2160 and reboot, all I can see post BIOS & GRUB is a brief output from the kernel booting, and then a black screen - Nouveau probably crashes somewhere. Question: how to either - figure out (and fix!) the crash in Nouveau (in particular, where do I find logs?) - or: convince the NVidia driver to detect (and use!) 3840x2160 ? EDIT: xrandr output:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 700mm x 390mm
   1920x1080     60.00*+  59.94    50.00    60.00    50.04  
   1680x1050     59.95  
   1600x900      60.00  
   1440x900      59.90    59.89  
   1280x1024     75.02    60.02  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    59.94    59.93  
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

when I try to manually add the 3840x2160 mode using xrandr, I get 'BadMatch' error:

> cvt 3840 2160
# 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz
Modeline "3840x2160_60.00"  712.75  3840 4160 4576 5312  2160 2163 2168 2237 -hsync +vsync

> xrandr --newmode "3840x2160_60.00"  712.75  3840 4160 4576 5312  2160 2163 2168 2237 -hsync +vsync

> xrandr --addmode DP-3 3840x2160_60.00
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  39
  Current serial number in output stream:  40

I recently flashed my BIOS chip with either GNUboot and libreboot. But I have not been able to get my external graphics card to work. The only error I could find regarding to nouveau is:

... vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none

Does anyone know what could cause this error, or in what direction to look? Everything worked before flashing. Now only able to get display with serial cable and on-board graphics.

I followed this guide to install nvidia drivers on kali linux. https://www.kali.org/docs/general-use/install-nvidia-drivers-on-kali-linux/ after reboot, keep getting blank black screen also cannot switch to tty mode by pressing ctrl+alt+f1 to f6( none working)

I'm using the open source Nouveau drivers, and I'd like to be able to run applications with my dedicated GPU, NVIDIA GeForce MX250 in X11. Proprietary drivers are out of the question for me as they prevent me from logging in. I tried using prime-run but when i boot minecraft it shows me that it uses integrated intel graphics, and when i run

-run glxinfo | grep OpenGL

, It returns the following output:

OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.2.1-1ubuntu3.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1-1ubuntu3.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

I'm not sure what this means, but I'm sure its meant to output my dedicated GPU, which [shows up no problem in neofetch](https://imgur.com/a/SH1L4jm) . Sorry if a lot of this information is unnecessary, I don't want to miss anything out

I have two boot configurations which more or less look like this: 1. modprobe.blacklist=nouveau 2. modprobe.blacklist=nvidia, Which serve to dynamically use the open source or proprietary driver when booting. Now I want to add another boot entry which disables both nouveau and nvidia in effect disabling the NVIDIA GPU. 3. modprobe.blacklist=nouveau,nvidia,... lsmod | grep -iE '(nouveau|nvidia)' still shows nvidia so my guess is that another module pulls that in. Normally I could create a file /etc/modprobe.d/blacklist:

install nvidia /bin/true
install nouveau /bin/true

But this would mean that I loose the lexibility of just choosing another boot entry. Is there any way this behavior could be achieved? My only idea was to have two small filesystems which contain different modprobe.d configurations and mount them dynamically as early as possible during the boot process after changing to the real root partition.

My Linux PC has a Nvidia GPU. I used to manage the graphics driver by the

-driver

package. However the stock is a bit behind so I decided to install the latest one myself from Nvidia. I made the script executable.

chmod +x NVIDIA-Linux-x86_64-535.98.run

I ran the script but I get an error.

NVIDIA-Linux-x86_64-535.98.run
ERROR: An NVIDIA kernel module 'nvidia-uvm' appears to already be loaded in your kernel. This may be because it is in use (for example, by an X server, a CUDA program, or the NVIDIA Persistence Daemon), but this may also happen if your kernel was configured without support for module unloading.  Please be sure to exit any programs that may be using the GPU(s) before attempting to upgrade your driver.  If no GPU-based programs are running, you know that your kernel supports module unloading, and you still receive this message, then an error may have occurred that has corrupted an NVIDIA kernel module's usage count, for which the simplest remedy is to reboot your computer.

I pressed ctrl+alt+f2 to switch to tty then logged in as root. Then I disabled the GUI and unloaded

-drm

.

systemctl isolate multi-user.target
modprobe -r nvidia-drm

I ran the script the second time but this time I got a message telling me that nvidia debian packages are not compatible with this method and thus should be uninstalled first. So I removed the nvidia debian packages to prevent conflicts.

sudo apt purge nvidia*

I ran the script again.

NVIDIA-Linux-x86_64-535.98.run

Now the script runs fine. I then rebooted to see whether it worked.

reboot

It booted to GUI just fine but during booting I saw an error message:

nouveau 0000:08:00.0: unknown chipset

I checked which driver was running and confirmed that the newly installed nvidia driver is running.

lshw -c video
  *-display                 
       description: VGA compatible controller
       product: GA102 [GeForce RTX 3080]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:08:00.0
       ...

Why is nouveau loaded during boot although I never activated it? How can I have the message not show up?

Have problem with my nouveau driver I use i3 if it matters I had a nvdia 340 driver before. This is the journalctl command log nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2 nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f nouveau 0000:01:00.0: vp: init failed, -2 nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2 nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103 nouveau 0000:01:00.0: bsp: init failed, -2 nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2 nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f nouveau 0000:01:00.0: vp: init failed, -2 nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2 nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103 nouveau 0000:01:00.0: bsp: init failed, -2

I recently received the following error in my syslog: syslog:Apr 28 09:59:02 vostrodell kernel: [ 883.401212] nouveau 0000:01:00.0: fb: trapped read at 0039824400 on channel 12 [3ed04000 systemd-logind] engine 05 [PFIFO] client 08 [PFIFO_READ] subclient 01 [SEMAPHORE] reason 00000002 [PAGE_NOT_PRESENT] So I went to the documentation: * https://nouveau.freedesktop.org/KernelModuleParameters.html#debug and I tried adding the following file: $ cat /etc/modprobe.d/nouveau.conf # debug nouveau options nouveau debug="PFIFO=debug" However this is not being passed as expected: # cat /sys/module/nouveau/parameters/debug (null) I understand that PFIFO is not listed under debug section on the documentation page, but should fall under the category of any engine (see above): * https://nouveau.freedesktop.org/KernelModuleParameters.html#config I believe this is the correct *engine* to pass as kernel module parameter. Did I misread the documentation ? What should be the correct way to track to gather some meaning full information about this bug (in case I reproduce it) ?

**Problem:** My Nvidia graphics card requires 340.x drivers, so I tried installing an older-than-most-recent driver to see if it could help me. It did not help, and now I that I removed it, I cannot get any other resolution on my screen, besides 1024 x 768. **Steps taken:** 1. apt install nvidia-legacy-390xx-driver (old, but not enough); 2. apt remove nvidia-drivers (too newer than 340); 3. apt-get install --reinstall xserver-xorg-core libgl1-mesa-glx because [someone on the internet said it would work](https://askubuntu.com/questions/360761/cannot-get-rid-of-nvidia-drivers-restore-nouveau-driver-and-get-desktop-working) . 4. apt install nvidia-drivers 5. apt remove nvidia-smi 6. apt-get install --reinstall xserver-xorg-core libgl1-mesa-glx again, because [someone on the internet still says it would work](https://askubuntu.com/questions/360761/cannot-get-rid-of-nvidia-drivers-restore-nouveau-driver-and-get-desktop-working) . This did not restore the resolution to the normal that I used before. On the settings through GUI, I can only set 1024 x 768. How to fix Nouveau on Debian 11?