The upside of a Chromebook is that the user never has to worry about hardware specifications, applications minimum requirements, or any of the typical headaches of computer ownership. It’s all handled through the Chrome browser. The downside of a Chromebook is that the user is not allowed to install traditional computer applications. Or at least, not by default. Under the hood, Chrome OS runs a Linux kernel, and it’s possible to use that as a foundation to extend computing experience outside the walled garden of Chrome OS. I started learning about Crouton, a project using
chroot capability of Linux kernel to allow a variant of Ubuntu or Debian to run on Chromebooks.
Documentation for Crouton referenced the Crostini project, a way to get a Linux shell and container support without putting a Chromebook into developer mode. It sounds like a great thing to try first! But unfortunately this particular Chromebook is not supported. More specifically, this Chromebook hardware generation with the code name ‘Swanky’ does not meet the hardware virtualization support required for Crostini.
Especially frustrating is the explanation that, while the Intel spec sheet says the Celeron N2840 has the required hardware virtualization support, ‘swanky’ Chromebooks actually use a special variant of the chip without such support. I guess it saved them some money at the time? Keeping in mind the original intent of Chromebooks, it made sense to cut out virtualization support. But that decision now cuts this laptop off from Crostini.
So no Crostini for this machine, back to looking at Crouton. And the next critical step is to switch this Chromebook into Developer Mode. Holding down
Refesh then pressing power, I can see the broken display is illuminated but the external monitor is not. It appears the recovery/developer mode menu is shown only on the built-in display, which I can’t read. And unlike the power wash menu earlier, the screen mirror key combination has no effect on the developer mode menu.
I searched online for a complete procedure to put this Chromebook into developer mode. Unfortunately all I found were”press control-D from recovery screen and follow menus” which isn’t helpful when I can’t read the screen!
It appears if I want to venture outside the Chrome OS sandbox, I have to look into screen replacement and the first step is investigating its removal.