== Installing GalliumOS on the Google Pixel 2015 (Samus) ==

=== Download and Write GalliumOS to USB ===
# Download the appropriate iso from [https://galliumos.org/download.html here]. For this tutorial, you’ll need the Chromebook Broadwell ISO.
# Download Win32DiskImager from [[sourceforge:projects/win32diskimager/|SourceForge]] and install it. Linux/Mac users will use a terminal.
# Insert an empty USB drive (all data will be erased during the write process!). Run Win32DiskImager. Make sure you have the correct USB drive selected under “Device.” Click on the blue folder icon. On the bottom right you’ll see, Disk Images (*.img *.IMG). Click on it and change it to *.* Now you’ll be able to locate the GalliumOS iso. Locate it and double-click it. Making sure that you have the correct USB selected, click on “Write.” When the USB is ready, eject it and put it aside for when you’ll need it later in this tutorial.
# Linux/Mac users need to follow the instructions found [https://galliumos.org/wiki/index.php?title=Installing/Creating_Bootable_USB here].

=== Backup data ===
If you have any data stored locally on the chromebook that you would like to keep, backup the data to either a USB drive or to Google Drive. '''Enabling developer mode will wipe your device.'''

=== Enable Developer Mode and Boot Flags ===
# Boot into recovery by press and hold the Esc + Refresh keys, then press the power button.
# At the Recovery screen press Ctrl-D. It will ask you to confirm by pressing the RECOVERY BUTTON again. It will now enable Developer Mode. It will take about 10-15 minutes to complete. During this time, your chromebook will be wiped of all user data.
# You’ll see a white screen after rebooting. Press Ctrl-D and you’ll boot into ChromeOS with Developer Mode enabled.
# Connect to the Internet and accept the terms and agreements. You don’t have to login to ChromeOS using your account (you can if you want to, but I didn’t). Login as Guest and open up a Crosh session by pressing Ctrl-Alt-T. Type <code>shell</code> and hit enter to open bash. The prompt should look like this: <code>chronos@localhost / $</code>
# Alternatively, ou can immediately press Ctrl+Alt+F2 to get to a TTY.
# Type <code>sudo crossystem dev_boot_usb=1 dev_boot_legacy=1</code> and hit enter.

=== Boot from USB ===
# Reboot your Chromebook
# Press Ctrl-L at the scary white screen.
# Press the ESC key when you see the prompt to do so. You’ll now be in the boot menu.(If you don’t press ESC in time just reboot and do it again.)
# At the boot menu you’ll see your boot options. Select to boot from USB.
# You’ll now get the option to live boot or install GalliumOS. You want to live boot.
# Test GalliumOS. Explore until you’re sure everything works fine. If you decide to install GalliumOS (and why wouldn’t you?), don’t install it while you’re live booted. For some reason that didn’t work for me, and I had to do it over again. Instead, reboot and follow the above steps until you get to the live boot or install GalliumOS menu. Choose Install GalliumOS. There’ll be a few prompts during the installation process.
## Disclaimer: From here on out once you install Gallium you will need to hit those keys after each reboot unless you are willing to open the Pixel and remove a Write Protect screw to allow you to disable that screen. Be aware you DON'T NEED TO DO THIS with that screw unless you don't want to hit those keys, the Pixel 2015 doesn't have the out of power glitch the original Pixel had and with the Developer Screen there it provides a very nice fail safe in case you severely screw up your install and want to move back to ChromeOS again.

=== Installing GalliumOS ===
# Installing Gallium is the easiest albeit the most flexible part of this process. Run the installer located on the desktop of the Live USB environment and follow through the prompts with your preferences (I'd recommend connecting to the internet if you can and also selecting the Download Extra Software option) until you get to Partitioning portion. This can be highly subjective on how you want to setup this partitioning BUT for me this is what I went with:
## After that hit the Plus Icon. This will be your main partition where everything will be run from, you can set it to be the full size of the disk if you want with no issues since Gallium uses ZRam. Set it to be formated to "EXT4" and for the Mount point select "/". Hit OK and give it a second to resize the partitions.
## After that hit next and a confirmation screen will ask for sure if you want to do this, select OK if you are.
# After that you will be prompted for Region, Keyboard, User name, yadayada you should know what to do here.
# At this point it will then install everything and prompt you to reboot. Reboot the unit and remove your install media at the prompt

=== Post GalliumOS Install ===

==== Update GalliumOS Packages ====
In terminal update the packages by executing the following command:

<code>sudo apt-get update</code>
<code>sudo apt-get dist-upgrade</code>

Reboot the unit and once you get it up and running we will need to install a few things to get this started.

==== Install Git ====
First we will need to install this, this is how you are going to build the kernel from Github where its hosted. Open a terminal window up and type:
<code> sudo apt-get install git</code>
This will bring up a long list of dependencies and files to install, just hit "y" and let it do its thing.

==== Installing Kernel Source ====
Now for the Kernel work (thanks to Raphael, https://github.com/raphael/linux-samus). Open up a Terminal (it will start at /home/"Your Username" by default, so every command below is located in /home/"Your Username"/"cd command" as a reference for you) and Type:
git clone https://github.com/raphael/linux-samus
This will start the download and compile of the Kernel, its a little less than 100,000 files so probably grab some coffee. Once that is done, navigate to the folder below or type:
cd linux-samus/build/debian
After that install the kernel via:
sudo dpkg -i *.deb
Now the kernel will be installed! For good measure to update grub, type:
sudo update-grub
Now you should be able to reboot and once the unit comes back you should be able to use the touchpad far more effectively (still needs a little more configuring) and can start the final bits of setting up the sound, Xorg optimizations, and screen brightness key commands.

==== XOrg and Touchpad Tweaks ====
I'll list the easy ones first, Xorg and touchpad tweaks. With Xorg you will need to type into terminal:
cd linux-samus/scripts/setup/xorg
./xaccel.sh
There won't be any confirmation message, if you get an error message you will want to confirm you are in the correct directory. After that we will do the touchpad tweaks. First we need to enable an Atmel script first, after that we will be setting up up a service to run the script. This is because since Linux 4.3 the Atmel chip needs to be reset on boot to guarantee that the touchpad works. First you will enter:
cd linux-samus/scripts/setup/touchpad
./enable-atmel.sh
After that you will want to run the systemd script:
./setup.systemd.sh
At this point you should have a fully functioning trackpad and be able to avoid random unresponsive moments. Now we will setup the Brightness Keys. If you don't want to change the keys default behavior as F-Keys then don't bother with this step.
cd scripts/setup/brightness
./brightness --help
This enables F6 and F7 to change screen brightness
./keyboard_led --help
This enables ALT-F6 and ALT-F7 to change keyboard brightness.
./setup.systemd.sh
This setups up these scripts as a service. At this point the easy stuff is done, last is the sound which is definitely the hardest part of the process.

==== Setting up Sound ====
Setting up sound can POSSIBLY be done via the sound script Raphael made but I rarely have luck with it. I still recommend doing it just to see if it works and to do some of the work for you, but its probably going to take doing each step separately. To run the script:
cd linux-samus/scripts/setup/sound
./sound.sh
At this point you can try the speakers by clicking the PulseAudio tray icon and setting up the following:
* Default Server to (Numbers)unix:/run/user/1000/pulse/native
* Default Sink to bdw-rt677 Analog Stereo
* Volume Control/Output Devices/bdw-rt677 Analog Stereo and set to fallback and to the port you want to listen through (Headphones or Speakers).
Give this a test, if it works you lucked out! If not, then we need to follow the script steps manually. Most of this is verbatim from Raphael's Readme with a few tweaks in areas I got confused on or fixed something for Gallium Specifically. The first thing to do is to copy over the firmware files from the firmware directory to wherever your distribution installs firmware (/lib/firmware).After that open a add a default.conf file in /etc/modprobe.d containing the following line:
options snd slots=snd_soc_sst_bdw_rt5677_mach,snd-hda-intel
SHUTDOWN and POWER BACK ON (Reboot doesn't seem to work 100% with Gallium) your computer and after that open a Terminal windows and type:
aplay -l
Hopefully it should output:
**** List of PLAYBACK Hardware Devices ****
card 0: bdwrt5677 [bdw-rt5677], device 0: System Playback (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
If this doesn't show up check for errors through dmesg. At this point change directory to:
cd linux-samus/scripts/setup/sound
After that type the command:
ALSA_CONFIG_UCM=ucm/ alsaucm -c bdw-rt5677 set _verb HiFi
At this point we will have the speakers and headphones setup properly but we have a few more steps to get the mic working. Next you will be opening the PulseAudio config (default.pa) as root to load the mic modules located in:
/etc/pulse/default.pa
You can also edit with commands:
sudo mousepad /etc/pulse/default.pa
Add the lines above load-module module-udev-detect:
load-module module-alsa-source device=hw:0,1
load-module module-alsa-source device=hw:0,2
The guide recommends you just restart PulseAudio but I found it more consistent to just power down and back on. After that open Terminal again and run commands:
cd linux-samus/scripts/setup/sound
sudo alsactl restore --file alsa/asound.state

WOO! We did it! At this point you may need to power down and back on one more time to get it to work but for me it worked right after the restore state command. If it still doesn't work check these steps again:
* Default Server to (Numbers)unix:/run/user/1000/pulse/native
* Default Sink to bdw-rt677 Analog Stereo
* Volume Control/Output Devices/bdw-rt677 Analog Stereo and set to fallback and to the port you want to listen through (Headphones or Speakers).

=== Success ===
You now have GalliumOS installed. How cool is that?

If you run into problems or have any questions, the awesome people at [https://kiwiirc.com/client/irc.freenode.net#galliumos #GalliumOS] are happy to help in any way they can. You can also post on [https://www.reddit.com/r/galliumos/ /r/galliumos].

=== Sources ===
https://www.reddit.com/r/GalliumOS/comments/47qeh0/pixel_setup_guide_for_gallium_os/

https://galliumos.org/wiki/index.php?title=Installing/Preparing

Hardware Compatibility

2016-02-27T00:53:58Z

Jdferron: /* GalliumOS Support by Model */

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''', 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 [https://github.com/GalliumOS/galliumos-distro/issues issue tracker] and submit a bug report.

Firmware updates for many devices are available from [https://johnlewis.ie/custom-chromebook-firmware/rom-download/ John Lewis] or [https://github.com/MattDevo/scripts Matt Devillier].

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



<ref name="Pineview"/>
<ref name="ARM"/>
<ref name="SandyIvy"/>
<ref name="Haswell"/>
<ref name="Broadwell"/>
<ref name="BayTrail"/>
<ref name="Braswell"/>
<ref name="chrx"/>
<ref name="TextMode"/>
<ref name="HiDPI2560"/>
<ref name="SAMUS"/>
<ref name="PANTHER"/>


== GalliumOS Support by Model ==



{| class="wikitable"
|-
! scope="col"| Model
! scope="col"| Hardware ID
! scope="col"| Released
! scope="col"| Processor
! scope="col"| Supports GalliumOS?
! scope="col"| … with factory firmware?
! scope="col"| … with custom firmware?
! scope="col"| … dual-boot with ChromeOS?<ref name="chrx"/>
! scope="col"| More Info
|-
| 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
| style="text-align:center;" | [[Installing/Parrot|Installation]]
|-
| 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
| style="text-align:center;" | [[Installing/Parrot|Installation]]
|-
| Acer C720
| 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"/>
| style="text-align:center;" | [[Installing/Peppy|Installation]]
|-
| Acer 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"/>
| style="text-align:center;" | [[Installing/Peppy|Installation]]
|-
| 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:#ffe8e8" | No
|-
| Acer C910
| YUNA
| 2014
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Major 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, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook 11 C740
| PAINE
| 2014
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Tested
| style="text-align:center;background-color:#ffffcc" | Major 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, after firmware update<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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| 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 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:#ffe8e8" | No
|-
| 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" | Major 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, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook R11
| CYAN
| 2015
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | ?
|
| style="text-align:center;background-color:#ffe8e8" | not yet (Dec 2015)
|
|-
| 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"/>
| style="text-align:center;" | [[Installing/Panther|Installation]]
|-
| Acer Chromebox CXI2
| RIKKU
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Major 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, after firmware update<ref name="chrx"/>
|
|-
| ASUS 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:#ffe8e8" | No
|-
| ASUS C201
| 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 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:#ffe8e8" | No
|-
| ASUS Chromebox
| PANTHER
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Major issue: USB init<ref name="PANTHER"/>
| 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"/>
| style="text-align:center;" | [[Installing/Panther|Installation]]
|-
| ASUS Chromebox CN62
| GUADO
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Major 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, after firmware update<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 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:#ffe8e8" | No
|-
| Dell Chromebook 11
| WOLF
| 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"/>
|-
| 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:#ffe8e8" | No
|-
| Dell Chromebook 13
| LULU
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Major 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, after firmware update?<ref name="chrx"/>
| style="text-align:center;" | [[Installing/Lulu|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Panther|Installation]]
|-
| Google Chromebook Pixel
| LINK
| 2013
| Intel Ivy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffffcc" | known issues, including HiDPI<ref name="HiDPI2560"/> custom build planned
| 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:#ffffcc" | Yes, with issues: audio<ref name="SAMUS"/>, HiDPI<ref name="HiDPI2560"/>
| 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"/>
| style="text-align:center;" | [[Installing/Samus|Installation]]
|-
| Google Cr-48
| MARIO
| 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" | -
|-
| 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:#ffffcc" | ?
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffe8e8" | not yet (Dec 2015)
| style="text-align:center;background-color:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| HP Chromebox
| ZAKO
| 2014
| Intel Haswell<ref name="Haswell"/>
| style="text-align:center;background-color:#ccffcc" | Yes
| style="text-align:center;background-color:#ffffcc" | Major issue: USB init<ref name="PANTHER"/>
| 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"/>
| [[Installing/Panther|Installation]]
|-
| HP Pavilion Chromebook 14
| BUTTERFLY
| 2013
| Intel Sandy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffffcc" | Probably
|
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
|
|-
| LG Chromebase
| 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"/>
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| Lenovo ThinkCentre Chromebox
| TIDUS
| 2015
| Intel Broadwell<ref name="Broadwell"/>
| style="text-align:center;background-color:#ffffcc" | Probably
|
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
|
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| Lenovo X131e Chromebook
| STOUT
| 2013
| Intel Ivy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffffcc" | Probably
|
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
|
|-
| Samsung Chromebook
| 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:#ffe8e8" | No
| style="text-align:center;" | [https://sites.google.com/site/winkychromebook/ Installation]
|-
| 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 Series 3 Chromebox
| STUMPY
| 2012
| Intel Sandy Bridge<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffffcc" | Probably
| style="text-align:center;background-color:#ffcccc" | No
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="SandyIvy"/>
| style="text-align:center;background-color:#ffcccc" | No
|-
| Samsung Series 5
| 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:#ccffcc" | Yes<ref name="SandyIvy"/>
|
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| 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:#ffe8e8" | No
|-
| 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" | possibly
| style="text-align:center;background-color:#ccffcc" | Yes<ref name="Broadwell"/>
| 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?
! scope="col"| … with custom firmware?
! scope="col"| … dual-boot with ChromeOS?<ref name="chrx"/>
! scope="col"| More Info
|-
|}

=== Notes ===

<references>
<ref name="Pineview">
'''Pineview''' models do not ship with compatible firmware, and custom firmware is not available at this time. See [[Support/Pineview]].
</ref>
<ref name="SandyIvy">
'''Sandy/Ivy Bridge''' models, 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 in 1.0beta2 and later. 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 new and '''not''' well-supported. See [[Support/Braswell]].
</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. This bug will hopefully be patched in future firmware versions (either from the factory or via ChromeOS update); for now, custom firmware is the only resolution.
</ref>
<ref name="HiDPI2560">'''HiDPI''':
This model has a 2560x1700 display. GalliumOS (Xfce, Gtk2, xfwm4) does not support HiDPI at this geometry, so display resolution will be limited.
</ref>
<ref name="SAMUS">'''SAMUS'''
(Google Pixel, 2015) has known issues with [https://github.com/GalliumOS/galliumos-distro/issues/100 internal audio].
</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="chrx">'''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 [https://chrx.org/ chrx].
</ref>
<references />

Installing

2016-02-27T00:51:46Z

Jdferron: /* Specific Device Install Documents */

Installing

2016-02-20T20:03:29Z

Jdferron:

== General Install Instructions ==
You have two possible options for installing GalliumOS:
# '''From an ISO image written to USB drive or SD card''' This method works on '''most''' devices, and enables you to entirely replace ChromeOS on your internal SSD or HDD. It also allows you to set up more complex configurations such as dual-booting alongside Windows or other Linux distributions.
# '''From the ChromeOS command-line using chrx''' This method works on '''many''' devices, and will configure your device to dual-boot GalliumOS alongside ChromeOS.

See [[Hardware Compatibility]] for the installation options available for your ChromeOS device model.

=== Traditional ISO Install ===

The traditional installer allows you to use your entire SSD or HDD for GalliumOS. You will need to use a USB flash drive or SD card. You can even boot the GalliumOS Live image to try out the features of GalliumOS before you decide to install!

# Go to [[Installing/Preparing]] and get your Chromebook ready to run GalliumOS.
# Download a GalliumOS suitable for your device ISO from the [https://galliumos.org/download.html downloads page on GalliumOS.org]
# Write (or "burn") the ISO to a USB flash drive or an SD card. Detailed instructions for this are at [[Installing/Creating Bootable USB]]
# Plug your USB flash drive or SD card into your Chromebook
# Reboot your Chromebook and boot from the USB flash drive or SD card.
## If you have installed custom firmware, press Esc at the BIOS screen and press 2 to boot from USB.
## If you have the scary white screen, press Ctrl+L.
# Wait for GalliumOS to boot up. Once in the live environment you can play around with GalliumOS, or you can install it using the Install GalliumOS icon on the desktop.

=== chrx Installation ===

GalliumOS is also installable on many ChromeOS devices via [https://chrx.org/ chrx], which allows you to dual-boot GalliumOS alongside ChromeOS. Check the [https://chrx.org/#compatibility chrx hardware compatibility list] to see if your device supports chrx, and whether any preparation steps are required.

See [https://chrx.org#usage chrx installation instructions] for full details, but here's a quick overview:

# Prepare your ChromeOS device
## Enable Developer Mode
## Install firmware feature update if required (some Broadwell devices only)
# Boot device into ChromeOS and configure networking; you do not need to log in
# Switch to a virtual terminal by pressing <code>CTRL+ALT+F2(top row right arrow)</code>, then log in as user <code>chronos</code> with no password
# Run chrx: <code>curl -O <nowiki>https://chrx.org/go</nowiki> && sh go -d galliumos</code> (see [https://chrx.org/#options chrx docs] for additional options)
# Follow on-screen prompts to repartition your SSD and install GalliumOS. If this is the first time running chrx on this ChromeOS machine, chrx will reboot after the partitioning step and you will need to continue the installation by running chrx again with the same command line.
# After reboot, at the white "OS verification is OFF" screen, press <code>CTRL+L</code> for GalliumOS, or <code>CTRL+D</code> for ChromeOS

== Specific Device Install Documents ==
Our community is also making in-depth install guides for certain devices. Below is a list.
* [[Installing/Lulu|Lulu (Dell Chromebook 13 7310)]]
* [[Installing/Panther|Panther (ASUS Chromebox 2014)]]
* [[Installing/Parrot|Parrot (Acer C710, Acer C7)]]
* [[Installing/Peppy|Peppy (Acer C720, Acer C720P)]]
* [[Installing/Kip|Kip (HP Chromebook 11 G3, HP Chromebook 11 G4, HP Chromebook 14 G4)]]
__FORCETOC__