565 release feedback & discussion

Graphics / Linux Linux
290

Still can’t mmap dma-buf with my RTX 2080 SUPER and AMD CPU with the latest 565.77 driver.

Edit: Power management is still broken.

291

Someone tested if this drivers still cause screen to randomly freeze?

292

For me works ideally (tested on kernel 6.12 only)

293

Shame, I expected it to be fixed ☹️

294

Also tested new 565 stable build. If I’m being honest it seems like nothing was even changed and Nvidia didn’t really fix any user submitted bugs in this release.

Suspend on open kernel modules still broken for me.
All the other mentioned issues also don’t seem to have a solution (these were posted in another comment by myself, I’d rather not do Nvidia a dirty and link it here again, I’m sure they’ve already seen it)

Guess we’ll wait for 570.

295

What issues? Nvidia added support for explicit sync and works on Wayland now. All bugs are fixed now.

1 Like
296

you’re right you’re right haha

seems like they’ve slacked a little since explicit sync was implemented but if you’re being serious about the bugs i am still having quite a few issues including suspend not working on open modules, high vram usage on wayland compositors, high vram usage / bad performance on a lot of games, games just outright not working. Here is the list of stuff i’ve experienced: 565 release feedback & discussion - #200 by faz

297

I know.

298

I also have started experiencing stutters after upgrading to the 565 beta, I haven’t tested the 565 stable yet but the stutters started appearing after like half an hour of gameplay, the game would start lagging/stuttering

299

this is a steam bug with their new game capture
you need to use LD_PRELOAD= %command% as game launch arguments

300

thank you, it’s nice to know that it’s not a nvidia bug
I wasn’t capturing the game tho

301

Yeap, it doesn’t matter if you are actually capturing

1 Like
302

thank you so much

303

This issue is still present with the 565.77 driver release, and is preventing use of the default Vulkan backend for GTK4 applications.

304

I had my hopes up with the 565.77 stable.
I’m still experiencing the same crashes and freezes I mention here

I’m always testing nobara40 and cachyos.
All of those using 6.11-6.13RC.
Mesa versions 24.2 - 24.3.1

still the same errors on nvidia and nvidia-open.
Is there anything I can do to help analyze those issues ?
I’m still stuck at 555 since almost half a year now and I’d really like to use the new features

305

Guess i stick with 555.58.02 driver. I have installed the latest one on another notebook, reviving the system from suspend you see weird glitches and then the login screen. It does not have it with the 555.58.02 driver. If nvidia wants i can post a video of it.

306

Just upgraded to 565.77, suspend still doesn’t work (detailed info on the previous post).

307

565.77 working great for me. Fixes the DVI regression. Thanks, Nvidia devs.

1 Like
308

565.77 still dumps this, doesn’t seem to be critical tho’ and might be kwin related only:

dec 07 08:41:29 auros kwin_wayland[1014]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
dec 07 08:41:43 auros kwin_wayland[1014]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.

And as mentioned, the vertex explosions in some games isn’t fixed, I was really hoping they would be gone.

1 Like
309

Vertex explosions are sadly still there. Also, i have to set fbdev=0 to even be able to load Hyprland, but this causes all my monitors to show up as 1 single monitor called “Unknown-1”. This driver version is basically unusable compared to the 560 driver for me