techsupport

2439 readers

23 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Software gore

Recommendations

founded 1 year ago

MODERATORS

GatoB

[Solved!] EndeavourOS freezing during boot process. Any idea on how to proceed? (leminal.space)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/techsupport

5 comments fedilink hide all child comments

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...

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.

you are viewing a single comment's thread
view the rest of the comments

[–] pete_the_cat 2 points 2 months ago (1 children)

Increase the boot verbosity or boot it up in single user mode and inspect the boot log to see if you can spot the issue.

[–] [email protected] 2 points 2 months ago

Thanks that got me to the solution