Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Fedora 33 packages "/usr/lib64/dri/radeonsi_drv_video.so" under the mesa-dri-drivers; the same package mesa-dri-drivers does not contain this file. This file is import for proper functioning of VAAPI under AMDGPUs.
Version-Release number of selected component (if applicable): mesa-20.3.3-2.el8.src.rpm
How reproducible:
Check package contents.
Steps to Reproduce:
1. Check package contents via "rpm -ql mesa-dri-drivers | grep radeonsi_drv"
Actual results:
/usr/lib64/dri/radeonsi_drv_video.so
/usr/lib/dri/radeonsi_drv_video.so
Expected results:
No output
Additional info:
I built a copy of vainfo (libva-utils isn't packaged?), and it revealed:
libva info: VA-API version 1.5.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
I brought this back up, and realized I inverted the actual an expected results; it should be:
Actual results:
No output
Expected results:
/usr/lib64/dri/radeonsi_drv_video.so
/usr/lib/dri/radeonsi_drv_video.so
Hi,
We evaluated the request and decided that we will keep them disabled for now until we have a more clear understanding of the video driver and how codecs are being used. Thanks for filing this BZ.
For posterity, what are the concerns?
This seems like it should be a relatively straightforward request, packaged not only by the "upstream" Fedora, but packaged in a similarly stable distro, Debian -- in versions Buster (10), Stretch (9), and Jessie (8).
Lack of this file makes Cent OS and downstream derivatives that follow this guidance very poor for anything that needs to do video encoding or decoding. This impacts streaming in the server workload case, and even something as simple as video playback in the destkop workload case.
Comment 8Christopher Pereira
2022-11-28 17:57:13 UTC
Why WONTFIX?
The RHEL package is missing important drivers and breaking hardware acceleration support.
Not understanding how something works, is not a reason for breaking it.
An appropiate explanation for this decission is very welcome.
Comment 9Christopher Pereira
2022-11-30 02:22:47 UTC