-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am Mon, 18 Jun 2018 07:42:20 -0600 Warner Losh <imp_at_bsdimp.com> schrieb: > On Mon, Jun 18, 2018, 3:01 AM Olivier Cochard-Labbé <olivier_at_freebsd.org> > wrote: > > > On Sun, Jun 17, 2018 at 10:01 AM O. Hartmann <ohartmann_at_walstatt.org> > > wrote: > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA512 > > > > > > Running CURRENT as routing and firewalling appliance on a PCengines APU > > > 2C4 with the > > > latest (official) SEABios available for this product, NanoBSD (FreeBSD > > > CURRENT FreeBSD > > > 12.0-CURRENT #60 r335278: Sun Jun 17 07:57:20 CEST 2018 amd64)is unable > > to > > > boot recent > > > OS at the first stage (GPT partitioning, SD card memory). > > > > > > Hi, > > > > > > My nanobsd images are based on : > > [root_at_apu2]~# uname -a > > FreeBSD apu2 12.0-CURRENT FreeBSD 12.0-CURRENT r335286M amd64 > > > > And I don't remember to have upgraded its BIOS: > > [root_at_apu2]~# kenv smbios.bios.reldate > > 03/07/2016 > > [root_at_apu2]~# kenv smbios.system.product > > apu2 > > > > But I'm using MBR partitionning on a mSATA disk. > > > > Do you know the first version to have this problem? Are you using geli? > > Warner > > > Hello, if you addressed me (wasn't so clear from your reply on Olivier Cochard-Labbé's reply to me), I could give you this information (I posted it to Allen Jude in response to svn commit: r335254 - in head/stand/i386: libi386 zfsboot probably the wrong commit. Please allow me to copy-paste: [...] I realised that CURRENT r335222 from Friday, 10th June 2018 booted without problems (NanoBSD, slightly modified to boot off GPT/UEFI partitions, but in general a simple "gpart bootcode -b pmbr -p /boot/gptboot -i 2 mmcsd0" preparation of a dd'd image). Another try with recent r335282 on a APU 2C4, freshly build NanoBSD, fails to boot firststage: the (most recent) SEABios stopps for ever at telling "Booting from hard disk"; were usually a carret starts to spinn there is vast emptyness. Preparing the boot partition with an older bootcode on that very same SD card via "gpart bootcode -b pmbr - - -p /boot/gptboot -i 2 mmcsd0" with an older booted image of CURRENT has solved the problem. The layout of the SD card is as follows, just for the record: #: gpart show mmcsd0 => 40 60751792 mmcsd0 GPT (29G) 40 1024 2 freebsd-boot (512K) 1064 2205944 3 freebsd-ufs (1.1G) 2207008 2210127 4 freebsd-ufs (1.1G) 4417135 1048576 5 freebsd-ufs (512M) 5465711 55286121 - free - (26G) [...] I didn't bi-sect the issue du to time constraints, but if it helps, I could try. I resolved the problem temporarely by writing the bootcode and partition code from an older image. The APU is serial console only. Kind regards, Oliver Hartmann - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWyfUjQAKCRDS528fyFhY lJZ6AfwOeHnA01kpMxQgEtkIaoCYGoa1wetyss1HvkJj/kolplwJT9mVRKypLjZb CWxS+ldHyy2lhs9Q1dIrrm64TfVbAgCAc3oZyuOtzoO9+CbMopmUwt5FqFBGn/b0 AI7w7mVu+EzWww/Qx/73E98j6LtZIjB8jpHGc0lqlpDwD6HL5IHt =mFD0 -----END PGP SIGNATURE-----Received on Mon Jun 18 2018 - 13:49:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:16 UTC