My monitor is 165 Hz with Adaptive Sync, RX 6600 should support it but seems locked at 60 Hz

[MandSpades]

So, I currently have just built a badass gaming rig (from the perspective of someone from a developing country anyways) with a HGMT000 Husky gamer monitor which has adaptive sync at up to 165 Hz.

The CPU is a Ryzen 5500, the monitor plugs straight into the wall socket (because apparently the manufacturers assumed a pitiful gaming 700 W PSU could never handle it alongside other hardware) and into my RX 6600 through a Display Port cable that came with it. I'm running Linux Mint 21.1 and everything else is working perfectly: my 3200 MHz memory runs fine with DOCP, my wifi USB adapter gets recognized, all is well.

EXCEPT for the monitor's ungodly refresh rate which doesn't seem to work. WHY? How do I troubleshoot? What do I have to do to make them 165 Hz work?

[ringshellfish]

Can you post the output of inxi -Fxxxrz and xrandr?

[MandSpades]

Code: Select all

System:
  Kernel: 5.15.0-58-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.7 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING A520M-PLUS II v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2804
    date: 05/11/2022
CPU:
  Info: 6-core model: AMD Ryzen 5 5500 bits: 64 type: MT MCP smt: enabled
    arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 2426 high: 2783 min/max: 400/4267 boost: enabled cores:
    1: 2374 2: 2373 3: 2374 4: 2374 5: 2375 6: 2372 7: 2374 8: 2373 9: 2375
    10: 2374 11: 2595 12: 2783 bogomips: 86397
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: ASRock
    driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: DP-1
    empty: DP-2,DP-3,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:73ff
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
    s-diag: 582mm (22.9")
  Monitor-1: DisplayPort-0 mapped: DP-1 model: MO-HSN-24C serial: <filter>
    res: 1920x1080 hz: 60 dpi: 92 size: 530x300mm (20.9x11.8")
    diag: 609mm (24") modes: max: 1920x1080 min: 720x400
  OpenGL:
    renderer: AMD DIMGREY_CAVEFISH (LLVM 13.0.1 DRM 3.42 5.15.0-58-generic)
    v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 0b:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 0b:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-58-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 09:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp9s0 state: down mac: <filter>
  Device-2: Realtek RTL8188CUS 802.11n WLAN Adapter type: USB
    driver: rtl8xxxu bus-ID: 1-3:7 chip-ID: 0bda:8176 class-ID: 0000
    serial: <filter>
  IF: wlx007511005cb9 state: up mac: <filter>
Drives:
  Local Storage: total: 476.94 GiB used: 28.01 GiB (5.9%)
  ID-1: /dev/nvme0n1 model: NVME SSD 512GB size: 476.94 GiB
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: VC0S036H
    temp: 39.9 C scheme: GPT
Partition:
  ID-1: / size: 467.89 GiB used: 28 GiB (6.0%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 1.5 MiB (0.1%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 39.0 C
    mem: 40.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
  Packages: 2372 apt: 2365 flatpak: 7
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://mirror.ufam.edu.br/linuxmint-packages vera main upstream import backport
    2: deb https://mirror.uepg.br/ubuntu jammy main restricted universe multiverse
    3: deb https://mirror.uepg.br/ubuntu jammy-updates main restricted universe multiverse
    4: deb https://mirror.uepg.br/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/winehq-jammy.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/winehq-kinetic.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/ubuntu kinetic main
Info:
  Processes: 344 Uptime: 3h 39m wakeups: 1 Memory: 15.42 GiB
  used: 4.5 GiB (29.2%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.13

/\ this is the output of the first command you asked me for

Code: Select all

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 530mm x 300mm
   1920x1080     60.00*+ 165.00   144.00   120.00   119.88   120.00    59.94  
   1680x1050     59.95  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1440x900      59.89  
   1280x960      60.00  
   1280x800      60.00  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    60.00    59.94  
   720x400       70.08  
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 disconnected (normal left inverted right x axis y axis)

/\
This is the output of xrandr.

[ringshellfish]

Try to set the refresh rate with xrandr --output DisplayPort-0 --mode 1920x1080 --rate 165. Also I would suggest installing a newer kernel since your hardware is fairly new, sudo apt-get install linux-oem-22.04c. This will install the 6.1 oem kernel.

[MandSpades]

BOHOHOHOHOH it seems to have worked! Though my eyes aren't sharp enough to be 100% sure. Is there some way I can verify my actual frame rate? To tell the software itself to tell me how fast the monitor is rendering stuff.

[ringshellfish]

Yes run the xrandr command again, there should be a "*+" at 165. Also most monitors show their refresh rate in the menu.

[rene]

A note is that that xrandr tweak won't survive a reboot. You'd normally pick the 165Hz output mode through your desktop environments "display" configuration.

[MandSpades]

Mine unfortunately doesn't show the current refresh rate, or else I'd totally be using that. Well, it sure claims to be 165Hz on the terminal, so I'll thank you. Would be cool to have something like one of these HUDs, but I can do without them.

Also, mine is Cinnamon. Where do I pick said refresh rate?

[rene]

Not currently on Mint to quickly check but you should have a refresh rate option in the normal display settings. I.e., as per the picture at https://www.omgubuntu.co.uk/2020/02/cin ... ng-support

[MandSpades]

Thank you!
BTW, a semi-unrelated problem that just happened: I let my PC sleep because I had just eaten dinner and decided to read some manga laying down on bed, and after the screen fully turned off I couldn't turn it back on. It did not respond to any keystrokes or power button taps, so I had to ACPI shut it down and turn it back on. Any idea why that might be and how to fix it?

[rene]

Yes, it's a fairly well-known issue (that is, not waking from suspend) with your type of hardware. F.e. https://www.phoronix.com/news/AMD-s2idle-Check-FW

I see that a much newer BIOS (2023-01-12) is available for your board at https://www.asus.com/motherboards-compo ... 0M-PLUS-II

I'd first of all try that before I'd go look anywhere else...

[MandSpades]

Uh, and how do I apply the AMD patch? Do I have to upgrade to a newer kernel or what?

[rene]

You're on 5.15 and that will with the fixes that that kernel still gets probably be good enough. Updating kernel might be a fair try -- but I'd only bother after trying and finding a BIOS-sides fix to not be enough, i.e., I'd update the BIOS. I'm fairly sure you'll be able to do that on your board by downloading the linked BIOS from ASUS, unpacking it onto a USB stick or some such and updating it from within the BIOS setup itself.

If I'm not mistaken 5.15 is still the only series offered by Mint 21.x through Update Manager -> View -> Linux Kernels, so I'd again for now just do the BIOS update: your current 5.15.0-<some number> is probably good and will have seen fixes for this issue backported to it.

[MandSpades]

isn't it more dangerous to update the BIOS than the kernel? I didn't understand your logic for trying a kernel update only AFTER a BIOS update.

[rene]

A BIOS update is generally safe. The logic as to doing that is that there are as of now no newer kernel (serie)s available for Mint 21.x.

You can install newer series via so-called "oem" kernels but that's relatively nonstandard/invasive whereas your current 5.15.0-58 -- assuming that that's the current 5.15 series kernel on Mint 21, i.e., that you are up to date according to Update Manager -- will have very likely received any patches that went in to newer kernel series anyway by ways of Ubuntu, the supplier of the Mint kernel, integrating those patches into this so-called LTS, Long Term Support, 5.15 kernel series of theirs.

[EDIT] Am away by the way; I'd not be too scared of a BIOS update; they tend to be important.

[MandSpades]

hmm... I'll try to check that out after I get a NoBreak. I live in an area with a certain risk of blackouts and am absolutely terrified of one happening while I update the BIOS, you know?

[rene]

I'd myself be sure to weigh chances against getting in a traffic accident while underway to get said NoBreak -- but, well, whatever I suppose. Nighty

[SMG]

I didn't understand your logic for trying a kernel update only AFTER a BIOS update.

The kernel must work with the information in the BIOS. If your BIOS does not have necessary fixes for your hardware (because the BIOS is too old) then it does not matter how new a kernel you have because the underlying necessary BIOS information is not there to get things working properly.

ASUS does not usually provide much information about what is in a BIOS update, but their updates usually do fix issues.

The 5.19 kernel is now available in Update Manager if you want to try it.

By the way, that AMD patch referenced in the article from last year was for laptops. The issue with AMD graphics drivers and some monitor connections not resuming from sleeps (on conversely some immediately waking up after being suspended) depends on the GPU and the monitor port (HDMI or DP). There have been a regular stream of issues related to suspend for at least the past year. You can do searches here AMD Issues to see what others have reported on your specific hardware.

[SMG]

You can install newer series via so-called "oem" kernels but that's relatively nonstandard/invasive

Invasive?

OEM Kernels are maintained by Canonical. They receive patches and maintenance just like other Canonical kernels and are available in Synaptic Package manager.

[rene]

You can install newer series via so-called "oem" kernels but that's relatively nonstandard/invasive

Invasive?

If you insist we can keep it at nonstandard. The main point that needed making is that his LTS kernel gets lots of by kernel-upstream and/or by Ubuntu directly backported fixes already and that it is as such not necessarily useful to in the case of bugs (rather than new hardware support) go for a fully newer series.

In any case first testing with things BIOS-sides fixed -- the link I posted was just an example; there's been a fair few resume bugs fixed on his generation with and without ACPI involvement -- would in any case be preferred since updating BIOS is something OP wants to do anyway... had there apparently not been a lack of NoBreaks.

Yes, well...