Automatically updated kernels for MX23.3 with KDE [Solved]

[ornithorhynchus]

Hi people,

I'm trying to get a handle on which kernels in a MX23.3 KDE system automatically get updated. Can you please tell me if what I've written below is correct?

For MX23.3 with KDE the only installation I could install from today's download page that's part of the automatic kernel update system is MX-23.3_x64 KDE, with the 6.1 kernel. If I was to install another MX kernel into this installation - say Liquorix 6.7.12-1 - it wouldn't be part of the automatic update system. But I could update to a Debian kernel, say 6.6.11 64 bit AHS, which would be part of the automatic kernel update system because it's AHS.

I believe I need to make sure whatever kernel I have does get automatically updated - for security reasons as well as for work-ability.

Here's my Quick System Info.

Code: Select all

System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.3_KDE_x64 Libretto
    July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: Z390 D v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F3c date: 12/18/2019
CPU:
  Info: model: Intel Core i5-9400F bits: 64 type: MCP arch: Coffee Lake gen: core 9 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
    microcode: 0xF4
  Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB
    L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 800 min/max: 800/4100 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 bogomips: 34798
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ASUSTeK driver: nvidia v: 470.239.06 non-free:
    series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Fermi 2 code: GF119/GK208
    process: TSMC 28nm built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 01:00.0
    chip-ID: 10de:128b class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.02x10.71") s-diag: 554mm (21.82")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
    diag: 547mm (21.54") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 470.239.06 renderer: NVIDIA GeForce GT 710/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:0e0f class-ID: 0403
  API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 894.28 GiB used: 255.88 GiB (28.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: B1E1 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: B1E1 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: B1E1 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: B1E1 scheme: GPT
Partition:
  ID-1: / raw-size: 107.19 GiB size: 104.95 GiB (97.91%) used: 18.04 GiB (17.2%) fs: ext4
    dev: /dev/sdc2 maj-min: 8:34
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sdc1 maj-min: 8:33
  ID-3: /home raw-size: 116.12 GiB size: 113.74 GiB (97.95%) used: 16.89 GiB (14.8%) fs: ext4
    dev: /dev/sdc3 maj-min: 8:35
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 25.0 C pch: 30.0 C mobo: N/A gpu: nvidia temp: 43 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2947 pm: dpkg pkgs: 2946 libs: 1638 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 1
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://debian.mirror.digitalpacific.com.au/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://debian.mirror.digitalpacific.com.au/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.datamossa.io/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.datamossa.io/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 233 Uptime: 5h 19m wakeups: 1 Memory: 15.55 GiB used: 1.85 GiB (11.9%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Have I got it right please?

Thanks and Cheers.

[dolphin_oracle]

there are two paths to automatic kernel updates.

linux-image-amd64 metapackage, which pulls in debian's stable kernel, currently a 6.1 kernel. there is also linux-image-i686-pae for our 32 bit users.

linux-image-liquorix-amd64 metapackage, which will pull in whatever the latest liquorix kernel is. this package is in ahs.

there are easy entries for both in mx-packageinstaller -> popular apps-> kernels.


the early versions of mx23-kde were missing the debian linux-image-amd64 metapackage (and the linux-headers-amd64 metapackage). So you probably need to install the them to get updates. the 6.1 kernel is up to 6.1.0-21.

[DukeComposed]

I believe I need to make sure whatever kernel I have does get automatically updated - for security reasons as well as for work-ability.

Keep in mind how apt-get understands when a package update is available.

If apt-get knows you have a package named "foo" installed, then it knows that foo is at, say, version 1.2. When you run "apt-get update", apt-get contacts the package repos and checks if there's a new version of foo. If a new foo package with version 1.3 shows up, apt-get notices and marks it as an upgradable package.

If the package is named "linux-image-6.7.12-1-liquorix-amd64", there will never be a newer version of that package. That means apt-get will never update it.

What you need to look for in cases like this are metapackages. Metapackages are Debian packages that don't actually contain the software. Instead, they tell apt-get which packages to check to get the software you want. Linux kernels are handled by the metapackages called "linux-image-amd64" and "linux-headers-amd64". Neither of these packages will give you a kernel. They will give you the name and version of the latest kernel, and apt-get will find and install that instead.

[ornithorhynchus]

@dolphin_oracle

@DukeComposed

Thanks for your comments. Much appreciated.

You can see from my Quick System Info that I'm using the 6.1.0-10-amd64 kernel.

Here's what my Package Installer says:



I downloaded Liquorix 6.5.11.3 but I haven't begun to use it yet. It's an option in the screen in MX Boot Options:



That image shows I've also downloaded AVLMX. I boot it when I want to work with audio. I installed AVLMX after I'd installed MX23.

Here's what the Advanced options show for MX 23 when I boot to it:



It doesn't show Liquorix 6.5.11.3. Maybe that's because it was AVMX that created that screen immediately above and it doesn't know that I now have an additional kernel for MX.

Here's my question. When I boot to MX23 with 6.1.0, is that kernel (6.1.0) getting updated as necessary? Or do I need to download something else? The "Debian 64-bit" as Dolphin-Oracle indicated and I think DukeComposed mentioned?

I'm really hoping I can do all I want with MX Package Installer and Discover. I haven't used the terminal to do apt commands.

There's another question that relates to Liquorix 6.5.11-3 that I'll also ask, but I'll leave it until after I've got this question for 6.1.0-10 sorted.

Thanks and Cheers.

[DukeComposed]

Here's my question. When I boot to MX23 with 6.1.0, is that kernel (6.1.0) getting updated as necessary?

Remember what you've been told about kernel metapackages. If you have the metapackage installed, that kernel series will get updated as long as the Debian release supports it. If you remove the metapackage, you won't get updates.

[asqwerth]

Just search Synaptic or MX Packageinstaller to see if the metapackage you have been told about is installed. If yes, it's all good.

[ornithorhynchus]

@DukeComposed

@asqwerth

Thanks, people. But I am thick. If I'm using 6.1.0 and I click on and successfully download Debian 64-bit does that keep my 6.1.0 updated?

Given my current level of understanding, I can't tell from the postings whether the answer to this is yes or no.

Much appreciated.

Thanks and Cheers.

[asqwerth]

If the metapackage is installed, then whenever there is an update to the default Debian kernel for MX23 (6.1 series), it will update it. Note this is only for the default 6.1 series.

If you are on Liquoriix kernel, you need to have the liquorix metapackage installed, which I believe was also described by name in this thread. I'm not on Liquorix kernel for MX23, so I can't confirm this.

[MXRobo]

I'm on MX-21 and Xfce, so not an exact match, but….

which would be part of the automatic kernel update system because it's AHS.

False - as not necessarily.

As per D.O. post #2 :
linux-image-amd64 – which is a metapackage – note no version numbers (VERSION NUMBER is key!)
linux-image-liquorix-amd64 which is a metapackage – again, note no version numbers, hence a metapackage.

Verus for example: linux-image-6.1.0-20mx-ahs-amd64-unsigned which has version numbers, "6.1.0-20".
The versioned are not metapackages, and will not autoupdate.

Try that in MXPI→ Enabled Repo when searching for "linux-image" or "linux-header".
In both Popular Applications, and Enabled Repos tabs, highlight > R-click > more information

Again, per D.O.'s post #2 image, the Debian 64 bit Description says "autoupdates".
And Liquorix 64 bit (ahs updates package) Package name say updated, but the Description says that ahs repo has to be permanently enabled for autoupdates. I believe that this is only required for the liquorix kernels because they are installed from the ahs repo. Also note, both non-versioned – no version numbers.

Caveat – IIRC, this was true, but MAY have changed for some of the very recent liquorix kernels – not sure. For, me it doesn't matter, because if I install a liquorix kernel, I usually leave the ahs repo permanently enabled anyway – as does D.O. Again, not sure about this possible recent change.
===========================================================================

Duke Composed's comment:

If the package is named "linux-image-6.7.12-1-liquorix-amd64", there will never be a newer version of that package.

That means apt-get will never update it, because it has a version number - apt will never see that same version number in a new package.
============================

I downloaded Liquorix 6.5.11.3 but I haven't begun to use it yet. It's an option in the screen in MX Boot Options:

In terminal, type "uname -a" or "uname -r"
Actually, 6.5.11.4 (not 3) shows as available, but the latest kernel should boot automatically.

That image shows I've also downloaded AVLMX. I boot it when I want to work with audio.

Not sure about that, I didn't know (if it does) that MX Boot Options would show another installed distro. Again, don't know what's going on.

It's been a while since I dual booted (thanks to MX and it's testing and backports), and I'm not really sure what you have, but if AVLMX is installed as a separate distro, I think you have to run "sudo update-grub" from the distro that is "controlling grub" or has grub – either way, running "sudo update-grub" from either distro should do no harm, it'd just be redundant. Not sure about this, except the latter won't harm.


MXPI > Popular Applications > Kernels – more info will usually state whether it is a metapackage – I think.

[ornithorhynchus]

Thanks people.

Thanks for taking the time with detailed postings.

I installed Debian 64 bit. During installation I could see that the system was constructing components of the 6.1.0-21 kernel. I selected it from MX Boot Options. But after reboot the 6.1.0-21 option wasn't in Advanced options in the boot menu and I found I'd rebooted only to 6.1.0-10.

@MXRobo

Then I did as you suggested: sudo update-grub. When I did that within the MX system I got the same result as immediately above in this post. So I booted to AVL and did sudo update-grub. Then when I rebooted into MX, 6.1.0-21 was an option (as was also the liquorix kernel I've downloaded, 6.5.11-4). I selected 6.1.0-21 and lo and behold my quick system info shows that's what I now have running.



So thanks for all your help here.

Cheers to all.