Date: Mon, 18 May 2020 19:23:14 +0200 From: Marcin Wojtas <mw@semihalf.com> To: Dan Kotowski <dan.kotowski@a9development.com> Cc: myfreeweb <greg@unrelenting.technology>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <CAPv3WKdBPG-%2BNCzh5e3an12qaU%2BJF7P=Q5VSUG9aZ6Kc_%2BD7GQ@mail.gmail.com> In-Reply-To: <9UQiT9Df6hGA9k3-pzwpHifFsu7BVL2zFGOqDsnGva556e8nyvrKPp5XnKWxksvEKx1bpD-dnuYw8VCGiP9Z_kHc6tDFJcmRXzeJqLbo-yo=@a9development.com> References: <seVuHXPQIJwJasZ3wb2s2t61PcRQY5fyhT6njAvxEJ47Sj02pDtHbh-6EyHOf5M22BZdd27q4wK-zMPfCkJ2FIhFNnhILGxOQPebbQ19-0M=@a9development.com> <72D47662-240E-4851-844A-A4F92F18B3F2@unrelenting.technology> <20200516051207.GT4213@funkthat.com> <3nsQUg1Gm4VFYfpHVELk6PWaHyYNb3CoyoKnLV55_3VR48tr90bhaseG3sJg007L8czZ4mXUmR_YMQvYVdMbUs1bsoqGtZp5d17FqYT6b-o=@a9development.com> <7AFDA7E0-82EC-4CD2-BB03-B7E33D019EDA@unrelenting.technology> <_lvahpuNQE69s4KpHud6ANL6yzL3RCVI-MTyB0_J_ULyW-3UWsqAXnm5gfoFcOyvfRQRabZk4Z4bQgyp15a001kA-WcvsvnWcjqgMBkgGTY=@a9development.com> <BB317821-62C7-416E-83E6-69101A64E9A3@unrelenting.technology> <cjE8j_Tehwtmk7Aw0hzP-EZxwfAQC4ywIrgcqrarkCiRI_X5kacVsJHpaX_SMO9QHVCqfEdJH45eC4AE2cwzfx9nmHzWbhE7M-h09hDe8MA=@a9development.com> <7F9D7164-2C04-4E27-85F9-A495EAC8FC84@unrelenting.technology> <9UQiT9Df6hGA9k3-pzwpHifFsu7BVL2zFGOqDsnGva556e8nyvrKPp5XnKWxksvEKx1bpD-dnuYw8VCGiP9Z_kHc6tDFJcmRXzeJqLbo-yo=@a9development.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Dan, pon., 18 maj 2020 o 18:12 Dan Kotowski <dan.kotowski@a9development.com> napisa=C5=82(a): > > > > > > > > The 12.1 aarch64 memstick installer iamge fails out trying to= mount the UFS partition and drops into the mountroot> shell with error 19.= Listing GEOM managed disk devices returned an empty list. > > > > > > > > > > > > What devices does the boot log show? No xhci I guess, how about= pci, sdhci? > > > > > > > > > > Does this answer your question? https://gist.github.com/agrajag9/= ce1107a1962283b64205bc8f35123a5c > > > > > If not, I'll happily run what's needed to get you something bette= r. > > > > > > > > No, the interesting part is the kernel boot log (dmesg) =E2=80=93 t= he one where you saw the mountroot prompt! > > > > > > Better? https://gist.github.com/agrajag9/9a69b5baff70c8c1040fabeebd03= 7214 > > > > Oh, well that explains the lack of devices: > > > > > Using DTB provided by EFI > > > > Try choosing ACPI in the UEFI setup menu if that's available. > > And/or setting kern.cfg.order=3Dacpi in the FreeBSD loader menu / /boot= /loader.conf > > I couldn't find any options regarding ACPI in the UEFI menus, so I tried = using `set kern.cfg.order=3Dacpi` but that still failed in the same way. > > https://gist.github.com/agrajag9/2fa73fc21bff10c9bee9eba810ea283d > > I also included the output from running some of the diagnostic UEFI shell= commands in case that helps. And I have the compiled DTB on hand if that h= elps as well. > Did you try to change the relevant variable (responsible for switching between ACPI and DT) via BootManager menu? Device Manager -> O/S Hardware Description Selection -> <Device Tree/ACPI> (F10 to save and then reset, so that it's taken into account when loading the ACPI modules modules)? It should work this way if it's done in a generic way, I haven't studied SolidRun's edk2-platforms code much yet. Please let me know if it helped. Best regards, Marcin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPv3WKdBPG-%2BNCzh5e3an12qaU%2BJF7P=Q5VSUG9aZ6Kc_%2BD7GQ>