6
« Last post by sorveltaja on March 24, 2026, 02:44:42 PM »
Yesterday, when I updated my Debian 13 installation, using commands 'sudo apt update' and 'sudo apt upgrade', it went well without errors.
But when I rebooted the system - it booted only to tty(no gui, command line mode).
It appears that the new kernel 6.12.74+deb13+1-amd64 might have caused this issue.
But in the boot screen, when selecting advanced options, one can see what kernels are installed. In this case I chose the older one, 6.12.73+deb13-amd64, and it booted just fine, as it used to previously.
So, one option to get back to the OS, is to set the old kernel as a default, when booting, instead of new one.
I'm not quite sure, if this is the only way to do so, but anyway, I edited grub:
GRUB_DEFAULT=saved -- previously that value was 0
GRUB_SAVEDEFAULT=true -- this line is a new addition
Now, when selecting that old kernel when booting, it *should* stay that way. At least it seems to do so in my case.
It's bugger when things like that happen - of course there is an option to use the installation media to access recovery mode, but I find it to be cryptic, especially when I had no idea, that the issue wasn't necessarily about existing hardware drivers, but possibly about new kernel conflicting with some of them.
In the end, I tried several things from different sources to fix the failed, updated kernel, but meh, I rather keep on using the old one.
What kind of precautions there might be, just in case that this happens again, when trying to update the system? Make a backup every time before attempting such?