Description of problem: I think I've lost HW video decoding acceleration on A10 PRO-7800B R7 with recent kernel/mesa. My kodi was nicely using vdpau until recently, I cannot say when exactly it happened. Now only SW decoding and high CPU usage. I think I have all needed packages installed but vaapi also seems to be gone, when I do: [entertainer@swir ~]$ vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: mesa gallium vaapi vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc # end of output and there should be more, right? In dmesg I see: ... [ 2.125588] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130F 0x1849:0x130F 0x00). [ 2.125619] [drm] doorbell mmio base: 0xD0000000 [ 2.125620] [drm] doorbell mmio size: 8388608 [ 2.125693] ATOM BIOS: 113 [ 2.125758] radeon 0000:00:01.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used) [ 2.125760] radeon 0000:00:01.0: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF [ 2.125763] [drm] Detected VRAM RAM=2048M, BAR=256M [ 2.125764] [drm] RAM width 128bits DDR [ 2.125885] [TTM] Zone kernel: Available graphics memory: 7184660 kiB [ 2.125887] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 2.125887] [TTM] Initializing pool allocator [ 2.125891] [TTM] Initializing DMA pool allocator [ 2.125923] [drm] radeon: 2048M of VRAM memory ready [ 2.125923] [drm] radeon: 2048M of GTT memory ready. [ 2.125940] [drm] Loading kaveri Microcode [ 2.126071] [drm] Internal thermal controller without fan control [ 2.128154] [drm] radeon: dpm initialized [ 2.128175] radeon 0000:00:01.0: Direct firmware load for radeon/bonaire_uvd.bin failed with error -2 [ 2.128177] radeon 0000:00:01.0: radeon_uvd: Can't load firmware "radeon/bonaire_uvd.bin" [ 2.128840] radeon 0000:00:01.0: Direct firmware load for radeon/BONAIRE_uvd.bin failed with error -2 [ 2.128842] radeon 0000:00:01.0: radeon_uvd: Can't load firmware "radeon/BONAIRE_uvd.bin" [ 2.129030] radeon 0000:00:01.0: failed UVD (-2) init. Please fee free to tell me how & what more details to get you if necessary. many thanks, L. Version-Release number of selected component (if applicable): kernel-4.12.13-300.fc26.x86_64 kernel-4.12.14-300.fc26.x86_64 mesa-dri-drivers-17.1.7-1.fc26.x86_64 mesa-vdpau-drivers-17.1.7-1.fc26.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
only kernel that seems ok is: 4.11.8-300.fc26.x86_64 [ 1.920353] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130F 0x1849:0x130F 0x00). [ 1.920395] [drm] register mmio base: 0xFEB00000 [ 1.920396] [drm] register mmio size: 262144 [ 1.920399] [drm] doorbell mmio base: 0xD0000000 [ 1.920399] [drm] doorbell mmio size: 8388608 [ 1.920458] ATOM BIOS: 113 [ 1.920504] radeon 0000:00:01.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used) [ 1.920506] radeon 0000:00:01.0: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF [ 1.920509] [drm] Detected VRAM RAM=2048M, BAR=256M [ 1.920509] [drm] RAM width 128bits DDR [ 1.921798] [TTM] Zone kernel: Available graphics memory: 7152286 kiB [ 1.921798] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 1.921799] [TTM] Initializing pool allocator [ 1.921802] [TTM] Initializing DMA pool allocator [ 1.921826] [drm] radeon: 2048M of VRAM memory ready [ 1.921827] [drm] radeon: 2048M of GTT memory ready. [ 1.921835] [drm] Loading kaveri Microcode [ 1.921964] [drm] Internal thermal controller without fan control [ 1.922727] [drm] radeon: dpm initialized [ 1.922852] [drm] Found UVD firmware Version: 1.64 Family ID: 9 [ 1.924776] [drm] Found VCE firmware/feedback version 40.2.2 / 15! [ 1.935324] [drm] GART: num cpu pages 524288, num gpu pages 524288 [ 1.946290] [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000). [ 1.946477] radeon 0000:00:01.0: WB enabled [ 1.946491] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffffa05ba8a84c00 [ 1.946494] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffffa05ba8a84c04 [ 1.946495] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffffa05ba8a84c08 [ 1.946497] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffffa05ba8a84c0c [ 1.946499] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffffa05ba8a84c10 [ 1.946880] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000078d30 and cpu addr 0xffffb29c42438d30 [ 1.947030] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and cpu addr 0xffffa05ba8a84c18 [ 1.947032] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and cpu addr 0xffffa05ba8a84c1c [ 1.947035] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 1.947035] [drm] Driver supports precise vblank timestamp query. [ 1.947083] radeon 0000:00:01.0: radeon: using MSI. [ 1.947105] [drm] radeon: irq initialized.
but even with 4.11.8-300.fc26.x86_64 fails: $ vdpauinfo display: localhost:11.0 screen: 0 libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns -1 libva info: User requested driver 'radeonsi' libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva error: /usr/lib64/dri/radeonsi_drv_video.so init failed libva info: va_openDriver() returns 2
Seems that kernel 4.13.4-200.fc26.x86_64 loads firmware successfully but still no VDPAU and VA-API is also broken.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
ok