Hacker News Reader

Comment by fps_doug | Hacker News Reader

Bayfail was utterly broken on Linux until two years ago or so. There is a bugzilla entry with more than 1000 replies. And it appears that some platforms with that CPU still have issues with Linux, which according to that issue is yet another bug.

View on HN

The biggest problems I had with Bay/Cherry is because they are 64bit processors but have 32bit UEFI. So the distro has to be able to install a 64bit version but from a 32bit UEFI. Most of the "mini PC" that came with those Atoms came with a 32bit Windows preinstalled, I assume for the same reason. Some distributions like AntiX, MX Linux, and Void Linux, can boot 64bit OS from 32bit UEFI.

Also WiFi/Bluetooth can be problematic when they are on SDIO, in my personal experience. Which anecdotally for me was about 50% of the time.

That might be why some manufacturers decided to disable 64-bit support on them, which as it turns out, is another MSR you can do a BIOS mod to unlock.

What does its compatibility with Linux have to do with how good it was as a chip?

Strictly technically speaking, not much, however having working Linux Open Source drivers extends the life of the product using it well beyond the point Microsoft, and/or the hardware manufacturers, declare it obsolete then stop any further development for that chip. There's a huge number of old systems out there that are supported by mainline Linux but couldn't run anything newer than Windows XP or 7, and they aren't just laptops. If you have put some money into a piece of hardware that still works perfectly and are forced to ditch it because either its manufacturer or Microsoft suddenly say "sorry, no more drivers, but here's an offer for the new model", that definitely sucks.

Reply on news.ycombinator.com