Subj : Re: Why has new bookwork installation given me a newer kernel than an u To : The Natural Philosopher From : Chris Green Date : Fri Jan 31 2025 09:00:16 The Natural Philosopher wrote: > On 30/01/2025 21:41, Chris Green wrote: > > The Natural Philosopher wrote: > >> On 30/01/2025 20:54, Chris Green wrote: > >>> Marco Moock wrote: > >>>> On 30.01.2025 16:00 Uhr Chris Green wrote: > >>>> > >>>>> I'm confused, I've just installed Raspberry Pi OS (Bookworkm) on a > >>>>> new Pi 4B and it has installed Kernel: 6.6.62+rpt-rpi-v8 aarch64. > >>>>> > >>>>> I have another 4B on which I installed Bookworm a while ago and have > >>>>> updated regularly and it only has Kernel: 6.1.21-v8+ aarch64. > >>>> > >>>> apt list installed 'linux-image*' > >>>> > >>> That simply lists every possible matching package as far as I can see, > >>> not what's actually installed. > >>> > >>> There isn't anything actually installed with a package name matching > >>> 'linux-image':- > >>> > >>> chris@homepi$ dpkg -l | grep linux-image > >>> chris@homepi$ > >>> > >>> > >>> The 'older' system has /boot/kernel8.img installed from the > >>> raspberrypi-kernel package. > >>> > >>> The 'newer' system says /boot/kernel8.img comes from the > >>> raspberrypi-kernel package but there isn't any raspberrypi-kernel > >>> package installed. :- > >>> > >>> root@newodinpi:~# apt-file search kernel8.img > >>> raspberrypi-kernel: /boot/kernel8.img > >>> root@newodinpi:~# dpkg -l | grep raspberrypi-kernel > >>> root@newodinpi:~# > >>> > >>> Something is funny here! > >>> > >> Don't you have to use apt-get dist-upgrade to install newer kernels? > >> I assumed that was to avoid the need to reboot on automated updates. > >> > >> Yeah. I think I am right. The policy is not to change the kernel on > >> normal upgrades > >> > > I tried that, no change, still 6.1 kernel:- > > > > root@homepi# uname -a > > Linux homepi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux > > root@homepi# apt update > > Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB] > > Hit:2 http://deb.debian.org/debian bookworm InRelease > > Hit:3 http://deb.debian.org/debian bookworm-updates InRelease > > Hit:4 http://archive.raspberrypi.org/debian bookworm InRelease > > Get:5 https://apt.syncthing.net syncthing InRelease [15.7 kB] > > Fetched 63.6 kB in 2s (38.1 kB/s) > > Reading package lists... Done > > Building dependency tree... Done > > Reading state information... Done > > All packages are up to date. > > root@homepi# apt dist-upgrade > > Reading package lists... Done > > Building dependency tree... Done > > Reading state information... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > root@homepi# > > > > > Odd. apt and apt-get may have different rules > > "apt-get upgrade only upgrades the apps, tools, and utilities. It does > not install new Linux kernel of the OS. > > "apt upgrade upgrades the apps, tools, and utilities and installs new > Linux kernel of the OS. However, it never removes old packages. > > "apt full-upgrade upgrades the apps, tools, and utilities and installs > new Linux kernel of the OS. It also removes old packages if needed for > the upgrade." > > It looks to me apt full-upgrade does the same thing as apt-get > dist-upgrade. That is to say the full-upgrade will check for and install > a new kernel if available and removes old packages if the removal is > necessary for the upgrade." > > I don't think apt dist-upgrade is actually a valid command. > > "apt full-upgrade and apt-get dist-upgrade are the same command. But > again apt is the newer command." > > Anyway see if any of that works., I am pretty sure it did for me > root@homepi# apt-get update Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:3 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB] Hit:4 http://archive.raspberrypi.org/debian bookworm InRelease Get:5 https://apt.syncthing.net syncthing InRelease [15.7 kB] Fetched 119 kB in 2s (71.8 kB/s) Reading package lists... Done root@homepi# apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@homepi# apt update Hit:1 http://security.debian.org/debian-security bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.org/debian bookworm InRelease Get:5 https://apt.syncthing.net syncthing InRelease [15.7 kB] Fetched 15.7 kB in 2s (9,499 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@homepi# apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@homepi# uname -a Linux homepi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux root@homepi# They both look the same to me, neither of them gets the latest kernel. I think running 'rpi-update' may update the kernel but it shouldn't be necessary to do that. -- Chris Green ยท --- SoupGate-Win32 v1.05 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3) .