NVIDIA 495 Linux Beta Driver Released With GBM Support

[Myownfriend]

It can't be implemented well without support from Wayland.

Since when? GTK doesn't support fractional scaling with X11 or Wayland. Why would toolkits be prevented from supporting fractional scaling on one backend just because the other doesn't support it? GTKs lack of support for fractional scaling means that GTK applications really can't have looked any better in X11.

It's implemented by rendering everything at a higher resolution and downscaling.

Yes, I'm aware. It still results in a better DPI scaling experience than X11 though.

This is both wasteful of resources and makes it impossible to use subpixel hinting for antialiasing.

Why would that prevent sub-pixel hinting when the native frame buffer is higher resolution than the final buffer? If you render text at 4x resolution (2x along each axis) and then downsampled it to 66% of its rendered resolution then it would be impossible for that text to not have sub-pixel anti-aliasing via super sampling.

Nothing in particular, just user's needs. Simple things like clipboard functionality, screen sharing weren't even implemented properly for years because Wayland designers didn't think about them.

It still doesn't define a means of screen sharing, but it can do it. Wayland doesn't have to specify things like that.

Also you will notice the discussion around Wayland is still mostly stuck at DEs. Very few apps actually support Wayland and of those that do, they don't use it by default.

DE support kind of has to happen before app support, at least to some degree. Developers need means of testing

Fun fact: Wayland is now over a third of X's age, but nowhere near a third of X's adoption.

The X protocol has been around since 1984 when GUIs in computing were niche and I believe it was implemented into the X windowing system as it was being created. Wayland was just designed as a protocol released in text form. It's first commit was in 2008, after Windows Vista and the iPhone came out. The first stable release of it's client API was in version 1.0 in October of 2012 and the first stable release of it's server API was in version 1.2 in July of 2013. Regardless of which one of those points you're using to do you math, it's never over a third of X's age. In fact, two of those dates would make it less than a fourth of X's age. You're comparing two very different forms of release in two very different worlds of computing.

[Templar82]

I think the funniest thing about this is that Wayland was just starting to work for me by default in OpenSUSE KDE with Nvidia.

Still this is good news for everybody.

[You-]

If Anyone else is lost on the timelines due to two close releases:

1. 470 Driver - should support accelerated Xwayland, DMABUF etc. It also has same driver support compared to older drivers. For most this should have been enough for stable wayland, but the EGLStream implementation was found to have bgs late in the day that are not fixed.

2. 495 Driver series. This drops support for older cards (AFAIK Geforce 6xx and 7XX). Adds gbm, so will exercise same code paths as mesa drivers. However all software will need to delete or update hacks that forced gbm to not work on nvidia (gbm was disabled for nvidia driveras it can be done without hardware acceleration...). Bugs have also been found in the nvidia implementation of gbm that needs fixing. Older DE releases will NOT use Wayland with this driver wihout unpatching the previous workarounds.

All in all, good forward movememnt, but both paths are still buggy and one of the more prevalent bugs can cause transparent windows when using the proprietary nvidia drivers.

[Linuxxx]

Dishonored 2 went from playable to extremely playable with this driver, that being said, even the RX 6800 XT had some serious issues with that game across several cards in the 6000's series by multiple different owners. Dishonored 2 is also in my opinion one of those games that will really test the strength of a GPU aside from the opinion of mine that to date is one of the best games ever made.

Just curious, do you happen to own the game on Steam?
If yes, I take it shaders were already pre-cached for you, right?
And you were playing with default Proton settings, i.e. Esync enabled, or?

I ask because I own the GOG version and therefore don't have access to Steam's rather handy distributed shader cache system for this particular game.

Therefore I would get noticable compile-time stutter by default, however disabling Esync for Proton-GE dramatically improved the situation!

Anyway, that's why I'm asking in the first place...

[pWe00Iri3e7Z9lHOX2Qx]

Doesn't look different compared to 470

Supported products

NVIDIA TITAN Series:
NVIDIA TITAN RTX, NVIDIA TITAN V, NVIDIA TITAN Xp, GeForce GTX TITAN X, GeForce GTX TITAN, GeForce GTX TITAN Black, GeForce GTX TITAN Z

GeForce RTX 30 Series (Notebooks):
GeForce RTX 3080 Laptop GPU, GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU, GeForce RTX 3050 Ti Laptop GPU, GeForce RTX 3050 Laptop GPU

GeForce RTX 30 Series:
GeForce RTX 3090, GeForce RTX 3080 Ti, GeForce RTX 3080, GeForce RTX 3070 Ti, GeForce RTX 3070, GeForce RTX 3060 Ti, GeForce RTX 3060

GeForce RTX 20 Series (Notebooks):
GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060

GeForce RTX 20 Series:
GeForce RTX 2080 Ti, GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060 SUPER, GeForce RTX 2060

GeForce MX400 Series (Notebooks):
GeForce MX450

GeForce MX300 Series (Notebooks):
GeForce MX350, GeForce MX330

GeForce MX200 Series (Notebooks):
GeForce MX250, GeForce MX230

GeForce MX100 Series (Notebook):
GeForce MX150, GeForce MX130, GeForce MX110

GeForce GTX 16 Series (Notebooks):
GeForce GTX 1660 Ti, GeForce GTX 1650 Ti, GeForce GTX 1650

GeForce 16 Series:
GeForce GTX 1660 SUPER, GeForce GTX 1650 SUPER, GeForce GTX 1660 Ti, GeForce GTX 1660, GeForce GTX 1650

GeForce 10 Series:
GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030, GeForce GT 1010

GeForce 10 Series (Notebooks):
GeForce GTX 1080, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050

GeForce 900 Series:
GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950

GeForce 900M Series (Notebooks):
GeForce GTX 980, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M, GeForce GTX 960M, GeForce GTX 950M, GeForce 945M, GeForce 940MX, GeForce 930MX, GeForce 920MX, GeForce 940M, GeForce 930M

GeForce 800M Series (Notebooks):
GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M

GeForce 700 Series:
GeForce GTX 780 Ti, GeForce GTX 780, GeForce GTX 770, GeForce GTX 760, GeForce GTX 760 Ti (OEM), GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 745, GeForce GT 740, GeForce GT 730, GeForce GT 720, GeForce GT 710

GeForce 600 Series:
GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 645, GeForce GT 640, GeForce GT 635, GeForce GT 630

GeForce 600M Series (Notebooks):
GeForce GT 640M LE

NVIDIA RTX Series:
NVIDIA RTX A6000, NVIDIA RTX A5000, NVIDIA RTX A4000, NVIDIA RTX A2000, NVIDIA T1000, NVIDIA T600, NVIDIA T400

NVIDIA RTX Series (Notebooks):
NVIDIA RTX A5000 Laptop GPU, NVIDIA RTX A4000 Laptop GPU, NVIDIA RTX A3000 Laptop GPU, NVIDIA RTX A2000 Laptop GPU, NVIDIA T1200 Laptop GPU , NVIDIA T600 Laptop GPU, NVIDIA T500

Quadro RTX Series:
Quadro RTX 8000, Quadro RTX 6000, Quadro RTX 5000, Quadro RTX 4000, Quadro RTX 3000

Quadro RTX Series (Notebooks):
Quadro RTX 6000

Quadro Series:
Quadro GV100, Quadro GP100, Quadro P6000, Quadro P5200, Quadro P5000, Quadro P4000, Quadro P2200, Quadro P2000, Quadro P1000, Quadro P620, Quadro P600, Quadro P400, Quadro M6000 24GB, Quadro M6000, Quadro M5000, Quadro M4000, Quadro M2000, Quadro K6000, Quadro K5200, Quadro K5000, Quadro K4000, Quadro K4200, Quadro K2200, Quadro K2000, Quadro K2000D, Quadro K1200, Quadro K620, Quadro K600, Quadro K420, Quadro 410

Quadro Series (Notebooks):
Quadro T2000, Quadro T1000, Quadro P5200, Quadro P5000, Quadro P4200, Quadro P3200, Quadro P4000, Quadro P3000, Quadro P2000, Quadro P1000, Quadro P600, Quadro P520, Quadro P500, Quadro M2200, Quadro M1200, Quadro M620, Quadro M520, Quadro M5500, Quadro M5000M, Quadro M4000M, Quadro M3000M, Quadro M2000M, Quadro M1000M, Quadro M600M, Quadro M500M, Quadro K2200M, Quadro K620M

Quadro Blade/Embedded Series :
Quadro P5000, Quadro P3000, Quadro M5000 SE, Quadro M3000 SE

Quadro NVS Series:
NVS 810, NVS 510

GRID Series:
GRID K520

NVS Series:
NVS 810, NVS 5

Are you sure you looked at the right driver page?

Version:    495.29.05

[B]NVIDIA TITAN Series:[/B]
NVIDIA TITAN RTX, NVIDIA TITAN V, NVIDIA TITAN Xp, NVIDIA TITAN X (Pascal), GeForce GTX TITAN X, GeForce GTX TITAN, GeForce GTX TITAN Black, GeForce GTX TITAN Z

[B]GeForce RTX 30 Series (Notebooks):[/B]
GeForce RTX 3080 Laptop GPU, GeForce RTX 3070 Laptop GPU, GeForce RTX 3060 Laptop GPU, GeForce RTX 3050 Ti Laptop GPU, GeForce RTX 3050 Laptop GPU

[B]GeForce RTX 30 Series:[/B]
GeForce RTX 3090, GeForce RTX 3080 Ti, GeForce RTX 3080, GeForce RTX 3070 Ti, GeForce RTX 3070, GeForce RTX 3060 Ti, GeForce RTX 3060

[B]GeForce RTX 20 Series (Notebooks):[/B]
GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060

[B]GeForce RTX 20 Series:[/B]
GeForce RTX 2080 Ti, GeForce RTX 2080 SUPER, GeForce RTX 2080, GeForce RTX 2070 SUPER, GeForce RTX 2070, GeForce RTX 2060 SUPER, GeForce RTX 2060

[B]GeForce MX400 Series (Notebooks):[/B]
GeForce MX450

[B]GeForce MX300 Series (Notebooks):[/B]
GeForce MX350, GeForce MX330

[B]GeForce MX200 Series (Notebooks):[/B]
GeForce MX250, GeForce MX230

[B]GeForce MX100 Series (Notebook):[/B]
GeForce MX150, GeForce MX130, GeForce MX110

[B]GeForce GTX 16 Series (Notebooks):[/B]
GeForce GTX 1660 Ti, GeForce GTX 1650 Ti, GeForce GTX 1650

[B]GeForce 16 Series:[/B]
GeForce GTX 1660 SUPER, GeForce GTX 1650 SUPER, GeForce GTX 1660 Ti, GeForce GTX 1660, GeForce GTX 1650

[B]GeForce 10 Series:[/B]
GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030, GeForce GT 1010

[B]GeForce 10 Series (Notebooks):[/B]
GeForce GTX 1080, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 Ti, GeForce GTX 1050

[B]GeForce 900 Series:[/B]
GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950

[B]GeForce 900M Series (Notebooks):[/B]
GeForce GTX 980, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M, GeForce GTX 960M, GeForce GTX 950M, GeForce 945M, GeForce 940MX, GeForce 930MX, GeForce 920MX, GeForce 940M, GeForce 930M

[B]GeForce 800M Series (Notebooks):[/B]
GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M

[B]NVIDIA RTX Series:[/B]
NVIDIA RTX A6000, NVIDIA RTX A5000, NVIDIA RTX A4000, NVIDIA RTX A2000, NVIDIA T1000, NVIDIA T600, NVIDIA T400

[B]NVIDIA RTX Series (Notebooks):[/B]
NVIDIA RTX A5000 Laptop GPU, NVIDIA RTX A4000 Laptop GPU, NVIDIA RTX A3000 Laptop GPU, NVIDIA RTX A2000 Laptop GPU, NVIDIA T1200 Laptop GPU , NVIDIA T600 Laptop GPU, NVIDIA T500

[B]Quadro RTX Series:[/B]
Quadro RTX 8000, Quadro RTX 6000, Quadro RTX 5000, Quadro RTX 4000, Quadro RTX 3000

[B]Quadro RTX Series (Notebooks):[/B]
Quadro RTX 6000, Quadro RTX 5000, Quadro RTX 4000, Quadro RTX 3000

[B]Quadro Series:[/B]
Quadro GV100, Quadro GP100, Quadro P6000, Quadro P5200, Quadro P5000, Quadro P4000, Quadro P2200, Quadro P2000, Quadro P1000, Quadro P620, Quadro P600, Quadro P400, Quadro M6000 24GB, Quadro M6000, Quadro M5000, Quadro M4000, Quadro M2000, Quadro K2200, Quadro K1200, Quadro K620

[B]Quadro Series (Notebooks):[/B]
Quadro T2000, Quadro T1000, Quadro P5200, Quadro P5000, Quadro P4200, Quadro P3200, Quadro P4000, Quadro P3000, Quadro P2000, Quadro P1000, Quadro P600, Quadro P520, Quadro P500, Quadro M2200, Quadro M1200, Quadro M620, Quadro M520, Quadro M5500, Quadro M5000M, Quadro M4000M, Quadro M3000M, Quadro M2000M, Quadro M1000M, Quadro M600M, Quadro M500M, Quadro K2200M, Quadro K620M

[B]Quadro Blade/Embedded Series :[/B]
Quadro P5000, Quadro P3000, Quadro M5000 SE, Quadro M3000 SE

[B]Quadro NVS Series:[/B]
NVS 810

[B]NVS Series:[/B]
NVS 810

Kepler is gone.

Also, picking a Kepler from supported-gpus.json from the extracted installer...

"devid":"0x11B4","name":"Quadro K4200","legacybranch":"470.xx"

[vb_linux]

much simpler way:
- no novideo hardware
that's all

Thanks for our helpful suggestion!!

I ordered AMD gpu with my setup and after two months of waiting vendor told me too with either 3070 or cancel the order because AMD did announce the cards but there was nothing on the market last year.

[shanedav4]

I must say the beta 495.29.05 driver is working way better than the current non beta. I just installed it on Arch using Gnome and the animations are way smoother or at least they seem that way. Had an issue with Chrome not opening a window but i deleted the .cache and .config folders for Chrome and now it works fine. Nvidia-Settings is still not working on Wayland. I installed GPU-Viewer and it does show that the Nvidia driver is using Mesa, which wasn't there before. One thing that is strange is that GPU-Viewer is not showing the config for Vulkan like it normally does. I had to install Vulkan Caps Viewer to see Vulkan information, but everything seems to be ok in it. I haven't run any games yet but plan to later tonight. I tried installing EGL-Wayland from git because it is newer than the one installed. System didn't like it so I had to go back to the older one. I'm going to try installing the Dev version of Mesa next and see what that combined with the 495 driver bring. I hope it's not headaches.

[Turbine]

That's great and all, but I haven't been able to run a Steam game in over a year using proton and Fedora/Ubuntu with the Nvidia driver.

[IndioNuvemChuva]

Why would that prevent sub-pixel hinting when the native frame buffer is higher resolution than the final buffer? If you render text at 4x resolution (2x along each axis) and then downsampled it to 66% of its rendered resolution then it would be impossible for that text to not have sub-pixel anti-aliasing via super sampling.

Subpixel hinting necessarily relies on rendering to a surface that is the same resolution as the target surface, downscaling and filtering will absolutely remove any trace of it. And, while you're right that scaling down images rendered at higher resolutions does also provide anti-aliasing, you have to remember that legible and smooth aren't the same, and often times scaling fonts rendered at high resolutions down gives them a fuzzy look which can be pretty harsh on the eyes. You can see that for yourself if you open GIMP, type a few words on a high resolution canvas then scale it all down using Sinc.

It still doesn't define a means of screen sharing, but it can do it. Wayland doesn't have to specify things like that.

Wayland is designed in such a way there's nothing between the display and the compositor that can be talked to and that has the complete screen frame. For screen capture, this means that there has to be some protocol for applications to get this information from the compositor. Right now, it is being achieved through protocols and standards running parallel to the Wayland spec, totally separate from it.

This means there's yet another aspect of fragmentation being added to the already frankly staggeringly fragmented Wayland ecosystem, just to add basic functionality that lots of people rely on. Now, thinking whether specifying standard protocols for common functionality most compositors should be expected to provide is Wayland's job is up to you, but, personally, I think it should be.

[Myownfriend]

Subpixel hinting necessarily relies on rendering to a surface that is the same resolution as the target surface, downscaling and filtering will absolutely remove any trace of it. And, while you're right that scaling down images rendered at higher resolutions does also provide anti-aliasing, you have to remember that legible and smooth aren't the same, and often times scaling fonts rendered at high resolutions down gives them a fuzzy look which can be pretty harsh on the eyes. You can see that for yourself if you open GIMP, type a few words on a high resolution canvas then scale it all down using Sinc.

I understand that simply super sampling isn't the same thing, but that doesn't mean that sub-pixel hinting can't be done this, it just can't be done in the same way.

Fractional scaling may seem straight forward when you're just thinking about fonts but how would you propose handling fraction scaling of thin borders for example?

Wayland is designed in such a way there's nothing between the display and the compositor that can be talked to and that has the complete screen frame. For screen capture, this means that there has to be some protocol for applications to get this information from the compositor. Right now, it is being achieved through protocols and standards running parallel to the Wayland spec, totally separate from it.

And that's fine. It looks like fragmentation only because people are used to Xorg which is a suite of tools and window system built around a protocol. X doesn't define a method of capture either. The tools that people use to capture under X are just tools that come with Xorg which exploit the fact that X allows any application to see the contents of every other window. It's a security flaw that people talk about as a feature.

This means there's yet another aspect of fragmentation being added to the already frankly staggeringly fragmented Wayland ecosystem, just to add basic functionality that lots of people rely on. Now, thinking whether specifying standard protocols for common functionality most compositors should be expected to provide is Wayland's job is up to you, but, personally, I think it should be.

Why should it be Wayland's job? Why can't it be a protocol for a specific thing? Why be an all encompassing pseudo-OS like Xorg?