Date: Sat, 25 Apr 2020 15:22:21 +0000 From: greg@unrelenting.technology To: "Mark Murray" <markm@freebsd.org> Cc: "Marcel Flores" <marcel@brickporch.com>, freebsd-arm@freebsd.org Subject: Re: Bootable image for Macchatobin Double Shot? Message-ID: <e307725bcba79d7c9e0f122ebce26ff1@unrelenting.technology> In-Reply-To: <E2887392-01E4-4ECC-8D0A-4871657D5F8E@FreeBSD.org> References: <E2887392-01E4-4ECC-8D0A-4871657D5F8E@FreeBSD.org> <9F7FB8F8-A29C-4F95-B0BB-CFEFEAFDDD5E@FreeBSD.org> <1039B382-2CA4-4F49-9F95-08BD1386A447@FreeBSD.org> <CA07A9C8-267B-4657-B9D1-1F53B62A969B@brickporch.com> <092721df6b1de3e75820acd32ba1b0e7@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
April 25, 2020 5:51 PM, "Mark Murray" <markm@freebsd.org> wrote:=0A=0A>> = https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image.= bin=0A>> https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/fla= sh-image2.bin=0A> =0A> The second has the same binary bits as the one I d= ownloaded from the link in my original post.=0A=0AIt should work then..= =0A=0AUnless I really screwed something up and *somehow* this is not a go= od image -=0Ayou can check by running (as root):=0A=0A/usr/sbin/acpidump = -t -d -o /dev/null | grep -a -C10 PNP0C02=0A=0Athat should find the PCIe = controller in the DSDT table, its Memory32Fixed resource should=0Acontain= the address 0xE0000000, NOT 0xE0008000.=0A=0A=0AWhat does the pci comman= d in the EFI Shell say? Run `pci 00 00 00 -i` to get info about a particu= lar device,=0Ae.g. https://gist.github.com/myfreeweb/8b09f1c93ee9572aef01= 513ba9bf756f=0A=0AAlso, have you tried any other PCIe cards?=0A=0A> The f= irst fails with this at power-up:=0A=0AOh, okay, that's the bad one. Dele= ted.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e307725bcba79d7c9e0f122ebce26ff1>