INTL 3:770/1 3:770/3   
   REPLYADDR cl@isbd.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  52ac280b   
   REPLY:  72bcb600   
   PID: SoupGate-Win32 v1.05   
   I think there's something awry or different in some way on the older   
   system.  There is a hardware difference, the older system (which is a   
   2Gb Pi 4B) boots in the standard way from an SD card.  The newer   
   system (which is a 1Gb Pi 4B) boots from USB.   
      
   The contents of /boot are different on the two systems:-   
      
   Newer Pi 4B (wiht kernel 6.6.62):-   
      
       chris@newodinpi$ ls /boot   
       System.map-6.6.51+rpt-rpi-2712  config-6.6.51+rpt-rpi-v8          
   initrd.img-6.6.51+rpt-rpi-v8    vmlinuz-6.6.51+rpt-rpi-v8   
       System.map-6.6.51+rpt-rpi-v8    config-6.6.62+rpt-rpi-2712        
   initrd.img-6.6.62+rpt-rpi-2712  vmlinuz-6.6.62+rpt-rpi-2712   
       System.map-6.6.62+rpt-rpi-2712  config-6.6.62+rpt-rpi-v8          
   initrd.img-6.6.62+rpt-rpi-v8    vmlinuz-6.6.62+rpt-rpi-v8   
       System.map-6.6.62+rpt-rpi-v8    config.txt                      issue.txt   
       cmdline.txt                     firmware                        overlays   
       config-6.6.51+rpt-rpi-2712      initrd.img-6.6.51+rpt-rpi-2712    
   vmlinuz-6.6.51+rpt-rpi-2712   
       chris@newodinpi$   
      
   Older Pi 4B (with kernel 6.1.21):-   
      
       chris@homepi$ ls /boot   
       COPYING.linux             bcm2710-rpi-zero-2.dtb  cmdline.txt     
   fixup_cd.dat  start4.elf   
       LICENCE.broadcom          bcm2711-rpi-4-b.dtb     config.txt      
   fixup_db.dat  start4cd.elf   
       bcm2710-rpi-2-b.dtb       bcm2711-rpi-400.dtb     fixup.dat       
   fixup_x.dat   start4db.elf   
       bcm2710-rpi-3-b-plus.dtb  bcm2711-rpi-cm4-io.dtb  fixup4.dat      
   issue.txt     start4x.elf   
       bcm2710-rpi-3-b.dtb       bcm2711-rpi-cm4.dtb     fixup4cd.dat    
   kernel8.img   start_cd.elf   
       bcm2710-rpi-cm3.dtb       bcm2711-rpi-cm4s.dtb    fixup4db.dat    
   overlays      start_db.elf   
       bcm2710-rpi-zero-2-w.dtb  bootcode.bin            fixup4x.dat     
   start.elf     start_x.elf   
       chris@homepi$   
      
      
   The newer system has all the bcm and similar files in /boot/firmware.  I can't   
   see the vmlinuz   
   files and such anywhere on the older system.   
      
   The older system does seem to have a rather anomolous configuration:-   
      
       root@homepi# apt-file search vmlinuz-6.6.62   
       linux-image-6.6.62+rpt-rpi-2712: /boot/vmlinuz-6.6.62+rpt-rpi-2712   
       linux-image-6.6.62+rpt-rpi-v8: /boot/vmlinuz-6.6.62+rpt-rpi-v8   
      
   So apt thinks the vmlinuz files should be in /boot but they definitely aren't   
   there.   
   It also shows the version as 6.6.62 and that *isn't* the actually running   
   kernel.   
      
      
      
   I have just tried:-   
      
       apt reinstall linux-image-6.6.62+rpt-rpi-v7   
       apt reinstall linux-image-6.6.62+rpt-rpi-v8   
       apt reinstall linux-image-6.6.51+rpt-rpi-2712   
      
      
   But apart from installing the vmlinuz files in /boot that hasn't changed   
   anything,   
   it still boots into a 6.1.21 kernel.   
      
   It seems maybe as if something in the boot sequence is different/wrong.   
      
   --   
   Chris Green   
   ·   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 19/38 105/81 106/201 128/187 129/305 153/757 7715 154/110   
   SEEN-BY: 218/700 840 220/70 226/17 30 100 227/114 229/110 111 114   
   SEEN-BY: 229/200 206 275 300 317 400 426 428 470 550 616 664 700 705   
   SEEN-BY: 266/512 267/800 291/111 292/854 310/31 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 281 418 420 509 2744 712/848 770/1   
   SEEN-BY: 770/3 100 330 340 772/210 220 230 902/26 2320/105 5020/400   
   SEEN-BY: 5075/35   
   PATH: 770/3 1 633/280 229/426