MX-Linux 23.6 New Install Display Not Keeping Config [Solved]

Alexzee

Silver Member
Silver Supporter
Joined
Jun 1, 2019
Messages
5,115
Reaction score
3,123
Credits
32,755
Yesterday the fresh installation went well. :)
Took maybe 10 minutes if that.

I've set the display (refresh rate) to 165 Hz 3 times between yesterday and today.
After selecting to keep the new config it's all good. However; if I leave to make a pot of coffee and return to the pc it defaults back to 60.00 Hz.

Do I need to create a new display profile?
 

Attachments

  • Advanced Display.png
    Advanced Display.png
    37.1 KB · Views: 212


I think it means that your Monitor can't go faster than 60 Hz (which is standard and derived from standard alternating current electricity delivery). Nothing's wrong, nothing's broken. That's my 2 cents.
 
I checked the Xorg file and it confirms 1920x1080 and 170 Hz as the max.

Running xrandr shows the same deal-
Code:
$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
   1920x1080     60.00 + 170.00   165.00*  144.00   120.00   100.00   119.88    60.00    50.00

I haven't this issue in Debian 12 or Slackware since installing the new GPU and adjusting the display to 165 Hz. I'm thinking maybe XFCE is missing a pkg?

When it defaults back to 60.00 Hz there's lines all over the monitor and I can bearly see things until I reset it again. It's acting like a bug however, it may not be one.
I could try the 'TearFree' or the 'VariableRefresh' under the man page for amdgpu but I don't know what I'm doing with that and need hlep.

Maybe @Brickwizard, @wizardfromoz or @osprey will know how to tweak this?

It's getting late and have to work in the morning.
 

Attachments

  • Xorg Log.png
    Xorg Log.png
    297 KB · Views: 169
  • Max 170 Hz.png
    Max 170 Hz.png
    251.9 KB · Views: 176
Last edited:
Maybe @Brickwizard, @wizardfromoz or @osprey will know how to tweak this?

Not I, said the fly.

I took a look at this earlier in my day Alex, but moved on, as I had nothing to offer.

That being said, I may have a way for you to identify a couple of files that may or may not help.

I'll come back with them shortly while you are catching zzz's.

Wiz
 
OK, so take a look at my #40 post here https://linux.org/threads/configuring-dual-monitors-in-linux-mint.50916/post-238579
...on what is an unrelated matter. Once you've read that, you may see where I am headed.

Back?

In your case, I would, starting with your 60 Hz state
  1. create the timestamp file
  2. change your refresh rate to the desired 165 Hz
  3. issue from Terminal
    Code:
    find -newer timestamp
  4. note the files that have changed
  5. examine those files if they are human readable
  6. leave to make a pot of coffee and return to the pc
  7. if it has reverted back to 60 run
    Code:
    find -newer timestamp
    again and
  8. examine the additional files (or same files again) if they are human readable
This may at least give you some troubleshooting leads besides what you have so far examined.

I find this quite useful, and use it periodically.

HTH and good luck

Wiz
 
I checked the Xorg file and it confirms 1920x1080 and 170 Hz as the max.

Running xrandr shows the same deal-
Code:
$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
   1920x1080     60.00 + 170.00   165.00*  144.00   120.00   100.00   119.88    60.00    50.00

I haven't this issue in Debian 12 or Slackware since installing the new GPU and adjusting the display to 165 Hz. I'm thinking maybe XFCE is missing a pkg?

When it defaults back to 60.00 Hz there's lines all over the monitor and I can bearly see things until I reset it again. It's acting like a bug however, it may not be one.
I could try the 'TearFree' or the 'VariableRefresh' under the man page for amdgpu but I don't know what I'm doing with that and need hlep.

Maybe @Brickwizard, @wizardfromoz or @osprey will know how to tweak this?

It's getting late and have to work in the morning.
Since the output from xrandr shows 170 and 165 refresh rates as options, you could try and use xrandr to set it temporarily with a command like:
Code:
xrandr --output HDMI-A-0 --mode 1920x1080 --rate 165
Then run xrandr again to see if it has registered the change.

For a permanent change one normally writes an xorg.conf snippet file and places in
/usr/share/X11/xorg.conf.d, or /etc/X11/xorg.conf.d/.

Perhaps see if the temporary change works first.

Edit: it looks like your change to 165 did work, so to set it permanently perhaps write an xorg snippet file named something like: 10-refresh.conf
Code:
Section "Monitor"
     Identifier "HDMI-A-0"
     Option "PreferredMode" "1920x1080_165"
 EndSection

I usually place such files in /usr/share/X11/xorg.conf.d, but others use the /etc directory mentioned above.
 
Last edited:
OK, so take a look at my #40 post here https://linux.org/threads/configuring-dual-monitors-in-linux-mint.50916/post-238579
...on what is an unrelated matter. Once you've read that, you may see where I am headed.

Back?

In your case, I would, starting with your 60 Hz state
  1. create the timestamp file
  2. change your refresh rate to the desired 165 Hz
  3. issue from Terminal
    Code:
    find -newer timestamp
  4. note the files that have changed
  5. examine those files if they are human readable
  6. leave to make a pot of coffee and return to the pc
  7. if it has reverted back to 60 run
    Code:
    find -newer timestamp
    again and
  8. examine the additional files (or same files again) if they are human readable
This may at least give you some troubleshooting leads besides what you have so far examined.

I find this quite useful, and use it periodically.

HTH and good luck

Wiz
Forgot all about the touch cmd, thanks Chris.
Perhaps I didn't do this correctly?

Code:
touch timestamp
@mxmix:~
$ find -newer timestamp
./.mozilla/firefox/d0g7mbj7.default-release/places.sqlite-wal
./.mozilla/firefox/d0g7mbj7.default-release/datareporting
./.mozilla/firefox/d0g7mbj7.default-release/datareporting/glean/db
./.mozilla/firefox/d0g7mbj7.default-release/datareporting/glean/db/data.safe.bin
./.mozilla/firefox/d0g7mbj7.default-release/datareporting/aborted-session-ping
./.mozilla/firefox/d0g7mbj7.default-release/storage/default/https+++www.linux.org/cache
./.mozilla/firefox/d0g7mbj7.default-release/storage/default/https+++www.linux.org/cache/context_open.marker
./.mozilla/firefox/d0g7mbj7.default-release/storage/default/https+++www.linux.org/cache/caches.sqlite-wal
./.mozilla/firefox/d0g7mbj7.default-release/storage/default/https+++www.linux.org/ls
./.mozilla/firefox/d0g7mbj7.default-release/storage/default/https+++www.linux.org/ls/usage
./.mozilla/firefox/d0g7mbj7.default-release/storage/default/https+++www.linux.org/ls/data.sqlite
./.mozilla/firefox/d0g7mbj7.default-release/extension-store-menus
./.mozilla/firefox/d0g7mbj7.default-release/extension-store-menus/data.safe.bin
./.mozilla/firefox/d0g7mbj7.default-release/cookies.sqlite-wal
./.cache/xfce4/clipman
./.cache/xfce4/clipman/textsrc
./.cache/mozilla/firefox/d0g7mbj7.default-release/cache2/entries
./.cache/mozilla/firefox/d0g7mbj7.default-release/cache2/entries/134A7503F3FEC83A4DD38F6119EAA54AFE436063
./.cache/mozilla/firefox/d0g7mbj7.default-release/cache2/entries/C7492476A565ACC2B68CF01A1D9F6B0161D9F943
 
Since the output from xrandr shows 170 and 165 refresh rates as options, you could try and use xrandr to set it temporarily with a command like:
Code:
xrandr --output HDMI-A-0 --mode 1920x1080 --rate 165
Then run xrandr again to see if it has registered the change.

For a permanent change one normally writes an xorg.conf snippet file and places in
/usr/share/X11/xorg.conf.d, or /etc/X11/xorg.conf.d/.

Perhaps see if the temporary change works first.

Edit: it looks like your change to 165 did work, so to set it permanently perhaps write an xorg snippet file named something like: 10-refresh.conf
Code:
Section "Monitor"
     Identifier "HDMI-A-0"
     Option "PreferredMode" "1920x1080_165"
 EndSection

I usually place such files in /usr/share/X11/xorg.conf.d, but others use the /etc directory mentioned above.
Walking away for 15 minutes to see what happens.

If the refresh doesn't work correctly, I'll create a xorg.conf, shut down, reboot and be back to let you know how things went.
 
Well, it's been 15-20 min's and the display config window was open again with it reset to 60 Hz's. See the attached file.

To recall as it's been a while, I double checked on where nano places new files. Nano puts new files in your current directory. Having said that, I'll just have to move the new xorg config I'm about to make to /usr/share/X11.confd/ with root privileges.

So, I'm off to create the xorg conf.:)
 

Attachments

  • Display Default.png
    Display Default.png
    41.3 KB · Views: 166
Last edited:
Just curious... did you change a cable, or change to a different port?

For example, I have a 2k 165Hz monitor... well, under certain conditions I do.
If I use a display port cable, plugged into the first display port socket on the card I get 165 Hz.
If I use HDMI, I get 60Hz. If I use the 2nd display port, I get 60Hz.

Sometimes these things make a dfference.
 
Just curious... did you change a cable, or change to a different port?

For example, I have a 2k 165Hz monitor... well, under certain conditions I do.
If I use a display port cable, plugged into the first display port socket on the card I get 165 Hz.
If I use HDMI, I get 60Hz. If I use the 2nd display port, I get 60Hz.

Sometimes these things make a dfference.
No, I didn't change a cable just used the same HDMI cable that came with the monitor. Then plugged the opposing end into the HDMI port on the new GPU.

This new Radeon RX 550 only has one port.
 
Ok rebooted after moving the new 10-refresh file to the /usr/share/X11.conf.d and the Display MGR popped up again with the wrong refresh rate and screen flashing.

Got other things on the table now that need tending to so I'll have to work on this over the next few days.

FWIW, On this triple booted rig, Debian 12 is set to 165 Hz as is Slackware. I'm not having any issue's with the display or the refresh rate just an issue with MX-Linux.

@osprey Could it be that the XFCE DE is missing a pkg/lib or some other dependency that is causing the Display MGR to keep launching on the screen/monitor?

Is there a way to test the API of the Display MGR?
 
Last edited:
sorry about my uninformed response. i didn't know that modern conventional systems were now at that high of display refresh rates. sorry about that.
 
sorry about my uninformed response. i didn't know that modern conventional systems were now at that high of display refresh rates. sorry about that.
It's all good mate. Enjoy the day.
 
The display mgr still continues to launch with the incorrect refresh rate. See the attached file.

I'm reading online how other Linux users have tweaked the Xorg config file to rectify the refresh rate situation. After a stressful week I need a break.

IF, I find anything useful I'll post it.

@wizardfromoz and @osprey thanks for the help.:)
 
Just for laughs, does it work on a Live USB? This shouldn't be that hard.

1748625608768.png


I don't think I've touched my X11.conf in years.

@LianLi:/etc/X11$ tree
.
├── applnk
├── fontpath.d
│ ├── liberation-mono-fonts -> ../../../usr/share/fonts/liberation-mono-fonts
│ ├── liberation-narrow-fonts -> /usr/share/fonts/liberation-narrow
│ ├── liberation-sans-fonts -> ../../../usr/share/fonts/liberation-sans-fonts
│ ├── liberation-serif-fonts -> ../../../usr/share/fonts/liberation-serif-fonts
│ └── xorg-x11-fonts-misc:unscaled:pri=10 -> /usr/share/X11/fonts/misc
├── xinit
│ ├── Xclients
│ ├── Xclients.d
│ ├── xinitrc
│ ├── xinitrc-common
│ ├── xinitrc.d
│ │ ├── 00-start-message-bus.sh
│ │ ├── 10-qt5-check-opengl2.sh
│ │ ├── 10-qt6-check-opengl2.sh
│ │ ├── 50-systemd-user.sh
│ │ ├── 50-xinput.sh
│ │ ├── 98vboxadd-xclient.sh
│ │ └── localuser.sh
│ ├── xinput.d
│ │ ├── ibus.conf
│ │ ├── none.conf
│ │ ├── xcompose.conf
│ │ └── xim.conf
│ ├── xinputrc -> /etc/alternatives/xinputrc
│ └── Xsession
├── Xmodmap
├── xorg.conf.d
│ └── 00-keyboard.conf
├── Xresources
└── Xsession.d
└── 90xbrlapi

14 directories, 20 files
 
Just for laughs, does it work on a Live USB? This shouldn't be that hard.

View attachment 26290

I don't think I've touched my X11.conf in years.

@LianLi:/etc/X11$ tree
.
├── applnk
├── fontpath.d
│ ├── liberation-mono-fonts -> ../../../usr/share/fonts/liberation-mono-fonts
│ ├── liberation-narrow-fonts -> /usr/share/fonts/liberation-narrow
│ ├── liberation-sans-fonts -> ../../../usr/share/fonts/liberation-sans-fonts
│ ├── liberation-serif-fonts -> ../../../usr/share/fonts/liberation-serif-fonts
│ └── xorg-x11-fonts-misc:unscaled:pri=10 -> /usr/share/X11/fonts/misc
├── xinit
│ ├── Xclients
│ ├── Xclients.d
│ ├── xinitrc
│ ├── xinitrc-common
│ ├── xinitrc.d
│ │ ├── 00-start-message-bus.sh
│ │ ├── 10-qt5-check-opengl2.sh
│ │ ├── 10-qt6-check-opengl2.sh
│ │ ├── 50-systemd-user.sh
│ │ ├── 50-xinput.sh
│ │ ├── 98vboxadd-xclient.sh
│ │ └── localuser.sh
│ ├── xinput.d
│ │ ├── ibus.conf
│ │ ├── none.conf
│ │ ├── xcompose.conf
│ │ └── xim.conf
│ ├── xinputrc -> /etc/alternatives/xinputrc
│ └── Xsession
├── Xmodmap
├── xorg.conf.d
│ └── 00-keyboard.conf
├── Xresources
└── Xsession.d
└── 90xbrlapi

14 directories, 20 files
Agreed, it should not be this hard.
I'll boot into the Live usb of MX Linux later this evening or tomorrow morning and let you know.
Frustrated at the moment and have many things that need tending to.
 
Ok, @dos2unix
Just booted into the thumb drive MX Linux Live from the BIOS.
The welcome screen flashes. Just couldn't capture it as it was too fast for the camera.

So, yeah the display and refresh rate are off balance just like the fresh installation.

See the 3 attached files.
 

Attachments

  • MX Tearing.jpg
    MX Tearing.jpg
    2.7 MB · Views: 172
  • MX Welcome.jpg
    MX Welcome.jpg
    2.3 MB · Views: 162
  • MX BIOS.jpg
    MX BIOS.jpg
    1.1 MB · Views: 174
Modifying the config for Xorg made no difference.
Made several attempts to contact the MX Forum Admin and that failed as the Captcha program is broken / mis-configured.

Performing a fresh installation of Sparky Linux went well.

Code:
root@Debiansparky:~# cat /etc/os-release
PRETTY_NAME="SparkyLinux 7.7 (Orion-Belt)"
NAME="SparkyLinux"
VERSION_ID="7.7"
VERSION="7.7 (Orion-Belt)"
ID=sparky
ID_LIKE=debian
HOME_URL="https://sparkylinux.org/"
SUPPORT_URL="https://sparkylinux.org/forum/"
BUG_REPORT_URL="https://sourceforge.net/p/sparkylinux/tickets"
VERSION_CODENAME=orion-belt
DEBIAN_CODENAME=bookworm
 

Attachments

  • Sparky DE.png
    Sparky DE.png
    92.4 KB · Views: 165
  • Sparky DE 2.png
    Sparky DE 2.png
    194.2 KB · Views: 163
  • Sparky Apt.png
    Sparky Apt.png
    2 MB · Views: 183


Follow Linux.org

Members online


Latest posts

Top