(update, Vulkan disappeared!) Believe it or not, I solved! For real this time! | HW Video Acceleration

Pathduck

@Panino said in SOLVED! (for the last time) This time on Stable - NEON | HW Video Acceleration:

And how each version is using different drivers? It's because the Stable is new and works differently, it has it's own driver?

No - "Google Inc. (Intel)". means it's using Software rendering, not hardware.
Explains the "Video Acceleration" being blank as well I guess.

Other than that, I can't help much with Linux and GPU driver problems.

npro

@Panino said in SOLVED! (for the last time) This time on Stable - NEON | HW Video Acceleration:

on the snapshot where acceleration is working

You really sure about that? The only way to be absolutely sure is the picture I showed you, Hardware Decoder should be showing true, not what you see under vivaldi://gpu. For example you see Video Decode: Hardware accelerated there but the textboxes in VA-Info are not showing any info.

I checked vivaldi://gpu for my Snapshot, it is what you are showing for Stable.
Use X11 and skip the parameter --use-gl=egl as I wrote above.

@Pathduck said in SOLVED! (for the last time) This time on Stable - NEON | HW Video Acceleration:

"Google Inc. (Intel)". means it's using Software rendering, not hardware.
Explains the "Video Acceleration" being blank as well I guess.

For strictly software rendering that would be Swiftshader, which is not in OP's case. ANGLE should be ok. OP needs additionally the parameter --enable-features=VaapiVideoDecoder for the textboxes to show the VA values.

The problem lies into that Chromium changes all the time, some things that used to work before don't quite work now.

Pathduck

@npro Well, I don't really know - but I do know that if I disabled HW accel. here (Windows with Nvidia card), GPU0 will show as:

VENDOR= 0xffff [Google Inc. (Google)], DEVICE=0xffff [ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver-5.0.0)], LUID={0,0}, DRIVER_VENDOR=SwANGLE, DRIVER_VERSION=5.0.0 *ACTIVE*

GL_VENDOR will be Google Inc. (Google) and Video Acceleration Information will show empty values.

So that was my observation, that it has nothing to do with Stable vs. Snapshot and all about HW accel. being disabled. For whatever reason that might be...

npro

@Pathduck Yes but you have that SwiftShader Device (Subzero) (<- ) there (OP didn't have that), that confirms you 've disabled hardware acceleration . Anyway it's pretty messy, always have been.

P.S. For some reason I couldn't post this with V. (error), had to use Firefox...

npro

This post is deleted!

Panino

@npro I can guarantee you, acceleration is working on the Snapshot.

I configured the Stable the same, some times tried to add or remove a few things, didn't worked. Then I noticed this detail about the drivers.
Why? As I said before, I think? In the past acceleration worked on the Stable, but then a minor update fix would make it stop working again, that's why all this time I always kept using the Snapshot. I had planned to make the switch to Stable this year but my plans failed because of this.

I don't understand, why on the same system the Snapshot used the correct driver but the Stable don't. Tricks to force Vivaldi/the browser to use an specific driver is something I hadn't tried yet.
Now, even adding these flags --gpu-testing-vendor-id=0x8086 --gpu-testing-device-id=0x1916 nothing changes there.

EDIT: I just tried every combination of flags, not matters what I do, Stable insist on using "Angle" and "Google, Inc".

Panino

Video Acceleration broke on the Snapshot too after Mesa and Vaapi packages, all hope is lost.
Now I'll have to use Firefox only for watching videos.

npro

@Panino Chromium devs messed it up by moving on to a new decoder (which is -from the little I read- working for Intel GPUs only), Vivaldi based on Chromium 114 is the last working version for other GPUs.

Panino

Not the only one with this problem: https://www.reddit.com/r/vivaldibrowser/comments/15jquqs/comment/jzfxhlu/?context=3

npro

This post is deleted!

edwardp

@Panino r/vivaldibrowser is not an official support channel.

Has this been reported as a bug? If not, please submit a bug report, provide all relevant information (including the Linux distro and version, mesa and vaapi package version numbers) and provide the bug report number (VB-xxxxx) in this thread. You can also include this message topic (post its URL) in the bug report.

Thank you.

npro

@npro Works with Chromium 115.0.5790.170 (AMD)

Panino

Just as short update.
All those categories in "vivaldi:gpu" were displaying as "software only". Nothing I did made any difference, nothing, absolutely nothing. I gave up and was using it that way, with Firefox Open to watch videos.

Today I wanted to use BleachBit and used it to clean system and Vivaldi's cache and guess what... those categories changed to "hardware accelerated".

Video acceleration still not working, that problem with GL_Vendor being Google Inc persists, but at least not the general performance should be better, I hope.

Panino

This week I switched from KDE Neon to Tuxedo OS, maybe change played it's part, but still... FINALLY DID IT!

Noticed that "Vulkan" was "Disabled" on the GPU page and thought, "shouldn't this be enabled?"
Changed it's flag from "Default" to "Enabled" and it worked!

alt text

Finally! After all these years!
Sorry Firefox, I don't you need anymore.

Panino

@Panino said in Believe it or not, I solved! For real this time! | HW Video Acceleration:

This week I switched from KDE Neon to Tuxedo OS, maybe change played it's part, but still... FINALLY DID IT!

Noticed that "Vulkan" was "Disabled" on the GPU page and thought, "shouldn't this be enabled?"
Changed it's flag from "Default" to "Enabled" and it worked!

Finally! After all these years!
Sorry Firefox, I don't you need anymore.

Vivaldi updated to version 7.1, and I noticed that video acceleration stopped working while watching a video on YT.

Went to check GPU and Vulkan is disabled.
Went to check Flags and:

alt text

It's gone!
What happened with Vulkan?

DoctorG

@Panino said in (update, Vulkan disappeared!) Believe it or not, I solved! For real this time! | HW Video Acceleration:

What happened with Vulkan?

Was removed from Chromium 132 core on Linux as i can see.

Perhaps commandline helps:

--use-vulkan

Enable Vulkan support and select Vulkan implementation, must also have ENABLE_VULKAN defined. This only initializes Vulkan, the flag --enable-features=Vulkan must also be used to select Vulkan for compositing and rasterization.

https://peter.sh/experiments/chromium-command-line-switches/#use-vulkan

Could be that in Flags the Temporarily unexpire M130 flags brings back the flag.

Ouch, enabling M130 flags and enabling Vulkan does not start my Vivaldi anymore on Debian 12 KDE with NVidia. I removed Vulkan setting in flags now.

DoctorG

@Panino Closed bug report VB-113707 as it is a Chromium upstream issue and i do not know if setting will come back with Chromium in future.

npro

I have hardware video acceleration with my UHD600 without vulkan:

Panino

@DoctorG said in (update, Vulkan disappeared!) Believe it or not, I solved! For real this time! | HW Video Acceleration:

@Panino Closed bug report VB-113707 as it is a Chromium upstream issue and i do not know if setting will come back with Chromium in future.

I CAN'T BELIEVE IT!!!!!

Which one is the last (.deb) snapshot with Vulkan?

npro

@Panino Just use the equivalent parameter --enable-features=Vulkan or unexpire the flag as DoctorG did chrome://flags/#temporary-unexpire-flags-m130 if you need vulkan so much.

Seems like the removal is only temporal or by mistake: