Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: mm0fmf <none@invalid.com>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Raspbery Pi OS Lite stuck
Date: Tue, 18 Jun 2024 17:38:21 +0100
Organization: A noiseless patient Spider
Lines: 51
Message-ID: <v4sd5v$1eeo6$1@dont-email.me>
References: <v4rhbg$18u3u$1@dont-email.me>
 <718738882@f1.n770.z20481.fidonet.org> <v4s9eb$1dn50$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 18 Jun 2024 18:38:23 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="52db7d4796f9ef113bc60fb4d4d4bebf";
	logging-data="1522438"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+bEl22jJugJj33sXZcgWg8"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.1
Cancel-Lock: sha1:Omx+wdOFXxvyEEHH1Sqyz075Mkc=
In-Reply-To: <v4s9eb$1dn50$1@dont-email.me>
Content-Language: en-GB
Bytes: 3531

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.