Jump to content

Google Chromebooks with x64 CPU (google-x64cros)

From postmarketOS Wiki
Revision as of 12:23, 11 February 2023 by Alpernebbi (talk | contribs) (Add section about audio and suspend issues)
Google Chromebooks with x64 CPU
Lenovo IdeaPad 3 Chromebook (11IGL05) ("Google Lick") running postmarketOS
Lenovo IdeaPad 3 Chromebook (11IGL05) ("Google Lick") running postmarketOS
Manufacturer Google
Name Chromebooks with x64 CPU
Codename google-x64cros
Hardware
Architecture x86_64
Software
Original software ChromeOS
FOSS bootloader yes
postmarketOS
Category testing
Pre-built images no
Mainline yes
Features
USB Networking
No data
Internal storage
No data
SD card
No data
Battery
Works
Screen
Works
Touchscreen
No data
Keyboard
Works
Touchpad
Works
Multimedia
3D Acceleration
Works
Audio
Works
Camera
Works
Camera Flash
No data
Connectivity
WiFi
Works
Bluetooth
Works
Miscellaneous
FDE
Broken
USB-A
Works
USB OTG
Works
HDMI/DP
No data
Sensors
Accelerometer
No data
Magnetometer
No data
Ambient Light
No data
Proximity
No data
Hall Effect
No data
Haptics
No data
Barometer
No data
Power Sensor
No data


This device allows postmarketOS to run on x86_64 ChromeOS boards by using its verified boot mechanism.

Contributors

Based on the Generic x64 UEFI device port contributed by:

And ChromeOS-specific postmarketOS integration by:

Installation

See Chrome OS devices page.

Common Issues

Audio

There are reports of people damaging the speakers while tinkering with audio stuff on various Chromebooks. This includes ARM ones, but those are ported and tested per-device to be safe. Although this generic port doesn't add any configuration beyond what upstream projects do, those upstream configurations may or may not be safe to run on your specific device.

Suspend

Suspending the device makes the firmware go into recovery mode, and disables booting from external devices or with alternative firmware. This is because a TPM involved in the boot flow must be informed that the OS has booted OK. The kernel drivers that do this have not been enabled yet, enabling them fixes the issue.

See also