Date: Mon, 18 May 2020 15:04:16 +0000 From: myfreeweb <greg@unrelenting.technology> To: Dan Kotowski <dan.kotowski@a9development.com> Cc: John-Mark Gurney <jmg@funkthat.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <BB317821-62C7-416E-83E6-69101A64E9A3@unrelenting.technology> In-Reply-To: <_lvahpuNQE69s4KpHud6ANL6yzL3RCVI-MTyB0_J_ULyW-3UWsqAXnm5gfoFcOyvfRQRabZk4Z4bQgyp15a001kA-WcvsvnWcjqgMBkgGTY=@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 18, 2020 2:34:35 PM UTC, Dan Kotowski <dan=2Ekotowski@a9development= =2Ecom> wrote: >> > The 12=2E1 aarch64 memstick installer iamge fails out trying to mount= the UFS partition and drops into the mountroot> shell with error 19=2E Lis= ting GEOM managed disk devices returned an empty list=2E >> >> What devices does the boot log show? No xhci I guess, how about pci, sd= hci? > >Does this answer your question? https://gist=2Egithub=2Ecom/agrajag9/ce11= 07a1962283b64205bc8f35123a5c > >If not, I'll happily run what's needed to get you something better=2E No, the interesting part is the kernel boot log (dmesg) =E2=80=93 the one = where you saw the mountroot prompt! > Load Device: eMMC(0xCA) huh, wait, where was the memstick image written to again? >> Please don't waste time on u-boot=2E > >Any particular reason? Most of SolidRun's documentation is based on u-boo= t, the online documentation from u-boot and the in-console help lines have = been much easier to follow, and I'm finding it has a lot more capability to= interact with the underlying systems - e=2Eg=2E reading/writing arbitrary = blobs from/to memory/disk=2E u-boot does not support ACPI, and only ACPI is appropriate for running non= -Linux OSes on this hardware=2E Upstream development is focused on EDK2 with ACPI and approaching SBSA com= pliance=2E People have managed to run OpenBSD, NetBSD, and Windows=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BB317821-62C7-416E-83E6-69101A64E9A3>