From Newsgroup: comp.sys.raspberry-pi

I have a Pi Zero W that was running running a Debian 11 version of
Rapsberry PIOS Lite. It was originally running Debian 10 and was
successfully updated to 11 by an in-place update. The Bullseye update
fine and with a few mods to minimise SDcard writes has been running for
years.

A while back I upgraded it in in-place to Bookworm and it went OK. I
think there were some strange network rules such that the Wifi is not
managed by NetworkManager but it works fine. This Pi runs headless and
is used as an SSH gateway from the wonderful internet to my network.

OK, I did an in-place upgrade which they say you should not do but it
worked and the Pi is 100% fine. And I did an in-place upgrade again
which worked. So that's 10->11->12

Except... I've noticed that the kernel is stuck on 6.1.x from 2023 and
whilst there are updates for the components when I run the regular "sudo
apt update / sudo apt upgrade" the kernel doesn't get touched. Looking
on the PiOS website it's says Pi OS lite 32bit is on kernel 6.6.

So my question is whether there is some way with apt update/upgrade to
get the kernel updated? Or I am facing (what I expect to the case) that
I need to do a clean install of the latest image and re-apply my SDcard
wear reducing mods?

Ideas?

--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On Tue, 18 Jun 2024 09:43:26 +0100, mm0fmf wrote:

OK, I did an in-place upgrade which they say you should not do ...

Debian does officially support that, provided you do not go up more than
one major version step at a time.

So my question is whether there is some way with apt update/upgrade
to get the kernel updated?

The kernel is just another package, with a name like “linux-image-«version»-«arch»”. Look for packages with that form of name, and try explicitly installing the version you want. But yeah, I
thought this should be automatic.
--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

Except... I've noticed that the kernel is stuck on 6.1.x from 2023 and
whilst there are updates for the components when I run the regular "sudo
apt update / sudo apt upgrade" the kernel doesn't get touched. Looking
on the PiOS website it's says Pi OS lite 32bit is on kernel 6.6.

So my question is whether there is some way with apt update/upgrade to
get the kernel updated? Or I am facing (what I expect to the case) that
I need to do a clean install of the latest image and re-apply my SDcard
wear reducing mods?

Ideas?

The raspberry pi website suggests that you use "full-upgrade" each time
instead of "upgrade." My kernel would sometimes be listed as "held back"
if I only used "upgrade." "full-upgrade" seems to cause it to be updated
when one is available.


* SLMR 2.1a * */ <==-- Tribble with a lightsaber
--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 17/06/2024 20:29, Mike Powell wrote:

Except... I've noticed that the kernel is stuck on 6.1.x from 2023 and
whilst there are updates for the components when I run the regular "sudo
apt update / sudo apt upgrade" the kernel doesn't get touched. Looking
on the PiOS website it's says Pi OS lite 32bit is on kernel 6.6.

So my question is whether there is some way with apt update/upgrade to
get the kernel updated? Or I am facing (what I expect to the case) that
I need to do a clean install of the latest image and re-apply my SDcard
wear reducing mods?

Ideas?

The raspberry pi website suggests that you use "full-upgrade" each time instead of "upgrade." My kernel would sometimes be listed as "held back"
if I only used "upgrade." "full-upgrade" seems to cause it to be updated when one is available.

* SLMR 2.1a * */ <==-- Tribble with a lightsaber

Thanks for the suggestions. Spending a while looking about the system
showed there was no linux-image-xxxx package installed. I don't know
how that actually happened but it would explain why the kernel was not
being updated. The kernel would be the files from bullseye I'm assuming.
I had a few half-hearted attempts to try to install the
linux-image-6.1.xx package that the currently installed kernel came from
but I got errors each time I tried.

So... I took the MS way out and blitzed it with the latest image and
installed on a new card. A bit of headless setup fun and then checking
in an A+ with a serial console and a Wifi dongle meant I could confirm everything was working. SDcard into the Pi Zero, booted up and auto
connected to the Wifi. Followed by apt update/upgrade, copy some files
from the old card, install fail2ban, make the wear reducing changes and
we're back in business.

I've kept the old card so I may try seeing I can can fix the borked
install and get it to update. I feel I'd understand things better that
way. I don't know if this was the result of doing an in-place update
from bullseye to bookworm.

Thanks for the comments.
--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 18/06/2024 16:34, mm0fmf wrote:

On 17/06/2024 20:29, Mike Powell wrote:

Except... I've noticed that the kernel is stuck on 6.1.x from 2023 and
whilst there are updates for the components when I run the regular "sudo >>> apt update / sudo apt upgrade" the kernel doesn't get touched. Looking
on the PiOS website it's says Pi OS lite 32bit is on kernel 6.6.

So my question is whether there is some way with apt update/upgrade to
get the kernel updated? Or I am facing (what I expect to the case) that
I need to do a clean install of the latest image and re-apply my SDcard
wear reducing mods?

Ideas?

The raspberry pi website suggests that you use "full-upgrade" each time
instead of "upgrade."  My kernel would sometimes be listed as "held back" >> if I only used "upgrade."  "full-upgrade" seems to cause it to be updated >> when one is available.


  * SLMR 2.1a * */  <==-- Tribble with a lightsaber

Thanks for the suggestions.  Spending a while looking about the system showed there was no linux-image-xxxx package installed.  I don't know
how that actually happened but it would explain why the kernel was not
being updated. The kernel would be the files from bullseye I'm assuming.
I had a few half-hearted attempts to try to install the
linux-image-6.1.xx package that the currently installed kernel came from
but I got errors each time I tried.

So... I took the MS way out and blitzed it with the latest image and installed on a new card. A bit of headless setup fun and then checking
in an A+ with a serial console and a Wifi dongle meant I could confirm everything was working. SDcard into the Pi Zero, booted up and auto connected to the Wifi. Followed by apt update/upgrade, copy some files
from the old card, install fail2ban, make the wear reducing changes and we're back in business.

I've kept the old card so I may try seeing I can can fix the borked
install and get it to update. I feel I'd understand things better that
way. I don't know if this was the result of doing an in-place update
from bullseye to bookworm.

Thanks for the comments.

And I've had to fix the systemd issues so fail2ban works and enable nftable.service so nft rules get loaded on boot. No doubt there'll be more.

Systemd: the gift that keeps on giving.
--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 18/06/2024 16:34, mm0fmf wrote:

I've kept the old card so I may try seeing I can can fix the borked
install and get it to update. I feel I'd understand things better that
way. I don't know if this was the result of doing an in-place update
from bullseye to bookworm.

My in place upgrade installed the 6.6 kernel, that was on a 64 bit
install, but 32 bit should do the same.

---druck

--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 2024-06-18, Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

OK, I did an in-place upgrade which they say you should not do ...

Debian does officially support that, provided you do not go up more than
one major version step at a time.

Yes, but you should then read the "upgrade" chapter in the debian release
notes for the new version - sometimes there are manual steps required (I remember "pick a kernel package and install it", but I am not sure for which version that was). Of course, debian will not list raspbian-specific topics,
so these need to be considered additionally.

On i386/x64, I have done lots of in-place upgrades, in one case starting at Debian 3.0, and all worked fine - I don't know why is is recommended to do a fresh install for new raspberry pi os versions.

cu
Michael
--
Some people have no respect of age unless it is bottled.
--- Synchronet 3.19b-Win32 NewsLink 1.113