FS#77975 - [nvidia] 530.41.03-1 high refresh rate problems

Attached to Project: Arch Linux
Opened by Konstantin (imlegr) - Friday, 24 March 2023, 02:46 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 15 June 2023, 17:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No

Details

Description:
After the last driver update for my video card, my main monitor in wayland stopped working.

The graphics card is an Nvidia 4080.
Main monitor: 144Hz 2k - not working.
Second monitor: 75Hz 1080p - works.

If I set the resolution below 2k or refresh rate below 144Hz - then both monitors work.

Additional info:
nvidia-dkms 530

Steps to reproduce:
Update the drivers and boot into a Wayland session
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 15 June 2023, 17:04 GMT
Reason for closing:  Fixed
Comment by Nikita (mcmodder) - Friday, 24 March 2023, 13:25 GMT
I have simular issue after updating to xorg-xwayland 23.1.0 and nvidia 530.41.03:
Any fullscreen xwayland app "freezes" image on my monitor (1440p 60Hz), killing xwayland app does not help.
I tried to downgrade nvidia drivers to 525.89.02 - fullscreen apps are working, but with lots of visual glitches.

After downgrading xorg-xwayland back to 22.1.8, both 530.41.03 and 525.89.02 drivers are working without freezing/glitching in fullscreen apps.
Comment by Vlad (BoneFeaR) - Friday, 24 March 2023, 17:45 GMT
I have issues also with 530 driver.
NVIDIA RTX 3090. Hyprland ( wayland ) + 2 monitor setup. One is 2k 240hz, second is 1080p 60fps. Nvidia 530 ( tried nvidia-open-dkms also ), xwayland 23.1.0-1.
All games ( wine/native ) shows visual corruptions if i move cursor out of main monitor. Also when i move cursor out of main monitor, fps drop from 237 to 120.
People on hypr discord also report problems with 530 driver. Black screen on high HZ monitor + image corruption in games.
Comment by jk (su1) - Friday, 24 March 2023, 18:17 GMT
Same here with the RTX 4080, two monitors. Only 60hz is ok'ish, but cannot change to anything above that.
Will try to downgrade the NVIDIA now.

Edit: Just tried to downgrade the xorg-xwayland back to 22.1.8 and It did not work for me. Still freezing and not working main monitor when change to 170mhz.
Tried the latest NVIDIA and NVIDIA-Utils as well as 525.89.02, same story. Unfortuantely.
Comment by Toolybird (Toolybird) - Friday, 24 March 2023, 21:12 GMT
https://old.reddit.com/r/archlinux/comments/1206ffa/is_nvidia53041031_borked_just_for_me_or_everyone/

This is an upstream issue and not an Arch packaging problem. It needs to be reported to Nvidia. Also a reminder, folks must double-check to ensure initramfs is regenerated when using Nvidia drivers.
Comment by Konstantin (imlegr) - Friday, 24 March 2023, 22:04 GMT
What do I end up doing? Nothing works for me. Not X, not Wayland. My computer is only good for typing right now. I've tried rolling back drivers and it's no use. I don't want to go back to windows. I need to do something urgently or I will just lose my job.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 24 March 2023, 23:08 GMT
As another data point, I run X11 on 144hz screen at 1440p and that works fine for me on these drivers. Can you guys link the upstream bug reports from the NVIDIA forums and xorg-wayland here?
Comment by Konstantin (imlegr) - Friday, 24 March 2023, 23:32 GMT
I don't quite understand exactly what you're suggesting we do. The point is that I can't do anything at all on my computer. I have tried every possible option and solution. I lowered the frequency to 60Hz, I turned off monitors, I even reinstalled the system completely. Even going back to the old drivers doesn't help! When I run FurMark it says: OpenGL. Not a single game will run.

I have to work and my computer is only good for typing right now. I'm just desperate and don't know what to do.
Comment by Nikita (mcmodder) - Friday, 24 March 2023, 23:36 GMT
@imlegr https://wiki.archlinux.org/title/Arch_Linux_Archive#How_to_restore_all_packages_to_a_specific_date maybe?
If downgrading nvidia drivers (you may need to downgrade kernel or use -dkms package) and xwayland did not help.
Comment by Konstantin (imlegr) - Friday, 24 March 2023, 23:45 GMT
@mcmodder I'm going to try to do that now. Thank you. The thing is that I went back to the old drivers before, but the problem persists
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 24 March 2023, 23:53 GMT
@imlegr: You need to isolate the problem and then report a bug on the upstream project that is at fault here. You said that going back to the older driver didn't fix your issue. That being case, this is not an nvidia driver issue put perhaps another piece of software. I suggest you open a new bug report on our tracker and upstream once you figure out what the culprit is.
Comment by Konstantin (imlegr) - Saturday, 25 March 2023, 00:07 GMT
Unfortunately, I have no idea how to find out what the problem is. I'm a 3D artist, not a programmer. I could pay if someone would contact me, help me solve this problem.
Comment by Konstantin (imlegr) - Saturday, 25 March 2023, 00:13 GMT
Comment by Konstantin (imlegr) - Saturday, 25 March 2023, 00:20 GMT
@mcmodder I went back to the old packages. From the 20th. The problem is still there for some reason. Maybe I'm doing something wrong? If you have a way to contact me, please help, I will definitely thank you
Comment by Konstantin (imlegr) - Saturday, 25 March 2023, 00:21 GMT
Anyway, I have no idea what's going on. If I use Timeshift to restore the backup, then everything works. But if I restore the drivers and all other packages, unfortunately the problem remains.

I did this and the problem remains:
[core] (I changed for all repositories)
SigLevel = PackageRequired
Server=https://archive.archlinux.org/repos/2023/03/20/$repo/os/$arch
Comment by Nikita (mcmodder) - Saturday, 25 March 2023, 01:22 GMT
@Svenstaro: in my case problems were caused by xorg-xwayland update, newest version (23.1.0) is unusable for me (mostly in fullscreen X apps) with both current (530.41.03) and previous (525.89.02) nvidia drivers. My env: GNOME, Wayland, NVIDIA GTX 1080 Ti, nvidia-dkms drivers, vanilla (linux) kernel. All packages are up-do-date except xorg-xwayland: I rolled it back to 22.1.8 to make system usable.
I was unable to find upstream bug report, and I don't know how to clearly describe my problem, so I didn't create upsteam bug report by myself.

@imlegr: we can try to talk in other places, like Telegram (t.me-slash-mcmodder). I'll be available for the next ~2 hours
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 25 March 2023, 02:11 GMT
Please report a bug upstream. Stuff like that makes the world go 'round. :)
Comment by Konstantin (imlegr) - Saturday, 25 March 2023, 17:34 GMT
They helped me to roll back the drivers to the old version and do it right. Everything works for me, it turns out that the problem was with the drivers (apparently, when I rolled them back, I did something wrong before).

But with the new drivers, unfortunately, the problem still persists. If I understand correctly - I do not need to create a new report about the error?
Comment by Konstantin (imlegr) - Saturday, 25 March 2023, 18:01 GMT
Friends, please write to Nvidia about this problem, that with the new drivers does not work graphics acceleration and turns off the monitor 144Hz connected through the display port. And 75Hz monitor via HDMI works with strong brakes.

The only thing that helped was to roll back to the previous drivers.

The thing is that I lost a lot of time and now I have a lot of work to do. So I'm asking some of you to reach out to Nvidia. If you need anything, please write.

I don't understand at all, why on Nvidia's website the latest version is 525 and in the repository 530?
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 25 March 2023, 20:18 GMT
It's the latest non-beta driver: https://www.nvidia.com/en-us/drivers/unix/
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 25 March 2023, 20:19 GMT
Can you start a thread on the Nvidia forums about this issue and link it here?
Comment by Konstantin (imlegr) - Sunday, 26 March 2023, 01:23 GMT
I have no idea where or how. There you have to put the new drivers back in, then send the logs, then put the old ones back in. I physically don't have time for that. Others have this problem as well. Have someone else write to Nvidia. I've sent so many bug reports concerning linux this year that I'm already dreaming about them (Wine, KDE, Ocenaudio, Arch Linux, Moonlight, etc.). Again, I was unable to work for a few days because of a driver bug, and now I have a lot of work to do. Thank you for your understanding.
Comment by Konstantin (imlegr) - Monday, 27 March 2023, 20:13 GMT
I found the problem. For the 4080 graphics card, the 530 driver is still in beta and is not stable. The latest stable driver for the 4080 is 525.
Comment by Nikita (mcmodder) - Monday, 27 March 2023, 20:18 GMT
I found some info about this issue.
530.41.03 driver DOES NOT SUPPORT RTX4070/RTX4080!
530.41.03 Supported products:
GeForce RTX 40 Series:
NVIDIA GeForce RTX 4090

But 530.30.02 beta and 525.89.02 release do.


I think it is nessesary to notify users to use nvidia-lts or do not upgrade their driver to 530.41.03 in case they're using RTX 4070 Ti or RTX 4080
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 27 March 2023, 23:05 GMT
Where did you get that info from? The 4080 and 4090 are roughly the same age aren't they? I think this might just be a typo by NVIDIA. As far as I've seen, the GPUs are basically treated the same and it wouldn't make sense for them to regress on this now.
Comment by Konstantin (imlegr) - Tuesday, 28 March 2023, 00:22 GMT
Go to the Nvidia website and see for yourself. For the 4090 there is version 530, for the 4080 525 the latest stable version.
Comment by Lou (Lou) - Tuesday, 28 March 2023, 21:27 GMT
I have the same issue with 530.41.03 on a 3080, which is supposed to be supported. I would say this is a typo from Nvidia
Comment by Ochi (ochi) - Tuesday, 28 March 2023, 21:36 GMT
I also have a refresh rate issue. My Samsung Ultra-Wide used to run at 120 Hz. With the 530 driver, it only does 60 Hz (on a 1080).

Sure, this might be an issue of the NVIDIA driver itself. However, the 530 driver is their (unstable) "New Feature Branch" and the 525 driver is their (stable) "Production Branch". In general, would it be possible to provide Arch users with two nvidia packages which track NVIDIA's production and new feature branches, respectively? This might at least provide users with an alternative if a new major release shows to be problematic.
Comment by Nikita (mcmodder) - Tuesday, 28 March 2023, 21:41 GMT
... like https://archlinux.org/packages/extra/x86_64/nvidia-lts/ ?
Comment by Lou (Lou) - Tuesday, 28 March 2023, 21:42 GMT
This is the nvidia driver for LTS kernel, not LTS Nvidia driver. This is still 530.41.03
Comment by Ochi (ochi) - Tuesday, 28 March 2023, 21:53 GMT
Exactly, nvidia-lts is the same NVIDIA driver version (530), just built for the linux-lts (6.1) kernel. I just tried linux-lts and nvidia-lts to make sure it's not some NVIDIA 530 + Linux 6.2 issue, but I'm still seeing the same problem with linux-lts and nvidia-lts.
Comment by Konstantin (imlegr) - Friday, 31 March 2023, 00:27 GMT
@Svenstaro, Will nvidia-dkms 525.105.17 be released for the 4080, which is released 2023.3.30? Because right now nvidia-dkms has version 530.41.03 which does not work on the 4080.
Comment by jk (su1) - Friday, 31 March 2023, 06:23 GMT
As a workaround downgrade packages with A.L.A - https://aur.archlinux.org/packages/downgrade
Use - 525.89.02-1 or 525.89.02-2 (where -1 is not available)
Packages I have installed/downgraded, I'm on X.org now (because Diablo 4 killed apps rendering in my system, so I moved to X.org for now)
(I have 4080, two 2k monitors 60hz and 170hz, all good after the downgrade, or at least I did not notice any issues so far)

lib32-nvidia-utils 525.89.02-1
libxnvctrl 525.89.02-1
nvidia-dkms 525.89.02-2
nvidia-settings 530.41.03-1
nvidia-utils 525.89.02-2
opencl-nvidia 525.89.02-2

I'm not an expert, but nvidia-settings might stay the 530 version. Cheers.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 31 March 2023, 07:57 GMT
I think splitting the drivers to track nvidia's production and new-feature drivers is a good idea. We just need someone to do it. I'm only ever running the respectively newest drivers so we'll have to find someone interested in maintaining and running the other drivers. One thing I noticed that might make this annoying is: nvidia sometimes releases one or the other driver as the newest one. So the production driver might actually be more recent than the new-feature branch one. This will be annoying for users as they might have to constantly switch to get the newest drivers.

I'm not sure how to best solve this conundrum. It feels to me like we shouldn't inconvenience the larger user base to solve a problem only a small number of users have.
Comment by Konstantin (imlegr) - Friday, 31 March 2023, 11:18 GMT
I am not a programmer, but we need someone to make nvidia-dkms for 4080 because it is an expensive video card and it should also have stable drivers in the Arch repository
Comment by Konstantin (imlegr) - Saturday, 01 April 2023, 03:30 GMT
You can do nvidia-dkms and nvidia-dkms-nf (new futures)
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 01 April 2023, 05:42 GMT
We could do that and then make the respectively newest package provide a virtual package that would then make sure that users who wish to always be on the most recent version will no be hassled. I think we can pull this off if I get a co-maintainter on Nvidia. With my current workload I don't think I could maintain the structure well by myself. Keep in mind we're all volunteers working in our spare time.
Comment by Konstantin (imlegr) - Saturday, 01 April 2023, 07:31 GMT
Thank you. I thank you for your work. I really hope Arch Liux will develop and sometimes worry that its development may stop or be abandoned. Could this happen? And how many people are working on Arch Liux? Do any of them even get paid?
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 01 April 2023, 08:06 GMT
There are around 50 people more or less actively working in Arch and not a single one's getting paid for it. :) For the last 20 something years, this has worked out fine.
Comment by Konstantin (imlegr) - Saturday, 01 April 2023, 08:10 GMT
This is amazing! I admire you! I thought some of the big companies like Steam or Google were funding the development :)

My respect for you is even greater. Thank you for your work! I Love Arch Linux :)
Comment by Ochi (ochi) - Saturday, 01 April 2023, 23:33 GMT
Maybe the packages could be named "nvidia-still" and "nvidia-fresh" ;) – SCNR; if you don't get the reference, never mind. ^^

On a more serious note: Thank you for considering making separate branches available (and for your work in general). Regarding the question of making the latest version available to users: Maybe this shouldn't even be an issue of the package maintainer since "upstream changes are not the responsibility of Arch devs" (quote from the Arch FAQ). Whatever versions the upstream provider (i.e. NVIDIA) deems to be "production-ready" or "bleeding edge" should be reflected by the respective packages. I don't know if it's really sensible to provide a (virtual) package that switches between branches just to provide the highest version number available at any given point in time.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 10 April 2023, 18:11 GMT
The only problem I really have with this is that sometimes, newer kernels or Xorg versions are only compatible with the very newest version and sometimes there are months until that's fixed. Since we can't block kernel updates on nvidia for such a long time, we'd be left with broken packages. I'm not sure how to feel about that. It doesn't happen very often anymore but it used to be fairly often.
Comment by Shisui (shisui) - Sunday, 16 April 2023, 08:08 GMT
nvidia 525 have some important fix:

```
Resolved an issue when invoking nvidia_p2p_put_pages by providing a new APIs nvidia_p2p_get/put_pages_persistent for persistent memory.
```
https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-525-105-17/index.html

while nvidia530 did not reviced it yet.

nvidia530 is apparently not taken seriously! at least for now.

Hope to support nvidia525 branch.
Comment by Shisui (shisui) - Monday, 17 April 2023, 04:17 GMT
A 525.105.17-1 archlinuix package is here:

https://github.com/homjay/archlinux-nvidia-production-branch/releases/tag/x86_64

I have confirmed that it works on RTX 4090 GPU.
Comment by Dylan (dylif) - Tuesday, 18 April 2023, 13:44 GMT
Shisui, would it be possible for you to put this package on the AUR? I was going to begin packaging the production branch on the AUR, but found this bug report. If you don't have the time to maintain, I'd be happy to, but I need to receive my new NVIDIA hardware which should be happening soon.
Comment by Shisui (shisui) - Tuesday, 18 April 2023, 14:30 GMT
Sure, either you or I can help with this.
I can submit to AUR the weekend.
I need to read the documentation before submitting, since I never submitting package before.
If you have the time, you can submit to AUR anytime suites you.
Comment by Gil Vicente (gilvbp) - Tuesday, 18 April 2023, 20:23 GMT
added the remaining (32 bit version) packages here https://github.com/gilvbp/archlinux-nvidia-production-branch/releases/tag/x86_32
Comment by Jérémy Lecocq (Vrakfall) - Thursday, 27 April 2023, 04:38 GMT
I just did submit the 525 branch to AUR, enjoy: https://aur.archlinux.org/packages?K=525xx

I am going to use that specific branch on one of my machines for the time being as it has some issues with 530.
Comment by Gil Vicente (gilvbp) - Wednesday, 03 May 2023, 11:29 GMT
Hi @Vrakfall, Could you please update the packages to the Latest Production Branch Version: 525.116.03
Thanks
Comment by Jérémy Lecocq (Vrakfall) - Thursday, 04 May 2023, 16:04 GMT
@gilvbp
Hi! Done deal, check my comments on AUR for more details. ;)
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 14 June 2023, 23:12 GMT
Does 535 work for you guys?
Comment by Gil Vicente (gilvbp) - Thursday, 15 June 2023, 09:22 GMT
Yes, it's working with 144hz!

Loading...