I installed EndeavourOS with the MATE desktop, choosing auto-login and encryption in the installer. Now when system boots I get a blank screen as soon as I see the messages about lightdm starting. Switching to other ttys doesn’t seem to work, so I have to power off.
If I disable the lightdm service with systemctl, linux boots normally in text mode, then I login and type “systemctl start lightdm” to start the dm manually and it works. But if I reenable the service and reboot, I get the blank screen again.
Any idea what could be the problem? This is an amd 4700u (vga 7) laptop so maybe its igpu is not well supported yet?
EDIT: I have also tried with the slim DM but I get the same result
It sounds strange: But do you have the possibility to connect another monitor for testing?
I had the same problem and it was on my monitor (Terra LCD). Different monitor, and everything worked…
I’ve already tried with the slim display manager, but the problem remains.
However if I disable lightdm and start the lightdm service manually with systemctl, it starts and I can see the desktop. I also see an amdgpu error in dmesg: “failed to add display topology” but since the desktop works if started manually I don’t understand where the issue is.
EDIT: it seems other distros have similar problems with this laptop.
Would be great to explain the all start of your bug in spite to open threads everywhere maybe it would help us more in giving us the information we need !
I opened 2 threads because they were 2 different problems: first the partitioning in the installer, which I marked as solved, and now the display manager, which prevents me from using the desktop. If you feel 2 threads are too much for this forum feel free to delete them.
It’s not the way of EndeavourOS to delete threads but if you want us to help you correctly, give us the information and feedback from our help, it will work better…
I think you misunderstood @FLVAL, don’t forget that this forum is used by an international community who don’t have English as their first language. Sometimes things can get lost in translation.
What FLVAL meant is that in this particular thread your hardware specs weren’t shown, which is much easier for the community to help you further. It is in no way be meant as an imposition from our side, not everybody reads every thread, most users will open a thread if they think they can offer help on the matter and if your first thread isn’t in their level of help they wont open and read it.
There are a few sections there might be useful, e.g. “LightDM does not appear or monitor only displays TTY output” and “Long pause before LightDM shows up when home is encrypted”
I thought too. But Mate is too slow to move now and some things are not implemented for years like using gnomeweather instead of libmateweather for example.
That’s why I went with MATE: slow pace = stability As a GNOME devotee, I spent way too much time reporting bugs and fixing inconsistencies after updates, not to mention those javascript bindings (memory leaks and so on…)
As a GNOME devotee, I spent way too much time reporting bugs and fixing inconsistencies after updates, not to mention those javascript bindings (memory leaks and so on…)