Finally got my wife away from Windows and on Fedora 40 (Gnome 46).

Now, when her PC goes to suspend and when she wakes it up, one of her 2 monitors doesn’t wake up.

Both are connected to HDMI ports (no dedicated video card, just the integrated card in her Ryzen 9).

Any ideas on what could be happening? I wouldn’t want her to go back to Winblows over something so insignificant, but she would.

  • acockworkorange
    link
    fedilink
    arrow-up
    9
    ·
    7 months ago

    This happens to me consistently on Linux Mint. My secondary monitor which is an HDMI TV resumes fine and takes over as primary. The primary screen on a Display Port over USB fails to wake up.

    I’m using the edge kernel line, version 6.5. I’ll try to downgrade to 5.15 to check if this is a kernel regression.

    I’m running an AMD system with embedded graphics from Minisforum, btw. What are you running and which kernel?

    • applepie@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      7 months ago

      i got pop (fresher kernel?) and xorg but same issue you described. i keep unplugged unless i am using it but also since it will limit main monitor fps.

      • acockworkorange
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        I have tried disconnecting and then connecting the display to see if it will wake up, but it doesn’t work. Sometimes shutting down the display and turning it on again work.

      • acockworkorange
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        7 months ago

        I managed to get it on kernel 5.15 and replicate the issue. I had to find its USB-C charger to keep it on while I power down my monitor otherwise it would hard shutdown it. So, connecting the monitor back, the weirdest thing just happened. The display rearranged, but didn’t use the new monitor. Instead, the lock screen got resized and I could see my session behind it without logging in (!).

        I’ve got this on dmesg: [119330.829398] amdgpu 0000:63:00.0: [drm] *ERROR* no VCPI for [MST PORT:00000000e7b3da3d] found in mst state 000000005563f49a

        journalctl gives more details:

        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (II) AMDGPU(0): Allocate new frame buffer 2560x1440
        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (II) AMDGPU(0):  => pitch 10240 bytes
        May 03 17:05:01 Glass rtkit-daemon[1209]: Supervising 7 threads of 3 processes of 1 users.
        May 03 17:05:01 Glass rtkit-daemon[1209]: Successfully made thread 33483 of process 1581 owned by '1000' RT at priority 5.
        May 03 17:05:01 Glass rtkit-daemon[1209]: Supervising 8 threads of 3 processes of 1 users.
        May 03 17:05:01 Glass csd-media-keys[1761]: Unable to get default sink
        May 03 17:05:01 Glass csd-color[1770]: failed to reset xrandr-Samsung Electric Company-SAMSUNG gamma tables: gamma size is zero
        May 03 17:05:01 Glass csd-color[1770]: failed to reset xrandr-Samsung Electric Company-SAMSUNG gamma tables: gamma size is zero
        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (II) Quirked EDID physical size to 0x0 cm
        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (--) AMDGPU(0): HDMI max TMDS frequency 225000KHz
        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (II) AMDGPU(0): EDID vendor "SAM", prod id 29044
        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (II) AMDGPU(0): Using hsync ranges from config file
        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (II) AMDGPU(0): Using vrefresh ranges from config file
        May 03 17:05:01 Glass /usr/libexec/gdm-x-session[1601]: (II) AMDGPU(0): Printing DDC gathered Modelines:
        

        I got it to switch monitors using Cinammon’s Display app, but it will not take two displays at the same time.

        • youmaynotknow@lemmy.mlOP
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          I would totally try a kernel update, even if it meant uxing zen kernel. Older kernels is one of the reasons why I stay away from Mint and Zorin.

          • acockworkorange
            link
            fedilink
            arrow-up
            2
            ·
            7 months ago

            Weirdest thing is I could swear it didn’t use to happen on Mint 21 until I both upgraded to 21.2 and switched to the edge low latency kernel. It doesn’t bother me much, and everything else just works, plus I’m addicted to aptitude so I need a Debian based distro.