Date: Wed, 14 Nov 2018 18:15:08 +0100 From: Michael Tuexen <Michael.Tuexen@macmic.franken.de> To: Justin Hibbits <chmeeedalf@gmail.com> Cc: freebsd-ppc@freebsd.org Subject: Re: after running the installer on a PowerMac G5 no root filesystem found Message-ID: <C5D0E698-26F7-476D-ABB4-51812C0553D8@macmic.franken.de> In-Reply-To: <20181114110252.68fa2070@ralga.knownspace> References: <6f6d590b-02ef-ef9c-ed58-50121142e616@blastwave.org> <15F2B2EA-2129-46A8-BAAA-5AB8A9B6478B@macmic.franken.de> <806379E7-97EE-4977-B334-B3C53522F789@macmic.franken.de> <64612e49-7798-bf2a-44b6-56cfcd3b3e80@blastwave.org> <20181114110252.68fa2070@ralga.knownspace>
index | next in thread | previous in thread | raw e-mail
> On 14. Nov 2018, at 18:02, Justin Hibbits <chmeeedalf@gmail.com> wrote: > > On Wed, 14 Nov 2018 11:52:45 -0500 > Dennis Clarke <dclarke@blastwave.org> wrote: > >> <snip> >>>>> >>>>> At first boot I get a load of text and then a strange prompt that >>>>> seems to be asking where is the root filesystem? It also lists >>>>> all the various filesystems found. I tried to enter >>>>> ufs:/dev/adas2 and similar things but this gets me nothing but an >>>>> unrecognized filesystem message. >>>>> >>>>> So .. something obvious? >>>> Can you try setting the variable kern.smp.disabled to 1 at the >>>> loader prompt? >>>> If that helps, you can add >>>> kern.smp.disabled=1 >>>> to /boot/leader.conf >>> I meant /boot/loader.conf. >> >> To do that at all I would need to be able to get to the root >> filesystem. > > You can do it at the loader. > > set kern.smp.disabled=1 > boot > >> >>>> I had all sorts of problems until I disabled SMP on my G5 >>>> PowerMacs. Without SMP they are running very stable. >> >> So FreeBSD can not run on ye old IBM PPC970 units with multiple cores >> or multiple sockets? That sounds like a critical bug. > > It could until recently, due to my fault. I can revert the change that > caused it, but haven't yet, because I don't understand why it's causing I think I tried a kernel with you change reverted. It didn't fix the problem. I can try again, but at that time the problem was not only related to the one commit. Best regards Michael > the problem. And I'm pretty confident it's not causing the mountroot > issue (though, I was pretty confident it wouldn't cause any problem > anyway, but that turned out to be false confidence). > >> >> Dennis Clarke > > Can you somehow get a dmesg dump to post to the list? I'm very curious > to see what could be causing the problem you're seeing. > > - Justin > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org"home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C5D0E698-26F7-476D-ABB4-51812C0553D8>