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.

    • youmaynotknow@lemmy.mlOP
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      I’ll check all the logs as soon as she stands up from her desk. Thanks so much.

      And about the “joke”, not really a joke. Most of us see that as nothing more than a slight bump on the road. But Windows users moving over to the brighter side of computers will see that as an excuse to go back to pain. People are weird.

  • Corngood@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    1 year ago

    I’d probably:

    1. make sure it can be reliably reproduced using something like systemctl suspend
    2. try swapping the cables and see if it still happens on the same screen, or the same port
    3. look at journald/dmesg output for the period from suspend to resume

    When the screen fails to wake, are you able to get it back by powering it off, or by unplugging it? Is it X or wayland?

    • Para_lyzed@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Fedora 40 removes X by default (you’d have to install it yourself), so this is going to be using Wayland. Seems like they’re using Ryzen integrated graphics, so at least it shouldn’t be related to any of the problems with Nvidia on Wayland.

      • youmaynotknow@lemmy.mlOP
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        That’s correct. She’s on Ryzen integrated, and Wayland by default, and all info on this subject out there points to Nvidia related issues. Thanks guys.

    • youmaynotknow@lemmy.mlOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Switched cables for between monitors, the same monitor did not come up again.

      Wayland is the default on Fedora.

      I’m waiting for my wife to get up from her desk to look at all the logs.

  • Shareni@programming.dev
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    If you’re on xorg, try executing an xrandr script. I’m currently having a similar issue but haven’t gotten around to automating it yet.

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

    Thanks to everyone that tried to guide me.

    Quick update: For some weird reason, it’s not happening anymore. I ran a dnf update out of habit on it last night when we were going to bed, and completely neglected testing it. Today she suspended it to go out, and when she came back, it just woke up, entered her password, and both monitors were working.

    May have been I updated the kernel, but I honestly don’t remember if it even asked to restart to update,so,maybe it wasn’t? I’m confused, but happy that she never even mentioned windows, so it seems like she’s staying on this side of smart.

  • onlinepersona@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    So it works on windows? If so, then it’s probably not a hardware issue.

    What I could recommend to help track down the issue:

    • test another distro, if possible - sitting here on NixOS it works for me
    • test another display manager (aka X11)
    • test another desktop (KDE, LXDE, whatever)

    If it’s none of the above, you might need to get your hands dirty

    • check if it’s always the same monitor
    • check the logs (journalctl --boot -xe) maybe something will jump out
    • monitor the reconnection of peripherials with sudo udevadm monitor
    • start it when everything’s booted up and everything’s plugged in
    • disconnect problem monitor then reconnect it and observe the output
    • suspend then wake the computer and check the output

    That might give you a hint of what’s going on.

    There’s a change something isn’t working in terms of drivers. You can probe her computer with the executable from https://linux-hardware.org/ and share uploaded result here. Maybe there’ll be an indication of a missing driver or something.

    Anti Commercial-AI license