4 ms·
>It's got an AMD APU and apparently FreeBSD has zero support for it. When's the last time you tried. I don't remember if I've run FreeBSD on it, but I have a c
by non-entity 7y ago
>It's got an AMD APU and apparently FreeBSD has zero support for it.
When's the last time you tried. I don't remember if I've run FreeBSD on it, but I have a cheap board with an AMD APU that's run NetBSD within the last year.
> I've never been able to get FreeBSD fully working on a laptop. Something is always broken (usually WiFi)
Yeah WiFi support is super shaky seemingly across all BSDs. I had to make a small patch to an existing kernel driver to get it to work with one of my Realtek cards in FreeBSD. To my knowledge the same card will cause panics in NetBSD when the driver is attached and I have an Intel WiFi card broken in DragobflyBSD.
- giantrobot 7y ago> When's the last time you tried. I don't remember if I've run FreeBSD on it, but I have a cheap board with an AMD APU that's run NetBSD within the last year. It's been two or three years since I last bothered. While FreeBSD's support for the board might be better there's no real upside for me to even try installing it. The router box has been happily running in a closet for years. Best case scenario is it does exactly what it does now with minimal effort on my part. It's not worth the effort. This is my common refrain whenever I think about using FreeBSD for a project. I'll most likely end up with some set of things I need to fix or debug. Each problem then saps my time, motivation, and patience. It's an order of magnitude easier to just use Linux and save my energy for interesting parts of a project.