On Wed, Jul 13, 2022 at 01:39:45PM +1000, Paul W. Rankin wrote:
> On 2022-03-16 01:18, Tom Szilagyi wrote:
> > After installing and playing with OpenBSD on the Pinebook Pro for a
> > couple weeks, I have collected a stack of patches to improve things a
> > little bit. I recently published them with lots of context (that I do
> > not want to flood the list with) here:
> >
> > https://tomscii.sig7.se/2022/03/Patches-for-OpenBSD-on-the-PinebookPro
> >
> > As described therein, I believe most patches are not appropriate for
> > upstreaming, but are rather intended as a demo of where the issues
> > lie. The desired end state is to have appropriate fixes in upstream;
> > please let me know if you have any ideas on how I can help make that
> > happen.
>
> Much love to Tom for all his efforts getting OpenBSD into a user-friendly
> boot state on the Pinebook Pro.
>
> I would like to follow Tom’s blog post and build a release for my PBP.
> Unfortunately the serial cable from Pine64 is not functional (widely
> reported to be manufacture defect) and I see that cross-compiling is not
> intended for general use, which stymies my desire to do just that using my
> amd64 OpenBSD VPS.
>
> This message then is more to enquire on what the temperature is on the
> patches listed in Tom’s blog post -- i.e. are OpenBSD devs aware of the
> patches here, and how enthusiastic is anyone on these getting closer to
> upstream? (Apologies if these are dumb questions.)
>
> Otherwise, I speculate I could patch & compile a release using
> qemu-system-aarch64 on my macOS system, however attempts at even getting an
> OpenBSD guest system running have made me feel rather stupid -- if anyone
> can point me toward any guide (the -h flag output is almost useless) I would
> much appreciate it.
>
You will be waiting a long, long time for that to finish. But here you go:
ulimit -d 8388608
qemu-system-aarch64 \
-machine virt \
-smp 4 \
-m 4096m \
-cpu cortex-a72 \
-drive
if=pflash,format=raw,file=/usr/local/share/qemu/edk2-aarch64-code.fd,readonly=on
\
-hda install71.img \
-hdb openbsd-arm64.qcow2 \
-netdev user,id=usernet -device virtio-net-pci,netdev=usernet
use a disk based install from sd0->sd1 then make hda the .qcow2 file on the
next boot. You can make the .qcow2 with vmctl create or qemu-img.
This is going to be so ridiculously slow though, that you probably would be
better off buying a Raspberry Pi and building there (or better, Mac M1 with
OpenBSD installed).
