Zorin keep booting using previous Kernel

I’m using Zorin OS and recently the system has received the kernel 7.0.0-28.
Unfortunately my system keep booting using:

uname -a 
Linux ThinkPad-P14s-Gen-6 6.17.0-1030-oem #30-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 16 15:01:53 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux

To try to analyzed the problem:

ls /boot/vmlinuz*
/boot/vmlinuz  /boot/vmlinuz-6.17.0-1030-oem  /boot/vmlinuz-7.0.0-28-generic  /boot/vmlinuz.old

grep menuentry /boot/grub/grub.cfg | head -20

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
  menuentry_id_option=""
export menuentry_id_option
menuentry 'Zorin OS' --class zorin --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-dcdf8297-c755-4df8-ac99-7a4792ef1522' {
submenu 'Advanced options for Zorin OS' $menuentry_id_option 'gnulinux-advanced-dcdf8297-c755-4df8-ac99-7a4792ef1522' {
	menuentry 'Zorin OS, with Linux 6.17.0-1030-oem' --class zorin --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.17.0-1030-oem-advanced-dcdf8297-c755-4df8-ac99-7a4792ef1522' {
	menuentry 'Zorin OS, with Linux 6.17.0-1030-oem (recovery mode)' --class zorin --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.17.0-1030-oem-recovery-dcdf8297-c755-4df8-ac99-7a4792ef1522' {
	menuentry 'Zorin OS, with Linux 7.0.0-28-generic' --class zorin --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-7.0.0-28-generic-advanced-dcdf8297-c755-4df8-ac99-7a4792ef1522' {
	menuentry 'Zorin OS, with Linux 7.0.0-28-generic (recovery mode)' --class zorin --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-7.0.0-28-generic-recovery-dcdf8297-c755-4df8-ac99-7a4792ef1522' {
		menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {

and to try to fix it I have changed the entry

in /etc/default/grub

from

GRUB_DEFAULT=0

to:

GRUB_DEFAULT="gnulinux-7.0.0-28-generic-advanced-dcdf8297-c755-4df8-ac99-7a4792ef1522"

and then:
sudo update-grub

I just want to add that I’m using an encrypted partition.

I would really appreciate any help to fix this problem.

Welcome to the Forum!

First: I changed the Category from Feedback to General Help because this is more a Help Request.

To Your Issue:
The oem Kernel is not the Standard Kernel. Did You installed that manually? Could You post the complete Content of the GRUB config File /etc/default/grub please? So, we can have a complete Overview from it.

Thank you for your replay.
I do not really remeber to have installed it on pourpose. So it's a bit strange it is in use.

/etc/default/grub:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT="gnulinux-7.0.0-28-generic-advanced-dcdf8297-c755-4df8-ac99-7a4792ef1522"
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

GRUB_THEME=/usr/share/grub/themes/zorin/theme.txt
GRUB_DISABLE_MEMTEST=true

From /etc/apt/source.list.d

-rw-r--r-- 1 root root  240 mag  6 13:19 oem-sutton-dario-meta.list.distUpgrade
-rw-r--r-- 1 root root  100 lug 19 21:50 oem-sutton-dario-meta.sources
-rw-r--r-- 1 root root  100 lug 19 21:50 oem-sutton-dario-meta.sources.save

They are listed as additional drivers for Lenovo

Maybe due to this?

/etc/default/grub.d/oem-flavour.cfg:

# This file is automatically generated by oem-sutton-dario-meta, and changes will be overriden
GRUB_FLAVOUR_ORDER=oem

Maybe this is the cause?

Keeping adding informations, sorry

Yes, I think that setting would prioritize the oem kernel.

Answer Brave AI (Leo):
The setting GRUB_FLAVOUR_ORDER=oem is a hidden configuration option in the Ubuntu grub2 package that allows users to specify a preferred kernel flavor for the default boot entry.

Okay, I would suggest to try the Following:

In /etc/default/grub, You change the Line:

GRUB_DEFAULT="gnulinux-7.0.0-28-generic-advanced-dcdf8297-c755-4df8-ac99-7a4792ef1522"

to

GRUB_DEFAULT=0

And here:

You set at the Beginning of the Line a # to comment it out so it looks like this:

#GRUB_FLAVOUR_ORDER=oem

Then make a sudo update-grub and check if it starts in the 7.0 Kernel. If it shouldn't directly start in the 7.0 Kernel, choose on the GRUB Menu one time the 7.0 Kernel in ''Advances Options'' and then check if it stays with rebooting again.

1 Like

It worked!!!
Thanks everyone for your help.

Linux ThinkPad-P14s-Gen-6 7.0.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul  1 15:50:57 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
2 Likes

For clarity: What this does is lock you into the 7.0 kernel you are currently on. So when it gets an update, you will keep booting into this kernel, not that new one.

The cause of the original issue was that you were not using the HWE line, but using the OEM kernel, instead. Since there was no update to the OEM, you remained on the only available OEM kernel.

Removing the OEM and then installing the HWE would put you on track to then upgrade to the 7.0 HWE kernel.

However

I do not recommend doing this just to see a higher kernel number. There is a reason you were on the OEM kernel and since I do not know at this distance what that reason is... it cannot be said you should switch kernels.

Thank you for your replay.
I understand your point. At the moment I'm using the 7.0 kernel and I do not have any problem. I will keep testing and in case switch back to the oem ones.