Just discovered that if you change the unlocking mode to 2 in AB (via cfg file) and set unlocking of voltage under settings in AB
you can set voltage, memory and core to pretty much anything. Memory is still limited to 685 on the low end.
This works with catalyst 12.3 and 8.95 driver. However, I have trouble running my 3x7970s below 1000 memory.
Not sure if it is my BIOS settings or what. One card can run at 1177/685, but not three. So far 1100/1000 is my latest stable
configuration. Maybe I need to undervoltage it or change BIOS. Not sure at this point.
When I set memory below 1000, GPU-Z sensor page shows it, cgminer starts it and accepts it. It can run for 20 minutes with low memory
settings on all three cards and then I get "Device XXX idle to 60 seconds" on one of the devices. Usually GPU 0 or 1, never #2.
Temperature is ok on all three. CPU stays below 50% as I'm testing with -I 9.
Topic: 2 BTC bounty - why can't I get lower Mem clocks? (Read 3305 times)
Elmojo,
FYI,
I've installed 8.95.0.0 driver, the pre-certified catalyst
http://support.amd.com/us/kbarticles/Pages/AMDCatalystSoftwareSuiteVersion122PreCertified.aspx
Driver Packaging Version 8.95-120214a-133662E-ATI
AB (beta14) cannot change the values in the BIOS, but I run cgminer with bin from run on older driver and
I can run 1177/685. I cannot change the memory clock but I can run it @ 685
So the hack is to downgrade, run cgminer, upgrade, re-run cgminer with its bin from previous run.
http://www.fileswap.com/dl/hp3bvRV6SX/pre-certified-catalyst-1177-685.bmp.html
FYI,
I've installed 8.95.0.0 driver, the pre-certified catalyst
http://support.amd.com/us/kbarticles/Pages/AMDCatalystSoftwareSuiteVersion122PreCertified.aspx
Driver Packaging Version 8.95-120214a-133662E-ATI
AB (beta14) cannot change the values in the BIOS, but I run cgminer with bin from run on older driver and
I can run 1177/685. I cannot change the memory clock but I can run it @ 685
So the hack is to downgrade, run cgminer, upgrade, re-run cgminer with its bin from previous run.
http://www.fileswap.com/dl/hp3bvRV6SX/pre-certified-catalyst-1177-685.bmp.html
Here is my driver's info:
Driver Version 8.921.0.0
Driver Version 8.921.0.0
That's the old driver version I was talking about.
With the new driver (8.96), it breaks AB, even Beta 14.
My bad, I thought I had the latest version.
Try using ati tray tools as well. I dont know if it supports the 79xx series yet but, I used it to lower the memclock on my 6950 to 150mhz (confirmed via gpuz) where all other tools failed to set it this far down.
I've installed 8.95.0.0 driver, the pre-certified catalyst
http://support.amd.com/us/kbarticles/Pages/AMDCatalystSoftwareSuiteVersion122PreCertified.aspx
Driver Packaging Version 8.95-120214a-133662E-ATI
AB (beta14) cannot change the values in the BIOS, but I run cgminer with bin from run on older driver and
I can run 1177/685. I cannot change the memory clock but I can run it @ 685
So the hack is to downgrade, run cgminer, upgrade, re-run cgminer with its bin from previous run.
That's good info, thanks.http://support.amd.com/us/kbarticles/Pages/AMDCatalystSoftwareSuiteVersion122PreCertified.aspx
Driver Packaging Version 8.95-120214a-133662E-ATI
AB (beta14) cannot change the values in the BIOS, but I run cgminer with bin from run on older driver and
I can run 1177/685. I cannot change the memory clock but I can run it @ 685
So the hack is to downgrade, run cgminer, upgrade, re-run cgminer with its bin from previous run.
AMD is doing everything they can to drag users through mud...
My bad, I thought I had the latest version.
No problem, this whole thing confuses the heck out of me!
I'm debating rolling back to an earlier driver, but I'll probably wait at least until I get my water block installed later this week.
Here is my driver's info:
Driver Version 8.921.0.0
Driver Version 8.921.0.0
That's the old driver version I was talking about.
With the new driver (8.96), it breaks AB, even Beta 14.
afterburner (beta 14) will let you lower it to 685. Real value as shown using GPU-Z sensors tab.
Then start your cgminer with -gpu-memclock 685
I'm running cgminer at 1200/685, see my signature for details.
Then start your cgminer with -gpu-memclock 685
I'm running cgminer at 1200/685, see my signature for details.
Not with the latest AMD drivers it doesn't.
Version 8.96 (Feb 14) pretty much breaks AB completely.
In fact, i had to uninstall it to get my card to even run a stock clocks.
Hopefully Unwinder will fix it soon, but it's in AMD's lap now.
Using the beta allowed me to lower the clock.
So who deserves the bounty? I will honor the wishes of the forum!
So who deserves the bounty? I will honor the wishes of the forum!
Very simple question and only you can decide: Did any of the specific info posted help you reach the answer (did you already know it or not). If it didn't help no bounty, if it did bounty.
So how does it impact performance? AFAIK, you need SDK 2.6 for radeon 7 cards, and with SDK 2.6, hashrate scales pretty good with mem speed (IOW, if you lower your mem speed, hashrates take a nosedive).
Am I wrong?
Am I wrong?
I seem to be missing something here.
The several posts above mine appear to suggest that the issue has been resolved.
Has it? Not for me.
I still can't drop my mem clocks below the AMD default of Core Clock - 150mV.
Has this been resolved and I missed it?
The several posts above mine appear to suggest that the issue has been resolved.
Has it? Not for me.
I still can't drop my mem clocks below the AMD default of Core Clock - 150mV.
Has this been resolved and I missed it?
Using the beta allowed me to lower the clock.
So who deserves the bounty? I will honor the wishes of the forum!
The latest beta? If so, it looks like you would have got it done regardless (you suggested "the beta" before anyone else did) So who deserves the bounty? I will honor the wishes of the forum!
I thought so too, but I did not want to be seen as suggesting that!
Using the beta allowed me to lower the clock.
So who deserves the bounty? I will honor the wishes of the forum!
The latest beta? If so, it looks like you would have got it done regardless (you suggested "the beta" before anyone else did) So who deserves the bounty? I will honor the wishes of the forum!
Using the beta allowed me to lower the clock.
So who deserves the bounty? I will honor the wishes of the forum!
So who deserves the bounty? I will honor the wishes of the forum!
Oh... interesting. I haven't tried updating the drivers on the rig since I started mining. I started using Linux shortly after. Looks like BIOS flashing may end up being the solution for newer drivers unless ATI decides to leave the old RivaTuner stuff in the driver.
Make sure you're using 2.2.0 Beta 10. It's one of the only versions currently working for setting voltages and memclocks on a 7970. The other option is manually hex editing the BIOS and flashing. Apparently the BIOS signature check is disabled in Windows in the current driver, but I haven't tested it (works on Linux though).
Beta 10 didn't work at all on my XFX 7970. I had to get Beta 11 to make it at least partially work.
Unwinder said that the latest AMD drivers (12.3) removed some dlls and broke the unofficial overclocking feature.
Hopefully AB Beta 14 will find a fix...
Make sure you're using 2.2.0 Beta 10. It's one of the only versions currently working for setting voltages and memclocks on a 7970. The other option is manually hex editing the BIOS and flashing. Apparently the BIOS signature check is disabled in Windows in the current driver, but I haven't tested it (works on Linux though).
The current version (Beta 12) of afterburner does NOT work correctly with the 7970.
I'm fighting that battle right now.
I can set whatever I want in AB, but the card just mostly ignores it when I start mining.
The best I've been able to get so far is 1000 core/800 mem @ .893v
I'm hoping when Beta 14 is released (possibly today) it might fix this bug.
The author of AB says the issues are due to AMD jacking around with the drivers and causing stuff to break.
I'm fighting that battle right now.
I can set whatever I want in AB, but the card just mostly ignores it when I start mining.
The best I've been able to get so far is 1000 core/800 mem @ .893v
I'm hoping when Beta 14 is released (possibly today) it might fix this bug.
The author of AB says the issues are due to AMD jacking around with the drivers and causing stuff to break.
Why not just use Afterburner?
Edit the MSIAfterburner.cfg
[ATIADLHAL]
EnableUnofficialOverclocking = 1
UnofficialOverclockingEULA = I confirm that I am aware of unofficial overclocking limitations and fully understand that MSI will not provide me any support on it
UnofficialOverclockingMode = 2
AccessibilityCheckingPeriod = 0
And your good to go.
Edit the MSIAfterburner.cfg
[ATIADLHAL]
EnableUnofficialOverclocking = 1
UnofficialOverclockingEULA = I confirm that I am aware of unofficial overclocking limitations and fully understand that MSI will not provide me any support on it
UnofficialOverclockingMode = 2
AccessibilityCheckingPeriod = 0
And your good to go.
I think you need to do this to the MSIAfterburner.cfg file.
On my 6970s, I wasn't able to go to 685 until I modified this file.
I am going to try the afterburner beta tonight and see if that works.
Yes, make sure it's the Beta. It didn't work for me with the other versions.
Why not just use Afterburner?
Edit the MSIAfterburner.cfg
[ATIADLHAL]
EnableUnofficialOverclocking = 1
UnofficialOverclockingEULA = I confirm that I am aware of unofficial overclocking limitations and fully understand that MSI will not provide me any support on it
UnofficialOverclockingMode = 2
AccessibilityCheckingPeriod = 0
And your good to go.
Edit the MSIAfterburner.cfg
[ATIADLHAL]
EnableUnofficialOverclocking = 1
UnofficialOverclockingEULA = I confirm that I am aware of unofficial overclocking limitations and fully understand that MSI will not provide me any support on it
UnofficialOverclockingMode = 2
AccessibilityCheckingPeriod = 0
And your good to go.
I think you need to do this to the MSIAfterburner.cfg file.
On my 6970s, I wasn't able to go to 685 until I modified this file.
I am going to try the afterburner beta tonight and see if that works.
Jump to: