24.04 uses old kernel after upgrade

[dmeyermail]

Hello,
I upgraded to Ubuntu 24.04. However, my machine still seems to be using kernel 5.14.0-1049-oem. This is what I get from

uname -r

5.14.0-1049-oem

Here is my /boot directory:

ls /boot

config-5.14.0-1049-oem memtest86+ia32.efi
config-6.8.0-44-generic memtest86+x64.bin
efi memtest86+x64.efi
grub System.map-5.14.0-1049-oem
initrd.img System.map-6.8.0-44-generic
initrd.img-5.14.0-1049-oem vmlinuz
initrd.img-6.8.0-44-generic vmlinuz-5.14.0-1049-oem
initrd.img.old vmlinuz-6.8.0-44-generic
memtest86+ia32.bin vmlinuz.old

So the 6.8-44 kernel seems to be there but not used. Any help very much appreciated!

[ubfan1]

What does your grub menu show? Both kernels, with the default on the old one (last one booted)? There are ways to have grub default to the last booted kernel, so you may have to explicitly select the new one to boot it the first time.

[1fallen2]

Early in the Development cycle for Noble, I was faced with the same old kernel only from grub.

And ubfan1 has an idea, could you please show us the "/etc/default/grub"
This may help us:

less /etc/default/grub

And it would be nice to see this as well:

sudo update-grub

Please wrap those in Code Tags [CODE]your pastes here[/CODE]

[dmeyermail]

Thanks a lot. Here is /etc/default/grub

less /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=0
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"
~
~
~
~

The second command does not work

sudo apt update-grub
E: Invalid operation update-grub

I did

sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/oem-flavour.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.14.0-1049-oem
Found initrd image: /boot/initrd.img-5.14.0-1049-oem
Found linux image: /boot/vmlinuz-6.8.0-44-generic
Found initrd image: /boot/initrd.img-6.8.0-44-generic
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-5.14.0-1049-oem
Found initrd image: /boot/initrd.img-5.14.0-1049-oem
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.8.0-44-generic
Found initrd image: /boot/initrd.img-6.8.0-44-generic
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

[deadflowr]

Without knowing what it does my gut instinct says the problem probably relates to the file:
`/etc/default/grub.d/oem-flavour.cfg'

Maybe look at what it does or says it does.

[dmeyermail]

I get

less /etc/default/grub.d/oem-flavour.cfg
# This file is automatically generated by oem-stella.cmit-pinsir-meta, and changes will be overriden
GRUB_FLAVOUR_ORDER=oem
/etc/default/grub.d/oem-flavour.cfg (END)

[1fallen2]

That might come in from a PPA, will you show us this:

inxi -r

[dmeyermail]

Here I get6

inxi -r
Repos:
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/gnumdk-ubuntu-lollypop-focal.sources
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.sources
    1: deb http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/oem-stella.cmit-pinsir-meta.sources
    1: deb http://hp.archive.canonical.com/ noble stella stella.cmit
  No active apt repos in: /etc/apt/sources.list.d/signal-xenial.sources
  No active apt repos in: /etc/apt/sources.list.d/teams.sources
  No active apt repos in: /etc/apt/sources.list.d/third-party.sources
  Active apt repos in: /etc/apt/sources.list.d/ubuntu.sources
    1: deb http://gb.archive.ubuntu.com/ubuntu/ noble noble-updates noble-backports main restricted universe multiverse
    2: deb http://security.ubuntu.com/ubuntu noble-security main restricted universe multiverse

[deadflowr]

Does oem-stella.cmit-pinsir-meta even exists on noble?

Look at

apt policy oem-stella.cmit-pinsir-meta

it might be possible to simply change the line from

GRUB_FLAVOUR_ORDER=oem
to 
GRUB_FLAVOUR_ORDER=generic

Might even be possible to comment out the line ( adding a # to the beginning of the line will turn it off)

Depending on if the package exists on 24.04,
since if it does exist still then any updates can change it back.
But if it doesn't, then the change should stick.

Of course then the issue is the fact that oem kernels are built more for specific hardware configurations and stuff,
and it's unclear whether or not the generic kernel will suffice as those are built for a more general hardware.
Probably not an issue, but you never know until you know.

Just some random thoughts.

[1fallen2]

Does oem-stella.cmit-pinsir-meta even exists on noble?

Look at

apt policy oem-stella.cmit-pinsir-meta

it might be possible to simply change the line from

GRUB_FLAVOUR_ORDER=oem
to 
GRUB_FLAVOUR_ORDER=generic

Might even be possible to comment out the line ( adding a # to the beginning of the line will turn it off)

Depending on if the package exists on 24.04,
since if it does exist still then any updates can change it back.
But if it doesn't, then the change should stick.

Of course then the issue is the fact that oem kernels are built more for specific hardware configurations and stuff,
and it's unclear whether or not the generic kernel will suffice as those are built for a more general hardware.
Probably not an issue, but you never know until you know.

Just some random thoughts.

+1 to all the random thoughts.

The OP might find this interesting on Noble:

You have searched for packages that names contain oem-stella.cmit-pinsir-meta in suite(s) noble, all sections, and all architectures.
Sorry, your search gave no results