-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardware Video Decoding broken on all browsers... except two #1835
Comments
I stumbled upon an Arch Wiki for enabling hardware acceleration on Chromium based browsers. What it worked was the Vulkan line:
The config file can be found at I tried to make Chrome work on Wayland with Video Hardware Acceleration successfully with these flags, if anyone is interested in running it through Wayland. I also disabled the X11 socket on Flatseal just to ensure Chrome doesn't touches it.
I tried using |
I'll add to this that this will work on AMD graphics card exvlusively. I've tested on an Intel iGPU (Intel® HD Graphics 630 KBL GT2) and there was no acceleration on Chrome (and probably all other Chromium-based browsers). I also enabled GPU HA via Flatseal, and set the variable GNOME Web (Epiphany) and Firefox worked out of the box, both in Wayland and X11. GNOME Web requires GPU HA, while Firefox won't, for Hardware Video Acceleration. This may be a bug on Chromium side of things, so until that is resolved, you should probably switch to other browser in the meantime if your workflow is video-heavy. |
First, it's not Chromium, but I started with the related issue linked in the main description and started by troubleshooting with Firefox. See my results here: #1409 (comment) TL;DR of that link... Firefox flatpak seems to be working great for me with all default flapak and browser settings on Intel. And, my system is a bluefin stable nvidia image ( Version: 40.20241101.0 )... So Fedora 40... but this is after the recent fixes to nvidia driver configs last week. So, I did the same thing with Chrome's most recent flatpak (Version 130.0.6723.91) as I did for Firefox.
Finally, I pulled up the same 4K video linked above and tested it both in Firefox and Chromium. In Firefox I do see the Intel GPU enc/dec hardware getting used, but NOT in Chrome and also Chrome shows higher CPU usage. So...
I now see HW video enc/dec being used on the iGPU and low CPU usage. So, generally speaking, on at least Intel hardware, Chrome seems to be working with vaapi for HW accelerated decoding. There is a report in bazzite of vaapi not working for AMD. I don't have access to AMD hardware for a few days, but at least this much validation is done. I'll do some more testing in a few days when I get access to that hardware again. |
I'm trying the same flags on Chrome (130.0.6723.91) and Edge (130.0.2849.56) and no dice. Plus, the driver log on
Just for show I used this flags:
No dice. Also tried both
Same results... but at least Vulkan is enabled ( |
I can tell you, I only have the following:
If I enable Vulkan, Chrome stops using the intel haw decoder. |
Weird, because I used only those flags and the results were the same. Enabling Vulkan doesn't make any difference, as by default Chrome uses Can you output your |
You're running on X11 (XWayland, to be precise). Also, Tiger Lake GT2 (Gen 12.1). Does |
I fixed it on my end by adding custom kernel arguments, even if it taints the kernel, by following the Arch guide to enable HVA on Intel graphics, but adding the kernel parameters via rpm-ostree kargs --add=i915.enable_guc=3 For some reason, using
Th thing is, if I put People without Video Hardware Acceleration on Intel iGPU (for any reason) may need kernel parameters to enable it. Also, that kernel parameter is the only one added to the bunch. After that, Chrome and Edge loaded, but they needed the @bsherman Can you return the output of |
Describe the bug
I've tried multiple browsers against YouTube, which is using VP9 codec for all videos, and all of these do play the video using the CPU rather than the VP9 hardware video decoder.
As expected, CPU usage spikes as the video resolution rises. Weaker CPUs will struggle, and older laptops will last less on battery.
What did you expect to happen?
To use the Hardware Video Decoder from the platform.
Output of
rpm-ostree status
(Yeah, moved from latest to stable because latest borked GNOME Shell preferences on their latest, but I believe I saw the same problem of hardware video acceleration).
Output of
groups
Extra information or context
The platform is a Ryzen 8845HS w/ Radeon 780M. It's confirmed to support VP9:
I've tried the following browsers against the same 4K video, all Flatpaks:
GPU Decoding was measured through Mission Center 0.6.1.
I will re-test all of them by forcing them to run in Wayland, with Graphic Acceleration.Added GPU HA via Flatseal.¹: Zen works with Video Hardware Decoding even if the
device=dri
option from Flatseal comes disabled by default.²: I loaded GNOME Web on X11 and Hardware Video Decoding was available. I disabled it via Flatseal and the video was decoded by the CPU.
³: Most browsers don't work on Wayland, except Zen, GNOME Web (Epiphany) and LibreWolf.
Related
The text was updated successfully, but these errors were encountered: