Bug 68213 - TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!
Summary: TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCP...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-17 10:22 UTC by XoD
Modified: 2013-08-19 16:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg radeon kernel 3.10.7 (3.45 KB, text/plain)
2013-08-17 10:22 UTC, XoD
no flags Details

Description XoD 2013-08-17 10:22:15 UTC
Created attachment 84167 [details]
dmesg radeon kernel 3.10.7

I have tested to use UVD on my discrete radeon 6570.

My PC run with a Ubuntu 13.04, I have build a 3.10.7 kernel and installed the radeon uvd firmeware.
But UVD don't work, and when I watch the dmesg I have this error :
[drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!

The radeon card is plugged in "pci express 1.0" on an 'old' motherboard(GA-K8N-SLI)

Thank you.
Comment 1 Alex Deucher 2013-08-17 13:42:49 UTC
Make sure you update to the latest rlc firmware.  This is required for UVD support.  Also make sure all the necessary firmware is in your initrd if you are using one or if you are compiling the driver into the kernel, you must also compile the firmware into the kernel.
Comment 2 XoD 2013-08-19 14:03:22 UTC
It seems I don't have the latest rlc firmware, I have updated them and I currently rebuild the kernel 3.10.7 for test again.

But I'm not sure than the firmeware are include in the initrd/kernel, how I can verify this ? (I use a kernel configuration derivated from the configuration of the ubuntu kernel).
Comment 3 Christian König 2013-08-19 14:28:17 UTC
An outdated RLC firmware is the usual problem for this. After updating the firmware you either neeed to run "update-initramfs" to get it into your initrd or "make clean" into your kernel source if you compiled it into the kernel.

Anyway this bug can probably be closed now.
Comment 4 XoD 2013-08-19 16:33:09 UTC
Update firmware, rebulid kernel, and call update-initramfs fix the problem.

I hadn't see the update of firmware file.
Sorry for the inconvenience.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.