Multiple Discrete GPU - Broken Hardware Decoding

This might be similar to the following previously closed bug:

My os-tree ouput

rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia-open:stable-daily
                   Digest: sha256:15f6ea94e85df6cbf95df9a4514226015973a02d95dd1f55866ad88d7aea33e8
                  Version: 41.20250309.1 (2025-03-09T06:07:15Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia-open:stable-daily
                   Digest: sha256:15f6ea94e85df6cbf95df9a4514226015973a02d95dd1f55866ad88d7aea33e8
                  Version: 41.20250309.1 (2025-03-09T06:07:15Z)

When running vainfo with the Titan RTX driving both of my monitors I ended up with:

vainfo
Trying display: wayland
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_1_0
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: VA-API NVDEC driver [direct backend]
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain12             :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileHEVCMain444            :	VAEntrypointVLD
      VAProfileHEVCMain444_10         :	VAEntrypointVLD
      VAProfileHEVCMain444_12         :	VAEntrypointVLD

When running vainfo with both monitors on the AMD 9700 XTX or mixing them I end up with

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 25.0.0 for AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 19.1.7, DRM 3.59, 6.12.13-200.fc41.x86_64)
vainfo: Supported profile and entrypoints
      VAProfileJPEGBaseline           :    VAEntrypointVLD
      VAProfileVP9Profile0            :    VAEntrypointVLD
      VAProfileVP9Profile2            :    VAEntrypointVLD
      VAProfileAV1Profile0            :    VAEntrypointVLD
      VAProfileAV1Profile0            :    VAEntrypointEncSlice
      VAProfileNone                   :    VAEntrypointVideoProc

Switching from nvidida-stable to stable and plugging into the AMD card gives me the following output

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:stable-daily
                   Digest: sha256:14040692a85089a62a39ecb91b605684e0f7284dc2c8bd1e8162cdd6aecb0e8a
                  Version: 41.20250309.2 (2025-03-09T19:24:17Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia-open:stable-daily
                   Digest: sha256:15f6ea94e85df6cbf95df9a4514226015973a02d95dd1f55866ad88d7aea33e8
                  Version: 41.20250309.1 (2025-03-09T06:07:15Z)

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 25.0.0 for AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 19.1.7, DRM 3.59, 6.12.13-200.fc41.x86_64)
vainfo: Supported profile and entrypoints
      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
      VAProfileAV1Profile0            :	VAEntrypointEncSlice
      VAProfileNone                   :	VAEntrypointVideoProc

Any thoughts on what could be going on here?

Likely we got dnf’ed again.

We’re fixing another issue with Nvidia right now and I’m assuming this will be fixed at the same time.

But basically dnf at times like to “upgrade” packages when installing other packages. Sometimes this undos packages we’ve installed.

Normally this is caused by dnf wanting to install something with a newer version from fedora-updates.

1 Like

Thanks for chiming in here.

I was starting to wonder if it was an issue with simultaneous AMD/NVidia use. :slight_smile:

The issue is that when installing Nvidia drivers it needs to install 32 bit mesa.

Fedora-nvidia negativio17 doesn’t have those. So we need fedora-multimedia enabled when first installing those 32 bit mesa packages.

Bluefin was pinned to an older version of the Nvidia install script that wasn’t doing this so it broke…

But if someone sees missing hw acceleration on amd on bluefin. Dnf likely removed negativio17 mesa.

After the update on daily I got the following

❯ 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 25.0.0 for AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 19.1.7, DRM 3.61, 6.13.5-200.fc41.x86_64)
vainfo: Supported profile and entrypoints
      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
      VAProfileAV1Profile0            :	VAEntrypointEncSlice
      VAProfileNone                   :	VAEntrypointVideoProc

Resolve still can’t make use of the nvidia card but still tries to use the nvidia configuration to decode video. However, I think that problem has a lot more to do with davinci box than anything else.

Yeah, I can’t really help with davinci box. I haven’t looked at how that works. But looks like you have hw acceleration again on the AMD card

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.