Bug 493673

Summary:	Option for 360Hz not showing up
Product:	[Plasma] kwin	Reporter:	P Saini <prateek.saini.1999>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	kde, nate, xaver.hugl
Priority:	NOR
Version First Reported In:	6.1.5
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	output of `kscreen-doctor -o`

Description P Saini 2024-09-26 06:44:19 UTC

SUMMARY
Option for 360Hz not showing up in System Settings

STEPS TO REPRODUCE
1. Open System Settings -> Display & Monitor -> Refresh rate

OBSERVED RESULT
Max refresh rate is 240Hz

EXPECTED RESULT
Max refresh rate should be 360Hz

SOFTWARE/OS VERSIONS
Windows: 10 Home
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.8.0-45-generic (64-bit)
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
I have a 1440p 360Hz monitor. I have a dual boot setup. 360Hz works just fine in Windows with the same cable / system.
`kscreen-doctor -o` output does not list 360Hz as valid mode.

Additionally it also shows the display as VRR incapable and HDR incapable, both of which work fine in Windows as well. (Should I open separate issues for these?)

Comment 1 P Saini 2024-09-26 06:46:39 UTC

Created attachment 174092 [details]
output of `kscreen-doctor -o`

Comment 2 Zamundaaa 2024-09-26 18:05:47 UTC

KWin doesn't filter modes, the list you see is the list the kernel says is available.

What GPU are you using?

Comment 3 P Saini 2024-09-28 04:29:43 UTC

(In reply to Zamundaaa from comment #2)
> What GPU are you using?

1660 Ti (Mobile)
Mobile because it's a laptop
It's run through the DP port which is directly connected to the GPU so no issues with iGPU

Comment 4 David Edmundson 2024-10-03 10:51:18 UTC

I'm afraid your issue is lower in the stack than kwin. Please report to your graphic driver vendor.

Comment 5 P Saini 2024-10-07 16:10:08 UTC

Actually this turned out to be a trivial issue. I thought Neon comes with proprietary Nvidia drivers installed but it doesn't.
Being new to this I just put `nvidia` in the terminal and saw `nvidia-detector` which said I am using nvidia-driver-550.

I followed the guide here to actually install the Nvidia driver: https://discuss.kde.org/t/install-nvidia-drivers-on-kde-neon/1648
Installing them solved the issue

---
I suppose it was falling back to the `amdgpu` driver for the iGPU so the bug could be there