Why should I trust 'MrChromebox' firmware? I trust Google more than some rando side project on GitHub.
Why should I trust 'MrChromebox' firmware? I trust Google more than some rando side project on GitHub.
The project has been around about 10 years. I think it if was not trustworthy we probably would have heard something by now.
I remember using the SeaBIOS firmware from them around 2014. Since then I've updated all machines to the UEFI firmware and now they can even boot Windows. I run the latest Fedora distribution on all of them and they work fine.
That ship sailed a long time ago.
Look, being able to look at the source of truth is the best you can hope for. Moreover, the project has been around for some time. If that's not enough, then fair, at the end of the day the choice is yours.
For more detail, I point you toward the fine documentation
* git clone https://github.com/MrChromebox/coreboot.git
* cd coreboot
* git submodule update --init --checkout --recursive
* make crossgcc-i386
* ./build-uefi.sh <name of board to build>
Before COVID hit, I used his firmware and ~20 1st Gen Asus/HP Chromeboxen (upgraded RAM to 16G and 128/256GB SSD replacements, i7-4600U Haswell, cases stripped off and heatsinks added to the new SSDs) to create a physical K8s lab.
I no longer need to run that kind of lab, but I still use those a few of those nodes for running services at home. Proxmox/Docker/K8s/Win Server/etc, a bit more power draw, but x86-64 and since they "expire", you'll see a periodic flood of devices to places like eBay.