Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 76. (Read 324169 times)
February 25, 2012, 11:44:47 AM
I have been trying to overclock my cards all night. If I set my voltage to the stock setting it accepts the overclock. Not much of a solution though. Even in ati, it only lets the voltage raise to 1.049 which is stock on the 5970.
February 25, 2012, 11:38:43 AM
Thanks I must have had too many or few spaces. It is working now.
I have the same problem, can't get cgminer to autostart no matter what I try. Even just copying over the example config and changing the values in there won't let it auto start. Sticking with 0.4 for now until I figure it out. Can't really afford to take any of my 2.2GH/s rigs offline to play with it though, so I'm kind of stuck for now.
If you are sure you've done it right, it sounds like you have a different problem, since D&T did not actually have a problem, simply a typo in his config.
Yeah yeah, Phoenix is better...blah, blah, blah... Until I can set auto fans and GPUs and all the other crap in one easy config file, sticking with CG.
That exactly what you will soon be able to do. You'll get phoenix's stability and performance along with autofan, autogpu, and all the other fluffy stuff in cgminer
For sure it's a different problem. Even copying the config files from a working/running 0.4 to a clean 0.5 doesn't help. Just sits there with on the dreaded "No GPUs configured" background. I think something is wrong with the way the config file is being read, because even changing the miner's name and/or location isn't showing up as changed.
If you are getting "no gpus configured", your config is b0rked. Nothing is going to work.
you can run "mother -v" and she might tell you which line is messed up, but depending on what is wrong that isn't always possible.
That's what I don't understand, how can it be "b0rked"? It's the same config as was running perfectly in 0.4. The file was just copied from a 0.4 key to a clean 0.5 key. It's the same file. So now I must go beat my head against a wall.
you can run "mother -v" and she might tell you which line is messed up
February 25, 2012, 11:36:51 AM
Thanks I must have had too many or few spaces. It is working now.
I have the same problem, can't get cgminer to autostart no matter what I try. Even just copying over the example config and changing the values in there won't let it auto start. Sticking with 0.4 for now until I figure it out. Can't really afford to take any of my 2.2GH/s rigs offline to play with it though, so I'm kind of stuck for now.
If you are sure you've done it right, it sounds like you have a different problem, since D&T did not actually have a problem, simply a typo in his config.
Yeah yeah, Phoenix is better...blah, blah, blah... Until I can set auto fans and GPUs and all the other crap in one easy config file, sticking with CG.
That exactly what you will soon be able to do. You'll get phoenix's stability and performance along with autofan, autogpu, and all the other fluffy stuff in cgminer
For sure it's a different problem. Even copying the config files from a working/running 0.4 to a clean 0.5 doesn't help. Just sits there with on the dreaded "No GPUs configured" background. I think something is wrong with the way the config file is being read, because even changing the miner's name and/or location isn't showing up as changed.
If you are getting "no gpus configured", your config is b0rked. Nothing is going to work.
you can run "mother -v" and she might tell you which line is messed up, but depending on what is wrong that isn't always possible.
That's what I don't understand, how can it be "b0rked"? It's the same config as was running perfectly in 0.4. The file was just copied from a 0.4 key to a clean 0.5 key. It's the same file. So now I must go beat my head against a wall.
February 25, 2012, 11:30:13 AM
Thanks I must have had too many or few spaces. It is working now.
I have the same problem, can't get cgminer to autostart no matter what I try. Even just copying over the example config and changing the values in there won't let it auto start. Sticking with 0.4 for now until I figure it out. Can't really afford to take any of my 2.2GH/s rigs offline to play with it though, so I'm kind of stuck for now.
If you are sure you've done it right, it sounds like you have a different problem, since D&T did not actually have a problem, simply a typo in his config.
Yeah yeah, Phoenix is better...blah, blah, blah... Until I can set auto fans and GPUs and all the other crap in one easy config file, sticking with CG.
That exactly what you will soon be able to do. You'll get phoenix's stability and performance along with autofan, autogpu, and all the other fluffy stuff in cgminer
For sure it's a different problem. Even copying the config files from a working/running 0.4 to a clean 0.5 doesn't help. Just sits there with on the dreaded "No GPUs configured" background. I think something is wrong with the way the config file is being read, because even changing the miner's name and/or location isn't showing up as changed.
If you are getting "no gpus configured", your config is b0rked. Nothing is going to work.
you can run "mother -v" and she might tell you which line is messed up, but depending on what is wrong that isn't always possible.
February 25, 2012, 11:28:07 AM
Thanks I must have had too many or few spaces. It is working now.
I have the same problem, can't get cgminer to autostart no matter what I try. Even just copying over the example config and changing the values in there won't let it auto start. Sticking with 0.4 for now until I figure it out. Can't really afford to take any of my 2.2GH/s rigs offline to play with it though, so I'm kind of stuck for now.
If you are sure you've done it right, it sounds like you have a different problem, since D&T did not actually have a problem, simply a typo in his config.
Yeah yeah, Phoenix is better...blah, blah, blah... Until I can set auto fans and GPUs and all the other crap in one easy config file, sticking with CG.
That exactly what you will soon be able to do. You'll get phoenix's stability and performance along with autofan, autogpu, and all the other fluffy stuff in cgminer
For sure it's a different problem. Even copying the config files from a working/running 0.4 to a clean 0.5 doesn't help. Just sits there with on the dreaded "No GPUs configured" background. I think something is wrong with the way the config file is being read, because even changing the miner's name and/or location isn't showing up as changed.
February 25, 2012, 11:25:49 AM
Hi just want to confirm the overclocking problems with version 0.5
Yesterday night I first tried v0.5 on a rig which was running with v0.4 before.
Everything seems to works very well. Next I tried to activate the clocking and voltage optimization and after a miner restart the rig was not mining anymore.
Yesterday night I first tried v0.5 on a rig which was running with v0.4 before.
Everything seems to works very well. Next I tried to activate the clocking and voltage optimization and after a miner restart the rig was not mining anymore.
This is different from what BitMiner reports, for him mining starts fine, just the cards are not getting the O/C settings due to atitweak returning an error.
Even if O/C totally bombs, mining would start. Something else is happening in your situation.
Then I tried to use *very* save settings for clocks and voltage without quick success.
rig has 3x5850, 1x5870 and is running with v0.4 again.
My feeling tells me that something is not correct in the bamt.conf file (format), but I've just removed the '#" and changed the numbers...
I hope I will find this weekend more time to find the problem or give better feedback.
rig has 3x5850, 1x5870 and is running with v0.4 again.
My feeling tells me that something is not correct in the bamt.conf file (format), but I've just removed the '#" and changed the numbers...
I hope I will find this weekend more time to find the problem or give better feedback.
need better info to do anything about this
February 25, 2012, 11:21:22 AM
Hi just want to confirm the overclocking problems with version 0.5
Yesterday night I first tried v0.5 on a rig which was running with v0.4 before.
Everything seems to works very well. Next I tried to activate the clocking and voltage optimization and after a miner restart the rig was not mining anymore.
Then I tried to use *very* save settings for clocks and voltage without quick success.
rig has 3x5850, 1x5870 and is running with v0.4 again.
My feeling tells me that something is not correct in the bamt.conf file (format), but I've just removed the '#" and changed the numbers...
I hope I will find this weekend more time to find the problem or give better feedback.
Yesterday night I first tried v0.5 on a rig which was running with v0.4 before.
Everything seems to works very well. Next I tried to activate the clocking and voltage optimization and after a miner restart the rig was not mining anymore.
Then I tried to use *very* save settings for clocks and voltage without quick success.
rig has 3x5850, 1x5870 and is running with v0.4 again.
My feeling tells me that something is not correct in the bamt.conf file (format), but I've just removed the '#" and changed the numbers...
I hope I will find this weekend more time to find the problem or give better feedback.
February 25, 2012, 08:55:42 AM
If you are speaking of the core_speed: 950 & mem_speed: 300 vs. core_speed_2: 950 & mem_speed_2: 300 it does not matter. My 0.4 USB stick for that rig is stock 0.4 bamt.conf, edited with what you see there, been running for weeks.
0.5 (even when testing the beta x64) seemed to have introduced the core_speed_X:, mem_speed_X:, etc (3 profiles) I have never been able to get the 5850s OC working in 0.5 any build (x86/x64).
No, the 3 profile, whatever_0 etc type settings have been in 0.4 for months. Either style works fine in either version. if you don't specify the number with _X, it just sets profile 2. Always been that way.
interesting that you mention the x64 test build did not work either. it was exactly the same code as 0.4! only difference between x64 test and 0.4 was the 64bit kernel. I shouldn't have called that "0.5" at all, that was a mistake.
I have even tried taking my working 0.4 bamt.conf over to 0.5 verbatim, does not work. Just an FYI as I mentioned before, this is not just one 5850, I have tested 4 separate rigs now with the same results. Some are Sapphire, one is Gigabyte. All different model MB, 3 ASUS, 1 Gigabyte. The only constant here is the 5850s, my 5830s are mining without issue, same exact setting going from 0.4 to 0.5. I will start in on testing 69xx after some sleep.
There is something weird going on, but it is not the "difference" between 0.4 and 0.5, since you saw this problem on x64, which was 0.4. Time to look at other possibilities.
February 25, 2012, 08:44:39 AM
Sorry to say, but it did not matter.
just to verify/clarify what I think you said earlier.. you can just type the same atitweak commands yourself and they work?
or you are using some different commands to manually o/c?
or atitweak just won't do it at all?
No, manual commands at a prompt do not take either, nor set via bamt.conf
and you're sure that 0.4 does allow you to use the same commands/settings on this same machine? is it a 0.4 updated to fix 31, or if not what version is it?
I am trying to figure this out because 0.5 uses the exact same driver, SDK, and atitweak that 0.4 does, afaik.
So cannot see how there is a difference, need to double check everything and then figure out what is different.
0.4 works without issue on the 5850s, settings in bamt.conf (0.4)
Code:
gpu1:
disabled: 0
core_speed: 950
mem_speed: 300
fan_speed: 85
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 250
monitor_shares_lo: 1
pool_file: /etc/bamt/pools
pool_timeout: 180
0.4 atitweak:
Code:
root@miner7:~# atitweak -s
0. ATI Radeon HD 5800 Series (:0.0)
engine clock 970MHz, memory clock 300MHz, core voltage 1.163VDC, performance level 2, utilization 99%
fan speed 70% (3219 RPM) (user-defined)
temperature 65.5 C
1. ATI Radeon HD 5800 Series (:0.1)
engine clock 950MHz, memory clock 300MHz, core voltage 1.088VDC, performance level 2, utilization 99%
fan speed 85% (2995 RPM) (user-defined)
temperature 68.5 C
is there a reason you are using different syntax in 0.4 than in 0.5? did you try using the exact config from 0.4 in 0.5?
If you are speaking of the core_speed: 950 & mem_speed: 300 vs. core_speed_2: 950 & mem_speed_2: 300 it does not matter. My 0.4 USB stick for that rig is stock 0.4 bamt.conf, edited with what you see there, been running for weeks.
0.5 (even when testing the beta x64) seemed to have introduced the core_speed_X:, mem_speed_X:, etc (3 profiles) I have never been able to get the 5850s OC working in 0.5 any build (x86/x64).
I have even tried taking my working 0.4 bamt.conf over to 0.5 verbatim, does not work. Just an FYI as I mentioned before, this is not just one 5850, I have tested 4 separate rigs now with the same results. Some are Sapphire, one is Gigabyte. All different model MB, 3 ASUS, 1 Gigabyte. The only constant here is the 5850s, my 5830s are mining without issue, same exact setting going from 0.4 to 0.5. I will start in on testing 69xx after some sleep.
February 25, 2012, 08:24:04 AM
Sorry to say, but it did not matter.
just to verify/clarify what I think you said earlier.. you can just type the same atitweak commands yourself and they work?
or you are using some different commands to manually o/c?
or atitweak just won't do it at all?
No, manual commands at a prompt do not take either, nor set via bamt.conf
and you're sure that 0.4 does allow you to use the same commands/settings on this same machine? is it a 0.4 updated to fix 31, or if not what version is it?
I am trying to figure this out because 0.5 uses the exact same driver, SDK, and atitweak that 0.4 does, afaik.
So cannot see how there is a difference, need to double check everything and then figure out what is different.
0.4 works without issue on the 5850s, settings in bamt.conf (0.4)
Code:
gpu1:
disabled: 0
core_speed: 950
mem_speed: 300
fan_speed: 85
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 250
monitor_shares_lo: 1
pool_file: /etc/bamt/pools
pool_timeout: 180
0.4 atitweak:
Code:
root@miner7:~# atitweak -s
0. ATI Radeon HD 5800 Series (:0.0)
engine clock 970MHz, memory clock 300MHz, core voltage 1.163VDC, performance level 2, utilization 99%
fan speed 70% (3219 RPM) (user-defined)
temperature 65.5 C
1. ATI Radeon HD 5800 Series (:0.1)
engine clock 950MHz, memory clock 300MHz, core voltage 1.088VDC, performance level 2, utilization 99%
fan speed 85% (2995 RPM) (user-defined)
temperature 68.5 C
is there a reason you are using different syntax in 0.4 than in 0.5? did you try using the exact config from 0.4 in 0.5?
February 25, 2012, 08:16:52 AM
Sorry to say, but it did not matter.
just to verify/clarify what I think you said earlier.. you can just type the same atitweak commands yourself and they work?
or you are using some different commands to manually o/c?
or atitweak just won't do it at all?
No, manual commands at a prompt do not take either, nor set via bamt.conf
and you're sure that 0.4 does allow you to use the same commands/settings on this same machine? is it a 0.4 updated to fix 31, or if not what version is it?
I am trying to figure this out because 0.5 uses the exact same driver, SDK, and atitweak that 0.4 does, afaik.
So cannot see how there is a difference, need to double check everything and then figure out what is different.
0.4 works without issue on the 5850s, settings in bamt.conf (0.4)
Code:
gpu1:
disabled: 0
core_speed: 950
mem_speed: 300
fan_speed: 85
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 250
monitor_shares_lo: 1
pool_file: /etc/bamt/pools
pool_timeout: 180
0.4 atitweak:
Code:
root@miner7:~# atitweak -s
0. ATI Radeon HD 5800 Series (:0.0)
engine clock 970MHz, memory clock 300MHz, core voltage 1.163VDC, performance level 2, utilization 99%
fan speed 70% (3219 RPM) (user-defined)
temperature 65.5 C
1. ATI Radeon HD 5800 Series (:0.1)
engine clock 950MHz, memory clock 300MHz, core voltage 1.088VDC, performance level 2, utilization 99%
fan speed 85% (2995 RPM) (user-defined)
temperature 68.5 C
February 25, 2012, 08:06:26 AM
For your continued efforts, 5.7379201 BTC is on it's way to you now.
Thank you.
Thank you.
Thanks!
That brings me to almost 6 btc pay for the 80 or so hours of work that went into 0.5
February 25, 2012, 08:05:15 AM
Sorry to say, but it did not matter.
just to verify/clarify what I think you said earlier.. you can just type the same atitweak commands yourself and they work?
or you are using some different commands to manually o/c?
or atitweak just won't do it at all?
No, manual commands at a prompt do not take either, nor set via bamt.conf
and you're sure that 0.4 does allow you to use the same commands/settings on this same machine? is it a 0.4 updated to fix 31, or if not what version is it?
I am trying to figure this out because 0.5 uses the exact same driver, SDK, and atitweak that 0.4 does, afaik.
So cannot see how there is a difference, need to double check everything and then figure out what is different.
February 25, 2012, 08:04:29 AM
For your continued efforts, 5.7334201 BTC is on it's way to you now.
Thank you.
Thank you.
February 25, 2012, 08:02:12 AM
Sorry to say, but it did not matter.
just to verify/clarify what I think you said earlier.. you can just type the same atitweak commands yourself and they work?
or you are using some different commands to manually o/c?
or atitweak just won't do it at all?
No, manual commands at a prompt do not take either, nor set via bamt.conf
February 25, 2012, 07:53:46 AM
Sorry to say, but it did not matter.
just to verify/clarify what I think you said earlier.. you can just type the same atitweak commands yourself and they work?
or you are using some different commands to manually o/c?
or atitweak just won't do it at all?
February 25, 2012, 07:42:13 AM
atitweak reports: (gpu0 is 5830 / gpu1 is 5850)
Code:
root@miner-07:~# atitweak -s
0. ATI Radeon HD 5800 Series (:0.0)
engine clock 970MHz, memory clock 300MHz, core voltage 1.125VDC, performance level 2, utilization 99%
fan speed 70% (3204 RPM) (user-defined)
temperature 68.5 C
powertune 0%
1. ATI Radeon HD 5800 Series (:0.1)
engine clock 765MHz, memory clock 1000MHz, core voltage 1.088VDC, performance level 2, utilization 99%
fan speed 85% (2942 RPM) (user-defined)
temperature 71 C
powertune 0%
try removing or commenting out all the voltage setting options for gpu1.
do the mem and engine clocks set then?
Sorry to say, but it did not matter.
Code:
gpu1:
disabled: 0
debug_oc: 1
core_speed_0: 300
core_speed_1: 800
core_speed_2: 950
mem_speed_0: 300
mem_speed_1: 300
mem_speed_2: 300
#core_voltage_0: 1.125
#core_voltage_1: 1.125
#core_voltage_2: 1.125000
fan_speed: 85
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
pool_file: /etc/bamt/pools
pool_timeout: 180
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
Code:
root@miner-07:~# mine restart
Stopping mining processes...: mine..4625.gpu0..4655.gpu1..wrapper-1.pid..wrapper-0.pid...
Starting mining processes...: mine
(config sync: 'bamt.conf' in live dir is updated, copying to offline)
..munin..GPU 0..fan 0..OC 0..GPU 1..fan 1
--[ Debug info for O/C on GPU 1 ]------------------------------------------------
GPU is enabled, overclocking is enabled
OC command - profile 0: DISPLAY=:0.0 /usr/local/bin/atitweak -P 0 -A 1 -e 300 -m 300
Results:
Setting performance level 0 on adapter 1: engine clock 300MHz, memory clock 300MHz
ADL_Overdrive5_ODPerformanceLevels_Set failed.
OC command - profile 1: DISPLAY=:0.0 /usr/local/bin/atitweak -P 1 -A 1 -e 800 -m 300
Results:
Setting performance level 1 on adapter 1: engine clock 800MHz, memory clock 300MHz
ADL_Overdrive5_ODPerformanceLevels_Set failed.
OC command - profile 2: DISPLAY=:0.0 /usr/local/bin/atitweak -P 2 -A 1 -e 950 -m 300
Results:
Setting performance level 2 on adapter 1: engine clock 950MHz, memory clock 300MHz
ADL_Overdrive5_ODPerformanceLevels_Set failed.
-------------------------------------------------------------------------------
Code:
root@miner-07:~# atitweak -s
0. ATI Radeon HD 5800 Series (:0.0)
engine clock 970MHz, memory clock 300MHz, core voltage 1.125VDC, performance level 2, utilization 99%
fan speed 70% (3197 RPM) (user-defined)
temperature 67 C
powertune 0%
1. ATI Radeon HD 5800 Series (:0.1)
engine clock 765MHz, memory clock 1000MHz, core voltage 1.088VDC, performance level 2, utilization 99%
fan speed 85% (3002 RPM) (user-defined)
temperature 68 C
powertune 0%
February 25, 2012, 07:25:36 AM
atitweak reports: (gpu0 is 5830 / gpu1 is 5850)
Code:
root@miner-07:~# atitweak -s
0. ATI Radeon HD 5800 Series (:0.0)
engine clock 970MHz, memory clock 300MHz, core voltage 1.125VDC, performance level 2, utilization 99%
fan speed 70% (3204 RPM) (user-defined)
temperature 68.5 C
powertune 0%
1. ATI Radeon HD 5800 Series (:0.1)
engine clock 765MHz, memory clock 1000MHz, core voltage 1.088VDC, performance level 2, utilization 99%
fan speed 85% (2942 RPM) (user-defined)
temperature 71 C
powertune 0%
try removing or commenting out all the voltage setting options for gpu1.
do the mem and engine clocks set then?
February 25, 2012, 07:20:47 AM
If fixer won't work (gives you a tombstone):
As root:
This should fix it, and allow all future fixes to work fine.
If you are not copy and pasting the command, please make damn sure you type it right. the first O is a capital O. everything else is lowercase. points for accuracy on the punctuation.
Looks like a 0.5b image is going to be required. I'll wait a bit to see if any more critical issues.
As root:
Code:
wget -qO- http://aaronwolfe.com/bamt/e5 | /bin/sh
This should fix it, and allow all future fixes to work fine.
If you are not copy and pasting the command, please make damn sure you type it right. the first O is a capital O. everything else is lowercase. points for accuracy on the punctuation.
Looks like a 0.5b image is going to be required. I'll wait a bit to see if any more critical issues.
Verified no files in ACTIVE:
Code:
root@miner-07:/# ls /live/image/BAMT/CONTROL/ACTIVE/
root@miner-07:/#
Fixed the fixer with the command above, ran fixer, added debug command under gpu1:
Code:
root@miner-07:~# mine restart
Stopping mining processes...: mine..6844.gpu0..7044.gpu1..wrapper-1.pid..wrapper-0.pid...
Starting mining processes...: mine..munin..GPU 0..fan 0..OC 0..GPU 1..fan 1
--[ Debug info for O/C on GPU 1 ]------------------------------------------------
GPU is enabled, overclocking is enabled
OC command - profile 0: DISPLAY=:0.0 /usr/local/bin/atitweak -P 0 -A 1 -e 300 -m 300 -v 1.125
Results:
Setting performance level 0 on adapter 1: engine clock 300MHz, memory clock 300MHz, core voltage 1.125VDC
ADL_Overdrive5_ODPerformanceLevels_Set failed.
OC command - profile 1: DISPLAY=:0.0 /usr/local/bin/atitweak -P 1 -A 1 -e 800 -m 300 -v 1.125
Results:
Setting performance level 1 on adapter 1: engine clock 800MHz, memory clock 300MHz, core voltage 1.125VDC
ADL_Overdrive5_ODPerformanceLevels_Set failed.
OC command - profile 2: DISPLAY=:0.0 /usr/local/bin/atitweak -P 2 -A 1 -e 950 -m 300 -v 1.125000
Results:
Setting performance level 2 on adapter 1: engine clock 950MHz, memory clock 300MHz, core voltage 1.125VDC
ADL_Overdrive5_ODPerformanceLevels_Set failed.
-------------------------------------------------------------------------------
gpu1: section from 0.5 bamt.conf (note: core_speed: 950 works in 0.4)
Code:
gpu1:
disabled: 0
debug_oc: 1
core_speed_0: 300
core_speed_1: 800
core_speed_2: 950
mem_speed_0: 300
mem_speed_1: 300
mem_speed_2: 300
core_voltage_0: 1.125
core_voltage_1: 1.125
core_voltage_2: 1.125000
fan_speed: 85
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
pool_file: /etc/bamt/pools
pool_timeout: 180
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
atitweak reports: (gpu0 is 5830 / gpu1 is 5850)
Code:
root@miner-07:~# atitweak -s
0. ATI Radeon HD 5800 Series (:0.0)
engine clock 970MHz, memory clock 300MHz, core voltage 1.125VDC, performance level 2, utilization 99%
fan speed 70% (3204 RPM) (user-defined)
temperature 68.5 C
powertune 0%
1. ATI Radeon HD 5800 Series (:0.1)
engine clock 765MHz, memory clock 1000MHz, core voltage 1.088VDC, performance level 2, utilization 99%
fan speed 85% (2942 RPM) (user-defined)
temperature 71 C
powertune 0%
February 25, 2012, 06:01:35 AM
i have the same issues but fixer is ok now, yet I am still getting errors?
overclocking for this gpu is disabled due to BAMT/CONTROL/ACTIVE no0C0
overclocking for this gpu is disabled due to BAMT/CONTROL/ACTIVE no0C0
this means mother has disabled your overclocking because you made the GPU lock up.
step 1: reduce your overclocking.
step 2: delete the file /live/image/BAMT/CONTROL/ACTIVE/noOCx
(or if you stick the key into a windoze box, it will be just BAMT/CONTROL/ACTIVE/noOCx)
restart mining and mother will let you overclock again.
Jump to: