https://wiki.galliumos.org/api.php?action=feedcontributions&user=Didfem&feedformat=atomGalliumOS Wiki - User contributions [en]2024-03-28T22:32:34ZUser contributionsMediaWiki 1.27.3https://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=797Installing/New To Linux2016-03-19T15:08:04Z<p>Didfem: /* Capital Lock Key */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (GB). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16 GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 GB of memory on your Chromebook with three 256 GB external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 GB internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Supports GalliumOS</u>''': Better be safe than sorry! Make sure that your Chromebook is supported by GalliumOS. <br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
[[File:TurnOSverif.jpg|centre|thumb|564x564px|Last chance to change your mind!]] <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer Chromebook 15.]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”. (Selecting "Default" is also fine; it does the same thing as the second option but it doesn't say so.)<br />
[[File:Unetboot-Select-A.jpg|centre|thumb|505x505px|Use the Arrow down key to select GalliumOS Live]]<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Save the file.<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
Note that an external keyboard plugged into your Chromebook through whatever connection (USB, Bluetooth, etc.) will work as it is supposed to do according to the particular model, even if you modify/create the configuration files as indicated above. (See below in "Chromebook Special Keys".)<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
Now that you are in "shellball", there is a file there that you have to make executable; it is "gbb_utility". So you type at the prompt:<br />
<br />
chmod +x gbb_utility<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
* The file "bios.bin.new" may not be present in the shellball folder. In that case, the second and forth commands below are not required. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid='ABCXYX X1X-Y2Y-Z3Z' bios.bin<br />
<br />
./gbb_utility --set --hwid='ABCXYX X1X-Y2Y-Z3Z' bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.<br />
<br />
== Conclusion: How much space left? ==<br />
The major concern for a Chromebook user after installing GalliumOS is the amount of space left on the SDD. As initially mentioned, unless you have a large SSD because either you bought a top-of-the line Chromebook or you upgraded to a larger SSD, the usual SSD size on a Chromebook is 16GB. Normally, however, the data files (text, image, video, etc.) should preferably be stored on external drives when using a Chromebook. Still, as a matter of interest, I checked with GParted (available in Settings) the space used on my 16GB Acer CB3-111 after a GalliumOS installation; several applications were added and a complete OS update was performed. I have 5.74GB of free space left, that is more than 1/3 of the drive. But I have to mention that I installed more applications than I'll ever need! For instance, I installed the complete LibreOffice Suite AS WELL AS the complete Microsoft Office 2007 suite, with three grammar and spell-checkers (English, Spanish, French). I also installed Firefox AND Chrome on top of Chromium. So it may be safe to say that for about 90% of the average computer users, space should not be an issue on a Chromebook, provided external USB flash or SD drives are used to keep non-executable files.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Talk:Installing/New_To_Linux&diff=796Talk:Installing/New To Linux2016-03-19T14:58:03Z<p>Didfem: </p>
<hr />
<div>Tracking reviews...<br />
<br />
<!-- ☐ ✓ ☑️ ✘ --><br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Rename page<br />
|-<br />
! <br />
| '''reynhout''': What's the proper name for this page? Installing/New_Linux_Users ? Installing/New_To_Linux ?<br />
<br />
'''didfem''': Installing/New_To_Linux is fine with me.<br />
<br />
'''reynhout''': OK, I'll rename it as such.<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Add authorship and date/version info<br />
|-<br />
! <br />
| '''reynhout''': I think it's important to note this info so readers have assurance that it's current (or reasons to think it might not be) and a channel to primary author(s) for clarification. I think we should do this for all extensive documentation pages.<br />
<br />
'''didfem''': I am not sure what you have in mind for "a channel to primary author". Where should this be mentioned, and what kind of communication means should be used?<br />
<br />
'''reynhout''': Maybe we can just link it to a Reddit thread? We should announce the page when you're ready to go live with it, and solicit comments etc. Then add the link to that thread to the page to complete the circle. Does that sound good?<br />
<br />
'''didfem''': I am OK with all your suggestions regarding Name and Authorship. I feel that this Wiki page is now OK for publishing. Also, I installed GalliumOS/Sandy Bridge-Ivy Bridge on an Acer C710 following the same procedure as outlined here and the process went without a hitch. Maybe you could liaise with ColtronDRG to check if he is OK to have my C710 Installation procedure inputted in the wiki page he opened; this would save some time and effort for all of us. Incidentally, I used the same version of Unetbootin to create the USB GalliumOS/Sandy Bridge-Ivy Bridge live USB and I found that the "timer" that shows up initially to automatically boot to Default GalliumOS worked as advertised (I did two full installs, just to be sure.). This would lead to believe that the problem with this non-functioning timer in other versions of GalliumOS (BayTrail and Broadwell) is not with Unetbootin but with something in the distros themselves. Still, this is fairly unimportant.<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | UNetBootIn? (major?)<br />
|-<br />
! <br />
| '''reynhout''': UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me.<br />
<br />
'''<u>Reply didfem</u>''': I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic.<br />
<br />
'''reynhout''': Fair point. I really dislike that it changes the boot menu, though. What does "Default" do?<br />
<br />
'''didfem''': When you talk about "changing the boot menu", I assume you mean the blue page you see when the computer first boots from the Live USB. This only comes up when you boot from the USB drive. Once GalliumOS is installed, you never see this page again. You get the standard "Press Escape" and boot drive selection. Now that you mention it, I don't really know what "Default" does. I'll have to check it, but I suspect it starts whatever OS is already there on the internal drive. I'll check it to-morrow, for fun.<br />
<br />
'''reynhout''': Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :(<br />
<br />
'''didfem''': Funny enough, I tried all three options in the UNetbootin page. The first one "Default" and the second one "GalliumOS Live Image and Installer" do exactly the same thing. The third one is now (?!) different from the screen dump I took only a week ago and inserted in the wiki. It states: "GalliumOS CLI". When this last option is selected, it first displays the standard GalliumOS front page (logo with blue background) then a terminal to enter galliumos login name then password. I don't know if there is a standard login name and password to install GalliumOS from the command line and I think it's totally immaterial. The indications I wrote in the wiki are still valid, although I could also state that pressing Enter when Default is highlighted (the "opening" option) will do the same thing. The only indication that is wrong in the UNetbootin start-up page is where it states: "Automatic boot in 10 seconds". You can wait all day, it won't boot! I haven't had this problem with many (too many...!) live USB I prepared with UNetbootin. So it might be something in GalliumOS or UNetbootin, or the interaction between the two, that causes this slightly odd behavior. Nevertheless, if you follow the Tutorial (Select "GalliumOS Live Image and Installer" with the down arrow key and press Enter), you should have no problem. I am going to take another image of the new (!) UNetbootin start-up page and drop it into the wiki page.<br />
<br />
'''didfem''': I pushed further my investigation of the CLI option in UNetbootin. It takes you to a terminal prompting you for a "galliumos login". If you enter "username" and leave the Password blank, you get to a standard Linux terminal prompt. If you enter "startx", you get to the GalliumOS Live USB page (glass building shot from below, "Install GalliumOS" icon, etc.). In other words, it's a long way to reach the same destination. No gas saving there!<br />
<br />
'''reynhout''': Yes, the CLI option is for the case when the graphical environment won't start correctly, so a command line interface is the only choice. We discussed whether it was useful to include in the release ISOs and decided it might be, but at the worst was harmless -- assuming people know what CLI stands for. I'm open to removing it or renaming it. <br />
<br />
I wonder if there might be options to Unetbootin that say "don't mess with the ISO, man.."? If it's truly identical to the first option that we create, then I guess it's safe to overlook. I just don't understand why it's there at all. If it affects anything that has an impact in support requests, that would be an issue.<br />
<br />
'''didfem''': I don't think there is any harm in leaving the CLI option as it is. If people select it and don't know what it is, nothing happens: they get to the prompt, are puzzled by the galliumos login, get back out and try the other options which "fortunately" give both the same results. I wonder, however, if this Tutorial should cater to those who want or need to use the command line interface. Since it is aimed at people without Linux and programming expertise, I don't think it would be a good idea that users tinker with a bunch of commands. The options could stay, but we don't have to talk about it. Note that the mystery remains about the "Automatic boot in 10 seconds" that doesn't work. However, I have noticed over the years that this function occasionally doesn't work with some distros; it's kind of "temperamental". Still, in my mind, it's only a "nice to have" feature, not a "need to have". Regarding the publication of this Tutorial, I leave it to you to decide how and when. Also, regarding ColtronDRG, I think I messed up when I try to send a message through the IRC channel. (I am way below the bottom of the learning curve in that IRC thing ...) Just let him know that I am willing to collaborate with him on the Acer 710 Tutorial and contact me through e-mail or through this page. Also, tell him that I suggest to use this Tutorial as a basis for the Acer 710 one; nothing much would have to be changed.<br />
<br />
'''reynhout''': OK, it sounds like UNetBootin does no harm. I don't know much about the failure to autoboot, I don't think I've seen the problem. I will ping ColtonDRG re the Parrot page, and hopefully this weekend have some more time to read your full page properly. :) <br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | GigaBytes (minor, but important)<br />
|-<br />
! <br />
| '''reynhout''': SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks.<br />
<u>'''Reply didfem'''</u>: "Gb" replaced by "GB".<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Hardware Compatibility table (minor)<br />
|-<br />
! <br />
| '''reynhout''': The Hardware Compatibility table lists ''all'' known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility.<br />
'''<u>Reply didfem</u>''': Line added to emphasize the need to check that the Chromebook is supported.<br />
|-<br />
|}</div>Didfemhttps://wiki.galliumos.org/index.php?title=Talk:Installing/New_To_Linux&diff=793Talk:Installing/New To Linux2016-03-19T03:37:47Z<p>Didfem: </p>
<hr />
<div>Tracking reviews...<br />
<br />
<!-- ☐ ✓ ☑️ ✘ --><br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Rename page<br />
|-<br />
! <br />
| '''reynhout''': What's the proper name for this page? Installing/New_Linux_Users ? Installing/New_To_Linux ? <br />
didfem: Installing/New_To_Linux is fine with me. <br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Add authorship and date/version info<br />
|-<br />
! <br />
| '''reynhout''': I think it's important to note this info so readers have assurance that it's current (or reasons to think it might not be) and a channel to primary author(s) for clarification. I think we should do this for all extensive documentation pages. <br />
didfem: I am not sure what you have in mind for "a channel to primary author". Where should this be mentioned, and what kind of communication means should be used? <br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | UNetBootIn? (major?)<br />
|-<br />
! <br />
| '''reynhout''': UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me.<br />
<br />
'''<u>Reply didfem</u>''': I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic.<br />
<br />
'''reynhout''': Fair point. I really dislike that it changes the boot menu, though. What does "Default" do?<br />
<br />
'''didfem''': When you talk about "changing the boot menu", I assume you mean the blue page you see when the computer first boots from the Live USB. This only comes up when you boot from the USB drive. Once GalliumOS is installed, you never see this page again. You get the standard "Press Escape" and boot drive selection. Now that you mention it, I don't really know what "Default" does. I'll have to check it, but I suspect it starts whatever OS is already there on the internal drive. I'll check it to-morrow, for fun.<br />
<br />
'''reynhout''': Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :(<br />
<br />
'''didfem''': Funny enough, I tried all three options in the UNetbootin page. The first one "Default" and the second one "GalliumOS Live Image and Installer" do exactly the same thing. The third one is now (?!) different from the screen dump I took only a week ago and inserted in the wiki. It states: "GalliumOS CLI". When this last option is selected, it first displays the standard GalliumOS front page (logo with blue background) then a terminal to enter galliumos login name then password. I don't know if there is a standard login name and password to install GalliumOS from the command line and I think it's totally immaterial. The indications I wrote in the wiki are still valid, although I could also state that pressing Enter when Default is highlighted (the "opening" option) will do the same thing. The only indication that is wrong in the UNetbootin start-up page is where it states: "Automatic boot in 10 seconds". You can wait all day, it won't boot! I haven't had this problem with many (too many...!) live USB I prepared with UNetbootin. So it might be something in GalliumOS or UNetbootin, or the interaction between the two, that causes this slightly odd behavior. Nevertheless, if you follow the Tutorial (Select "GalliumOS Live Image and Installer" with the down arrow key and press Enter), you should have no problem. I am going to take another image of the new (!) UNetbootin start-up page and drop it into the wiki page.<br />
<br />
'''didfem''': I pushed further my investigation of the CLI option in UNetbootin. It takes you to a terminal prompting you for a "galliumos login". If you enter "username" and leave the Password blank, you get to a standard Linux terminal prompt. If you enter "startx", you get to the GalliumOS Live USB page (glass building shot from below, "Install GalliumOS" icon, etc.). In other words, it's a long way to reach the same destination. No gas saving there!<br />
<br />
'''reynhout''': Yes, the CLI option is for the case when the graphical environment won't start correctly, so a command line interface is the only choice. We discussed whether it was useful to include in the release ISOs and decided it might be, but at the worst was harmless -- assuming people know what CLI stands for. I'm open to removing it or renaming it. <br />
<br />
I wonder if there might be options to Unetbootin that say "don't mess with the ISO, man.."? If it's truly identical to the first option that we create, then I guess it's safe to overlook. I just don't understand why it's there at all. If it affects anything that has an impact in support requests, that would be an issue.<br />
<br />
'''didfem''': I don't think there is any harm in leaving the CLI option as it is. If people select it and don't know what it is, nothing happens: they get to the prompt, are puzzled by the galliumos login, get back out and try the other options which "fortunately" give both the same results. I wonder, however, if this Tutorial should cater to those who want or need to use the command line interface. Since it is aimed at people without Linux and programming expertise, I don't think it would be a good idea that users tinker with a bunch of commands. The options could stay, but we don't have to talk about it. Note that the mystery remains about the "Automatic boot in 10 seconds" that doesn't work. However, I have noticed over the years that this function occasionally doesn't work with some distros; it's kind of "temperamental". Still, in my mind, it's only a "nice to have" feature, not a "need to have". Regarding the publication of this Tutorial, I leave it to you to decide how and when. Also, regarding ColtronDRG, I think I messed up when I try to send a message through the IRC channel. (I am way below the bottom of the learning curve in that IRC thing ...) Just let him know that I am willing to collaborate with him on the Acer 710 Tutorial and contact me through e-mail or through this page. Also, tell him that I suggest to use this Tutorial as a basis for the Acer 710 one; nothing much would have to be changed.<br />
<br />
'''reynhout''': OK, it sounds like UNetBootin does no harm. I don't know much about the failure to autoboot, I don't think I've seen the problem. I will ping ColtonDRG re the Parrot page, and hopefully this weekend have some more time to read your full page properly. :) <br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | GigaBytes (minor, but important)<br />
|-<br />
! <br />
| '''reynhout''': SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks.<br />
<u>'''Reply didfem'''</u>: "Gb" replaced by "GB".<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Hardware Compatibility table (minor)<br />
|-<br />
! <br />
| '''reynhout''': The Hardware Compatibility table lists ''all'' known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility.<br />
'''<u>Reply didfem</u>''': Line added to emphasize the need to check that the Chromebook is supported.<br />
|-<br />
|}</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=748Installing/New To Linux2016-03-09T03:54:03Z<p>Didfem: </p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (GB). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16 GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 GB of memory on your Chromebook with three 256 GB external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 GB internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Supports GalliumOS</u>''': Better be safe than sorry! Make sure that your Chromebook is supported by GalliumOS. <br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
[[File:TurnOSverif.jpg|centre|thumb|564x564px|Last chance to change your mind!]] <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer Chromebook 15.]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”. (Selecting "Default" is also fine; it does the same thing as the second option but it doesn't say so.)<br />
[[File:Unetboot-Select-A.jpg|centre|thumb|505x505px|Use the Arrow down key to select GalliumOS Live]]<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
Now that you are in "shellball", there is a file there that you have to make executable; it is "gbb_utility". So you type at the prompt:<br />
<br />
chmod +x gbb_utility<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
* The file "bios.bin.new" may not be present in the shellball folder. In that case, the second and forth commands below are not required. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid='ABCXYX X1X-Y2Y-Z3Z' bios.bin<br />
<br />
./gbb_utility --set --hwid='ABCXYX X1X-Y2Y-Z3Z' bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.<br />
<br />
== Conclusion: How much space left? ==<br />
The major concern for a Chromebook user after installing GalliumOS is the amount of space left on the SDD. As initially mentioned, unless you have a large SSD because either you bought a top-of-the line Chromebook or you upgraded to a larger SSD, the usual SSD size on a Chromebook is 16GB. Normally, however, the data files (text, image, video, etc.) should preferably be stored on external drives when using a Chromebook. Still, as a matter of interest, I checked with GParted (available in Settings) the space used on my 16GB Acer CB3-111 after a GalliumOS installation; several applications were added and a complete OS update was performed. I have 5.74GB of free space left, that is more than 1/3 of the drive. But I have to mention that I installed more applications than I'll ever need! For instance, I installed the complete LibreOffice Suite AS WELL AS the complete Microsoft Office 2007 suite, with three grammar and spell-checkers (English, Spanish, French). I also installed Firefox AND Chrome on top of Chromium. So it may be safe to say that for about 90% of the average computer users, space should not be an issue on a Chromebook, provided external USB flash or SD drives are used to keep non-executable files.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Talk:Installing/New_To_Linux&diff=686Talk:Installing/New To Linux2016-02-25T23:46:51Z<p>Didfem: </p>
<hr />
<div>Tracking reviews...<br />
<br />
<!-- ☐ ✓ ☑️ ✘ --><br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | UNetBootIn? (major?)<br />
|-<br />
! <br />
| '''reynhout''': UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me.<br />
<br />
'''<u>Reply didfem</u>''': I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic.<br />
<br />
'''reynhout''': Fair point. I really dislike that it changes the boot menu, though. What does "Default" do?<br />
<br />
'''didfem''': When you talk about "changing the boot menu", I assume you mean the blue page you see when the computer first boots from the Live USB. This only comes up when you boot from the USB drive. Once GalliumOS is installed, you never see this page again. You get the standard "Press Escape" and boot drive selection. Now that you mention it, I don't really know what "Default" does. I'll have to check it, but I suspect it starts whatever OS is already there on the internal drive. I'll check it to-morrow, for fun.<br />
<br />
'''reynhout''': Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :(<br />
<br />
'''didfem''': Funny enough, I tried all three options in the UNetbootin page. The first one "Default" and the second one "GalliumOS Live Image and Installer" do exactly the same thing. The third one is now (?!) different from the screen dump I took only a week ago and inserted in the wiki. It states: "GalliumOS CLI". When this last option is selected, it first displays the standard GalliumOS front page (logo with blue background) then a terminal to enter galliumos login name then password. I don't know if there is a standard login name and password to install GalliumOS from the command line and I think it's totally immaterial. The indications I wrote in the wiki are still valid, although I could also state that pressing Enter when Default is highlighted (the "opening" option) will do the same thing. The only indication that is wrong in the UNetbootin start-up page is where it states: "Automatic boot in 10 seconds". You can wait all day, it won't boot! I haven't had this problem with many (too many...!) live USB I prepared with UNetbootin. So it might be something in GalliumOS or UNetbootin, or the interaction between the two, that causes this slightly odd behavior. Nevertheless, if you follow the Tutorial (Select "GalliumOS Live Image and Installer" with the down arrow key and press Enter), you should have no problem. I am going to take another image of the new (!) UNetbootin start-up page and drop it into the wiki page.<br />
<br />
'''didfem''': I pushed further my investigation of the CLI option in UNetbootin. It takes you to a terminal prompting you for a "galliumos login". If you enter "username" and leave the Password blank, you get to a standard Linux terminal prompt. If you enter "startx", you get to the GalliumOS Live USB page (glass building shot from below, "Install GalliumOS" icon, etc.). In other words, it's a long way to reach the same destination. No gas saving there!<br />
<br />
'''reynhout''': Yes, the CLI option is for the case when the graphical environment won't start correctly, so a command line interface is the only choice. We discussed whether it was useful to include in the release ISOs and decided it might be, but at the worst was harmless -- assuming people know what CLI stands for. I'm open to removing it or renaming it. <br />
<br />
I wonder if there might be options to Unetbootin that say "don't mess with the ISO, man.."? If it's truly identical to the first option that we create, then I guess it's safe to overlook. I just don't understand why it's there at all. If it affects anything that has an impact in support requests, that would be an issue.<br />
<br />
'''didfem''': I don't think there is any harm in leaving the CLI option as it is. If people select it and don't know what it is, nothing happens: they get to the prompt, are puzzled by the galliumos login, get back out and try the other options which "fortunately" give both the same results. I wonder, however, if this Tutorial should cater to those who want or need to use the command line interface. Since it is aimed at people without Linux and programming expertise, I don't think it would be a good idea that users tinker with a bunch of commands. The options could stay, but we don't have to talk about it. Note that the mystery remains about the "Automatic boot in 10 seconds" that doesn't work. However, I have noticed over the years that this function occasionally doesn't work with some distros; it's kind of "temperamental". Still, in my mind, it's only a "nice to have" feature, not a "need to have". Regarding the publication of this Tutorial, I leave it to you to decide how and when. Also, regarding ColtronDRG, I think I messed up when I try to send a message through the IRC channel. (I am way below the bottom of the learning curve in that IRC thing ...) Just let him know that I am willing to collaborate with him on the Acer 710 Tutorial and contact me through e-mail or through this page. Also, tell him that I suggest to use this Tutorial as a basis for the Acer 710 one; nothing much would have to be changed.<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | GigaBytes (minor, but important)<br />
|-<br />
! <br />
| '''reynhout''': SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks.<br />
<u>'''Reply didfem'''</u>: "Gb" replaced by "GB".<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Hardware Compatibility table (minor)<br />
|-<br />
! <br />
| '''reynhout''': The Hardware Compatibility table lists ''all'' known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility.<br />
'''<u>Reply didfem</u>''': Line added to emphasize the need to check that the Chromebook is supported.<br />
|-<br />
|}</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=684Installing/New To Linux2016-02-25T18:37:46Z<p>Didfem: /* Install GalliumOS */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (GB). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16 GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 GB of memory on your Chromebook with three 256 GB external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 GB internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Supports GalliumOS</u>''': Better be safe than sorry! Make sure that your Chromebook is supported by GalliumOS. <br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
[[File:TurnOSverif.jpg|centre|thumb|564x564px|Last chance to change your mind!]] <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer Chromebook 15.]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”. (Selecting "Default" is also fine; it does the same thing as the second option but it doesn't say so.)<br />
[[File:Unetboot-Select-A.jpg|centre|thumb|505x505px|Use the Arrow down key to select GalliumOS Live]]<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.<br />
<br />
== Conclusion: How much space left? ==<br />
The major concern for a Chromebook user after installing GalliumOS is the amount of space left on the SDD. As initially mentioned, unless you have a large SSD because either you bought a top-of-the line Chromebook or you upgraded to a larger SSD, the usual SSD size on a Chromebook is 16GB. Normally, however, the data files (text, image, video, etc.) should preferably be stored on external drives when using a Chromebook. Still, as a matter of interest, I checked with GParted (available in Settings) the space used on my 16GB Acer CB3-111 after a GalliumOS installation; several applications were added and a complete OS update was performed. I have 5.74GB of free space left, that is more than 1/3 of the drive. But I have to mention that I installed more applications than I'll ever need! For instance, I installed the complete LibreOffice Suite AS WELL AS the complete Microsoft Office 2007 suite, with three grammar and spell-checkers (English, Spanish, French). I also installed Firefox AND Chrome on top of Chromium. So it may be safe to say that for about 90% of the average computer users, space should not be an issue on a Chromebook, provided external USB flash or SD drives are used to keep non-executable files.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:Unetboot-Select-A.jpg&diff=683File:Unetboot-Select-A.jpg2016-02-25T18:32:59Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Talk:Installing/New_To_Linux&diff=682Talk:Installing/New To Linux2016-02-25T18:21:52Z<p>Didfem: </p>
<hr />
<div>Tracking reviews...<br />
<br />
<!-- ☐ ✓ ☑️ ✘ --><br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | UNetBootIn? (major?)<br />
|-<br />
! <br />
| '''reynhout''': UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me.<br />
<br />
'''<u>Reply didfem</u>''': I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic.<br />
<br />
'''reynhout''': Fair point. I really dislike that it changes the boot menu, though. What does "Default" do?<br />
<br />
'''didfem''': When you talk about "changing the boot menu", I assume you mean the blue page you see when the computer first boots from the Live USB. This only comes up when you boot from the USB drive. Once GalliumOS is installed, you never see this page again. You get the standard "Press Escape" and boot drive selection. Now that you mention it, I don't really know what "Default" does. I'll have to check it, but I suspect it starts whatever OS is already there on the internal drive. I'll check it to-morrow, for fun.<br />
<br />
'''reynhout''': Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :(<br />
<br />
'''didfem''': Funny enough, I tried all three options in the UNetbootin page. The first one "Default" and the second one "GalliumOS Live Image and Installer" do exactly the same thing. The third one is now (?!) different from the screen dump I took only a week ago and inserted in the wiki. It states: "GalliumOS CLI". When this last option is selected, it first displays the standard GalliumOS front page (logo with blue background) then a terminal to enter galliumos login name then password. I don't know if there is a standard login name and password to install GalliumOS from the command line and I think it's totally immaterial. The indications I wrote in the wiki are still valid, although I could also state that pressing Enter when Default is highlighted (the "opening" option) will do the same thing. The only indication that is wrong in the UNetbootin start-up page is where it states: "Automatic boot in 10 seconds". You can wait all day, it won't boot! I haven't had this problem with many (too many...!) live USB I prepared with UNetbootin. So it might be something in GalliumOS or UNetbootin, or the interaction between the two, that causes this slightly odd behavior. Nevertheless, if you follow the Tutorial (Select "GalliumOS Live Image and Installer" with the down arrow key and press Enter), you should have no problem. I am going to take another image of the new (!) UNetbootin start-up page and drop it into the wiki page.<br />
<br />
'''didfem''': I pushed further my investigation of the CLI option in UNetbootin. It takes you to a terminal prompting you for a "galliumos login". If you enter "username" and leave the Password blank, you get to a standard Linux terminal prompt. If you enter "startx", you get to the GalliumOS Live USB page (glass building shot from below, "Install GalliumOS" icon, etc.). In other words, it's a long way to reach the same destination. No gas saving there!<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | GigaBytes (minor, but important)<br />
|-<br />
! <br />
| '''reynhout''': SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks.<br />
<u>'''Reply didfem'''</u>: "Gb" replaced by "GB".<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Hardware Compatibility table (minor)<br />
|-<br />
! <br />
| '''reynhout''': The Hardware Compatibility table lists ''all'' known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility.<br />
'''<u>Reply didfem</u>''': Line added to emphasize the need to check that the Chromebook is supported.<br />
|-<br />
|}</div>Didfemhttps://wiki.galliumos.org/index.php?title=Talk:Installing/New_To_Linux&diff=680Talk:Installing/New To Linux2016-02-25T18:01:03Z<p>Didfem: </p>
<hr />
<div>Tracking reviews...<br />
<br />
<!-- ☐ ✓ ☑️ ✘ --><br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | UNetBootIn? (major?)<br />
|-<br />
! <br />
| '''reynhout''': UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me.<br />
<br />
'''<u>Reply didfem</u>''': I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic.<br />
<br />
'''reynhout''': Fair point. I really dislike that it changes the boot menu, though. What does "Default" do?<br />
<br />
'''didfem''': When you talk about "changing the boot menu", I assume you mean the blue page you see when the computer first boots from the Live USB. This only comes up when you boot from the USB drive. Once GalliumOS is installed, you never see this page again. You get the standard "Press Escape" and boot drive selection. Now that you mention it, I don't really know what "Default" does. I'll have to check it, but I suspect it starts whatever OS is already there on the internal drive. I'll check it to-morrow, for fun.<br />
<br />
'''reynhout''': Right. The issue has come up before where users are looking for support and saying they used the "default" install option. We didn't create that and don't know what it does. In fact I had no idea where it was coming from until I saw your screenshots. It might be fine. I can't think of any good reason that it would be added by UnetBootIn though, and plenty of bad reasons. :(<br />
<br />
'''didfem''': Funny enough, I tried all three options in the UNetbootin page. The first one "Default" and the second one "GalliumOS Live Image and Installer" do exactly the same thing. The third one is now (?!) different from the screen dump I took only a week ago and inserted in the wiki. It states: "GalliumOS CLI". When this last option is selected, it first displays the standard GalliumOS front page (logo with blue background) then a terminal to enter galliumos login name then password. I don't know if there is a standard login name and password to install GalliumOS from the command line and I think it's totally immaterial. The indications I wrote in the wiki are still valid, although I could also state that pressing Enter when Default is highlighted (the "opening" option) will do the same thing. The only indication that is wrong in the UNetbootin start-up page is where it states: "Automatic boot in 10 seconds". You can wait all day, it won't boot! I haven't had this problem with many (too many...!) live USB I prepared with UNetbootin. So it might be something in GalliumOS or UNetbootin, or the interaction between the two, that causes this slightly odd behavior. Nevertheless, if you follow the Tutorial (Select "GalliumOS Live Image and Installer" with the down arrow key and press Enter), you should have no problem. I am going to take another image of the new (!) UNetbootin start-up page and drop it into the wiki page.<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | GigaBytes (minor, but important)<br />
|-<br />
! <br />
| '''reynhout''': SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks.<br />
<u>'''Reply didfem'''</u>: "Gb" replaced by "GB".<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Hardware Compatibility table (minor)<br />
|-<br />
! <br />
| '''reynhout''': The Hardware Compatibility table lists ''all'' known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility.<br />
'''<u>Reply didfem</u>''': Line added to emphasize the need to check that the Chromebook is supported.<br />
|-<br />
|}</div>Didfemhttps://wiki.galliumos.org/index.php?title=Talk:Installing/New_To_Linux&diff=672Talk:Installing/New To Linux2016-02-25T01:44:32Z<p>Didfem: </p>
<hr />
<div>Tracking reviews...<br />
<br />
<!-- ☐ ✓ ☑️ ✘ --><br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | UNetBootIn? (major?)<br />
|-<br />
! <br />
| '''reynhout''': UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me.<br />
<br />
'''<u>Reply didfem</u>''': I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic.<br />
<br />
'''reynhout''': Fair point. I really dislike that it changes the boot menu, though. What does "Default" do?<br />
<br />
'''didfem''': When you talk about "changing the boot menu", I assume you mean the blue page you see when the computer first boots from the Live USB. This only comes up when you boot from the USB drive. Once GalliumOS is installed, you never see this page again. You get the standard "Press Escape" and boot drive selection. Now that you mention it, I don't really know what "Default" does. I'll have to check it, but I suspect it starts whatever OS is already there on the internal drive. I'll check it to-morrow, for fun.<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | GigaBytes (minor, but important)<br />
|-<br />
! <br />
| '''reynhout''': SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks.<br />
<u>'''Reply didfem'''</u>: "Gb" replaced by "GB".<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☑️<br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Hardware Compatibility table (minor)<br />
|-<br />
! <br />
| '''reynhout''': The Hardware Compatibility table lists ''all'' known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility.<br />
'''<u>Reply didfem</u>''': Line added to emphasize the need to check that the Chromebook is supported.<br />
|-<br />
|}</div>Didfemhttps://wiki.galliumos.org/index.php?title=Talk:Installing/New_To_Linux&diff=669Talk:Installing/New To Linux2016-02-24T23:00:11Z<p>Didfem: </p>
<hr />
<div>Tracking reviews...<br />
<br />
<!-- ☐ ✓ ☑️ ✘ --><br />
{| class="wikitable"<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐ <!-- ✓ --><br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | UNetBootIn? (major?)<br />
|-<br />
! <br />
| UNetBootIn might not be the right tool to recommend. I don't know much about it, but it appears to mess with the image before creating the USB drive. That concerns me. 20160224/reynhout<br />
'''<u>Reply didfem</u>''': I have used UNetbootin for years in Windows and Linux and I have never observed a problem that I could trace back to this application. I suggested it because it is available in all three major OS's. However, if you know of another application as simple to use as UNetbootin, we could swap the info. In the wiki, I avoided the "dd" method because users may not have Linux and/or maybe uncomfortable with using a script that requires figuring out what the drives are called and other things. I would really like to keep it basic.<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐ <!-- ✓ --><br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | GigaBytes (minor, but important)<br />
|-<br />
! <br />
| SSD capacities are in Gigabytes (always capital "GB"). Gigabits are "Gb", and are frequently used to measure network throughput rates, but not disks. 20160224/reynhout<br />
<u>'''Reply didfem'''</u>: "Gb" replaced by "GB".<br />
|-<br />
| style="text-align:center;font-weight:bold;background-color:#e0e0e0" | ☐ <!-- ✓ --><br />
| style="text-align:left;font-weight:bold;background-color:#e0e0e0" | Hardware Compatibility table (minor)<br />
|-<br />
! <br />
| The Hardware Compatibility table lists ''all'' known ChromeOS devices, so you need to check the "Supports GalliumOS?" column to determine compatibility. 20160224/reynhout<br />
'''<u>Reply didfem</u>''': Line added to emphasize the need to check that the Chromebook is supported.<br />
|-<br />
|}</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=668Installing/New To Linux2016-02-24T22:47:47Z<p>Didfem: </p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (GB). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16 GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 GB of memory on your Chromebook with three 256 GB external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 GB internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Supports GalliumOS</u>''': Better be safe than sorry! Make sure that your Chromebook is supported by GalliumOS. <br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
[[File:TurnOSverif.jpg|centre|thumb|564x564px|Last chance to change your mind!]] <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer Chromebook 15.]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
[[File:Unetboot-Select.jpg|centre|thumb|588x588px|Use the Arrow down key to select GalliumOS Live]]<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./GBb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./GBb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./GBb_utility --set --flags=0x489 bios.bin<br />
<br />
./GBb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_GBb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.<br />
<br />
== Conclusion: How much space left? ==<br />
The major concern for a Chromebook user after installing GalliumOS is the amount of space left on the SDD. As initially mentioned, unless you have a large SSD because either you bought a top-of-the line Chromebook or you upgraded to a larger SSD, the usual SSD size on a Chromebook is 16GB. Normally, however, the data files (text, image, video, etc.) should preferably be stored on external drives when using a Chromebook. Still, as a matter of interest, I checked with GParted (available in Settings) the space used on my 16GB Acer CB3-111 after a GalliumOS installation; several applications were added and a complete OS update was performed. I have 5.74GB of free space left, that is more than 1/3 of the drive. But I have to mention that I installed more applications than I'll ever need! For instance, I installed the complete LibreOffice Suite AS WELL AS the complete Microsoft Office 2007 suite, with three grammar and spell-checkers (English, Spanish, French). I also installed Firefox AND Chrome on top of Chromium. So it may be safe to say that for about 90% of the average computer users, space should not be an issue on a Chromebook, provided external USB flash or SD drives are used to keep non-executable files.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=663Installing/New To Linux2016-02-24T15:56:16Z<p>Didfem: /* Conclusion: How much space left? */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
[[File:TurnOSverif.jpg|centre|thumb|564x564px|Last chance to change your mind!]] <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer Chromebook 15.]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
[[File:Unetboot-Select.jpg|centre|thumb|588x588px|Use the Arrow down key to select GalliumOS Live]]<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.<br />
<br />
== Conclusion: How much space left? ==<br />
The major concern for a Chromebook user after installing GalliumOS is the amount of space left on the SDD. As initially mentioned, unless you have a large SSD because either you bought a top-of-the line Chromebook or you upgraded to a larger SSD, the usual SSD size on a Chromebook is 16Gb. Normally, however, the data files (text, image, video, etc.) should preferably be stored on external drives when using a Chromebook. Still, as a matter of interest, I checked with GParted (available in Settings) the space used on my 16Gb Acer CB3-111 after a GalliumOS installation; several applications were added and a complete OS update was performed. I have 5.74Gb of free space left, that is more than 1/3 of the drive. But I have to mention that I installed more applications than I'll ever need! For instance, I installed the complete LibreOffice Suite AS WELL AS the complete Microsoft Office 2007 suite, with three grammar and spell-checkers (English, Spanish, French). I also installed Firefox AND Chrome on top of Chromium. So it may be safe to say that for about 90% of the average computer users, space should not be an issue on a Chromebook, provided external USB flash or SD drives are used to keep non-executable files.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=662Installing/New To Linux2016-02-24T15:52:21Z<p>Didfem: /* Get into Developer Mode */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
[[File:TurnOSverif.jpg|centre|thumb|564x564px|Last chance to change your mind!]] <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer Chromebook 15.]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
[[File:Unetboot-Select.jpg|centre|thumb|588x588px|Use the Arrow down key to select GalliumOS Live]]<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.<br />
<br />
== Conclusion: How much space left? ==<br />
The major concern for a Chromebook user after installing GalliumOS is the amount of space left on the SDD. As initially mentioned, unless you have a large SSD because either you bought a top-of-the line Chromebook or you upgraded to a larger SSD, the usual SSD size on a Chromebook is 16Gb. Normally, as was already mentioned the data files (text, image, video, etc.) to be kept should be stored on external drives. Still, as a matter of interest, I checked with GParted (available in Settings) the space used on my 16Gb Acer CB3-111 after a GalliumOS Install, several applications added and a complete OS update. I have 5.74Gb of free space left, that is more than 1/3 of the drive. But I have to mention that I installed more applications than I'll ever need! For instance, I installed the complete LibreOffice Suite AS WELL AS the complete Microsoft Office 2007 suite, with three grammar and spell-checkers (English, Spanish, French). I also installed Firefox AND Chrome on top of Chromium. So it may be safe to say that for about 90% of the average computer users, space should not be an issue on a Chromebook, provided external USB flash or SD drives are used to keep non-executable files.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:TurnOSverif.jpg&diff=661File:TurnOSverif.jpg2016-02-24T15:46:03Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=639Installing/New To Linux2016-02-18T20:48:41Z<p>Didfem: /* Reset the "flags" and OS Verification */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer CB3-111]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
[[File:Unetboot-Select.jpg|centre|thumb|588x588px|Use the Arrow down key to select GalliumOS Live]]<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.<br />
<br />
== Conclusion: How much space left? ==<br />
The major concern for a Chromebook user after installing GalliumOS is the amount of space left on the SDD. As initially mentioned, unless you have a large SSD because either you bought a top-of-the line Chromebook or you upgraded to a larger SSD, the usual SSD size on a Chromebook is 16Gb. Normally, as was already mentioned the data files (text, image, video, etc.) to be kept should be stored on external drives. Still, as a matter of interest, I checked with GParted (available in Settings) the space used on my 16Gb Acer CB3-111 after a GalliumOS Install, several applications added and a complete OS update. I have 5.74Gb of free space left, that is more than 1/3 of the drive. But I have to mention that I installed more applications than I'll ever need! For instance, I installed the complete LibreOffice Suite AS WELL AS the complete Microsoft Office 2007 suite, with three grammar and spell-checkers (English, Spanish, French). I also installed Firefox AND Chrome on top of Chromium. So it may be safe to say that for about 90% of the average computer users, space should not be an issue on a Chromebook, provided external USB flash or SD drives are used to keep non-executable files.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=638Installing/New To Linux2016-02-18T20:01:59Z<p>Didfem: </p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer CB3-111]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
[[File:Unetboot-Select.jpg|centre|thumb|588x588px|Use the Arrow down key to select GalliumOS Live]]<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just double-click on Install GalliumOS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
[[File:Erase-disk.jpg|centre|thumb|577x577px|An easy choice at last: Erase the disk!]] <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:Erase-disk.jpg&diff=637File:Erase-disk.jpg2016-02-18T20:00:25Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=636Installing/New To Linux2016-02-18T19:50:23Z<p>Didfem: /* Install GalliumOS */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer CB3-111]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
[[File:Unetboot-Select.jpg|centre|thumb|588x588px|Use the Arrow down key to select GalliumOS Live]]<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
[[File:InstallGall0S.jpg|centre|thumb|608x608px|Just click on Install Gallium OS icon!]]<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:InstallGall0S.jpg&diff=635File:InstallGall0S.jpg2016-02-18T19:45:54Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=File:Unetboot-Select.jpg&diff=634File:Unetboot-Select.jpg2016-02-18T19:45:26Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=633Installing/New To Linux2016-02-18T19:34:21Z<p>Didfem: /* Remove the Write Protection, if required */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
[[File:WP-screw-02.jpg|centre|thumb|720x720px|Write-protection screw (circled in red) on an Acer CB3-111]] <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=632Installing/New To Linux2016-02-18T19:31:25Z<p>Didfem: /* Get into Developer Mode */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. <br />
[[File:OSVerifOFF.jpg|centre|thumb|577x577px|Let your computer do its thing!]] <br />
<br />
After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:OSVerifOFF.jpg&diff=631File:OSVerifOFF.jpg2016-02-18T19:29:02Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=630Installing/New To Linux2016-02-18T19:21:48Z<p>Didfem: /* Get into Developer Mode */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeMissModel.jpg|centre|thumb|576x576px|Scary, but informative!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:ChromeMissModel.jpg&diff=629File:ChromeMissModel.jpg2016-02-18T19:20:20Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=628Installing/New To Linux2016-02-18T19:13:30Z<p>Didfem: </p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." <br />
[[File:ChromeOSMissing.jpg|centre|thumb|588x588px|The "scary page"!]] <br />
<br />
Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:WP-screw-02.jpg&diff=627File:WP-screw-02.jpg2016-02-18T19:10:28Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=File:ChromeOSMissing.jpg&diff=626File:ChromeOSMissing.jpg2016-02-18T19:09:56Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=625Installing/New To Linux2016-02-18T18:58:27Z<p>Didfem: /* Chromebook Recovery Media */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|649x649px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
[[File:Identify-Chromebook.jpg|centre|thumb|604x604px|Your Chromebook Identity]] <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:Identify-Chromebook.jpg&diff=624File:Identify-Chromebook.jpg2016-02-18T18:55:17Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=File:Recovery-icon-02.jpg&diff=623File:Recovery-icon-02.jpg2016-02-18T17:37:41Z<p>Didfem: Didfem uploaded a new version of File:Recovery-icon-02.jpg</p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=622Installing/New To Linux2016-02-18T17:33:53Z<p>Didfem: /* Chromebook Recovery Media */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu|400x400px]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=621Installing/New To Linux2016-02-18T17:28:59Z<p>Didfem: /* Chromebook Recovery Media */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
[[File:Recovery-icon-02.jpg|centre|frameless|Recovery Icon in ChromeOS Menu]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=620Installing/New To Linux2016-02-18T17:24:50Z<p>Didfem: /* Chromebook Recovery Media */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
<nowiki>[[File:Recovery-icon-02.jpg|20px|link=]]</nowiki> <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=619Installing/New To Linux2016-02-18T16:56:46Z<p>Didfem: </p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
[[:File:Recovery-icon-02.jpg]] <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=File:Recovery-icon-02.jpg&diff=618File:Recovery-icon-02.jpg2016-02-18T16:36:43Z<p>Didfem: </p>
<hr />
<div></div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=613Installing/New To Linux2016-02-18T03:06:22Z<p>Didfem: /* Restart your computer */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF.<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page.<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=612Installing/New To Linux2016-02-18T03:05:04Z<p>Didfem: /* Office Suite */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. <br />
<br />
If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. All the praise you may read on Internet about this Office Suite is well deserved. <br />
<br />
In case you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, your option is to use Wine, an application that makes Windows applications "believe" they are in Windows OS. Wine per se is a bit tricky to configure; the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it. However, you will find in Synaptic Package Manager a front-end for Wine called PlayOnLinux that will make installing Windows application a breeze. Once installed in GalliumOS, PlayOnLinux comes in the Menu under Games (?!!). Installing Microsoft Office with PlayOnLinux is fairly straightforward. However, installing the updates or "Service Packs (SP)" may be a bit trickier, so here is how it goes. <br />
<br />
Let's assume that you have installed MS Office 2007 with PlayOnLinux. You also downloaded the appropriate update from the MS site (SP3, in the case of Office 2007); it goes into your Downloads folder. You now open PlayOnLinux (in Games, remember?) and you click on the Configure icon. In the PlayOnLinux configuration window, you click on Office2007 (or whichever MS Office Suite you installed). You now click on the Miscellaneous tab and click on "Run a .exe file in this virtual drive". You select in Downloads the MS Office Service Pack .exe file and follow the instructions. Your MS Office 2007 will be updated as required.<br />
<br />
If you really want to make it very simple, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. <br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=611Installing/New To Linux2016-02-17T21:51:51Z<p>Didfem: /* Office Suite */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. <br />
<br />
In the very improbable case that you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, you may wish to install CrossOver Office by Codeweavers. (See https://www.codeweavers.com) This application is not free but it simplifies greatly the installation of Windows applications in Linux. Although Wine, on which CrossOver Office is based, is freely available through Synaptic Package Manager, the user without a thorough knowledge of Wine may not obtain satisfactory results when attempting to use it.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=610Installing/New To Linux2016-02-17T21:10:27Z<p>Didfem: /* File Transfer on Private Network */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
=== Office Suite ===<br />
AbiWord is a simple and efficient application for word-processing. In AbiWord, you can open and save Microsoft<sup>TM</sup> Office Word documents. If you need a full Office Suite, look no further than LibreOffice, a free and open-source software. <br />
<br />
In the very improbable case that you absolutely need the actual Microsoft<sup>TM</sup> Office Suite, it is recommended that you install it through Wine that creates a bridge between the Windows program and Linux. Wine can be installed with Synaptic Package Manager.<br />
<br />
To make it even simpler, you may wish to install CrossOver Office by Codeweavers. See https://www.codeweavers.com<br />
<br />
This application is not free (about US$60.00) but it simplifies greatly the installation of Windows applications in Linux.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device (probably a single screw to put back in place) if a change on the motherboard was required to disable the physical BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=609Installing/New To Linux2016-02-17T20:38:35Z<p>Didfem: /* Printers */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
NOTE: Many Chromebooks have small screens. In Linux, it may happen that you are not able to see the bottom of a displayed window. This is particularly embarrassing if you have something to click on in that area. There is an easy trick: keep a finger on Left Alt and click on the window. As long as you keep the Left Alt key and the left mouse button pressed in, you can bring the window up or down, and move it around wherever you please.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, select Printers. Click on Add. If you have one or more Network printers - that is the most probable scenario - just click on Network Printer and Find Network Printer. It may take a while (15-20 seconds), but the printers on your local network should be detected. If the system proposes a "generic printer" or if you cannot find the exact printer model in the list under the manufacturer's name, it means that the driver is not available in the present Linux kernel; however, it is most probably available on the manufacturer’s site. Just go to their site, enter your computer model and follow the instructions. Actually, as a rule, it always safer to check if there is a Linux driver on the manufacturer's site. <br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file (the application file format in GalliumOS), you install it using GDebi. To do so, open your Thunar file manager (the icon on the taskbar that looks like a folder), go to the Downloads folder and find in there the file with the ".deb" suffix you just downloaded. Right click on the file icon and select "Open with GDebi package manager". Follow the instructions.<br />
<br />
=== New Applications and Updates ===<br />
You have thousands of applications at your disposal in Linux. You also have in GalliumOS a very easy and efficient tool to install applications: Synaptic Package Manager. In GalliumOS Menu, the Synaptic Package Manager is found under System. Just click on it, enter your password, search the application you need and, when it is listed in the window, right click on the window and select "Mark for Installation". You may have to Mark additional required changes (the system will ask you if you accept to do that), and you then click Apply. That's all.<br />
<br />
If you want to install all updates that may have cropped up since your GalliumOS version first came out, you also use the Synaptic Package Manager. First, you click on All, in the left window, then on Reload, in the Icon bar, then on Mark All Upgrades, also in the Icon bar. You just have to click Apply, still in the Icon bar, and all your software will be updated. <br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. Use Synaptic Package Manager to select and install the Nautilus application. <br />
<br />
In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
Office Suite<br />
<br />
AbiWord is quite a decent application for word-processing. If you need a full Office Suite, look no further than LibreOffice<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=608Installing/New To Linux2016-02-17T19:47:17Z<p>Didfem: /* Mouse and Touchpad */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Follow the instructions, except that at the beginning, you won't access the terminal by entering Ctrl+Alt+T. But it's even simpler in GalliumOS: just click in the taskbar on the icon that shows an arrow head and a minus sign. <br />
<br />
Once Touchpad Indicator is installed, you need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray". However, the icon may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. While you are in Touchpad indicator Preferences, go to the Actions tab, and select "Disable touchpad when a mouse plugged" and "Enable touuchpad on exit". In General options, select "Autostart". With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, you will find Printers. Select Add Printer and follow the indication. It may take 15-20 seconds, but the printers, whether they are USB or Network, should be detected. In some cases, the drivers are not readily available in the particular version of your Linux shell but are available on the manufacturer’s site. Just find them and follow the instructions.<br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file, you install it using GDebi. In your Thunar file manager, go to the application .deb file that should normally be in the Download folder, right click on it and select Open with GDebi package manager. Follow the instructions.<br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=607Installing/New To Linux2016-02-17T17:51:09Z<p>Didfem: /* Keyboard [TO BE EDITED AFTER MORE TESTING] */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
=== Keyboard ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard.<br />
<br />
==== Capital Lock Key ====<br />
You may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key.<br />
<br />
To get your Capital Lock back, you have to modify a file and create another one. <br />
<br />
Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
<br />
==== Chromebook Special Keys ====<br />
Once you have confirmed that your Capital Lock is working, go the GalliumOS Menu (Icon in the left hand corner of the Taskbar) and go to Settings, then to Settings Manager. In the Settings window, click on Keyboard (under Hardware). Select the tab Layout. Under "Keyboard model", select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Once Touchpad Indicator is installed, you may need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray"; however, it may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. In Actions, select the option to deactivate the touchpad when a mouse is plugged in and make sure Activate the touchpad when leaving is selected. In General options, select Automatic start. With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, you will find Printers. Select Add Printer and follow the indication. It may take 15-20 seconds, but the printers, whether they are USB or Network, should be detected. In some cases, the drivers are not readily available in the particular version of your Linux shell but are available on the manufacturer’s site. Just find them and follow the instructions.<br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file, you install it using GDebi. In your Thunar file manager, go to the application .deb file that should normally be in the Download folder, right click on it and select Open with GDebi package manager. Follow the instructions.<br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=606Installing/New To Linux2016-02-17T16:40:37Z<p>Didfem: /* Access the “shell” and flash the firmware */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [https://wiki.galliumos.org/Installing/Preparing Preparing/Installing] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
=== Keyboard [TO BE EDITED AFTER MORE TESTING] ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard. If you click on the icon in the bottom left corner, you get to your GalliumOS menu. Now go to Settings [TO BE EDITED]<br />
<br />
Regarding the keyboard, you may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key. <br />
<br />
To get your Capital Lock back, you have to create a file and modify another one. Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
Once you have confirmed that your Capital Lock is working, go to Setting, Keyboard, Setup and, in Keyboard Model, select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Once Touchpad Indicator is installed, you may need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray"; however, it may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. In Actions, select the option to deactivate the touchpad when a mouse is plugged in and make sure Activate the touchpad when leaving is selected. In General options, select Automatic start. With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, you will find Printers. Select Add Printer and follow the indication. It may take 15-20 seconds, but the printers, whether they are USB or Network, should be detected. In some cases, the drivers are not readily available in the particular version of your Linux shell but are available on the manufacturer’s site. Just find them and follow the instructions.<br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file, you install it using GDebi. In your Thunar file manager, go to the application .deb file that should normally be in the Download folder, right click on it and select Open with GDebi package manager. Follow the instructions.<br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=605Installing/New To Linux2016-02-17T16:33:27Z<p>Didfem: /* Get into Developer Mode */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. When it's done, it reboots and you get the scary message again. Since you don't want to stare at it for 30 seconds, just press "ctrl+D" to get to your familiar ChromeOS Welcome screen. <br />
<br />
In Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering ctrl+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter. From now on, follow the [[GalliumOS Installing/Preparing]] tutorial for your appropriate CPU architecture from the line where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
=== Keyboard [TO BE EDITED AFTER MORE TESTING] ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard. If you click on the icon in the bottom left corner, you get to your GalliumOS menu. Now go to Settings [TO BE EDITED]<br />
<br />
Regarding the keyboard, you may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key. <br />
<br />
To get your Capital Lock back, you have to create a file and modify another one. Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
Once you have confirmed that your Capital Lock is working, go to Setting, Keyboard, Setup and, in Keyboard Model, select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Once Touchpad Indicator is installed, you may need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray"; however, it may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. In Actions, select the option to deactivate the touchpad when a mouse is plugged in and make sure Activate the touchpad when leaving is selected. In General options, select Automatic start. With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, you will find Printers. Select Add Printer and follow the indication. It may take 15-20 seconds, but the printers, whether they are USB or Network, should be detected. In some cases, the drivers are not readily available in the particular version of your Linux shell but are available on the manufacturer’s site. Just find them and follow the instructions.<br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file, you install it using GDebi. In your Thunar file manager, go to the application .deb file that should normally be in the Download folder, right click on it and select Open with GDebi package manager. Follow the instructions.<br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=604Installing/New To Linux2016-02-17T16:14:40Z<p>Didfem: /* Get into Developer Mode */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. As indicated in the Tutorial, you need to hold the "esc" (escape) and Refresh key and start your Chromebook to begin the process of getting into Developer mode. The first page you see is the "scary one": "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Once your heartbeat is back to normal after having read this ominous warning, you can quietly read what else is written on this page. You notice on the last line, at the bottom of the page, the Chromeboook Model number. If you haven't written it down yet, as you should have, you get another chance to do it. (Got the message?). Now press "ctrl+D" (the letter "D" for "developer"). You get to another (less) scary white page which, again, shows the Model number. (Did I tell you this number is important?). But it also states that "To turn OS verification OFF, press ENTER." As it's written, "Your system will reboot and local data will be cleared". Go ahead, but it's your last chance to save your birthday photos on your Chromebook SSD! If you are not sure, press ESC. <br />
<br />
From now on, you let your computer do its thing. It first reboots and shows a big red exclamation mark. After 30 seconds, the Chromebook beeps twice and reboots, then you have another chance to change your mind and, after 30 seconds, it restarts again and prepares the system for Developer Mode. <br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
Once you are in Developer Mode, your Chromebook still works normally. The only difference is a white window that is displayed for 30 seconds upon restart and that you can bypass by entering CTRL+D. After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter, just as indicated in the [[GalliumOS Installing/Preparing]] tutorial. From now on, follow this tutorial for your appropriate CPU architecture from where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
=== Keyboard [TO BE EDITED AFTER MORE TESTING] ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard. If you click on the icon in the bottom left corner, you get to your GalliumOS menu. Now go to Settings [TO BE EDITED]<br />
<br />
Regarding the keyboard, you may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key. <br />
<br />
To get your Capital Lock back, you have to create a file and modify another one. Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
Once you have confirmed that your Capital Lock is working, go to Setting, Keyboard, Setup and, in Keyboard Model, select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Once Touchpad Indicator is installed, you may need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray"; however, it may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. In Actions, select the option to deactivate the touchpad when a mouse is plugged in and make sure Activate the touchpad when leaving is selected. In General options, select Automatic start. With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, you will find Printers. Select Add Printer and follow the indication. It may take 15-20 seconds, but the printers, whether they are USB or Network, should be detected. In some cases, the drivers are not readily available in the particular version of your Linux shell but are available on the manufacturer’s site. Just find them and follow the instructions.<br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file, you install it using GDebi. In your Thunar file manager, go to the application .deb file that should normally be in the Download folder, right click on it and select Open with GDebi package manager. Follow the instructions.<br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/Preparing&diff=603Installing/Preparing2016-02-17T15:53:32Z<p>Didfem: /* Bay Trail */</p>
<hr />
<div>If you have already used Linux on your Chromebook in the past (Crouton does NOT count), you probably don't need to do this. This article will cover the very minimal requirements for making it work on each generation of Chromebook. This means we won't flash any firmware if we don't need to. If you want instructions for flashing firmware, see [[Firmware]]. Please note that this process can be very dangerous, so please carefully read everything and do not skip any steps. We are not responsible if you brick your Chromebook, even though we think it sucks that you did. Despite the fact that the Chromebook Pixel and 2015 Chromebook Pixel are Sandy Bridge and Broadwell respectively, you should use the Haswell process for both of them. We know this doesn't make any sense, but just trust us.<br />
<br />
<br />
== Sandy Bridge / Ivy Bridge ==<br />
<br />
With the exception of the original Chromebook Pixel, on Sandy Bridge Chromebooks, you will have to flash your firmware. Luckily, John Lewis' script makes it a very straight forward process. Unfortunately, you'll have to open up your Chromebook. Also note that after completing this process, you will no longer be able to run Chrome OS on your Chromebook, so no dualbooting for this one I'm afraid.<br />
<br />
First, you need to put the device in developer mode. You'll know if you're in developer mode because you will see the "scary white screen" before you are able to boot the computer. If you are not in developer mode, you can get there by shutting down your computer, holding Esc and Refresh (F3), then powering on the computer. You will see a screen that says "Chrome OS is missing or damaged.". Don't panic! This is normal. You need to press Ctrl-D. Your computer will reboot a few times and you will see a few prompts. Please note that this will wipe your data (similar to a powerwash) so make sure you have backed everything up first. Now that you're in developer mode, proceed to the next step.<br />
<br />
Now your Chromebook is rooted. Now, we need to flash the firmware. Unfortunately, this means you will need to open your Chromebook. You need to open your Chromebook and either bridge the jumper with a piece of tin foil, or remove the screw that governs hardware write protection. This process varies from model to model, so you should look up how to do it on the internet. We do hope to have a guide for all models here at some point, so you don't have to go searching, but it's not ready yet, so you'll have to do some googling.<br />
<br />
Once you've disabled the write protection, we can really get started. First, log into your Chromebook and make sure it's connected to the internet. Next, press Ctrl+Alt+T to open a crosh session. Now, you can open bash by simply typing<br />
<br />
<code>shell</code><br />
<br />
and hit enter. Now you should be in bash. You'll have a prompt that looks something like this.<br />
<br />
<code>chronos@localhost / $</code><br />
<br />
Now, you just need to download and run John Lewis' script. Again, make very sure you have a stable internet connection before doing this. When you're positive you're ready, run<br />
<br />
<code>cd; rm -f flash_chromebook_rom.sh; curl -L -O <nowiki>https://johnlewis.ie/flash_chromebook_rom.sh</nowiki>; sudo -E bash flash_chromebook_rom.sh</code><br />
<br />
and follow the onscreen prompts carefully. Hopefully, if everything went well, you should be good to go. Reboot your computer, plug in your GalliumOS USB, and start installing! Note that after completing this process your computer will be unable to boot. You must insert a USB drive with an operating system on it (hopefully GalliumOS :P) and install it to the hard drive.<br />
<br />
<br />
== Haswell ==<br />
<br />
Haswell Chromebooks are mostly incredibly easy to work with. There is no additional firmware needed. You just need to enable developer mode, enable a couple boot flags, and you're good to go!<br />
<br />
First, you need to put the device in developer mode. You'll know if you're in developer mode because you will see the "scary white screen" before you are able to boot the computer. If you are not in developer mode, you can get there by shutting down your computer, holding Esc and Refresh (F3), then powering on the computer. You will see a screen that says "Chrome OS is missing or damaged.". Don't panic! This is normal. You need to press Ctrl-D. Your computer will reboot a few times and you will see a few prompts. Please note that this will wipe your data (similar to a powerwash) so make sure you have backed everything up first. Now that you're in developer mode, proceed to the next step.<br />
<br />
Now your Chromebook is rooted. Now you need to enable a couple boot flags, and you're good to go. Log into your Chromebook and connect it to the internet. Press Ctrl+Alt+T to open a crosh session. Now, you can open bash by simply typing<br />
<br />
<code>shell</code><br />
<br />
and hit enter. Now you should be in bash. You'll have a prompt that looks something like this.<br />
<br />
<code>chronos@localhost / $</code><br />
<br />
Now, you just need to enable a couple boot flags. You can skip this step if you plan on using chrx to dualboot GalliumOS with ChromeOS.<br />
<br />
<code>sudo crossystem dev_boot_usb=1 dev_boot_legacy=1</code><br />
<br />
If everything went smoothly, you should be ready to go. Just reboot your computer, pop in your GalliumOS USB, press Ctrl+L at the scary white screen, and install away! If you want to remove the scary white screen, or boot to Linux by default, see flashing [[Firmware]].<br />
<br />
<br />
== Broadwell ==<br />
<br />
With the exception of the 2015 Chromebook Pixel, Broadwell is the same basic process as Haswell, but it doesn't come with SeaBIOS, so we'll have to install it before we can use it. Luckily, we don't have to open up the Chromebook, and the process is very simple.<br />
<br />
First, you need to put the device in developer mode. You'll know if you're in developer mode because you will see the "scary white screen" before you are able to boot the computer. If you are not in developer mode, you can get there by shutting down your computer, holding Esc and Refresh (F3), then powering on the computer. You will see a screen that says "Chrome OS is missing or damaged.". Don't panic! This is normal. You need to press Ctrl-D. Your computer will reboot a few times and you will see a few prompts. Please note that this will wipe your data (similar to a powerwash) so make sure you have backed everything up first. Now that you're in developer mode, proceed to the next step.<br />
<br />
Now your Chromebook is rooted. Now you need to enable a couple boot flags, and you're good to go. Log into your Chromebook and connect it to the internet. Press Ctrl+Alt+T to open a crosh session. Now, you can open bash by simply typing<br />
<br />
<code>shell</code><br />
<br />
and hit enter. Now you should be in bash. You'll have a prompt that looks something like this.<br />
<br />
<code>chronos@localhost / $</code><br />
<br />
Now, you need to download and run John Lewis' script. Again, make very sure you have a stable internet connection before doing this. When you're positive you're ready, run<br />
<br />
<code>cd; rm -f flash_chromebook_rom.sh; curl -L -O <nowiki>https://johnlewis.ie/flash_chromebook_rom.sh</nowiki>; sudo -E bash flash_chromebook_rom.sh</code><br />
<br />
and follow the onscreen prompts carefully. If everything went smoothly, you're almost ready to go. Now, you just need to enable a couple boot flags. You can skip this step if you're planning to use chrx to dualboot GalliumOS with ChromeOS.<br />
<br />
<code>sudo crossystem dev_boot_usb=1 dev_boot_legacy=1</code><br />
<br />
If everything went smoothly, you should be ready to go. Just reboot your computer, pop in your GalliumOS USB, press Ctrl+L at the scary white screen, and install away! Unfortunately, there is no way to remove the scary white screen on Broadwell (yet!), but you can set it up to boot Linux by default. For more information, see [[Firmware]]<br />
<br />
<br />
== Bay Trail ==<br />
<br />
On Bay Trail Chromebooks, you will have to flash your firmware. Luckily, John Lewis' script makes it a very straight forward process. Unfortuantely, you'll have to open up your Chromebook. Also note that after completing this process, you will no longer be able to run Chrome OS on your Chromebook, so no dualbooting for this one I'm afraid.<br />
<br />
First, you need to put the device in developer mode. You'll know if you're in developer mode because you will see the "scary white screen" before you are able to boot the computer. If you are not in developer mode, you can get there by shutting down your computer, holding Esc and Refresh (F3), then powering on the computer. You will see a screen that says "Chrome OS is missing or damaged.". Don't panic! This is normal. You need to press Ctrl-D. Your computer will reboot a few times and you will see a few prompts. Please note that this will wipe your data (similar to a powerwash) so make sure you have backed everything up first. Now that you're in developer mode, proceed to the next step.<br />
<br />
Now your Chromebook is rooted. Now, we need to flash the firmware. Unfortunately, this means you will need to open your Chromebook. You need to open your Chromebook and either bridge the jumper with a piece of tin foil, or remove the screw that governs hardware write protection. This process varies from model to model, so you should look up how to do it on the internet. We do hope to have a guide for all models here at some point, so you don't have to go searching, but it's not ready yet, so you'll have to do some googling. Also note that this process is very complicated on the Toshiba Chromebook 2 (2014 version) because of Toshiba's poor design.<br />
<br />
Once you've disabled the write protection, we can really get started. First, log into your Chromebook and make sure it's connected to the internet. Next, press Ctrl+Alt+T to open a crosh session. Now, you can open bash by simply typing<br />
<br />
<code>shell</code><br />
<br />
and hit enter. Now you should be in bash. You'll have a prompt that looks something like this.<br />
<br />
<code>chronos@localhost / $</code><br />
<br />
Now, you just need to download and run John Lewis' script. Again, make very sure you have a stable internet connection before doing this. When you're positive you're ready, run<br />
<br />
<code>cd; rm -f flash_chromebook_rom.sh; curl -L -O <nowiki>https://johnlewis.ie/flash_chromebook_rom.sh</nowiki>; sudo -E bash flash_chromebook_rom.sh</code><br />
<br />
and follow the onscreen prompts carefully. Hopefully, if everything went well, you should be good to go. Reboot your computer, plug in your GalliumOS USB, and start installing! Note that after completing this process your computer will be unable to boot. You must insert a USB drive with an operating system on it (hopefully GalliumOS :P) and install it to the hard drive.<br />
<br />
<br />
== Braswell ==<br />
<br />
We know nothing about Braswell yet. We'll let you know as soon as we have information about running GalliumOS on Braswell.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=595Installing/New To Linux2016-02-17T02:24:39Z<p>Didfem: </p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. <br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
Once you are in Developer Mode, your Chromebook still works normally. The only difference is a white window that displays for 30 seconds when you start and that you can bypass by entering CTRL+D. (“D” for Developer). After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter, just as indicated in the [[GalliumOS Installing/Preparing]] tutorial. From now on, follow this tutorial for your appropriate CPU architecture from where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
=== Keyboard [TO BE EDITED AFTER MORE TESTING] ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard. If you click on the icon in the bottom left corner, you get to your GalliumOS menu. Now go to Settings [TO BE EDITED]<br />
<br />
Regarding the keyboard, you may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key. <br />
<br />
To get your Capital Lock back, you have to create a file and modify another one. Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
Once you have confirmed that your Capital Lock is working, go to Setting, Keyboard, Setup and, in Keyboard Model, select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Once Touchpad Indicator is installed, you may need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray"; however, it may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. In Actions, select the option to deactivate the touchpad when a mouse is plugged in and make sure Activate the touchpad when leaving is selected. In General options, select Automatic start. With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, you will find Printers. Select Add Printer and follow the indication. It may take 15-20 seconds, but the printers, whether they are USB or Network, should be detected. In some cases, the drivers are not readily available in the particular version of your Linux shell but are available on the manufacturer’s site. Just find them and follow the instructions.<br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file, you install it using GDebi. In your Thunar file manager, go to the application .deb file that should normally be in the Download folder, right click on it and select Open with GDebi package manager. Follow the instructions.<br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfemhttps://wiki.galliumos.org/index.php?title=Installing/New_To_Linux&diff=594Installing/New To Linux2016-02-17T02:17:00Z<p>Didfem: /* File Transfer on Private Network */</p>
<hr />
<div>= Tutorial: How to install GalliumOS on a Chromebook =<br />
<br />
== Objective of this Tutorial ==<br />
This Tutorial is aimed at people with limited or zero computer programming experience who wish to install Linux GalliumOS on their Chromebook. It is a step-by-step recipe that requires no knowledge in computer programming. Its scope is limited in that it doesn't intend to show you how to install any Linux distribution but only GalliumOS. Furthermore, the user should not attempt to install GalliumOS on a Chromebook that IS NOT on the GalliumOS Hardware Compatibility List. (See below in "Things to check first"). <br />
<br />
GalliumOS is one of the numerous Linux "distributions". A Linux distribution is a set of software packages with an installation program that allows the user not only to access his or her computer with Linux Operating System (OS) but also to complete most of the tasks that an average user is expected to do with computers (word, presentation and spreadsheet processing, audio and video playing and editing, Internet browsing, e-mailing, etc.). In that respect, it differs from "commercial" operating systems that don't provide much besides access to the computer system. Linux is the most advanced operating system in the world: as of November 2015, 494 or 98.8% of the 500 world's fastest supercomputers use the Linux kernel. (See [[wikipedia:TOP500|https://en.wikipedia.org/wiki/TOP500]])<br />
<br />
GalliumOS is different from other Linux distributions in that it is designed for Chromebooks. But then, why would you want Linux on your Chromebook?<br />
<br />
== Why Install Linux on a Chromebook ==<br />
Chromebooks are lean and mean computing machines that are designed to work in conjunction with the Internet. A Chromebook "keeps" hardly any software on its internal drive; what the user needs to complete a task is downloaded from Internet - often for a price - and is not kept inside the computer when the task is done. This is why most Chromebooks are equipped with a very small solid-state drive (SSD), typically 16 or 32 gigabits (Gb). Often, this SSD is not upgradable and most of the time, the random-acess memory (RAM) is not upgradable either: Chromebooks' SSD and RAM are frequently hard-wired to the motherboard. With Linux installed on a Chromebook, applications stay inside the computer and can be accessed any time, with or without Internet. <br />
<br />
The often talked about constraint about installing Linux on a Chromebook is the SSD size. This SHOULD NOT be a deterrent when installing Linux. 16GB is plenty to install GalliumOS; all your music, photos, videos and other paraphernalia that don’t fit on the static drive can go to an external drive. On all Chromebooks, you have the luxury of at least three ports: two USB and one SD. Without spending much, you could have at any given time 768 Gb of memory on your Chromebook with three 256 Gb external drives! Even a Thunderbird mail profile, for instance, can sit on an external drive without any significant speed penalty. All your Linux OS and programs can sit nicely on the 16 Gb internal drive with room to spare. <br />
<br />
Furthermore, quite a few Chromebooks now can be upgraded with a larger capacity static drive. For a little investment, you could end up with a powerful laptop for a fraction of the price that you would normally pay for something other than a Chromebook.<br />
<br />
== Things to check first ==<br />
You probably don’t want to venture into uncharted territory, so you need to do a few checks before you start converting your Chromebook computer to a GalliumOS Linux machine. There are many benefits with using Linux, notably the ability to run thousands of excellent applications without ever accessing the Net, but you have to be reasonably certain that your Chromebook will allow you to do that. The first place to find out whether your Chromebook is supported for a GalliumOS install is: https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
Here are a few explanations about this table:<br />
<br />
'''<u>Model</u>''': The basic idea is that it is not advisable to attempt a GalliumOS install unless your Chromebook Model is listed in this table.<br />
<br />
'''<u>Hardware ID</u>''': The Hardware ID is something that you will read in your Chromebook when you create a Recovery Media for your specific model (see below). This is valuable information; '''write it down!'''<br />
<br />
'''<u>Processor Name</u>''': The Processor name (Sandy/Ivy Bridge, Bay Trail, Haswell, Broadwell, etc.) is something else you will need when you select the GalliumOS version you have to download. See: https://galliumos.org/download.html<br />
<br />
'''<u>Firmware</u>''': That is one of the crucial changes that may, or may not, be required to make your Chromebook a GalliumOS Linux machine. The firmware modification requirement is indicated in the column titled “…with custom firmware?”. Fortunately, this firmware change is a fairly straightforward operation thanks to the work of John Lewis. Basically, it boils down to opening a terminal page in Chrome on your Chromebook (we will get to that) and writing, or copying and pasting, a short script. <br />
<br />
('''NOTE''': Although there is still the possibility to dual-boot (GalliumOS and ChromeOS), this is not discussed here as it is assumed that the user has a limited, small static drive on which space doesn’t really allow two Operating Systems. In this tutorial, we will dedicate the entire drive space to Linux.)<br />
<br />
I '''<u>strongly suggest</u>''' that you '''<u>note</u>''' all the data regarding the Model name, Hardware ID, Processor Name and Firmware modification requirement specific to your Chromebook. You will need it later. <br />
<br />
Now that you have determined that you can give yourself the go-ahead for a GalliumOS installation on your Chromebook, let’s do first a little bit of house-cleaning and preparation.<br />
<br />
== Backup ==<br />
You may have a few files on your Chromebook drive that you wish to keep. You should transfer all those files onto an USB flash drive or an SD drive. Remember that everything on your drive is going to be wiped out when you install GalliumOS Linux.<br />
<br />
== Chromebook Recovery Media ==<br />
You need to create a Chromebook Recovery Media in case, further down the road, you wish to return your Chromebook to its original state. (See at the end of this Tutorial "Back to ChromeOS<ref name=":0">[[Back]] to ChromeOS</ref>".) To do that, you need to download the Chromebook Recovery Utility from the Google Web Store (it is in your ChromeOS Menu). Once downloaded, the Recovery icon will also be in your ChromeOS Menu. <br />
<br />
This software allows you to create a recovery media for your Chromebook. You need a 4GB USB flash drive or SD card that does not contain data that you want to keep because this drive too is going to be totally erased to receive the recovery data. <br />
<br />
Once the Recovery icon is in your Chromebook Launcher, click on it to start the Recovery Media creation process. Go past the first page by clicking on "Get started" to access the next page titled “Identify your Chromebook”. This page contains '''important information''' regarding your specific Chromebook model number. <br />
<br />
There is a line that states: “For this Chromebook, enter XYZ XXX-XXX-XXX-XXX”.<br />
<br />
'''<u>Write down</u>''' the MODEL NUMBER for YOUR Chromebook. It could be something like:<br />
<br />
GNAWTY C2C-E3N-A2M<br />
<br />
YUNA D21-A3B-L4A-A35<br />
<br />
YUNA D25-B3B-B4A-A4M, etc.<br />
<br />
Everything is important in this number, so keep it in a safe place; add it to the other info you already wrote down (Model, Hardware ID, Processor, firmware required, etc.). The first word could be something like: BANJO, CANDY, FALCO, GNAWTY, MONROE, PARROT, YUNA, etc. You notice that this first word is the Hardware ID that you have seen on the “GalliumOS Support by Model” table, that we have already talked about and is displayed at:<br />
<br />
https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
You need the whole number, not just the first word, to create a recovery utility; you also need the name if you ever need a “shellball” to bring your Chromebook back to its original state. We’ll get back to that, but for now, make sure you have this whole number kept somewhere.<br />
<br />
In the "Identify your Chromebook" page of the Recovery Utility, the number we just talked about extensively is already written in blue in the Recovery window; just click on it and it will print automagically in the window below. But if you were to create a recovery utility for ANOTHER Chromebook, this is the window where you would enter the specific model number as outlined above. Since Google is nice to you, you could also select the Chromebook from a list that you call up by clicking on “Select a model from a list”. It is safer however to use the model number.<br />
<br />
Click on Continue to proceed with the actual Media creation. Just follow the instructions.<br />
<br />
== Create your GalliumOS USB or SD installation drive ==<br />
The Operating System you want to install, GalliumOS, must be available to you on a “bootable” USB or SD drive that you need to create. You therefore proceed to https://galliumos.org/download where you download the GalliumOS version appropriate to your Chromebook architecture (Haswell, Broadwell, Bay Trail, etc.). These are the Processor names that are displayed in the Hardware Compatibility List; you should have the name specific to your Chromebook available, if you wrote it down as was suggested earlier. <br />
<br />
This GalliumOS installation file you download is an .iso file. The beauty of a file of this type is that you have on a single file all the bits and pieces required to install a Linux operating system with everything you need on a computer. Once this file has been downloaded, however, it needs to be decompressed and put on an USB flash or SD drive. To do that, it is recommended you use an application called Unetbootin that is available for Linux, Windows and Mac. It can be downloaded at:<br />
<br />
http://unetbootin.github.io/<br />
<br />
Once Unetbootin is installed on your computer, you plug in an USB or SD drive and follow the indications in Unetbootin. It is recommended you use a 4GB USB drive. It has been found that Chromebooks may not boot with large capacity USB drives. Also, an USB 3 drive may also not be willing to boot. Do it cheap and simple!<br />
<br />
Now, you should have two drives (USB or SB) to keep: one with your Chromebook Recovery Media; one with GalliumOS. Make sure you label them properly and don’t misplace or erase them.<br />
<br />
== Prepare the Chromebook ==<br />
=== Select the procedure according to your Chromebook architecture ===<br />
For this step, please see https://wiki.galliumos.org/Installing/Preparing This Wiki page explains how a Chromebook has to be prepared for installation according to the architecture of its processor (CPU). You notice that the architecture names (Sandy Bridge, Haswell, Broadwell, etc.) for which a specific installation is described are the same as the Processor names we already saw at https://wiki.galliumos.org/Hardware_Compatibility<br />
<br />
If you followed our indications so far, your Chromebook architecture should have be noted somewhere.<br />
<br />
For every architecture, the GalliumOS Installing/Preparing tutorial refers to SeaBIOS firmware. BIOS stands for Basic Input/Output System. It is a tiny – but very important – program (firmware) that tells your computer, among other things, where to look to find an operating system that will make it go. A special type of BIOS called SeaBIOS is required to install Linux on a Chromebook. Chromebooks with Haswell CPU architecture come with SeaBIOS already installed and you normally shouldn't have to worry about it. However, some bugs are reported in the SeaBIOS preinstalled on Haswell Chromebooks. (See https://wiki.galliumos.org/Firmware) It may therefore be advisable to install another version of the SeaBIOS on these machines. If you need to “flash” (replace) the BIOS firmware on your machine, you follow the procedure indicated in the [[Installing/Preparing tutorial]]. This is a delicate operation that you don't want to botch up as you may "brick" your Chromebook. ("Bricking" means that you make your computer worth no more than a brick of the same weight!) Luckily, John Lewis’ scripts to flash Chromebook BIOS makes it very easy. Before we get there, however, you need to put your Chromebook in developer mode.<br />
<br />
=== Get into Developer Mode ===<br />
The process to put the device in developer mode is very well described in the [https://wiki.galliumos.org/Installing/Preparing GalliumOS Installing/Preparing] Tutorial. Just in case you are looking for the Refresh key, it is the 4th one from the top left; it shows a clockwise arrow. <br />
<br />
It takes about 15 minutes to put your Chromebook into Developer Mode. Once you are in Developer Mode, your Chromebook is “rooted”; it means that you have access to the “root” of the computer system. It also means you have to tread carefully… Note that some older Chromebooks have a physical switch that you'll have to flip in order to turn on Developer Mode. If you aren't sure, look up instructions for your specific device on enabling Developer Mode.<br />
<br />
Once you are in Developer Mode, your Chromebook still works normally. The only difference is a white window that displays for 30 seconds when you start and that you can bypass by entering CTRL+D. (“D” for Developer). After you are in Developer mode, it is suggested you configure your Internet access normally and enter your Gmail name and password, just to reassure you that your Chromebook is still alive and well. Also, for the continuation of the operation, you will need Internet access.<br />
<br />
=== Remove the Write Protection, if required ===<br />
The BIOS is write-protected through physical and software means. If you have a Sandy Bridge / Ivy Bridge or a Bay Trail Chromebook, you will have to remove the physical write protection. To do that, you have to open the computer and, generally, remove a screw. You will find the information on how to do that through a quick search in Google. <br />
<br />
=== Access the “shell” and flash the firmware ===<br />
Let’s assume now that you have restarted your Chromebook in Developer mode, entered your password and accessed the Chrome browser in your Chromebook. The next step is to open a Terminal window. This will take you to the heart of your computer. The Terminal is the screen that allows you to talk to the innards of your machine through commands and scripts. (Just like you see in the movies when the hacker is about to steal government secrets!) You can do all that in a Chromebook. (Not steal government secrets, but access a terminal window!) You just have to press CTRL+ALT+T. (Kind of an anticlimax, isn’t it?)<br />
<br />
In this black terminal screen, at the prompt, you type: “shell” (without quotation marks) and hit Enter, just as indicated in the [[GalliumOS Installing/Preparing]] tutorial. From now on, follow this tutorial for your appropriate CPU architecture from where it is stated:<br />
<br />
“and hit enter. Now you should be in bash. You’ll have a prompt that looks something like this.”<br />
<br />
('''NOTE''': If your Chromebook has a Haswell architecture but you prefer to flash the BIOS, follow the procedure outlined for the Broadwell architecture.)<br />
<br />
Follow John Lewis’ script carefully. I recommend that you cut and paste it into the terminal. Remember that the Terminal is just another tab in the Chrome browser; you can access any other Internet site in other tabs and flip through tabs to Cut and Paste whatever you want from one page to another page.<br />
<br />
After John Lewis’ script has been run, you continue with the GalliumOS Installing/Preparing Tutorial with a little caveat. Where it states: “Reboot your computer, plug in your GalliumOS USB and start installing!”, it should be the other way round. You must first plug in your GalliumOS USB drive, then reboot your computer.<br />
<br />
== Install GalliumOS ==<br />
When the Chromebook starts, a blue Unetbootin page comes up. It shows three options and states that you edit options with the Tab key. Actually, you don’t want to edit options at this stage; you only want to select one of them. You change selections with the Arrow keys and press Enter to select. I suggest you select the second one, “Gallium Live Image and Installer”.<br />
<br />
In a few seconds, you get a beautiful display of a glass skyscraper shot from below. You also have a fully functional Operating System at your disposal but your SSD is untouched because this is a “Live USB” (or "Live SD"): you totally bypass your SDD drive to talk to your computer. You can configure your WiFi and browse the Net. You can open AbiWord text processor and write your biography. But this is not what you want right now: you want to install GalliumOS. Fortunately, at the top right of the screen, there is an icon that states – Would you believe? – Install GalliumOS. Just double-click on it and follow the instructions.<br />
<br />
When it comes to the page titled “Preparing to install GalliumOS, a Warning pop-up windows may come up to inform you of an error. You can safely ignore. You then come up to the Installation type window. The choice here is easy: select the first option, “Erase disk and install GalliumOS”. The installation may take 15-20 minutes. Relax and let GalliumOS do its thing. <br />
<br />
== GalliumOS is installed! ==<br />
Now you have removed your GalliumOS installation USB drive and restarted your computer. The first thing you see is “Press ESC for boot menu.” You press ESC and the screen shows “Select boot device:” and a choice of devices. If there is no USB flash or SD drive plugged into your computer, you have only choice # 1, that is the computer SSD. If more than one device is displayed, select the one you know is your SSD. The type and the size should help you determine which the right one is. And if you make a mistake, no big deal: you just won’t start GalliumOS.<br />
<br />
Once GalliumOS is opened, you will want to test the applications that come with it. You can also add other applications: you have tens of thousands applications to choose from! If you want to add applications, open Synaptic Package Manager that you will find in the Menu under System.<br />
<br />
=== Keyboard [TO BE EDITED AFTER MORE TESTING] ===<br />
GalliumOS is a fantastic Linux distribution tailored to Chromebooks. So, of course, the first thing to check is the keyboard because, as you know, the Chromebook keyboard is not standard. If you click on the icon in the bottom left corner, you get to your GalliumOS menu. Now go to Settings [TO BE EDITED]<br />
<br />
Regarding the keyboard, you may be from the "old school" like me and prefer to use the Chromebook Search key as a "Normal" Capital Lock key. <br />
<br />
To get your Capital Lock back, you have to create a file and modify another one. Besides being useful, this procedure will show you how easy it is to change things in Linux.<br />
* Open Thunar File Manager. Under View, select "Show Hidden Files". Files that you were not aware of now show up in your Home folder.<br />
* One of the file is ".bashrc". Notice the dot (.) before the file name. This dot is what causes this file to be hidden. Simple, isn't it?<br />
* Right click on .bashrc and select "Open with Mousepad".<br />
* When .bashrc is open in Mousepad, cut and paste the following lines at the bottom of the file and Save.<br />
if [-s ~/.Xmodmap]; then<br />
<br />
xmodmap ~/.Xmodmap <br />
<br />
fi<br />
* Still in Mousepad, go to File and click on New.<br />
* In this new document, just enter: <br />
keycode 133 = Caps_Lock<br />
* Save this file in your Home folder as .Xmodmap (Don't forget the "dot" before the file name!).<br />
* Close Mousepad and Log out of your session and back in. Your Capital Lock key should now work "normally".<br />
Once you have confirmed that your Capital Lock is working, go to Setting, Keyboard, Setup and, in Keyboard Model, select: "Chromebook | No overlay | F keys mapped to media keys". You now have a standard Chromebook keyboard with the exception of the Search key that is now a normal Caps Lock. You can use the special function keys normally (Full Screen, Brightness, Volume, etc.). <br />
<br />
You can also use the Keyboard Model window to select an external keyboard you wish to use if you plug one in. If you don't find the exact keyboard model in the list, you may use one close enough (same manufacturer, similar performance, etc.). You can try and see until you find a model that fits your needs. You can always use your mouse to change your selection if your external keyboard has a strange behavior.<br />
<br />
=== Mouse and Touchpad ===<br />
You may also prefer to use a mouse because the touchpad may feel awkward to use for you and interferes with your typing. Many people prefer having the touchpad deactivated when they type. There is a simple solution called: Touchpad Indicator. To install this application, go to:<br />
<br />
http://tipsonubuntu.com/2014/05/26/install-touchpad-indicator-ubuntu-14-04/<br />
<br />
Once Touchpad Indicator is installed, you may need to reboot the computer for the Touchpad-indicator to work. In the Menu, the application is under Accessories; click on it to start. It will put an icon in the right of the taskbar, in an area generally called the "tray"; however, it may not be visible, depending on the Desktop theme you have selected. If you see what looks like an empty spot in the tray, it may well be the Touchpad indicator icon. Click on it and select Preferences. First go to Theme and select the icon on the right; the Touchpad-indicator icon should now be visible in the tray. In Actions, select the option to deactivate the touchpad when a mouse is plugged in and make sure Activate the touchpad when leaving is selected. In General options, select Automatic start. With this configuration, the touchpad will be ON when you start the computer without a mouse and OFF when a mouse is plugged in.<br />
<br />
=== Printers ===<br />
Your printers may have been detected by Linux and configured. In the GalliumOS Menu, under System, you will find Printers. Select Add Printer and follow the indication. It may take 15-20 seconds, but the printers, whether they are USB or Network, should be detected. In some cases, the drivers are not readily available in the particular version of your Linux shell but are available on the manufacturer’s site. Just find them and follow the instructions.<br />
<br />
If you have downloaded a printer driver, or any other software for that matter, as a .deb file, you install it using GDebi. In your Thunar file manager, go to the application .deb file that should normally be in the Download folder, right click on it and select Open with GDebi package manager. Follow the instructions.<br />
<br />
=== File Transfer on Private Network ===<br />
If you want to transfer files between computers on your own private network, through your own router, the easiest way is to install Nautilus file manager. In Nautilus, you just right click on the folder you want to share and select Share on local network.<br />
<br />
== Back to ChromeOS ==<br />
You may wish to return your Chromebook to its original state; in other words, you want to run it under ChromeOS instead of GalliumOS. This is also a fairly simple operation as long as you follow the procedure. <br />
<br />
If you flashed the original Chromebook BIOS to install GalliumOS, you have to flash again the BIOS to bring it back to original. Remember that even if you have a Haswell CPU, you may have chosen to install initially John Lewis' SeaBIOS.<br />
<br />
=== Download the appropriate shellball ===<br />
The first thing to do is to download a "shellball", that is a folder that contains a bunch of files specific to your particular Chromebook to bring it back to original. You find the shellballs at:<br />
<br />
https://johnlewis.ie/Chromebook-ROMs/shellballs<br />
<br />
When you get to that page, you see an Index listing names one of which should be familiar to you: it is your Hardware ID that was displayed in the [[Hardware Compatibility List]] that we referred to at the beginning of this tutorial. You may wish to go back to that list, just to be sure.<br />
<br />
Open Thunar and go to your Home page. In there, create a folder named "shellball". Download into that folder all the files under the appropriate shellball name that you found in the [[shellballs list]]. <br />
<br />
=== Get John Lewis' flashrom utility ===<br />
Next, go to https://johnlewis.ie/Chromebook-ROMs/utils/<br />
<br />
In the list, right click on "flashrom" and click on "Save Target As ...". Save this file in your Home folder.<br />
<br />
In Thunar, go to your Home folder, right click on this downloaded "flashrom" file and Rename it "flashrom.sh"<br />
<br />
Open a Terminal window. (XFCE Terminal is in your Panel and your Menu.) The Terminal normally opens in your Home folder. (The prompt should show [YOUR_COMPUTER_NAME]:~$)<br />
<br />
You are now going to make "flashrom.sh" executable. To do so, at the prompt, type:<br />
<br />
chmod +x flashrom.sh<br />
<br />
While you are in the terminal, change to the shellball folder. To do so, at the prompt, type:<br />
<br />
cd shellball<br />
<br />
=== Enter the required commands ===<br />
Still in the terminal, you now have to type the commands below. You may Cut and Paste, EXCEPT the "hwid" which is specific to your Chromebook. <br />
<br />
'''<u>NOTE:</u>''' <br />
* When you type the commands, ensure that you have two dashes before « set » and « hwid » and not an M-dash (a single long dash). Text editors have a mind of their own and sometimes replace two consecutive dashes by a single M-dash. <br />
* Replace the Hardware ID (hwid) number (ABCXYX X1X-Y2Y-Z3Z) by the one specific to your Chromebook and that you should have kept. Mine is GNAWTY C2C-E3N-A2M; yours is probably different. <br />
* If a command does not work, i.e. you get a message like “Command cannot be found” it is quite likely that you missed a dot (.) or a slash (/) at the beginning of the command line. <br />
The commands are:<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin<br />
<br />
./gbb_utility --set --hwid=ABCXYX X1X-Y2Y-Z3Z bios.bin.new<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin<br />
<br />
./gbb_utility --set --flags=0x489 bios.bin.new<br />
<br />
Everytime, the system should confirm that the command was successful. <br />
<br />
Still in the terminal, return to the home folder by typing "cd" and two dots at the prompt, like so: <br />
<br />
cd ..<br />
<br />
Then, run this command:<br />
<br />
sudo ./flashrom.sh -w shellball/bios.bin<br />
<br />
=== Restart your computer ===<br />
Your Chromebook first displays a message with a red exclamation mark stating: OS verification is OFF. (PHOTO)<br />
<br />
After some beeps, another message appears: "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.(PHOTO)<br />
<br />
Insert your USB or SD Chromebook Recovery Media into the appropriate port. Follow the instructions. <br />
<br />
(Basically, just wait until the recovery is complete.) <br />
<br />
When it's done, remove the Recovery Media and the Chromebook restarts.<br />
<br />
After the restart, you get a beep, then the usual Chromebook opening page. (PHOTO)<br />
<br />
Enter all the required data to log into your Chromebook.<br />
<br />
=== Reset the "flags" and OS Verification ===<br />
You don't really have to know what these flags are. Just keep in mind that they dictate the sequence of the boot process. You need to reset them for your Chromebook to boot like new.<br />
<br />
Open a terminal with CTRL+ALT+T<br />
<br />
At the command prompt, type “shell” and press Enter.<br />
<br />
Type each of the following command, pressing Enter after each one: <br />
<br />
sudo flashrom --wp-disable<br />
<br />
sudo /usr/share/vboot/bin/set_gbb_flags.sh 0x000<br />
<br />
sudo flashrom --wp-enable<br />
<br />
Restart the computer.<br />
<br />
You get the message stating "OS verification is OFF. Press SPACE to re-enable." Press the spacebar.<br />
<br />
Your Chromebook is now - almost - back to where it was when new. <br />
<br />
To make it complete, reinstall the physical write protect device if a change on the motherboard was required to disable the BIOS write-protection.</div>Didfem