previous kernel boot option disappeared

vyzle

Hi all,
I'm such a noob I cant stop 'fixing' things.

I tried a 'sudo snap refresh' and the terminal stopped responding. Didn't return to command prompt on CTRL+c.
So I followed help from here...
https://discuss.getsol.us/d/1800-snap-software-are-not-working
no joy, so tried this...
https://discuss.getsol.us/d/1517-snap-apps-not-running-why-does-this-still-happen/2

Rebooted, Snaps now work fine but noticed the previous kernel entry had disappeared leaving only the current one. I don't have UEFI bios and boot is via grub. Boots fine but having the previous kernel made me feel safe as it's come in handy before.

i did 'sudo clr-boot-manager list-kernels' and there is only the current - com.solus-project.current.5.6.18-156

Any way I can restore the previous kernel as an option, but keep booting into the current one?

thanks all!!

DataDrake

clr-boot-manager is supposed to keep the two most-recent versions around, but there's a bug that I haven't been able to isolate where sometimes the second kernel gets removed. If your boot partition is large enough (>250MB Solus-only, > 500MB shared), I would suggest installing the linux-lts kernel package as a more reliable back-up option.

vyzle

Thanks @DataDrake.

I'm pretty sure I only ran the apparmor and usysconf commands mentioned in the links above, so hopefully maybe that could be helpful in locating the bug? I know nothing so I'll shut up.

I'll try the LTS advice as although Solus is super stable, it's nice to have a safety net.
cheers!

DataDrake

vyzle usysconf will run clr-boot-manager which can cause it, I just don't know why it's happening inside of clr-boot-manager is all.

vyzle

DataDrake
I'd offer to help but last bit of debugging I did was in BASIC on a zx81.
anyhow, you're doing an amazing job!!