The step-by-step guidelines below provided by Arm for your convenience contain information about downloading and installing files, licensed by third parties, which are subject to their own licence terms and conditions. Your use of such downloads are expressly subject to those third party terms. You hereby agree to comply with all the terms and conditions imposed on you by the relevant third party terms. You acknowledge that ARM shall have no liability to you in respect of those third party files and that your use of the step-by-step guidelines is at your own risk.
This guide provides instructions to build and run a GNU/Linux distribution on the Samsung Chromebook devicears as an alternative to the Chrome OS operating system. Some experience with Linux as a programmer is expected in order to use this guide. More specifically, one should be familiar with opening and executing commands in a terminal and mounting storage devices. The supported windowing systems are fbdev (direct frame buffer access), X11 and Weston (Wayland). The instructions are written for several Chromebook variants with accompanying notes to highlight specific things for each of them.
The first prerequisite is to have one of the following devices covered by this guide:
You will then need the following extra items in order to be able to follow this guide:
This step is to prepare your host Ubuntu system to compile and install the Chromebook software. You may use an alternative Linux distribution but these instructions have been tested only with Ubuntu 14.04 and 16.04.
Run the following command to install all the required packages on the host Ubuntu system:
For Ubuntu 14.04:
sudo apt-get install build-essential curl wget git gdisk u-boot-tools sudo apt-get install device-tree-compiler libssl-dev uuid-dev liblzma-dev libyaml-dev libtspi-dev sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1-dev lib32bz2-1.0
For Ubuntu 16.04:
sudo apt-get install build-essential curl wget git gdisk u-boot-tools sudo apt-get install device-tree-compiler libssl-dev uuid-dev liblzma-dev libyaml-dev libtspi-dev sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1-dev libbz2-1.0:i386
If this is a new installation of Git, you need to configure your name and email. Otherwise, cloning the Linux kernel repository will fail. You can do this with the following commands:
git config --global user.name "Your Name" git config --global user.email "your email"
Download the attached mali_chromebook-setup_006.tar.gz set-up archive and extract it in an empty directory:
tar xzf mali_chromebook-setup_006.tar.gz cd mali_chromebook-setup_006
This archive contains a chromebook-setup.sh script, also referred to as the set-up script, to automate the process of preparing an SD card, as well as some associated data files like Linux kernel patches and configuration files for the Chromebook.
chromebook-setup.sh
The set-up script relies on several configuration options. This step is to determine which values you need to use for each of them.
The ‑‑variant option is to specify the Chromebook variant you want to use. The product code needs to be used, as previously listed in the 2. Prerequisites section. For example:
‑‑variant
--variant=XE303C12 # for Samsung Chromebook 1
You then need to determine the block device associated with your SD card and pass it to the ‑‑storage option. Insert the SD card into as SD card reader on your host computer. There should be a new block device corresponding to the SD card which you can discover by running lsblk:
‑‑storage
lsblk
$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 42G 0 disk ├─sda1 8:1 0 38G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 4G 0 part [SWAP] sdc 8:32 1 3.7G 0 disk ├─sdc1 8:33 1 16M 0 part ├─sdc2 8:34 1 16M 0 part └─sdc3 8:35 1 3.4G 0 part sr0 11:0 1 1024M 0 rom
In this example, /dev/sdc is the SD card of 4GB in capacity. It’s also possible to look at the kernel messages (only showing relevant lines here):
/dev/sdc
$ dmesg | tail sd 8:0:0:1: [sdc] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB) sdc: sdc1 sdc2
The option should then look like this:
--storage=/dev/sdX # adjust to match your actual device like /dev/sdc
It is highly recommended to use the latest available version of the Mali drivers, in which case this step can be skipped. Otherwise, if you want to use an older driver version, make sure you download the appropriate archives and pass the corresponding version code to the ‑‑mali option. For example, you may use:
‑‑mali
--mali=r12p0-04rel0 # to manually specify the Mali driver version
Note: The current version of this guide only supports r12p0 but more driver versions with different features may be made available in the future.
This step will automatically perform all the necessary actions to install a full Debian system on an SD card which can then be directly used with the Chromebook. Among other things, this means creating partitions, building and installing the Linux kernel as well as copying the Debian operating system files. If you later need to re-run only a subset of this process or if you want to do something different, then please refer to the 8. Manual set-up.
This will automatically download the Debian 9 (Stretch) file system built for the armhf architecture from the Linaro website.
armhf
To compile the Linux kernel and bootloader, a Linaro compiler toolchain will be automatically downloaded and extracted in the current directory.
This will also download the source code of the Linux kernel and bootloader for the Chromebook. The exact revisions can be found in the script.
With the SD card still present with the same device name, you now only need to run the do_everything command with options as determined in the previous section:
do_everything
./chromebook-setup.sh --storage=/dev/sdX --variant=VARIANT do_everything
This typically takes about 20 minutes but will vary greatly depending on the network and SD card speed to download and install files as well as the host PC performance to build the Linux kernel.
After successful completion, you should see these final messages which indicate that the SD card is ready to be inserted into the Chromebook:
Ejecting storage device... All done.
You now need to enable Developer Mode on the Chromebook to allow booting with an alternative operating system from USB/SD card with the procedure below.
Warning: Enabling Developer Mode will erase all user data. Make a back-up first.
root
crossystem dev_boot_usb=1 crossystem dev_boot_signed_only=0
You will now be able to boot from SD card after powering on the Chromebook when the ‘OS Verification’ message is displayed by pressing Ctrl+U. To boot in normal Chrome OS mode, press Ctrl+D. The Chromebook should now be able to boot in fbdev mode, i.e. without any windowing system. Log in as root with an empty password.
fbdev
This step explains how to do just a few extra things on the Chromebook while it’s running. For example, the Debian distribution contains a large repository of packages from which you can install many more programs using the apt-get utility.
apt-get
The network should automatically be started at boot time; this can be verified by running ifconfig.
If this does not work, the following commands can be run to bring up the network manually:
ifconfig -a # to find out the name of the usb ethernet interface - usually beginning with enx dhcpcd enx??? # replace as appropriate
To enable hardware-accelerated graphics rendering with X11, you will need the armsoc DDX driver and compatible Mali user-space driver. As armsoc is not available in the Debian repositories, you need to build it from source. You can run the install-x11.sh script to do this automatically, which gets installed automatically during the setup_rootfs command. Boot the Chromebook, log in as root and run:
./install-x11.sh . ~/.bashrc # reload the .bashrc to provide the runX alias runX # to actually start X11
The runX command is being used as a workaround in place of the usual startx command due to an incompatibility between the current versions of the armsoc driver and systemd-logind package. It starts the X server on virtual terminal 12 instead of the current one. This should be removed when a future version of armsoc becomes available.
Note: The graphical performance is currently suboptimal with the X11 windowing system. Please see section 7.3. Weston windowing system to enable the Weston windowing system.
X11
Note: X11 is currently not supported on the ASUS C201 Chromebook, this should also get resolved with a future armsoc version.
To enable hardware-accelerated graphics rendering with Wayland, you will need to install the relevant Weston/Wayland packages and compatible Mali user-space driver. The install-wayland.sh script can be used to automate this; it should have already been installed as part of the automatic set-up. Boot the Chromebook, log in as root and run:
./install-wayland.sh runweston-drm # to start weston with DRM backend runweston-fbdev # to start weston with fbdev backend
The Samsung Chromebook devices support Wayland with Weston and DRM back-end; this provides the best performance.
Note: The ASUS C201 Chromebook only supports Wayland with fbdev backend due to a kernel display driver issue when starting Weston with DRM back-end.
As an alternative to the guidelines described in section 5. Automatic Set-up, it is also possible to run each step of the set-up process manually. This is especially useful if you want to build with a different toolchain, partition the SD card differently, use a different version of Debian or modify the Linux kernel.
To get a detailed description of all the available commands in the set-up script, run:
./chromebook-setup.sh help
Here’s a summary of the syntax:
Usage:
./chromebook-setup.sh COMMAND [ARGS] OPTIONS
Only COMMAND and ARGS are positional arguments; the OPTIONS can be
placed anywhere and in any order. The definition of ARGS varies
with each COMMAND.
Options are detailed in 4. Configuration. Here’s a short summary of each command:
Create partitions and format the storage device.
Extract Debian archive on the root file system and adjust system configuration.
Download the relevant Mali user-side driver archives.
Extract the Mali user-side driver archive into the root file system.
Download and extract the default cross-compiler toolchain.
Create a shallow clone of the Chromebook Linux kernel Git repository and apply any extra patches.
Build the Linux kernel and install modules on the root file system.
Create a shallow clone of the Chromebook bootloader Git repository.
Build the bootloader, package it with the Linux kernel image and install it on the boot partition.
Once you’ve completed the manual process, you can run this to safely remove your storage device:
sync sudo eject /dev/sdX # adjust to match your storage device
Had to revive my old 13.3" Chromebook recently. A few updates:
1. To be compiled under Ubuntu 16.04. In 18.04 some libssl-dev libs are not compatible with the given kernel.2. More build-time dependencies needed, even in Ubuntu 16.04: sudo apt install pkg-config pkg-config-arm-linux-gnueabihf Probably they did exist implicitly in 2016 setup; probably some dependencies were lifted by now, and if you set up a [virtual] machine from the ground up, to compile this project, with current 16.04.something distribution, they are not pulled in automatically. 3. Mali drivers (r12p0) now available at developer.arm.com/.../user-space in Odroid XU3 section (earlier versions in Archive section at the bottom)4. Linaro preconfigured filesystem now available at releases.linaro.org/.../linaro-stretch-alip-20160921-1.tar.gz 5. Linaro toolchain gcc-linaro-arm-linux-gnueabihf-4.9-2014.07_linux.tar.xz now available at releases.linaro.org/.../ later versions may work or not...
One may correct the chomebook-setup.sh or just download them manually and put into the working directory alomgside with the said script.
chromeos-3.8 kernel and vboot sources are still in place.
Strange enough, all the components turned out to be still available (though some in different places), in exactly the same versions, and the entire project still builds successfully.
As to the user environment, my 16.04 setup with X11, LXDE (Lubuntu), XFCE and MATE does work well; not tried KDE. Upgrade to 18.04 results in multiple problems with MATE, and worst of all - Network Manager does not work. Fresh install of 19.10 heals the NM, and LXDE still works (there are only minor bugfixes over the past years). LXQT is not usable. LXDE is likely to survive until Ubuntu 20.04 LTS, hence it will be supported until 2025. Hopefully I'll loose or break this piece of hardware, or have it stolen by that time, or will be gone myself...
Apparently I can't see nor edit the post I just did. I forgot the link to the repo, which is:gitlab.com/.../chromebook-arm-setup
Hi Guillaume,I have reposted the script you wrote on my gitlab repo with fixed links. Neverthless, I am getting errors on the last step (build vboot).On the repo you can find the error I am getting (a conflict between the openssl headers in the vboot source code vs those installed on archlinux).Could you help me solve this? In general I see the compiled kernel is from the 3.x branch. Is there a way to have wayland hardware acceleration with mali with an upstream kernel?Cheers,Pellegrino
Hi!
The drivers are now here: https://developer.arm.com/products/software/mali-drivers/user-space
(see this thread: https://community.arm.com/graphics/f/discussions/10139/cannot-download-mali-t60x_r12p0-04rel0_linux_1-x11-tar-gz-user-space-driver-file-404)
I had the same issue and I changed the Mali_Url_Base in the chrombook_config.sh to: "https://developer.arm.com/-/media/Files/downloads/mali-drivers/user-space/firefly/malit76xr12p004rel0linux1fbdevtar.gz?revision=508727a8-07e4-49e9-a89d-6533ba792113"But I have another issue with the mali driver now.....