After upgrade from 15.3 (in 2 steps) now on 17.2, but getting vmlinuz 5.15... in apt updates rather than vmlinuz 6.8

Installing Zorin OS
1

This may not really be an install issue, but thinking I need to change a setting somewhere post upgrade to 17.2.

I used the GUI-driven upgrades from 15.3 to 16.x and now on 17.2. The vmlinuz version I have in /boot is 6.8.0-52-generic (FWIW, running on a circa 2017 System76 lemur-pro--didn't like PopOS); however, the latest apt update gave me vmlinuz-5.15.0-134-generic (!?!).

I perused my software update settings but nothing jumped out at me showing why I would be retrograded in this way. This is not the first time--I yanked the offending retrograded vmlinuz and associated files (config, System.map, initrd.img) and repointed the links appropriately after the last apt update, then tested with a reboot. But like a bad penny, they've returned with latest apt update.

Any insights from anyone? Many thanks in advance!

2

Can you post the result of

ls /etc/apt/spirces.list.d

and

cat /etc/apt/sources.list

3 
$ ls /etc/apt/sources.list.d
element-io.list       mozilla.list.save  zorinos-ubuntu-apps-bionic.list       zorinos-ubuntu-drivers-bionic.list.save  zorinos-ubuntu-stable-bionic.list
element-io.list.save  zorin.list         zorinos-ubuntu-apps-bionic.list.save  zorinos-ubuntu-patches-bionic.list       zorinos-ubuntu-stable-bionic.list.save
mozilla.list          zorin.list.save    zorinos-ubuntu-drivers-bionic.list    zorinos-ubuntu-patches-bionic.list.save


# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jammy main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jammy universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy universe
deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ jammy multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy multiverse
deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu jammy partner
# deb-src http://archive.canonical.com/ubuntu jammy partner

deb http://security.ubuntu.com/ubuntu jammy-security main restricted
# deb-src http://security.ubuntu.com/ubuntu jammy-security main restricted
deb http://security.ubuntu.com/ubuntu jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu jammy-security universe
deb http://security.ubuntu.com/ubuntu jammy-security multiverse
# deb-src http://security.ubuntu.com/ubuntu jammy-security multiverse
4

I failed to catch my typo
It is

ls /etc/apt/sources.list.d

5

Caught and modified--see above :smile:

6

I think I just saw it--references to bionic, no?

Interestingly, I was receiving no updates for that release at the point at which I chose to upgrade, and now I'm seeing them. Weird.

7

After reading this I realized my good old Canon iP2702 may not be supported under the latest version...maybe I don't want to be too hasty about ditching the old "bionic" release...just in case... :thinking:

8

Yes, let's go ahead and remove them.
They actually should be harmless. I have several still retained that say focal from having done testing on the Upgrader Tool that I never did remove.
But for de-cluttering and randome chance, let's clear them out.

Elevate to root:

sudo -i

Launch file manager:

nautilus

Navigate to /etc/apt/sources.list.d You can remove the dot-saves, since those are generated automatically.
Right click and select Rename replace "bionic" with "jammy" on each.
Now, let's change their contents:
zorinos-ubuntu-apps-jammy.list

deb http://ppa.launchpad.net/zorinos/apps/ubuntu jammy main
# deb-src http://ppa.launchpad.net/zorinos/apps/ubuntu jammy main

zorinos-ubuntu-drivers-jammy.list

deb http://ppa.launchpad.net/zorinos/drivers/ubuntu jammy main
# deb-src http://ppa.launchpad.net/zorinos/drivers/ubuntu jammy main

zorinos-ubuntu-stable-jammy.list

deb http://ppa.launchpad.net/zorinos/stable/ubuntu jammy main
# deb-src http://ppa.launchpad.net/zorinos/stable/ubuntu jammy main

zorinos-ubuntu-patches-jammy.list

deb http://ppa.launchpad.net/zorinos/patches/ubuntu jammy main
# deb-src http://ppa.launchpad.net/zorinos/patches/ubuntu jammy main

Please be sure to save all your work.

Once done, in terminal run:

uname -r

and relay your kernel version.
Reboot.
After boot, run

sudo apt update && sudo apt full-upgrade

in terminal

EDIT:

Your sources cannot pick and choose - so you will want to keep all sources strictly Jammy.

Instead, focus on the proper sources - then we can address your Printer afterward.

9

Very good, thanks.

10

Got lazy:

# for i in `ls -1 *bionic*`; do j=`echo $i | sed s/bionic/jammy/`; mv $i $j; done
# vi *jammy*.list

Noticed all files already had "jammy" references in place of "bionic" references as of March 2nd.

Might we be barking up the wrong tree here, or is it simply the file names that caused apt to go a little nuts?

11

Got smart and industrious. :wink:

Yes, the actual references should be Jammy and therefore, the remaining files should be harmless as leftovers.
But, erring on side of caution due to you having a package issue seems wise.

Have you yet run

sudo apt update && sudo apt full-upgrade

12

Just did:

Fetched 257 kB in 5s (54.0 kB/s)       
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  cryptsetup cryptsetup-bin cryptsetup-initramfs libcryptsetup12
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
root@lemur-pro:/etc/apt/sources.list.d# apt list --upgradable
Listing... Done
cryptsetup-bin/jammy-updates 2:2.4.3-1ubuntu1.3 amd64 [upgradable from: 2:2.4.3-1ubuntu1.2]
cryptsetup-initramfs/jammy-updates,jammy-updates 2:2.4.3-1ubuntu1.3 all [upgradable from: 2:2.4.3-1ubuntu1.2]
cryptsetup/jammy-updates 2:2.4.3-1ubuntu1.3 amd64 [upgradable from: 2:2.4.3-1ubuntu1.2]
libcryptsetup12/jammy-updates 2:2.4.3-1ubuntu1.3 amd64 [upgradable from: 2:2.4.3-1ubuntu1.2]
13

You can run

sudo apt install cryptsetup cryptsetup-bin cryptsetup-initramfs libcryptsetup12

to clear that up...

Then reboot and use your grub menu to also check which kernel versions you have and are about to boot into.

14

I had always presumed that when packages are held back in apt it is because there is not yet full library support for them. That message doesn't particularly bother me, so I'll err on the side of caution.

Re: grub, I can pretty much predict what is going to happen by looking at /boot:

# ll /boot
total 319392
drwxr-xr-x  5 root root      4096 Mar  7 18:06 ./
drwxr-xr-x 20 root root      4096 Mar  2 15:44 ../
-rw-r--r--  1 root root    262228 Feb 12 11:47 config-5.15.0-134-generic
-rw-r--r--  1 root root    287013 Jan 15 09:27 config-6.8.0-52-generic
drwx------ 10 root root      4096 Dec 31  1969 efi/
drwxr-xr-x  5 root root      4096 Mar  7 18:06 grub/
lrwxrwxrwx  1 root root        29 Mar  7 18:06 initrd.img -> initrd.img-5.15.0-134-generic
-rw-r--r--  1 root root 110483329 Mar  7 18:06 initrd.img-5.15.0-134-generic
-rw-r--r--  1 root root 173801007 Mar  2 15:49 initrd.img-6.8.0-52-generic
lrwxrwxrwx  1 root root        27 Mar  2 15:50 initrd.img.old -> initrd.img-6.8.0-52-generic
drwx------  2 root root     16384 Jul 11  2021 lost+found/
-rw-r--r--  1 root root    182800 Feb  6  2022 memtest86+.bin
-rw-r--r--  1 root root    184476 Feb  6  2022 memtest86+.elf
-rw-r--r--  1 root root    184980 Feb  6  2022 memtest86+_multiboot.bin
-rw-------  1 root root   6295053 Feb 12 11:47 System.map-5.15.0-134-generic
-rw-------  1 root root   8667805 Jan 15 09:27 System.map-6.8.0-52-generic
lrwxrwxrwx  1 root root        26 Mar  7 18:06 vmlinuz -> vmlinuz-5.15.0-134-generic
-rw-------  1 root root  11711336 Feb 12 12:36 vmlinuz-5.15.0-134-generic
-rw-------  1 root root  14928264 Jan 15 09:51 vmlinuz-6.8.0-52-generic
lrwxrwxrwx  1 root root        24 Mar  2 15:48 vmlinuz.old -> vmlinuz-6.8.0-52-generic
15

When performing the upgrade command, it will install the upgrades as long as no additional dependency packages need to be installed to do so. If additional dependencies must be installed; it will hold them back.
Running the sudo apt install command will then install them, due to that apt package management command being authorized to install dependencies as needed.

Your grub config will override those symlinks, so what grub_default is set in your grub file?

cat /etc/default/grub

16

Thanks for your insights on apt and grub! As requested...

# cat /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=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on vfio-pci.ids=8086:4905"
GRUB_CMDLINE_LINUX=""

# 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-pc only)
#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
17

Interesting. Well, you can set it to

sudo nano /etc/default/grub

GRUB_DEFAULT="Zorin, with Linux 6.8.0-52-generic"
Tap ctl+o to overwrite, then enter to save current configuration, then ctl+x to exit the editor.
Now, run

sudo update-grub

Reboot and test if it boots to 6.8

Alternatively

You can use this simple technique to set it to the Later kernel, by following the same steps, but doing so booted into the 6.8 kernel:

18

Thanks again!

I did check /boot/grub/grub.cfg and the top entry appears to be 6.8.0-52-generic, so I imagine the "0" default might just automatically choose that.

Looks like grub.cfg is largely unchanged after "update-grub" command.

I'll reboot after a bit...

Thanks @Aravisian for your most helpful guidance!!!

1 Like
19

Reboot completed.

I'll confess, I didn't change the "GRUB_DEFAULT" entry so my running "update-grub" was unnecessary; however, as you predicted, @Aravisian, it did boot up into vmlinuz 6.8, defying my earlier presumptions regarding the symbolic links in /boot.

Once again, many thanks for your most gracious and helpful education of an old Unix head such as myself (since about 1987) in the many wonders of Linux--I learn something quite often, if not every day. :grin: