The primary architecture on which I run #FreeBSD is:

[emaste@mastodon.social]

The primary architecture on which I run #FreeBSD is:

[mason@partychickens.net]

@emaste I'd really like to change my answer to say aarch64, but I just don't have that hardware yet.

Can you recommend something not crazily expensive that supports ECC RAM and that runs FreeBSD 14 (or 15) reasonably well?

Failing that, something without ECC is probably okay as a way to get into it, but I wouldn't want to use it for anything like production.

[bonkers@nerdculture.de]

@emaste oh, last time it was a 32bit x86

[geofftc@mas.to]

@emaste

Does the PS5 count?

[pauamma@mstdn.social]

@emaste Are you asking readers to guess what you use yourself, or asking us what we use?

[bsdphk@fosstodon.org]

@emaste

But I'd prefer to run on pretty much anything but that, since neither AMD nor Intel can be trusted with your data any more.

[vermaden@mastodon.social]

@emaste

I used RPI2 (arm32) ... or officially ARMv7 ... and most things worked ... but a LOT packages missing.

When I read about more recent (4/5) RPI models ... a lot LESS is supported ... I really have ZERO reasons to use RPI for anything.

RockChip is also an alternative ... but I will probably hit other problems.

1/2

[vermaden@mastodon.social]

@emaste

With current Mini PC market with AMD Ryzen (or Embedded) solutions for often less then $250 ... with case, power supply, and low power consumption, everything - I have exactly ZERO reasons to even try arm64 (aarch64).

2/2

[Guest]

@emaste 15 years ago I would have needed to vote sparc.

[bastillebsd@fosstodon.org]

@emaste voted amd64 but I decided last year that all new hardware will be arm64. Primarily for power reasons but also because I’m done with Intel.

[emaste@mastodon.social]

@pauamma What you use

[ianthetechie@fosstodon.org]

@mason @emaste same lol. Even workstation class hardware (no ECC required for me) is very difficult / expensive to source.