Not all of the latest Chromebook news is happening at CES 2020, although the latest Chromebooks are appearing there. In fact, there’s some great news for Chromebooks that first launched in 2015: All nine Chrome OS devices running on the Intel Broadwell chipset are getting the ability to run Linux via Project Crostini.
A code commit from just a few days ago tipped the news with this description:
enable crostini on all BDW boards
samus already has crostini unconditionally enabled via this commit: commit 9da9edee2d44 (“Always use v4.14 kernel and audio config for samus”)
Enable it in the rest of the BDW systems.
The “BDW” in this case stands for Broadwell and these are the nine devices powered by that chipset:
- Acer C670 Chromebook 11
- Acer Chromebook CXI2
- Acer Chromebase 24
- Toshiba Chromebook 2 (2015 edition)
- Lenovo ThinkCentre Chromebox
- Google Chromebook Pixel 2015
- Acer Chromebook 15
- Dell Chromebook 13 7310
- Asus Chromebox CN62
The standout device here, at least to me, is the Google Chromebook Pixel 2015 as many folks still own and run that 2-in-1. In fact, that was the first of the Broadwell-based Chrome OS devices to get experimental Crostini support back on Chrome OS 77 as part of the “kernelnext” software effort. The eight other devices should be following suit soon.
Since the code commit just landed and the bug is listed as private, I can’t tell which Chrome OS release will include the change to add Crostini support to the above devices.
I did double-check the release log for Chrome OS 80 Dev Channel and didn’t find it there, however that release dropped back in December. With the code change being more recent, it makes sense that I didn’t find it.
I’ll keep an eye out for this in the next Dev Channel although it could already be present in the Canary Channel for Chrome OS. I’m at CES using the Pixelbook Go for coverage so I’m not about to throw Canary on my only current production machine. 😉
5 Comments
Chrome OS has had this for a little while. The problem is that when you enable and install Linux on a Chrome device it creates a virtual machine container for the Chrome OS which locks up nearly all of your existing storage for the Chrome side so if you want to use both OSs, you don’t have any storage for your Chrome OS anymore. This has been a known bug sense version 77 at least and they are tracking it and they support forum but I don’t see any near future resolution
I was wondering if there is any news on whether the Skylake/chell board will be getting Linux support anytime soon as well because they should.
Thanks
Great, but still no skylake. Many of us bought with the reasonable expectation that crostini would come to skylake. Doesn’t matter there are no guarantees, it’s a long story but it was a very reasonable expectation at the time.
That crostini is perpetually “Beta” and that we have no progress on skylake, no road map for when and whether it will come, etc. comes across as part of Google’s chaos and abandonment syndrome.
Why am I giving these guys all my personal data again?
I’d love to see google giving support to flatpak apps in chromebooks, all in the same store, seamless for the user…
Chromebook Pixel 2015 … 2-in-1? 🙂