Hey, > Your "a while" warm up theory is bogus. Pi3b+'s (and pi3 for that > matter) work "immediately" after boot at full speed on other OSes, so > anything going wonky on there is likely between the driver and SoC.
This isn't bogus, OpenBSD spends a lot of time at boot relinking, and as far as I am aware after relinking enough to drop into the shell it will, and it will spend a minute or two linking in the background, this is why running syspatch directly after a reboot sometimes doesn't work, it tells you to wait until relinking is finished or something like that. (if my memory doesn't deceive me) When I first connect to the rpi over terminal it is non-responsive for a good 30 seconds, and if I leave it a few minutes it will start to work. I am aware OpenBSD driver support is a known issue with a lot of hardware, but I heard good things about rpi support, and I have run a rpi 4b on OpenBSD for almost 4 years now with minimal problems, so it is a shame that rpi 3b+ is being problematic. Take care, -- Polarian Jabber/XMPP: [email protected]
