Linux Gaming

15347 readers

1 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Gaming on Linux

Matrix:

Telegram:

Gaming on Linux

founded 1 year ago

MODERATORS

monolalia@lemmy.world

Nvidia 555 drivers causing no display on secondary monitor (lemmy.world)

submitted 4 months ago* (last edited 4 months ago) by Bruhh@lemmy.world to c/linux_gaming@lemmy.world

10 comments fedilink hide all child comments

Currently, if I upgrade to 555 drivers, my second monitor will not show a display despite it being detected by Plasma and xrandr. Additionally, if I do get past the log screen on wayland, my framerate/refresh rate is abysmal but not reported by xrandr. Unplugging the second monitor fixes the issue.

Sometimes, before login, I simply get a black screen/no signal which I've seen other post about but have not seen anything about second display not displaying.

Initially happened on EOS but swapped over to Bazzite and same issue. Reverting to the last 550 drivers and both monitors work fine.

I've tried setting nvidia kernel parameters for wayland and disabiling GSP firmware with no luck. Both monitors connected to the GPU. Issue on both x11 and wayland. Any input would be great.

UPDATE: Connecting the second display with DisplayPort instead of HDMI resolved the issue and I can log into wayland no problem with both functioning displays

Ryzen 5600x
3070ti

Primary Monitor is connect via DisplayPort
Secondary Monitor is connected via HDMI

all 11 comments

sorted by: hot top controversial new old

[–] rolling_resistance@lemmy.world 9 points 4 months ago

Disappointed to learn that Nvidia drivers are still having such serious issues.

[–] BananaTrifleViolin@lemmy.world 3 points 4 months ago* (last edited 4 months ago) (2 children)

Have you tried connecting both via display port or both via HDMI?

Not that that should matter normally, but good starting point in trying to get around what may be a bug?

Edit: just remembered I've been having intermitten problems with my 2nd display since last nvidia driver if I have my vr head set plugged in to the 3rd port (even off). When i unplugged it and restarted I got my desktop loading as normal.

[–] Bruhh@lemmy.world 2 points 4 months ago

Yeah, the black screen after logjn happens when both monitors are plugged in I've noticed. If I unplug the second monitor I can get into a wayland session fine but the moment I plug the second monitor in, the refresh rate tanks if the DE doesn't freeze first.

I'll try your suggestion and update the results after work.

[–] Bruhh@lemmy.world 1 points 4 months ago

Believe or not, connecting my secondary monitor with display port seems to have solved the issue

[–] Shifty@sh.itjust.works 2 points 4 months ago (2 children)

Is one of your monitors HDR? I've been getting similar issues (EndevourOS) ever since upgrading to 555, where both of my monitors are black/no signal when logging into Wayland. Unplugging my primary monitor fixes the secondary monitor, and it seems like HDR is the problem in my case - https://bugs.kde.org/show_bug.cgi?id=488941

After deleting ~/.config/kwinoutputconfig.json, I could login. I did some tests and the issue happens when HDR is enabled. In the config file that put "highDynamicRange" and "wideColorGamut" to "true". Just changing "highDynamicRange" to "false" doesn't work, but if I put both to "false", I can login again.

Simply deleting kwinoutputconfig didn't fix the problem for me but I haven't tried setting it as read-only yet (Probably a good idea to back it up first). My X11 is working normally so I'll stick with that until this bug is resolved.

[–] Bruhh@lemmy.world 2 points 4 months ago

Main monitor does support HDR but I never have it enabled. I'll give this a shot when I get the chance

[–] Bruhh@lemmy.world 2 points 4 months ago

Connecting my second display with a display port rather than HDMI seems to have solved the issue

[–] Rooki@lemmy.world 2 points 4 months ago (1 children)

Are both directly connected to the GPU? Or did you connect one to the GPU and one to the Motherboard?

[–] Bruhh@lemmy.world 1 points 4 months ago

Updated post: Both monitors are connected to the GPU