Earlier this year, a mysterious project appeared on the Chromium Git. The Chrome OS developers had created a new firmware branch of the Google Pixelbook called eve-campfire and were working on a new “Alt OS mode” for this branch. We have since confirmed this Alt OS refers to Microsoft Windows 10 and found evidence that it wasn’t just an internal project but intended for public release.
It’s been a few weeks since our last feature, we’ve got more interesting details to share.
The Google Pixelbook won’t be the only Campfire-enabled Chromebook
It would be fair to say that Alt OS and Campfire won’t make it to the hundreds of Chromebooks out there, but developer time would be wasted if this was only destined for the Google Pixelbook. Mentions of multiple “campfire variants,” and changes merging into the master branch instead of device-specific branches indicate that the Google Pixelbook won’t be the only Chromebook with Campfire support. However, given that support means putting devices through added testing and configuration, it could be limited to select Chromebooks—perhaps only new devices, or even only to Google-branded devices. It’s too early to tell.
Campfire won’t require enabling Developer Mode in Chrome OS
Dual-booting other OSes on a Chromebook traditionally requires enabling Developer Mode, an inconvenient yet powerful mode on Chrome OS that makes your Chromebook wipeable at the tap of a spacebar every boot. Unfortunately, enabling Developer Mode also renders your Chromebook less secure by disabling features like Verified Boot. As dual-booting on a Chromebook will be supported directly by Google, enabling Alt OS mode and booting into Microsoft Windows 10 won’t require Developer Mode.
Setting up Campfire to dual boot Windows 10 is seamless
The developers have reworked the way in which they distribute updates to a rarely-used section of ROM on Chromebooks called RW_LEGACY. The RW_LEGACY section on a Chromebook’s ROM traditionally gives users the ability to dual-boot into an alternative OS, but it is something of an afterthought during production and the section is rarely updated after a device leaves the factory. Now, with Campfire, Google will push signed updates to RW_LEGACY via the regular auto-update process, so firmware flashing won’t be a concern for Joe Public. A recent commit for enabling Alt OS through crosh with a simple [alt_os enable] command indicates that it will be a fairly easy setup process from the user’s end too.
Campfire is closer to release than you think
Campfire and Alt OS mode are visibly incomplete at this stage with no UI changes to speak of. However, the developers have been pushing fairly hard to get changes merged sooner rather than later, indicating a tight timescale on Chrome’s roadmap. Google’s hardware event is just around the corner, with rumours of a Google Pixelbook v2 featuring alongside the heavily leaked Google Pixel 3 and Google Pixel 3 XL. It would be reasonable to expect an announcement or demo at this event, even if the full functionality isn’t ready yet.