Date: Mon, 18 May 2020 15:36:37 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: myfreeweb <greg@unrelenting.technology> Cc: John-Mark Gurney <jmg@funkthat.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <cjE8j_Tehwtmk7Aw0hzP-EZxwfAQC4ywIrgcqrarkCiRI_X5kacVsJHpaX_SMO9QHVCqfEdJH45eC4AE2cwzfx9nmHzWbhE7M-h09hDe8MA=@a9development.com> In-Reply-To: <BB317821-62C7-416E-83E6-69101A64E9A3@unrelenting.technology> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > The 12.1 aarch64 memstick installer iamge fails out trying to mount= the UFS partition and drops into the mountroot> shell with error 19. Listi= ng 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/ce1107= a1962283b64205bc8f35123a5c > > If not, I'll happily run what's needed to get you something better. > > No, the interesting part is the kernel boot log (dmesg) =E2=80=93 the one= where you saw the mountroot prompt! Better? https://gist.github.com/agrajag9/9a69b5baff70c8c1040fabeebd037214 2 files to truncate the >100 empty lines dumped to the console between them= . > > Load Device: eMMC(0xCA) > > huh, wait, where was the memstick image written to again? Artifact of a Layer 8 failure, you can ignore that console output... > > > Please don't waste time on u-boot. > > > > Any particular reason? Most of SolidRun's documentation is based on u-b= oot, the online documentation from u-boot and the in-console help lines hav= e been much easier to follow, and I'm finding it has a lot more capability = to interact with the underlying systems - e.g. reading/writing arbitrary bl= obs from/to memory/disk. > > u-boot does not support ACPI, and only ACPI is appropriate for running no= n-Linux OSes on this hardware. > > Upstream development is focused on EDK2 with ACPI and approaching SBSA co= mpliance. People have managed to run OpenBSD, NetBSD, and Windows. Noted, I'll stick to UEFI then.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cjE8j_Tehwtmk7Aw0hzP-EZxwfAQC4ywIrgcqrarkCiRI_X5kacVsJHpaX_SMO9QHVCqfEdJH45eC4AE2cwzfx9nmHzWbhE7M-h09hDe8MA=>