Updating Q4OS (Gemini) to the latest kernel

FlexQ4 · 2026-06-06 13:54

Hello,
with an apt-cache search linux-image | grep 5. i get the following large list:

~\> apt-cache search linux-image | grep 5.
linux-headers-5.10.0-30-amd64 - Header files for Linux 5.10.0-30-amd64
linux-headers-5.10.0-30-cloud-amd64 - Header files for Linux 5.10.0-30-cloud-amd64
linux-headers-5.10.0-30-rt-amd64 - Header files for Linux 5.10.0-30-rt-amd64
linux-headers-5.10.0-32-amd64 - Header files for Linux 5.10.0-32-amd64
linux-headers-5.10.0-32-cloud-amd64 - Header files for Linux 5.10.0-32-cloud-amd64
linux-headers-5.10.0-32-rt-amd64 - Header files for Linux 5.10.0-32-rt-amd64
linux-image-5.10.0-30-amd64-dbg - Debug symbols for linux-image-5.10.0-30-amd64
linux-image-5.10.0-30-amd64-unsigned - Linux 5.10 for 64-bit PCs
linux-image-5.10.0-30-cloud-amd64-dbg - Debug symbols for linux-image-5.10.0-30-cloud-amd64
linux-image-5.10.0-30-cloud-amd64-unsigned - Linux 5.10 for x86-64 cloud
linux-image-5.10.0-30-rt-amd64-dbg - Debug symbols for linux-image-5.10.0-30-rt-amd64
linux-image-5.10.0-30-rt-amd64-unsigned - Linux 5.10 for 64-bit PCs, PREEMPT_RT
linux-image-5.10.0-32-amd64-dbg - Debug symbols for linux-image-5.10.0-32-amd64
linux-image-5.10.0-32-amd64-unsigned - Linux 5.10 for 64-bit PCs
linux-image-5.10.0-32-cloud-amd64-dbg - Debug symbols for linux-image-5.10.0-32-cloud-amd64
linux-image-5.10.0-32-cloud-amd64-unsigned - Linux 5.10 for x86-64 cloud
linux-image-5.10.0-32-rt-amd64-dbg - Debug symbols for linux-image-5.10.0-32-rt-amd64
linux-image-5.10.0-32-rt-amd64-unsigned - Linux 5.10 for 64-bit PCs, PREEMPT_RT
linux-image-5.10.0-30-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-30-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-30-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-5.10.0-32-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-32-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-32-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-headers-5.10.0-43-amd64 - Header files for Linux 5.10.0-43-amd64
linux-headers-5.10.0-43-cloud-amd64 - Header files for Linux 5.10.0-43-cloud-amd64
linux-headers-5.10.0-43-rt-amd64 - Header files for Linux 5.10.0-43-rt-amd64
linux-headers-5.10.0-44-amd64 - Header files for Linux 5.10.0-44-amd64
linux-headers-5.10.0-44-cloud-amd64 - Header files for Linux 5.10.0-44-cloud-amd64
linux-headers-5.10.0-44-rt-amd64 - Header files for Linux 5.10.0-44-rt-amd64
linux-image-5.10.0-43-amd64-dbg - Debug symbols for linux-image-5.10.0-43-amd64
linux-image-5.10.0-43-amd64-unsigned - Linux 5.10 for 64-bit PCs
linux-image-5.10.0-43-cloud-amd64-dbg - Debug symbols for linux-image-5.10.0-43-cloud-amd64
linux-image-5.10.0-43-cloud-amd64-unsigned - Linux 5.10 for x86-64 cloud
linux-image-5.10.0-43-rt-amd64-dbg - Debug symbols for linux-image-5.10.0-43-rt-amd64
linux-image-5.10.0-43-rt-amd64-unsigned - Linux 5.10 for 64-bit PCs, PREEMPT_RT
linux-image-5.10.0-44-amd64-dbg - Debug symbols for linux-image-5.10.0-44-amd64
linux-image-5.10.0-44-amd64-unsigned - Linux 5.10 for 64-bit PCs
linux-image-5.10.0-44-cloud-amd64-dbg - Debug symbols for linux-image-5.10.0-44-cloud-amd64
linux-image-5.10.0-44-cloud-amd64-unsigned - Linux 5.10 for x86-64 cloud
linux-image-5.10.0-44-rt-amd64-dbg - Debug symbols for linux-image-5.10.0-44-rt-amd64
linux-image-5.10.0-44-rt-amd64-unsigned - Linux 5.10 for 64-bit PCs, PREEMPT_RT
linux-image-5.10.0-43-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-43-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-43-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-5.10.0-44-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-44-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-44-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-headers-5.10.0-28-amd64 - Header files for Linux 5.10.0-28-amd64
linux-image-5.10.0-22-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-28-amd64 - Linux 5.10 for 64-bit PCs (signed)

The both latter (5.10.0-22/28) are those from installation, and 5.10.0-28 runs rock-stable for 2 years now!

a) May i presume, that an update to the latest kernel - linux-image-5.10.0-44-amd64 - is advisable though?
b) It is simply done by sudo apt install linux-image-5.10.0-44-amd64 ?
c) Should i run an additional sudo apt install linux-headers-5.10.0-44-amd64 for the headers?
d) How much additional space is approximately needed on disk?
e) Why are kernels 5.10.0-33 - 5.10.0-42 missing in the list above?

F) Is it possible to revert back to kernel 5.10.0-28 if something goes wrong?

Thank you!

hchiper · 2026-06-06 21:49

a) Yes
b, c) Easier to let Update Manager do the upgrade.
d) About no additional space since an older version will be removed.
e) ?
f) Probably yes (your current version will be kept alongside the new one)

FlexQ4 · 2026-06-06 23:48

Thanks for your answers, hchiper!

I did a test-upgrade, on a backup-disk (from 5.10.0-22), using the sudo apt install manually.
Together with the headers, that op uses additional ~ 400 MB (no kernel to purge in this case!).

Now i'm trying to figure out where the new 5.10.0-44 kernel-"package" was stored, if its possible to copy it to my main disk, and start the kernel-update there ,locally' (without downloading th package again).

If someone here yet knows, your welcome to assist ;-)

Thanks!

Last edited by FlexQ4 (2026-06-07 13:08)

FlexQ4 · 2026-06-09 22:06

No, on my main disk i first downloaded the kernel (linux-image-5.10.0-44-amd64) and then installed it:
$ apt install ./linux-image-5.10.0-44-amd64.deb

That seems to work too, BUT the output of neofetch - unlike to the test-disk - now seems somewhat poorly:

        #####           me@flex7
       #######          --------
       ##O#O##          OS: Linux (Unknown) x86_64
       #######          Kernel: 5.10.0-44-amd64
     ###########        Uptime: 3 mins
    #############       Packages: 2021 (dpkg)
   ###############      Shell: bash 5.1.4
   ################     Resolution: 1440x900
  #################     DE: Trinity R14.0.12
#####################   WM: twin
#####################   Theme: Q4OS02 [GTK2], Q4OS01 [GTK3]
  #################     Terminal: konsole

It doesn't recognize it's Q4OS/Debian here! (See also snapshot below)

Attachments:

snapshot3.png, Size: 25.6 KiB, Downloads: 17

hchiper · 2026-06-10 08:50

FlexQ4 wrote:

Now i'm trying to figure out where the new 5.10.0-44 kernel-"package" was stored, if its possible to copy it to my main disk, and start the kernel-update there ,locally' (without downloading th package again).

Maybe in /var/cache/apt/archives/

hchiper · 2026-06-10 08:56

FlexQ4 wrote:

No, on my main disk i first downloaded the kernel (linux-image-5.10.0-44-amd64) and then installed it:
$ apt install ./linux-image-5.10.0-44-amd64.deb
That seems to work too, BUT the output of neofetch - unlike to the test-disk - now seems somewhat poorly:
(...)
It doesn't recognize it's Q4OS/Debian here! (See also snapshot below)

I may be wrong, but I believe the reason is that you didn't let Update Manager install the kernel and also tweak some configuration files to add the "Q4OS" references.

q4osteam · 2026-06-10 09:41

You should install the official kernel from Debian repositories, we don't recommend installing any inappropriate or unknown kernels.

FlexQ4 · 2026-06-10 13:20

I think i did install the official kernel from Debian repositories in both cases:
Test-disk:
apt install linux-image-5.10.0-44-amd64 > neofetch works fine!

On the main disk: first dowloaded the kernel, then installed it:
- apt download linux-image-5.10.0-44-amd64
- apt install ./linux-image-5.10.0-44-amd64_5.10.257-1_amd64.deb

That really shouldn't make a great difference!?

And all the known tools are delivering the correct informations:

$ hostnamectl
   Static hostname: flex7
         Icon name: computer-desktop
           Chassis: desktop
        Machine ID: <...>
           Boot ID: <...>
  Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: Linux 5.10.0-44-amd64
      Architecture: x86-64

$ cat /usr/lib/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ uname -a
Linux flex7 5.10.0-44-amd64 #1 SMP Debian 5.10.257-1 (2026-05-27) x86_64 GNU/Linux

Edit: just to be clear: The output of the 3 commands above are identcal on both disks!

Only neofetch has an issue after the update made in ,two steps', that's somewhat weird.

Last edited by FlexQ4 (2026-06-10 13:33)

FlexQ4 · 2026-06-10 16:45

LoL - i updated my main (Debian 11 based) disk to Python 3.12 (to /usr/local/lib/python3.12) a time ago - which (for some reason) lacks of lsb_release.py - but neofetch relies on it! A simple symlink to it (it's still in /usr/share/pyshared) fixed the issue.

Q4OS Forum

#1 2026-06-06 13:54

Updating Q4OS (Gemini) to the latest kernel

#2 2026-06-06 21:49

Re: Updating Q4OS (Gemini) to the latest kernel

#3 2026-06-06 23:48

Re: Updating Q4OS (Gemini) to the latest kernel

#4 2026-06-09 22:06

Re: Updating Q4OS (Gemini) to the latest kernel

#5 2026-06-10 08:50

Re: Updating Q4OS (Gemini) to the latest kernel

#6 2026-06-10 08:56

Re: Updating Q4OS (Gemini) to the latest kernel

#7 2026-06-10 09:41

Re: Updating Q4OS (Gemini) to the latest kernel

#8 2026-06-10 13:20

Re: Updating Q4OS (Gemini) to the latest kernel

#9 2026-06-10 16:45

Re: Updating Q4OS (Gemini) to the latest kernel

Board footer