EndeavourOS occasionally hangs on boot

Can you try to install something like lightdm and see if the issue persists using that? Because for me in the past sddm always as been a little bit “unpredictable” let’s say.

Will do - or try to. It seems Lightdm refuses to work on this system.

pacman -S lightdm systemctl enable lightdm.service -f

After running this I noticed it replaced display-manager.service.

░░ The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
Jul 05 09:11:26 humppakone systemd[1]: Failed to start Light Display Manager.
░░ Subject: A start job for unit lightdm.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit lightdm.service has finished with a failure.
░░ 
░░ The job identifier is 1582 and the job result is failed.
Jul 05 09:11:27 humppakone systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Automatic restarting of the unit lightdm.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 05 09:11:27 humppakone systemd[1]: Stopped Light Display Manager.
░░ Subject: A stop job for unit lightdm.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit lightdm.service has finished.
░░ 
░░ The job identifier is 1678 and the job result is done.
Jul 05 09:11:27 humppakone systemd[1]: lightdm.service: Start request repeated too quickly.
Jul 05 09:11:27 humppakone systemd[1]: lightdm.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit lightdm.service has entered the 'failed' state with result 'exit-code'.
Jul 05 09:11:27 humppakone systemd[1]: Failed to start Light Display Manager.
░░ Subject: A start job for unit lightdm.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit lightdm.service has finished with a failure.
░░ 
░░ The job identifier is 1678 and the job result is failed.

Maybe stupid question: have you disabled sddm first? (I saw the -f flag but for my experience sometimes it doesn’t works)
Have you also tried to start your DE without DM but using only xinit? If not follow this https://wiki.archlinux.org/title/KDE#Starting_Plasma
and choose x11 or Wayland accordingly. Then disable all DM, reboot you system and after login
startx
to start the graphic environment.

If you are using plasma sddm is the way to go.

Arch is too fast! I had this issue on a very minimal Debian installation and the GDM would not ever show the Wayland option until I did early KMS for the radeon driver.

I had a lot of issues with booting up EOS without KDE/SDDM or something else crashing, at one point I couldn’t even complete the boot process. The solution was to:

  1. Add radeonmodule to initramfs (/etc/mkinitcpio.conf) for early KMS.
  2. Explicitly set to use radeon in /etc/default/grub with radeon.modeset=1

Now all my problems have gone away. Phew! :relieved: