You are not logged in.
guiodic wrote:I have the same problem, but only using "modesetting" dirver. With old intel driver it's ok.
Oh that's interesting.
Which hardware do you have ?
Here I have a 12th gen intel and the intel driver is too broken for that platform AFAICT, it causes more issues than it solves.
Intel Tigerlake (gen 11)
Yes, the old intel driver causes other problems (screenshot corruption in my case). It's a shame that Intel dropped that driver, it has a very good 2D acceleration (SNA).
Offline
p.s. not sure but I remember that all began when chrome dropped --use--gl=desktop (now only angle works)
Offline
I opened https://bugs.chromium.org/p/chromium/is … id=1467689 feel free to chime in and add any info you have ...
Thank you sir, I was already thinking I'm crazy. Happens also for me on i915 Intel HD 630 , Intel(R) Core(TM) i7-7700HQ
Offline
I sometimes wonder about how many dinosaurs had to give their lives so that we can push video data in the order of petabytes/second over the pcie bus...
Offline
On chrome 115.0.5790.110 with 12th gen intel:
vaapi is working with just this flag
--enable-features=VaapiVideoDecodeLinuxGL
I tested it on youtube with vp9 and av1 video.
Offline
I sometimes wonder about how many dinosaurs had to give their lives so that we can push video data in the order of petabytes/second over the pcie bus...
The difference between 32GB/s and 1,000,000 GB/s is approximately 1,000,000 GB/s +/- 0.004%
Oil is mostly made of bacteria and marine algae and organisms.
Just saying....
Last edited by ewaller (2023-08-01 03:24:10)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
Most of it is also older than most of the "Dinosaurs" you're probably thinking of, certainly than the CT extinction.
Which btw. had to happen for an even more devastating species to show up for what should be the prime aspect of any of those debates:
The climate conditions we're headed for have indeed existed in the past (so the planet is gonna be fine, btw) and human ancestors at the time were typically referred to as "breakfast".
Let's just say, I'd leave Florida. The only thing more scary than a 10m crocogator is a 10m crocogator on meth…
Offline
Log shows this:
Failed to export buffer to dma_buf: No such file or directory (2)
Bzzz_56 wrote:gilvbp wrote:Nvidia video acceleration doesn't work with Wayland . Has anyone got it to work?
It works with chromium-wayland-vaapi (at least with my tiger lake intel igpu, and videos of format x264), while it crashes a lot when I use fcitx5 (via the flag --enable-wayland-ime), which is a deal-breaker for me...Sorry for not seeing that you have a nvidia gpu, I'm not sure if libva-nvidia-driver will work with chromium-wayland-vaapi or not...
Anyone?UPDATE: It was a regression chromium bug, already addressed: https://bugs.chromium.org/p/chromium/is … 273758#c11
Just to share my recent experiences with this on Wayland+nvidia, this absolutely would not work with any build of chromium except chromium-wayland-vaapi.
The regression bug listed is still open and has only been triaged on Jun 30th with radio silence from the dev assigned to the bug report. I suggest anyone facing issues with Wayland + nvidia to star bug report.
Offline
To workaround the memory leak:
LIBVA_DRI3_DISABLE=1 google-chrome-stable --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder
Edit: doesn't work for 116, I stay with 115...
Last edited by guiodic (2023-08-12 23:32:28)
Offline
Hi, I have problems with youtube in chrome 115.0.5790.170 on Peppermint 10, frame drops about 20-50% in any video. No such problem in Chromium, Firefox, Opera but same issue in Vivaldi, Brave, no hardware acceleration in any browser.
Google Chrome 115.0.5790.170 (Official Build) (64-bit)
Revision cc0d30c2ca5577520c8646671513241faa0bc105-refs/branch-heads/5790@{#1923}
OS Linux
JavaScript V8 11.5.150.22
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
Command Line /usr/bin/google-chrome-stable --force-dark-mode --enable-features=WebUIDarkMode --enable-features=VaapiVideoEncoder,VaapiVideoDecoder,CanvasOopRasterization --disable-gpu-drive --disable-direct-compositionr-bug-workarounds --enable-native-gpu-memory-buffers --enable-gpu-rasterization --enable-oop-rasterization --disable-gpu-vsync --enable-zero-copy --use-gl=desktop --enable-accelerated-video-decode --enable-accelerated-video-encode --ignore-gpu-blocklist --enable-gpu-compositing --enable-smooth-scrolling --disable-gpu-driver-workarounds --disable-font-subpixel-positioning --disable-features=UseChromeOSDirectVideoDecoder --enable-unsafe-webgpu --flag-switches-begin --disable-accelerated-video-decode --ignore-gpu-blocklist --enable-features=VaapiVideoEncoder,VaapiVideoDecoder,CanvasOopRasterization,Vulkan --flag-switches-end --desktop-startup-id=xfce4-panel/|usr|bin|google-chrome-stable/3525-3-xxml_TIME21105026 --origin-trial-disabled-features=WebGPU
Tried all flags but no success.
Offline
Sorry, but These forums are for Arch Linux users ONLY, a fact you agreed to when you registered here. Please ask the Peppermint people.
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
Sorry, but no such discussion in other forums.
Offline
Nor in this one.
This thread is abotu HW acceleration in chromium, you're posting about google chrome issues that are explicitly *not* related to hardware acceleration (despite your commandline suggesting different) and explcitily *not* chromium related.
For all we know this could be some extension or whanot - since you've also not read https://bbs.archlinux.org/viewtopic.php?id=57855
You can certainly lurk and comment on this thread, but
1. stay on topic
2. understand that nobody here can or will help you to solve a specific problem that might hinge on something specific to your distro - because nobody else here uses anywhere nearly the same software stack.
Offline
Tnx, useful forum.
Offline
chrome 116 broke atleast for me hardware acceleration again, nothing atleast which i know works now
- libva_dri3_disable flag is enabled, i tried without it - no difference
- with chrome-flags.conf flags: --ignore-gpu-blocklist
--enable-gpu-rasterization
--enable-zero-copy
--disable-features=UseChromeOSDirectVideoDecoder or without them
edif: I found --disable-features=UseChromeOSDirectVideoDecoder isn't working anymore and before without this flag it didnt work for me anyway... So until someone find out new similar flag then chromium 116 hardware acceleration i guess is no-go
Last edited by adi222 (2023-08-16 15:31:20)
Offline
So until someone find out new similar flag then chromium 116 hardware acceleration i guess is no-go
See this: https://chromium.googlesource.com/chrom … e398f8da1b
They just removed VaapiVideoDecodeAccelerator, so now vaapi is only possible for intel gpu
Last edited by impavid (2023-08-16 15:59:17)
Offline
adi222 wrote:So until someone find out new similar flag then chromium 116 hardware acceleration i guess is no-go
See this: https://chromium.googlesource.com/chrom … e398f8da1b
They just removed VaapiVideoDecodeAccelerator, so now vaapi is only possible for intel gpu
well i have uhd620 igpu and it doesnt work anyways, maybe it works on newer igpus or only on arc ones who knows
for now i downgraded to 115.0.5790.170 and works again but well or i will need change browser or build chromium everytime without this commit which will be pain or maybe someone will fix it in different way
Last edited by adi222 (2023-08-16 18:21:50)
Offline
they wrote "we have fully transitioned to the new VD video decoder path."
They are fully transitioned to a heavy buggy decoder...
it's unbelievable, i've been using hardware acceleration with vaapi for more than a decade without any problems with gstreamer and mpv, but all the power of google is unable to write a decent decoder.
Offline
I rebased my (rather hacky) patch to get VaapiVideoDecoder to work on AMD - it now applies to Chromium 116: https://gist.github.com/thubble/235806c … 9173d24d9f
It works on my RX 6800, verified using chrome://media-internals/ - VaapiVideoDecoder is being used.
I'm running on (X)Wayland with KDE Plasma 5.27, with the following Chromium flags (forcing XWayland - native Wayland will not work with VAAPI as far as I know). I know some of these are unnecessary or redundant/duplicate, but I can't be bothered testing to see which are actually required:
--ozone-platform=x11 --enable-features=CanvasOopRasterization,VaapiVideoDecoder,UseChromeOSDirectVideoDecoder,VaapiIgnoreDriverChecks,PlatformHEVCDecoderSupport,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE --use-cmd-decoder=passthrough --use-gl=angle --use-angle=vulkan --use-vulkan=native --ignore-gpu-blocklist --enable-zero-copy --enable-gpu-rasterization --enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
Offline
On nvidia+wayland systems, the only hw video accelerated browser I could achieve, is firefox through nvidia-vaapi-driver. There's an ongoing issue on chrome support branch, but it's not going well.
Offline
gothmog123 wrote:sorry out of the loop. is it working on wayland nowadays?
Chromium 114.0.5735.106, iHD video, wayland, default settings.
The only one flag in ~/.config/chromium-flags.conf
--enable-features=VaapiVideoDecodeLinuxGL
It works for me.
Oh yeah, thanks man!! After testing thousand of flags, it works just with this.
Chromium Version 116.0.5845.110 (Official Build) Arch Linux (64-bit)
Linux archlinux 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64 GNU/Linux
You can deinstall libva-intel-driver for these igpu (only needs intel-media-driver):
12th Gen Intel(R) Core(TM) i5-12600
Offline
I Uploaded the last working Wayland nvidia version here (https://www.dropbox.com/scl/fi/6x65jhgd … pk631&dl=0)
please use this version!
PS: Here are the old diffs https://aur.archlinux.org/cgit/aur.git/ … land-vaapi (you should use 111.0.5563.146-1 source files)
gilvbp wrote:Log shows this:
Failed to export buffer to dma_buf: No such file or directory (2)
Bzzz_56 wrote:
It works with chromium-wayland-vaapi (at least with my tiger lake intel igpu, and videos of format x264), while it crashes a lot when I use fcitx5 (via the flag --enable-wayland-ime), which is a deal-breaker for me...Sorry for not seeing that you have a nvidia gpu, I'm not sure if libva-nvidia-driver will work with chromium-wayland-vaapi or not...
Anyone?UPDATE: It was a regression chromium bug, already addressed: https://bugs.chromium.org/p/chromium/is … 273758#c11
Just to share my recent experiences with this on Wayland+nvidia, this absolutely would not work with any build of chromium except chromium-wayland-vaapi.
The regression bug listed is still open and has only been triaged on Jun 30th with radio silence from the dev assigned to the bug report. I suggest anyone facing issues with Wayland + nvidia to star bug report.
Last edited by gilvbp (2023-08-30 09:38:21)
Offline
Oh yeah, thanks man!! After testing thousand of flags, it works just with this.
Chromium Version 116.0.5845.110 (Official Build) Arch Linux (64-bit)
Linux archlinux 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64 GNU/Linux
You don't have the memory leak issue ?
(Check with `xrestop` if the PxMem column keeps increasing when playing video)
Offline
On chrome 115.0.5790.110 with 12th gen intel:
vaapi is working with just this flag
--enable-features=VaapiVideoDecodeLinuxGL
I tested it on youtube with vp9 and av1 video.
You are my hero. Works for me too!
Offline
bwidlar wrote:Oh yeah, thanks man!! After testing thousand of flags, it works just with this.
Chromium Version 116.0.5845.110 (Official Build) Arch Linux (64-bit)
Linux archlinux 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64 GNU/LinuxYou don't have the memory leak issue ?
(Check with `xrestop` if the PxMem column keeps increasing when playing video)
I didn't know anything about this bug, thanks for the information.
And yes, after tested with xrestop the PxMem column keeps increasing when playing videos.
The longer Chromium it's open, the longer it takes for the X11 system to recover after closing.
This clearly points to that bug.
It was too good to be true ; ) Let's hope they fix it soon.
Last edited by bwidlar (2023-08-31 07:25:52)
Offline