Date: Mon, 18 May 2020 17:05:17 +0000 From: greg@unrelenting.technology To: "Dan Kotowski" <dan.kotowski@a9development.com> Cc: "John-Mark Gurney" <jmg@funkthat.com>, freebsd-arm@freebsd.org Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <63b4f78ff4ee07359a345bcbc03afeaa@unrelenting.technology> In-Reply-To: <9UQiT9Df6hGA9k3-pzwpHifFsu7BVL2zFGOqDsnGva556e8nyvrKPp5XnKWxksvEKx1bpD-dnuYw8VCGiP9Z_kHc6tDFJcmRXzeJqLbo-yo=@a9development.com> References: <9UQiT9Df6hGA9k3-pzwpHifFsu7BVL2zFGOqDsnGva556e8nyvrKPp5XnKWxksvEKx1bpD-dnuYw8VCGiP9Z_kHc6tDFJcmRXzeJqLbo-yo=@a9development.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
May 18, 2020 7:11 PM, "Dan Kotowski" <dan.kotowski@a9development.com> wrote: >>>>>> 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 better. >>> >>> No, the interesting part is the kernel boot log (dmesg) – the one where you saw the mountroot >> prompt! >> >> Better? https://gist.github.com/agrajag9/9a69b5baff70c8c1040fabeebd037214 >> >> 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=acpi 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=acpi` but that still failed in the same way. > > https://gist.github.com/agrajag9/2fa73fc21bff10c9bee9eba810ea283d Same as in it still says "using DTB"? I wonder if that's the same weirdness I saw on the RPi4, FreeBSD failing acpi_find_table(ACPI_SIG_SPCR) even though the SPCR table is present and deciding we don't have ACPI.. You could try my current kernel which has has_acpi hardcoded to true (extract into the root of the memstick's ufs partition): https://send.firefox.com/download/c3d69444ce92d3cf/#AuYrYtDvJWNYbEeJWRX4fA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?63b4f78ff4ee07359a345bcbc03afeaa>