565 release feedback & discussion

[bsimons]

Gentoo Linux x11-drivers/nvidia-drivers-565.77
X11/KDE/Plasma6
Razer blade pro 4K IGZO touch display NVidia G-Sync 3840x2160 laptop

pls see (below) attached log from: /var/log/Xorg.0.log

[ 8.582] (II) NVIDIA dlloader X Driver 565.77 Wed Nov 27 22:57:27 UTC 2024
[ 8.582] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs

[ 8.633] (II) NVIDIA(0): NVIDIA GPU NVIDIA GeForce GTX 1080 (GP104-B) at PCI:1:0:0

[ 8.677] (–) NVIDIA(GPU-0): Sharp CRX1200 (DFP-1): connected
[ 8.677] (–) NVIDIA(GPU-0): Sharp CRX1200 (DFP-1): Internal DisplayPort
[ 8.677] (–) NVIDIA(GPU-0): Sharp CRX1200 (DFP-1): 1440.0 MHz maximum pixel clock

This laptop display with the backlight (off in 565) is a Sharp CRX1200
It’s been off since “something changed” after version 470

b.

Xorg.0.log (38.5 KB)

[toastUnlimited]

Regression 565 PRIME offloading

Hi, been a while. I’m not really asking for direct help on this: I installed the 550 driver from the .run file, so I can just sit on it for a bit. This is more what can I do to help you all fix this issue, so I can go back to using a driver from the package manager. Games appear to crash with both DXVK and VKD3D when NVIDIA is the graphics renderer and an AMD is the primary Xorg renderer. This happens after a seemingly random amount of time spent in the application. I’ve seen it crash almost i…

I made this post on the forum generally and didn’t get a response in 9 days, so I thought I might try here?

Basically a Proton application will deadlock after up to 20 minutes when an NVIDIA GPU is rendering, and [something else] is the display adapter. Downgrading the driver fixed the issue, which is not an ideal solution.

[phoenix91140]

Eh a new problem appears. Driver 565.77 not working with kernel 6.13 that just arrived on distribution. Any fixes, NVidia, please? Closed driver, not open one. Urgent update, fix is highly appreciated. Thanks in advance!

[agarplayerarlon]

yeah same problem, I just get a black screen with 6.13

[phoenix91140]

Yeah, exactly. Hoping NVidia provides solution any time soon. Maybe this will help to NVidia to make newer version => nvidia-drm 565.77 fix for Linux kernel 6.13-rc1 · GitHub . Told to patch open driver, but I need the closed one, since gpu a bit old. But probably will help nvidia to use it as a start point for fixing driver compatibility

[shelter]

cachyos got a patch for the closed driver, i don’t know which one it is tho’, I can’t check right now

I’m using it now tho’ through the dkms package.

Linux auros 6.13.0-1-cachyos #1 SMP PREEMPT_DYNAMIC Mon, 20 Jan 2025 14:39:57 +0000 x86_64 GNU/Linux

NVIDIA-SMI 565.77

❯ nvidia-smi -q |grep GSP
    GSP Firmware Version                  : N/A

[phoenix91140]

Does it work normally? Please digg for patch, if possible

[shelter]

It works fine…

They are probably on the github page.

[phoenix91140]

Thanks. Hmm… As far as I understand there’s patching for open driver only

[shelter]

The PKGBUILD generates both the closed and open driver package. So they are there.
The CachyOS team is usually quite fast with their nvidia patches/fixes, this time around I haven’t been following it at all because most 6.13-rc Nvidia stuff was made during the holidays, at least when I was on holiday anyway.

[imgmedia]

Has anyone got a similar issue or even better a solution of this: I run an A5000 on latest Pop OS, with 565.77 drivers. The idle power consumption is constantly at 90 Watts at 0% utilization. Only short after the boot process the power consumption is below that. The card stays at P0, only sometimes, of <2 seconds it drops to P3 an immediately does back up to P0. When I run Ollama or python script power consumption of course goes up and then returns to about 90. Swapping the A5000 for an 4070 Super shows that idle mode works, so no background tasks or stuff.

Did anyone solve this issue?

[agarplayerarlon]

yeah I’ve tried it on CachyOS and it works, but on other distros I still get a black screen with 6.13

[faz]

Should be fixed on nixOS once linuxPackages_latest.nvidiaPackages.{stable,latest,beta}: fix build by Bot-wxt1221 · Pull Request #375838 · NixOS/nixpkgs · GitHub gets merged.

[faz]

Wayland compositor VRAM usage still seems to be way too high even after the fix at Xwayland VRAM usage is still excessive when resizing X11 apps under wayland. · Issue #126 · NVIDIA/egl-wayland · GitHub was implemented into the driver.

When I launch Hyprland on my PC, launch a term, and run nvidia-smi as fast as possible, I can see this:

vram usage of hyprland is about 400MiB.

If I keep running nvidia-smi every second or so, I see the vram keep going up and up and up, until 15 seconds later (see the timestamp on the first line of the output) it reaches over 1GiB:

This is entirely unacceptable, especially considering my 3070 only has 8gib vram. Its not a hyprland issue either, as I can use the same setup on my laptop, with the same monitors plugged in and vram usage is like 180MiB:

We need a fix for this in 570.

[luanv.oliveira]

570 will be released January 30th. (source)

[vkd3d_enjoyer]

Idk about that. To me it sounds like that is the latest possible it could drop.

I am told on 30 January for the retail availability launch date they will have a Linux driver available – just as we have been used to seeing for many years and NVIDIA product generations. So worst case scenario is waiting until the end of next week to be able to begin testing the GeForce RTX 5090 under Linux.

I really hope it has fixes for multimonitor vrr, DX12 performance, RT performance, idle power usage, vaapi, etc.

[andre.ocosta]

Thanks for the heads-up. I really, really hope it includes a fix for the suspend issue on notebooks 🙏

[dr.silens]

Multi monitor vrr confirmed fixed in 570. Driver is “available” already in fedora.

[shelter]

Nice find but you also provided a workaround. You can also add hyprland with lowercase to an own app profile yourself for the time being.

Generally, regarding the VRAM issue, they are working on a solution.

[andre.ocosta]

Cool! Which repo? RPMFusion non-free updates-testing doesn’t show it yet, and neither does negativo17.