Really right now I’m stumped as to what course of action to take. I’m not sure what’s wrong exactly.
I can Ctrl-Alt-F3 out to a tty session AND SEE IT (though the monitor doesn’t like that it’s not its native resolution), ONLY IF I’ve plugged in my new DisplayPort monitor AFTER booting the computer.
If it was plugged in during boot, both screens will visually hang at whatever they were showing on the desktop until I Ctrl-Alt-F2 back into GNOME.
nVidia GTX 1070 video card, desktop is GNOME on Wayland. 6.12 kernel branch.
Issues appear before the gdm session first comes up, though. Screen stalls in much the same way before gdm comes up, and after entering password to start the session.
I have tried a few things, to indeterminate nonsuccess (I temporarily made the screen-halt incidences turn into screen-black incidences, with kernel parameters or something). Please give me an idea on how to prepare a way to troubleshoot this and get it into a working state, or even a stylish state if I can. I never really had that tty / boot-up busy state output customized much as of yet, very plain.
Huh. How do I start?
What happens if you use x11?
Using X11, the same issue is experienced when booting up, but while in GNOME and I try to Ctrl-Alt-F3 to a tty, instead of the screen hanging with an image of the desktop stuck on screen, it goes black and my monitors both indicate that they are receiving no signal.
What exactly do you have in the command line? Is it grub or systemd-boot? Single monitor? Not enough information here.
The reason i ask is because you said monitors?
Edit: Can you post the hardware? Post the url
inxi -Faz | eos-sendlog
Dual monitor setup. One 15 year old monitor that seems to perform fine, another new that performs great except for the occasional issues that crop up.
systemd-boot
Here’s the URL for that output I got from
inxi -Faz | eos-sendlog
In the past in attempting to get GNOME Wayland to work (successfully) I added these to my dracut.conf.d
force_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "
and in modprobe.d I added (this might have been for a sleep issue…)
options nvidia NVreg_PreserveVideoMemoryAllocations=1
@Prusten
I see you have the latest Bios version available. Both monitors are hooked up via DP cables. Not sure what the cable specs are but there is a huge difference in cables. Some do not meet the specs they are supposed to. Are they connected both directly to the pc or through an adapter? One monitor is HD 1920x1080 and the newer one is 2k running 2560x1440. Are they both running 60 Hz? Hardware output looks fine. I’m not sure about all of the parameters.
Not sure what you mean here. But i assume this is the new monitor and i would think it’s native resolution is 2K setting? Have you tried testing setting both monitors to HD and same hz?
I’m not big on Gnome so the only other suggestion i have also would be to try a different display manager instead of GDM.
Also have you tried it with just the newer monitor alone? I think you are going to have to try some different things to figure out the reason it’s happening. Is it a power issue on boot? Wish i could be more help. Have you also tried a different desktop such as KDE Plasma?