MX Linux Forum

figueroa wrote: Wed Dec 13, 2023 3:31 pm If 6.1.0.15 is the problem child, and I'm on 6.1.0.13 (bog standard MX-23 xfce4 up-to-date) whey is the updater still offering to upgrade to:

Code: Select all

linux-image-6.1.0-15-amd64 (6.1.66-1)

even when the repo is set to the Salt Lake City location? Shouldn't it be blacklisted?

comes from debian, not MX. We would have removed the offending kernel (and in fact have removed ones that had the issue that we did supply) but debian has chosen to leave it up. which is dumb, but not our servers.

you can remove the linux-image-amd64 and linux-headers-amd64 packages and the update will not be offered. I will be posting when the next kernel is ready, which should be pretty soon.

Thank's @dolphin_oracle. What I chose to do in the short term was to do a basic upgrade (not full-upgrade) through the command-line, since there were many other package upgrades to make. Just doing "apt-get upgrade" held back the kernel and header. I'll watch carefully and avoid updating kernel and header till Debian to stabilize the next version.

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.

SimplyFojin wrote: Thu Dec 14, 2023 12:40 am

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.

Depending on what version(s) you have purged, you *should ReInstall* the metapackages in any scenario, to get the next releases offered by 'apt update' or MXPI, IMO.

See this last (asof: 2023/12/14 - 07:00) posting on the bugtracker: https://bugs.debian.org/cgi-bin/bugrepo ... 1057843#98

Finally, I wanted to note: if you did `apt purge linux-image-6.1.0-14-amd64`, you might need to `apt install linux-image-amd64` (the meta package) before you can successfully pick up the new linux-image-6.1.0-15-amd64 automatically as a dependency (say, when doing apt update; apt dist-upgrade). At least, I needed to, as I think the purge automatically removed the meta package, leaving me with no *automatic* upgrade to the new kernel via those commands.

Good luck!

Also - in this posting, he gives some hints on howto check for possible files data corruption

SimplyFojin wrote: Thu Dec 14, 2023 12:40 am 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.

For this very reason you need to remove /purge that. Cause it will keep last two and install the new one (totally 3 kernels). At least till you feel/see/learn it's ok with the new released (Debian, default) kernel (whatever it is ...-17 , ...-18 etc..).. then you can simply install back the metapackages (as above or with MXPI) and let it install that new kernel etc. and go on auto-installation/removal as before ...

In case you want particularly (and to always) keep the -10 and/or -13 (for whatever reason), then you need to "apt-mark hold" them.

Same - doesn't connect to wifi and crashes soon after. Using 6.1.0-13 works just fine though. Also it hangs on shutdown when trying to stop the network processes. Should I make a separate topic? They seem exactly alike.

Just make the -13 default with "MX Boot Options" - "Boot to", at least till the "proven to be non-buggy" release is announced (whatever: -16 or -17 ...), then you can happily remove the -14 and -15 ..

(Or just remove them now (MX Cleanup is simple to use for this) and also the metapackages to prevent their reinstallation as an update)

Let's just hope Debian gets out kernel 6.1.67 = 6.1.0-16 soon and also let's hope it doesn't introduce another nasty problem. Debian had enough going wrong in the last few days....

6.1.0-15 runs fine on my machine, but that is probably only because I don't use any wifi hardware. I had 6.1.0-14 running for one day, but since the file system corruption actually happens only with very special programs (i.e. usually database software), my system (and most desktop systems) shouldn't be affected.

For now, staying on 6.1.0-13 is surely the safest option.

Thanks! Done! I wish I had checked the forums (on another computer) - or thought to use Kernel -13 a while ago. I have been trying to troubleshoot this for hours and installed the old wifi driver to no success.

The weird thing is that things were working with my old TP-link TN-WN822N, and stopped working I think when I tried to install the old driver for my main wifi adapter and tried to switch to it. Then it just kept failing to accept my wifi password and would eventually freeze.

Ah well I guess probably not too important but maybe it is somehow useful - especially that using that was working - and it wasn't crashing!

EDIT - do you think that the fact that I had to manually power off my computer by holding the power button so many times could have damaged anything? Are there any commands or anything I can do to help restore the filesystem if any thing was damaged?

Kernel 6.1.67 = 6.1.0-16 is now offered in the MX-Package Installer.