improper resolution passed to monitor

NVIDIA / open-gpu-kernel-modules

NVIDIA Linux open GPU kernel module source

Other

15.14k stars 1.27k forks source link

improper resolution passed to monitor #281

Open jumpers775 opened 2 years ago

jumpers775 commented 2 years ago

NVIDIA Open GPU Kernel Modules Version

515.48.07

Does this happen with the proprietary driver (of the same version) as well?

Yes

Operating System and Version

Arch Linux

Kernel Release

5.18.1-arch1-1

Hardware: GPU

NVIDIA GeForce RTX 2060 (UUID: GPU-27024b8f-ce0b-2546-7f78-676a22fa9c42)

Describe the bug

When I set the resolution to 75 hz my monitor says input not supported. this is because my monitor is only capable of displaying exactly what is shown in its edid. I am using an acer sb220q bi. this issue first occured in the proprietary drivers with the 510 line. not entirely sure why this is, but im more than happy to provide an additional information.

To Reproduce

connect an acer sb220q bi (or likely other acer monitors that lock the resolutions to whats in the edid), and set the resolution to 75 hz.

Bug Incidence

Always

nvidia-bug-report.log.gz

More Info

No response

aritger commented 2 years ago

Thanks for the report. Could you please capture the edid.bin file for your monitor and attach it here? Using nvidia-settings, go to the display page, and click on "Acquire EDID..."

jumpers775 commented 2 years ago

well, i usually run wayland, but it seems im getting fish: Job 1, 'nvidia-settings -V' terminated by signal SIGSEGV (Address boundary error) when running nvidia-settings under x for that option. anyway, i have also attached the edid, which it wouldnt let me upload without compressing.

ThisNekoGuy commented 2 years ago

@jumpers775 I don't think nvidia-settings supports wayland yet; other important functionality such as changing the fan speed and overclocking isn't available under wayland yet either, so that isn't a surprise

On a side note, though not directly related... Being able to have literally any settings under Wayland would be great; assuming we can even get Wayland to work right first... that hasn't been great, personally, for things like Window stability, proper HiDPI resolution support, and correct framerates but I haven't tested these for some months

ThisNekoGuy commented 2 years ago

@aritger On a similar note, because it sounds like jumpers775 meant "framerate" rather than "resolution(?)," I also experience an issue with running Wayland where the framerate Hz is capped to half of my display's maximum refresh rate where this isn't an issue on X11/Xorg

On X11 I can run 3840x2160 @ 60 Hz (the refresh rate of my display) but on Wayland 3840x2160 is capped at 30Hz (half of that of my display). It was mentioned to the KDE devs over here, but it was said to be a driver bug.