Display Stream Compression (DSC) support #238
Replies: 31 comments 53 replies
-
|
Yes, thanks. The Linux driver in general does support DSC, but not yet at the higher rates that you're referring to. I don't have an ETA for that, but we know it is an important feature that many people are asking for. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
One of the real-world examples where it's needed are 5120x1440@240Hz monitors like Samsung Odyssey (neo) G9, which seems to be moderately popular among gamers. |
Beta Was this translation helpful? Give feedback.
-
Thank you for confirming this. |
Beta Was this translation helpful? Give feedback.
-
|
Just bought a 3080, while I dual boot into windows for some games I'm kinda disappointed this was not supported. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Nvidia folks. The lack of DSC support in Unix drivers is problematic at this point. More and more display require it ti use their full spectrum of modes: 5120x1440@240Hz (Samsung Odyssey G9 (Neo)), 4k@>120Hz (Acer XB323K, Samsung Neo G8, Samsung Ark, Sony Inzone M9, Acer X32 FP, Samsung Neo G7, HP Omen 32u). |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your answer @aritger . Also have an Odyssey G9, and I have kept Windows separately for this reason. It was also buggy and took a long time to solve on Windows, both from Samsung and from NVIDIA, but it was eventually sorted. At least bring us some kind of compatibility with DSC at these refresh rates (which are quite common nowadays). AMD at least gives the option to set the resolution and refresh rate. There is visual noise and artifacts but people found a way to solve it. At least give us the option. Thank you. PS: Is there any kind of ETA since this is a problem with over 2 years now? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we definitely appreciate the priority of this. We're trying to get this support in place for our 530.xx release series, but dates are always in flux, so I can't give a firm ETA. |
Beta Was this translation helpful? Give feedback.
-
|
@3dpt & @aritger But the problem is still not solved on Windows. The dsc always crashes when you have a full screen app/game and a windows popup appears. Especially the samsung g9 goes black. |
Beta Was this translation helpful? Give feedback.
-
|
@rakuri255 I used to have that problem in Windows as well when I bought my G9. What firmware are you on? Check the monitor firmware version, update to newest version, and check if you have newest nvidia drivers available. Make sure you uninstall previous drivers (you can use Display Driver Uninstaller for this). I can guarantee that the problem is solved in Windows, and has been for a few years now. If you have that problem with newest monitor firmware and graphics drivers, you can check online if there are other fixes, but in the meantime, you can contact Samsung, as you might have a defective unit. |
Beta Was this translation helpful? Give feedback.
-
|
@3dpt thanks for the help! The G9 is up to date. I tried a few driver versions and found that the problem has been occurring since version 526.47. I am now using the older version 522.25 where it currently works. |
Beta Was this translation helpful? Give feedback.
-
|
I also have a G9 Odyssey, which I have had since release and never have been able to use the 240hz 5120x1440 side of it. Very interested to see this implemented |
Beta Was this translation helpful? Give feedback.
-
|
It works sometimes on my neo g9. But when you get an popup in win11 (like the volume bar) it crashes and goes black screen. |
Beta Was this translation helpful? Give feedback.
-
You might be in the wrong repo my dud |
Beta Was this translation helpful? Give feedback.
-
|
Yeah i seen that to late :D |
Beta Was this translation helpful? Give feedback.
-
Same here. Would love to see that implemented |
Beta Was this translation helpful? Give feedback.
-
|
Not having DSC also prevents the majority of modern VR headsets from running on their native resolutions. With SteamVR being usable on Linux, it's actually an issue now. |
Beta Was this translation helpful? Give feedback.
-
|
With 8k monitors coming in 2023,, would be great to see this released... we cannot expect people to use 8k in 30hz, specially with these monitors costing as much as they will cost. 8k @ 60hz is a must for basic productivity. |
Beta Was this translation helpful? Give feedback.
-
NVIDIA have still not released necessary drivers to support high pixel clock modes for DSC. It's been years, and still nothing. What a complete joke. |
Beta Was this translation helpful? Give feedback.
-
|
I've had an 8K display (Samsung QN800A) for almost two years now and still stuck on 30 Hz haha. In fact, an 8K display is not that expensive nowadays, you can get one for $2000. It's like having four 4K displays in a grid, it's amazing for looking at terminals. But I am excited about driver version 530 which will hopefully finally enable 60 Hz. |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, Any update on this implementation ? Hey, nvidia, please prioritize this, please :-) Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
I apologize again for the delays in delivering this. This is still prioritized and receiving engineering attention. Unfortunately, I do not have an ETA at this time. Thanks for your patience. |
Beta Was this translation helpful? Give feedback.
-
|
Without giving an ETA, can you tell us if this feature is still planned for 530.xx drivers, as you mentioned a few months ago, or if it is being pushed back further? Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
We're working to provide this feature, but I can't say for certain whether it will be in 530.xx. Thanks again for your patience. |
Beta Was this translation helpful? Give feedback.
-
|
Well, looks like it didn't make the 530 drivers cut :( @aritger are you able to tell us if they have actually started work on it? Wondering if I sell my GPU and buy an AMD. |
Beta Was this translation helpful? Give feedback.
-
|
@ElRoberto538 You're always better off with AMD on Linux, so if you can switch, I'd highly recommend it. The situation will not get better, only worse: AMD is actively working on HDR support for Linux, so AMD cards will be among the first to support it. Meanwhile, NVIDIA on Linux is still struggling with the basics and far away from anything new that's a little more complex such as HDR. And if you want to use Wayland, well, then AMD is basically still your only option (plenty of applications still only render a black window, night mode etc. still don't work, etc.). And you can't even fix things yourself or implement new features, like with AMD, so if NVIDIA isn't working on the fixes/features you want, you're just out of luck. // Edit: To be clear here, I am not blaming the engineers. This is a management problem at NVIDIA, which still does not prioritize Linux work. |
Beta Was this translation helpful? Give feedback.
-
Not sure why your comment was down-voted tbh. It's not going to taste well sitting on an nVidia related discussion, but it's definitely the truth. Had I known a while back now how much I was going to get in to Linux I honestly wouldn't have bought my RTX 3090. Is it nice to have the ability to run LLMs locally and all that jazz? Yeah it is... but the near constant frustrations I have had on Linux with Nvidia have cost me countless hours of problems. In one case I had 2 separate Linux images on 2 USBs, and I couldn't get either to boot for the EXACT same reasons. Being Nvidia driver issues. Yes other distros worked, but it seems to be a consistent issue in some form or other. Now just after purchasing this monitor, and having a (now known to be fruitless) play around with cabling, switching on/off, kernel updates, driver updates and Googling around.. I find that just shy of 3 YEARS after this monitor released, Nvidia have failed to provide any support in their drivers. That is... insane. They say they are working on it, but I work in the tech industry, that answer is absolutely meaningless without a date attached, and I could almost guarantee they literally have no deadline they are expected to meet to get this working. We don't have the numerical fortitude to get them to actually prioritise this and it's just extra frustrating in that my only options to get it are to switch to Windows (why should I have to??) or give it back. I had a look back at some Reddit posts and they were releasing hotfixes for Windows back in 2020 for their drivers and this screen resolution.... I repeat... it's just under 3 YEARS later, and we still don't have any Linux support. That should tell you all you need to know about how much they care. |
Beta Was this translation helpful? Give feedback.
-
|
Came here to add my support for this functionality being added. I am hoping it does make the 530 release because being locked into lower refresh rates isn't ideal. Hoping this gets more prioritization!!! Kind of surprised how long these requests have been outstanding! This needs to get more traction! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we're actively working on the support to drive these high resolutions. I think if you look at the changes in src/nvidia-modeset/ for 530.03.02, quite a bit of the ground work is there (the "apiHead" vs "hwHead" separation, to allow multiple heads to be used to drive one extreme high refresh rate), but it unfortunately was not complete in time for 530.03.02. |
Beta Was this translation helpful? Give feedback.
-
|
530.41.03 has, for example, |
Beta Was this translation helpful? Give feedback.
-
|
DSC has been supported in the NVIDIA Linux GPU driver for quite some time. To drive these extremely high pixelclock modes on current NVIDIA hardware requires reprogramming the display hardware in a special way, ganging multiple "heads" together to drive these pixelclocks. That's really what this thread is asking for, and what I hope we're finally close to shipping. Thanks for your patience. |
Beta Was this translation helpful? Give feedback.
-
|
@aritger I know, you've explained it before, but from the end user's point of view, these modes which have a pixelclock rate greater than HDMI bandwidth without DSC don't work, and all of the modes that have a bandwidth that don't require DSC work. With the lack of better terminology (since we don't have an easy way to describe it), users are looking for DSC support to get these high bandwidth modes working. In any case, I've managed to get 530.41.03 installed, and as you've confirmed, these high bandwidth modes are not yet shipping. |
Beta Was this translation helpful? Give feedback.
-
|
The terminology is kind of confusing and I apologize that we've been struggling to explain the limitations clearly. You're right that DSC is needed in order to push the number of pixels required for these high-bandwidth modes through HDMI. DSC is also used for DisplayPort and having it enabled allows modes to work on lower-bandwidth links that would otherwise be rejected. That part is working today. However, the HDMI or DisplayPort link isn't the only bandwidth limit within the GPU. The problem we're running into here is that even though DSC unlocks higher effective bandwidths over HDMI or DP links, the part of the display engine that fetches pixels from memory and formats them for transfer over the physical display link has its own internal bandwidth limit. In the driver source code here, you'll see this unit referred to as a "head". In upstream DRM terminology it's referred to as a "CRTC". You can consider those to be synonymous. As Andy mentioned, in order to push enough pixels into the display connector to support high bandwidth modes, we need to program the GPU to use two heads simultaneously. That's the part that we're working on now. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the explanation @aaronp24 Spawn that async head worker! |
Beta Was this translation helpful? Give feedback.
-
|
Nvidia.. (note: a company whose 2023 revenue was $27billion), haven't been able to get this working on Linux after 3 years. I find this near insulting as a consumer of your products since I was a teenager. That is over 20 damn years of buying Nvidia graphics cards going back to a Geforce3 Ti200. I, personally, have spent £1000s of my personal cash on your products and I'm at a point now where I've realised I have absolutely no reason to show any brand loyalty to Nvidia anymore and will be jumping ship the minute my current card has had it's time. It's worse than this, the main advertising page for the RTX 3090 (the card I own personally) actually states this right in bold text: Well that's not true is it? And it's more annoying that the "up to" was likely legal jargon to allow you to say that given it doesn't actually work on some operating systems right? This monitor, (I say that like it's the only really high res screen in existence (it's not)), came out just shy of 3 years ago... no support. Someone asks on here, May 2022 (likely ran out of patience already)... -- November 2022 response: -- Feb 2023 response: -- End of Feb 2023 response: -- April 2023 response: If you worked for me and you didn't have something working on Linux that you had working on Windows 3 YEARS ago, you'd be sacked. Of course, the issue and the problem itself isn't actually the technical skill or knowledge of their engineers.. it's the fact that it is a mega profit-driven organisation who quite clearly under no drive to devote any time to niche consumer problems. I almost want my 3090 and my Intel i7 to die at this point, as it's a tiny push at the end of a long road of pushes for me to completely switch to AMD. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
"Added support for driving very high pixel clock mode timings such as 8K @ 60Hz. Please see the "MaxOneHardwareHead" X11 ModeValidation token in the README for details." |
Beta Was this translation helpful? Give feedback.
-
|
Can I get a link for the README file? |
Beta Was this translation helpful? Give feedback.
-
|
http://us.download.nvidia.com/XFree86/Linux-x86_64/535.43.02/README/xconfigoptions.html But, starting with 535.43.02, these higher refresh rate modes should work by default; MaxOneHardwareHead is just there as a way to turn that off if it causes |
Beta Was this translation helpful? Give feedback.
-
|
No... way. I tried it temp on random Arch build.. yup. It works. Waiting for AUR nvidia-beta to be updated. Tried to modify/create my own PKGBUILD and it went miserably... so I will just wait for the community to catch up (Arch user). |
Beta Was this translation helpful? Give feedback.
-
|
It appears to be working for me (4k@144Hz), though somewhat surprisingly still via just one hardware head like when it last worked with 470 drivers. I believe the referenced setting is only needed if you want to limit it to one hardware head for some reason: |
Beta Was this translation helpful? Give feedback.
-
|
I'm glad it is working for you, now. That it worked for you in 470.xx makes me suspect there was some other bug that was causing your problem, and not missing support for the functionality that "multiple hardware heads" enables. But, in any case, I'm glad your issue is resolved. |
Beta Was this translation helpful? Give feedback.
-
|
somewhere I saw a credible theory at one point that some hard-coded threshold that forced either DSC, multiple hardware heads or both may have changed causing some configurations that worked despite lack of support for those things to break. I figured if that was true that support for those things should also fix my issue, which one way or another seems to have happened. Thanks for all the updates as this worked its way through the development process! |
Beta Was this translation helpful? Give feedback.
-
|
for completeness, here is the info under 470 drivers. Seems like back under 470 it would drive it via dual connection link where as of 535 it now works again but as single link. I assume this means some other issue with the drivers 490-530 made it always try and fail to use a single link rather than dual, now with DSC it succeeds with a single link. I do wish I had a method to force dual link to allow it to work while these new drivers work there way out of the beta stage. |
Beta Was this translation helpful? Give feedback.
-
|
Lovely, can't wait to use 280hz on my desktop |
Beta Was this translation helpful? Give feedback.
-
|
For those who were struggling on Ubuntu with installing the beta from the nvidia download portal, add the beta repo: sudo add-apt-repository ppa:graphics-drivers/ppa Then do the general apt update, then from "Additional Drivers", install the nvidia-driver-535 option. It'll ask for a UEFI password. During the next reboot, you'll need to import the key to UEFI, then after reboot it works as expected. |
Beta Was this translation helpful? Give feedback.
-
|
Been having a nightmare trying to find a package manager that actually packages the latest beta in a timely manner. Not updated on AUR yet and manual steps are a bit.... prone to issues... I'll patiently wait for it to appear on AUR. I've tested it and it does work though. Finally. |
Beta Was this translation helpful? Give feedback.
-
|
nvidia-all by frogging family |
Beta Was this translation helpful? Give feedback.
-
|
(Since multiple people did this now:) This is not really the right place to discuss your distribution's packaging. This is about the kernel module for the NVIDIA driver and what downstream distributions do with it belongs on a distribution's bug tracker, not here. Discussing your distribution here a.) spams NVIDIA employees who get less motivated to fix bugs b.) makes it easy to miss regressions someone reports c.) spams everyone who is subscribed to this bug, most of which are not using your distribution. |
Beta Was this translation helpful? Give feedback.
-
|
As a follow-up, I can report that an RTX 3080 with a TCL 65R648 (8k 6-series from 2 years ago) works fantastically at 8k60Hz! |
Beta Was this translation helpful? Give feedback.
-
|
When reading about the new ability to use multiple heads in 535.54.03 I noticed the following:
I'm a bit confused by this - I have a 1080 Ti and my 3440x1440 display has no problem reaching 160Hz with the Windows driver but is limited to 144Hz on Linux. I imagine this is then unrelated to the multiple heads issue? For reference the display has a built in "overclock" feature that is enabled and allows it to reach 160Hz. |
Beta Was this translation helpful? Give feedback.
-
|
No 160Hz option presented. I switched to daily driving Linux at driver 515 and haven't ever been able to go above 144Hz. I'll have to try 470 when I'm free. |
Beta Was this translation helpful? Give feedback.
-
|
You probably have the same LG monitor I had. It doesn’t need nor does it support DSC, so that’s entirely unrelated to this issue. The monitor stops reporting 160 Hz when using a HDR mode, so maybe some initial HDR support was added to the NVIDIA driver and that’s the reason. |
Beta Was this translation helpful? Give feedback.
-
|
It's the 34GP83A-B and HDR is disabled but perhaps there is some bug around that. This issue is probably best asked in the NVIDIA Linux forum. |
Beta Was this translation helpful? Give feedback.
-
|
@crimist: Yes, I think your issue is unrelated to the DSC + multiple-heads-driving-one-monitor-behind-your-back functionality of this Issue. It would probably be best to start a new thread on the NVIDIA Linux forums. I would suggest adding the "ModeDebug" X configuration option to your X config file ( |
Beta Was this translation helpful? Give feedback.
-
|
@aritger Thanks for the suggestion. For anyone following along I've filed the issue on NVIDIAs Linux forums here. |
Beta Was this translation helpful? Give feedback.
-
|
The support requested in this discussion is available in the 535.xx drivers. I'm going to go ahead and close this discussion thread. Please start new threads if there are specific problems with the functionality. |
Beta Was this translation helpful? Give feedback.
-
|
I upgraded to
I think it's some kind of compression artifact or a bug that is quite annoying to look at. I also don't know if this is a driver issue or a problem with my monitor. Is this normal when running at maximum data rates? |
Beta Was this translation helpful? Give feedback.
-
|
I'll wait for feedback and then I'll create a new thread if this is an issue that should be reported. |
Beta Was this translation helpful? Give feedback.
-
|
You seem to have an Odyssey Neo G9 (or maybe also non-Neo). This is a known defect with this monitor. Some exhibit it more than others, but it is an issue with the panel and I suggest you RMA it and try the lottery of getting one without issues again.Am 15.11.2023 um 16:07 schrieb Itay Grudev ***@***.***>:
@aritger
I upgraded to 535.129.03 but I am observing some visual artifacts when running at ***@***.***
Frequency
Sample
Description
120Hz
Normal pixel blending
240Hz
Note how every second pixel row is brighter.
I think it's some kind of compression artifact or a bug that is quite annoying to look at. I also don't know if this is a driver issue or a problem with my monitor. Is this normal when running at maximum data rates?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I'm having an issue with 3440x1440@240hz on the latest 535, 545, and 550 drivers |
Beta Was this translation helpful? Give feedback.
-
|
i have a odesy g7 neo miniled, 4k 165 herz. the option 165 hertz 4k is aviable, but selecting it causes the monitor to go into a infinite loop of going on and off again. it does work 144 hertz the problem is not the hdmi cable |
Beta Was this translation helpful? Give feedback.
-
|
On linux, when exiting fullscreen vrr at 4k 144hz the screen goes blank (for instance in a FS YouTube video on brave browser). |
Beta Was this translation helpful? Give feedback.
-
|
Same happens to me. Turning dsc off or disabling adaptive sync fixes it. Doesn't happen with the closed driver. I also sometimes get random system freezes with dsc on, mostly happens when starting any video on youtube. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using the proprietary driver + X11 + KDE, and I've also been experiencing random freezes with DSC on. I recently got two 4K 240Hz monitors for my ThinkPad X1 Extreme Gen 5 (3080 Ti, firmware 94.03.19.40.2D). One of them is connected via HDMI 2.1 and the other one via USB Type-C (DP Alt 1.4). There are no issues whatsoever if I choose 120Hz. However, when I bump them up to 165/200/240Hz, every now and then one or both of my screens freeze, and I have to go through (sometimes partial) REISUB. Interestingly, even when both screens froze, I often could still move my cursor around. Freezes usually happen after two or three hours of use. When I still had one working screen, I could issue No matter what exactly happened, I could see logs similar to: (@Thorium0 Did you also see similar logs?) I had this issue with version 570.86.16, 570.124.04, 570.133.07, and also now with 570.144. xrandr output FYIScreen 0: minimum 320 x 200, current 7680 x 2160, maximum 16384 x 16384
eDP-1 connected (normal left inverted right x axis y axis)
3840x2400 60.00 +
3840x2160 59.97
3200x1800 59.96 59.94
2880x1620 59.96 59.97
2560x1600 59.99 59.97
2560x1440 59.99 59.96 59.95
2048x1536 60.00
1920x1440 60.00
1856x1392 60.01
1792x1344 60.01
2048x1152 59.99 59.98 59.90 59.91
1920x1200 59.88 59.95
1920x1080 60.01 59.97 59.96 59.93
1600x1200 60.00
1680x1050 59.95 59.88
1400x1050 59.98
1600x900 59.99 59.94 59.95 59.82
1280x1024 60.02
1400x900 59.96 59.88
1280x960 60.00
1440x810 60.00 59.97
1368x768 59.88 59.85
1280x800 59.99 59.97 59.81 59.91
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 56.25
840x525 60.01 59.88
864x486 59.92 59.57
700x525 59.98
800x450 59.95 59.82
640x512 60.02
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
640x400 59.88 59.98
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-1-0 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-0 connected 3840x2160+3840+0 (normal left inverted right x axis y axis) 700mm x 390mm
3840x2160 60.00 + 240.00 199.98 164.99 119.88* 100.00 59.94 50.00 29.97 25.00 23.98
2560x1440 239.97 120.00 59.95
1920x1080 239.99 119.88 100.00 59.94 50.00 23.98
1680x1050 59.95
1600x900 60.00
1440x900 59.89
1440x480 59.94
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 100.00 60.00 59.94 50.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x480 59.94
640x480 75.00 72.81 59.94
DP-1-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 690mm x 390mm
3840x2160 60.00 + 240.00 199.98 164.99 119.88* 100.00 59.94 50.00 29.97 25.00
2560x1440 239.97 120.00 59.95
1920x1080 239.99 119.88 100.00 59.94 50.00
1680x1050 59.95
1600x900 60.00
1440x900 59.89
1440x480 59.94
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 100.00 60.00 59.94 50.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x480 59.94
640x480 75.00 72.81 59.94
DP-1-3 disconnected (normal left inverted right x axis y axis)
2560x1440 (0x53) 241.500MHz +HSync -VSync
h: width 2560 start 2608 end 2640 total 2720 skew 0 clock 88.79KHz
v: height 1440 start 1443 end 1448 total 1481 clock 59.95Hz
1680x1050 (0x63) 146.250MHz -HSync +VSync
h: width 1680 start 1784 end 1960 total 2240 skew 0 clock 65.29KHz
v: height 1050 start 1053 end 1059 total 1089 clock 59.95Hz
1280x1024 (0x6a) 108.000MHz +HSync +VSync
h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 63.98KHz
v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz
1280x960 (0x6d) 108.000MHz +HSync +VSync
h: width 1280 start 1376 end 1488 total 1800 skew 0 clock 60.00KHz
v: height 960 start 961 end 964 total 1000 clock 60.00Hz
1280x800 (0x74) 83.500MHz -HSync +VSync
h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 49.70KHz
v: height 800 start 803 end 809 total 831 clock 59.81Hz
1024x768 (0x7b) 65.000MHz -HSync -VSync
h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz
v: height 768 start 771 end 777 total 806 clock 60.00Hz
800x600 (0x8a) 40.000MHz +HSync +VSync
h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz
v: height 600 start 601 end 605 total 628 clock 60.32Hz
800x600 (0x8b) 36.000MHz +HSync +VSync
h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz
v: height 600 start 601 end 603 total 625 clock 56.25Hz
640x480 (0x97) 25.175MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz
v: height 480 start 490 end 492 total 525 clock 59.94Hz |
Beta Was this translation helpful? Give feedback.
-
|
I'm using nvidia-open-dkms + wayland + kde. This is the error I get (log is reversed): |
Beta Was this translation helpful? Give feedback.
-
|
Ever since I moved to the 570 series, I have frequent 1 second black screens when the whole screen updates if DSC is enabled. This doesn't happen when DSC is not used, or in earlier driver series for me. 3090, open gpu module, both happens with the open and the closed source driver. |
Beta Was this translation helpful? Give feedback.
-
|
this has happened for me on my 4090 through all nvidia driver versions (535-575, open and closed) |
Beta Was this translation helpful? Give feedback.
-
|
Oh! I think it's related to switching between VRR and Non VRR. I changed my VRR setting in KDE's display settings from adaptive to always and I can no longer reproduce the issue. So both no DSC + Adaptive VRR and DSC + Always VRR are fine. EDIT: DSC + Always VRR is much better but not perfect, I just had a random flicker. EDIT2: DSC + Always VRR seems to randomly go to black screen when the GPU is in low power state? |
Beta Was this translation helpful? Give feedback.
-
|
OMG has this been the issue with monitor all along? It felt like there was a pattern for these 1 second "No Signal" interrupts on DisplayPort but could not put my finger on it. Now I read this and yeah I think it only happens on full screen updates. I'll look into changing VRR settings and see what happens. |
Beta Was this translation helpful? Give feedback.
-
|
I should be clear that it's still a linux nvidia driver bug, as it does NOT happen on Windows |
Beta Was this translation helpful? Give feedback.
-
|
Yes I'm also talking about the Linux drivers. In my case, "Always VRR" does not work at all, "Adaptive VRR" causes problems in certain games and "No VRR" works perfectly fine. This is for DisplayPort only, HDMI works fine. Monitor: GigaByte GS27U (DP 1.4 DSC) GPU: RTX 5070 Ti OS: Arch Driver: 570.144 DE: KDE on Wayland |
Beta Was this translation helpful? Give feedback.
and others
-
DSC allows people to drive 4k/240hz and 8k/60hz displays with DP 1.4 and HDMI 2.1. The NVIDIA driver for Windows supports this however the Linux one doesn't. Many people in the Linux Gaming community want this and moving into the future 8K or high refresh rate 4k will become more common for movies or gaming. Linux is a great choice for building a media center pc and nvidia cards are best in class for decoding video such as 8k60 so such a feature would be more than welcome
Beta Was this translation helpful? Give feedback.
All reactions