On Friday 13 May 2022 21:36 Michael Tremer wrote: > Hello, > >> On 13 May 2022, at 16:02, Rob Brewer wrote: >> >> On Thursday 12 May 2022 14:15 Rob Brewer wrote: >> >>> On Thursday 12 May 2022 13:51 Michael Tremer wrote: >>> >>>> Hello Rob, >>>> >>>> You seem to already have lost the kernel there which is not part of >>>> 168. >>>> >>>> Can you extract any log files from /var/log/pakfire? >>>> >>>> -Michael >>>> >>> I was upgrading 165-168 so I think Linux 5.15.23-ipfire was from 165. >>> I am trying to build a bootable USB drive so I can mount the ssd and >>> look at the Pakfire logs. >>> >>> >>> Rob >>> >> I have been unable to boot from a usb drive so I re-fitted an old mSATA >> SSD with an earlier version of IPFIRE and was surprisingly unable to boot >> from there also. >> >> On investigation the bios is reporting: >> >> SeaBIOS (version rel-1.14.0.1-0-g8610266a) >> >> yet I manually upgraded it to v4.16.0.2 a few weeks ago after a >> discussion with Bernard. >> >> https://community.ipfire.org/t/entropy-with-new-apu-firmware/7707 >> >> Could something have downgraded or corrupted the BIOS? > > No, we never touch this as it is too unpredictable what would happen. > >> I'll try to re-flash back to v4.16.0.2 if I can and try to boot again. > > But that is not the same version number that you are comparing there. > > SeaBIOS is a part of the firmware and comes in a different version. Yes sorry the BIOS version was a red-herring. When I eventually could boot from USB I could see that the correct BIOS version was displayed on the boot screen. My problem seems to be that grub hasn't been correctly updated to load the current kernel. Rob