I’m facing an issue with booting into KDE Plasma on Arch Linux. When I boot the system, it takes me to a black screen with a blinking cursor. The mouse can move, but I can’t interact with anything, and the keyboard seems to be working physically but not responding software-wise. I’ve tried a few things, but nothing has resolved the issue so far.
Here’s what I’ve tried:
Replaced quiet with several boot parameters (like acpi=off, nomodeset, and acpi_osi=Linux) in GRUB, but this still leads to the black screen.
Booted into a console and checked logs, but no clear solution has emerged.
Tried various keyboard shortcuts to switch consoles and troubleshoot, but the system remains unresponsive.
Switched to the fallback initramfs (single-user mode) but encountered the same problem.
Has anyone else experienced this? If so, how did you fix it? Any advice or suggestions would be greatly appreciated.
 in SDDM. Actually, this has happened more than once. After some time/updates, it was always fixed.
If indeed the problem occurs when you try to log in with SDDM, try changing to X11, this always worked for me as temporary fix.
No, the error happens before SSDDM where the boot splash screen should appear.
I think knowing the errors should help so
Errors I found when running journalctl -p 3 -x:
Error 1: SGX disabled or unsupported by BIOS
Error 2: ACPI Errors (Could not resolve symbol, AE_NOT_FOUND)
Error 3: integrity: Problem loading X.509 certificate
UPDATE: I have found a way to bypass the usual boot by spamming f2 and now i can select which device I want
I’m going to go to the usb flash drive boot and see what I can config from there
Update: it didnt work as when I tried to do a restart from the lonovo eufi it starting spamming pop ups and lenovo was trying to fight grub and now I cant even acess the usb flash drive boot and I genuinly don’t know what to do now
To best focus what guidance folks may think of - can you describe, in the state that the system is in now, exactly what happens when you power it on from a powered-off state?
Basically, what exactly do you see when the display first comes on, what messages appear as it’s starting up, and what does it look like when it’s “done” starting up?
When you tried to do a restart from the Lenovo UEFI - what specific option did you choose, and what messages did it show you?
(Less urgent things below, separate from trying to get your current installation back up and running!)
If I can offer a thought - others may disagree and have valid reason for doing so, but in my opinion Arch Linux is a very tricky choice for your overall introduction to Linux. To build that initial familiarity, I would personally recommend a distribution that offers built-in assistance with getting a system up and running, and that has a bit of orientation toward “user-friendliness”.
On the other hand, Arch is “intended to fill the needs of those contributing to it, rather than trying to appeal to as many users as possible. It is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems.” The project’s FAQ about Linux beginners isn’t explicitly discouraging, but does make it clear that it requires a lot of work from the user that wouldn’t necessarily be required elsewhere.
Arch enthusiasts value that choices aren’t made for them, but as an…intermediate?..user, I personally get a ton of benefit from the thoughtful decisions that go into assembling a more “curated” operating system (like the Ubuntus, Fedoras, etc. of the world).
I first of all just wanted to say that after basically a day of trying to config it to work it did but I can’t say the same for everyone as I think this is more lenovo based as when I sent eufi lenovo it had the option to restart the boot and it worked and I took advice from skyfishgoo to install something that helps me go back before the error happened in the first place and then try and fix what’s wrong before it happens
Now for the your personal advice, look I’ve been and tried ubunto and fedora and it’s just not for me and my best way to learn something new is to dive into it
You think I knew how to install arch? Hell naw I went there head first and after a week I came out done with all the new knowledge in my head I have resorted to asking here as a last resort after trying to do it myself (and I barely did anything as I haven’t dived head first before) but now I did and even without help from here managed to reboot it, so no, I’m sticking with arch even though it’s painfil because I like that I control the computer and not someone else I like how I can do everything by myself exactly the way I like it withought some company controlling and limiting my customization
Also unrelated note: may I ask why you have leader under your name? Are you the head of kde support?
And I’m glad you found a Linux experience that fits what you’re looking for - sorry, I had thought from just those few initial posts that you might be in a “ugh, I’m stuck in something I hate” situation, and that maybe other paths might help you get unstuck. But if building it yourself, getting stuck along the way, and then figuring your way out is part of the fun - rock on
On the “Leader” badge, that’s the Discourse title for its “trust level 4” - I’m definitely not the head of anything, but based on being around the community for long enough and having what I hope is a good history of positive contributions, I do have access to some tools to help out around the forums a little more (like moving topics to a better fitting category, assigning tags to posts to help them be found more easily, or closing/merging topics when needed).
