MX Linux Forum

Hello,
similar to this topic my laptop lenovo T470 does not boot after the last update.

This message occurred: The message that follows is the same as in the post mentioned above and after entering "exit" again the same message mentioned there.

May be the reason is the lack of zstd, which is obviously necessary now.

How can I boot my computer with AVLinux? At the moment I can only boot Kali from an USB-Stick.

Thank you for your help!

P.S.: I discovered that I can boot with an older kernel, so the acute problem is solved.

I think the answer for AV Linux 21.3 (Bullseye-based) is as stated in the other thread is to not go further than 6.6.8.2..

We need to remember that MX-21 (AVL-MXE-21) are all on Debian oldstable now, upstream folks like Liquorix aren't making any decisions on what may happen to oldstable users if they make big changes like that. Unless you have a known security issue to fix there is really no reason to constantly update Kernels especially on a production workstation, if the Kernel the OS installed with supports the hardware and gives good performance you're good to go. Updating the Kernel for no reason is always a roll of the dice, at the absolutely ridiculous pace of Kernel development now regressions are becoming more and more common.

This is the reason that AVL-MXE doesn't have the Kernel meta-packages installed to force constant updates..

If this is relevant, or helps, and I'm using MX-21.3 Xfce:

The 6.6.9-1 kernel (and the last one installed automatically with liquorix kernel metapackages) ran fine on my daily driver; the others either were not updated for some time, or I were previously running on an ahs non-liquorix kernel.
The 6.6.10-3 kernel does not work on MX-21.3 for me.

From: viewtopic.php?p=760963#p760963

Cheers!

Niko wrote: Thu Jan 11, 2024 8:16 am How can I boot my computer with AVLinux? At the moment I can only boot Kali from an USB-Stick.

P.S.: I discovered that I can boot with an older kernel, so the acute problem is solved.

Yes, with kernel upgrade, you would always have at least the kernel running during upgrade available as boot options within the GRUB menu. So not really something to worry, except wait until the new kernel issue is fixed.
Until a newer kernel comes along or another fix to solve the issue with the non-working kernel, you can make within MX Boot Options, the last working kernel as default pre-selected within GRUB menu.

Thanks for the informative comments!
Since I had never used an old kernel before, I only had the idea of using one after a delay.

In the meantime the kernel was updated: linux-headers-6.6.11-1-liquorix-amd64
Now everything works fine.