#[SOLVED] EndeavourOS Gnome 44.4 Wayland multi-monitor refresh rates.

52 messages · Page 1 of 1 (latest)

fresh bear
#

I have a dual monitor setup with primary as 27" 1920x1080 @75hz, secondary being 22", 1920x1080 @60hz. However, my issue is that my 27" is locked at 60hz to match the maximum of my 22". The option to switch my primary to 75hz is available, but when I select it, the OS locks up for about 20 seconds and the monitor goes black. After that brief freeze, it all comes back, and the monitor is back to 60hz. I've tried searching all over multiple forum boards, and found quite a number of people with the same issue, including bugs reported on gitlab from ~5 years ago. None of the reports I've found have a solution. Maybe I'm just missing something, or is this still an issue? Any help is greatly appreciated.

fresh bear
#

I don't know why this is not referenced anywhere else on the internet that I can find, but here it is for future reference.

granite monolith
#

... solved

wild cradleBOT
#

#9742 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.

  • You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
  • You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".

Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you

fresh bear
# granite monolith ... solved

Semi-Solved? The refresh rates available showes 74.20, when I know it should be 75. Minor inconvenience, I can deal.
Bigger problem is, it won't stick.

granite monolith
#

That’s normal

fresh bear
#

Reboot resets to 60hz.

granite monolith
#

Set the refresh rate to 75Hz in either the x config or a wm startup script to make it persist

fresh bear
#

https://davejansen.com/add-custom-resolution-and-refresh-rate-when-using-wayland-gnome/
I've found this, but I'll also look into setting it in x config (is this still a thing in wayland?)

Dave Jansen

Monitors and/or adapters don't always return all the supported resolutions and refresh rates to your computer. In those cases you may need to do some finagling to get the right configuration to work.

On Windows you can usually rely on your graphics card's accompanying software to offer such functionality,

granite monolith
fresh bear
#

I'll try the link I just posted, if it works, I'll mark this post as solved. Thank you.

granite monolith
#

Well, it’s not quite solved yet, so don’t.

#

Jeez why does well autocorrect to we’ll

fresh bear
#

Oh, no, once I determine if that link is the solution.

Autocorrect isn't as smart as we like to think it is.

granite monolith
#

Yea

fresh bear
#

On the off chance, would you know if I'll need to set it for both monitors? Or just the one that I need the setting available for?

granite monolith
#

I’m not really sure what you mean

fresh bear
#

Nevermind, the tutorial has multiple monitors, and only sets the added setting for one without specifying anything for the second.

fresh bear
granite monolith
#

Ok, cool

fresh bear
#

Okay, that didn't work. Hunting down a solution for setting default refresh rate on google is only giving me results for setting wayland as default. 😕

#

In case anyone runs across this before I come back with a solution... My current issue is that I can set my primary monitor to the correct refresh rate after installing 'mutter-vrr' and 'gnome-control-center-vrr'
However, once I've set the refresh rate, it reverts back to the 60hz that matches my secondary display after a reboot. I'm currently searching for a way to set the primary to 75hz by default.

fresh bear
#

Tried editing the preferred settings in ~/.config/monitors.xml and rebooting. No success.
Tried 'cp ~/.config/monitors.xml /var/lib/gdm/.config/monitors.xml' No success.

fresh bear
#

Okay, so my issue is initially resolved, but now I can't seem to get my display configuration to stick after reboot or sleep. It always reverts to default. So I've got to go into display settings and change everything back to the way I want it.
I noticed this issue started when I enabled fractional scaling. So I disabled it, thinking that might fix the issue, however it does not. Does anyone have any insight to this? Because I can't find any recent bug reports or forum posts that address this.

granite monolith
#

Running whatever command you use to set it to 75Hz, I mean

fresh bear
#

I don't use a command, I set the prefferred setting via gnome display settings.

granite monolith
#

Find out if there’s a way to do it via a command.

fresh bear
fresh bear
#

FWIW, I followed the instructions in these two links to enable vrr..
Ran 'gsettings set org.gnome.mutter experimental-features "['variable-refresh-rate']"'
and installed mutter-vrr and gnome-control-center-vrr

#

As I said, I did also enable fractional scaling, but that's when the issue started, so I disabled fractional scaling. I'm now wondering if there is a config file that is saved somewhere from enabling fractional scaling that might be the culprit.

#

Gnome uses ~/.config/monitors.xml to control monitor configuration. I can't upload mine as a txt file, so I'll link a pastebin below. It gets reset to "default" every time I reboot. So I suspect there is something in startup that is pulling a "default" version, which is not changing when I modify the settings via gui. Currently backtracking to find out what 'creates' this file on boot. Maybe that will shed some light on what keeps resetting these settings.
https://pastebin.com/UsQz9svi

fresh bear
#

A bug that is eight freaking years old. Should have been addressed by now. Seriously. What's going on here?

granite monolith
#

You could become maximum jank and have a script write the proper values to the file on gnome startup.

fresh bear
#

So copying ~/.config/monitors.xml to /var/lib/gdm/.config/ is a no-go. Doesn't work.

#

I don't use gnome for jank though. I use it because it's supposed to be MORE user friendly. Blah. I may just make a startup script that does a quick cp of the corrected file to the location before everything is loaded.

#

Now I gotta learn to script.

granite monolith
granite monolith
#

Hopefully dumb issues like this get fixed someday

fresh bear
#

(idk how to superscript)

fresh bear
# granite monolith ``` #!/bin/bash cp /place/monitors.xml /betterplace/ ``` 💥

Looks like this is how it'll have to be done. Just make a copy of the corect monitors.xml in my home directory somewhere, then have the script run at startup before gdm loads to place the file where gdm can read it.
Though, this may not work, if gdm is pulling the information from somewhere else when it loads, and replacing the monitors.xml file.

#

Wish I knew how it was pulling the information for building monitors.xml. Then I might be able to work out how to stop it from doing that. Like I said before, I think it's a borked config file somewhere.

fresh bear
#

SOLUTION

Found the proper solution to gnome wayland not saving monitor configuration settings at the link below.
The link references the arch wiki entry for gdm, but the arch wiki isn't super clear on what to do. The gnome discourse page is very explicit on exacly what commands to execute in order to make this work.
Essentially...

  1. delete ~/.config/monitors.xml
  2. Open display settings and adjust to your liking, click apply when finished. This will generate a new monitors.xml file.
  3. Open terminal and run 'sudo cp ~/.config/monitors.xml ~gdm/.config'
  4. run 'sudo chown gdm: ~gdm/.config/monitors.xml'
    https://discourse.gnome.org/t/how-do-you-configure-your-displays-for-gdm/13762

I think someone might need to look into the arch wiki link provided in the gnome discourse I've linked here and see about making the information more clear.