Difference between revisions of "Hardware Compatibility"
From GalliumOS Wiki
(→GalliumOS Support by Model) |
(→GalliumOS Support by Model) |
||
| Line 358: | Line 358: | ||
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/> | | style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/> | ||
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/> | | style="text-align:center;background-color:#ccffcc" | Yes<ref name="chrx"/> | ||
| − | | style="text-align:center;" | [[Installing/Samus|Installation]] | + | | style="text-align:center;" | [[Installing/Samus|Installation]] [https://www.reddit.com/r/GalliumOS/comments/48zgsz/guideadd_pixel_2015_default_resolution_options/ HiDPI config] |
|- | |- | ||
| Google Cr-48 | | Google Cr-48 | ||
Revision as of 22:05, 4 March 2016
In order to install and run GalliumOS, your ChromeOS device needs firmware with Legacy Boot capability. This feature is typically provided by SeaBIOS, and included in 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, and Sandy/Ivy Bridge Chromebooks and Chromeboxes are supported by GalliumOS
- Intel Braswell models are brand new and have not seen any testing at all yet
- Intel Pineview models are 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 issue tracker and submit a bug report.
Firmware updates for many devices are available from John Lewis or Matt Devillier.
Additionally, some devices can support dual-boot (GalliumOS alongside ChromeOS) either with stock firmware or with updated firmware. See chrx for more details.
GalliumOS Support by Model
| Model | Hardware ID | Released | Processor | Supports GalliumOS? | … with factory firmware? | … with custom firmware? | … dual-boot with ChromeOS?[8] | More Info |
|---|---|---|---|---|---|---|---|---|
| Acer AC700 | ZGB | 2011 | Intel Pineview[1] | No[1] | - | - | - | |
| Acer C7 | PARROT | 2012 | Intel Sandy/Ivy Bridge[3] | Yes | No | Yes[3] | No | Installation |
| Acer C710 | PARROT | 2012 | Intel Sandy/Ivy Bridge[3] | Yes | No | Yes[3] | No | Installation |
| Acer C720 | PEPPY | 2013 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | Installation |
| Acer C720P | PEPPY | 2013 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | Installation |
| Acer C730 | GNAWTY | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Acer C910 | YUNA | 2014 | Intel Broadwell[5] | Yes | Major issues: text display[9] |
Yes[5] | Yes, after firmware update[8] | |
| Acer Chromebook 11 C740 | PAINE | 2014 | Intel Broadwell[5] | Tested | Major issues: text display[9] |
Yes[5] | Yes, after firmware update[8] | |
| Acer Chromebook 11 (CB3-111) | GNAWTY | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Acer Chromebook 11 (CB3-131) | GNAWTY | 2016 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Acer Chromebook 13 C810 | (tbd) | 2015 | ARM[2] | No[2] | - | - | - | |
| Acer Chromebook 13 (CB5-311) | BIG | 2014 | ARM[2] | No[2] | - | - | - | |
| Acer Chromebook 15 (CB3-531) | BANJO | 2015 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Acer Chromebook 15 (CB5-571) | YUNA | 2014 | Intel Broadwell[5] | Yes | Major issues: text display[9] |
Yes[5] | Yes, after firmware update[8] | |
| Acer Chromebook R11 | CYAN | 2015 | Intel Braswell[7] | ? | not yet (Mar 2016) | |||
| Acer Chromebox CXI | MCCLOUD | 2014 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | Installation |
| Acer Chromebox CXI2 | RIKKU | 2015 | Intel Broadwell[5] | Yes | Major issues: text display[9] |
Yes[5] | Yes, after firmware update[8] | |
| ASUS C200 | SQUAWKS | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| ASUS C201 | SPEEDY | 2015 | ARM[2] | No[2] | - | - | - | |
| ASUS C300 | QUAWKS | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| ASUS Chromebox | PANTHER | 2014 | Intel Haswell[4] | Yes | Major issue: USB init[12] |
Yes[4] | Yes, after firmware update[8] | Installation |
| ASUS Chromebox CN62 | GUADO | 2015 | Intel Broadwell[5] | Yes | Major issues: text display[9] |
Yes[5] | Yes, after firmware update[8] | |
| ASUS Flip C100 | MINNIE | 2015 | ARM[2] | No[2] | - | - | - | |
| CTL J2 Chromebook for Education | JERRY | 2015 | ARM[2] | No[2] | - | - | - | |
| CTL J4 Chromebook for Education | JERRY | 2015 | ARM[2] | No[2] | - | - | - | |
| CTL NL6 Education Chromebook | ENGUARDE | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Dell Chromebook 11 | WOLF | 2014 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | |
| Dell Chromebook 11 (3120) | CANDY | 2015 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Dell Chromebook 13 | LULU | 2015 | Intel Broadwell[5] | Yes | Major issues: text display[9] |
Yes[5] | Yes, after firmware update?[8] | Installation |
| Dell Chromebox | TRICKY | 2014 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | Installation |
| Google Chromebook Pixel | LINK | 2013 | Intel Ivy Bridge[3] | known issues, including HiDPI[10] custom build planned |
Yes, with issues? | Yes[3] | Yes[8] | |
| Google Chromebook Pixel | SAMUS | 2015 | Intel Broadwell[5] | Yes, with issues: audio[11], HiDPI[10] |
Yes | Yes[5] | Yes[8] | Installation HiDPI config |
| Google Cr-48 | MARIO | 2011 | Intel Pineview[1] | No[1] | - | - | - | |
| Haier Chromebook 11 | JAQ | 2015 | ARM[2] | No[2] | - | - | - | |
| Haier Chromebook 11 (edu) | MIGHTY | 2015 | ARM[2] | No[2] | - | - | - | |
| Haier Chromebook 11 G2 | HELI | 2015 | Intel Bay Trail[6] | ? | No | not yet (Dec 2015) | No | |
| HEXA Chromebook Pi | EXPRESSO | 2014 | ARM[2] | No[2] | - | - | - | |
| HiSense Chromebook 11 | JERRY | 2015 | ARM[2] | No[2] | - | - | - | |
| HP Chromebook 11 G1 | SPRING | 2013 | ARM[2] | No[2] | - | - | - | |
| HP Chromebook 11 G2 | SKATE | 2013 | ARM[2] | No[2] | - | - | - | |
| HP Chromebook 11 G3 | KIP | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| HP Chromebook 11 G4 | KIP | 2015 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| HP Chromebook 14 | FALCO | 2013 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | |
| HP Chromebook 14 G3 | BLAZE | 2014 | ARM[2] | No[2] | - | - | - | |
| HP Chromebook 14 G4 | KIP | 2015 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| HP Chromebox | ZAKO | 2014 | Intel Haswell[4] | Yes | Major issue: USB init[12] |
Yes[4] | Yes, after firmware update[8] | Installation |
| HP Pavilion Chromebook 14 | BUTTERFLY | 2013 | Intel Sandy Bridge[3] | Probably | Yes[3] | |||
| LG Chromebase | MONROE | 2014 | Intel Haswell[4] | Probably | Yes[4] | Probably[8] | ||
| Lenovo 100S Chromebook | ORCO | 2015 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Lenovo N20 Chromebook | CLAPPER | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Lenovo N20P Chromebook | CLAPPER | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Lenovo N21 Chromebook | ENGUARDE | 2015 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Lenovo ThinkCentre Chromebox | TIDUS | 2015 | Intel Broadwell[5] | Probably | Yes[5] | |||
| Lenovo ThinkPad Yoga | GLIMMER | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Lenovo ThinkPad 11e Chromebook | GLIMMER | 2015 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Lenovo X131e Chromebook | STOUT | 2013 | Intel Ivy Bridge[3] | Probably | Yes[3] | |||
| Samsung Chromebook | SNOW | 2012 | ARM[2] | No[2] | - | - | - | |
| Samsung Chromebook 2 (XE500C12) | WINKY | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | Installation |
| Samsung Chromebook 2 (XE503C12) | PIT | 2014 | ARM[2] | No[2] | - | - | - | |
| Samsung Chromebook 2 (XE503C32) | PI | 2014 | ARM[2] | No[2] | - | - | - | |
| Samsung Chromebook 3 | CELES | 2016 | Intel Braswell[7] | ? | not yet (Mar 2016) | |||
| Samsung Series 3 Chromebox | STUMPY | 2012 | Intel Sandy Bridge[3] | Probably | No | Yes[3] | No | |
| Samsung Series 5 | ALEX | 2011 | Intel Pineview[1] | No[1] | - | - | - | |
| Samsung Series 5 550 | LUMPY | 2012 | Intel Sandy Bridge[3] | Yes | Yes[3] | |||
| Senkatel Edu | ENGUARDE | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Toshiba Chromebook CB30 | LEON | 2014 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | |
| Toshiba Chromebook CB35 | LEON | 2014 | Intel Haswell[4] | Yes | Yes | Yes[4] | Yes[8] | |
| Toshiba Chromebook 2 CB30 | SWANKY | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Toshiba Chromebook 2 CB35 | SWANKY | 2014 | Intel Bay Trail[6] | Yes | No | Yes[6] | No | |
| Toshiba Chromebook 2 CB35 | GANDOF | 2015 | Intel Broadwell[5] | Yes | possibly | Yes[5] | Yes, after firmware update?[8] | |
| Model | Hardware ID | Released | Processor | Supports GalliumOS? | … with factory firmware? | … with custom firmware? | … dual-boot with ChromeOS?[8] | More Info |
Notes
<references> [1] [3] [4] [6] [5] [2] [7] [9] [10] [11] [12] [8]
- Pineview models do not ship with compatible firmware, and custom firmware is not available at this time. See Support/Pineview.
- ARM models do not ship with compatible firmware, and custom firmware is not available at this time. See Support/ARM.
- Sandy/Ivy Bridge models, see Support/SandyIvy.
- Haswell models are well-supported. See Support/Haswell.
- Broadwell models are well-supported. See Support/Broadwell.
- Bay Trail models are well-supported in 1.0beta2 and later. See Support/BayTrail.
- Braswell models are new and not well-supported. See Support/Braswell.
- Dual-Booting with ChromeOS is possible where the factory firmware supports SeaBIOS, or the custom firmware installs SeaBIOS without removing ChromeOS boot functionality. Currently, dual-boot systems must be installed with chrx.
- 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. Custom firmware is the only resolution.
- HiDPI: This model has a 2560x1700 display. GalliumOS (Xfce, Gtk2, xfwm4) does not support HiDPI at this geometry, so display resolution will be limited.
- SAMUS (Google Pixel, 2015) has known issues with internal audio.
- 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.
