linux kernel 6.1.0.15 causing crashes in mx linux 23.1 flagship Xfce edition?

[Charlie Brown]

• Code: Select all

  sudo apt purge linux-image-amd64 linux-headers-amd64 -y

• Code: Select all

  sudo apt update ; sudo apt install linux-image-amd64 linux-headers-amd64 -y

[dolphin_oracle]

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

[Charlie Brown]

In the meantime, my second command was for this one:

...and whenever this issue is solved download them again.

:)

(Not to apply them successively)

[SimplyFojin]

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 way is effective for not screwing up my computer.

[oops]

The 6.1.64 (6.1.0-14) kernel was replaced by 6.1.66 in Debian Bookworm. All those other updates were pushed as part of the 12.2 to 12.3 Bookworm point release. Those point releases happen on a regular schedule ~every two months.

Right, ext issue "iomap: update ki_pos a little later in iomap_dio_complete " was fixed with 6.1.66 = (deb 6.1.0-15) (also for k6.6.5) ... and the wifi issue "Revert "wifi: cfg80211: fix CQM for non-range use" was fixed with 6.1.67 (deb 6.1.0-16) (also for k 6.6.6) ... so that should be OK now (not only Debian kernels was affected, but a lot of distribs) . So should be OK now with 6.1.67 (deb 6.1.0-16) (also with k6.6.6).

[oops]

doublon

[Charlie Brown]

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 way is effective for not screwing up my computer.

Removing a package removes all packaged data, but leaves usually small (modified) user
configuration files behind, in case the remove was an accident. Just issuing an
installation request for the accidentally removed package will restore its function as
before in that case. On the other hand you can get rid of these leftovers by calling
purge even on already removed packages. Note that this does not affect any data or
configuration stored in your home directory.

remove
remove is identical to install except that packages are removed instead of installed.
Note that removing a package leaves its configuration files on the system...

purge
purge is identical to remove except that packages are removed and purged (any
configuration files are deleted too).

Remove is softer, you can use that one.

[Stevo]

linux-image-amd64 and linux-headers-amd64 are the amd64 stock kernel and header metapackages, not the actual kernel and headers. They are built at the same time as the latest kernel, and will depend on that same version, which, as of now, is 6.1.0-16 for Bookworm, (6.1.67 kernel source). When a new stock kernel becomes available in the repos, a new set of metapackages in the repos will become an upgrade, which in turn pulls the new matching kernel and headers. Removing the metapackages stops the upgrades without removing the actual kernel and headers, which can become a terrible, horrible, no good, very bad thing.

[Charlie Brown]

@Stevo Thank you for the best explanation I've read so far. Bookmarked your post for future reference :)

(Btw. then we can also say "nothing to be afraid of purging" , in this case).

[figueroa]

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) why 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?