INTL 3:770/1 3:770/3   
   REPLYADDR none@invalid.com   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  2f0009f3   
   REPLY: 20481:770/1.0 2ad715c2   
   PID: SoupGate-Win32 v1.05   
   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.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 19/38 90/1 105/81 106/201 128/260 129/305 153/757 7715 218/700   
   SEEN-BY: 218/840 220/70 226/17 30 100 227/114 229/110 111 112 113   
   SEEN-BY: 229/200 206 300 317 400 426 428 470 550 616 664 700 266/512   
   SEEN-BY: 267/800 282/1038 291/111 292/854 310/31 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 281 412 418 420 509 2744 712/848 770/1   
   SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 5075/35   
   PATH: 770/3 1 633/280 229/426