NVIDIA 510.68.02 Released As A Minor Bug Fix Update

[phoronix]

Phoronix: NVIDIA 510.68.02 Released As A Minor Bug Fix Release

NVIDIA released the 510.68.02 Linux driver today as a very minor bug-fix release...

https://www.phoronix.com/scan.php?pa...68.02-Released

[DanL]

NvFBC was requesting Vulkan 1.1 but actually using Vulkan 1.1

Typo. Should be 'requesting Vulkan 1.0'

[blacknova]

That is a lot of fixes for a month of work. Not.

[ezst036]

Kind of sad this might not address any of the big controversies happening right now. Between Ubuntu and SDL2 being held back by the spotty GBM and surrounding infrastructure items, we really need more assistance from Nvidia's driver team right now.

Their driver is stuck in 2019-Linux land and Nvidia doesn't want to move forward.

[birdie]

That is a lot of fixes for a month of work. Not.

A quick bug fix for those who needs it. If you don't, keep your current driver just like I do.

[Weasel]

Kind of sad this might not address any of the big controversies happening right now. Between Ubuntu and SDL2 being held back by the spotty GBM and surrounding infrastructure items, we really need more assistance from Nvidia's driver team right now.

Their driver is stuck in 2019-Linux land and Nvidia doesn't want to move forward.

Wayland is backward not forward.

[Hibbelharry]

Wayland is backward not forward.

Haters gonna hate.

[bearoso]

Their driver is stuck in 2019-Linux land and Nvidia doesn't want to move forward.

The driver is actually stuck in the 1990s. Nvidia only seems to want to focus on the use-case of one hardware-accelerated application at a time taking up the whole screen. That seems to work well. But add a second program multitasking or redirection like a compositor and it chugs. It's a shame, since they made it work fine on Windows.

[Paradigm Shifter]

Well, this update explains why my desktop broke yesterday. Quick and easy fix, but...

The driver is actually stuck in the 1990s. Nvidia only seems to want to focus on the use-case of one hardware-accelerated application at a time taking up the whole screen. That seems to work well. But add a second program multitasking or redirection like a compositor and it chugs. It's a shame, since they made it work fine on Windows.

They didn't really have a lot of choice as soon as Microsoft decided 3D acceleration for the desktop in Vista was going to happen come Hell or High Water, and then proceeded to drop the minimum GPU requirements so Intel Integrated could "run" Aero... which gave Vista a large portion of its not-entirely-deserved bad reputation. Combine that with manufacturers deciding they were going to refuse to make drivers for the new driver model (I'm particularly thinking of a certain scanner manufacturer...) which Vista used even on equipment which had been released just months before Vista released and... yeah.

[piotrj3]

Haters gonna hate.

There is nothing wrong with hating relativly low level graphic server that has implicit sync on buffers.

In general there is nothing wrong with having higher level APIs/graphics with implicit sync (dx11 and older, OpenGL, xorg).

There is nothing wrong (it is actually right thing) to have explicit sync API with lower level APIs/systems like Vulkan,DX12, Metal, Android graphics etc.

But Wayland does something inexplainably stupid, it combines low level with implicit sync. What means a ton of issues for running something like Vulkan on Wayland, and also means you need to assume on every single low level wayland call that you need to synchronize, even when many usages of that call absolutly doesn't need that call so you lose performance for nothing. That was noted by Intel engineer that he had cases when he missed to make explicit sync on side of vulkan that didn't make any error because wayland make acccidently sync on its side.