Those chips are still botnet bugware though. I tried to boot an armv7 and the framebuffer didn't work right, just got a blank screen when the kernel loaded the wsdisplay driver. The screen works fine in u-boot, and on NetBSD. Anyway there's also no stuff like LibreOffice, Firefox, Chrome for OpenBSD/arm.
What is some good cheap desktop hardware that's compatible with openbsd...
Josiah Price
Jackson Clark
Turned out to be a problem with the old version of fvwm openbsd is shipping with. Doesn't work on twm either. But it works on cwm, and a newer fvwm. A bit disappointing.
Jose Scott
Thinkpad t440p here. Any issue regarding compatibility?
Brandon Sullivan
I have a G3 and prefer to get use out of it, which is why it runs MacOS 9.2.
Jose Parker
What web browser do you use?
Daniel Thomas
Those all exist in OpenBSD's ports collection. They may not be available as packages but can't you just build the port? Did you even know there is a difference between ports and packages?
Aaron Diaz
I have no idea about old PowerPC systems, but it would probably suck to build Firefox on an A20 or other commonly used ARM SoC.
Zachary Phillips
you're forgetting that this board is the most rtfm/not-normie tech site there is. I'm pretty sure as soon as mentioned his needs, some shitposter (that probably doesn't hold a tech job at all) will probably harp on about how 'botnet' something is.
Caleb Martin
The user you are replying to is correct. The state of ports and packages on non-x86 arches is bad and has been for at least five years.
The port's Makefile says "ONLY_FOR_ARCHS= amd64 i386"
mpv: Makefile says "BROKEN-powerpc = atomics detection fails"
firefox-esr: "ONLY_FOR_ARCHS = amd64 i386"
qtwebengine: "ONLY_FOR_ARCHS = ${CLANG_ARCHS} amd64". powerpc is a GCC arch.
IIRC webkitgtk4 doesn't build.
chromium and iridium haven't ever worked on ppc.
qtwebkit 5.9 is outdated but still packaged. Browsers based on that are the only option to satisfy his requirements, but I don't know of any in the tree and as a result I haven't tested it.