MX Linux Forum

If you do the fsck / e2fsck / GParted on live session with an official iso (as suggested above):

The kernel is 6.1.0.10 (on MX-23) and 6.1.0.13 (on MX-23.1) or other non-buggy ones with previous releases.


Luckily after I updated today, 6.1.0-13 and -10 are still there. Even though 6.1.0-16 ...

Stevo wrote: Wed Dec 13, 2023 2:04 am Removing the metapackages stops the upgrades without removing the actual kernel and headers, which can become a terrible, horrible, no good, very bad thing.

So I shouldn't do anything? I'm concerned when theirs a new kernel update that 6.1.0.13 and 6.1.0.10 will be deleted.

They are just packages. You can use any package manager.


I think what I'm trying to convey, isn't there a terminal command to remove both packages safely?


sudo apt remove linux-image-amd64 linux-headers-amd64


How is that different from Charlie Browns method? I want to make sure which ...

dolphin_oracle wrote: Mon Dec 11, 2023 5:04 pm They are just packages. You can use any package manager.

I think what I'm trying to convey, isn't there a terminal command to remove both packages safely?

dolphin_oracle wrote: Mon Dec 11, 2023 4:54 pm Nope. They are just meta packages. They bring in the new kernels when they’re available.

I see. However I don't understand how to properly remove them and whenever this issue is solved download them again.

quite a lot of bug report action on the debian bugtracker about the 6.1.0-15 kernel. apparently a commit was imported from upstream that had already been reverted in elsewhere. the commit dealing with cfg80211, which certainly relates to wifi.


FYI, I recently got a new update from MX ...

quite a lot of bug report action on the debian bugtracker about the 6.1.0-15 kernel. apparently a commit was imported from upstream that had already been reverted in elsewhere. the commit dealing with cfg80211, which certainly relates to wifi.


FYI, I recently got a new update from MX Updater ...

nothing jumping out at me.

the dpkg --configure -a command, if it didn't' return any output, would indicate the updates are complete at least. that would still leave the question of why the -15 kernel doesn't work correctly,but at least you would know the updates were complete.


Updates were ...

FWIW, the 6.1.0-13 kernels are still in the debian repo and accessible.


What about history in package manager? This is what I spotted today.

2023-12-10 12:09:36 upgrade system-keyboard-qt amd64 23.12.01mx23 23.12.02mx23
2023-12-10 12:09:35 upgrade quick-system-info-gui amd64 23.09.01 23.12 ...

login seems to be OK. I'm running the kernel now.

Is that all I have to do, try to log in?


Makes me thinking next time I reboot my computer is just go into 6.1.0.13 instead. I wonder if its still a risk for me to continue using 6.1.0.14.


the risk was apparently ext4 file system ...