this post was submitted on 03 Dec 2024
24 points (92.9% liked)

Linux

8310 readers
177 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
 

Hi guys! I have KDE Neon 6.2.3 running on my Surface Pro 7+, and up until now it's been running rather smoothly, for years. But today I seem to be unable to fully boot anymore on normal mode. Linux will get stuck on the KDE spinning gear, with the gear frozen. And it becomes unresponsive, to open alternative consoles with control+alt+Fx, or even control+alt+del. The only thing that works is a force shutdown by holding the power button.

I tried with a previous kernel, with the same results (current is linux-image-6.10.10-surface-1, I have a generic 6.8.0-49, but it also freezes). I can boot in safe mode. It opens a different login screen, and after a failed attempt of opening lxde, it fails back to my usual KDE session, in safe graphics mode.

What can I test? How can I see what failed at boot?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 3 weeks ago (1 children)

All I can see in that is that your machine has an LTE SIM slot and that the LTE Modem isn't supported. That shouldn't stop you from booting.

[–] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Yeah...It looks to me like it just says it went alright, right until I hit the poweroff button, because it's actually completely crashed.

Just an update. Today I made a rescuezilla full backup of the whole drive, and then wiped and installed KDE Neon brand new from Dec 1st release from their page. Guess what...that one ALSO fails to boot.

[–] [email protected] 2 points 2 weeks ago (1 children)

If a clean install also fails then I would start considering hardware fault.
You could always check if you can boot Fedora Workstation with GNOME just in case but I think you should start looking for a replacement PC.

[–] [email protected] 1 points 2 weeks ago (1 children)

I actually clicked on the replace partition option on the installer, instead of a full disk wipe. The profile did look brand new once I managed to login in safe mode, but I didn't stay too long to check, as I just concluded hell, if it only boots in safe mode I might as well continue troubleshooting on the original install.

Anyway...After going back to the original image (as I had it backed up anyway), I paid a bit more attention at that weird popup on safe mode as I logged in, mentioning it failed to launch startlxde. So I ran

sudo dpkg --reconfigure sddm

And on the menu, for some reason sddm wasn't the first choice. After choosing it again, this time it went straight to the boot screen. Some other day I'll check again whichever random login menu is installed, and remove it, as it clearly causes issues.

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

Sweet, then you know what's going on and solved it!

You might wanna try out if your distro is compatible with cockpit:
https://cockpit-project.org/
https://github.com/cockpit-project/cockpit

It gives you a webUI that you can use to check out logs and services (among other things) and makes it a lot easier to troubleshoot computer troubles where the machine starts but your GUI doesn't.