GalliumOS Wiki - User contributions [en]

Hardware Compatibility

2018-05-09T12:22:40Z

Claviger-pc: /* GalliumOS Support by Model */ -make chart sortable

In order to install and run GalliumOS, your ChromeOS device needs firmware with Legacy Boot capability. This feature is typically provided by [http://www.seabios.org/ SeaBIOS], and included in [http://coreboot.org coreboot].

Some Chromebooks and Chromeboxes have Legacy Boot enabled in the default factory firmware. Other models require a firmware update to add or enable the feature, and unfortunately some models will not work at all.

In general, ChromeOS devices fall into categories by the core architecture of their CPU:

* '''Intel Haswell''', '''Broadwell''', '''Bay Trail''', '''Braswell''', and '''Sandy/Ivy Bridge''' Chromebooks and Chromeboxes are supported by GalliumOS
* '''Intel Skylake''' models are newer and ''mostly'' supported
* '''Intel Apollo Lake''' models are new and support is unknown
* '''Intel Kaby Lake''' models are new and support is unknown
* '''Intel Pineview''' models are older and not supported: they do not ship with compatible firmware, and custom firmware is not presently available
* '''ARM''' models are not supported: they do not ship with compatible firmware, and custom firmware is not presently available

The table below lists all ChromeOS devices ever produced, and the vital details regarding their ability to support GalliumOS. If you find any errors or omissions, please let us know!

If you run into any issues not covered here, please check our [https://github.com/GalliumOS/galliumos-distro/issues issue tracker] and submit a bug report.

Third party firmware updates for many devices are available from several parties -- see [[Firmware]].

Additionally, some devices can support dual-boot (GalliumOS alongside ChromeOS) either with stock firmware or with updated firmware. See [https://chrx.org/ chrx] for full details.



<ref name="Pineview"/>
<ref name="ARM"/>
<ref name="SandyIvy"/>
<ref name="Haswell"/>
<ref name="Broadwell"/>
<ref name="BayTrail"/>
<ref name="Braswell"/>
<ref name="Skylake"/>
<ref name="ApolloLake"/>
<ref name="KabyLake"/>
<ref name="hwid"/>
<ref name="chrx"/>
<ref name="Firmware"/>
<ref name="TextMode"/>
<ref name="HiDPI2560"/>
<ref name="SAMUS"/>
<ref name="PANTHER"/>


== GalliumOS Support by Model ==



{| class="wikitable sortable"
|-
! scope="col"| Model
! scope="col"| Hardware ID<ref name="hwid"/>
! scope="col"| Released
! scope="col"| Processor
! scope="col"| Supports GalliumOS?
! scope="col"| … with factory firmware?<ref name="Firmware"/>
! scope="col"| … with custom firmware?<ref name="Firmware"/>
! scope="col"| … dual-boot with ChromeOS?<ref name="chrx"/>
|-
| Acer AC700
| ZGB
| 2011
| Intel Pineview<ref name="Pineview"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="Pineview"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Acer C7
| PARROT
| 2012
| Intel Sandy/Ivy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffe8e8" | No
|-
| Acer C710
| PARROT
| 2012
| Intel Sandy/Ivy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffe8e8" | No
|-
| Acer C720/C720P
| PEPPY
| 2013
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Acer C730
| GNAWTY
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer C910
| YUNA
| 2014
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: text display<ref name="TextMode"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Acer Chromebook 11 (C740)
| PAINE
| 2014
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: text display<ref name="TextMode"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Acer Chromebook 11 (CB3-111)
| GNAWTY
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 11 (CB3-131)
| GNAWTY
| 2016
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 11 (C735)
| GNAWTY
| 2016
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 11 (C771, C771T)
| LILI, LARS
| 2017
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: boot video<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Acer Chromebook 11 N7 (C731)
| RELM
| 2017
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 11 (C732, C732T, C732L, C732LT)
| ASTRONAUT
| 2018
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 11 (CB311-8H/8HT)
| SANTA
| 2018
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 13 C810
| (tbd)
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Acer Chromebook 13 (CB5-311)
| BIG
| 2014
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Acer Chromebook 14 (CB3-431)
| EDGAR
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 14 For Work (CP5-471)
| LARS
| 2016
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: boot video<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Acer Chromebook 15 (CB3-531)
| BANJO
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 15 (CB5-571)
| YUNA
| 2014
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: text display<ref name="TextMode"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Acer Chromebook 15 (CB3-532)
| BANON
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 15 (CB515-1HT/1H)
| SAND
| 2017
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook R11 (CB5-132T, C738T)
| CYAN
| 2015
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook R13 (CB5-312T)
| ELM
| 2016
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Acer Chromebook Spin 11 (R751T)
| REEF
| 2017
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Acer Chromebox CXI
| MCCLOUD
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Acer Chromebox CXI2
| RIKKU
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| AOPEN Chromebase Commercial 22 (WT22M)
| SUMO
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| AOPEN Chromebox Commercial (DE3255)
| NINJA
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook Flip C101PA
| BOB
| 2017
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| ASUS Chromebook C200
| SQUAWKS
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook C201PA
| SPEEDY
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| ASUS Chromebook C202SA
| TERRA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook Flip C213SA
| REEF
| 2017
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook C300
| QUAWKS
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook C300SA
| TERRA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook C301SA
| TERRA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook Flip C302
| CAVE
| 2016
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: boot video<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| ASUS Chromebox CN60
| PANTHER
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: USB init<ref name="PANTHER"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| ASUS Chromebox CN62
| GUADO
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| ASUS Flip C100
| MINNIE
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| CTL J2 Chromebook for Education
| JERRY
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| CTL J4 Chromebook for Education
| JERRY
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| CTL Chromebook J5
| WIZPIG
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| CTL NL6 Education Chromebook
| ENGUARDE
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| CTL NL61 Chromebook
| RELM
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Dell Chromebook 11
| WOLF
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Dell Chromebook 11 (3120)
| CANDY
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Dell Chromebook 11 (3180)
| KEFKA
| 2017
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Dell Chromebook 11 (3189)
| KEFKA
| 2017
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Dell Chromebook 11 5190
| NASHER
| 2018
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Dell Chromebook 11 2-in-1 5190
| NASHER360
| 2018
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Dell Chromebook 13 (7310)
| LULU
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: text display<ref name="TextMode"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Dell Chromebook 13 (3380)
| ASUKA
| 2017
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: boot video<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Dell Chromebox
| TRICKY
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Edugear CMT Chromebook
| WIZPIG
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Edxis Education Chromebook
| RELM
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Google Chromebook Pixel
| LINK
| 2013
| Intel Ivy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: HiDPI<ref name="HiDPI2560"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues?
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Google Chromebook Pixel
| SAMUS
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SAMUS"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Google Cr-48
| MARIO
| 2011
| Intel Pineview<ref name="Pineview"/>
| style="text-align:center;background-color:#ffffcc" | Possibly<ref name="Pineview"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | Possibly<ref name="Pineview"/>
| style="text-align:center;background-color:#ffffcc" | Possibly, after firmware update<ref name="chrx"/>
|-
| Google Pixelbook
| EVE
| 2017
| Intel Kaby Lake<ref name="KabyLake"/>
| style="text-align:center;Xbackground-color:#ffffcc" | Unknown
| style="text-align:center;Xbackground-color:#ccffcc" | Unknown<ref name="KabyLake"/>
| style="text-align:center;Xbackground-color:#ccffcc" | Unknown<ref name="KabyLake"/>
| style="text-align:center;Xbackground-color:#ccffcc" | Unknown<ref name="chrx"/>
|-
| Haier Chromebook 11
| JAQ
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Haier Chromebook 11 (edu)
| MIGHTY
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Haier Chromebook 11 G2
| HELI
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Haier Convertible Chromebook 11 C
| WIZPIG
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| HEXA Chromebook Pi
| EXPRESSO
| 2014
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| HiSense Chromebook 11
| JERRY
| 2015
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| HP Chromebook 11 G1
| SPRING
| 2013
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| HP Chromebook 11 G2
| SKATE
| 2013
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| HP Chromebook 11 G3
| KIP
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| HP Chromebook 11 G4
| KIP
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| HP Chromebook 11 G5
| SETZER
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| HP Chromebook 11 G5 EE
| RELM
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| HP Chromebook 13
| CHELL
| 2016
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: boot video<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| HP Chromebook 14
| FALCO
| 2013
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| HP Chromebook 14 G3
| BLAZE
| 2014
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| HP Chromebook 14 G4
| KIP
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| HP Chromebook x360 11 G1
| SNAPPY
| 2017
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| HP Chromebox
| ZAKO
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: USB init<ref name="PANTHER"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| HP Pavilion Chromebook 14
| BUTTERFLY
| 2013
| Intel Sandy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffe8e8" | No
|-
| LG Chromebase (22CV241)
| MONROE
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ffffcc" | Probably
|
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ffffcc" | Probably<ref name="chrx"/>
|-
| LG Chromebase (22CB25S)
| MONROE
| 2016
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ffffcc" | Probably
|
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ffffcc" | Probably<ref name="chrx"/>
|-
| Lenovo 100e Chromebook
| ROBO
| 2018
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo 100S Chromebook
| ORCO
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo 500e Chromebook
| ROBO360
| 2018
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo N20 Chromebook
| CLAPPER
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo N20P Chromebook
| CLAPPER
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo N21 Chromebook
| ENGUARDE
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo N22 Chromebook
| REKS
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo N42 Chromebook
| REKS
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo ThinkCentre Chromebox
| TIDUS
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Lenovo ThinkPad 11e Chromebook
| GLIMMER
| 2015
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo ThinkPad 11e Chromebook G3
| ULTIMA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo ThinkPad 11e Chromebook G4
| PYRO
| 2017
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo ThinkPad 13 Chromebook
| SENTRY
| 2016
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: boot video<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Lenovo ThinkPad Yoga
| GLIMMER
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo ThinkPad Yoga G3
| ULTIMA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo ThinkPad Yoga G4
| PYRO
| 2017
| Intel Apollo Lake<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio, etc<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="ApolloLake"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Lenovo X131e Chromebook
| STOUT
| 2013
| Intel Ivy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffe8e8" | No
|-
| Mecer V2 Chromebook
| RELM
| 2017
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| NComputing Chromebook CX100/110
| JERRY
| 2016
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| PCMerge Chromebook (PCM-116T-432B)
| WIZPIG
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Prowise ProLine Chromebook
| WIZPIG
| 2017
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Samsung Chromebook (XE303C12)
| SNOW
| 2012
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Samsung Chromebook 2 (XE500C12)
| WINKY
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Samsung Chromebook 2 (XE503C12)
| PIT
| 2014
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Samsung Chromebook 2 (XE503C32)
| PI
| 2014
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Samsung Chromebook 3 (XE500C13)
| CELES
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Samsung Chromebook Plus (XE513C24)
| KEVIN
| 2017
| ARM<ref name="ARM"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="ARM"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Samsung Chromebook Pro (XE510C24)
| CAROLINE
| 2017
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: internal audio<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: boot video<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Skylake"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Samsung Series 3 Chromebox
| STUMPY
| 2012
| Intel Sandy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffe8e8" | No
|-
| Samsung Series 5 (XE500C21)
| ALEX
| 2011
| Intel Pineview<ref name="Pineview"/>
| style="text-align:center;background-color:#ffcccc" | No<ref name="Pineview"/>
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
| style="text-align:center;background-color:#ffe8e8" | -
|-
| Samsung Series 5 550
| LUMPY
| 2012
| Intel Sandy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffe8e8" | No
|-
| Senkatel Edu
| ENGUARDE
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Toshiba Chromebook CB30
| LEON
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Toshiba Chromebook CB35
| LEON
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Toshiba Chromebook 2 CB30
| SWANKY
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Toshiba Chromebook 2 CB35
| SWANKY
| 2014
| Intel Bay Trail<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="BayTrail"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
| Toshiba Chromebook 2 CB35
| GANDOF
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Yes, with issues: text display<ref name="TextMode"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/>
|-
| Viglen Chromebook 360
| WIZPIG
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Braswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
|-
! scope="col"| Model
! scope="col"| Hardware ID
! scope="col"| Released
! scope="col"| Processor
! scope="col"| Supports GalliumOS?
! scope="col"| … with factory firmware?<ref name="Firmware"/>
! scope="col"| … with custom firmware?<ref name="Firmware"/>
! scope="col"| … dual-boot with ChromeOS?<ref name="chrx"/>
|-
|}

=== Notes ===

<references>
<ref name="Pineview">
'''Pineview''' models do not ship with compatible firmware, and custom firmware is not generally available. MARIO (Google Cr-48) might be an exception. See [[Support/Pineview]].
</ref>
<ref name="SandyIvy">
'''Sandy/Ivy Bridge''' models are supported. See [[Support/SandyIvy]].
</ref>
<ref name="Haswell">
'''Haswell''' models are well-supported. See [[Support/Haswell]].
</ref>
<ref name="BayTrail">
'''Bay Trail''' models are well-supported. See [[Support/BayTrail]].
</ref>
<ref name="Broadwell">
'''Broadwell''' models are well-supported. See [[Support/Broadwell]].
</ref>
<ref name="ARM">
'''ARM''' models do not ship with compatible firmware, and custom firmware is not available at this time. See [[Support/ARM]].
</ref>
<ref name="Braswell">
'''Braswell''' models are well-supported. See [[Support/Braswell]].
</ref>
<ref name="Skylake">
'''Skylake''' models are '''mostly''' supported. See [[Support/Skylake]] and [https://github.com/GalliumOS/galliumos-distro/issues/274 Skylake Platform Validation].
</ref>
<ref name="ApolloLake">
'''Apollo Lake''' models are new, and support is uncertain. See [[Support/ApolloLake]] and [https://github.com/GalliumOS/galliumos-distro/issues/364 Apollo Lake Platform Validation].
</ref>
<ref name="KabyLake">
'''Kaby Lake''' models are new, and support is uncertain. See [[Support/KabyLake]] and [https://github.com/GalliumOS/galliumos-distro/issues/400 Kaby Lake Platform Validation].
</ref>
<ref name="TextMode">'''Text Mode''':
The factory firmware of this model fails to display text-mode output, so messages printed to screen during the early boot process will be invisible. This can be functional, but very difficult to debug if problems arise. Updated FULL ROM firmware fixes it. See [[Firmware]].
</ref>
<ref name="HiDPI2560">'''HiDPI''':
This model has a 2560x1700 display. GalliumOS (Xfce, Gtk2, xfwm4) will work at this geometry, but GUI elements will be very small (possibly unusably small), since they are not scaled appropriately. You can install the <code>galliumos-hidpi</code> package for better settings.
</ref>
<ref name="SAMUS">'''SAMUS'''
(Google Pixel, 2015) See [[Installing/Samus]] for some notes on audio and HiDPI config.
</ref>
<ref name="PANTHER">'''PANTHER/ZAKO'''
(ASUS Chromebox, 2014 / HP Chromebox, 2014) have a broken factory legacy boot payload that fails to initialize the USB3 ports; custom firmware is the only resolution. See also [[Installing/Panther]].
</ref>
<ref name="hwid">'''Hardware ID''': Each Chromebook/box/base model is identified by a hardware ID. Some manufacturers reuse model names for different hardware IDs (e.g. Samsung), and others market several versions of the same hardware ID (e.g. HP). For purposes of support questions, hardware ID is the most important identifier for your model. You can check your Hardware ID from the Developer Mode boot screen ("OS verification is OFF"), from the Terminal (<code>dmidecode -s system-product-name</code>) or from inside ChromeOS by navigating to <code>chrome://system</code>, where it's called <code>hardware_class</code>.
</ref>
<ref name="Firmware">'''Firmware''' options are available for all models, and required for some. See [[Firmware]].
</ref>
<ref name="chrx">'''Dual-Booting''' with ChromeOS is possible where the factory firmware supports legacy booting (SeaBIOS), or the custom firmware installs legacy boot capability without removing ChromeOS boot functionality. Currently, dual-boot setups are installed via [https://chrx.org/ chrx].
</ref>
</references>

FAQ/Touchpad

2018-04-27T12:30:16Z

Claviger-pc: /* Introduction */

==Introduction==

A common issue that presents itself to many GalliumOS users is the lack of palm detection as well as the inability to disable the touch pad for a fraction of a second while the user is typing. If you have had frustration dealing with the touchpad in GalliumOS, there is a way to fix this and have something very close to stock ChromeOS behavior.

Before trying the process below, you can try touchpad-indicator, which can disable the touchpad while typing, without changing the touchpad drivers which have been specially tweaked by the GalliumOS team. Touchpad indicator can be installed from the [http://ppa.launchpad.net/atareao/atareao/ubuntu/pool/main/t/touchpad-indicator/ .deb package], or using the following commands:

sudo add-apt-repository ppa:atareao/atareao
sudo apt update
sudo apt install touchpad-indicator

And to remove:

sudo apt remove touchpad-indicator && sudo apt autoremove

This guide will assume that your hardware is equipped with an 'Elan' touchpad. Nearly all Chromebooks use this hardware.

==Before you start==

Verify your hardware is using an Elan touchpad. Open up a terminal, and issue the following command:

<code>xfce4-mouse-settings</code>

If your touchpad is Elan hardware, you will see it clearly.

[[File:Elan_verify.png|centre|thumb|604x604px|This is an Elan touchpad!]]

If you do not see 'Elan Touchpad' as your hardware - proceed with caution. This fix has only been tested on Elan hardware.

We will be making changes to the input system. It's advised that before you begin this process, you have a backup of anything critical - just in case.

==Required Software==

To start off, we are going to need to install libinput. Open up a terminal, and issue the following command:

<code>sudo apt install xserver-xorg-input-libinput</code>

This will install libinput on your system, and configure it with the default settings.

Your output will look something like this:

[[File:Libinput_install.png|centre|thumb|604x604px|Installing libinput]]

If you choose to reboot or restart your xorg session at this point before configuration, do so at your own risk - I recommend that you follow along with this guide and configure the input before rebooting.

==Enable 'Tapping'==

This will set your touchpad to be what most users expect - a single 'tap' will be a 'left click', a 'tap with two fingers' will be a 'right click', and a 'tap with three fingers' will be a middle click.

We're going to open up a terminal, and issue the following command:

<code>sudo nano /usr/share/X11/xorg.conf.d/90-libinput.conf</code>

Your terminal will now be editing the configuration, and you will see something like this:

[[File:Libinput_edit2.png|centre|thumb|604x604px|Let's edit libinput!]]

Notice the 'third' entry. This is the entry that contains the line:

<code>MatchIsTouchpad "on"</code>

You will add this line:

<code>Option "Tapping" "true"</code>

See above screencapture and double check everything.

Once you have added this line and double checked you have it in the right place: issue a control + x (hold down ctrl key and press x). You will be prompted to save the file, the 'y' key will save the file.

==Test our changes==

Now that we have installed libinput and enabled proper tapping - this is a great time to reboot. Issue the following command in your terminal (or use the power key or any other method you prefer to reboot your machine)

<code>sudo reboot</code>

At this point, you may notice that the mouse cursor is 'faster' or 'slower' than you are used to; that's fine. We'll address this in the next section. For the moment, you should be able to move your cursor, issue a left click with a single tap, issue a right click with a two finger tap, and issue a middle click with a three finger tap.

To test this, open a web browser and search your favorite search engine for anything. In the results - a single tap should open a link, a double finger tap on the link should open the right click menu, and a triple finger tap on the link should open the link in a new tab.

==Tweak mouse acceleration==

At this point - your Elan touchpad should be ignoring movements/clicks/taps for a moment while you are typing. However, your mouse cursor may be too 'slow' or too 'fast' for your personal preferences. Thankfully, this is very easy to fix.

First up - we'll need to verify the device ID# of your touchpad. Open a terminal, and issue the following command:

<code>xinput</code>

This will return the device ID of your touchpad. As you can see in my example - the ID number is 10. Your ID number may not be the same, so take your time here and make sure you have the correct device ID.

[[File:check_elan_device.png|centre|thumb|604x604px|determining the device ID number]]

Now, we can go ahead and begin to tweak the acceleration.

<code>xinput --set-prop 10 'libinput Accel Speed' 0.2</code>

You will need to replace ## with the device ID of the 'Elan Touchpad' as determined by the above instructions. In my case, the device ID is '10' - however this very well may not the case on your system.

These changes will take effect right away, so go ahead and play with the mouse and determine if it is 'too fast' or 'too slow' for your personal preference. If it's too fast, try again with a speed of 0.15, if it's too slow, try again with a setting of 0.25. Continue to change the acceleration until you have a mouse speed that 'feels right' to you.

Once you are happy with the acceleration level, we're going to want to have this setting apply on every reboot. Open up a terminal, and issue the following command:

<code>nano ~/.bashrc</code>

Press control+v a few times to page forward, until you are at the end of the file. On a new line, simply add the following:

<code>xinput --set-prop foo 'libinput Accel Speed' bar</code>

Where foo is the device ID determined earlier, and bar is the acceleration setting that worked well for you. For my personal settings, it looks something like this:

<code>xinput --set-prop 10 'libinput Accel Speed' 0.125</code>

Once you have added the proper line to your .bashrc file, hold down the ctrl key, press the 'x' key, and answer 'y' to save the file. At this point, you can reboot and your custom mouse speed should take effect after login!

==Final Notes==

Now that we have made these changes, please note that the default XFCE GUI mouse settings in your control panel will no longer function. Any changes you need to make need to made in the above mentioned configuration files.

==Help! I hate this and and want to revert to stock behavior!==

Easy as pie. Open up a terminal and simple issue this command:

<code>sudo apt purge xserver-xorg-input-libinput</code>

And then reboot. All of your settings are back to stock GalliumOS behavior.

FAQ/Touchpad

2018-04-27T12:28:14Z

Claviger-pc: /* Introduction */

==Introduction==

A common issue that presents itself to many GalliumOS users is the lack of palm detection as well as the inability to disable the touch pad for a fraction of a second while the user is typing. If you have had frustration dealing with the touchpad in GalliumOS, there is a way to fix this and have something very close to stock ChromeOS behavior. Before trying the process below, you can try touchpad indicator, which will disable the touchoad while typing, without changing the touchpad drivers which have been specially tweaked by the GalliumOS team. Touchpad indicator can be installed from the [http://ppa.launchpad.net/atareao/atareao/ubuntu/pool/main/t/touchpad-indicator/ .deb package], or using the following commands:

sudo add-apt-repository ppa:atareao/atareao
sudo apt update
sudo apt install touchpad-indicator

And to remove:

sudo apt remove touchpad-indicator && sudo apt autoremove

This guide will assume that your hardware is equipped with an 'Elan' touchpad. Nearly all Chromebooks use this hardware.

==Before you start==

Verify your hardware is using an Elan touchpad. Open up a terminal, and issue the following command:

<code>xfce4-mouse-settings</code>

If your touchpad is Elan hardware, you will see it clearly.

[[File:Elan_verify.png|centre|thumb|604x604px|This is an Elan touchpad!]]

If you do not see 'Elan Touchpad' as your hardware - proceed with caution. This fix has only been tested on Elan hardware.

We will be making changes to the input system. It's advised that before you begin this process, you have a backup of anything critical - just in case.

==Required Software==

To start off, we are going to need to install libinput. Open up a terminal, and issue the following command:

<code>sudo apt install xserver-xorg-input-libinput</code>

This will install libinput on your system, and configure it with the default settings.

Your output will look something like this:

[[File:Libinput_install.png|centre|thumb|604x604px|Installing libinput]]

If you choose to reboot or restart your xorg session at this point before configuration, do so at your own risk - I recommend that you follow along with this guide and configure the input before rebooting.

==Enable 'Tapping'==

This will set your touchpad to be what most users expect - a single 'tap' will be a 'left click', a 'tap with two fingers' will be a 'right click', and a 'tap with three fingers' will be a middle click.

We're going to open up a terminal, and issue the following command:

<code>sudo nano /usr/share/X11/xorg.conf.d/90-libinput.conf</code>

Your terminal will now be editing the configuration, and you will see something like this:

[[File:Libinput_edit2.png|centre|thumb|604x604px|Let's edit libinput!]]

Notice the 'third' entry. This is the entry that contains the line:

<code>MatchIsTouchpad "on"</code>

You will add this line:

<code>Option "Tapping" "true"</code>

See above screencapture and double check everything.

Once you have added this line and double checked you have it in the right place: issue a control + x (hold down ctrl key and press x). You will be prompted to save the file, the 'y' key will save the file.

==Test our changes==

Now that we have installed libinput and enabled proper tapping - this is a great time to reboot. Issue the following command in your terminal (or use the power key or any other method you prefer to reboot your machine)

<code>sudo reboot</code>

At this point, you may notice that the mouse cursor is 'faster' or 'slower' than you are used to; that's fine. We'll address this in the next section. For the moment, you should be able to move your cursor, issue a left click with a single tap, issue a right click with a two finger tap, and issue a middle click with a three finger tap.

To test this, open a web browser and search your favorite search engine for anything. In the results - a single tap should open a link, a double finger tap on the link should open the right click menu, and a triple finger tap on the link should open the link in a new tab.

==Tweak mouse acceleration==

At this point - your Elan touchpad should be ignoring movements/clicks/taps for a moment while you are typing. However, your mouse cursor may be too 'slow' or too 'fast' for your personal preferences. Thankfully, this is very easy to fix.

First up - we'll need to verify the device ID# of your touchpad. Open a terminal, and issue the following command:

<code>xinput</code>

This will return the device ID of your touchpad. As you can see in my example - the ID number is 10. Your ID number may not be the same, so take your time here and make sure you have the correct device ID.

[[File:check_elan_device.png|centre|thumb|604x604px|determining the device ID number]]

Now, we can go ahead and begin to tweak the acceleration.

<code>xinput --set-prop 10 'libinput Accel Speed' 0.2</code>

You will need to replace ## with the device ID of the 'Elan Touchpad' as determined by the above instructions. In my case, the device ID is '10' - however this very well may not the case on your system.

These changes will take effect right away, so go ahead and play with the mouse and determine if it is 'too fast' or 'too slow' for your personal preference. If it's too fast, try again with a speed of 0.15, if it's too slow, try again with a setting of 0.25. Continue to change the acceleration until you have a mouse speed that 'feels right' to you.

Once you are happy with the acceleration level, we're going to want to have this setting apply on every reboot. Open up a terminal, and issue the following command:

<code>nano ~/.bashrc</code>

Press control+v a few times to page forward, until you are at the end of the file. On a new line, simply add the following:

<code>xinput --set-prop foo 'libinput Accel Speed' bar</code>

Where foo is the device ID determined earlier, and bar is the acceleration setting that worked well for you. For my personal settings, it looks something like this:

<code>xinput --set-prop 10 'libinput Accel Speed' 0.125</code>

Once you have added the proper line to your .bashrc file, hold down the ctrl key, press the 'x' key, and answer 'y' to save the file. At this point, you can reboot and your custom mouse speed should take effect after login!

==Final Notes==

Now that we have made these changes, please note that the default XFCE GUI mouse settings in your control panel will no longer function. Any changes you need to make need to made in the above mentioned configuration files.

==Help! I hate this and and want to revert to stock behavior!==

Easy as pie. Open up a terminal and simple issue this command:

<code>sudo apt purge xserver-xorg-input-libinput</code>

And then reboot. All of your settings are back to stock GalliumOS behavior.

FAQ/Touchpad

2018-04-27T12:25:18Z

Claviger-pc: /* Introduction */

==Introduction==

A common issue that presents itself to many GalliumOS users is the lack of palm detection as well as the inability to disable the touch pad for a fraction of a second while the user is typing. If you have had frustration dealing with the touchpad in GalliumOS, there is a way to fix this and have something very close to stock ChromeOS behavior. Before trying the process below, you can try touchpad indicator, which will take care of palm detection without changing the touchpad drivers which have been specially tweaked by the GalliumOS team. Touchpad indicator can be installed from the [http://ppa.launchpad.net/atareao/atareao/ubuntu/pool/main/t/touchpad-indicator/ .deb package], or using the following commands:

sudo add-apt-repository ppa:atareao/atareao
sudo apt update
sudo apt install touchpad-indicator

And to remove:

sudo apt remove touchpad-indicator && sudo apt autoremove

This guide will assume that your hardware is equipped with an 'Elan' touchpad. Nearly all Chromebooks use this hardware.

==Before you start==

Verify your hardware is using an Elan touchpad. Open up a terminal, and issue the following command:

<code>xfce4-mouse-settings</code>

If your touchpad is Elan hardware, you will see it clearly.

[[File:Elan_verify.png|centre|thumb|604x604px|This is an Elan touchpad!]]

If you do not see 'Elan Touchpad' as your hardware - proceed with caution. This fix has only been tested on Elan hardware.

We will be making changes to the input system. It's advised that before you begin this process, you have a backup of anything critical - just in case.

==Required Software==

To start off, we are going to need to install libinput. Open up a terminal, and issue the following command:

<code>sudo apt install xserver-xorg-input-libinput</code>

This will install libinput on your system, and configure it with the default settings.

Your output will look something like this:

[[File:Libinput_install.png|centre|thumb|604x604px|Installing libinput]]

If you choose to reboot or restart your xorg session at this point before configuration, do so at your own risk - I recommend that you follow along with this guide and configure the input before rebooting.

==Enable 'Tapping'==

This will set your touchpad to be what most users expect - a single 'tap' will be a 'left click', a 'tap with two fingers' will be a 'right click', and a 'tap with three fingers' will be a middle click.

We're going to open up a terminal, and issue the following command:

<code>sudo nano /usr/share/X11/xorg.conf.d/90-libinput.conf</code>

Your terminal will now be editing the configuration, and you will see something like this:

[[File:Libinput_edit2.png|centre|thumb|604x604px|Let's edit libinput!]]

Notice the 'third' entry. This is the entry that contains the line:

<code>MatchIsTouchpad "on"</code>

You will add this line:

<code>Option "Tapping" "true"</code>

See above screencapture and double check everything.

Once you have added this line and double checked you have it in the right place: issue a control + x (hold down ctrl key and press x). You will be prompted to save the file, the 'y' key will save the file.

==Test our changes==

Now that we have installed libinput and enabled proper tapping - this is a great time to reboot. Issue the following command in your terminal (or use the power key or any other method you prefer to reboot your machine)

<code>sudo reboot</code>

At this point, you may notice that the mouse cursor is 'faster' or 'slower' than you are used to; that's fine. We'll address this in the next section. For the moment, you should be able to move your cursor, issue a left click with a single tap, issue a right click with a two finger tap, and issue a middle click with a three finger tap.

To test this, open a web browser and search your favorite search engine for anything. In the results - a single tap should open a link, a double finger tap on the link should open the right click menu, and a triple finger tap on the link should open the link in a new tab.

==Tweak mouse acceleration==

At this point - your Elan touchpad should be ignoring movements/clicks/taps for a moment while you are typing. However, your mouse cursor may be too 'slow' or too 'fast' for your personal preferences. Thankfully, this is very easy to fix.

First up - we'll need to verify the device ID# of your touchpad. Open a terminal, and issue the following command:

<code>xinput</code>

This will return the device ID of your touchpad. As you can see in my example - the ID number is 10. Your ID number may not be the same, so take your time here and make sure you have the correct device ID.

[[File:check_elan_device.png|centre|thumb|604x604px|determining the device ID number]]

Now, we can go ahead and begin to tweak the acceleration.

<code>xinput --set-prop 10 'libinput Accel Speed' 0.2</code>

You will need to replace ## with the device ID of the 'Elan Touchpad' as determined by the above instructions. In my case, the device ID is '10' - however this very well may not the case on your system.

These changes will take effect right away, so go ahead and play with the mouse and determine if it is 'too fast' or 'too slow' for your personal preference. If it's too fast, try again with a speed of 0.15, if it's too slow, try again with a setting of 0.25. Continue to change the acceleration until you have a mouse speed that 'feels right' to you.

Once you are happy with the acceleration level, we're going to want to have this setting apply on every reboot. Open up a terminal, and issue the following command:

<code>nano ~/.bashrc</code>

Press control+v a few times to page forward, until you are at the end of the file. On a new line, simply add the following:

<code>xinput --set-prop foo 'libinput Accel Speed' bar</code>

Where foo is the device ID determined earlier, and bar is the acceleration setting that worked well for you. For my personal settings, it looks something like this:

<code>xinput --set-prop 10 'libinput Accel Speed' 0.125</code>

Once you have added the proper line to your .bashrc file, hold down the ctrl key, press the 'x' key, and answer 'y' to save the file. At this point, you can reboot and your custom mouse speed should take effect after login!

==Final Notes==

Now that we have made these changes, please note that the default XFCE GUI mouse settings in your control panel will no longer function. Any changes you need to make need to made in the above mentioned configuration files.

==Help! I hate this and and want to revert to stock behavior!==

Easy as pie. Open up a terminal and simple issue this command:

<code>sudo apt purge xserver-xorg-input-libinput</code>

And then reboot. All of your settings are back to stock GalliumOS behavior.

Media keys and default keybindings

2018-04-23T08:20:37Z

Claviger-pc: grammatical correction

GalliumOS includes five keyboard layouts customized for Chromebooks. They can be configured from the GalliumOS/Whisker Menu, in Settings >> Keyboard >> Layout >> Keyboard Model.

Media keys and Function keys can be accessed either with or without pressing the "Overlay" key first, depending on your choice of keyboard layout.

== Keyboard Layouts ==

{| class="wikitable"
!Layout Name
!Overlay Key
!Top row keys (alone)
!Top row keys (with Overlay)
|-
| Chromebook / No overlay / F keys mapped to media keys
| None
| Media keys
| Media keys
|-
| Chromebook / Right alt overlay
| <code>Right-Alt</code>
| Function keys
| Media keys
|-
| style="background-color:#e0e8ff" | '''Chromebook / Right alt overlay / F keys mapped to media keys''' '''** default for GalliumOS 1.0 and later **'''
| style="background-color:#e0e8ff" | <code>Right-Alt</code>
| style="background-color:#e0e8ff" | Media keys
| style="background-color:#e0e8ff" | Function keys
|-
| Chromebook / Search overlay previous default (1.0beta1), and Crouton default
| <code>Super (Search)</code>
| Function keys
| Media keys
|-
| Chromebook / Search overlay / F keys mapped to media key
| <code>Super (Search)</code>
| Media keys
| Function keys
|}

These layouts are stored in /usr/share/X11/xkb/symbols/chromebook* . To modify the functionality of a key, one can make changes to the appropriate file (as root). 
For instance, to remap the power key to Delete, add the following line in the appropriate file: <code>key <POWR> {[ Delete ] };</code>, and set the power button to "Do nothing" in the Power Manager menu.

== Key Mappings ==

{| class="wikitable"
!Key
!Combination
|-
|F1-F10
|Accessed directly or with <code>Overlay</code>, depending on Keyboard layout
|-
|F11
|
|-
|F12
|
|-
|Home
|<code>Overlay</code> + <code>Left Arrow</code>
|-
|End
|<code>Overlay</code> + <code>Right Arrow</code>
|-
|Page Up
|<code>Overlay</code> + <code>Up Arrow</code>
|-
|Page Down
|<code>Overlay</code> + <code>Down Arrow</code>
|-
|Insert
|<code>Overlay</code> + <code>.</code>
|-
|Delete
|<code>Overlay</code> + <code>Backspace</code>
|-
|Caps Lock
|Right-Alt as Overlay: <code>Overlay</code> + <code>Left Alt</code> + <code>Right Shift</code> Super as Overlay: <code>Overlay</code> + <code>Left Alt</code>
|}

Crouton keyboard layout: https://github.com/dnschneid/crouton/wiki/Keyboard

Other discussion: https://github.com/GalliumOS/galliumos-distro/issues/50

== Keyboard Shortcuts ==

{| class="wikitable"
!Key
!Combination
|-
|Screenshot (fullscreen)
|<code>Ctrl</code> + <code>F5(display)</code>
|-
|Screenshot (window)
|<code>Ctrl</code> + <code>Shift</code> + <code>F5(display)</code>
|-
|Whisker Menu/Search
|Right-Alt as Overlay: <code>Super</code> + <code>M</code> Super as Overlay: <code>Left-Alt</code> + <code>M</code>
|-
|Keyboard Backlight Toggle
|<code>Overlay</code> + <code>0</code> '''(not working!)'''
|-
|Keyboard Backlight Brightness Down
|<code>Overlay</code> + <code>-</code>
|-
|Keyboard Backlight Brightness Up
|<code>Overlay</code> + <code>=</code>
|}

Media keys and default keybindings

2018-04-23T06:24:20Z

Claviger-pc: add information on the layout files, suggestion about remapping power key

GalliumOS includes five keyboard layouts customized for Chromebooks. They can be configured from the GalliumOS/Whisker Menu, in Settings >> Keyboard >> Layout >> Keyboard Model.

Media keys and Function keys can be accessed either with or without pressing the "Overlay" key first, depending on your choice of keyboard layout.

== Keyboard Layouts ==

{| class="wikitable"
!Layout Name
!Overlay Key
!Top row keys (alone)
!Top row keys (with Overlay)
|-
| Chromebook / No overlay / F keys mapped to media keys
| None
| Media keys
| Media keys
|-
| Chromebook / Right alt overlay
| <code>Right-Alt</code>
| Function keys
| Media keys
|-
| style="background-color:#e0e8ff" | '''Chromebook / Right alt overlay / F keys mapped to media keys''' '''** default for GalliumOS 1.0 and later **'''
| style="background-color:#e0e8ff" | <code>Right-Alt</code>
| style="background-color:#e0e8ff" | Media keys
| style="background-color:#e0e8ff" | Function keys
|-
| Chromebook / Search overlay previous default (1.0beta1), and Crouton default
| <code>Super (Search)</code>
| Function keys
| Media keys
|-
| Chromebook / Search overlay / F keys mapped to media key
| <code>Super (Search)</code>
| Media keys
| Function keys
|}

These layouts are stored in /usr/share/X11/xkb/symbols/chromebook* . To modify the functionality of a key, one can make changes to the appropriate file (as root). 
For instance, to remap the power key to Delete, add the following line in appropriate file: <code>key <POWR> {[ Delete ] };</code>, and set the power button to "Do nothing" in the Power Manager menu.

== Key Mappings ==

{| class="wikitable"
!Key
!Combination
|-
|F1-F10
|Accessed directly or with <code>Overlay</code>, depending on Keyboard layout
|-
|F11
|
|-
|F12
|
|-
|Home
|<code>Overlay</code> + <code>Left Arrow</code>
|-
|End
|<code>Overlay</code> + <code>Right Arrow</code>
|-
|Page Up
|<code>Overlay</code> + <code>Up Arrow</code>
|-
|Page Down
|<code>Overlay</code> + <code>Down Arrow</code>
|-
|Insert
|<code>Overlay</code> + <code>.</code>
|-
|Delete
|<code>Overlay</code> + <code>Backspace</code>
|-
|Caps Lock
|Right-Alt as Overlay: <code>Overlay</code> + <code>Left Alt</code> + <code>Right Shift</code> Super as Overlay: <code>Overlay</code> + <code>Left Alt</code>
|}

Crouton keyboard layout: https://github.com/dnschneid/crouton/wiki/Keyboard

Other discussion: https://github.com/GalliumOS/galliumos-distro/issues/50

== Keyboard Shortcuts ==

{| class="wikitable"
!Key
!Combination
|-
|Screenshot (fullscreen)
|<code>Ctrl</code> + <code>F5(display)</code>
|-
|Screenshot (window)
|<code>Ctrl</code> + <code>Shift</code> + <code>F5(display)</code>
|-
|Whisker Menu/Search
|Right-Alt as Overlay: <code>Super</code> + <code>M</code> Super as Overlay: <code>Left-Alt</code> + <code>M</code>
|-
|Keyboard Backlight Toggle
|<code>Overlay</code> + <code>0</code> '''(not working!)'''
|-
|Keyboard Backlight Brightness Down
|<code>Overlay</code> + <code>-</code>
|-
|Keyboard Backlight Brightness Up
|<code>Overlay</code> + <code>=</code>
|}