Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Oct 2016 19:00:13 +0000
From:      Roger Leigh <rleigh@codelibre.net>
To:        Justin Hibbits <chmeeedalf@gmail.com>
Cc:        FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: Installer problems with 11.0-RC3
Message-ID:  <747f3eaa-251c-5740-0755-09bba55a5b04@codelibre.net>
In-Reply-To: <88b054f6-ae0b-dc32-8d54-016964a2cea8@codelibre.net>
References:  <725c6225-c7bf-f88f-d8e2-b5f9a02bcfe8@codelibre.net> <20160917184649.35d9a9ab@zhabar.knownspace> <88b054f6-ae0b-dc32-8d54-016964a2cea8@codelibre.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 18/09/2016 09:04, Roger Leigh wrote:
> On 17/09/2016 23:46, Justin Hibbits wrote:
>> On Sat, 17 Sep 2016 23:39:41 +0000
>> Roger Leigh <rleigh@codelibre.net> wrote:
>>
>>> Up until now, my G4 Mac Mini has been running 10.3-RELEASE.  Today, I
>>> tried the 11.0-RC3 installer.  Two issues noted:
>>>
>>> 1) The colours in the installer are different than the PC installer.
>>> The background is a mid brown with yellow text.  An issue with the
>>> console framebuffer?
>>>
>>> 2) It won't boot after the installer finished.
>>>      Invalid memory access at %SRR0: 018011f0    %SRR1: 00003030
>>
>> I just fixed the second issue, which should be going into the next ISO
>> (RC4? Final? Not sure at this point), but the initial commit was to
>> head at r305894, and finally merged to 11.0 (by way of stable/11) in
>> r305904 if you're curious.
>
> Super, thanks.  I'll retry this with the next ISO release.

I got the time to retry with the 11.0-RELEASE ISO, and the above problem 
is fixed, but unfortunately then hit a problem I'd previously seen and 
posted on the list when testing 11.0-STABLE in mid-September.  The 
kernel loads and boots correctly, but it hangs at this point:

   gem0: 10kB RX addr......
   gem0: Ethernet address .......
   cryptosoft0: <software crypto> on nexus0

At this point it just sits there with the CPU fan going full tilt.  I'm 
not sure what exactly the problem is here because I have no means to 
debug it that I'm aware of at that point during the boot.  Happy to 
investigate further if anyone could provide any hints about what I could 
do to assist.


Regards,
Roger



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?747f3eaa-251c-5740-0755-09bba55a5b04>