Reynhout: Created page with "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]..."

2019-06-30T05:09:43Z

Reynhout: Created page with "= GalliumOS 3.0 = 29 June 2019 GalliumOS 3.0 is available for download immediately. * '''Downloads, Mirrors, and Torrents:''' https://galliumos.org/download A special than..."

= GalliumOS 3.0 =

29 June 2019

GalliumOS 3.0 is available for download immediately.

* '''Downloads, Mirrors, and Torrents:''' https://galliumos.org/download

A special thanks to everyone who has contributed to the GalliumOS project! Your support helps us broaden and deepen GalliumOS support for Chromebook hardware.

Please visit our Support Forum on Reddit for comments and discussion: https://redd.it/5wroxp

== Installing GalliumOS ==

GalliumOS 3.0 installation images can be downloaded from https://galliumos.org/releases/3.0. You can preview GalliumOS in a "live boot" environment from the same image without installing.

GalliumOS can be installed in place of ChromeOS, or in a dual-boot configuration alongside ChromeOS. For dual-boot installs, see https://chrx.org/.

See the GalliumOS wiki for full installaton instructions: https://wiki.galliumos.org/Installing.



== Known Issues in GalliumOS 3.0 ==

We're working to bring full support to all Chromebooks and Chromeboxes. Some parts remain works in progress:

* No internal audio on Apollo Lake and Kaby Lake models
* Suspend clears <code>dev_boot_legacy</code> flag on Apollo Lake and Kaby Lake models

Full list of open issues: https://github.com/GalliumOS/galliumos-distro/issues

If you run into any issues with this or any GalliumOS release, please let us know!

== Thank You! ==

Thank you to everyone who has donated to the project, submitted patches, reported issues with previous releases, answered questions on our support forums, helped spread the word to friends and other news sites, or just installed and tested GalliumOS.

We thank you and hope GalliumOS will continue to make your Chromebooks and Chromeboxes more functional and fun.

== About GalliumOS ==

GalliumOS is a fast and lightweight Linux distribution specifically for Chromebooks and Chromeboxes. GalliumOS delivers a complete Linux environment with full hardware support and an attractive full-featured desktop.

GalliumOS features a touchpad driver customized for Chromebooks, kernel schedulers optimized for the CPUs and SSDs found in ChromeOS devices, and fixes dozens of device-specific bugs. All while requiring less memory and disk space compared to standard Linux desktop environments.

See https://wiki.galliumos.org/About_GalliumOS for more.

== GalliumOS Resources ==

* Downloads: https://galliumos.org/download
* Documentation: https://wiki.galliumos.org
** Hardware Compatibility: https://wiki.galliumos.org/Hardware_Compatibility
** Installing: https://wiki.galliumos.org/Installing
** FAQ: https://wiki.galliumos.org/FAQ
* Support forum: https://www.reddit.com/r/GalliumOS/
* Support chat: https://galliumos.org/irc
* Issue tracker: https://github.com/GalliumOS/galliumos-distro/issues

Hardware Compatibility

2019-03-29T15:06:49Z

Reynhout: /* GalliumOS Support by Model */

Support/Braswell

2018-07-23T18:25:26Z

Reynhout:

Intel processors with Braswell SoC's are the replacement for the previous-generation Bay Trail family.

Braswell support incomplete, but being tracked at GitHub: [https://github.com/GalliumOS/galliumos-distro/issues/270 Braswell Platform Validation]. You can subscribe to that ticket for the latest updates.

Braswell models do not include firmware support for booting legacy OSes, but custom firmware is available -- see [[Firmware]].

<div style="margin:3em 0; padding:1em; border:1px solid #ff8888;">
<span style="background-color:#ffcccc;padding:0.2em 0.4em">'''Important Note'''</span> '''(Now RESOLVED -- see below for details)'''

We have received several reports of '''hardware speaker damage''' in Braswell models with the Realtek ALC5650 audio chip. This includes most Braswells, '''except''' the Acer R11 Chromebook (CYAN), which has a Maxim MAX98090 chip instead.

This issue is not limited to GalliumOS or Linux, but it seems to happen more frequently when the machine is ''not'' booted into ChromeOS (i.e. at the Developer Mode screen, in firmware, in GRUB, or running Linux).

When your Chromebook is powered on or rebooted, the ChromeOS bootloader (depthcharge) is loaded first, regardless of what operating system you will be running. Depthcharge performs the first initialization of the audio chip. The chip is re-initialized later by ChromeOS, but if the Chromebook is booted into another operating system instead (or not booted at all), no further initialization is performed. It is ''possible'' that depthcharge is leaving the chip in an inappropriate state, but that should not be an adequate explanation -- unless some percentage of the Realtek chips are faulty.

<div style="border:1px solid #cccccc; padding:0 0 0 0.5em; margin:0 1em;">
'''Update 20170118''': GalliumOS now includes audio drivers for the Realtek ALC5650, and so ''does'' perform additional initialization after depthcharge. This ''might'' reduce the risk of speaker damage, but of course the additional initialization is not performed until GalliumOS is booted -- so there remains a period of time between power-on and fully-booted where the chip is only initialized by depthcharge, and might be at risk. Other Linux distros '''do not''' include these drivers yet, but they should be in mainline kernels around version 4.11 or 4.12.
</div>

Full details and current speculation can be found on the GitHub [https://github.com/GalliumOS/galliumos-distro/issues/270 Braswell Platform Validation] ticket.

The cautious approach is to disconnect your Chromebook speakers until and unless the ultimate cause of the problem can be identified and avoided.

A more casual approach is to ''carefully'' observe your Chromebook for unusual noises/heating around the speaker area while in use (or powered on), and be prepared to return any defective hardware within ordinary return windows if problems occur. We estimate the failure rate at about 2-3% of all devices, and the failure is expected to happen within a short period of use (minutes to single-digit hours).

At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return (or that has adequate time remaining on the return window), and which you are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org or freenode [https://galliumos.org/irc #galliumos]). Thank you!

<div style="border:1px solid #cccccc; padding:0 0 0 0.5em; margin:0 1em;">
<p>'''Update 20180723''': We've seen no new reports of this issue since before January 2017, so it's safe to consider this '''fully resolved'''.</p> <p>Additionally, Braswell models now have the option of full ROM firmware from MrChromebox (see [[Firmware]]), which replaces the ChromeOS firmware entirely, removing the last small gap of exposure.</p>
</div>

</div>

Support/Pineview

2018-07-22T02:07:01Z

Reynhout: /* Google Cr-48 (MARIO) */

The first ChromeOS devices shipped with Intel Atom processors with Pineview cores.

These models do not include general purpose bootloaders in their factory firmware, custom firmware is not generally available for them. Consequently, GalliumOS cannot be installed on these models, but you might be able to install an older version of Ubuntu (14.04) using the older ChrUbuntu script.

One possible exception is MARIO. See below.

== Model-Specific Notes ==

=== Google Cr-48 (MARIO) ===

There is a third party firmware floating around for MARIO. Reports indicate that it works with GalliumOS.

More info from u/cr08: https://www.reddit.com/r/GalliumOS/comments/902oet/cr48_confirmed_working_and_functional_questions/

See https://cr-48.wikispaces.com/ for details, and let us know how things go!

* https://cr-48.wikispaces.com/Flash+BIOS
* https://cr-48.wikispaces.com/Windows8

Hardware Compatibility

2018-07-22T02:04:52Z

Reynhout:

Installing/Creating Bootable USB

2018-07-19T16:08:40Z

Reynhout: /* Testing your USB drive and write */

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 ChromeOS or 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 -X <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. The <code>-X</code> option is required to strip any extended attributes that are added by web browsers to downloaded files.</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) ==

<div style="padding:0.2em; background-color:#ffffcc; border:1px solid #cccc88">
* We recommend '''Etcher''' (see above) or '''Win32DiskImager''' (see below)
* '''Rufus''' is also fine, but '''be sure to select <code>"Write in DD-Image mode"</code>'''
* '''Do not use UNetbootin'''
* '''Do not use YUMI'''
* '''Do not use ISO to USB'''
</div>

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.'''

== 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:

=== (Very) 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.

=== 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>
** macOS: <code>md5 ./galliumos.iso</code>
** Windows: https://www.microsoft.com/en-us/download/details.aspx?id=11533
* '''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.
* '''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 ===

You can verify your image, as-written to USB or SD media. This is often different from the image saved to the ISO file, which always indicates a problem!

The steps are a bit more complicated, and sometimes need to be repeated more than once to identify intermittently-failing USB/SD storage media:

# Verify the ISO image, as-written to USB or SD media
#
# Replace "galliumos.iso" with the path to your ISO file
# Replace "/dev/sdb" with the device path of your USD or SD media.
# (check with "lsblk" and use the disk device only, not a partition device)
#
# Visit our support channel on IRC or Reddit for help with any of these steps!
#
ISO_SIZE="$(stat -c '%s' galliumos.iso)"
ISO_MEDIA="/dev/sdb"
sudo head -c "$ISO_SIZE" "$ISO_MEDIA" | md5sum

This should return an MD5 result which matches the published value, and also matches the results of the check of the ISO file itself (described above).

Additionally, the GalliumOS ISO should boot any x86 computer. This is a safe test -- booting from the ISO launches a "Live" demo environment, which does not (automatically) attempt to install any software. This will only identify failed writes that impact booting, of course.

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