Repository navigation
FAQ
Below are short answers to common questions raised on January 18, 2026. This page is intentionally blunt and practical.
FreeBSD -CURRENT accepts drivers that behave and complete the full lifecycle. ChaosBSD exists for drivers that work but are not ready for upstream yet. It is a staging ground, not a replacement.
Yes. ChaosBSD is a staging repo for FreeBSD driver bring‑up. The difference is that it lives in a full FreeBSD tree, resets often, and keeps history disposable so iteration stays fast.
Documentation is about provenance, not idealism. If a blob has no source, that must be stated. If a license is unclear, that must be stated. The goal is traceability and sanity, not purity.
For new purchases, yes: buy supported hardware. But this doesn't help when you inherit second-hand gear, work with embedded/legacy devices, or find a laptop that is perfect for your needs except the webcam or Wi-Fi isn't supported. ChaosBSD exists so that imperfect hardware can still be studied and made usable.
It isn't a joke, and it isn't a distro. It's a working area for driver progress. amd64 and arm64 are supported today; other maintainers can take RISC‑V and more as the project grows.
Because -CURRENT is not a staging area. It is for drivers that already behave correctly and are production‑quality. ChaosBSD is where incomplete work lives until it is ready.
You can still help. Panic logs, backtraces, error messages, dmesg output, PCI/USB IDs, and "what happens when I do X" reports are all valuable. I am still learning drivers too, and I will be documenting the workflow as we go.
Linux has out‑of‑tree driver efforts. ChaosBSD is specifically about FreeBSD drivers inside a full FreeBSD tree, with a fast reset/merge loop and a clear path to upstreaming.
No. The project exists to improve FreeBSD driver coverage and upstream quality, not to emulate Windows policy or branding.