Linux
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:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Thanks. I pulled the journalctl. This is...A bit extensive. EDIT: Well seems I only can see the KDE logo and a frozen gear, but according to systemctl the system is up and running, and the network connected? After 7 seconds frozen I give up once more and hold power button, since this is the only thing it seems to react to, and yet, even this gets logged onto journalctl.
You need to specify the -b switch or you're just looking at logs for the current session. Something like
journalctl -xe -b 1
should do the trick.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.
OK so just to confirm: you get a boot freeze even on a fresh install before you restore a backup?
Are you able to boot a liveusb?
I would try another distro just to rule out a software problem but it sounds like hardware failure. I would test your ram, graphics card, and storage medium. Do you have an SSD or an HDD?