<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#c39">Comment # 39</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:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to Tobias Droste from <a href="show_bug.cgi?id=76490#c35">comment #35</a>) > 3) This card works fine with any sclk/mclk combination with the same vddc > (1238mV) in windows and I can overclock there! There is apparently some aspect of the set up that we are not programming correctly that manifests with higher clocks on certain boards. > > I'm also wondering why I get a different VBIOS size if I get the bios in > windows (gpu-z) and linux. Is it because different firmware gets loaded? The > (working) vbios under windows is twice as large as the linux one (see > attachments). The vbios is loaded from rom on the card. The firmware for the various micro-controllers on the GPU are loaded by the driver and are not part of the vbios. I'm not sure off hand why they differ. Perhaps gpuz always returns a 128K image regardless of what size the actual bios is? Or maybe it asks the driver windows driver for a copy and the windows driver always stores 128K images regardless of the actual image size. I quick look at the tables and I only see one small difference in the overdrive table: -OD max sclk: 140000, max mclk: 162500 (win) +OD max sclk: 107000, max mclk: 140000 (linux) Everything else appears to be the same. I'm guessing the windows driver patched that and gpuz fetches the copy from the driver.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>