this post was submitted on 28 Oct 2024
11 points (100.0% liked)

Linux Gaming

15818 readers
116 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS
poVoq@slrpnk.net
Quintus@lemmy.ml
mudle@lemmy.ml
11
Monitor keeps post login restarting after an update (Help Needed) (lemm.ee)
submitted 2 weeks ago by josephsh5@lemm.ee to c/linux_gaming@lemmy.ml
2 comments fedilink hide all child comments
 

Hello guys. I posted this problem elsewhere but I've yet to find a solution. I'm experiencing an extremely annoying issue in which the monitor keeps disconnecting and reconnecting in loop post login after a system update. I've first experienced this issue with fedora after updating my system and installing nvidia graphics card. I then tried Bazzite, same exact issue, but at least with Bazzite I can roll back the update, which is a temporary solution. There are several culprits that could be causing this issue:

  1. Kernel update

  2. Nvidia drivers update

  3. Wayland

  4. All of the above

Is anyone else experiencing this exact issue? And if so, any solution besides rolling back the update? Any help is appreciated.

Relevant specs:

  1. Nvidia RTX 3060ti GPU

  2. Intel Core i5 11400F CPU

  3. Asus Prime B560M-K motherboard

  4. Samsung Odyssey G5 Monitor (connected through displayport)

top 2 comments
sorted by: hot top controversial new old
[–] TheBakedPotato@sh.itjust.works 2 points 2 weeks ago

No idea if it will help you here, but everytime someone mentions to me they are having display output issues and they're using Wayland and an Nvidia GPU, I recommend trying X to see if problem persists or not. If it doesn't, I would suspect the GPU driver, but that is a VERY uninformed guess. Lol

[–] Varen@kbin.earth 1 points 2 weeks ago

It is related to the Samsung screen. There‘s a kde bug since Plasma 6.2 where this is happening. Long story short: disable ddc (look up your plasma-powerdevil.service file (mine was in /usr/lib/systemd/user) and add Environment="POWERDEVIL_NO_DDCUTIL=1" to it. Save, restart powerdevil (or reboot) and it shouldn‘t happen anymore.)

See https://bugs.kde.org/show_bug.cgi?id=494522 for reference. Hope it works