Date: Fri, 15 Jan 2021 18:10:47 -0800 From: Mark Millard <marklmi@yahoo.com> To: Brandon Bergren <bdragon@FreeBSD.org>, freebsd-ppc <freebsd-ppc@freebsd.org> Subject: Re: Modern 13 32-bit powerpc FreeBSD has early-fail boot for 2-socket/1-core-each PowerMac7,2 G5 Message-ID: <857A6DB5-1EFD-4DD1-888F-3A08C94AF32F@yahoo.com> In-Reply-To: <88B7B643-8B34-479F-8D95-EB684650F488@yahoo.com> References: <C503A323-A82A-49E1-9F71-3155F9A30ADD@yahoo.com> <02EACD59-674C-49F2-8E68-D08A33BC4523@yahoo.com> <88B7B643-8B34-479F-8D95-EB684650F488@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[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. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?857A6DB5-1EFD-4DD1-888F-3A08C94AF32F>