After updating the system yesterday i got stuck in the “starting” screen after booting. I followed the instructions of this post: [FAQ] Computer doesn’t boot, boots to a black screen, or stops at a message
The first option did not help, the second option did nothing yesterday, but today it did. I used startx and x started. I tried changing display manager from lightdm to gdm and now i can get into the DE.
But it seems I have no graphics drivers, the resolution and aspect ratio is wrong, and from this command inxi -FAZ --no-host | eos-sendlog i got this: Graphics: Device-1: NVIDIA GA104 [GeForce RTX 3070] driver: N/A Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 driver: X: loaded: vesa unloaded: fbdev,modesetting gpu: N/A resolution: 1024x768~76Hz API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.7 256 bits)
I have tried using nvidia-inst several times, but it always gives the message “==> nvidia-installer-kernel-para: info: systemd-boot or grub not in use”
I fixed the driver issue by manually installing the nvidia drivers with pacman -S nvidia.
I still can’t get past the starting screen with lightdm as display manager, but using gdm works.
In order to understand what exactly broke your system, you should check your pacman log and see what happened during the last update procedure. My guess is it was not completed successfully, or with no errors.
About the display managers, you may have edited/created some Xsetup script for LightDM, which may need modification, or have some xorg.conf.d custom conf file.
How old is your system?
Could you post these logs ?
My system is about a little over a year and a half old, but i first used manjaro, and changed to endeavouros after about a month i think, so I’ve had this endeavouros a little under a year and a half.
About LightDM, you can check old journal logs (pointing to a lightdm-failed boot session), and/or lightdm log files, to see error messages.
Additionally, you can check if there is any Xsetup modified script (path is in lightdm.conf files).
I suspect this means that the plymouth module was not included in the kernel for some reason. (in mkinitcpio in MODULES array, and the equivalent for dracut).
Best check plymouth Archwiki article to confirm proper installation.