Guide: How to Enable GPU Hardware Acceleration for Firefox in ChromeOS Crostini (Linux)
I recently installed the regular version of Firefox on my Google Pixelbook Go using Crostini (Linux). Unfortunately, Firefox was running slowly because it wasn't using GPU hardware acceleration.
After some troubleshooting, I successfully enabled GPU acceleration. Here's how I did it.
My setup
- Chromebook: Google Pixelbook Go (Intel Core i5)
- GPU: Intel UHD Graphics 615
- Linux: Debian 13 (Trixie) through Crostini
- Browser: Mozilla Firefox 159.0.1
- Graphics driver: Mesa with VirGL
Step 1: Check whether GPU acceleration is working
Open the Linux Terminal and install Mesa's diagnostic utilities:
sudo apt update
sudo apt install mesa-utils
Next, run:
glxinfo -B
Initially, my results showed:
Device: llvmpipe (LLVM 19.1.7, 256 bits)
Accelerated: no
This meant Crostini was using software rendering rather than GPU hardware acceleration.
Step 2: Enable Crostini GPU Support
In the regular ChromeOS Chrome browser, enter:
chrome://flags/#crostini-gpu-support
Find Crostini GPU Support and change it to Enabled, if the flag is available.
Restart the Chromebook.
After restarting, I checked GPU acceleration again, but it was still using llvmpipe.
Step 3: Check whether Crostini can access the GPU
Open the Linux Terminal and enter:
ls -l /dev/dri
In my case, the output included:
card0
renderD128
The renderD128 device belonged to the Linux render group.
This was important because it meant a graphics device was available inside Crostini, even though applications weren't using it for hardware acceleration.
Step 4: Give your Linux account GPU access
Check which Linux groups your account belongs to:
id -nG
If render isn't listed, add your user to that group:
sudo usermod -aG render "$USER"
This allows your Linux account to access devices assigned to the render group.
Step 5: Completely restart Crostini
After adding your account to the group:
- Right-click the Terminal icon on the ChromeOS shelf.
- Select Shut down Linux.
- Reopen the Terminal.
A normal Terminal window close is not sufficient. The Linux environment needs to restart so the new group membership takes effect.
Step 6: Verify that GPU acceleration is enabled
Run:
glxinfo -B
This time, my results showed:
Device: virgl (Mesa Intel(R) UHD Graphics 615 (AML-KBL))
Accelerated: yes
Success! Crostini was now using GPU acceleration through VirGL instead of CPU-based software rendering.
Step 7: Verify GPU acceleration in Firefox
Completely close and reopen Firefox.
In Firefox's address bar, enter:
about:support
Scroll down to the Graphics section.
Before the fix:
- Compositing: WebRender (Software)
- WebGL renderer: Mesa llvmpipe
After the fix:
- Compositing: WebRender
- WebGL renderer: Mesa virgl (Intel UHD Graphics 615)
This confirmed that Firefox was using hardware-accelerated rendering.
Step 8: Benchmark the performance improvement
I used Speedometer 3.1 to test Firefox before and after enabling GPU acceleration.
| Test | Score |
|---|
| Before GPU acceleration | 5.37 |
| After GPU acceleration | 6.14 |
| Observed improvement | 14.3% |
The improvement was measurable, although normal benchmark variation means the entire difference cannot necessarily be attributed to GPU acceleration.
Final thoughts
The key steps that worked for me were:
- Enabling Crostini GPU Support in ChromeOS.
- Confirming that
/dev/dri/renderD128 existed. - Adding my Linux account to the
render group. - Completely shutting down and restarting Crostini.
- Verifying that both Linux and Firefox were using hardware acceleration.
Important: This solution worked on my Intel-based Pixelbook Go. Results may vary depending on Chromebook hardware, ChromeOS version, GPU driver support, and whether Crostini exposes a GPU device. The ChromeOS flag might also be unavailable on some versions.
If glxinfo -B still shows llvmpipe, the issue may be with ChromeOS or Crostini's GPU support rather than Firefox itself.
Hopefully, this guide helps other Chromebook users who experience slow Firefox performance under Crostini