Solved Issue with Nvidia Drivers on Ubuntu: X11 Shows "Something Has Gone Wrong" After Installation

Solved issue

stillsurvivesomehow

New Member
Joined
Feb 1, 2025
Messages
16
Reaction score
4
Credits
249
Whenever I install any Nvidia driver version on Ubuntu, X11 fails to load and displays a white screen with the message: "Oh, sorry, something has gone wrong." However, if I uninstall the Nvidia driver, X11 works fine.

I need to use X11 instead of Wayland with the Nvidia drivers installed since I'm planning to overclock my GPU and game on it. Any help with resolving this issue would be greatly appreciated!
 


where are you getting the nvidia drivers from? most recent version of Ubuntu or something older? which nvidia card are you using?
 
where are you getting the nvidia drivers from? most recent version of Ubuntu or something older? which nvidia card are you using?
I installed the ubuntu recommended version of nvidia 560 through apt, didn't work. i installed the latest new feature branch driver 565 listed here: https://www.nvidia.com/en-us/drivers/unix/ didn't work. then i installed the latest recommended driver for my specific gpu which is gtx 950m listed on nvidia website from here: https://www.nvidia.com/en-in/drivers/details/238858/ ; also didn't work. installed version 550 through apt. didn't work.
 
I'd repeat this process to reproduce the problem then if upon reboot it doesn't work, run this command to figure out what happened:

Bash:
sudo dmesg | grep nvidia

Share your output here.
sorry I'm late, i was distracted by other problems on linux.

Logged to x11, got the problem, went to tty then executed the command you mentioned, this is what it gave:

[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.12.11-x64v3-xanmod1 root=UUID=aa9847d5-a40e-427f-a7af-f16cab6e061c ro quiet udev.log_priority=3 nvidia_drm.modeset=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
[ 0.038841] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.12.11-x64v3-xanmod1 root=UUID=aa9847d5-a40e-427f-a7af-f16cab6e061c ro quiet udev.log_priority=3 nvidia_drm.modeset=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
[ 1.160335] nvidia: loading out-of-tree module taints kernel.
[ 1.160345] nvidia: module license 'NVIDIA' taints kernel.
[ 1.160349] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 1.160350] nvidia: module license taints kernel.
[ 1.247031] nvidia-nvlink: Nvlink Core is being initialized, major device number 239
[ 1.634286] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 565.77 Wed Nov 27 22:53:48 UTC 2024
[ 1.636270] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 1.912656] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
[ 19.072037] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[ 19.097235] nvidia-uvm: Loaded the UVM driver, major device number 235.
[ 103.223592] audit: type=1400 audit(1738545419.277:193): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/proc/driver/nvidia/params" pid=2698 comm="Xorg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 103.223660] audit: type=1400 audit(1738545419.277:195): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/dev/nvidiactl" pid=2698 comm="Xorg" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
[ 103.223731] audit: type=1400 audit(1738545419.277:196): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/proc/driver/nvidia/params" pid=2698 comm="Xorg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 104.157118] audit: type=1400 audit(1738545420.209:201): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/proc/driver/nvidia/params" pid=2698 comm="Xorg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 110.123916] audit: type=1400 audit(1738545426.177:1431): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/dev/nvidiactl" pid=2698 comm="Xorg" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
[ 110.168760] audit: type=1400 audit(1738545426.221:1432): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/dev/nvidiactl" pid=2698 comm="Xorg" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
 
I need to use X11 instead of Wayland with the Nvidia drivers installed since I'm planning to overclock my GPU and game on it.

Why can't you do this with wayland?

Code:
./nvidia_oc set --index 0 --power-limit 200000 --freq-offset 160 --mem-offset 850 --min-clock 0 --max-clock 2000

Code:
from pynvml import *
nvmlInit()
myGPU = nvmlDeviceGetHandleByIndex(0)
nvmlDeviceSetGpcClkVfOffset(myGPU, 80)
nvmlDeviceSetMemClkVfOffset(myGPU, 2500)
nvmlDeviceSetPowerManagementLimit(myGPU, 216000)
 
Why can't you do this with wayland?

Code:
./nvidia_oc set --index 0 --power-limit 200000 --freq-offset 160 --mem-offset 850 --min-clock 0 --max-clock 2000

Code:
from pynvml import *
nvmlInit()
myGPU = nvmlDeviceGetHandleByIndex(0)
nvmlDeviceSetGpcClkVfOffset(myGPU, 80)
nvmlDeviceSetMemClkVfOffset(myGPU, 2500)
nvmlDeviceSetPowerManagementLimit(myGPU, 216000)
hey i managed to overclock my gpu and try games on wayland (they work terribly, huge input lags), i used ssprea nvidia control.
 
Which Nvidia GPU do you have?
 
Sorry but I don't see anything wrong in the output, maybe because it corresponds to text mode boot and not graphical boot.

Since you have very new kernel, maybe try beta driver:
with 570 installed i can overclock my gpu through PowerMizer option using nvidia-settings, that's a good improvement!
but x11 won't work
 
Yes you can try, but I suspect it will work since none of the drivers worked so far, this sounds like issue with ubuntu.
The drivers are just fine they work fine on my system.
Hey dude!
So I ran:
sudo nano /etc/gdm3/custom.conf
I set: WaylandEnable=false
then: sudo systemctl restart gdm3
logged to x11, gave me the error, ran tty then journalctl -b -p err
this is the log of error, i do hope it has information you need to help me out:
Feb 04 16:54:39 PCUNAME kernel: ata6.00: exception Emask 0x0 SAct 0x80002c80 SErr 0x0 action 0x0
Feb 04 16:54:39 PCUNAME kernel: ata6.00: irq_stat 0x40000008
Feb 04 16:54:39 PCUNAME kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb 04 16:54:39 PCUNAME kernel: ata6.00: cmd 60/08:38:00:a8:13/00:00:00:00:00/40 tag 7 ncq dma 4096 in
res 41/40:38:01:a8:13/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 04 16:54:39 PCUNAME kernel: ata6.00: status: { DRDY ERR }
Feb 04 16:54:39 PCUNAME kernel: ata6.00: error: { UNC }
Feb 04 16:54:39 PCUNAME kernel: I/O error, dev sdb, sector 1288193 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Feb 04 16:54:39 PCUNAME kernel: ata6.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action 0x0
Feb 04 16:54:39 PCUNAME kernel: ata6.00: irq_stat 0x40000008
Feb 04 16:54:39 PCUNAME kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb 04 16:54:39 PCUNAME kernel: ata6.00: cmd 60/08:78:00:a8:13/00:00:00:00:00/40 tag 15 ncq dma 4096 in
res 41/40:78:01:a8:13/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 04 16:54:39 PCUNAME kernel: ata6.00: status: { DRDY ERR }
Feb 04 16:54:39 PCUNAME kernel: ata6.00: error: { UNC }
Feb 04 16:54:39 PCUNAME kernel: I/O error, dev sdb, sector 1288193 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 04 16:54:39 PCUNAME kernel: Buffer I/O error on dev sdb3, logical block 0, async page read
Feb 04 16:54:46 PCUNAME kernel: ata6.00: exception Emask 0x0 SAct 0xa0014200 SErr 0x0 action 0x0
Feb 04 16:54:46 PCUNAME kernel: ata6.00: irq_stat 0x40000008
Feb 04 16:54:46 PCUNAME kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb 04 16:54:46 PCUNAME kernel: ata6.00: cmd 60/08:e8:00:a8:13/00:00:00:00:00/40 tag 29 ncq dma 4096 in
res 41/40:e8:01:a8:13/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 04 16:54:46 PCUNAME kernel: ata6.00: status: { DRDY ERR }
Feb 04 16:54:46 PCUNAME kernel: ata6.00: error: { UNC }
Feb 04 16:54:46 PCUNAME kernel: spi-nor spi0.0: probe with driver spi-nor failed with error -22
Feb 04 16:54:46 PCUNAME kernel: I/O error, dev sdb, sector 1288193 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Feb 04 16:54:46 PCUNAME kernel: ata6.00: exception Emask 0x0 SAct 0x780001 SErr 0x0 action 0x0
Feb 04 16:54:46 PCUNAME kernel: ata6.00: irq_stat 0x40000008
Feb 04 16:54:46 PCUNAME kernel: ata6.00: failed command: READ FPDMA QUEUED
Feb 04 16:54:46 PCUNAME kernel: ata6.00: cmd 60/08:00:00:a8:13/00:00:00:00:00/40 tag 0 ncq dma 4096 in
res 41/40:00:01:a8:13/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 04 16:54:46 PCUNAME kernel: ata6.00: status: { DRDY ERR }
Feb 04 16:54:46 PCUNAME kernel: ata6.00: error: { UNC }
Feb 04 16:54:46 PCUNAME kernel: I/O error, dev sdb, sector 1288193 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Feb 04 16:54:46 PCUNAME kernel: Buffer I/O error on dev sdb3, logical block 0, async page read
Feb 04 16:54:50 PCUNAME kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 570.86.16 Fri Jan 24 21:25:51 UTC 2025
Feb 04 16:56:52 PCUNAME gdm-password][2456]: gkr-pam: unable to locate daemon control file
Feb 04 16:57:02 PCUNAME systemd[2470]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2937.scope - Application launched by gnome-session-binary.
Feb 04 16:57:02 PCUNAME systemd[2470]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2934.scope - Application launched by gnome-session-binary.
Feb 04 16:57:02 PCUNAME gnome-shell[2960]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 585 error_code 8 request_code 156 (NV-GLX) minor_code 44)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Feb 04 16:57:04 PCUNAME systemd[2470]: Failed to start [email protected] - GNOME Shell on X11.
Feb 04 16:57:04 PCUNAME gnome-shell[2995]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 585 error_code 8 request_code 156 (NV-GLX) minor_code 44)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Feb 04 16:57:05 PCUNAME systemd[2470]: Failed to start [email protected] - GNOME Shell on X11.
Feb 04 16:57:06 PCUNAME gnome-shell[3110]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 585 error_code 8 request_code 156 (NV-GLX) minor_code 44)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Feb 04 16:57:33 PCUNAME gdm-password][3954]: gkr-pam: unable to locate daemon control file
Feb 04 16:57:34 PCUNAME systemd[2470]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-4340.scope - Application launched by gnome-session-binary.
Feb 04 16:57:34 PCUNAME systemd[2470]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-4336.scope - Application launched by gnome-session-binary.
Feb 04 16:58:26 PCUNAME systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled.
Feb 04 17:00:10 PCUNAME systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled.
Feb 04 17:03:35 PCUNAME gnome-shell[6721]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 573 error_code 8 request_code 156 (NV-GLX) minor_code 44)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Feb 04 17:03:47 PCUNAME gnome-shell[7014]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 573 error_code 8 request_code 156 (NV-GLX) minor_code 44)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the mtk_x_error() function.)
Feb 04 17:03:48 PCUNAME gnome-session-binary[6674]: Unrecoverable failure in required component org.gnome.Shell.desktop
Feb 04 17:04:08 PCUNAME systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled.
 
Why does he want to use X11? Wayland usually gives about 2-3% better performance in GLmark2 tests over X11.
 


Top