This process can be used to get Fedora installed on your Chromebook. This process will destroy your data so make sure you have backups of anything you need. When you're done ChromeOS will not be bootable and your data will be wiped. See the notes below for how to adapt them for other distrbutions.
What works and doesn't work:
| Component | Status |
|---|---|
| Ambient Light Sensor | Mostly Working Issue |
| Audio | Working |
| Brightness | Working |
| Bluetooth | Working |
| Camera | Working |
| Keyboard | Working |
| Orientation / Tablet Mode | Working |
| Suspend | Working |
| Touchpad | Working |
| Touchscreen | Working |
| Wireless | Working |
-
Google Pixelbook (2017) The steps below will wipe your data and account settings.
-
A second computer or a USB A to USB C adapter so you can plug the other end into the Pixelbook itself
-
A willingness to patiently troubleshoot and diagnose issues. This is an advanced task and yields imperfect results. Many desktop environments, display managers, and configurations have not been tested fully, if at all, and may require additional work to make function. Most of the packages, scripts, and configs provided here are workarounds to known issues for which there are currently no proper fix or configuration.
-
You should know how to perform these tasks or be ready to google them for troubleshooting purposes if something goes wrong:
- Install, remove, and update packages on Fedora
- Enable, disable, stop, and (re)start systemd services
- Change runlevels using systemd, including from the GRUB menu using the kernel command line
- Change display managers and / or desktops to determine if the problem is specific to one or all.
- Enable wireless network connections with NetworkManager or systemd-networkd from the shell.
- Install, configure, and run playbooks with ansible
These steps will wipe your data and account settings. Do not proceed if you need data on your Chromebook.
- Press
ESC+Refresh+Poweron the Pixelbook - At the recovery screen press
CTRL-D - Once you are certain your data is backed up you can confirm that you want to do this and proceed.
- At this point your Chromebook will be powerwashed and your account and data removed so once it finished log back in
- All of the instructions for this process are at mrchromebox.tech
- You must configure Closed Case Debug, disable write protect, and enable firmware flashing.
- To do all of this read, understand, and follow these instructions.
- Then use the Firmware Utility Script to install the UEFI firmware.
- Do make a backup of the stock firmware and ensure you do not lose it.
- If you ever want to go back to ChromeOS you can use the script to restore this backup firmware. Don't lose it.
If you followed the instructions above you should be all set.
If you skipped the instructions above because coreboot was already installed please ensure it is up to date. At least one trace in dmesg was resolved by a firmware update.
You may also encounter a bug that causes slow boots and hangs on shutdown if running coreboot versions prior to 4.16, which contains this fix.
- Prepare a bootable Fedora USB stick
- Insert it into the Pixelbook and install it normally.
Once fedora is installed you may make use of the ansible playbook provided for configuration or continue following the instructions in this file.
sudo dnf -y copr enable jmontleon/pixelbooksudo dnf -y update
By default audio will not work at all, but by copying topology and firmware files from a recovery image the speakers will work. With some additional configuration the microphone, headphone jack, and possibly other aspects work as well.
- Download the latest eve recovery image from chromiumdash.appspot.com/serving-builds
- Unzip the file. As an example
unzip chromeos_13904.55.0_eve_recovery_stable-channel_mp-v2.bin.zip - Create device maps
sudo kpartx -av chromeos_13904.55.0_eve_recovery_stable-channel_mp-v2.bin - Mount the ChromeOS root filesystem
sudo mount -o ro /dev/mapper/loop0p3 /mnt - Copy the files:
sudo cp /mnt/lib/firmware/9d71-GOOGLE-EVEMAX-0-tplg.bin /lib/firmware/sudo cp /mnt/lib/firmware/dsp_lib_dsm_core_spt_release.bin /lib/firmware/sudo cp /mnt/lib/firmware/intel/dsp_fw_C75061F3-F2B2-4DCC-8F9F-82ABB4131E66.bin /lib/firmware/intelsudo mkdir -p /opt/google/dsm/sudo cp /mnt/opt/google/dsm/dsmparam.bin /opt/google/dsm/dsmparam.bin
- Add audio packages
sudo dnf -y install pixelbook-alsa-ucm pixelbook-wireplumber pixelbook-scripts systemctl --user --now enable pixelbook-acpi- After rebooting you should have audio (Note: Some systems require 2 or occasionally 3 reboots. See the troubleshooting section for details)
sudo dnf install pixelbook-udev && sudo dnf -y update, if you haven't already.- Create
/etc/modprobe.d/i915.confwith one line:options i915 enable_dpcd_backlight=1 sudo dracut -f- After rebooting the backlight should work.
sudo dnf -y install pixelbook-udev, if you haven't already.
sudo dnf -y install pixelbook-scripts- Add yourself to the input group:
sudo usermod -aG input $USER - Set up a keyboard shortcut up to run
/usr/bin/pixelbook-keyboard-backlightwhen you pressctrl+space.
sudo dnf -y install pixelbook-udev pixelbook-scripts, if you haven't already.sudo dnf -y update, if you haven't already.- `edit /etc/acpi/events/powerconf and comment out the following two lines. This will prevent the power button from causing an immediate shutdown in Gnome.
event=button/power.*
action=/etc/acpi/actions/power.sh
sudo systemctl --now enable acpid- Gnome and KDE handle screen orientation automatically in tablet mode.
- For others
systemctl --user --now enable pixelbook-display-orientation systemctl --user --now enable pixelbook-acpiwill listen to tablet mode and audio jack related events and act accordingly
A frequent complaint is that the touchpad does not work after reboot. If you encounter this you can install the pixelbook-touchpad-service as a workaround. This is a service that unloads and loads two kernel modules.
sudo dnf -y install pixelbook-touchpad-servicesudo systemctl enable --now pixelbook-touchpad
If you enable Tap to Click in Gnome or Xfce it will also enable Tap to Drag. To disable Tap to Drag you can do one of the following.
gsettings set org.gnome.desktop.peripherals.touchpad tap-and-drag false
sudo dnf -y install pixelbook-touchpad-tweak
sudo dnf -y install pixelbook-scripts, if you haven't already.sudo usermod -aG input $USER, if you haven't alreadysudo usermod -aG tty $USER- Gnome and KDE have their own gesture logic. For Xfce and others
systemctl --user --now enable pixelbook-touchscreen-click
Watching journalctl you'll note lots of logging about AER corrections. The pixelbook-aer package contains a workaround for this.
sudo dnf -y install pixelbook-aersudo systemctl enable --now pixelbook-aer
A lot of common software is not available in Fedora, such as nvidia drivers and vlc. Fortunately a plethora of software is available from RPM Fusion.
When rebooting users have observed sound continuing to fail and the mouse not working. If this happens, the problem is often remedied by rebooting via the Power+Refresh button or holding down the the power button until the system powers off and then using it to power on the system again. The touchpad section above contains a service that will mask the problem.
5.16 introduced fixes to the display backlight.
Audio has been a particularly problematic area at times. Make sure you're not using a known broken kernel.
- An audio issue was introduced in the 5.15.5 kernel and fixed in 5.17.0. At some point 5.15 LTS kernels were also fixed.
- In general 5.17.0 and above should work well although HDMI output has been broken since 5.17.0
- 6.0-6.0.9 were broken
- 6.1-6.1.12 were broken
- A proposed patch for HDMI output is available but not yet in the kernel.
- There was one issue report for the error
rt5514 i2c-10EC5514:00: Device with ID register e0220042 is not rt5514appearing in dmesg and audio failing to work. The cause is unknown, but restoring ChromeOS and Reflashing the MrChromebox firmware appeared to resolve the issue.
Issues are welcome if you think you found something Pixelbook specific. Full logs, detailed explanations of steps taken, configuration performed, etc. are important. It is impossible to provide help with comments that simply state things aren't working as expected.
For the most part nothing in this repo is distribution specific other than the availability of packages to simplify the install process. The primary adjustments you will need to be concerned about are listed below.
- Reference this PR to see the kernel options that must be enabled for hardware support.
- To match placement of configuration and scripts that are provided by packages look at the corresponding spec file. All sources are located in the configs and scripts directories.
- When a package is referenced, using the alsa ucm package as an example, note the sources in the spec file and where they are installed and manually do the same. Alsa is a special case in that 1.2.6 and above put these files in a conf.d directory. For older versions you'll probably need to move them one directory up.
If you would like to provide these packages in an AUR, PPA, or similar repo for other distributions for yourself and others please let me know and I will add them to the instructions.