Conversation

Notices

1. Embed this notice
   INPC (mxtthxw@mxtthxw.art)'s status on Thursday, 29-Dec-2022 07:54:48 JST INPC

   This looks bad. I don't like the bit that says RIP.

   What do I do now?

   #AskFedi #Linux #RIP #Help #AskFreddy :freddy:

   • Embed this notice
     aab (aab@khp.ignorelist.com)'s status on Thursday, 29-Dec-2022 07:54:45 JST aab

     in reply to
     @mxtthxw Have you recently upgraded the kernel? Anyway, maybe booting with the previous one...
   • Embed this notice
     aab (aab@khp.ignorelist.com)'s status on Thursday, 29-Dec-2022 17:11:55 JST aab

     in reply to
     @mxtthxw Sure! If that works for you, then perfect. The new one will have security patches and "improvements" though (that, in your case, lead to a kernel panic).
     Knowing that a previous kernel works fine also gives you room to investigate; as someone has said before, sometimes the conflicted kernel can be "fixed" just adding parameters on grub.
   • Embed this notice
     INPC (mxtthxw@mxtthxw.art)'s status on Thursday, 29-Dec-2022 17:11:59 JST INPC

     in reply to

     • aab

     @aab Have managed to go back to the previous Kernal.

     Not sure what to do now, can I just keep going on the previous one?

   • Embed this notice
     aab (aab@khp.ignorelist.com)'s status on Thursday, 29-Dec-2022 18:15:36 JST aab

     in reply to
     @mxtthxw Just in case you don't know: if you are using Debian stable (I think I've read that in another post from you) you also have the option to use a backported kernel.
     They are also offered by Debian (no external sources needed), and they are more up-to-date that the ones in stable, so they could be the solution for your issue.
     Worth a try, as you can always go back to the kernel that works :)
   • Embed this notice
     INPC (mxtthxw@mxtthxw.art)'s status on Thursday, 29-Dec-2022 18:15:39 JST INPC

     in reply to

     • aab

     @aab Thanks, have cleared out some of the old kernals (boot disk was also nearly full). Will keep reading...