Date: Mon, 25 May 2020 00:58:39 +0000 From: greg@unrelenting.technology To: "Dan Kotowski" <dan.kotowski@a9development.com> Cc: "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <426b58bbea73305c52732e023ca2163c@unrelenting.technology> In-Reply-To: <PU1LOeii6s2eANBCYcXjsjv1XBLzoJxkbcciN4pIsjWI1B9ENZWSOGIGIYCvWtzg7YSvWnYoVL2CBjf-gBorqo3ju85HYX8YVVZk2a6j6w0=@a9development.com> References: <PU1LOeii6s2eANBCYcXjsjv1XBLzoJxkbcciN4pIsjWI1B9ENZWSOGIGIYCvWtzg7YSvWnYoVL2CBjf-gBorqo3ju85HYX8YVVZk2a6j6w0=@a9development.com> <fn58k-44ZAkuwnDdytVzV-cLaB9amYMgZWydbpR_muUcKNZwohKqn9zFxqqw_Vz8Ij8L8yOSv0XhefrcTSo_bSYSOe5_7wcjoBWl8Q2dDVM=@a9development.com> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <xoiJF1ZUP3-rgbxC8ZmJGQNpsJSyK4zsAXhbLl8Ml96Da1lBPGwPqn0ANf7q-GgthPAWePSR9QDCM5vKysd_3e2aGtp-0egUXu6AW3bhLDg=@a9development.com> <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com> <664db38a87ea8803be72af9738534994@unrelenting.technology> <b5105ce888b7a91eff50ec9118a910a8@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
May 25, 2020 1:05 AM, "Dan Kotowski" <dan.kotowski@a9development.com> wro= te:=0A=0A>> Booted with NetBSD -current=0A>> What was the panic? How abou= t with the NVMe drive?=0A=0A(is your mail client eating quote levels some= times? these shouldn't be both >>)=0A=0A>> I've sent a link to a known fi= rmware build before:=0A>> https://drive.google.com/file/d/1yXSS1O1U8Cmtwa= IPfxNDkzhAClJGvErK/view=0A>> Have you tried it? Any difference in FreeBSD= /NetBSD, with NVMe?=0A> =0A> Okay, lots of stuff here...=0A> =0A> https:/= /gist.github.com/agrajag9/7a1164387994cecea50170e2d93e257e=0A> =0A> 1. Th= e latest build didn't get far at all, no matter what hardware combo I thr= ew at it. Something=0A> about the GIC...=0A=0ASorry, silly error (missed = {}) when inserting debug prints all over the place.=0A=0ACould've tried t= he previous build with that firmware already ;) but new build, should be = fixed:=0A=0Ahttps://send.firefox.com/download/8b82b78a44456587/#KVNvzEyBb= iZJkJdhiPfbDg=0A=0A> 2. NetBSD was... non-deterministic? The first time I= tried booting it died real quick:=0A> =0A> But it sees the NVMe stick AN= D both the root sd card and the firmware sd card! And I was able to at=0A= > least read their geometries with fdisk! Progress!=0A=0AOkay so first of= all:=0A=0Adoes NetBSD's ability to work with NVMe change when you swap f= irmware between your build and the linked one?=0A=0A(repeat the experimen= t a couple times, we're doing Science here :D)=0A=0A> I also decided to j= ust go back to the stock u-boot + LSDK 19.09, just to grab the console ou= tput=0A> during boot. Sure enough, it does see the HDD and NVMe drives. I= tried it with the UEFI, but of=0A> course the Debian image I flashed was= MBR...=0A=0AUEFI supports MBR, generally (there is an MBR partition type= ).=0AActually the current FreeBSD/aarch64 images on Amazon EC2 are MBR (f= or no good reason lol)=0A=0AAnd Linux kernels often have the EFISTUB opti= on on, which means you can directly run the kernel as an EFI binary..=0At= hough an "LSDK" build might've turned that off. Also I'm not sure how tha= t works with the initramfs stuff that linux distros use.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?426b58bbea73305c52732e023ca2163c>