Date: Sun, 1 Dec 2019 13:32:10 -0800 From: Mark Millard <marklmi@yahoo.com> To: Greg V <greg@unrelenting.technology> Cc: Robert Crowston <crowston@protonmail.com>, freebsd-arm@freebsd.org Subject: Re: Problems booting a MACCHIATObin Double Shot Rev 1.3 with head -r335027 Message-ID: <366042EF-094B-4E7D-9582-256C5379DA20@yahoo.com> In-Reply-To: <8B89ADF5-FA8B-4EB9-B2CC-CFBF017A8BD7@yahoo.com> References: <32A4EC20-53AA-4985-BD93-34DA5FC270E8@yahoo.com> <C5CAD1EC-52E0-4952-87DA-D6E0F20EB7EA.ref@yahoo.com> <C5CAD1EC-52E0-4952-87DA-D6E0F20EB7EA@yahoo.com> <ydCU-MIAsoAlrNW81KZUmAahyQsWbeD49hg2MbS03xvqqZ8eDljPVRb_8aHGpGdBDbvwosY_ABZgcVzB1RyC903KD9RuyXMUybaRVK7NWcw=@protonmail.com> <e0e0f3b2e7d25b6a1dfc109fe489c254@unrelenting.technology> <8B89ADF5-FA8B-4EB9-B2CC-CFBF017A8BD7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Dec-1, at 12:45, Mark Millard <marklmi at yahoo.com> wrote: > [Mixing materials from 2 emails that came in.] >=20 > On 2019-Dec-1, at 12:18, greg at unrelenting.technology wrote: >=20 >> December 1, 2019 10:46 PM, "Mark Millard via freebsd-arm" = <freebsd-arm@freebsd.org> wrote: >>=20 >>> Note that edk2 is for UEFI. It is configurable for if it hands over >>> a dtb vs. ACPI information. Trying ACPI just got a report of the >>> dtb being missing. So I continued with the dtb option. >>=20 >> dtb missing is *correct* with ACPI :) >=20 > Yep. But: >=20 > A) The older FreeBSD got as far as did using dtb, not ACPI. > (Not that I'd tried ACPI then.) So my best evidence of > progress was with dtb. > B) It looked like FreeBSD materials were reporting an error > and possibly stopping because of it. >=20 > Not being familiar with what to expect beyond what I was > seeing, I went with dtb after that message showed up. >=20 >>>> You can also enable verbose boot, which might show a tiny little = more detail before the hang, but >>>> since we don't get to --<BOOT>--, I am not optimistic. >>=20 >> Yep, not getting --<BOOT>-- pretty much always means the serial = console is not configured correctly. >=20 >=20 > On 2019-Dec-1, at 12:16, greg at unrelenting.technology wrote: >=20 >> Have you tried connecting a GPU and monitor instead? :) >=20 > No GPU around to plug in. (No original intent to use a GPU > either.) >=20 >> Have you tried ACPI instead of DTB? (in setup, Device Manager - O/S = Hardware Description) >=20 > Yep. It did not work either. See above. >=20 >> Actually on Marcin's builds the serial console might not work with = that >> because the SPCR table there is intentionally wrong to support Linux, = but the links >> below should be my builds, you can try ACPI with them (they also = remove a >> PCIe hack for supporting "~legacy" devices to make other devices >> like the Radeon RX 480 work). >=20 >=20 > Thanks. That gives me another direction to try. >=20 > What is the distinction between the two .bin files? > Should I try both even if the first I try works? Is > there something of interest to be learned? With changing to ACPI with flash-image2.bin mostly worked and did boot to multi-user (dtb failed the same old way): # uname -apKU FreeBSD FBSDmacch 13.0-CURRENT FreeBSD 13.0-CURRENT #14 r355027M: Sat = Nov 23 03:58:57 PST 2019 = markmi@FBSDFHUGE:/usr/obj/cortexA72_clang/arm64.aarch64/usr/src/arm64.aarc= h64/sys/GENERIC-NODBG arm64 aarch64 1300061 1300061 But the console output for the boot has a large hole in it: . . . Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... No valid device tree blob found! WARNING! Trying to fire up the kernel, but no device tree blob found! !!!! LOTS OF STUFF MISSING HERE. !!!! Setting hostuuid: 7c431ce3-c871-11e8-974a-e0fff70020ed. Setting hostid: 0x22ac6547. Starting file system checks: /dev/ada0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0p2: clean, 189820987 free (59587 frags, 23720175 blocks, 0.0% = fragmentation) Mounting local filesystems:. . . . I do not know what to do to get, say, the slower speed EtherNet going, or if I can. But the serial console seems to be working fine once it starts going. FYI: Making no adjustments (such as to ACPI) failed in two different ways, one per .bin: dd if=3D/root/flash-image.bin bs=3D512 seek=3D1 of=3D/dev/da3 conv=3Dsync produced a uSD card that resulted in: ASSERT_EFI_ERROR (Status =3D Device Error) ASSERT [PciHostBridgeDxe] = /home/greg/src/github.com/tianocore/edk2/Build/Armada80x0McBin-AARCH64/REL= EASE_CLANG38/AARCH64/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciHostBridgeDx= e/DEBUG/AutoGen.c(436): !EFI_ERROR (Status) dd if=3D/root/flash-image2.bin bs=3D512 seek=3D1 of=3D/dev/da3 conv=3Dsync= produced a uSD card that resulted in: Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Using DTB provided by EFI at 0xbe7e4018. (stopping at the same place/way as my original report, at least for what is visible on the serial console). Thanks! =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?366042EF-094B-4E7D-9582-256C5379DA20>