O. Hartmann
2018-06-17 07:59:21 UTC
-----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).
Last known good image without boot issues is FreeBSD 12.0-CURRENT #52 r335222: Fri Jun 15
20:24:41 CEST 2018 amd64.
The issue is revealing itself by showing nothing but a static screen telling it is
booting from hard disk where usually the rotating indicator popps up.
Booting the APUwith my installation USB device and "gpart -b pmbr -p /boot/gptboot -i 2
mmcsd0" - which is a quite old image from December 2017 by the way, made the SD card
booting again - with r335278 now properly.
At the very moment, I do not dare to check whether the bootcode is broken on those boxes
I boot via MBR/GPTBOOT.
Can someone give me some hints how to check this further or is this issue already known?
Kind regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
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).
Last known good image without boot issues is FreeBSD 12.0-CURRENT #52 r335222: Fri Jun 15
20:24:41 CEST 2018 amd64.
The issue is revealing itself by showing nothing but a static screen telling it is
booting from hard disk where usually the rotating indicator popps up.
Booting the APUwith my installation USB device and "gpart -b pmbr -p /boot/gptboot -i 2
mmcsd0" - which is a quite old image from December 2017 by the way, made the SD card
booting again - with r335278 now properly.
At the very moment, I do not dare to check whether the bootcode is broken on those boxes
I boot via MBR/GPTBOOT.
Can someone give me some hints how to check this further or is this issue already known?
Kind regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).