<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#c24">Comment # 24</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#c19">comment #19</a>) > (In reply to <a href="show_bug.cgi?id=63935#c18">comment #18</a>) > > Benjamin and Parag have already indicated which firmware versions they are > > using, and I feel it's safe to assume that Christian is also using the > > proper versions as well. > > It's worth double checking. I've forgotten to update my ucode a number of > times and run into similar problems. Christian was using out of date ucode > and when he fixed it his UEFI system started working fine. OK, I see your point. There was a firmware update in Debian Sid on May 6, and that _did_ overwrite the newer firmware files that are also present in the firmware package. But I checked for this at the time (May 6) and have been vigilant about it since. The files are up to date right now, and have been since that firmware package upgrade. > We can take a look at register dumps. grab radeonreg: > <a href="http://cgit.freedesktop.org/~airlied/radeontool/">http://cgit.freedesktop.org/~airlied/radeontool/</a> > and dump the regs when booted with legacy vbios vs. UEFI and attach the > outputs. Looks like I cannot play; I have SUMO2 while Benjamin has TURKS, and with the git version of 'radeontool' I see this: # ./radeonreg regs all unknown chipset, specify the regs to dump # grep SUMO radeon_chipinfo_gen.h # grep TURKS radeon_chipinfo_gen.h { 0x6740, CHIP_FAMILY_TURKS, 1, 0, 0, 0, 0 }, { 0x6741, CHIP_FAMILY_TURKS, 1, 0, 0, 0, 0 }, { 0x6742, CHIP_FAMILY_TURKS, 1, 0, 0, 0, 0 }, { 0x6743, CHIP_FAMILY_TURKS, 1, 0, 0, 0, 0 }, { 0x6744, CHIP_FAMILY_TURKS, 1, 0, 0, 0, 0 }, { 0x6745, CHIP_FAMILY_TURKS, 1, 0, 0, 0, 0 }, { 0x6746, CHIP_FAMILY_TURKS, 0, 0, 0, 0, 0 }, { 0x6747, CHIP_FAMILY_TURKS, 0, 0, 0, 0, 0 }, { 0x6748, CHIP_FAMILY_TURKS, 0, 0, 0, 0, 0 }, { 0x6749, CHIP_FAMILY_TURKS, 0, 0, 0, 0, 0 }, { 0x6750, CHIP_FAMILY_TURKS, 0, 0, 0, 0, 0 }, { 0x6758, CHIP_FAMILY_TURKS, 0, 0, 0, 0, 0 }, { 0x6759, CHIP_FAMILY_TURKS, 0, 0, 0, 0, 0 }, My hardware is shown in <a href="show_bug.cgi?id=63935#c6">comment 6</a>, at this line of the 'dmesg' output: [drm] initializing kernel modesetting (SUMO2 0x1002:0x9644 0x1849:0x9640) # grep 9644 radeon_chipinfo_gen.h # grep 6741 radeon_chipinfo_gen.h { 0x6741, CHIP_FAMILY_TURKS, 1, 0, 0, 0, 0 }, Bummer. It looks like Benjamin has some good results. Hopefully that will lead to a fix.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>