Basically ninja’d by Stuart_MFrSu wrote: Tue Mar 15, 2022 4:50 pm @MXRobo: THX for your extensive information. I guess my system is from October 2019 as stated in the overview: Distro: MX-19.4_x64 patito feo October 21 2019
So the answer to my topic question is "YES". Because my system has an older kernel which does not automatically update and 21 does. Right?
@Stuart_M sorry, I did not read your post.
You're welcome.
Absolutely NOT, that is NOT my answer – but I’ll get to that in a minute.
RE: Distro: MX-19.4_x64 patito feo October 21 2019
I’m not sure what that means, first, I didn’t catch that, but I think I installed mine from 19.1 (doubtfully 19.2) and it reads February 15 2020 which isn’t that relatively close to what your date is. It may very well mean that.
________________________
Kernels 4.19 and 5.10 are (at least were, and I believe that are still) LTS (long term release) kernels which almost always receive automatic updates, but this was a rare unique situation where they did not.
Reread Stevo’s reply:
You and I originally installed a point release prior to the [“pivotal release” hypothetically say 19.2] , and we made “in-place” updates.Your system must have reached 19.4 through in-place updates instead of a fresh install to not have them--but I had the notion that MXPI was installing those 4.19 metapackages if you wanted the 4.19 kernel--this needs some research.
Say we originally installed MX19.0 , and then made “in-place” updates, from 19.0 to 19.1 to 19.2 to 19.3 to 19.4.
All of the in-place updates worked fine except for the 4.19 kernel, it remained stuck at 4.19.0-6-amd64 (Stuck @ 0-6)
Had we performed a fresh install of 19.3 (maybe 19.2, depending on what version started automatically updating again), then all of the in-place updates (to 19.4), including the kernels would have automatically updated as they should.
---------------------
The above may be incorrect as it could’ve depended on the kernel version (4.19.0-6-amd64, 0-6, 0-9, 0-12, etc.) as opposed to the MX point release, e.g. 19.2 or 19.3. - but I don’t think it really matters as the concept is similar.
--------------------
I, and many others are currenlty running MX19.4 fine, but you have a rare situation.
So, I’d suggest to try these three (3): (I made a typo or whatever in the previous reply)
1 - Open MX Package Installer (MXPI)>Popular Applications>Kernels
If 4.19 is NOT greyed-out (indicating that it is installed) just install (or reinstall), but I don’t think it will be.
Reboot, check kernel version in terminal with either uname -r or uname -a
it should be 4.19.0-19, at least 4.19.0-18.
2 - If it IS greyed-out: MXPI>Stable (or Synaptic P.M. - I believe) and install:
linux-image-4.19.0-19-amd64-unsigned
linux-headers-4.19.0-19-amd64
which should install: linux-image-4.19.0-19-common (Highlighted package>R-Click>more info – read it, it will tell if it will be installed.)
3 – This one can be done after doing one of the two above, I suggest the above in order to have an up to date 4.19 kernel to use if you have problems with the 5.10 kernel.
(If you system is fine, you don’t need the 5.10 kernel, but it probably work as good as the 4.19 kernel)
So option 3 is: MXPI>Popular Applications>Kernels and Install Debian 5.10 64 bit (latest)
It’s an LTS kernel also, which will get automatic updates, this should be fine.
You need the updates for security and bug fixes, you're way behind - I was behind in July of 2021!
Get in MXPI and just do it.
One last thought, I’d definitely update the 4.19 kernel for the obvious, to be up to date, but also, at the worst, you screw something up in 4.19, simply:
MXPI>Popular Applications>Kernels and Install Debian 5.10 64 bit (latest)
It will probably work fine.
HTH