Small correction: the AX211 card in the Framework 12 is able to connect to networks, not just scan. What you're missing is that a bunch of the Wi-Fi firmware blobs were removed from the base system between FreeBSD 14.2 and 14.3, and since 14.3 came out in June 2025 I assume that's what was tested. An upgrade from 14.2 to 14.3 would also have kept working, just not a fresh install of 14.3 or 15.0.
A user needs some other working network connection first. I used my Android phone's USB tethering — all that takes is a quick `dhclient ue0`. Then one can run `fwget` to get the firmware that will make the Wi-Fi work fully: https://man.freebsd.org/cgi/man.cgi?fwget%288%29
Source: very happy Framework 12 owner (currently dual-booting Windows 11 Enterprise and FreeBSD 15.0 + Wayland + KDE) :)
This is great. I've been checking on it periodically. I'm using the Framework 13 Ryzen AI 300 and the Framework Desktop so not quite there yet. Interested in taking FreeBSD for a spin when the support is there.
I can't speak to it driving a monitor over USB-C as I don't use one, but I'm currently running 15.0-RELEASE on a refurbished Dell Latitude 7280 that has worked flawlessly out of the box so far.
Somebody else did a nice writeup [0] on their experience with FBSD on the same laptop.
Apple's attitude towards other OSes running on their hardware is less "supportive" and more "barely tolerates". Also as a general rule Apple doesn't contribute much to open source outside of some high profile projects like Swift and Webkit.
MacOS was never based on BSD. Apple developed the USB drivers for BSP so they could copy it into their OS, but that very different from based on BSD. (It is likely some other parts are copied as well)
Any is a bit too strong. Apple has does (and still does) some useful work with clang/llvm, and a few other tools that BSDs use. However this is indirect at best.
Weird to see this downvoted, because it's totally true. Apple imports FreeBSD's userland periodically but not its kernel/drivers, and thus has nothing to do with how well FreeBSD works on PC hardware: https://wiki.freebsd.org/Myths#FreeBSD_is_Just_macOS_Without...
I would expect if anyone even considered it, they’d immediately reject the idea, as they clearly believe that Apple retains ownership of the computers they “sell” and should control the software you could run on them.
The table lists very limited support for M1 and not even lists newer variants! I guess it was only to be expected, asahi Linux also has challenges and of course FreeBSD has less eyeballs than Linux
(random anecdote) My first and last experience with FreeBSD laptop was trying to use 3.x (!) on a Dell Inspiron 3500 (PII-350 maybe?), no sound modules were precompiled or included or whatever. Took about 3 days for `make world` to finally finish rebuilding... and then sound still not work. Red Hat 6.x "just worked" in all regards.
Let me know when you can get a Dell XPS 13 (2024/25) working with FreeBSD out of the box without the need to hunt documentation down for the following.
- audio
- wifi
- biometrics
- GPU drivers that work well.
Do the biometrics work on Linux? Last time I had a laptop with a fingerprint reader the whole thing was controlled by some Broadcom thing that was hostile to anything not made by Microsoft. A fingerprint reader is a highly optional feature so it's not a problem if it is not working.
Yeah, I was also thinking of pointing out that I own a Dell XPS and AFAIK its fingerprint reader has never worked on Linux and the GPU is... well, it works these days, but Nvidia still isn't exactly the nicest thing on Linux.
My fingerprint worked out of the box on Linux Mint, as did NVIDIA Prime with the mobile 3080. Hibernation is historically (and still is) the main issue in linux land for me.
* And I believe those hibernation issues are related to corrupted graphics stacks because Nvidia, ha.
Unless you're trying to run your XPS on FreeBSD 3.x, I don't see what that has to do with either comment in this thread. Really really old OSs had problems. Current OSs also have problems, including that no OS supports all hardware, but I don't really see any connection between an anecdote about sound problems literally last century and missing drivers today.
Everything I mentioned many would consider to be essential parts of their system that should work, and would then fall under "Support and Usability" initiatives.
I guess I'm pointing out that his experience 20 something years ago is still relevant today, even if there's a lower barrier to entry now.
So, is there a laptop that has good support for FreeBSD support out of the box?
My requirements are: suspend/resume, being able to drive a 5K monitor over USB-C, wifi.
I found https://wiki.freebsd.org/Laptops but I don't know how up-to-date it is.
We’ve been working with Ed and team at FreeBSD on this, and have a document showing what works currently on Framework Laptops: https://github.com/FrameworkComputer/freebsd-on-framework
Small correction: the AX211 card in the Framework 12 is able to connect to networks, not just scan. What you're missing is that a bunch of the Wi-Fi firmware blobs were removed from the base system between FreeBSD 14.2 and 14.3, and since 14.3 came out in June 2025 I assume that's what was tested. An upgrade from 14.2 to 14.3 would also have kept working, just not a fresh install of 14.3 or 15.0.
A user needs some other working network connection first. I used my Android phone's USB tethering — all that takes is a quick `dhclient ue0`. Then one can run `fwget` to get the firmware that will make the Wi-Fi work fully: https://man.freebsd.org/cgi/man.cgi?fwget%288%29
Source: very happy Framework 12 owner (currently dual-booting Windows 11 Enterprise and FreeBSD 15.0 + Wayland + KDE) :)
This is great. I've been checking on it periodically. I'm using the Framework 13 Ryzen AI 300 and the Framework Desktop so not quite there yet. Interested in taking FreeBSD for a spin when the support is there.
I can't speak to it driving a monitor over USB-C as I don't use one, but I'm currently running 15.0-RELEASE on a refurbished Dell Latitude 7280 that has worked flawlessly out of the box so far.
Somebody else did a nice writeup [0] on their experience with FBSD on the same laptop.
[0] https://adventurist.me/posts/00352
I'm curious why Apple doesn't support this effort: they have done a lot of the work and it won't exactly harm their market share.
Apple's attitude towards other OSes running on their hardware is less "supportive" and more "barely tolerates". Also as a general rule Apple doesn't contribute much to open source outside of some high profile projects like Swift and Webkit.
I'm curious why you think Apple would support any effort that does not benefit their bottom line?
[delayed]
Users buying Macs to put BSD on them are less likely to buy things in the Mac App Store.
I still remember when MacOS being based on BSD had the community excited about the future
Interesting article on the failure of Darwin as an open source project: http://www.synack.net/~bbraun/writing/osfail.html
MacOS was never based on BSD. Apple developed the USB drivers for BSP so they could copy it into their OS, but that very different from based on BSD. (It is likely some other parts are copied as well)
Apple is struggling to make MacOS functional, why would they contribute engineering time to another OS?
Apple hasn't done any work that would be useful.
Any is a bit too strong. Apple has does (and still does) some useful work with clang/llvm, and a few other tools that BSDs use. However this is indirect at best.
Weird to see this downvoted, because it's totally true. Apple imports FreeBSD's userland periodically but not its kernel/drivers, and thus has nothing to do with how well FreeBSD works on PC hardware: https://wiki.freebsd.org/Myths#FreeBSD_is_Just_macOS_Without...
I would expect if anyone even considered it, they’d immediately reject the idea, as they clearly believe that Apple retains ownership of the computers they “sell” and should control the software you could run on them.
FreeBSD status on Apple Silicon, https://wiki.freebsd.org/AppleSilicon
The table lists very limited support for M1 and not even lists newer variants! I guess it was only to be expected, asahi Linux also has challenges and of course FreeBSD has less eyeballs than Linux
Linux is pretty much good to go on M1 or even M2 now. No joy on anything newer than that though.
(random anecdote) My first and last experience with FreeBSD laptop was trying to use 3.x (!) on a Dell Inspiron 3500 (PII-350 maybe?), no sound modules were precompiled or included or whatever. Took about 3 days for `make world` to finally finish rebuilding... and then sound still not work. Red Hat 6.x "just worked" in all regards.
I mean. Judging by 3.x, that was literally 25-27 years ago. Not sure what that has to do with the project that exists today?
Let me know when you can get a Dell XPS 13 (2024/25) working with FreeBSD out of the box without the need to hunt documentation down for the following.
- audio - wifi - biometrics - GPU drivers that work well.
Do the biometrics work on Linux? Last time I had a laptop with a fingerprint reader the whole thing was controlled by some Broadcom thing that was hostile to anything not made by Microsoft. A fingerprint reader is a highly optional feature so it's not a problem if it is not working.
Yeah, I was also thinking of pointing out that I own a Dell XPS and AFAIK its fingerprint reader has never worked on Linux and the GPU is... well, it works these days, but Nvidia still isn't exactly the nicest thing on Linux.
My fingerprint worked out of the box on Linux Mint, as did NVIDIA Prime with the mobile 3080. Hibernation is historically (and still is) the main issue in linux land for me. * And I believe those hibernation issues are related to corrupted graphics stacks because Nvidia, ha.
Unless you're trying to run your XPS on FreeBSD 3.x, I don't see what that has to do with either comment in this thread. Really really old OSs had problems. Current OSs also have problems, including that no OS supports all hardware, but I don't really see any connection between an anecdote about sound problems literally last century and missing drivers today.
Everything I mentioned many would consider to be essential parts of their system that should work, and would then fall under "Support and Usability" initiatives.
I guess I'm pointing out that his experience 20 something years ago is still relevant today, even if there's a lower barrier to entry now.
I still found it interesting and not worthy of the downvotes.