<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#c40">Comment # 40</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:kai@dev.carbon-project.org" title="Kai <kai@dev.carbon-project.org>"> Kai</a> <pre>(In reply to Sebastian Parborg from <a href="show_bug.cgi?id=82201#c38">comment #38</a>) > However I do not have windows installed at all. So I think we can rule that > one out. > > For me it seem like the card loses the ability to reclock after a while. > However I have regained the reclocking ability by rebooting to use fgrlx and > then reboot back to use radeon... > > I'm just as confused as you are why it stops working. :S (In reply to Sebastian Parborg from <a href="show_bug.cgi?id=82201#c39">comment #39</a>) > I take the fglrx stuff back. Seems like I were lucky the times that it > worked... Sounds right. It has been so annoying to not be able to come up with at least one 100 % case. For me the non-reclocking GPU happens relatively reliable after coming off a Windows boot or after installing a new initrd (preferably for a new kernel, but regular updates can trigger it as well). Then the most "reliable" way to get back a reclocking GPU is: - execute: echo 1 > /sys/bus/pci/devices/<pci bus id>/rom && cat /sys/bus/pci/devices/<pci bus id>/rom > /tmp/vbios.dump && echo 0 > /sys/bus/pci/devices/<pci bus id>/rom - reboot and when I'm prompted for the BIOS/UEFI password, which I've set for system boots, press the power button for a few seconds until the system powers off. - boot normally - in case the GPU doesn't reclock yet: repeat This is so esoteric and sounds completely arbitrary. I have no clue what stars need to align to get a reclocking GPU. If I have one, the performance is good in various games. Also, on every boot I'm seeing a line "radeon 0000:01:00.0: Invalid ROM contents": [ 18.843246] [drm] initializing kernel modesetting (HAWAII 0x1002:0x67B1 0x1682:0x9295). [ 18.843260] [drm] register mmio base: 0xF7E00000 [ 18.843261] [drm] register mmio size: 262144 [ 18.843267] [drm] doorbell mmio base: 0xF0000000 [ 18.843269] [drm] doorbell mmio size: 8388608 [ 18.843293] radeon 0000:01:00.0: Invalid ROM contents [ 18.843351] ATOM BIOS: C67111 [ 18.843405] radeon 0000:01:00.0: VRAM: 4096M 0x0000000000000000 - 0x00000000FFFFFFFF (4096M used) [ 18.843408] radeon 0000:01:00.0: GTT: 1024M 0x0000000100000000 - 0x000000013FFFFFFF [ 18.843410] [drm] Detected VRAM RAM=4096M, BAR=256M [ 18.843411] [drm] RAM width 512bits DDR [ 18.843475] [TTM] Zone kernel: Available graphics memory: 8215252 kiB [ 18.843477] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 18.843479] [TTM] Initializing pool allocator [ 18.843485] [TTM] Initializing DMA pool allocator [ 18.843508] [drm] radeon: 4096M of VRAM memory ready [ 18.843510] [drm] radeon: 1024M of GTT memory ready. [ 18.843526] [drm] Loading hawaii Microcode [ 19.238535] [drm] Internal thermal controller with fan control [ 19.238598] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e But since that happens with and without a reclocking GPU, it's probably unrelated. For me, the problem has become less often to occur with recent kernels (3.17.0 and currently 3.18-rc1), but it still happens.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>