Archive:Chromebox: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
Line 51: Line 51:


=== Along Side ChromeOS ===
=== Along Side ChromeOS ===
The following approaches install Ubuntu+XBMC or OpenELEC along side ChromeOS, either inside ChromeOS, or on a separate partition of the internal HDD.


==== Using Crouton ====
==== Using Crouton ====
Line 59: Line 61:


==== Using ChrUbuntu ====
==== Using ChrUbuntu ====
ChrUbuntu is a shell script developed by Jay Lee to automate the re-partitioning of the internal HDD and installation of Ubuntu.


Generic instructions for installing ChrUbuntu on any ChromeOS device are available at: http://goo.gl/Zekkcl
Generic instructions for installing ChrUbuntu on any ChromeOS device are available at: http://goo.gl/Zekkcl

Revision as of 22:20, 18 April 2014

Asus Chromebox
Asus chromebox.jpg
Manufacturer Asus
Released 2014-03-14 (US)
OS Chrome OS
CPU Intel® Celeron 2955U Processor
Storage 16GB internal SSD
RAM 2 GB, Dual Channel, DDR3 at 1600MHz
Graphics Intel® HD Graphics 4000
Connectivity HDMI, Displayport, Bluetooth 4.0, USB 3.0, Wifi 802.11 a/b/g/n, 10/100/1000 Ethernet, 2 -in-1 Card Reader, Audio jack
Dimensions 4.88 x 4.88 x 1.65 inch (WxDxH)
Asus Chromebox Rear Ports
Asus Chromebox Side/Front Ports
Home icon grey.png   ▶ Devices ▶ Chromebox

The ASUS Chromebox is a small lightweight intel PC that runs Chrome OS and can be made to boot into other linux versions. It features HDMI, Displayport, USB 3 ports, gig ethernet, SD card slot, and internal wireless-n networking. This page is a collection of links, information, tips, and guides related to running XBMC on the ASUS Chromebox line of computers.

Device Preparation

Put in Developer Mode

Putting the ChromeBox in developer mode will allow you to access the underlying Linux operating system features necessary for installing XBMC.

WARNING: This will erase all user data on the device.

With the device powered off, insert a paperclip into the hole left of the SD card slot and press the recovery button. Power on the device, and remove the paper clip after 2-3 seconds. When greeted with the recovery screen, press CTRL-D to enter developer mode, and press the recovery button again to confirm. The device will reboot and wipe any existing user data.

Recoverybutton.png

Disable Firmware Write Protect

With the device powered off and unplugged:

  1. Remove (4) rubber feet from bottom of unit
  2. Remove (4) screws under rubber feet
  3. Separate two halves of unit
  4. Remove write-protect screw circled below:
    Inside-chrome1.jpg
  5. Reassemble in reverse order

Factory Reset

  1. Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en
  2. With the device powered off, use a paperclip to press the Recovery button and power on the device
  3. Insert the recovery media (USB or SD) when prompted

Installing XBMC

As ChromeOS is based on Linux, all methods of running XBMC involve another Linux distribution in some shape or form.

Along Side ChromeOS

The following approaches install Ubuntu+XBMC or OpenELEC along side ChromeOS, either inside ChromeOS, or on a separate partition of the internal HDD.

Using Crouton

Crouton stands for Chromium OS Universal Chroot Environment. It allows for the installation of Ubuntu inside of ChromeOS. Full instructions are available at: https://github.com/dnschneid/crouton

Once Crouton/Ubuntu are installed, follow the standard instructions for installing XBMC under Linux.

Using ChrUbuntu

ChrUbuntu is a shell script developed by Jay Lee to automate the re-partitioning of the internal HDD and installation of Ubuntu.

Generic instructions for installing ChrUbuntu on any ChromeOS device are available at: http://goo.gl/Zekkcl

After ChrUbuntu is installed, follow the standard instructions for installing XBMC under Linux.

Using ChrOpenELEC

ChrOpenELEC is a modification of the ChrUbuntu installation script which installs OpenELEC instead of Ubuntu.

In order to install ChrOpenELEC, your ChromeBox must be in Developer Mode and Factory Reset (see above for instructions)

  1. Power on and boot to ChromeOS
  2. Hit CTRL-ALT-F2 to get to command prompt
  3. Login with user chronos (no password required)
  4. Download and run the ChrOpenELEC script with the command:
    sudo curl -L -O http://goo.gl/WIytxU; sudo bash WIytxU
    (with an uppercase 'i' not a lowercase 'l' in WIytxU)
  5. Enter the size of the partition to be used as a whole number, from 1 to the max recommended size (9GB for a stock 16GB SSD)
    NOTE: the numeric keypad is off by default, using it will enter garbage characters that will screw up the installation script and result in a failed install.
  6. Press Enter to reboot when prompted. ChromeOS will "repair" itself and reboot.
  7. Hit CTRL-ALT-F2 to get to command prompt
  8. Login with user chronos (no password required)
  9. Download and run the ChrOpenELEC script with the command:
    sudo curl -L -O http://goo.gl/WIytxU; sudo bash WIytxU
  10. Press Enter to install when prompted. The script will download and install OpenELEC, as well as update the bootloader and legacy BIOS (SeaBIOS) if needed.
  11. Press Enter to reboot when installation complete
  12. At the developer boot screen, press CTRL-L to boot the legacy BIOS and into OpenELEC

Using Entire Disk (Internal HDD or External USB/SD)

Coming soon: ChromeBox-compatible custom OpenELEC installer

Set Boot Options

With the firmware write-protect disabled, we can shorten the default boot wait time and set the device to default to booting the legacy BIOS (and into Ubuntu or ChrOpenELEC) instead of ChromeOS.

  • Power on and boot to ChromeOS
  • Hit CTRL-ALT-F2 to get to command prompt
  • Login with user chronos (no password required)


To shorten the boot wait time only, run the command:

sudo set_gbb_flags.sh 0x1


To shorten the boot wait time and set the default boot to the legacy BIOS:

sudo set_gbb_flags.sh 0x489


To reset these options to default, use:

sudo set_gbb_flags.sh 0x0

Known issues

  • MCE remote IR receivers do not currently work with USB 3.0 ports under Linux due to a bug in the mceusb kernel driver

Random notes

Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.

Links