No vaapi hardware encoding on AMD #1803
Comments
|
I've started testing to validate the general state of HW accelerated decoding in FIrefox/Chromium and raw driver support ublue-os/bluefin#1835 (comment) I'll be testing on AMD hardware when I get access again in a day or two. |
|
Seeing the exact same issue here since upgrading to F41.20241029. Similar hardware as well: 5700X 3D and an RX 7900 XT GPU. This effectively breaks Sunshine streaming as well (can't switch to HDR, will crash after a few minutes of laggy CPU encoding). |
|
Here's some testing on an AMD laptop. Not a discrete GPU (I hope to test on 6700XT sometime soon), but it should be same driver. Oh, and I noticed, I'm still on F40. So... I'll upgrade to F41 and test again. And finally, I can report that Firefox does use hw accelerated decoding if I set
|
|
Ok, I rebased to F41 from F40 and i get the same results. Only difference is kernel and fedora release: Oh, and i'm on Bluefin, not Bazzite, but at least this means it's not a problem with the mesa drivers from negativo17, nor firefox. |
|
Oh! I rebased to Bazzite for good measure... and I see at least one thing similar to the original report... no H264 or HEVC support! Compare these results to my previous posts. I still do get hardware accelerated decode of 8k video on youtube in Firefox, but that's because it's VP9. Looks like a bug that's bazzite related though. |
|
Same thing here. vainfo rpm-ostree status |
|
No idea if my report has value, quite honestly, I'm on Bluefin stable but have an AMD cpu with graphics + discrete nvidia GPU
|
|
Contributing with my report in case it is of any help vainfo rpm-ostree status |
|
Adding my report, hope it helps. If there's anything missing or wrong, please let me know and I'll try to fix it. vainfo rpm-ostree status |
|
Here's some additional reporting from me after I got access to a machine with AMD GPU and Intel iGPU.
Intel still has HEVC and h264 support, but not AMD. Anyway, pretty clearly an issue with bazzite, not bluefin. Next I'll start looking at the bazzite specific packages and builds. |
|
The change between Bazzite 40 and 41 is de I think Bazzite assumes this is now handled upstream but somehow we get the foss version from Fedora. Maybe a dependency install / replace? I don't know anything about the Negativo mesa build but perhaps installing I also tested on 41 with |
|
Adding my info in case it helps vainfo output rpm-ostree status |
|
Fastfetch vainfo rpm-ostree status |
@PVermeer Oh my! Thank you! I had run And sure enough, the symlink is what the
You are partially correct, as we HAD assumed that actual shared objects were contained in this RPM but had missed the symlinks, so Bazzite is not actually using any dri VA drivers from negativo17, we just thought they were. |
|
Yep, and doing the same test of the rpmfusion mesa-va-drivers RPM shows: So... that's the difference... now it'll at least be easier to sort out. |
|
Not an AMD card but seeing similar issue. This is after I installed the missing CUDA Toolkit. No layered packages either. |
|
Also see https://issues.chromium.org/issues/343352540 (I'm the OP) |
|
Is there a workaround for this until it gets an official fix? |
|
It works again in the latest stable ● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:8a391b6eee805df86c9d566bfa40097543b01aef5615829663cf5cacc48b83bc
Version: 41.20241118 (2024-11-18T05:53:51Z)
LayeredPackages: code containerd.io docker-buildx-plugin docker-ce docker-ce-cli docker-compose-plugin
gnome-boxes gnome-monitor-config gnome-system-monitor goverlay grsync idevicerestore
mullvad-vpn nextcloud-client-nautilus Sunshine
$ vainfo
Trying display: wayland
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Mesa Gallium driver 24.2.4 for AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 19.1.0, DRM 3.59, 6.11.8-305.bazzite.fc41.x86_64)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
Seems like a temporary fix so not sure if I should close this. |
Describe the bug
Bazzite does no longer hardware encoding.
What did you expect to happen?
Hardware encoding to be working out of the box
Output of
rpm-ostree statusDeployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:5ca34736bf048597c1595bd52bc763491b183cf5b7624866b6959604419ce53a
Version: 41.20241029 (2024-10-29T03:42:03Z)
LayeredPackages: code containerd.io docker-buildx-plugin docker-ce docker-ce-cli docker-compose-plugin gnome-boxes
gnome-monitor-config gnome-system-monitor goverlay grsync idevicerestore mullvad-vpn
nextcloud-client-nautilus Sunshine
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:cdc448e1818b0f44e0fd0882fe0bf590b408259395da457cf15bebd209224b2c
Version: 40.20241020 (2024-10-21T05:01:41Z)
LayeredPackages: code containerd.io docker-buildx-plugin docker-ce docker-ce-cli docker-compose-plugin gnome-boxes
gnome-monitor-config gnome-system-monitor goverlay grsync idevicerestore mullvad-vpn
nextcloud-client-nautilus Sunshine
Pinned: yes
Hardware
System Details Report
Report details
Hardware Information:
Software Information:
Extra information or context
The text was updated successfully, but these errors were encountered: