<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HAWAII] GPU doesn't reclock, poor 3D performance" href="https://bugs.freedesktop.org/show_bug.cgi?id=82201#c36">Comment # 36</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HAWAII] GPU doesn't reclock, poor 3D performance" href="https://bugs.freedesktop.org/show_bug.cgi?id=82201">bug 82201</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to Kai from <a href="show_bug.cgi?id=82201#c35">comment #35</a>) > (In reply to Christian König from <a href="show_bug.cgi?id=82201#c34">comment #34</a>) > > (In reply to Kai from <a href="show_bug.cgi?id=82201#c33">comment #33</a>) > > > And I have non-reclocking GPU again. > > > Is there any data I can provide, that would help you tracking down, what > > > Windows is setting, that is preventing proper initialisation of the card for > > > Linux? > > > > Well that could actually be perfectly normal behavior. For some hardware > > blocks you can upload the firmware only once after a bootup. > > > > So what could happen is that the windows driver loads one version and the > > linux driver needs a different one. The same problems applies the other way > > around as well. > > I think I need to rephrase the description: the system was powered off for > ten to twelve hours after I had Windows running, and then on the next boot > (into Linux), I didn't get a reclocking GPU. I didn't reboot the PC directly > into Linux. (Though I didn't disconnect power, so some parts of the > motherboard might stay powered.) Ah! Ok that's something different. As long as the system was completely off (defined by no power to the GPU) there shouldn't be any influence from the previously booted os.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>