Modern 13 powerpc64 FreeBSD with kern.vty=sc has early-fail boot for 2-socket/1-core-each PowerMac7,2 G5

[Mark Millard]

On 2021-Jan-15, at 18:10, Mark Millard <marklmi at yahoo.com> wrote:

> [For the modern FreeBSD tests, This turned out to be the
> 32-bit powerpc disk being put in the 2-socket/1-core-reach
> G5 each time. So I cut the material below to the basics of
> the early failure for an attempted 32-bit boot.]
> 
> On 2021-Jan-14, at 22:50, Mark Millard <marklmi at yahoo.com> wrote:
> 
>> On 2021-Jan-14, at 17:39, Mark Millard <marklmi at yahoo.com> wrote:
>> 
>>> On 2021-Jan-13, at 14:35, Mark Millard <marklmi at yahoo.com> wrote:
>>> 
>>>> I attempted [using the 32-bit powerpc FreeBSD] with the [. . .]
>>>> 2-socket/1-cores-each G5 that I have access to. It
>>>> silently hangs up almost immediately after the loader's timeout
>>>> prompt is "returned to" (or finishes the timeout). This happened
>>>> for both vt and sc for kern.vty .
>>>> . . .
>>> 
>>> . . . it stops on the 2-socket/1-core-each G5 after . . . :
>>> 
>>> Kernel entry at 0x100580 ...
>>> 
>>> So this is a very early failure.
>> 
> 
> Using the actual powerpc64 FreeBSD media booted the
> 2-socket/1-cores-each G5 just fine.

Well, for powerpc64,  . . .

A) Using kern.vty=vt booted the 2-socket/1-cores-each G5 just fine.

B) Using kern.vty=sc stopped after the "Kernel entry at . . ." message.
   (This behavior with sc is not new, it is very old in fact.)

(The iMac G3 boots with sc and fails to do so with vt: blank
screen very early on.)

These are as of:

# ~/fbsd-based-on-what-freebsd-main.sh mm-src
818390ce0ca539300dd15d7a817784f1e3f7a9b8
CommitDate: 2021-01-13 14:54:46 -0800
4180404713ec 818390ce0ca5 (HEAD -> mm-src) mm-src snapshot for mm's patched build in git context.


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)