FreeBSD on Layerscape/QorIQ LX2160X

[Dan Kotowski]

> > 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/images/NetBSD-9.99.63-evbarm-aarch64.iso
> > They don't have memstick images for arm, unfortunately -- idk whether dd'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 filesystem image:
> > http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch64/binary/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/installation/misc/bootaa64.efi
>
> ==
>
> 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 SAS 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...