You are not logged in.
- Topics: Active | Unanswered
#1 2024-05-15 20:08:32
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
[SOLVED] Problems with screen resolutions about hertz
Hello everyone, I have a problem with the resolution configuration of my screen, this happens to me in any desktop environment other than gnome and this also happens to me even if I am using X11 or Wayland. The specific problem is that my screen supports up to 144hz refresh rate tested at the hardware level but when I try to make that change in , in this case, using kde plasma. Something similar happens in Wayland, when I try to make the change the entire screen breaks. I have tried to diagnose on my own what the problem may be, however I have not been able to find a solution.
As I emphasize, this does not happen with gnome, it only happens with any other desktop environment. I'm going to upload a couple of videos that show the error so that it can be seen correctly.
Wayland error:
X11 Error:
My hardware:
❯ neofetch
-` mario@asus-arch
.o+` ---------------
`ooo/ OS: Arch Linux x86_64
`+oooo: Host: ASUS TUF Gaming A15 FA506QM_FA506QM 1.0
`+oooooo: Kernel: 6.6.30-2-lts
-+oooooo+: Uptime: 45 mins
`/:-:++oooo+: Packages: 1899 (pacman)
`/++++/+++++++: Shell: zsh 5.9
`/++++++++++++++: Resolution: 1920x1080
`/+++ooooooooooooo/` DE: Plasma 6.0.4
./ooosssso++osssssso+` WM: KWin
.oossssso-````/ossssss+` Theme: Breeze-Dark [GTK2], Breeze [GTK3]
-osssssso. :ssssssso. Icons: breeze-dark [GTK2/3]
:osssssss/ osssso+++. Terminal: konsole
/ossssssss/ +ssssooo/- CPU: AMD Ryzen 7 5800H with Radeon Graphics (16) @ 4.463GHz
`/ossssso+/:- -:/+osssso+- GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q
`+sso+:-` `.-/+oso: GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series
`++:. `-/+/ Memory: 6983MiB / 39511MiB --------------------------------------
kscreen log:
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandR::setConfig
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Requested screen size is QSize(1920, 1080)
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Needed CRTCs: 1
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Actions to perform:
Priorities: false
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Change Screen Size: false
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Disable outputs: false
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Change outputs: true
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: QList(82)
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Enable outputs: false
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: RRSetCrtcConfig (change output)
Output: 82 ( "eDP" )
CRTC: 78
Pos: QPoint(0,0)
Mode: KScreen::Mode(Id: "85" , Size: QSize(1920, 1080) @ 144 ) Preferred: "85"
Rotation: KScreen::Output::None
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandRCrtc 78 m_timestamp update 84201 => 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Result: 0 timestamp: 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandROutput 82 update
m_connected: 0
m_crtc XRandRCrtc(0x56497a5b69e0)
CRTC: 78
MODE: 85
Connection: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: RRSetOutputPrimary
New priority: 1
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: RRSetOutputPrimary
New priority: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandR::setConfig done!
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_CrtcChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 84201
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 78
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 85
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Geometry: 0 0 1920 1080
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRScreenChangeNotify
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 84201
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Config_timestamp: 9983
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Window: 46137350
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Root: 1335
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Size ID: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Size: 1920 1080
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: SizeMM: 508 285
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_CrtcChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 84201
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 78
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 85
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Geometry: 0 0 1920 1080
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_CrtcChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 78
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 85
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Geometry: 0 0 1920 1080
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_CrtcChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 79
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Geometry: 0 0 0 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_CrtcChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 80
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Geometry: 0 0 0 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_CrtcChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 81
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Geometry: 0 0 0 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_OutputChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Output: 82
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 78
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 85
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Connection: "Connected"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Subpixel Order: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: RRNotify_OutputChange
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Timestamp: 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Output: 83
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: CRTC: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Mode: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Rotation: "Rotate_0"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Connection: "Disconnected"
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xcb.helper: Subpixel Order: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandRCrtc 78 m_configTimestamp update 84201 => 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandRCrtc 79 m_configTimestamp update 84201 => 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandRCrtc 80 m_configTimestamp update 84201 => 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandRCrtc 81 m_configTimestamp update 84201 => 524502
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandROutput 82 update
m_connected: 0
m_crtc XRandRCrtc(0x56497a5b69e0)
CRTC: 78
MODE: 85
Connection: 0
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Output 82 : connected = true , enabled = true
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: XRandROutput 83 update
m_connected: 1
m_crtc QObject(0x0)
CRTC: 0
MODE: 0
Connection: 1
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Output 83 : connected = false , enabled = false
may 15 16:08:53 asus-arch kscreen_backend_launcher[1843]: kscreen.xrandr: Emitting configChanged()Last edited by Mario156090 (2024-05-17 12:43:11)
Offline
#2 2024-05-15 21:26:36
- seth
- Member
- Registered: 2012-09-03
- Posts: 59,884
Re: [SOLVED] Problems with screen resolutions about hertz
Recap of the videos: glxgears on compositing plasma/X11 reflects kscreen modeline changes (confirmed by xrandr) between 60Hz and 120Hz but changes to 144Hz (confirmed by xrandr) are inert and glxgears renders at the preovious rate.
Trying to set the 144Hz mode on plasma/wayland has causes massive visual corruption.
For plasma/X11 try to suspend the compositor (SHIFT+Alt+F12) - is the output https://wiki.archlinux.org/title/Variable_refresh_rate capable?
Since it's a hybrid system, do all environments run on the same GPU?
("glxinfo -B" should suffice)
Did you test gnome on X11 (as well) or (only) gnome on wayland?
Edit: Please use [code][/code] tags. Edit your post in this regard.
Last edited by seth (2024-05-15 21:27:19)
Online
#3 2024-05-15 22:11:36
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
Re: [SOLVED] Problems with screen resolutions about hertz
Recap of the videos: glxgears on compositing plasma/X11 reflects kscreen modeline changes (confirmed by xrandr) between 60Hz and 120Hz but changes to 144Hz (confirmed by xrandr) are inert and glxgears renders at the preovious rate.
Trying to set the 144Hz mode on plasma/wayland has causes massive visual corruption.For plasma/X11 try to suspend the compositor (SHIFT+Alt+F12) - is the output https://wiki.archlinux.org/title/Variable_refresh_rate capable?
Since it's a hybrid system, do all environments run on the same GPU?
("glxinfo -B" should suffice)
Did you test gnome on X11 (as well) or (only) gnome on wayland?Edit: Please use [code][/code] tags. Edit your post in this regard.
Hello, suspending compositor does not fix the issue.
xrandr output:
❯ xrandr --props
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
_KDE_SCREEN_INDEX: 1
EDID:
00ffffffffffff0038704d0000000000
331d0104a5221378036850985c588e28
1b505400000001010101010101010101
010101010101918a8004713832403020
350058c21000001abd39800471383240
3020350058c21000001a000000fd0030
90a3a323010a202020202020000000fe
004c4d3135364c462d324630330a0035
GAMMA_LUT_SIZE: 4096
range: (0, -1)
DEGAMMA_LUT_SIZE: 4096
range: (0, -1)
GAMMA_LUT: 0
range: (0, 65535)
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0
0 1
DEGAMMA_LUT: 0
range: (0, 65535)
TearFree: on
supported: off, on, auto
HDCP Content Type: HDCP Type0
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired
supported: Undesired, Desired, Enabled
vrr_capable: 1
range: (0, 1)
Colorspace: Default
supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
abm level: 0
range: (0, 4)
max bpc: 16
range: (8, 16)
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad
CONNECTOR_ID: 87
supported: 87
non-desktop: 0
range: (0, 1)
1920x1080 144.00*+ 120.00 96.00 72.00 60.00 50.01 48.00 60.00
1680x1050 144.00
1280x1024 144.00
1440x900 144.00
1280x800 144.00
1280x720 144.00
1024x768 144.00
800x600 144.00
640x480 144.00
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
GAMMA_LUT_SIZE: 4096
range: (0, -1)
DEGAMMA_LUT_SIZE: 4096
range: (0, -1)
GAMMA_LUT: 0
range: (0, 65535)
CTM: 0
DEGAMMA_LUT: 0
range: (0, 65535)
TearFree: on
supported: off, on, auto
HDCP Content Type: HDCP Type0
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired
supported: Undesired, Desired, Enabled
vrr_capable: 0
range: (0, 1)
Colorspace: Default
supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
max bpc: 16
range: (8, 16)
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad
CONNECTOR_ID: 95
supported: 95
non-desktop: 0
range: (0, 1)I tested in gnome wayland and x11 and works perfectly.
Offline
#4 2024-05-15 22:20:08
- seth
- Member
- Registered: 2012-09-03
- Posts: 59,884
Re: [SOLVED] Problems with screen resolutions about hertz
I tested in gnome wayland and x11 and works perfectly.
Possibly not.
https://wiki.archlinux.org/title/Variab … rate#GNOME
vrr_capable: 1Check your xorg log whether "VariableRefresh" is mentioned, https://wiki.archlinux.org/title/Xorg#General
Disabling VRR in KDE will likely get you similar behavior as in gnome - whether that's desirable is a different matter.
Well, it probably would be in the wayland context where this is apparently buggy?
Online
#5 2024-05-15 22:32:15
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
Re: [SOLVED] Problems with screen resolutions about hertz
I tested in gnome wayland and x11 and works perfectly.
Possibly not.
https://wiki.archlinux.org/title/Variab … rate#GNOMEvrr_capable: 1Check your xorg log whether "VariableRefresh" is mentioned, https://wiki.archlinux.org/title/Xorg#General
Disabling VRR in KDE will likely get you similar behavior as in gnome - whether that's desirable is a different matter.
Well, it probably would be in the wayland context where this is apparently buggy?
Ok, I understand. I checked my X11 configuration and watch this:
❯ cat /etc/X11/xorg.conf.d/20-amdgpu.conf
Section "OutputClass"
Identifier "AMD"
MatchDriver "amdgpu"
Driver "amdgpu"
Option "TearFree" "true"
Option "VariableRefresh" "false"
Option "EnablePageFlip" "on"
EndSectionand check my X11 log and say Vrr is turn off.
❯ cat /var/log/Xorg.0.log | grep Variable
[ 9.595] (**) AMDGPU(0): Option "VariableRefresh" "false"
[ 9.771] (**) AMDGPU(0): VariableRefresh: disabledBut after a reboot I check newly xrandr but still says vrr_capable = 1
❯ xrandr --props
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
_KDE_SCREEN_INDEX: 1
EDID:
00ffffffffffff0038704d0000000000
331d0104a5221378036850985c588e28
1b505400000001010101010101010101
010101010101918a8004713832403020
350058c21000001abd39800471383240
3020350058c21000001a000000fd0030
90a3a323010a202020202020000000fe
004c4d3135364c462d324630330a0035
GAMMA_LUT_SIZE: 4096
range: (0, -1)
DEGAMMA_LUT_SIZE: 4096
range: (0, -1)
GAMMA_LUT: 0
range: (0, 65535)
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0
0 1
DEGAMMA_LUT: 0
range: (0, 65535)
TearFree: on
supported: off, on, auto
HDCP Content Type: HDCP Type0
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired
supported: Undesired, Desired, Enabled
vrr_capable: 1
range: (0, 1)
Colorspace: Default
supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
abm level: 0
range: (0, 4)
max bpc: 16
range: (8, 16)
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad
CONNECTOR_ID: 87
supported: 87
non-desktop: 0
range: (0, 1)
1920x1080 144.00*+ 120.00 96.00 72.00 60.00 50.01 48.00 60.00
1680x1050 144.00
1280x1024 144.00
1440x900 144.00
1280x800 144.00
1280x720 144.00
1024x768 144.00
800x600 144.00
640x480 144.00
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
GAMMA_LUT_SIZE: 4096
range: (0, -1)
DEGAMMA_LUT_SIZE: 4096
range: (0, -1)
GAMMA_LUT: 0
range: (0, 65535)
CTM: 0
DEGAMMA_LUT: 0
range: (0, 65535)
TearFree: on
supported: off, on, auto
HDCP Content Type: HDCP Type0
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired
supported: Undesired, Desired, Enabled
vrr_capable: 0
range: (0, 1)
Colorspace: Default
supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
max bpc: 16
range: (8, 16)
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
link-status: Good
supported: Good, Bad
CONNECTOR_ID: 95
supported: 95
non-desktop: 0
range: (0, 1)So, your main teory is about vrr status. I am going to look how disable vrr.
OK, disable vrr is impossible now. Hahaha. I tried with kscreen-doctor and appears as incapable. xD
Output: 82 eDP
enabled
connected
priority 1
Panel
Modes: 85:1920x1080@144*! 86:1920x1080@120 87:1920x1080@96 88:1920x1080@72 89:1920x1080@60 90:1920x1080@50 91:1920x1080@48 92:1920x1080@60 93:1680x1050@144 94:1280x1024@144 95:1440x900@144 96:1280x800@144 97:1280x720@144 98:1024x768@144 99:800x600@144 100:640x480@144
Geometry: 0,0 1920x1080
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: incapable
Output: 83 HDMI-A-0
disabled
disconnected
priority 0
HDMI
Modes:
Geometry: 0,0 0x0
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: incapableLast edited by Mario156090 (2024-05-15 23:07:49)
Offline
#6 2024-05-16 06:44:02
- seth
- Member
- Registered: 2012-09-03
- Posts: 59,884
Re: [SOLVED] Problems with screen resolutions about hertz
But after a reboot I check newly xrandr but still says vrr_capable = 1
That will probably reflect only the output, not the driver.
Did you test the glxgears (on plasma/X11) behavior after disabling it in the driver?
Online
#7 2024-05-16 12:21:19
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
Re: [SOLVED] Problems with screen resolutions about hertz
But after a reboot I check newly xrandr but still says vrr_capable = 1
That will probably reflect only the output, not the driver.
Did you test the glxgears (on plasma/X11) behavior after disabling it in the driver?
Yes, I did. The behavior is the same. Same problem.
Offline
#8 2024-05-16 15:09:59
- seth
- Member
- Registered: 2012-09-03
- Posts: 59,884
Re: [SOLVED] Problems with screen resolutions about hertz
Same if you run
adaptive_sync=false glxgearsTo test whether this generally works,
vblank_mode=0 glxgearsshould get you completely unsynced, maximum FPS glxgears
Online
#9 2024-05-16 23:43:05
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
Re: [SOLVED] Problems with screen resolutions about hertz
Same if you run
adaptive_sync=false glxgearsTo test whether this generally works,
vblank_mode=0 glxgearsshould get you completely unsynced, maximum FPS glxgears
Hello, the code adaptive_sync=false does not show any difference.
With vblank_mode=0 the FPS are incredible hight but does not fix my problem.
❯ vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
95464 frames in 5.0 seconds = 19092.697 FPS
99769 frames in 5.0 seconds = 19953.523 FPS
100321 frames in 5.0 seconds = 20063.977 FPS
97406 frames in 5.0 seconds = 19481.168 FPS
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0"
after 427160 requests (390193 known processed) with 0 events remaining.Offline
#10 2024-05-17 01:05:53
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
Re: [SOLVED] Problems with screen resolutions about hertz
Offline
#11 2024-05-17 02:38:59
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
Re: [SOLVED] Problems with screen resolutions about hertz
Well, I upgraded my kernel to 6.9 from core-testing and fix my issue with X11, later I will to test with wayland.
Edit:
Wayland fixed. With 6.9 kernel every problem has been fixed.
Last edited by Mario156090 (2024-05-17 04:30:07)
Offline
#12 2024-05-17 06:34:11
- seth
- Member
- Registered: 2012-09-03
- Posts: 59,884
Re: [SOLVED] Problems with screen resolutions about hertz
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
FPS are incredible hight but does not fix my problem
For clarification, was there a (visual?) problem beyond glxinfo not stepping up to 144Hz? (This would of course not happen since glxgears ran completely unsynced)
Online
#13 2024-05-17 13:43:22
- Mario156090
- Member
- Registered: 2018-12-04
- Posts: 50
Re: [SOLVED] Problems with screen resolutions about hertz
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.FPS are incredible hight but does not fix my problem
For clarification, was there a (visual?) problem beyond glxinfo not stepping up to 144Hz? (This would of course not happen since glxgears ran completely unsynced)
In that case, glxgears exceeded 144hz, it went up to 95625625 fps. xd
Ok, I'm marking the thread as resolved.
Thanks for the valuable help, if you didn't tell me what it could be the variable refresh rate I wouldn't be able to locate the AMD bug. My God, AMD had us with a bug for 6 months and then we are demonizing Nvidia.
Offline