This sound like a similar problem I had when I installed a second gpu for VMs
SDDM is using X11 and using the iGPU as the “main” output. Setting the display server to Wayland in an SDDM config is what worked for me. https://wiki.archlinux.org/title/SDDM#Running_under_Wayland
You can check first before messing with configs by plugging your monitor in the other gpu. (your mobo chipset in your case)
Oh interesting - so merely creating that config file and putting “[General]
DisplayServer=wayland” in there did the trick?
Will definitely give this a try!
Did you find a way to fix this issue ? I have a similar thing on my side. I cannot seem to be able to log in with a Plasma Wayland session. Monitors lose signal after login. X11 still works properly on Plasma 6.01. I’m on a Nvidia 4090.
Edit : My monitors are all 144hz monitors.
I just wanted to comment and say that I am having weird issues with setting one display to 120hz and the other to 60hz on Wayland. I have an Nvidia 3080ti with one HDMI port connected to an LG C2 and the other is connected to an AVR just for sound. It still appears as a display, though. I haven’t totally nailed down the settings vs the symptom, but I would get a black login screen sometimes. I could was able to log in a few times, but my display settings like primary display and resolution would not be “remembered” and would be back at defaults.
This is what happens to me on Plasma 6.0.1 and even before the upgrade. It seems to work if only one monitor is plugged in at 120hz or if both are set to 60hz. I have a 3080ti and it is connected to an LG C2 and an AVR. A VM with a 4070ti Super passed through does not have this issue at 120hz using an HDMI dummy plug flashed with an LG C2 EDID.
Yes this seems to be related to the refresh rate of the monitors. I have 3 monitors. 1 is plugged over HDMI and 2 which are plugged over DP. The 3 of the are normally at 144hz. This is more an inconvenience for me since I can still use X11 which works fine.
Are you seeing the same behavior when over 60hz? Does it matter if they all match at above 60hz?
I am on plasma 6 now and have a 4060 with two 75hz monitors. I am able to login to wayland, but as soon as the computer sleeps, I get black screens on waking and only a hard reboot will bring it back. A couple of times there has been some display output, but it is unresponsive to input until I reboot. Similar to @Hyrules, I have one plugged into hdmi and one in DP.
I went back to X11 for the time being and do not have issues. Much to my surprise, there is a noticeable different between 60 and 75hz. Not sure if I want to try it at 60 just so Wayland works.
Same issue here. Blinking curser at the top right.
I have a gigabyte aero laptop w/ a 3070 ti video card.
I have the laptop thunderbolt going through an older dell thunderbolt dock to displayport to a Alienware 34" OLED monitor.
Works great before the upgrade to plasma 6.
Changing the refresh rate in X11 does not seem to have an impact on wayland. Still does not show any image. My screen goes to standby right after login in Plasma Wayland.
Yes, I would expect that to be the case. I’d suspect it needs to be changed in both. Since it seems okay in X11, I’m leaving it.
Some progress here. I created a new profile and logged in with Wayland and it work but… only once. After I logged in I notice some flickering from my screen when playing with screen order or resolution but after setting 144hz on the 3 monitors and logging out that was it next login was a black screen. At this point it’s most likely a bug with nvidia drivers or Wayland.
Hope you don’t mind me piggybacking on your thread, but I’ve also been having the exact issue with my RTX3060 mobile that you’ve been having with Wayland on Plasma, and I noticed switching to 60hz. Doing that FINALLY gave me a usable desktop in Wayland.
…but honestly…this is NOT a solution. I have a 165hz monitor and I expect to be able to use 165hz. So great, I can get into Wayland…it’s useless to me if it’s only 60hz.
Obviously I need to post in the proper developer forums for Plasma, Wayland, and even Nvidia, but they gotta make sure this bug is ironed out before even beginning to think about removing X11 from future releases, At this point, that thought process is far too close to becoming a reality and it’s about to leave Nvidia users such as myself and the OP of this post behind. I don’t mean to sound dramatic and obviously there’s little Endeavour themselves can do about this, but there is a dramatic difference between 60hz and 165hz and if the future plans on having me tied to the former, I’ll move on.
Sorry for my delayed response - exactly what’s being discussed by all of you is what I faced. New profiles work fine for one login. But once the refresh rate is set above 60Hz - on re-login, no dice.
X11 works fine. Wayland is where things break.
I have three monitors - I believe multiple monitors may be a requirement for this situation.
I have not yet tried this:
Got a bit occupied with life, and then I somehow broke my entire EndeavourOS install doing something silly with system files. No big deal - was going to reinstall anyway, was just some experimentation.
@wil2197 I feel exactly the same way. I paid for a 120Hz-capable monitor, I want to use 120Hz. It’s a big deal and a critical aspect of why I even bought it.
I haven’t posted elsewhere except the EndeavourOS subreddit, linking to here. I suppose more of us should post this issue in the various mentioned places (especially Nvidia developer forum) to gain appropriate attention on this issue.
So are most of you using hybrid graphics while having this happen?
No in my case. The onboard graphic card is disabled in the bios. I don’t use it.
I see, for me I don’t have the black screen issue myself and I thought I was starting to see a pattern.
I have an intel CPU, but I’m not sure if the iGPU is disabled in the BIOS. I’m on a desktop and nothing is plugged into the motherboard port so I don’t think the iGPU is rendering anything.
I do have an Intel CPU on a desktop, but it’s a KF version, which means no iGPU.
You are correct @dizzydre21, if nothing is plugged into a DP or HDMI port on the motherboard, then your iGPU isn’t doing anything.
@d-air1 I’ve not had the black screen on my current (i.e. less than one month old) system - yet… But when I had a laptop with hybrid graphics similar to described here, it was frequently a pain.
I was having the same no signal black screen issue since Plasma 5 and finally fixed it by simply setting “nvidia_drm.fbdev=1” and “initcall_blacklist=simpledrm_platform_driver_init” alongside “nvidia_drm.modeset=1”. After doing this, it no longer gave the black screen and loads the desktop when selecting a Wayland session.
I don’t see that you or anyone has mentioned these, so maybe give that a try and see if it helps.
I also have a 120hz monitor with a couple of side monitors, one at 100hz and one at 60hz, and this fixed the issue for me, so there’s that similarity between our setups.
