<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Hang during boot when DPM is on (R9 270X)" href="https://bugs.freedesktop.org/show_bug.cgi?id=76490#c100">Comment # 100</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Hang during boot when DPM is on (R9 270X)" href="https://bugs.freedesktop.org/show_bug.cgi?id=76490">bug 76490</a> from <a class="email" href="mailto:dex+fdobugzilla@dragonslave.de" title="Daniel Exner <dex+fdobugzilla@dragonslave.de>"> Daniel Exner</a> <pre>(In reply to Maxim Sheviakov from <a href="show_bug.cgi?id=76490#c99">comment #99</a>) > Interesting, but it got flashed 0_0 > Also, the problem is not in VBios or IDs. It's all about memory clock - > setting a value higher than 1.2GHz (in a quirk) makes the system hang after > Plymouth/before display server start. So, to my mind we have to do something > with DPM/PowerPlay code or make some userspace overclock support, as there's > no other way right now. By the way, is there such a tool that allows to > overclock memory of the card? If that worked for you you are lucky, but at least I won't flash a different BIOS just to _downgrade_ my card, possibly breaking it completely. Alas the already in place quirk results in exactly the same. > And yep, with its standard VBios card works with 1050MHz/1.2GHz > (core/memory) clocks. I'm using those SMC patches + new firmware. Maybe they > should be sent upstream, even to add that new firmware files and code to use > them? The new firmware files are fine for 370X it seems but still need work for 270X. I guess most 270X users CC in this ticket will happily test possible reworked ones as soon as they are available and we patiently wait for Alex.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>