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.