GalliumOS Wiki - User contributions [en]

Welcome to the GalliumOS Wiki

2021-06-20T02:06:30Z

ColtonDRG: Changed protection level for "Welcome to the GalliumOS Wiki" ([Move=Allow only administrators] (indefinite))

[https://galliumos.org/ GalliumOS] is a fast and lightweight Linux distro made for Chromebooks and Chromeboxes. GalliumOS delivers a complete Linux environment with full hardware support, a carefully tuned kernel, and a full-featured and attractive desktop.

== Downloads ==

Check our [[Hardware Compatibility]] table to determine whether your Chromebook or Chromebox will support GalliumOS.

==== GalliumOS 3.1 ====

* '''[https://galliumos.org/download Downloads, Mirrors, and Torrents]'''
* [[News/GalliumOS 3.1|Release Notes]]

==== GalliumOS Nightly Builds (experimental!) ====

* [[Nightly Builds|Information]]

== Documentation ==

* '''[[Why GalliumOS?]]'''
* '''[[Installing|Installing GalliumOS]]'''
* '''[[Media keys and default keybindings]]'''
* '''[[Hardware Compatibility]]'''
* '''[[FAQ]]'''
* '''[[Media|GalliumOS Media Coverage]]'''

== Community ==

* '''User Forums''' are hosted on Reddit: https://www.reddit.com/r/GalliumOS/
* '''Discussion''' happens on IRC Freenode #galliumos: https://galliumos.org/irc
* '''Development''' happens on GitHub: https://github.com/GalliumOS
* '''Issues''' are tracked on GitHub too: https://github.com/GalliumOS/galliumos-distro/issues

== Getting Involved ==

We are a small team with a big goal. If you'd like to help with code, design, devops, documentation (including this wiki!), testing and profiling, or anything else, join us in [https://kiwiirc.com/client/irc.freenode.net#galliumos #galliumos] or on [https://reddit.com/r/GalliumOS Reddit]. We'd love to meet you!

=== Editing this wiki ===

If you would like an account to add or edit pages on the GalliumOS wiki, please get in touch via [https://kiwiirc.com/client/irc.freenode.net#galliumos #galliumos]. Thank you.

__NOTOC__

Media keys and default keybindings

2020-04-20T22:40:33Z

ColtonDRG: /* Keyboard Shortcuts */

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'''<br>'''** 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<br>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).<br>
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<br>Also available with <code>Overlay</code> + number key (0 for F10)
|-
|F11
|<code>Overlay</code> + <code>-</code>
|-
|F12
|<code>Overlay</code> + <code>+</code>
|-
|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>Right Shift</code><br>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><br>Super as Overlay: <code>Left-Alt</code> + <code>M</code>
|-
|Keyboard Backlight Toggle
|<code>Overlay</code> + <code>\</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

2020-04-20T22:40:00Z

ColtonDRG: /* Key Mappings */

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'''<br>'''** 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<br>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).<br>
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<br>Also available with <code>Overlay</code> + number key (0 for F10)
|-
|F11
|<code>Overlay</code> + <code>-</code>
|-
|F12
|<code>Overlay</code> + <code>+</code>
|-
|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>Right Shift</code><br>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><br>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

2020-04-20T22:39:41Z

ColtonDRG: /* Key Mappings */

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'''<br>'''** 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<br>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).<br>
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
|Also available with <code>Overlay</code> + number key (0 for F10)
|-
|F11
|<code>Overlay</code> + <code>-</code>
|-
|F12
|<code>Overlay</code> + <code>+</code>
|-
|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>Right Shift</code><br>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><br>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

2019-06-21T20:13:49Z

ColtonDRG: /* Key Mappings */

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'''<br>'''** 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<br>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).<br>
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>Right Shift</code><br>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><br>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>
|}

VirtualBox

2019-06-21T00:50:46Z

ColtonDRG: Redirected page to Installing/VirtualBox

#REDIRECT [[Installing/VirtualBox]]

Hardware Compatibility2

2019-06-12T01:58:19Z

ColtonDRG: Redirected page to Hardware Compatibility

#REDIRECT [[Hardware Compatibility]]

Support/Haswell

2019-06-10T20:48:10Z

ColtonDRG:

Haswell core Intel processors are common in many 2013 and 2014 ChromeOS devices.

Support for Haswell Chromebooks has been implemented in upstream Linux with aplomb, so you should be able to run any recent Linux distribution you please with little to no friction.

Factory firmware support for booting legacy OSes via SeaBIOS is common, but custom firmware is also available for all Haswell models as well -- see [[Firmware]].

== Model-Specific Notes ==

=== ASUS Chromebox, 2014 (PANTHER) / HP Chromebox, 2014 (ZAKO) ===
* Factory legacy boot firmware bug prevents use of attached USB devices at boot, including keyboard
** While installation is possible with factory firmware, it is less than ideal.
** Custom firmware does not have bug; update <code>RW_LEGACY</code>. See [[Installing/Panther]].

Support/Broadwell

2019-06-10T20:45:51Z

ColtonDRG:

Broadwell core Intel processors are popular in higher end 2014 and 2015 Chromebooks.

Support for Broadwell Chromebooks has been implemented in upstream Linux with aplomb, so you should be able to run any recent Linux distribution you please with little to no friction.

Factory firmware support for coreboot and SeaBIOS is generally good on Broadwell models (with a few bugs), but custom firmware is also available -- see [[Firmware]].

=== GRUB bug with some factory firmwares ===
* One firmware bug relates to video init in early boot, which prevents the display of the GRUB boot menu. This can be worked around with GRUB settings:
** # Add settings to '''<code>/etc/default/grub</code>'''
** #* <code>GRUB_TERMINAL=console</code>
** #* <code>GRUB_GFXMODE=1024x768</code>
** # Run '''<code>sudo update-grub</code>'''
* This bug is not present on full custom [[Firmware]].

Support/Broadwell

2019-06-10T20:43:58Z

ColtonDRG:

Broadwell core Intel processors are popular in higher end 2014 and 2015 Chromebooks.

Support for Broadwell Chromebooks has been implemented in upstream Linux with aplomb, so you should be able to run any recent Linux distribution you please with little to no friction.

Factory firmware support for coreboot and SeaBIOS is generally good on Broadwell models (with a few bugs), but custom firmware is also available -- see [[Firmware]].

One firmware bug relates to video init in early boot, which prevents the display of the GRUB boot menu. This can be worked around with GRUB settings:

# Add settings to '''<code>/etc/default/grub</code>'''
#* <code>GRUB_TERMINAL=console</code>
#* <code>GRUB_GFXMODE=1024x768</code>
# Run '''<code>sudo update-grub</code>'''

This bug is not present on full custom [[Firmware]].

Support/Haswell

2019-06-10T20:39:55Z

ColtonDRG:

Intel processors using the Haswell architecture are very popular in 2013/2014-era ChromeOS devices.

Support for Haswell Chromebooks has been implemented in upstream Linux with aplomb, so you should be able to run any Linux distribution you please with little to no friction.

Factory firmware support for booting legacy OSes via SeaBIOS is common, but custom firmware is also available for all Haswell models as well -- see [[Firmware]].

== Model-Specific Notes ==

=== ASUS Chromebox, 2014 (PANTHER) / HP Chromebox, 2014 (ZAKO) ===
* Factory legacy boot firmware bug prevents use of attached USB devices at boot, including keyboard
** While installation is possible with factory firmware, it is less than ideal.
** Custom firmware does not have bug; update <code>RW_LEGACY</code>. See [[Installing/Panther]].

Installing/

2017-06-26T06:12:29Z

ColtonDRG: Redirected page to Installing

#REDIRECT [[Installing]]

News/2016 Annual Report and Announcement

2017-01-20T18:18:43Z

ColtonDRG: /* Shirts and Stickers */

== GalliumOS Project, 2016 ==

As we close the books on our first full year of operations, we'd like to thank everyone who helped make it such a great year for the GalliumOS Project!

Thank you for contributing, answering questions on Reddit and IRC, ''asking'' questions on Reddit and IRC, researching configuration tweaks, testing new builds, and reporting successes and failures.

We're looking forward to more in 2017, and hope you'll join us for the ride!

We have some announcements as well as some statistics for the past year.

== Shirts and Stickers ==

<gallery mode="traditional">
Image:stickerClear.png| Clear with just the logo
Image:stickerWhite.png| White with the logo and "GalliumOS"
Image:shirt.png| Blue unisex shirt with logo and "GalliumOS"
</gallery>

We now have stickers available to people that donate through PayPal for this year. They come in two varieties. If you'd like stickers, please send a mailing address with your PayPal donation. To donate, please go to [https://galliumos.org/donate our donation page.] Each mailing address sent with a donation will receive one of each variety of sticker.

We also have [https://teespring.com/galliumos shirts available] for a limited time through Teespring. They have the logo with "GalliumOS" on the front in your choice of blue, black, or gray, in unisex or women's. The campaign will run for two weeks, from January 18th to February 1st. If you miss your chance to purchase a shirt, don't worry, we will run the campaign again another time. We have made the shirts as inexpensive as possible, and any proceeds that we receive will be put into the donation pool.

== 2016 in Numbers ==

=== Global Domination, Progress Toward ===

{| class="wikitable"
|-
| '''45,194'''
| ISO Downloads:<br>
{| class="wikitable"
| style="text-align:right;" | 19,088
| Haswell
|-
| style="text-align:right;" | 7,834
| Broadwell
|-
| style="text-align:right;" | 14,249
| Bay Trail
|-
| style="text-align:right;" | 3,556
| Sandy/Ivy Bridge
|-
| style="text-align:right;" | 399
| Braswell
|-
| style="text-align:right;" | 33
| Skylake
|-
| style="text-align:right;" | 36
| Samus
|}
|-
| '''16,344'''
| chrx installs
|}

=== Web Statistics ===

==== galliumos.org ====

{| class="wikitable"
|-
| style="text-align:right;" | '''20,811'''
| Monthly unique users
|-
| style="text-align:right;" | '''66,792'''
| Monthly page views
|-
| style="text-align:right;" | '''2343 GB'''
| Monthly data transfer
|}

==== Reddit ====

{| class="wikitable"
|-
| style="text-align:right;" | '''5,581'''
| Monthly unique users
|-
| style="text-align:right;" | '''20,477'''
| Monthly page views
|}

=== Finances ===

{| class="wikitable"
|-
| style="text-align:right;" | '''$89.76'''
| Account balance, starting 2016
|-
| style="text-align:right;" | '''193'''
| Contributions
|-
| style="text-align:right;" | '''$3850.01'''
| Total contributions
|-
| '''$3198.08'''
| Expenses:<br>
{| class="wikitable"
| style="text-align:right;" | $182.21
|PayPal fees
|-
| style="text-align:right;" | $657.41
|Hosting for web/download/build servers
|-
| style="text-align:right;" | $1478.41
|Hardware for test and development<br>(GNAWTYx2, BANJO, CYAN, EDGAR, LARS, TERRA, SENTRY)
|-
| style="text-align:right;" | $87.53
|Other (domain renewals, shipping costs, etc)
|-
| style="text-align:right;" | $100.00
|Donation to the Numix Project
|-
| style="text-align:right;" | $133.00
|GalliumOS promotional stickers
|-
| style="text-align:right;" | $559.52
|Taxes, estimated
|}
|-
| style="text-align:right;" | '''$741.69'''
| Account balance, starting 2017
|}

== 2.1 Progress ==

Soon! We have functional UEFI multiboot images in testing, and audio is working on a couple of Braswell devices now. It's still a work in progress, and we appreciate all the help from testers and contributors alike.

== Thank You! ==

- The GalliumOS Team, 20170117

News/2016 Annual Report and Announcement

2017-01-20T18:18:28Z

ColtonDRG: /* Shirts and Stickers */

== GalliumOS Project, 2016 ==

As we close the books on our first full year of operations, we'd like to thank everyone who helped make it such a great year for the GalliumOS Project!

Thank you for contributing, answering questions on Reddit and IRC, ''asking'' questions on Reddit and IRC, researching configuration tweaks, testing new builds, and reporting successes and failures.

We're looking forward to more in 2017, and hope you'll join us for the ride!

We have some announcements as well as some statistics for the past year.

== Shirts and Stickers ==

<gallery mode="traditional">
Image:stickerClear.png| Clear with just the logo
Image:stickerWhite.png| White with the logo and "GalliumOS"
Image:shirt.png| Blue unisex shirt with logo and "GalliumOS"
</gallery>

We now have stickers available to people that donate through PayPal for this year. They come in two varieties. If you'd like stickers, please send a mailing address with your PayPal donation. To donate, please go to [https://galliumos.org/donate our donation page.] Each mailing address send with a donation will receive one of each variety of sticker.

We also have [https://teespring.com/galliumos shirts available] for a limited time through Teespring. They have the logo with "GalliumOS" on the front in your choice of blue, black, or gray, in unisex or women's. The campaign will run for two weeks, from January 18th to February 1st. If you miss your chance to purchase a shirt, don't worry, we will run the campaign again another time. We have made the shirts as inexpensive as possible, and any proceeds that we receive will be put into the donation pool.

== 2016 in Numbers ==

=== Global Domination, Progress Toward ===

{| class="wikitable"
|-
| '''45,194'''
| ISO Downloads:<br>
{| class="wikitable"
| style="text-align:right;" | 19,088
| Haswell
|-
| style="text-align:right;" | 7,834
| Broadwell
|-
| style="text-align:right;" | 14,249
| Bay Trail
|-
| style="text-align:right;" | 3,556
| Sandy/Ivy Bridge
|-
| style="text-align:right;" | 399
| Braswell
|-
| style="text-align:right;" | 33
| Skylake
|-
| style="text-align:right;" | 36
| Samus
|}
|-
| '''16,344'''
| chrx installs
|}

=== Web Statistics ===

==== galliumos.org ====

{| class="wikitable"
|-
| style="text-align:right;" | '''20,811'''
| Monthly unique users
|-
| style="text-align:right;" | '''66,792'''
| Monthly page views
|-
| style="text-align:right;" | '''2343 GB'''
| Monthly data transfer
|}

==== Reddit ====

{| class="wikitable"
|-
| style="text-align:right;" | '''5,581'''
| Monthly unique users
|-
| style="text-align:right;" | '''20,477'''
| Monthly page views
|}

=== Finances ===

{| class="wikitable"
|-
| style="text-align:right;" | '''$89.76'''
| Account balance, starting 2016
|-
| style="text-align:right;" | '''193'''
| Contributions
|-
| style="text-align:right;" | '''$3850.01'''
| Total contributions
|-
| '''$3198.08'''
| Expenses:<br>
{| class="wikitable"
| style="text-align:right;" | $182.21
|PayPal fees
|-
| style="text-align:right;" | $657.41
|Hosting for web/download/build servers
|-
| style="text-align:right;" | $1478.41
|Hardware for test and development<br>(GNAWTYx2, BANJO, CYAN, EDGAR, LARS, TERRA, SENTRY)
|-
| style="text-align:right;" | $87.53
|Other (domain renewals, shipping costs, etc)
|-
| style="text-align:right;" | $100.00
|Donation to the Numix Project
|-
| style="text-align:right;" | $133.00
|GalliumOS promotional stickers
|-
| style="text-align:right;" | $559.52
|Taxes, estimated
|}
|-
| style="text-align:right;" | '''$741.69'''
| Account balance, starting 2017
|}

== 2.1 Progress ==

Soon! We have functional UEFI multiboot images in testing, and audio is working on a couple of Braswell devices now. It's still a work in progress, and we appreciate all the help from testers and contributors alike.

== Thank You! ==

- The GalliumOS Team, 20170117

News/2016 Annual Report and Announcement

2017-01-20T18:14:43Z

ColtonDRG: /* Shirts and Stickers */

== GalliumOS Project, 2016 ==

As we close the books on our first full year of operations, we'd like to thank everyone who helped make it such a great year for the GalliumOS Project!

Thank you for contributing, answering questions on Reddit and IRC, ''asking'' questions on Reddit and IRC, researching configuration tweaks, testing new builds, and reporting successes and failures.

We're looking forward to more in 2017, and hope you'll join us for the ride!

We have some announcements as well as some statistics for the past year.

== Shirts and Stickers ==

<gallery mode="traditional">
Image:stickerClear.png| Clear with just the logo
Image:stickerWhite.png| White with the logo and "GalliumOS"
Image:shirt.png| Blue unisex shirt with logo and "GalliumOS"
</gallery>

We now have stickers available to people that donate through PayPal for this year. They come in two varieties. If you'd like stickers, please send a mailing address with your PayPal donation. To donate, please go to [https://galliumos.org/donate our donation page.] Each mailing address send with a donation will receive one of each variety of sticker.

We also have [https://teespring.com/galliumos shirts available] for a limited time through Teespring. They have the logo with "GalliumOS" on the front in your choice of blue, black, or gray, in unisex or women's. The campaign will run for two weeks, from January 18th to February 1st. If you miss your chance to purchase a shirt, don't worry, we will run the campaign again another time.

== 2016 in Numbers ==

=== Global Domination, Progress Toward ===

{| class="wikitable"
|-
| '''45,194'''
| ISO Downloads:<br>
{| class="wikitable"
| style="text-align:right;" | 19,088
| Haswell
|-
| style="text-align:right;" | 7,834
| Broadwell
|-
| style="text-align:right;" | 14,249
| Bay Trail
|-
| style="text-align:right;" | 3,556
| Sandy/Ivy Bridge
|-
| style="text-align:right;" | 399
| Braswell
|-
| style="text-align:right;" | 33
| Skylake
|-
| style="text-align:right;" | 36
| Samus
|}
|-
| '''16,344'''
| chrx installs
|}

=== Web Statistics ===

==== galliumos.org ====

{| class="wikitable"
|-
| style="text-align:right;" | '''20,811'''
| Monthly unique users
|-
| style="text-align:right;" | '''66,792'''
| Monthly page views
|-
| style="text-align:right;" | '''2343 GB'''
| Monthly data transfer
|}

==== Reddit ====

{| class="wikitable"
|-
| style="text-align:right;" | '''5,581'''
| Monthly unique users
|-
| style="text-align:right;" | '''20,477'''
| Monthly page views
|}

=== Finances ===

{| class="wikitable"
|-
| style="text-align:right;" | '''$89.76'''
| Account balance, starting 2016
|-
| style="text-align:right;" | '''193'''
| Contributions
|-
| style="text-align:right;" | '''$3850.01'''
| Total contributions
|-
| '''$3198.08'''
| Expenses:<br>
{| class="wikitable"
| style="text-align:right;" | $182.21
|PayPal fees
|-
| style="text-align:right;" | $657.41
|Hosting for web/download/build servers
|-
| style="text-align:right;" | $1478.41
|Hardware for test and development<br>(GNAWTYx2, BANJO, CYAN, EDGAR, LARS, TERRA, SENTRY)
|-
| style="text-align:right;" | $87.53
|Other (domain renewals, shipping costs, etc)
|-
| style="text-align:right;" | $100.00
|Donation to the Numix Project
|-
| style="text-align:right;" | $133.00
|GalliumOS promotional stickers
|-
| style="text-align:right;" | $559.52
|Taxes, estimated
|}
|-
| style="text-align:right;" | '''$741.69'''
| Account balance, starting 2017
|}

== 2.1 Progress ==

Soon! We have functional UEFI multiboot images in testing, and audio is working on a couple of Braswell devices now. It's still a work in progress, and we appreciate all the help from testers and contributors alike.

== Thank You! ==

- The GalliumOS Team, 20170117

Installing/Creating Bootable USB

2016-09-30T16:52:37Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

'''If you would like a video to follow along with''', I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, '''download the correct version of GalliumOS for your device''' from https://galliumos.org/download If you don't know which version you need, check out the [[Hardware Compatibility]] page.

Also, '''download the correct version of Etcher for your operating system''' from http://www.etcher.io/
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

# First, you need to download the GalliumOS iso for your Chromebook.
# Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.
# cd to the place where you downloaded the iso. It's probably ~/Downloads.
# <code>cd ~/Downloads</code>
#Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.
# <code>sudo umount -f /dev/sdb1</code>
# Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.
# <code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>
#Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==

Before you get started, '''download the correct version of GalliumOS for your device''' from https://galliumos.org/download If you don't know which version you need, check out the [[Hardware Compatibility]] page.

Also, '''download and install Win32DiskImager''' from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.

# '''Launch Win32DiskImager'''
# '''Plug in your USB device''' and identify it's drive letter.
# '''Click the folder button''' next to the empty box on Win32DiskImager.
# '''Change the file type''' from Disk Images (.img) to *.*.
# '''Select the GalliumOS iso''' by navigating through the files and folders on your filesystem.
# '''Select the letter of your USB drive''' from the dropdown in Win32DiskImager.
# '''Click the Write button''' on Win32DiskImager.
# '''Confirm the write''' if prompted to overwrite or corrupt of physical device.
# '''Wait''' for it to finish... It may take a while.
# '''Click OK''' when you see the Write Successful popup.
# '''Eject your USB drive''' before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Installing/Creating Bootable USB

2016-09-30T16:50:40Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

'''If you would like a video to follow along with''', I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, '''download the correct version of GalliumOS for your device''' from https://galliumos.org/download If you don't know which version you need, check out the [[Hardware Compatibility]] page.
Also, '''download the correct version of Etcher for your operating system''' from http://www.etcher.io/
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

# First, you need to download the GalliumOS iso for your Chromebook.
# Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.
# cd to the place where you downloaded the iso. It's probably ~/Downloads.
# <code>cd ~/Downloads</code>
#Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.
# <code>sudo umount -f /dev/sdb1</code>
# Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.
# <code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>
#Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==

Before you get started, '''download the correct version of GalliumOS for your device''' from https://galliumos.org/download If you don't know which version you need, check out the [[Hardware Compatibility]] page.
Also, '''download and install Win32DiskImager''' from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.

# '''Launch Win32DiskImager'''
# '''Plug in your USB device''' and identify it's drive letter.
# '''Click the folder button''' next to the empty box on Win32DiskImager.
# '''Change the file type''' from Disk Images (.img) to *.*.
# '''Select the GalliumOS iso''' by navigating through the files and folders on your filesystem.
# '''Select the letter of your USB drive''' from the dropdown in Win32DiskImager.
# '''Click the Write button''' on Win32DiskImager.
# '''Confirm the write''' if prompted to overwrite or corrupt of physical device.
# '''Wait''' for it to finish... It may take a while.
# '''Click OK''' when you see the Write Successful popup.
# '''Eject your USB drive''' before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Installing/Creating Bootable USB

2016-09-30T16:47:12Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

'''If you would like a video to follow along with''', I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, '''download the correct version of GalliumOS for your device''' from https://galliumos.org/download If you don't know which version you need, check out the [Hardware_Compatibility] page.
Also, '''download the correct version of Etcher for your operating system''' from http://www.etcher.io/
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

First, you need to download the GalliumOS iso for your Chromebook.

Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.

cd to the place where you downloaded the iso. It's probably ~/Downloads.

<code>cd ~/Downloads</code>

Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.

<code>sudo umount -f /dev/sdb1</code>

Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.

<code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>

Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==

Before you get started, '''download the correct version of GalliumOS for your device''' from https://galliumos.org/download If you don't know which version you need, check out the [Hardware_Compatibility] page.
Also, '''download and install Win32DiskImager''' from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.

# '''Launch Win32DiskImager'''
# '''Plug in your USB device''' and identify it's drive letter.
# '''Click the folder button''' next to the empty box on Win32DiskImager.
# '''Change the file type''' from Disk Images (.img) to *.*.
# '''Select the GalliumOS iso''' by navigating through the files and folders on your filesystem.
# '''Select the letter of your USB drive''' from the dropdown in Win32DiskImager.
# '''Click the Write button''' on Win32DiskImager.
# '''Confirm the write''' if prompted to overwrite or corrupt of physical device.
# '''Wait''' for it to finish... It may take a while.
# '''Click OK''' when you see the Write Successful popup.
# '''Eject your USB drive''' before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Installing/Creating Bootable USB

2016-09-30T16:40:59Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

'''If you would like a video to follow along with''', I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, '''download the correct version of GalliumOS for your device''' from https://galliumos.org/download If you don't know which version you need, check out the [Hardware_Compatibility] page.
Also, '''download the correct version of Etcher for your operating system''' from http://www.etcher.io/
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

First, you need to download the GalliumOS iso for your Chromebook.

Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.

cd to the place where you downloaded the iso. It's probably ~/Downloads.

<code>cd ~/Downloads</code>

Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.

<code>sudo umount -f /dev/sdb1</code>

Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.

<code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>

Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==


# First, download the correct iso for your device.
# Wait for the download to finish completely before proceeding.
# Also download, install, and open Win32DiskImager from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.
# Plug in your USB device and identify it's drive letter.
# Click the folder button next to the empty box on Win32DiskImager.
# Change the file type from Disk Images (.img) to *.*.
# Use the file dialog to navigate to and open the GalliumOS iso from your Downloads folder (or wherever else it may have saved).
# Select the letter of your USB drive from the dropdown in Win32DiskImager.
# Click the Write button on Win32DiskImager.
# If prompted to confirm overwrite or corruption of physical device, click Yes.
# Wait for it to finish... It may take a while.
# When you see the Write Successful popup, click OK.
# Eject your USB drive before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Installing/Creating Bootable USB

2016-09-30T16:40:18Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

'''If you would like a video to follow along with''', I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, '''download the correct version of GalliumOS for your device''' from [[https://galliumos.org/download|GalliumOS.org]]. If you don't know which version you need, check out the [Hardware_Compatibility] page.
Also, '''download the correct version of Etcher for your operating system''' from [[http://www.etcher.io/|Etcher.io]].
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

First, you need to download the GalliumOS iso for your Chromebook.

Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.

cd to the place where you downloaded the iso. It's probably ~/Downloads.

<code>cd ~/Downloads</code>

Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.

<code>sudo umount -f /dev/sdb1</code>

Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.

<code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>

Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==


# First, download the correct iso for your device.
# Wait for the download to finish completely before proceeding.
# Also download, install, and open Win32DiskImager from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.
# Plug in your USB device and identify it's drive letter.
# Click the folder button next to the empty box on Win32DiskImager.
# Change the file type from Disk Images (.img) to *.*.
# Use the file dialog to navigate to and open the GalliumOS iso from your Downloads folder (or wherever else it may have saved).
# Select the letter of your USB drive from the dropdown in Win32DiskImager.
# Click the Write button on Win32DiskImager.
# If prompted to confirm overwrite or corruption of physical device, click Yes.
# Wait for it to finish... It may take a while.
# When you see the Write Successful popup, click OK.
# Eject your USB drive before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Installing/Creating Bootable USB

2016-09-30T16:37:56Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

'''If you would like a video to follow along with''', I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, '''download the correct version of GalliumOS for your device''' from [[https://galliumos.org/downloads]]. If you don't know which version you need, check out the [Hardware_Compatibility] page.
Also, '''download the correct version of Etcher for your operating system''' from [[http://www.etcher.io/]].
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

First, you need to download the GalliumOS iso for your Chromebook.

Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.

cd to the place where you downloaded the iso. It's probably ~/Downloads.

<code>cd ~/Downloads</code>

Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.

<code>sudo umount -f /dev/sdb1</code>

Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.

<code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>

Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==


# First, download the correct iso for your device.
# Wait for the download to finish completely before proceeding.
# Also download, install, and open Win32DiskImager from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.
# Plug in your USB device and identify it's drive letter.
# Click the folder button next to the empty box on Win32DiskImager.
# Change the file type from Disk Images (.img) to *.*.
# Use the file dialog to navigate to and open the GalliumOS iso from your Downloads folder (or wherever else it may have saved).
# Select the letter of your USB drive from the dropdown in Win32DiskImager.
# Click the Write button on Win32DiskImager.
# If prompted to confirm overwrite or corruption of physical device, click Yes.
# Wait for it to finish... It may take a while.
# When you see the Write Successful popup, click OK.
# Eject your USB drive before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Installing/Creating Bootable USB

2016-09-30T16:37:22Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

If you would like a video to follow along with, I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, '''download the correct version of GalliumOS for your device''' from [[https://galliumos.org/downloads]]. If you don't know which version you need, check out the [Hardware_Compatibility] page.
Also, '''download the correct version of Etcher for your operating system''' from [[http://www.etcher.io/]].
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

First, you need to download the GalliumOS iso for your Chromebook.

Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.

cd to the place where you downloaded the iso. It's probably ~/Downloads.

<code>cd ~/Downloads</code>

Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.

<code>sudo umount -f /dev/sdb1</code>

Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.

<code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>

Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==


# First, download the correct iso for your device.
# Wait for the download to finish completely before proceeding.
# Also download, install, and open Win32DiskImager from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.
# Plug in your USB device and identify it's drive letter.
# Click the folder button next to the empty box on Win32DiskImager.
# Change the file type from Disk Images (.img) to *.*.
# Use the file dialog to navigate to and open the GalliumOS iso from your Downloads folder (or wherever else it may have saved).
# Select the letter of your USB drive from the dropdown in Win32DiskImager.
# Click the Write button on Win32DiskImager.
# If prompted to confirm overwrite or corruption of physical device, click Yes.
# Wait for it to finish... It may take a while.
# When you see the Write Successful popup, click OK.
# Eject your USB drive before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Installing/Creating Bootable USB

2016-09-30T16:35:11Z

ColtonDRG:

Creating bootable GalliumOS media is very similar to other Linux distributions. Unfortunately, that doesn't mean it's easy. The goal of this guide is to make it as straightforward as possible.

== On Windows, macOS (OS X), and Linux (using Etcher) ==

Etcher is an excellent tool for writing the ISOs to bootable USBs because it is fast, easy to use, and it automatically verifies the integrity of the image after writing it.

If you would like a video to follow along with, I've made this one, which I believe to explain the process very well: https://www.youtube.com/watch?v=Pv0WansPmLs

Before you get started, download the correct version of GalliumOS for your operating system from [[https://galliumos.org/downloads]]. If you don't know which version you need, check out the [Hardware_Compatibility] page.
Also, download the correct version of Etcher for your operating system from [[http://www.etcher.io/]].
Once you've downloaded both and installed Etcher, proceed with the guide.

# '''Launch Etcher.''' It may ask you for your password. Etcher requires root (or Administrator) permissions to get write access to the raw devices.
# '''Plug your flash drive in''' to your computer
# '''Click on "Select Image"''' in Etcher
# '''Select the GalliumOS iso''' by navigating through the files and folders in your filesystem
# '''Select your flash drive''' in Etcher. If it is the only one connected to your computer, it should select it automatically. Make certain you choose the right one. Everything on the selected drive will be permanently erased.
# '''Start the flash''' by clicking "Flash!" in Etcher. It may take quite a while, depending on the speed of your flash drive and your computer.
# '''Verify the write'''. After flashing, Etcher will automatically verify that the write was successful. '''Important!''' If you're on macOS, a dialog stating that the disk you inserted was not readable may appear. Make sure you click on "Ignore", as any other button may damage the GalliumOS Installer.
# '''Close Etcher''' after you see the "Flash Complete!" confirmation screen. '''It is now safe to remove your drive and install GalliumOS!'''

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Linux (Traditional) ==

First, you need to download the GalliumOS iso for your Chromebook.

Once the iso is finished downloading (you MUST wait for it to finish), open up your favourite Terminal emulator.

cd to the place where you downloaded the iso. It's probably ~/Downloads.

<code>cd ~/Downloads</code>

Plug in your USB device, identify it, and unmount it. This is a little tricky. You can use <code>lsblk</code> to get a list of storage devices attached to your system. Try to find out which one is your USB flash drive. It is very important to not get this wrong, as it could cause catastrophic data loss. Once you've figured it out, make sure the USB flash drive is unmounted.

<code>sudo umount -f /dev/sdb1</code>

Be sure to replace sdb1 with the actual partition name as listed in lsblk. Next, use dd to copy the ISO to the USB flash drive.

<code>sudo dd bs=1M if=galliumos.iso of=/dev/sdb ; sync</code>

Be sure to replace galliumos.iso with the filename of the iso you want to write. Usually typing "galliumos" and hitting tab will autocomplete it for you. Also be sure to replace <code>sdb</code> with the actual device as listed in <code>lsblk</code>. Make sure to write to the DEVICE and NOT the partition. This process can take a long time depending on the speed of your flash drive, USB connection, and hard drive. Be patient. Once the prompt comes back, the ISO should be written.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On macOS (OS X) (Traditional) ==

# '''Download the GalliumOS ISO''' for your ChromeOS device: https://galliumos.org/download
# '''Insert USB media''' into Mac OS X machine
# '''Carefully determine device path''' for newly inserted USB media from a Terminal.app window<div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil list</div>The device path will be something like <code>/dev/diskN</code>. Replace <code>N</code> in all steps below with the correct disk number.<div style="background-color:#fff8f8;border:1px solid #cc0000;padding:0.2em 0.5em;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#cc0000;margin:0 0.3em;padding:0.1em 0.3em;background-color:#ffdddd">⚡</span>It is '''''extremely''''' important to determine the correct device path for your USB media in this step. Using the wrong device path in the following steps could damage your OS X install and cause irreparable data loss!</div>
# '''Unmount USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil unmountDisk /dev/disk<span style="color:yellow">N</span></div>
# '''Copy the ISO''' to USB media (<code>dd</code> works too, but <code>cp</code> is simpler and more familiar)<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>sudo cp <span style="color:yellow">./galliumos.iso</span> /dev/<span style="color:#00ff00">r</span>disk<span style="color:yellow">N</span></div><div style="background-color:#fffff0;border:1px solid #c0c044;padding:0.2em 0.5em;margin:0.5em 0 0 0;width:80%"><span style="font-size:1.2em;font-weight:bold;color:#888822;margin:0 0.3em;padding:0.1em 0.25em;background-color:#ffffcc">★</span>Be sure to use the correct path and filename for the <code>galliumos.iso</code> file downloaded in step 1, and to use the <code>rdisk</code> device name as the copy destination.</div>
# '''Eject USB media''' from OS X<br><div style="background-color:#404040;color:white;padding:0.1em 0.5em;width:40em;font-family:monospace;font-size:1.2em"><span style="color:#00ff00">bash$ </span>diskutil eject /dev/disk<span style="color:yellow">N</span></div>
# '''Remove USB media''' from Mac OS X machine, it's now ready for your ChromeOS device

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On Windows (Traditional) ==


# First, download the correct iso for your device.
# Wait for the download to finish completely before proceeding.
# Also download, install, and open Win32DiskImager from [[http://sourceforge.net/projects/win32diskimager/files/latest/download SourceForge]]. If you already have it, just open it up.
# Plug in your USB device and identify it's drive letter.
# Click the folder button next to the empty box on Win32DiskImager.
# Change the file type from Disk Images (.img) to *.*.
# Use the file dialog to navigate to and open the GalliumOS iso from your Downloads folder (or wherever else it may have saved).
# Select the letter of your USB drive from the dropdown in Win32DiskImager.
# Click the Write button on Win32DiskImager.
# If prompted to confirm overwrite or corruption of physical device, click Yes.
# Wait for it to finish... It may take a while.
# When you see the Write Successful popup, click OK.
# Eject your USB drive before unplugging it.

'''If you are unable to boot your ChromeOS device using your new USB media, see [[Installing/Creating Bootable USB#Troubleshooting|Troubleshooting]], below.'''

== On ChromeOS ==

ChromeOS is very similar to Linux, but not identical. I will write a proper guide as soon as I have access to a Chromebook (that I haven't installed GalliumOS on :P)

== Troubleshooting ==

Creating installation media is (by far!) the most error-prone step to installing GalliumOS.

There are many things that can go wrong. Some errors are immediately obvious (won't boot), others can be very surprising (installer crash, IO errors). If you're having trouble, consider this list of possibilities:

=== Common Problems ===
* '''Mistaken write''': Human error happens! Please reread the instructions very carefully -- make sure you're writing to the correct device, and to the correct device file (which is different from the device file in other commands).
* '''Corrupt write''': We frequently see corrupt writes to USB/SD media even when all steps are followed correctly. Sometimes the second or third try "just works", but confirm the MD5 checksum first.
* '''Bad USB/SD media''': These devices aren't known for their reliability. Try a different USB drive or SD card if you are able.
* '''Wrong USB port''': Some models and firmwares only boot from USB2.0 (black) ports, not USB3.0 (blue) ports. This is only a boot problem -- writing should work to either.

=== Less-Common Problems ===
* '''Corrupt image download''': Compare the MD5 checksum for your download to the the published checksum. Replace <code>galliumos.iso</code> with the name of the file you downloaded, of course:
** Linux: <code>md5sum ./galliumos.iso</code>
** Mac OS X: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''Bad image''': Sometimes we make bad nightly images! It's rare, but it has happened. Please let us know if you run into this problem. The ISOs linked from the [https://galliumos.org/download GalliumOS download page] are well-tested, so try one of those instead.

=== Testing your USB drive and write ===

The GalliumOS ISO should boot any x86 computer that allows "Legacy Boot" (this might require config in the BIOS menu). This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software.

If all else fails, you might have better luck installing in a dual-boot config, which downloads directly from the GalliumOS servers, and does not require any installation media.

Hardware Compatibility

2016-08-26T22:00:56Z

ColtonDRG:

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 new and ''partially'' supported
* '''Intel Skylake''' models are new and ''mostly'' supported
* '''Intel Pineview''' models are older and <span style="color:#cc0000">not supported</span>: they do not ship with compatible firmware, and custom firmware is not presently available
* '''ARM''' models are <span style="color:#cc0000">not supported</span>: 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.

3rd 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 more details.

<span style="display:none">

<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="hwid"/>
<ref name="chrx"/>
<ref name="TextMode"/>
<ref name="HiDPI2560"/>
<ref name="SAMUS"/>
<ref name="PANTHER"/>
</span>

== GalliumOS Support by Model ==



{| class="wikitable"
|-
! 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?
! 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
|-
| 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
| 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:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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:<br>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" | Major issues:<br>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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| Acer Chromebook 11/Olay (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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, 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" | ?
|
| style="text-align:center;background-color:#ffe8e8" | not yet (Jun 2016)
|
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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:<br>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 (xx)
| BANON
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook R11 (C738T, CB5-132T)
| CYAN
| 2015
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, after firmware update<ref name="chrx"/>
|-
| Acer Chromebook R13
| 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 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:#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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| ASUS Chromebook 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 Chromebook C202SA
| TERRA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| ASUS Chromebook C300SA
| TERRA13
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, after firmware update<ref name="chrx"/>
|-
| ASUS Chromebook C301SA
| (tbd)
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, after firmware update<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" | Major issue:<br>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"/>
| 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:#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 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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:<br>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"/>
| 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"/><br>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:<br>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]]<br>[https://www.reddit.com/r/GalliumOS/comments/48zgsz/guideadd_pixel_2015_default_resolution_options/ HiDPI config]<br>[https://github.com/GalliumOS/galliumos-distro/issues/44 HiDPI Notes]
|-
| 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"/>
|-
| 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 (Jun 2016)
| 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:#ccffcc" | Yes, after firmware update<ref name="chrx"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| HP Chromebook 11 G5
| SETZER
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, after firmware update<ref name="chrx"/>
|-
| HP Chromebook 13
| CHELL
| 2016
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes (WIP)
| style="text-align:center;background-color:#ffffcc" | Yes (WIP)
| style="text-align:center;background-color:#ffffcc" | Yes (WIP)<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | Yes (WIP)<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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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:<br>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"/>
| style="text-align:center;" | [[Installing/Panther|Installation]]
|-
| 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 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| Lenovo N22 Chromebook
| REKS
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| Lenovo ThinkPad 11e Chromebook G3
| ULTIMA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, after firmware update<ref name="chrx"/>
|-
| Lenovo ThinkPad 13 Chromebook
| SENTRY
| 2016
| Intel Skylake<ref name="Skylake"/>
| style="text-align:center;background-color:#ffffcc" | ?
|
| style="text-align:center;background-color:#ffe8e8" | not yet (Jun 2016)
|
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| Lenovo ThinkPad Yoga G3
| ULTIMA
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, 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
|-
| NComputing Chromebook CX100
| 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" | -
|-
| 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"/>
| 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 Chromebook 3 (XE500C13)
| CELES
| 2016
| Intel Braswell<ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP
| style="text-align:center;background-color:#ffe8e8" | No
| style="text-align:center;background-color:#ffffcc" | WIP <ref name="Braswell"/>
| style="text-align:center;background-color:#ffffcc" | WIP, after firmware update<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
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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"/>
| style="text-align:center;" | [[Installing/Baytrail|Installation]]
|-
| 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" | Major issues:<br>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"/>
|-
! 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 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 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 '''not''' supported yet. We are currently working on a Braswell build. See [[Support/Braswell]].
</ref>
<ref name="Skylake">
'''Skylake''' models are new and '''preliminarily''' supported. We are currently working on a full Skylake build. See [[Support/Skylake]].
</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. There are some good settings and workarounds in the [https://github.com/GalliumOS/galliumos-distro/issues/44 HiDPI Issue Tracker thread].
</ref>
<ref name="SAMUS">'''SAMUS'''
(Google Pixel, 2015) has known issues with [https://github.com/GalliumOS/galliumos-distro/issues/100 internal audio] and [https://github.com/GalliumOS/galliumos-distro/issues/44 HiDPI]. Support is improving, see the issue tracker threads for details. [https://www.reddit.com/r/GalliumOS/comments/48zgsz/guideadd_pixel_2015_default_resolution_options/ More HiDPI notes].
</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="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 />

Packaging/Consolidation

2016-08-22T18:08:44Z

ColtonDRG:

__NOTOC__
<div style="background-color:#fee;border:1px solid red;padding:0.2em;">'''WIP''': notes on packaging/image reorg.</div>

== Goals ==

* Simplify support by building a single GalliumOS distribution image: <code>galliumos-xenon-2.1.iso</code>
** Currently shipping six hardware-specific images
*** baytrail, broadwell, broadwell-cbox, haswell, haswell-cbox, sandy
** Will add two to four more soon:
*** braswell, skylake, possibly samus and/or hidpi
** Only should be required for the iso. We can do any installed system stuff during installation and never think about it again at boot.

== Prerequisites ==

* Consolidate existing hardware-specific GalliumOS packages into a single package
** (or possibly merge them all into <code>galliumos-core</code> and <code>galliumos-desktop</code>)
** Why? In the installed system, it would still be massively helpful to have those.
** Maybe keep each of the individual packages, plus a galliumos-hwsetup package that is only installed in the iso.

== Issues ==

* All customization in packages must be done at (first?) boot, not package install time
** Booting from the Live Image must be customized for the model
** Images are built on a single machince (VM, non-GalliumOS)
* Some customizations must be in place ''early'' in the boot process
** Where not possible, they can be configured for the next boot (not useful for Live Image boot)

== Customizations ==

=== Categories ===
# kernel and kernel modules, e.g.:
#* <code>/etc/modprobe.d/iwlwifi-opts.conf</code>
# systemd config, e.g.:
#* <code>/lib/systemd/system-sleep/wifi.sh</code>
# services config, e.g.:
#* <code>/etc/pulse/default.pa</code>
# user config, e.g.:
#* <code>/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml</code>

=== Limitations ===

* All images must boot a single kernel
** Maybe not - We can have a GRUB menu to select an appropriate kernel for device class. Also thought of a way of detecting the device and selecting the correct kernel, maybe kexec?

== Methods ==

=== Detection ===
* Model detection via <code>dmidecode -s system-product-name</code>
** <code>Peppy</code>
* CPU detection via <code>dmidecode -s processor-version</code> as fallback
** <code>Intel(R) Celeron(R) 2955U @ 1.40GHz</code>
* Display resolution detection for selecting HiDPI pkg?
** Some models (YUNA) ship with identical CPU (3205U) for both 1366x and 1920x displays
** Can't detect by the usual methods (xdpyinfo, xrandr) in early boot -- no X server running

=== Process ===
* A <code>systemd</code> one-shot could set config files before reaching an early target
** Existing <code>galliumos-laptop</code> service does some model detection, but it is late in the boot
** Should work well for Customization categories #3 and #4; ''might'' work for #2, probably can't work for #1.
*** ''should'' work for #2, with <code>systemctl daemon-reload</code>
** Configurator could detect user-changed files by timestamp and checksum
*** What to do if there is a newer GalliumOS update?
* A kernel module that loaded early could handle everything necessary (except kernel selection)
** Yikes

Packaging/Consolidation

2016-08-22T06:28:11Z

ColtonDRG:

__NOTOC__
<div style="background-color:#fee;border:1px solid red;padding:0.2em;">'''WIP''': notes on packaging/image reorg.</div>

== Goals ==

* Simplify support by building a single GalliumOS distribution image: <code>galliumos-xenon-2.1.iso</code>
** Currently shipping six hardware-specific images
*** baytrail, broadwell, broadwell-cbox, haswell, haswell-cbox, sandy
** Will add two to four more soon:
*** braswell, skylake, possibly samus and/or hidpi
** Only should be required for the iso. We can do any installed system stuff during installation and never think about it again at boot.

== Prerequisites ==

* Consolidate existing hardware-specific GalliumOS packages into a single package
** (or possibly merge them all into <code>galliumos-core</code> and <code>galliumos-desktop</code>)

== Issues ==

* All customization in packages must be done at (first?) boot, not package install time
** Booting from the Live Image must be customized for the model
** Images are built on a single machince (VM, non-GalliumOS)
* Some customizations must be in place ''early'' in the boot process
** Where not possible, they can be configured for the next boot (not useful for Live Image boot)

== Customizations ==

=== Categories ===
# kernel and kernel modules, e.g.:
#* <code>/etc/modprobe.d/iwlwifi-opts.conf</code>
# systemd config, e.g.:
#* <code>/lib/systemd/system-sleep/wifi.sh</code>
# services config, e.g.:
#* <code>/etc/pulse/default.pa</code>
# user config, e.g.:
#* <code>/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml</code>

=== Limitations ===

* All images must boot a single kernel
** Maybe not - We can have a GRUB menu to select an appropriate kernel for device class. Also thought of a way of detecting the device and selecting the correct kernel, maybe kexec?

== Methods ==

=== Detection ===
* Model detection via <code>dmidecode -s system-product-name</code>
** <code>Peppy</code>
* CPU detection via <code>dmidecode -s processor-version</code> as fallback
** <code>Intel(R) Celeron(R) 2955U @ 1.40GHz</code>
* Display resolution detection for selecting HiDPI pkg?
** Some models (YUNA) ship with identical CPU (3205U) for both 1366x and 1920x displays
** Can't detect by the usual methods (xdpyinfo, xrandr) in early boot -- no X server running

=== Process ===
* A <code>systemd</code> one-shot could set config files before reaching an early target
** Existing <code>galliumos-laptop</code> service does some model detection, but it is late in the boot
** Should work well for Customization categories #3 and #4; ''might'' work for #2, probably can't work for #1.
*** ''should'' work for #2, with <code>systemctl daemon-reload</code>
** Configurator could detect user-changed files by timestamp and checksum
*** What to do if there is a newer GalliumOS update?
* A kernel module that loaded early could handle everything necessary (except kernel selection)
** Yikes

Packaging/Consolidation

2016-08-22T06:26:21Z

ColtonDRG:

__NOTOC__
<div style="background-color:#fee;border:1px solid red;padding:0.2em;">'''WIP''': notes on packaging/image reorg.</div>

== Goals ==

* Simplify support by building a single GalliumOS distribution image: <code>galliumos-xenon-2.1.iso</code>
** Currently shipping six hardware-specific images
*** baytrail, broadwell, broadwell-cbox, haswell, haswell-cbox, sandy
** Will add two to four more soon:
*** braswell, skylake, possibly samus and/or hidpi

== Prerequisites ==

* Consolidate existing hardware-specific GalliumOS packages into a single package
** (or possibly merge them all into <code>galliumos-core</code> and <code>galliumos-desktop</code>)

== Issues ==

* All customization in packages must be done at (first?) boot, not package install time
** Booting from the Live Image must be customized for the model
** Images are built on a single machince (VM, non-GalliumOS)
* Some customizations must be in place ''early'' in the boot process
** Where not possible, they can be configured for the next boot (not useful for Live Image boot)

== Customizations ==

=== Categories ===
# kernel and kernel modules, e.g.:
#* <code>/etc/modprobe.d/iwlwifi-opts.conf</code>
# systemd config, e.g.:
#* <code>/lib/systemd/system-sleep/wifi.sh</code>
# services config, e.g.:
#* <code>/etc/pulse/default.pa</code>
# user config, e.g.:
#* <code>/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml</code>

=== Limitations ===

* All images must boot a single kernel
** Maybe not - We can have a GRUB menu to select an appropriate kernel for device class. Also thought of a way of detecting the device and selecting the correct kernel, maybe kexec?

== Methods ==

=== Detection ===
* Model detection via <code>dmidecode -s system-product-name</code>
** <code>Peppy</code>
* CPU detection via <code>dmidecode -s processor-version</code> as fallback
** <code>Intel(R) Celeron(R) 2955U @ 1.40GHz</code>
* Display resolution detection for selecting HiDPI pkg?
** Some models (YUNA) ship with identical CPU (3205U) for both 1366x and 1920x displays
** Can't detect by the usual methods (xdpyinfo, xrandr) in early boot -- no X server running

=== Process ===
* A <code>systemd</code> one-shot could set config files before reaching an early target
** Existing <code>galliumos-laptop</code> service does some model detection, but it is late in the boot
** Should work well for Customization categories #3 and #4; ''might'' work for #2, probably can't work for #1.
*** ''should'' work for #2, with <code>systemctl daemon-reload</code>
** Configurator could detect user-changed files by timestamp and checksum
*** What to do if there is a newer GalliumOS update?
* A kernel module that loaded early could handle everything necessary (except kernel selection)
** Yikes

Packaging/Consolidation

2016-08-22T06:23:38Z

ColtonDRG:

__NOTOC__
<div style="background-color:#fee;border:1px solid red;padding:0.2em;">'''WIP''': notes on packaging/image reorg.</div>

== Goals ==

* Simplify support by building a single GalliumOS distribution image: <code>galliumos-xenon-2.1.iso</code>
** Currently shipping six hardware-specific images
*** baytrail, broadwell, broadwell-cbox, haswell, haswell-cbox, sandy
** Will add two to four more soon:
*** braswell, skylake, possibly samus and/or hidpi

== Prerequisites ==

* Consolidate existing hardware-specific GalliumOS packages into a single package
** (or possibly merge them all into <code>galliumos-core</code> and <code>galliumos-desktop</code>)

== Issues ==

* All customization in packages must be done at (first?) boot, not package install time
** Booting from the Live Image must be customized for the model
** Images are built on a single machince (VM, non-GalliumOS)
* Some customizations must be in place ''early'' in the boot process
** Where not possible, they can be configured for the next boot (not useful for Live Image boot)

== Customizations ==

=== Categories ===
# kernel and kernel modules, e.g.:
#* <code>/etc/modprobe.d/iwlwifi-opts.conf</code>
# systemd config, e.g.:
#* <code>/lib/systemd/system-sleep/wifi.sh</code>
# services config, e.g.:
#* <code>/etc/pulse/default.pa</code>
# user config, e.g.:
#* <code>/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml</code>

=== Limitations ===

* All images must boot a single kernel
** Maybe not - We can have a GRUB menu to select an appropriate kernel for device class. Also thought of a way of detecting the device and selecting the correct kernel, maybe kexec?

== Methods ==

=== Detection ===
* Model detection via <code>dmidecode -s system-product-name</code>
** <code>Peppy</code>
* CPU detection via <code>dmidecode -s processor-version</code> as fallback
** <code>Intel(R) Celeron(R) 2955U @ 1.40GHz</code>
* Display resolution detection for selecting HiDPI pkg?
** Some models (YUNA) ship with identical CPU (3205U) for both 1366x and 1920x displays
** Can't detect by the usual methods (xdpyinfo, xrandr) in early boot -- no X server running

=== Process ===
* A <code>systemd</code> one-shot could set config files before reaching an early target
** Existing <code>galliumos-laptop</code> service does some model detection, but it is late in the boot
** Should work well for Customization categories #3 and #4; ''might'' work for #2, probably can't work for #1.
** Configurator could detect user-changed files by timestamp and checksum
*** What to do if there is a newer GalliumOS update?
* A kernel module that loaded early could handle everything necessary (except kernel selection)
** Yikes

Mirrors

2016-06-29T21:32:20Z

ColtonDRG:

Here we'll have a list of GalliumOS static file and apt repository mirrors.

=== GaOS release download mirrors ===
https://galliumos.org/releases/ (Official release downloads) (New York, United States)

https://ca1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (California, United States)

https://va1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (Virgina, United States)

https://rb1.fr.mirror.galliumos.org/releases/ (Official release download mirror) (Roubaix, France)

=== <br> GaOS APT mirrors ===
https://apt.galliumos.org/ (Official APT repo) (New York, United States)

https://ca1.us.mirror.galliumos.org/apt/ (Official APT repo mirror) (California, United States)

https://rb1.fr.mirror.galliumos.org/apt/ (Official APT repo mirror) (Roubaix, France)

=== <br> GaOS website mirrors ===
https://galliumos.org/ (Official site) (New York, United States)

https://ca1.us.mirror.galliumos.org/ (Official site mirror) (California, United States)

Mirrors

2016-06-29T21:30:20Z

ColtonDRG: /* GaOS APT mirrors */

Here we'll have a list of GalliumOS static file and apt repository mirrors.

=== GaOS release download mirrors ===
https://galliumos.org/releases/ (Official release downloads) (New York, United States)

https://ca1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (California, United States)

https://va1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (Virgina, United States)

https://rb1.fr.mirror.galliumos.org/releases/ (Official release download mirror) (Roubaix, France)

=== <br> GaOS APT mirrors ===
https://apt.galliumos.org/ (Official APT repo) (New York, United States)

<nowiki>https://ca1.us.mirror.galliumos.org/apt/ (Official APT repo mirror) (California, United States)</nowiki>

https://rb1.fr.mirror.galliumos.org/apt/ (Official APT repo mirror) (Roubaix, France)

=== <br> GaOS website mirrors ===
https://galliumos.org/ (Official site) (New York, United States)

https://ca1.us.mirror.galliumos.org/ (Official site mirror) (California, United States)

Mirrors

2016-06-29T20:56:04Z

ColtonDRG: /* GaOS release download mirrors */

Here we'll have a list of GalliumOS static file and apt repository mirrors.

=== GaOS release download mirrors ===
https://galliumos.org/releases/ (Official release downloads) (New York, United States)

https://ca1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (California, United States)

https://va1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (Virgina, United States)

https://rb1.fr.mirror.galliumos.org/releases/ (Official release download mirror) (Roubaix, France)

=== <br> GaOS APT mirrors ===
https://apt.galliumos.org/ (Official APT repo) (New York, United States)

https://rb1.fr.mirror.galliumos.org/apt/ (Official APT repo mirror) (Roubaix, France)

=== <br> GaOS website mirrors ===
https://galliumos.org/ (Official site) (New York, United States)

https://ca1.us.mirror.galliumos.org/ (Official site mirror) (California, United States)

Mirrors

2016-06-29T20:55:13Z

ColtonDRG: /* GaOS APT mirrors */

Here we'll have a list of GalliumOS static file and apt repository mirrors.

=== GaOS release download mirrors ===
<nowiki>https://galliumos.org/releases/ (Official release downloads) (New York, United States)</nowiki>

<nowiki>https://ca1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (California, United States)</nowiki>

<nowiki>https://va1.us.mirror.galliumos.org/releases/ (Official release downloads mirror) (Virgina, United States)</nowiki>

<nowiki>https://rb1.fr.mirror.galliumos.org/releases/ (Official release download mirror) (Roubaix, France)</nowiki>

=== <br> GaOS APT mirrors ===
https://apt.galliumos.org/ (Official APT repo) (New York, United States)

https://rb1.fr.mirror.galliumos.org/apt/ (Official APT repo mirror) (Roubaix, France)

=== <br> GaOS website mirrors ===
https://galliumos.org/ (Official site) (New York, United States)

<nowiki>https://ca1.us.mirror.galliumos.org/ (Official site mirror) (California, United States)</nowiki>

Mirroring

2016-06-29T20:47:20Z

ColtonDRG: Created page with "GalliumOS has several mirrors so that people can access files and packages with great speed from all over the world. If you're interested in hosting a mirror for us, well, fir..."

GalliumOS has several mirrors so that people can access files and packages with great speed from all over the world. If you're interested in hosting a mirror for us, well, first, thanks! We appreciate the help.

Mirroring is done through rsync. There are two different repositories that you can mirror: apt and releases. The releases repository includes our release isos. The apt repository includes our Debian package repository (or apt repo) where various GalliumOS packages are downloaded from.

If you would like to mirror the releases repository, it would look something like this...

<code>
rsync -rtlvH --delete-after --delay-updates --safe-links rsync://galliumos.org/releases galliumos/releases/
</code>

If you would like to mirror the apt repository, it would look something like this...

<code>
rsync -rtlvH --delete-after --delay-updates --safe-links rsync://galliumos.org/apt galliumos/apt/
</code>

Once you've created and configure your mirror, you're free to add it to the [[Unofficial Mirrors]] list. If you run an unofficial mirror for a while, and we deem you trustworthy, we may approach you to upgrade your mirror to an Official Mirror.

Some other official mirrors also run their own rsync repositories.

If you want to mirror both repositories from the Roubaix mirror, it would look something like this...

<code>
rsync -rtlvH --delete-after --delay-updates --safe-links rsync://eu.mirrors.coltondrg.com/galliumos galliumos/
</code>

If you want to mirror the releases repository from the Roubaix mirror, it would look something like this...

<code>
rsync -rtlvH --delete-after --delay-updates --safe-links rsync://eu.mirrors.coltondrg.com/galliumos/releases galliumos/releases/
</code>

If you want to mirror the apt repository from the Roubaix mirror, it would look something like this...

<code>
rsync -rtlvH --delete-after --delay-updates --safe-links rsync://eu.mirrors.coltondrg.com/galliumos/apt galliumos/apt/
</code>

Additional Software

2016-04-26T12:27:53Z

ColtonDRG:

GalliumOS comes with a good selection of desktop and utility software, but there is a huge variety of additional options and alternatives.

GalliumOS can install any software packages built for Ubuntu, directly from the Canonical package servers.

There are also some frequently-requested applications that are not available from Canonical, or are more complicated to install. A few are listed here. Please add more!

== Desktop ==

=== Google Chrome ===

<pre style="margin:0 0 0 1.5em">
curl -O https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo dpkg -i google-chrome-stable_current_amd64.deb
sudo apt-get -f install
</pre>

The last step is necessary to finish installing some additional package dependencies: <code>libappindicator1 libdbusmenu-gtk4 libindicator7</code>.


=== TeamViewer ===

<pre style="margin:0 0 0 1.5em">
sudo dpkg --add-architecture i386
curl -OL http://download.teamviewer.com/download/teamviewer_i386.deb
sudo dpkg -i teamviewer_i386.deb
</pre>

=== Google Drive integration ===

* Install the software
<pre style="margin:0 0 0 1.5em">
sudo add-apt-repository ppa:alessandro-strada/ppa
sudo apt-get update
sudo apt-get install google-drive-ocamlfuse
</pre>

* Next, add yourself to the Linux group ''fuse'' so you can mount Google Drive without root.
<pre style="margin:0 0 0 1.5em">
sudo usermod -a -G fuse <user_name>
exec su -l $USER
</pre>

* Run google-drive-ocamlfuse for first time setup.
<pre style="margin:0 0 0 1.5em">
google-drive-ocamlfuse
</pre>

You'll get a browser window asking you to sign in to your Google account and if you want to give gdfuse OAuth2 Endpoint permission to access your Drive files. Hit Accept / Allow for any following dialog. Close the browser window.

* Next, create a directory where your Google Drive files will be mounted, preferably in your home directory, and mount Google Drive to that directory.
<pre style="margin:0 0 0 1.5em">
mkdir ~/googledrive
google-drive-ocamlfuse ~/googledrive
</pre>

You can check if Google Drive is mounted by performing:
<pre style="margin:0 0 0 1.5em">
mount
</pre>

You can also check how much space you have left:
<pre style="margin:0 0 0 1.5em">
df
</pre>

If you want to unmount, simply run
<pre style="margin:0 0 0 1.5em">
fusermount -u ~/googledrive
</pre>

* To mount Google Drive at startup, set the following command to run at boot with Session and Startup.
<pre style="margin:0 0 0 1.5em">
google-drive-ocamlfuse -label default /home/<user>/googledrive
</pre>

A word of warning, large files such as movies or large videos don't work too well with google-drive-ocamlfuse using default settings. Files are cached to ~/.gdfuse/default/cache. A config file can be found in the directory above that, with parameters to allow for streaming larger files, cache size, etc.. The streaming larger files parameter is perfect for large videos and movies. For more information, check out gdfuse on GitHub.

Adapted from: http://xmodulo.com/mount-google-drive-linux.html

=== Skype ===

<pre style="margin:0 0 0 1.5em">
sudo dpkg --add-architecture i386
sudo add-apt-repository "deb http://archive.canonical.com/ $(lsb_release -sc) partner"
sudo apt-get update && sudo apt-get install skype
</pre>

Source: https://help.ubuntu.com/community/Skype

See also: https://www.skype.com/en/download-skype/skype-for-linux/

=== Wine ===

Wine has been a source of frustration. These instructions are verified on a fresh install of 1.0beta2.

<pre style="margin:0 0 0 1.5em">
sudo dpkg --add-architecture i386
sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get update
sudo apt-get install wine1.8
</pre>

=== Simple Screen Recorder ===
<pre style="margin:0 0 0 1.5em">
sudo add-apt-repository -y ppa:maarten-baert/simplescreenrecorder
sudo apt-get update
sudo apt-get install simplescreenrecorder
</pre>

=== Spotify ===

<pre style="margin:0 0 0 1.5em">
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys BBEBDCB318AD50EC6865090613B00F1FD2C19886
echo deb http://repository.spotify.com stable non-free | sudo tee /etc/apt/sources.list.d/spotify.list
sudo apt-get update
sudo apt-get install spotify-client
</pre>

Source: https://www.spotify.com/us/download/linux/

== Games ==

=== Steam ===
<pre style="margin:0 0 0 1.5em">
curl -O http://repo.steampowered.com/steam/archive/precise/steam_latest.deb
sudo dpkg -i steam_latest.deb
</pre>

Then launch Steam from the application launcher. Your user must be in the "sudo" group (if it is not, the dpkg command above will also fail), so that the installer can do all the things it needs to do.

=== Minecraft ===
<pre style="margin:0 0 0 1.5em">
sudo bash
apt-get install default-jre
curl -o /usr/local/bin/Minecraft.jar https://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.jar
curl -o /usr/share/pixmaps/minecraft.png https://chrx.org/minecraft.png
mkdir -p /usr/local/share/applications
cat > /usr/local/share/applications/minecraft.desktop <<EOF
[Desktop Entry]
Type=Application
Name=Minecraft
Comment=Minecraft
Exec=java -jar /usr/local/bin/Minecraft.jar
Icon=/usr/share/pixmaps/minecraft.png
Categories=Game;
EOF
</pre>

If the launcher won't start and is throwing SSL errors, try running this.
<pre style="margin:0 0 0 1.5em">
sudo apt-get update-ca-certificates -f
</pre>

== Utilities ==

=== grsync ===
Graphical lightweight version of rsync to back up data between drives
<pre style="margin:0 0 0 1.5em">
sudo add-apt install grsync
</pre>

=== aptik ===
Backup APT sources/repository data
<pre style="margin:0 0 0 1.5em">
sudo apt-add-repository -y ppa:teejee2008/ppa
sudo apt-get update
sudo apt-get install aptik
</pre>

=== OpenVPN ===
Install the following two packages to get OpenVPN connectivity with your favorite VPN service.
<pre style="margin:0 0 0 1.5em">
sudo apt-get install openvpn network-manager-openvpn
</pre>

== Hardware Optimization ==

=== Battery Tuning ===

==== Powertop ====
Monitor process and device power consumption. Includes a handy auto-tune option which can be run at startup that helps to minimize power consumption. Powertop also provides a calibration option. This may not currently play nice with GalliumOS and may lock up the device. Your mileage may vary.

<pre style="margin:0 0 0 1.5em">
sudo apt-get install powertop
sudo powertop
</pre>

Powertop needs to be run every time the system boots. See https://wiki.archlinux.org/index.php/Powertop for instructions on creating a one-shot <code>systemd</code> service.

==== TLP ====
Advanced power management tool that also provides a default configuration optimized for battery life for "install and forget it" benefits. TLP has reportedly provided some improvement to battery life. Your mileage may vary.

<pre style="margin:0 0 0 1.5em">sudo add-apt-repository ppa:linrunner/tlp
sudo apt-get install tlp
sudo tlp start</pre>

== Miscellaneous ==

These have been discussed, but are not presently candidates for inclusion in the default installation. They might be of special interest, might have important caveats, or might be the unchosen of other options. Presented here for convenience.

==== Hardware temperature monitor ====
* <code>xfce4-sensors-plugin</code> from Ubuntu repositories. '''WARNING:''' Do '''not''' select <code>tachos</code>. It will crash your desktop.

==== Clipboard Manager ====
* <code>clipit</code> from Ubuntu repositories. Developer homepage is missing. Be conscious of the security implications of all clipboard managers.

==== Video Player ====
* https://mpv.io/ Lightweight, but very minimal UI
* <code>smplayer</code> from Ubuntu repositories. Lightweight.

==== Screen Recorder ====
* <code>kazam</code> from Ubuntu repositories. Alternative to <code>simplescreenrecorder</code>, above. See https://apps.ubuntu.com/cat/applications/kazam/ for more info.

==== Disk Usage/Performance Indicators ====
* <code>xfce4-goodies</code> from Ubuntu repositories includes a free space checker applet
* <code>xfce4-diskperf-plugin</code> from Ubuntu repositories is a disk performance monitor applet, and shows usage as well

Support/UEFI

2016-04-02T08:29:57Z

ColtonDRG: Created page with "GalliumOS currently does not support UEFI, however it is possible to get it working with some time and effort. We opted to exclude UEFI support for GalliumOS because there is..."

GalliumOS currently does not support UEFI, however it is possible to get it working with some time and effort. We opted to exclude UEFI support for GalliumOS because there is currently no acceptable UEFI payload for the target hardware of GalliumOS. There are currently some teams working on bringing coreboot UEFI payloads to Chrome hardware, and following the release of a working UEFI custom firmware, GalliumOS does plan to add UEFI support.

UEFI support is interesting to GalliumOS because it could bring better Bay Trail support (see [[Support/BayTrail]]), support for Braswell (see [[Support/Braswell]]), potential support for some ARM models (see [[Support/ARM]]), and potentially even support for other non-Chrome hardware that could be considered as possible targets for GalliumOS. UEFI support is also interesting because it could potentially reduce boot time and possibly even bring it very close to parity with ChromeOS.

GalliumOS currently has no specific plans for how we plan to implement UEFI, however it seems likely that we will go about it in a very different way from Debian or Ubuntu. UEFI allows booting the Linux kernel directly, without the need for any bootloader, which could save us a lot of boot time by skipping GRUB entirely.

Support/Braswell

2016-04-02T08:20:30Z

ColtonDRG:

Intel processors with Braswell cores are very new (Dec 2015) and only available in a very small number ChromeOS devices. Braswell seems to be positioned as the replacement for Bay Trail, so this will likely change in 2016.

Factory firmware support for coreboot and SeaBIOS is uncertain but considered unlikely. Custom firmware is not presently available.

SeaBIOS support on Braswell may be possible, but there is no video BIOS, so SeaBIOS would not be able to initialize the GPU. GPU initialization on Braswell is handled by a UEFI GOP, and for that reason, Braswell support will likely be impossible until UEFI custom firmware becomes available and GalliumOS adds UEFI support. For more information about GalliumOS's plans for UEFI support, see [[Support/UEFI]].

At the moment, your best option for running Linux on a Braswell ChromeOS device is probably Crouton.

Infrastructure

2016-03-20T14:42:38Z

ColtonDRG: /* ci.galliumos.org */

An overview of our infrastructure needs and plans

== Services ==

=== Public-facing ===

* website
* blog (github)
* wiki
* download primary
* download mirrors (various)
* apt repo
* nameserver (dreamhost)
* mail host (reynhout)
* IRC bouncer
* user forums (reddit)
* issue tracker (github)
* version control (github)
* Jenkins

=== Restricted ===

* package build server
* image build server
* backups

== Servers ==

=== galliumos.org ===

;Services
:website, wiki, primary downloads, apt repo, IRC bouncer

;Resources
:RAM 360/2048GB
:disk 94/160GB
:cpu Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz, 6 cores (VPS, shared)

=== ci.galliumos.org ===

;Services
:package build server, image build server, download mirror, Jenkins

;Resources
:RAM 7815/15951GB
:disk 349G/1.8TB
:cpu Intel(R) Core(TM) i5-3570S CPU @ 3.10GHz, 4 cores

MATE

2016-02-25T17:12:23Z

ColtonDRG: Created page with "....... No.... No(t yet)....."

.......

No....

No(t yet).....

News/Dont Install Ubuntu Software Center

2016-02-25T04:40:43Z

ColtonDRG:

{{DISPLAYTITLE:(News) Don't Install Ubuntu Software Center}}
Hello. It has come to my attention that people are installing Ubuntu Software Center. Please don't. Seriously, just don't do it.

What's wrong with Ubuntu Software Center? Well, for starters, it's a terrible piece of software that interfaces with apt very poorly. I have had Ubuntu Software Center break more systems than I can count on both hands. That's a lot of systems. It crashes and freezes and breaks your system. Also, it has dependencies, and not innocent dependencies. Ubuntu Software Center depends on Software Updater, which is basically a nag tool that runs in the background (and not efficiently) and nags you to update your system. We do believe that update nags are useful in reminding users to keep their system up to date, but this specific one is incredibly inefficient, and it WILL waste your resources. Devices with the Software Updater installed will see high CPU usage when idle, the CPU heating up seemingly for no reason, lag spikes, CPU usage spikes, and many more ill effects. And finally, the icing on the cake is an annoying nag to update to Ubuntu 15.10. If you have the Software Updater installed, it can and WILL nag you to upgrade to Ubuntu 15.10, which WILL completely destroy your GalliumOS install and you'll have to start over should you accept the upgrade.

In conclusion, Ubuntu Software Center should not be installed on any GalliumOS system. Say no to Ubuntu Software Center. If you need an alternative for user friendly software installing and updating, consider Lubuntu Software Center. It's pretty nice.

Update: If you've installed the software center, run the following command to remove it and the other garbage.

<code>sudo apt-get purge software-center update-manager-core ubuntu-release-upgrader-core</code>

This has been a GalliumOS user curtosey PSA by [[User:ColtonDRG]]

Adobe Flash

2016-02-20T20:58:00Z

ColtonDRG:

Adobe Flash apps (and Twitch streams, etc) require Adobe Flash Player, which is not included by default in GalliumOS.

You have a few options for installing Adobe Flash, depending on your preferred web browser:

* '''Chromium and Firefox''': Install adobe-flashplugin from Canonical's evil partner repo.
** (confirm installation by entering <code>chrome://plugins</code> (Chromium) or <code>about:plugins</code> (Firefox) into the URL bar)
<pre style="margin:0 0 0 2em; padding:0.4em;">
sudo su -c "echo deb http://archive.canonical.com/ubuntu vivid partner > /etc/apt/sources.list.d/vivid-partner.list"
sudo apt-get update
sudo apt-get install adobe-flashplugin
</pre>

* '''Google Chrome''': The proprietary version of Google Chrome includes PepperFlash. See [[Additional Software]] for installation instructions.

Adobe Flash

2016-02-20T20:57:19Z

ColtonDRG:

Adobe Flash apps (and Twitch streams, etc) require Adobe Flash Player, which is not included by default in GalliumOS.

You have a few options for installing Adobe Flash, depending on your preferred web browser:

* '''Chromium and Firefox''': Install adobe-flashplugin from Canonical's evil partner repo.
** (confirm installation by entering <code>chrome://plugins (Chromium) or about:plugins (Firefox)</code> into the URL bar)
<pre style="margin:0 0 0 2em; padding:0.4em;">
sudo su -c "echo deb http://archive.canonical.com/ubuntu vivid partner > /etc/apt/sources.list.d/vivid-partner.list"
sudo apt-get update
sudo apt-get install adobe-flashplugin
</pre>

* '''Firefox''': Install the Adobe Flash plugin for NPAPI
** (confirm installation by entering <code>about:plugins</code> into the URL bar)
** (TODO)

* '''Chrome''': The proprietary version of Google Chrome includes PepperFlash. See [[Additional Software]] for installation instructions.

Adobe Flash

2016-02-20T20:48:47Z

ColtonDRG:

Adobe Flash apps (and Twitch streams, etc) require Adobe Flash Player, which is not included by default in GalliumOS.

You have a few options for installing Adobe Flash, depending on your preferred web browser:

* '''Chromium''': Install PepperFlash
** (confirm installation by entering <code>chrome://plugins</code> into the URL bar)
<pre style="margin:0 0 0 2em; padding:0.4em;">
sudo su -c "echo deb http://archive.canonical.com/ubuntu vivid partner > /etc/apt/sources.list.d/vivid-partner.list"
sudo apt-get update
sudo apt-get install adobe-flashplugin
</pre>

* '''Firefox''': Install the Adobe Flash plugin for NPAPI
** (confirm installation by entering <code>about:plugins</code> into the URL bar)
** (TODO)

* '''Chrome''': The proprietary version of Google Chrome includes PepperFlash. See [[Additional Software]] for installation instructions.

Adobe Flash

2016-02-20T20:47:25Z

ColtonDRG:

Adobe Flash apps (and Twitch streams, etc) require Adobe Flash Player, which is not included by default in GalliumOS.

You have a few options for installing Adobe Flash, depending on your preferred web browser:

* '''Chromium''': Install PepperFlash
** (confirm installation by entering <code>chrome://plugins</code> into the URL bar)
<pre style="margin:0 0 0 2em; padding:0.4em;">
sudo su -c "echo "deb http://archive.canonical.com/ubuntu vivid partner" > /etc/apt/sources.list.d/vivid-partner.list"
sudo apt-get update
sudo apt-get install adobe-flashplugin
</pre>

* '''Firefox''': Install the Adobe Flash plugin for NPAPI
** (confirm installation by entering <code>about:plugins</code> into the URL bar)
** (TODO)

* '''Chrome''': The proprietary version of Google Chrome includes PepperFlash. See [[Additional Software]] for installation instructions.

Adobe Flash

2016-02-20T20:43:52Z

ColtonDRG:

Adobe Flash apps (and Twitch streams, etc) require Adobe Flash Player, which is not included by default in GalliumOS.

You have a few options for installing Adobe Flash, depending on your preferred web browser:

* '''Chromium''': Install PepperFlash
** (confirm installation by entering <code>chrome://plugins</code> into the URL bar)
<pre style="margin:0 0 0 2em; padding:0.4em;">
sudo echo "deb http://archive.canonical.com/ubuntu vivid partner" > /etc/apt/sources.list.d/vivid-partner.list
sudo apt-get update
sudo apt-get install adobe-flashplugin
</pre>

* '''Firefox''': Install the Adobe Flash plugin for NPAPI
** (confirm installation by entering <code>about:plugins</code> into the URL bar)
** (TODO)

* '''Chrome''': The proprietary version of Google Chrome includes PepperFlash. See [[Additional Software]] for installation instructions.

Hardware/Lulu/SSD

2016-02-20T20:36:44Z

ColtonDRG: Created page with "Page created at request of User:jdferron"

Page created at request of [[User:jdferron]]

News/Dont Install Ubuntu Software Center

2016-02-17T11:07:05Z

ColtonDRG:

{{DISPLAYTITLE:(News) Don't Install Ubuntu Software Center}}
Hello. It has come to my attention that people are installing Ubuntu Software Center. Please don't. Seriously, just don't do it.

What's wrong with Ubuntu Software Center? Well, for starters, it's a terrible piece of software that interfaces with apt very poorly. I have had Ubuntu Software Center break more systems than I can count on both hands. That's a lot of systems. It crashes and freezes and breaks your system. Also, it has dependencies, and not innocent dependencies. Ubuntu Software Center depends on Software Updater, which is basically a nag tool that runs in the background (and not efficiently) and nags you to update your system. We do believe that update nags are useful in reminding users to keep their system up to date, but this specific one is incredibly inefficient, and it WILL waste your resources. Devices with the Software Updater installed will see high CPU usage when idle, the CPU heating up seemingly for no reason, lag spikes, CPU usage spikes, and many more ill effects. And finally, the icing on the cake is an annoying nag to update to Ubuntu 15.10. If you have the Software Updater installed, it can and WILL nag you to upgrade to Ubuntu 15.10, which WILL completely destroy your GalliumOS install and you'll have to start over should you accept the upgrade.

In conclusion, Ubuntu Software Center should not be installed on any GalliumOS system. Say no to Ubuntu Software Center. If you need an alternative for user friendly software installing and updating, consider Lubuntu Software Center. It's pretty nice.

This has been a GalliumOS user curtosey PSA by [[User:ColtonDRG]]

News

2016-02-17T11:05:11Z

ColtonDRG:

== 2016 ==

* '''February 17 '''[[News/Dont Install Ubuntu Software Center|Don't Install Ubuntu Software Center]]
* '''February 9''' [[News/GalliumOS 1.0beta2|GalliumOS 1.0beta2 released]]

== 2015 ==

* '''November 10''' GalliumOS 1.0beta1 released

News/Dont Install Ubuntu Software Center

2016-02-17T11:04:34Z

ColtonDRG: ColtonDRG moved page News/Don't Install Ubuntu Software Center to News/Dont Install Ubuntu Software Center

News/Don't Install Ubuntu Software Center

2016-02-17T11:04:34Z

ColtonDRG: ColtonDRG moved page News/Don't Install Ubuntu Software Center to News/Dont Install Ubuntu Software Center

#REDIRECT [[News/Dont Install Ubuntu Software Center]]

News/Dont Install Ubuntu Software Center

2016-02-17T11:04:16Z

ColtonDRG: