<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!" href="https://bugs.freedesktop.org/show_bug.cgi?id=63935#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - TURKS [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!!" href="https://bugs.freedesktop.org/show_bug.cgi?id=63935">bug 63935</a> from <a class="email" href="mailto:dawitbro@sbcglobal.net" title="Dave Witbrodt <dawitbro@sbcglobal.net>"> Dave Witbrodt</a> <pre>(In reply to <a href="show_bug.cgi?id=63935#c15">comment #15</a>) > > The good news is that I can reproduce the problem, and it indeed looks like > the firmware image gets corrupted. But that seems to always happen not only > when the image is loaded from initrd. That is a fact. I run my locally-built kernels without initrd files; the kernel has an initramfs facility which allows files to be manually selected for inclusion in the vmlinuz image (I used to use this for uvesafb), and a separate set of config options (CONFIG_EXTRA_FIRMWARE*, see <a href="show_bug.cgi?id=63935#c9">comment 9</a> above) specifically for including firmware files into a particular location in the initial filesystem. I have been doing this for several years. It currently works for UVD on 2 out of 3 systems. (A fourth machine has an integrated Radeon GPU too old to be supported by this UVD code, though it also boots Linux without an initrd.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>