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> wro= te:=0A=0A>>>>>> The 12.1 aarch64 memstick installer iamge fails out tryin= g to mount the UFS partition and=0A>> drops into the mountroot> shell wit= h error 19. Listing GEOM managed disk devices returned an empty=0A>> list= .=0A>>>>> =0A>>>>> What devices does the boot log show? No xhci I guess, = how about pci, sdhci?=0A>>>> =0A>>>> Does this answer your question?=0A>>= https://gist.github.com/agrajag9/ce1107a1962283b64205bc8f35123a5c=0A>>>>= If not, I'll happily run what's needed to get you something better.=0A>>= > =0A>>> No, the interesting part is the kernel boot log (dmesg) =E2=80= =93 the one where you saw the mountroot=0A>> prompt!=0A>> =0A>> Better? h= ttps://gist.github.com/agrajag9/9a69b5baff70c8c1040fabeebd037214=0A>> =0A= >> Oh, well that explains the lack of devices:=0A>> =0A>> Using DTB provi= ded by EFI=0A>> =0A>> Try choosing ACPI in the UEFI setup menu if that's = available.=0A>> And/or setting kern.cfg.order=3Dacpi in the FreeBSD loade= r menu / /boot/loader.conf=0A> =0A> I couldn't find any options regarding= ACPI in the UEFI menus, so I tried using `set=0A> kern.cfg.order=3Dacpi`= but that still failed in the same way.=0A> =0A> https://gist.github.com/= agrajag9/2fa73fc21bff10c9bee9eba810ea283d=0A=0ASame as in it still says "= using DTB"?=0A=0AI wonder if that's the same weirdness I saw on the RPi4,= =0AFreeBSD failing acpi_find_table(ACPI_SIG_SPCR) even though the SPCR ta= ble=0Ais present and deciding we don't have ACPI..=0A=0AYou could try my = current kernel which has has_acpi hardcoded to true=0A(extract into the r= oot of the memstick's ufs partition):=0A=0Ahttps://send.firefox.com/downl= oad/c3d69444ce92d3cf/#AuYrYtDvJWNYbEeJWRX4fA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?63b4f78ff4ee07359a345bcbc03afeaa>