From owner-freebsd-arm@freebsd.org Mon May 18 17:05:23 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 10B092CFF47 for ; Mon, 18 May 2020 17:05:23 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49Qlkn3XR9z42n9 for ; Mon, 18 May 2020 17:05:20 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1589821519; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=U7Z5/FTjths8wDfAHd+gEgx1lRXCfuLKMxsGZnP8K2s=; b=IEucq4aTzYGX7lhJhjBAW1nEj48FMvWQzVlllJzt9EIA4ls1whAh71nk2YaUSdwa8ZHELK BB3ax+bYRJuQ68uJCKGJmr7zEd4vJXm69l/soxaNsz8HJ8yg3VuEhXmCbG8WPSo3Gr7O81 5nh7SvosgGw9sPzDTfuevCtAQtk9t9Q= Date: Mon, 18 May 2020 17:05:17 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: <63b4f78ff4ee07359a345bcbc03afeaa@unrelenting.technology> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "John-Mark Gurney" , freebsd-arm@freebsd.org In-Reply-To: <9UQiT9Df6hGA9k3-pzwpHifFsu7BVL2zFGOqDsnGva556e8nyvrKPp5XnKWxksvEKx1bpD-dnuYw8VCGiP9Z_kHc6tDFJcmRXzeJqLbo-yo=@a9development.com> References: <9UQiT9Df6hGA9k3-pzwpHifFsu7BVL2zFGOqDsnGva556e8nyvrKPp5XnKWxksvEKx1bpD-dnuYw8VCGiP9Z_kHc6tDFJcmRXzeJqLbo-yo=@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> <7F9D7164-2C04-4E27-85F9-A495EAC8FC84@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49Qlkn3XR9z42n9 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=IEucq4aT; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-1.47 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.47)[-0.473]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2020 17:05:23 -0000 May 18, 2020 7:11 PM, "Dan Kotowski" 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