r/MXLinux • u/jupa300 • 6d ago
Help request Facing Kernel Panic error. Can't login to MXLinux
Any way to log into MX Linux as I updated my boot time to 0 second and I can't see my GRUb screen.
Using MX-25.3_Xfce_x64
Probable Reason: I beleive, the probable reason could be my upgrading of Deb Packages from MX Package Installer and I upgraded the Kernel from 6.12 Stable to 7.2.12
GRUB by default loads into latest kernel which shows Kernel Panic screen.
Any ways to fix? Or I will have to re-install the OS?
3
u/couriousLin 6d ago
Try holding the right-hand SHIFT key after you boot. This should override the 0 timeout.
2
u/tazman998 6d ago
You could boot from an MX Linux live usb and use the MX Boot Repair tool to see if that will get you back in.🤷🏼♂️
4
u/Admirable-Song-7353 5d ago
Guys, I feel myself as an outcast at this point, I'm using Linux for 5years straight now, and I never faced this kernel panic stuff, idk even how it looks, am I alone with this? I mean, not if I'm arguing, but I always think about myself as the most hacky person living on this person, always experimenting with the unthinkable, and still I'm experiencing this Debian rock solid vibes (but with MX since it's based on it).
🤷
3
u/pseudonym-161 5d ago
I only had it happen on Linux Mint of all distros, just a bad point release of an LTS kernel that didn't jive with something in my configuration. I never set grub timeout to 0 because I like having my options at boot (running both AHS and LTS kernels currently) so there's that too 🤷
2
u/Admirable-Song-7353 5d ago
Yeah same, I have all the kernels, currently using siductionn and liquorix, and keeping LTS if I have to fallback for a reason, which honestly never happened in the past. I feel siduction a bit better for cpu intense older games
3
u/Comfortable-Ad9468 6d ago
When computer is starting up, hold SHIFT key (or tap ESC). one of them should work
2
u/tce111 6d ago
I had this happen a couple weeks ago. Just reboot and in the grub menu you can select the older kernel. This worked for me. I was able to find a command to use to remove the faulty kernel and the problem was solved. Then I saw I had an update available and it was the new kernel which worked fine.
1
u/siamhie 6d ago
His timeout is set to 0. They don't get a grub screen.
2
u/adrian_mxlinux MX dev 6d ago
You can still get it, I think if you can hold Shift during startup on a BIOS system, or repeatedly tap Esc on a UEFI system to get the menu.
2
u/asoxone 6d ago
Have you tried holding shift down as you boot? https://unix.stackexchange.com/questions/219061/grub-boot-loader-set-timeout-0-how-to-get-the-boot-menu/732216#732216
2
u/Hot-Development-9036 6d ago
Yes holding down the Shift key should work. Once you are back in use MX Tools to create an image of your computer and then make a bootable image on an external drive. This works like a charm.
1
u/Admirable-Song-7353 5d ago
Press shift during boot (or actually anything works, I usually press arrow down and up in a quick fingering so if I get into mx menu grub it wont slip over) pick a older kernel and once you're in set back your grub timer to 5, so next time you don't have to do the quick fingering stuff
1
u/cloudberri 5d ago
Something might be off here. I've run into a kernel oops running 6.1.0-55-amd64. I can barely remember the last time I had to deal with this sort of thing. So far, rolling back to an older kernel is helping.
1
5
u/Scared_Hedgehog_7556 6d ago
Use live distribution of mx and you can choose which one to boot and then probably change grub settings