this post was submitted on 28 Oct 2025
502 points (98.5% liked)
Linux Memes
996 readers
1 users here now
A community for posting memes relating to linux!
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No clue how to fix it. I had a similar issue and it fixed itself when I switched to endeavouros with i3.
Ok, thank you for the feedback still. You were able to install a different OS and boot into it normally?
~~Yes, it was only after grub that the drivers were loaded and the kernel presumably panicked or at least nothing was displayed. Not sure if that is what you mean by bricked the entire workstation. If something broke before the kernel is loaded I doubt it was because of the drivers. If you want to keep your current Debian installation alive you can try to
chrootinto it from a live usb. Sorry if this is completely obvious to you but I really don't know what to expect based on your description.~~Having looked at your other comments and the post you linked I too am intimidated. It looks as though you have access to your boot menu and bios though. I don't know what the upsides of secure boot are but I never turned it on on my current desktop PC. Maybe disabling it could help?
Thanks for the suggestion, I disabled it and it boots again! a few people suggested the same, and I asked them in return how important they think secureboot is. It's not very clear to me because if I have to toggle it on again, it means I have to solve that MOK key thing I just inflicted on myself. And I'm not clear on how
Thanks again
😊