| Summary: | x11-drivers/nvidia-drivers-530.41.03: Unable to run highest frame-rate on Wayland | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ivo Šmerek <ivo97> |
| Component: | Current packages | Assignee: | Ionen Wolkens <ionen> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | ionen, soap |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
Kernel configuration |
||
Created attachment 860147 [details]
Kernel configuration
I doubt kernel configs are related, but I don't really have a way to tell what changed (much is still closed source and there's no proper history for modules), and don't have a setup to test these resolutions either. Have to take things like this with NVIDIA unless you believe the problem is Gentoo-specific, or is major enough to require masking. Note that 530 is a new feature branch (NFB), it will never be marked stable unlike production 525.x -- regressions are more likely, especially with its wayland support which barely works as-is. About kernel, when in doubt about your configs you can always try gentoo-kernel-bin for a quick generic kernel. But I suspect it's just a driver regression and is unrelated. Alright, I understand. Thank you for the information. |
Created attachment 860146 [details] emerge --info I'm currently testing x11-drivers/nvidia-drivers-530.41.03 from Portage tree and experiencing an issue that doesn't occur in the stable 525.105.17 version. I have a monitor that runs 3440x1440 resolution with 165Hz. Everything works fine with 525.105.17. But with 530.41.03 version, Wayland cannot display this resolution with this specific frame-rate anymore. I use Gnome Mutter and if I set the frame-rate down to 100Hz, it starts working. This issue doesn't occur on Xorg where 165Hz works fine. I have: kernel: 6.1.19-gentoo-x86_64 GPU: GeForce RTX 3080 12GB DE: gnome-base/gnome-shell-43.3 with dev-libs/wayland-1.21.0-r1 Are there any logs I can look into to get some more information about this problem? Did something change in the recommended kernel configuration for the newest drivers?