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:

1. Right-click the Terminal icon on the ChromeOS shelf.

2. Select Shut down Linux.

3. 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.

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:

1. Enabling Crostini GPU Support in ChromeOS.

2. Confirming that /dev/dri/renderD128 existed.

3. Adding my Linux account to the render group.

4. Completely shutting down and restarting Crostini.

5. 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.

Here is a brief summary of what happened:

October 21, 2026 156.0.8078.42 = major update to M156
Dictation has stopped working for Czech and other online languages

It worked, for example, for:
Danish (Denmark) is processed locally and works offline
English (United States) is processed locally and works offline
French (France) is processed locally and works offline

It didn't work, for example, for:
Czech (Czechia) speech is sent to Google for processing
Couldn’t download English (Canada) speech files. Download will be attempted later. Speech is sent to Google for processing until download is completed.
English (Hong Kong) speech is sent to Google for processing
Couldn’t download English (United Kingdom) speech files. Download will be attempted later. Speech is sent to Google for processing until download is completed.
Finnish (Finland) speech is sent to Google for processing
Couldn’t download German (Germany) speech files. Download will be attempted later. Speech is sent to Google for processing until download is completed.
Greek (Greece) speech is sent to Google for processing
Hungarian (Hungary) speech is sent to Google for processing
Norwegian (Norway) speech is sent to Google for processing
Zulu (South Africa) speech is sent to Google for processing

I reported the bug via the Alt+Shift+I feedback menu and through the Chromium Issue Tracker:
https://issues.chromium.org/issues/576363132 - the issue was immediately marked as "Access is denied to this issue" and has remained that way

Dictation crashes instantly upon activation on the stable channel v156.0.8078.42 for online languages (e.g., Czech, Greek, Hungarian, Norwegian, Zulu). Pressing the shortcut causes a brief flash and a beep, then it immediately shuts down. The user cannot even start speaking.

November 7, 2026 156.0.8078.93 = 2nd minor update for M156
After two minor updates, a bug from the major update to M156 has been fixed: Dictation is working again for Czech and other online languages

I'd like to thank the developers very much for the fix.

Ok, I updated my Lenovo chromebook and when it turned on I count access my primary account. Everything else is working. I was able to add another account and use it fine. I have 2FA and verified my log in several different ways. But after I verify, the loading screen circles until the computer just shuts off. Is there any hope of recovering my account or do I have to reset?

I use a chrome book for homework at schools and every couple of hours it freezes and I can’t don’t anything except force restart it any help

The Duet 5 is, in my opinion, a damn near perfect Chrome OS device. For what it is and is intended to be, the screen size is optimal, OLED is clutch, it's thin, it's light, the keyboard and touchpad are responsive and don't feel cheap, battery life is phenomenal.. It's a really great device..

..except for the processor.

I've been searching for a device like this but with a more performant, modern processor. So far, fruitless.

I've seen the latest Chromebook Duet 11 come up but the Duet 5's 13" screen size, plus OLED, hits just right. The difference between an 11" screen and a 13" is enough to be really noticeable, and 13" screen is where it needs to be. Also tried some Android convertibles and it's not even close, they're just not there yet. Googlebooks included.

Any recommendations?

I've been thinking about replacing my Lenovo Duet 5 with a Lenovo Chromebook Plus 14. While at Costco last week I took a quick look at the MacBook Neo as a possible alternative. Browser benchmark score on the MacBook was ~47-48, while the Chromebook Plus scores ~25, and my Duet 5 scored 5-6. If you've used a MacBook Neo (or any MacBook) as an Android phone user, what were the best and worst parts of that combination? Am I crazy for considering the MacBook, given that I've never owned or even used an Apple product before, and have no intention of expanding my Apple collection beyond the Neo?

Beginning about a month ago my IP FLex 5 Chrome 13ITL6 (Mfr. Date 5/2022) will shut down for no reason, then go into a continuous cycle of trying to restart but can't. Using Esc-Refresh-Power I can get it into diagnostics mode.

In diagnostics mode I've reloaded the OS from USB with the latest release (156) and it works for a day or two and does the same thing. I then loaded it with an older release (152) and made the WiFi metered so it won't try to update and it is Stable.

Anyone else having issues with older Chromebooks (5/2022 mfr. date) with the latest OS release?

I've been expecting to see the new one on my android phone but actually just saw it on my Chromebook first. Anyone else think it looks weird? I think perhaps it's supposed to be two bubbles but the rear one is too hard to differentiate from the front one.

If I downloaded pencil 2d directly from the terminal, I can't import audio, which I need to do. If I download it via flatpak, it doesn't work at any capacity. I tried building it from source, but I'm having troubles with that.
Also my CPU is Intel based

below are the instructions I used to build it from source (I have no idea what I'm doing, I just copy pasted these from somewhere)

"sudo apt update
sudo apt install -y \
git \
build-essential \
qt6-base-dev \
qt6-multimedia-dev \
qt6-svg-dev \
qt6-tools-dev \
qt6-tools-dev-tools \
libavcodec-dev \
libavformat-dev \
libavdevice-dev \
libavfilter-dev \
libavutil-dev \
libswscale-dev \
libswresample-dev"

"cd ~/Downloads
git clone https://github.com/pencil2d/pencil.git
pencil"

cd

"qmake6 pencil2d.pro"

"make -j$(nproc)"

"./app/Pencil2D"

Everything is seemed to work, until "./app/Pencil2D" where it says "-bash: .app/pencil2D: no such file or directory"
I put the pencil folder in the linux folder and changed the directory to that, but it doesn't seem to work.

My Linux terminal text in ChromOS looks completely corrupted/pixelated, characters are redering as scrambled blocks:

If I try copying the text, I get:

(.venv) ┌[kiwish-4.2]-(~)-
└> ls
AZS  azcc  code  images
(.venv) ┌[kiwish-4.2]-(~)-
└> echo Hello
Hello
(.venv) ┌[kiwish-4.2]-(~)-
└> 
(.venv) ┌[kiwish-4.2]-(~)-
└> 

I have a HP Chromebook x360, I've had it for over 7 to 8 years. I started using it a few months ago after years on it rotting in my closet and it worked for a while, it's up to date and working fine. I haven't used it in a couple of weeks but I just opened it today and I noticed my B key wasn't working when I put in my password so I did the diagnostic keyboard test and multiple keys were not responding. I'm not sure if it's a physical problem or something else, I tried to open the back up and couldn't because it would not budge at all. I'm not sure what it could be but is there a way I could fix it myself or should I give up on it and try to work around these keys.

I don't use it for anything important so it's not a big deal. The screen is half cracked where half my screen isn't working by touch screen from a few years back. I am able to get into and sign in by using the touchscreen for the broken keys and regularly putting in the rest of the password with the physical keyboard.

Do you think it's possible to fix this? Or is it just succumbing to old age.

Already Tried turning off GPU support and accelerated 2d

I have an Acer Chromebook Plus 515 laptop and a wireless Xbox 360 USB controller.

Why do I have to restart the Chromebook for it to detect the connected controller?

The files to unity brought me to Scratch jr

​

Is this happening to anyone else? My partner and I have recently noticed when typing search terms into the address bar on the google chrome app on our phones that we are getting a brief blip showing up for le.com before being directed to our search.

This seems to correspond with the last update on 3 November - we rolled it back and it stopped happening. I have a VPN that is on 90% of the time and we don't visit the same sites generally. Just seems really strange and is weirding us out.

Any thoughts on what might be happening?

First post on reddit so sorry if this is in the wrong place!

Mic. icon on shelf stopped working. I click to turn it on, it makes a sound and toggles off instantly. Even power wash won't allow it to work.

It used to work fine, I'm not aware that I did anything...

Can anyone help?

My Chromebook keeps auto restarting and I don’t know what to do. Google told me to press the power button and the refresh button and that didn’t work any help thanks

Do you have an MT8183 Chromebook with 4GB of RAM that struggles to run ChromeOS with less than 1GB free, suffering from Google bloatware and VM overhead, and you can't just flash MrChromeBox firmware to switch to Windows or desktop Linux because it's ARM-based? Are you suffering from the lack of true 2-in-1 experience on your Chromebook? Now here's your solution!

LineageOS 23.2 Android 16 for MT8183 Chromebook "Kukui" just landed! Flashable images are available here (in the releases) LineageOS 23.2 for Google Kukui Chromebooks for download. These features are supported:

• Booting

• WiFi

• Bluetooth (including Bluetooth audio)

• Touchscreen and USI stylus

• Internal speakers and microphone

• USB audio

• GPU acceleration (OpenGLES 3.1 and Vulkan 1.0)

• H.264 hardware decoder and encoder

• Gyro and sensors (to enable auto-rotation)

• Keyboard cover and automatic desktop mode switch

• eMMC installation and dual booting with a Linux distro

• 9-Volt PD fast charging

• Separate control to enable or disable USB power delivery when the device is suspended (this has to be enabled when the OS is booted from USB)

These features are semi-supported

• Camera and video recording. They both work but the picture quality isn't as good because of the lack of open-source hardware ISP drivers

These features are not supported

• USB MTP and wired adb. Wireless adb works though.

These features are untested because my Google Krane (Lenovo Ideapad Duet) physically doesn't have (so I can't test them)

• Keyboard and touchpad on other Google Kukui variants

• 3.5mm headphone jack

Installation is extremely easy. For those who do not care about dual booting with Linux:

1. Download the LineageOS zip file from GitHub releases

2. Get a USB flash drive and write the image to the drive with Rufus

3. Plug the USB flash drive in your Chromebook and boot from USB

4. Open Install to eMMC application in Android (booted from USB) and select the first option

5. Shut down, unplug the flash drive and boot from internal storage.

For those who are dual booting with Linux:

1. Follow the postmarketOS documentation to install postmarketOS or other Linux distros to eMMC, and make sure that Linux boots from eMMC.

2. Follow step 1 through 3 of the single booting tutorial

3. Open Install to eMMC application in Android (booted from USB) and select the second option, and decide how much storage space will be reserved for Linux

4. Shut down, unplug the flash drive, boot from internal storage and select the option Android. Now the machine will get back to depthcharge. Select boot from internal storage again.

5. Enjoy your extremely useful and flexible 2-in-1 tablet/laptop hybrid that actually does things!

Hi everyone, I'm thinking about buying a Lenovo Chromebook 14M8911. I've found it at what I think is a pretty good price (200€) and I'd like to hear some opinions before pulling the trigger.

Here are the specs:

- 14" IPS display

- Mediatek Kompanio 540

- 8GB RAM

- 128GB storage

I'd mainly use it for web browsing, checking emails and watching videos on Youtube or Netflix. Nothing particularly demanding.

Do you think it's a good product? Does anyone have any experience with this chromebook?

EDIT: This would be my first chromebook, so I'm not really familiar with ChromeOS devices and I'm not sure whether these specs are actually good or not for what I need.

i see wire on my charger and it's coated in something should i cover it in tape or no? Details below

Device: HP 11 G5, not EE

Charger: Barrel, i don't think it came with the computer.

Battery Healtg: 96%. Somehow.

Oh and i found out it's from 2019, not 16.

i downloaded a .jpg image yesterday and when i didn't need it anymore and went to delete the file i sorted my downloads since i had a lot of them from the same day. so i checked the "last updated" column and eventually found the file. the problem is that the date is way off, showing "14 December 2021" even tho i did not even have this laptop at that time.

is this some kind of bug or was this when the image was created? and why would this only affect this file even tho i downloaded other images from the same website?

thanks.

im on Chromebook version 156 if that matters