Hello there. I’ve been having a frequent issue on my system running EndeavourOS with Plasma and Wayland where sometimes, when I boot, I get stuck with a black screen and just my cursor, before reaching SDDM. I am usually able to simply press Power once and it shutdowns cleanly, but I have to restart several times this way to get to a working boot. This used to happen maybe 50% of the time, but after I recently did a system upgrade and took a bit too long to get to it, it became even more frequent; I had to restart about seven times this morning.
I am generally able to reach other terminals when it fails, but I tried running startplasma-wayland to start Plasma manually as suggested online and it just freezes the machine completely (even the fans stop) until I force shutdown. Other than that, I haven’t really got a clue what to try. I’ve looked at other threads on this forum that seemed to mention similar issues but none of them seemed exactly applicable to my situation. It seems like this is a frequent symptom of a variety of issues?
Actually I just noticed you’re running a different kernel, the g14 kernel for the Asus laptop.
I had thought your system was not quite up-to-date because of kernel 7.0.5, but I see now that’s actually the current latest version of the g14 kernel (https://arch.asus-linux.org/).
It might we worth trying the standard, or LTS kernel all the same, to see if the issue is isolated to the g14 kernel.
Edit: I’d also suggest disabling the iGPU for now, if that’s possible in the BIOS. There is an error in the boot log pointing to some issues there, but I’m not sure if they’d cause the issue you’re facing or not.
Booting in linux-lts does seem to work consistently, thank you. I’ve just tried it three times and got to the login screen each time. I don’t know why I hadn’t tried that; I was sure I did. I tried the standard kernel too and it didn’t work, just like `g14`.
I’m not sure if I should just stick to lts or try to fix whatever is happening when I boot into the other two. I use `g14` simply because asus-linux’s resources recommend it for compatibility (this is an ASUS TUF A15 FA506QM laptop) without actually having ever noticed a difference, so it’s probably fine…? Still, do you have an idea what could be the cause, considering it works on LTS? If not, I’ll just mark as solved now.
Where do you see issues with the iGPU? I’m interested to know more, because I have noticed that `nvidia-smi` doesn’t show the iGPU and just shows all processes under my dGPU…
Mon May 25 14:17:59 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 595.71.05 Driver Version: 595.71.05 CUDA Version: 13.2 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 3060 ... Off | 00000000:01:00.0 Off | N/A |
| N/A 57C P8 9W / 90W | 37MiB / 6144MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 897 G /usr/lib/Xorg 2MiB |
| 0 N/A N/A 1943 C+G /usr/bin/python 4MiB |
+-----------------------------------------------------------------------------------------+
The two Asus laptops I look after (Rog and Zen), are both using LTS and Zen kernel. They’ve not had this issue yet. The system of mine that does have the issue is running an old Intel 7700K on (get this) an Asus TUF motherboard (desktop).
A curious coincidence
I’m not sure I’d make to much of the TUF thing though, there’s far more difference between the systems than similarities, I’d suspect.
It was actually this line in your working log that caught my notice:
mai 25 11:38:09 gb-eos2 kernel: amdgpu 0000:06:00.0: [drm] Failed to setup vendor infoframe on connector HDMI-A-1: -22
The reason being, it crops in in the working log, right where the failing log tripped up.
I’ve tried to look for a way to disable the iGPU in the BIOS but wasn’t able to find one… the NB or GFX Configuration options that people mention online aren’t present on my end.
I’ve not tried updating my BIOS yet, since it’s more delicate, but I’ll give it a go if it could be tied to this.
