https://bugs.freedesktop.org/show_bug.cgi?id=68213
Priority: medium Bug ID: 68213 Assignee: dri-devel@lists.freedesktop.org Summary: TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! Severity: normal Classification: Unclassified OS: All Reporter: xoddark@gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI
Created attachment 84167 --> https://bugs.freedesktop.org/attachment.cgi?id=84167&action=edit 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.
https://bugs.freedesktop.org/show_bug.cgi?id=68213
--- Comment #1 from Alex Deucher agd5f@yahoo.com --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=68213
--- Comment #2 from XoD xoddark@gmail.com --- 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).
https://bugs.freedesktop.org/show_bug.cgi?id=68213
Christian König deathsimple@vodafone.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID
--- Comment #3 from Christian König deathsimple@vodafone.de --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=68213
XoD xoddark@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from XoD xoddark@gmail.com --- Update firmware, rebulid kernel, and call update-initramfs fix the problem.
I hadn't see the update of firmware file. Sorry for the inconvenience.
dri-devel@lists.freedesktop.org