Date: Sun, 24 May 2020 19:08:30 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: Mark Millard <marklmi@yahoo.com> Cc: greg@unrelenting.technology, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <fn58k-44ZAkuwnDdytVzV-cLaB9amYMgZWydbpR_muUcKNZwohKqn9zFxqqw_Vz8Ij8L8yOSv0XhefrcTSo_bSYSOe5_7wcjoBWl8Q2dDVM=@a9development.com> In-Reply-To: <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> References: <YI70eszO0ei1z8fnsDWQ7Cwt9u63BkXvIDMcBQ0XYj6gwcloNfare1sgktdUeO9cgby8KQk8v7EVqIOVigIwlnrPlcFDYAxgEJKcbZUyi2w=@a9development.com> <f801aa134da12d1b4a34b87dbc180b4a@unrelenting.technology> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Also, to rule out firmware bugs, would be good to test Linux and NetBSD= with the same firmware. > > (with NVMe, it's something that would definitely get attempted at boot) > > NetBSD -CURRENT: http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/i= mages/NetBSD-9.99.63-evbarm-aarch64.iso > > They don't have memstick images for arm, unfortunately -- idk whether d= d'ing an iso image to a usb drive > > would boot, probably not, try tools like rufus maybe. > > John McNeill appears to have: > > https://www.armbsd.org/arm/ > > for "NetBSD Arm Bootable Images". > > It has 32 NetBSD 9 images and 33 NetBSD -current images. > > One is called: Generic 64-bit > for each. NetBSD -current has: > > Build: 202005232000Z > > (so yesterday's build) and NetBSD 9 has: > > Build: 202005222300Z > > (so the day before yesterday). > > Might one or both of those be appropriate? > > > Or assemble your own memstick with what I assume is just the root files= ystem image: > > http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch64/bin= ary/gzimg/arm64.img.gz > > plus the boot loader you'd have to place on the EFI partition manually > > http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch64/ins= tallation/misc/bootaa64.efi > > =3D=3D > > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) Booted with NetBSD -current Generic 64-bit Build: 202005232000Z SHA256: c64278c292489674215f9ecd335f2cbf01b99c2886f03a76b24415cd1c24d255 https://gist.github.com/agrajag9/6f2c986c99fbca413e60cf608a453a00 Found the onboard eMMC (sdmmc1), so that's nice. But it panicked with the S= AS HBA attached. Removed it and wired a drive straight up to the SATA ports= , but fdisk doesn't like it. Smelling more like a firmware problem now...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fn58k-44ZAkuwnDdytVzV-cLaB9amYMgZWydbpR_muUcKNZwohKqn9zFxqqw_Vz8Ij8L8yOSv0XhefrcTSo_bSYSOe5_7wcjoBWl8Q2dDVM=>