Arch Linux

Xalares

Member

Registered: 2022-02-09

Posts: 27

Second screen not always detected at startup.

Hi everybody, I'm facing an issue since some times now, I have two screens and sometimes, at startup, only one screen is detected.
I can solve the issue by unplug and plug again the cable. It may be irrelevant, but It's an HDMI cable plugged to an HDMI to display port adapter. My GPU is an NVIDIA 2060RTX, and I'm using NVIDIA's driver on X org.
I'm using lts kernel version.
Here is the system log for such a boot
https://0x0.st/HqSB.log
I've found these lines in the log, I guess it's somewhat related, but maybe I'm wrong.

mai 24 11:20:06 xalares.tk gnome-shell[1576]: Failed to open gpu '/dev/dri/card0': No suitable mode setting backend found
mai 24 11:20:06 xalares.tk org.gnome.Shell.desktop[1576]: Failed to setup: No GPUs found
mai 24 11:20:07 xalares.tk gnome-session[1563]: gnome-session-binary[1563]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
mai 24 11:20:07 xalares.tk gnome-session-binary[1563]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
mai 24 11:20:07 xalares.tk gnome-session-binary[1563]: Unrecoverable failure in required component org.gnome.Shell.desktop

Thanks for your help, I'm available for any questions !

Last edited by Xalares (2023-05-24 09:51:39)

seth

Member

Registered: 2012-09-03

Posts: 38,628

Re: Second screen not always detected at startup.

mai 24 11:20:06 xalares.tk gnome-shell[1576]: Failed to open gpu '/dev/dri/card0': No suitable mode setting backend found

https://wiki.archlinux.org/title/NVIDIA … de_setting

This will also provide you w/ a proper edid, but it's not clear whether that's the cause for your main concern.

I exclusively see one output in that journal ("Asustek Computer Inc VA249")?
Before re-plugging the monitor, what's the output of "xrandr -q"?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Your xinitrc is broken

Xalares

Member

Registered: 2022-02-09

Posts: 27

Re: Second screen not always detected at startup.

Hi ! Thanks for your reply. I've already visited https://wiki.archlinux.org/title/NVIDIA … de_setting but I might have misunderstood the process.
I've understood that I had the choice between enabling nvidia_drm.modeset=1 in grub and adding nvidia, nvidia_modeset, nvidia_uvm and nvidia_drm to the initramfs,
so I've added these modules to the initramfs and of course added the related pacman hook, but I've not set nvidia_drm.modeset = 1.

Before re-plugging the monitor, what's the output of "xrandr -q"?

I'll investigate that when the bug reappears.

Last edited by Xalares (2023-05-25 14:36:09)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 19,247

Re: Second screen not always detected at startup.

It's generally both of the things so you should set nvidia_drm.modeset=1 as well.

Xalares

Member

Registered: 2022-02-09

Posts: 27

Re: Second screen not always detected at startup.

I'll try with nvidia_drm.modeset=1, and see if something change.

Xalares

Member

Registered: 2022-02-09

Posts: 27

Re: Second screen not always detected at startup.

Hi, I think that was the issue, it corrected some other bugs I got on boot with plymouth. But now I'm on Wayland, and I got jerky images when a watch a video, but that's another issue.

seth

Member

Registered: 2012-09-03

Posts: 38,628

Re: Second screen not always detected at startup.

https://wiki.archlinux.org/title/GDM#Use_Xorg_backend

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Your xinitrc is broken

Xalares

Member

Registered: 2022-02-09

Posts: 27

Re: Second screen not always detected at startup.

Hi, actually that wasn't the solution, unfortunately, it happened again. I've run "xrandr -q" and got this result https://0x0.st/HbXY.log. But this time I didn't have to plug and unplug the monitor, only to disable it in the display settings and re-enable it. What's weird is that even if my screen was off, it was detected in the display settings this time, it wasn't the case before so the case evolved.