X11 and multiple refresh rates

After this update my computer no longer has its self respecting refresh rates for each monitor like I had painstakingly set up earlier before the update. Now, my 240 is displaying at 60. How do I make them just work again

Kernel: 6.7.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3e56dd2d-916f-4822-9f3d-d9762a8c38d9 rw rootflags=subvol=@
quiet loglevel=3 nvidia-drm.modeset=1 nvidia-drm.modeset=1 ibt=off
Desktop: KDE Plasma v: 6.0.1 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Type: Desktop Mobo: Micro-Star model: MAG X570S TOMAHAWK MAX WIFI (MS-7D54)
v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.00 date: 07/06/2021
Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3737 high: 3800 min/max: 2200/4850 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3800 2: 3600
3: 3800 4: 3800 5: 3608 6: 3599 7: 3600 8: 3800 9: 3800 10: 3800 11: 3800
12: 3600 13: 3800 14: 3800 15: 3800 16: 3800 bogomips: 121604
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Vulnerabilities: <filter>
Device-1: NVIDIA GA104 [GeForce RTX 3070 Ti] vendor: ASUSTeK driver: nvidia
v: 550.54.14 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
(as of 2024-02; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none off: DP-2,HDMI-A-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 2d:00.0 chip-ID: 10de:2482 class-ID: 0300
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 81 s-size: 1204x343mm (47.40x13.50")
s-diag: 1252mm (49.29")
Monitor-1: DP-2 note: disabled pos: primary,left model: ES-27G2
serial: <filter> built: 2022 res: 1920x1080 dpi: 70 gamma: 1.2
size: 698x393mm (27.48x15.47") diag: 687mm (27.1") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
Monitor-2: HDMI-A-2 mapped: HDMI-1 note: disabled pos: right
model: Dell S2409W serial: <filter> built: 2009 res: 1920x1080 hz: 60
dpi: 92 gamma: 1.2 size: 531x298mm (20.91x11.73") diag: 609mm (24")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
memory: 7.81 GiB
API: Vulkan v: 1.3.279 layers: 11 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 3070 Ti driver: nvidia v: 550.54.14 device-ID: 10de:2482
surfaces: xcb,xlib
Device-1: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 2d:00.1 chip-ID: 10de:228b class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:2
chip-ID: 0db0:a073 class-ID: 0300
API: ALSA v: k6.7.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 26:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp38s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 28:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:2 chip-ID: 8087:0032
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Local Storage: total: 4.78 TiB used: 1.03 TiB (21.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 39.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM004-2CV104
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: ST750LM022 HN-M750MBB
size: 698.64 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: MBR
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 332.96 GiB (71.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 332.96 GiB (71.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 332.96 GiB (71.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 332.96 GiB (71.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
System Temperatures: cpu: 38.8 C mobo: N/A gpu: nvidia temp: 45 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Memory: total: 32 GiB available: 31.26 GiB used: 3.22 GiB (10.3%)
Processes: 376 Power: uptime: 15m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.47 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1969 libs: 577 tools: octopi,paru Compilers:
clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.0
running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2023-12-15
Last full system update: 2024-03-07
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

Your going to need to use Wayland for multiple refresh rates as X11 does not support it to my knowledge.

Yea but like I had to switch to x11 because wayland is a broken stutterfest

Gonna need an actual fix

Switch to a AMD GPU

1 Like

Okay sure, 700 dollars and make myself crash on the few games I play (that are known to be god awful on amd gpus) Sure. Shut up and take my money AMD so you can sponsor forspoken 2

just an FYI, but there looks like there are two nvidia-drm.modeset=1 in the kernel parameters set. X11 typically doesn’t need this kernel parameter, so you can either try just keeping one in there, or removing both.

nah but like on x11 my whole pc is 60hz and that’s unacceptable from my hardware

I’d be happy if you try to be less pushing and more respectful towards people. The words you used to create some of your posts are also unacceptable.


I got this update pushed onto me, I didn’t ask for any of this. I would’ve gladly just let my system be but yall put a big red exclamation point telling me to do this and warned if I waited I’d have problems. I never waited, updated whenever I saw that (or once a week whichever came first) And now I find myself in this predicament where my 3000$ machine (which is one of the only things I own that I care about and it is not working as it should. You can get why I might be a bit anal right now, right? apologies.) Sauce me the fix and I’m on my way to not post to this forum for another 3 or so months in peace

You can just restore a snapshot and be done with it for a while. And I don’t think that justifies any of this as nobody forced you into anything. Anyways consider this a warning, discussion over :slight_smile:


If I restore to my latest snapshot, discord stops working, and my steam library won’t launch a single title released in the last 3 years. This is why I need an actual fix to this issue. Wayland is a stuttering unusable mess and X11 is 60hz hell. A solution to just one of these would be amazing.

or no, just ignore me because “DiSCUsSiOn OvEr :slightly_smiling_face:

Welcome to a rolling release distro. Perhaps you should move to a stable distro if you’re not fond of how Arch works.

Also I get you’re annoyed, but that’s not an excuse to be disrepectful to someone who’s not even to blame.


Not even remotely funny. Tell you a story.

I bought a 6600 to replace a nVidia 1550 and had nothing but issues with the 6600 right out of the gate. Gigabyte kept swearing there was nothing wrong with the card, but after boot issues with it on my PC and my roommates PC and a friend tested on two of his machines we determined the card had issues. I ended up going back to nVidia with a 3060 and have had no issues.

@orangeyouglad blame the Arch devs who chose to give no warning whatsoever, cause this is on them not the Garuda devs.

1 Like

If all that won’t work after rolling back to before the Plasma 6.0 update then they weren’t working before you did the update. In other words don’t blame the update for what from the sound of it with the exception of the refresh rates was aready broken.

You can’t base your whole opinion on one bad experience and it sounds like a Gigabyte issue and not AMD, it could have been a NVIDIA Gigabyte card that had issues and then you swore off NVIDIA.

That’s like saying you will never buy a Ford again because it came with michelin tires and the tires were bad.

You wanted to run on the bleeding edge and now complain you got bloodied? You should wear your scars like a badge of honor. :wink:

There’s a solution to this. Actually, several.

I can cause the first time I have bought an AMD card in years and it has nothing but issues.

This is a frustrating issue I’m trying to solve permanently as well. Wayland is also broken for me (greetings from Manjaro haha), so I’m on X11 and have the same nonsense.
I have three monitors, two at 240hz, one at 144hz. Every time I reboot, I have to execute these commands:

xrandr --output DP-0 --mode 1920x1080 -r 239.96
xrandr --output DP-2 --mode 1920x1080 -r 144.00
xrandr --output DP-4 --mode 1920x1080 -r 239.96

Note that you’ll have to execute “xrandr” by itself first to find the output values for your own system. It should be obvious, like “DP-0 connected blah blah”. And of course you can put it in a script.

There’s probably a smarter way to do this as this is an annoying band-aid, but I’m not the smart guy that will figure it out. Refresh rates mysteriously disappeared from the system settings GUI, so this is all we’ve got.

1 Like