I have EndeavourOS installed on my X200S. When I power it on it gets past “Welcome to EndeavourOS” but gets stuck around
Starting Bluetooth service…
Or
Starting Network Manager…
I believe it got stuck on a few other spots previously but I can’t recall where. The “Drive in use” indicator light stops flashing at this point. At that point the only option as far as I can tell is to press the power button.
I can boot from a USB drive without any issues.
I had updated my computer but I believe I was believe I did a successful reboot after that.
Any suggestions? I can’t seem to find a solution online. A lot of the support pages end with them giving up and reinstalling EndeavourOS.
Solution:
My X200S runs Libreboot and apparently that has issues with the current Linux kernel. I created a bootable EndeavourOS USB unlocked the LUKS drive with sudo cryptsetup luksOpen /dev/sda1/unlockedFolder. Mounted it with sudo mount /dev/mapper/unlockedFolder /mnt. Ran arch-chroot /mnt so I could gain access to the OS. Switched to the LTS kernel using sudo pacman -S linux-lts and edited the grub files to add the -lts.
I originally tried just downgrading the kernel but it caused my WiFi not to work.
The whole issue was quite strange because it would freeze at random parts and even successfully boot at times.
Endeavour uses systemd, which means a lot of your services try to start after network.target. boot into a live USB and take a look around /etc/systems/system for problematic services.
Is there a way to tell what might be the issue?
I see folders like bluetooth.target.wants and network-online.target.wants and they contain .service files. I feel like this is probably what I’m after.
I wonder if it’s an issue with Mullvad blocking network connections.
I tried disabling the network manager and Bluetooth through arch-croot but now it’s freezing at