Bug 480998 - In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 120.
Summary: In KDE Neon testing external monitor with a capability of 120 hz displays onl...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.93.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-07 10:46 UTC by Nikolay
Modified: 2024-03-09 21:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay 2024-02-07 10:46:48 UTC
SUMMARY
***
In KDE Neon testing external monitor with a capability of 120 ghz displays only 60 when trying to set 144. Right behaviour in windows 11 and fedora 39 gnome.
***


STEPS TO REPRODUCE
1. Connect an external monitor to laptop with 120 hz via USB4 type C to the display port
2. Switch refresh rate to 120 hz.

OBSERVED RESULT
only 60 hz

EXPECTED RESULT
120 hz

SOFTWARE/OS VERSIONS
Windows 11: work
macOS: work
Linux: Fedora 39 (gnome) work 

KDE Neon Version: neon-testing-20240206-0538 don't work
Comment 1 Zamundaaa 2024-02-15 14:02:13 UTC
Could you describe in more detail what the problem is? Do the display settings only allow you to go up to 60Hz, or can you set it to 120Hz but the monitor shows that it's only doing 60Hz, or does it actually go to 120Hz but feels slower than it should?

Also, what exact laptop are you using?
Comment 2 Nikolay 2024-02-19 06:01:23 UTC
(In reply to Zamundaaa from comment #1)
> Could you describe in more detail what the problem is? Do the display
> settings only allow you to go up to 60Hz, or can you set it to 120Hz but the
> monitor shows that it's only doing 60Hz, or does it actually go to 120Hz but
> feels slower than it should?
> 
> Also, what exact laptop are you using?

In default mode external monitor use 2560x1440@60 it works, but when I try switch to 2560x1440@120 monitor frozen about 3 seconds, firefox crashed and monitor anyway in 60 gz mode 
Laptop is asus rog flow x13 2023 with amd ryzem 7940hs and 780m graphics. 
drm info - https://drive.google.com/file/d/1q4pVVL36NOhZXQhXJQenMkFmVBX_ArJi/view?usp=sharing
drm info in Fedora 39 gnome when it works properly - https://drive.google.com/file/d/1ESA4P03WMiMz_41LrZnWsLp-64waLYuL/view?usp=sharing
And I see problems with graphics in 165 gz internal monitor in 60 gz on external it's ok
video - https://drive.google.com/file/d/12p-dErQNivp0LI8KwWN4ZyQjBu4hWjr8/view?usp=sharing
Comment 3 Zamundaaa 2024-02-19 13:35:47 UTC
Okay. Could you try again with KWIN_DRM_PREFER_COLOR_DEPTH=24 in /etc/environment ?
Comment 4 Nikolay 2024-02-20 06:45:55 UTC
(In reply to Zamundaaa from comment #3)
> Okay. Could you try again with KWIN_DRM_PREFER_COLOR_DEPTH=24 in
> /etc/environment ?

Thanks! It works, my external monitor is now working correctly at 120 Hz, but the internal monitor still displays graphical errors when I switch virtual desktops or the dock at the bottom changes its position
Comment 5 Nikolay 2024-02-20 06:52:35 UTC
(In reply to Zamundaaa from comment #3)
> Okay. Could you try again with KWIN_DRM_PREFER_COLOR_DEPTH=24 in
> /etc/environment ?

Internal monitor works without bugs when I switch from 165 gz to 96 or less
Comment 6 Bug Janitor Service 2024-03-06 03:46:50 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Zamundaaa 2024-03-09 21:51:00 UTC
Okay, both of these issues are driver bugs. You can report them at https://gitlab.freedesktop.org/drm/amd/-/issues