Embedded Files
On a website I read this article. Its great for installing ubuntu on this chromebook.
On a website I read this article. Its great for installing ubuntu on this chromebook.
Allthough the script to get the touchscreen working didn't work for me. The script couldn't find the needed files.
Only installing Chrubuntu is explained here
- Make sure the Chromebook is turned off
- Hold Escape and Refresh and tap the Power button
- When the device reaches the recover screen, press Ctrl+d and then (after releasing Ctrl+d) press Enter
- The system will reboot (this will take some time)
- When the system finally boots to the set up, select a wireless connection and click continue
- Accept the EULA by clicking Accept and continue
- Once you reach the Google login screen, do NOT log in
- Press Ctrl+alt+ → (not the right cursor key, but the key where the standard F2 key would be)
- At the ChromeOS command login (not the usual) GUI login, type chronos and hit Enter (no password is needed) to finally enter Developer mode.
You are now ready to begin the installation process.
Install Ubuntu using ChrUbuntu
Install Ubuntu using ChrUbuntu
You should now be at the command prompt on your Chromebook. Here, type:
curl -L -O http://goo.gl/9sgchs; sudo bash 9sgchs -u lts
Make sure you get this command exactly right. Once you've done that, you will be asked to configure a size for the Ubuntu installation. This will obviously depend upon the size of SSD on your Chromebook. The recommended size is 24 GB. After you type the size and hit enter, the device will reboot a couple of times. This process is setting up the Stateful partition to make room for ChrUbuntu. Eventually it will come back to the Chromebook setup screen. Once again, configure your network and then hit Ctrl+alt+ → at the login screen. Log back in as chronos and then type the original command again:
curl -L -O http://goo.gl/9sgchs; sudo bash 9sgchs -u lts
You need a newer Kernel if you want the touchscreen and resume after closing the lid work properly. Look here for the newest kernel. I advise to install the latest kernel, but not a release candidate (rc) You can download an install 3 corresponding .deb files or use these scripts (for a working, allthough not newest kernel)
Installing a newer kernel is explained here:
http://www.reddit.com/r/chrubuntu/comments/2dw1b2/offical_chromebook_driver_support_released/
use these commands from that page:
Official Chromebook driver support is installed this way
For 32-bit system, navigate to /tmp, download the debs and finally install them via below commands:
cd /tmp/ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/linux-headers-3.17.0-031700-generic_3.17.0-031700.201410060605_i386.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/linux-headers-3.17.0-031700_3.17.0-031700.201410060605_all.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/linux-image-3.17.0-031700-generic_3.17.0-031700.201410060605_i386.deb sudo dpkg -i linux-headers-3.17.0-*.deb linux-image-3.17.0-*.deb
For 64-bit system, run:
cd /tmp/ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/linux-headers-3.17.0-031700-generic_3.17.0-031700.201410060605_amd64.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/linux-headers-3.17.0-031700_3.17.0-031700.201410060605_all.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/linux-image-3.17.0-031700-generic_3.17.0-031700.201410060605_amd64.deb sudo dpkg -i linux-headers-3.17.0-*.deb linux-image-3.17.0-*.deb
When done, restart your computer.
The previous version I used that worked is installed this way:
For 64 bit in a terminal:
cd /tmp
sudo mkdir kernel
cd /kernel
sudo dpkg -i *.deb
sudo reboot
Caution: Modifications you make to the system are not supported by Google, may cause hardware, software or security issues and may void warranty.
An unrelated note: Holding just Refresh and poking the Power button hard-resets the machine without entering Recovery. That's occasionally useful, but use it with care - it doesn't sync the disk or shut down politely, so there's a nonzero chance of trashing the contents of your stateful partition.
Introduction
Introduction
Enabling Developer mode is the first step to tinkering with your Chromebook. With Developer mode enabled you can do things like poke around on a command shell (as root if you want), install Chromium OS, or try other OS's. Note that Developer mode turns off some security features like verified boot and disabling the shell access. If you want to browse in a safer, more secure way, leave Developer mode turned OFF. Note: Switching between Developer and Normal (non-developer) modes will remove user accounts and their associated information from your Chromebook.
Entering
Entering
On this device, both the recovery button and the dev-switch have been virtualized. Our partners don't really like physical switches - they cost money, take up space on the motherboard, and require holes in the case.
To invoke Recovery mode, you hold down the ESC and Refresh (F3) keys and poke the Power button.
To enter Dev-mode you first invoke Recovery, and at the Recovery screen press Ctrl-D (there's no prompt - you have to know to do it). It will ask you to confirm, then reboot into dev-mode.
Dev-mode works the same as always: It will show the scary boot screen and you need to press Ctrl-D or wait 30 seconds to continue booting.
USB Boot
USB Boot
By default, USB booting is disabled. Once you are in Dev-mode and have a root shell, you can run:
sudo crossystem dev_boot_usb=1and reboot once to boot from USB drives with Ctrl-U.
Legacy Boot
Legacy Boot
This device includes the SeaBIOS firmware which supports booting images directly like a legacy BIOS would. Note: the BIOS does not provide a fancy GUI for you, nor is it easy to use for beginners. You will need to manually boot/install your alternative system.
Like USB boot, support for this is disabled by default. You need to get into Dev-mode first and then run:
sudo crossystem dev_boot_legacy=1and reboot once to boot legacy images with Ctrl-L.
Leaving
Leaving
To leave Dev-mode and go back to normal mode, just follow the instructions at the scary boot screen. It will prompt you to confirm.
If you want to leave Dev-mode programmatically, you can run crossystem disable_dev_request=1; reboot from a root shell. There's no way to enter Dev-mode programmatically, and just seeing the Recovery screen isn't enough - you have to use the three-finger salute which hard-resets the machine first. That's to prevent a remote attacker from tricking your machine into dev-mode without your knowledge.
Troubleshooting
Troubleshooting
Legacy Boot Doesn't Work
Legacy Boot Doesn't Work
Sometimes it's possible to break the SeaBIOS install in the flash (sometimes doing innocuous things like tweaking the GBB flags). If you do get into such a situation:
- Check that dev_boot_legacy is set to 1 when you run crossystem
- If it isn't, then see the normal Legacy Boot section above
- if it is, then see below
You can safely reset the copy of SeaBIOS in your flash by running (as root):
# chromeos-firmwareupdate --sb_extract /tmp# flashrom -w /tmp/bios.bin -i RW_LEGACYR
R
Page updated
Google Sites
Report abuse