Chromebook

This guide details the generic part of installing Gentoo on a Chromebook

Developer mode
All Chromebooks have a so-called Developer Mode allowing to boot on something else than ChromeOS.

This mode allows to use the so-called Legacy Boot, which is a regular BIOS boot (booting from a MBR), this is NOT a UEFI boot.

Entering Developer Mode
The procedure is detailed here, find your model in the table and click on the link in the Model column.

Flashing the firmware
The stock firmware should allow the Legacy Boot, but is sometimes bugged, requiring flashing.

There are various levels of flashing available, the most basic just allows the Legacy Boot, while the most complex turns the Chromebook into a regular PC, completely wiping any trace of ChromeOS.

The whole procedure and its various options are all detailed on MrChromeBox's site

Installing Gentoo
Once you have the Legacy Boot working (or the UEFI boot if you flashed a full firmware), installing Gentoo is rather straight-forward: boot on a liveUSB and follow the Handbook as if installing on a regular x86_64 or arm machine.

Instructions for specific models

 * Acer Chromebook C720
 * Asus Chromebook C201
 * Google Chromebook Pixel LTE
 * Toshiba Chromebook 2

Layout
The layout is supported by Xorg The MatchProduct section might not fit your hardware, to check the correct name, use:

Missing Keys
Since some keys are missing, they are emulated with :

Extra Keys
is treated as a windows key (Super_L)

Multimedia Keys
The multimedia keys should works as expected, except:
 * (in the F4 spot) will be treated as
 * (in the F5 spot) will be treated as

When used with or  or, these keys will behave as

Example: + = +

How to reboot
Since there is no key, it is imposible to use ++. There is also no key, making it impossible to use the Magic Keys.

Fortunatly the firmware has a few keyboard shortcuts available:
 * for several seconds = power off
 * + = instant reboot

Stuck at the warning screen
Try using ++ to force a firmware reset

If that is not enough, follow the offical procedure

Unexpected reboot when coming out of suspend to ram
This can be caused by a missing TPM (Trusted Platform Module) driver in the kernel, see in Drivers → Character Devices

External resources

 * MrChromebox - Firmwares and firmware flashing tool
 * GalliumOS - Linux distribution for Chromebooks
 * Arch Linux Wiki - Similar page on the Arch Linux Wiki