Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard

Am Sat, 9 Dec 2017 13:00:12 -0700
Warner Losh <imp_at_bsdimp.com> schrieb:

> On Sat, Dec 9, 2017 at 12:13 PM, Michael Tuexen <tuexen_at_freebsd.org> wrote:
> 
> > > On 9. Dec 2017, at 19:41, O. Hartmann <ohartmann_at_walstatt.org> wrote:
> > >
> > > Running a PCengines APU2C4 with FreeBSD Current, r326734, fails to boot,  
> > it gets stuck at  
> > > the very first messages on the serial console prompting
> > >
> > > Consoles: internal video/keyboard
> > >
> > > and then nothing more.  
> > I don't think it is a general problem with r326734. I'm running on the
> > same hardware
> > that revision (with some modifications to the TCP I'm testing):  
> > > uname -a  
> > FreeBSD nf3.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #31 r326734M: Sat
> > Dec  9 20:03:59 CET 2017     tuexen_at_nf3.testbed:/usr/home/
> > tuexen/head/sys/amd64/compile/TCP  amd64
> >  
> 
> Hi Michael,
> 
> What's your boot setup? BIOS vs UEFI? UFS vs ZFS? GELI? GPT vs MBR? Plants
> vs Zombies? And did you update your boot blocks or not?
> 
> Warner

All right, I got your point here, my bad, my apaologies.

I boot from a NanoBSD-prepared image residing on a SD card. The partiton scheme is GPT,
non UEFI (the SeaBIOS, latest version available for the APU2C2 available) doesn't support
UEFI. NanoBSD scripts (legacy.sh) has been modified to fit our requests.

The modifications target at most the creation of a GPT partition scheme layout,
installing boot/pmbr as bootcode and boot/gptboot on a freebsd-boot partition as well as
boot/boot1.efifat onto a dedicated efi-type partition. The UEFI partition is usually
created before(!) the freebsd-boot partition, but in this specific version, there is NO
EFI partition, only the gptboot containing partition. The binaries of the above mentioned
bootcode/efi code images are taken from the newly build world. I do not use boot0sio, the
portion where it is installed is excluded by some "if GPT; then" clause.

The last known-good version I reported in working is the image I backuped last time. I
lost the USB 2.0 flash device today containing the last version, that was not far from
r326218, the version that corrupted FreeBSD, I guess it was r326184, but I really do not
know and I havn't a backup of that image.

The buildworld process is maintained by a bunch of WITHOUT_ statements in a file driving
NanoBSD. This just for the record just in case FreeBSD build system changed
something significantly.

Building a world takes 90 minutes or more, so bi-secting the problem would be a pain in
the arse (that said, I imply that world and kernel need to be in sync).

I would appreciate hints or tipps where to look after or how to increase verbosity
especially at the first boot stage.

The PCengines APU with the most recent SeaBIOS isn't capable of booting FreeBSD from USB
3.0 devices. Even from USB 2.0 flashdrives working images fail at the boot loader with
"failed with error 19".

> 
> 
> 
> > Best regards
> > Michael  
> > >
> > > FreeBSD CURRENT FreeBSD 12.0-CURRENT #52 r324234: Tue Oct  3 11:00:53  
> > CEST 2017 amd64  
> > > works fine.
> > >
> > > What the heck has changed?
> > >
> > > 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).
> >
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> >  
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"



-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).