BAMT is for mining on dedicated rigs. Linuxcoin has lots of other stuff, like a wallet. Depends on what you are looking for. |
|
|
|
|
Great job with BIP voting inaba, one more reason for miners to use this pool. If this is the only pool offering voting, you should put an post on the discussion board, see if brings in more miners until it gets moved.
|
|
|
|
Note also that you are having it being disabled and reading OFF. There is only one place in the code where cgminer does this itself - when it hits the thermal cutoff limit. Now it is possible there is some code convolution issue going on somehow that makes the fan not rise when one of the GPUs is being restarted. Note that your bug report shows thread 2 being idle (which would be GPU 1) and then it proceeds to disable threads 4 and 5 (being GPU 2)... Interesting... I'll audit the code, but perhaps try it without auto-fan on, setting what you know to be a safe static fan speed and see if the problem persists.
Running 10+ hours without auto-fan and no errors. I'll update if I get one, but looks promising. |
|
|
|
That rig runs fairly cool so I'll try overnight without auto-fan. Here is the rest of the errors from 2.2.1 sessions - I just lowered clock speeds for the different sessions. [2012-02-02 18:22:19] Thread 1 idle for more than 60 seconds, GPU 1 declared SICK!
[2012-02-02 18:22:19] Attempting to restart GPU
[2012-02-02 18:22:19] Thread 2 still exists, killing it off
[2012-02-02 18:22:19] Thread 3 still exists, killing it off
[2012-02-02 18:22:19] Thread 2 restarted
[2012-02-02 18:22:20] Thread 3 restarted
[2012-02-02 18:22:21] Accepted 00000000.40372a1e.d75ae9ba GPU 0 thread 0 pool 0
[2012-02-02 18:22:21] Thread 2 being disabled
[2012-02-02 18:22:21] Thread 3 being disabled
[2012-02-02 17:58:17] Thread 3 idle for more than 60 seconds, GPU 3 declared SICK!
[2012-02-02 17:58:17] Attempting to restart GPU
[2012-02-02 17:58:17] Thread 6 still exists, killing it off
[2012-02-02 17:58:17] Thread 7 still exists, killing it off
[2012-02-02 17:58:18] Thread 6 restarted
[2012-02-02 17:58:19] Thread 7 restarted
[2012-02-03 21:19:13] Thread 4 still exists, killing it off
[2012-02-03 21:19:13] Thread 5 still exists, killing it off
[2012-02-03 21:19:14] Thread 4 restarted
[2012-02-03 21:19:14] Accepted 00000000.0cd03974.6e1c40e3 GPU 0 thread 1 pool 0
[2012-02-03 21:19:14] Thread 5 restarted
[2012-02-03 21:19:15] Thread 4 being disabled
[2012-02-03 21:19:16] Thread 5 being disabled
[2012-02-03 20:47:14] Thread 2 idle for more than 60 seconds, GPU 2 declared SICK!
[2012-02-03 20:47:14] Attempting to restart GPU
[2012-02-03 20:47:14] Thread 4 still exists, killing it off
[2012-02-03 20:47:14] Thread 5 still exists, killing it off
[2012-02-03 20:47:14] Thread 4 restarted
[2012-02-03 20:47:15] Accepted 00000000.b422fb13.d18b69ee GPU 1 thread 3 pool 0
[2012-02-03 20:47:15] Thread 5 restarted
[2012-02-03 20:47:15] Accepted 00000000.8db73352.22b376e6 GPU 0 thread 1 pool 0
[2012-02-03 20:47:16] Thread 4 being disabled
[2012-02-03 20:47:16] Thread 5 being disabled
[2012-02-04 17:29:18] Thread 2 idle for more than 60 seconds, GPU 2 declared SICK!
[2012-02-04 17:29:18] Attempting to restart GPU
[2012-02-04 17:29:18] Thread 4 still exists, killing it off
[2012-02-04 17:29:18] Thread 5 still exists, killing it off
[2012-02-04 17:29:19] Thread 4 restarted
[2012-02-04 17:29:19] Thread 5 restarted
[2012-02-04 17:29:20] Thread 4 being disabled
[2012-02-04 17:29:20] Thread 5 being disabled
|
|
|
|
Well 2.2.1 has the dual GPU linkage going on which 2.1.2 does not. Bear in mind the auto fanspeed control now looks at the temps of both GPUs, but overall this should run things cooler rather than hotter so unless you have some specific setup, or maybe have autofan off on one of the devices or different clock settings... Also, have you checked it's actually detecting the right card in the right device and linking the right devices?
I use these flags -I 8 --gpu-engine 950,850,830,950 --gpu-memclock 850,180,180,850 --auto-fan --temp-target 75 --temp-overheat 82 How do I check it's detecting right? It lists in the same order as 2.1.2. --gpu-reorder worth checking? |
|
|
|
Using 2.2.1 on a mixed card rig [2012-02-05 00:01:17] CL Platform vendor: Advanced Micro Devices, Inc.
[2012-02-05 00:01:17] CL Platform name: AMD Accelerated Parallel Processing
[2012-02-05 00:01:17] CL Platform version: OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10)
[2012-02-05 00:01:17] GPU 0 AMD Radeon HD 6800 Series hardware monitoring enabled
[2012-02-05 00:01:17] GPU 1 ATI Radeon HD 5900 Series hardware monitoring enabled
[2012-02-05 00:01:17] GPU 2 ATI Radeon HD 5900 Series hardware monitoring enabled
[2012-02-05 00:01:17] Failed to ADL_Overdrive5_FanSpeedInfo_Get
[2012-02-05 00:01:17] GPU 3 AMD Radeon HD 6800 Series hardware monitoring enabled
[2012-02-05 00:01:17] Dual GPUs detected: 2 and 1
[2012-02-05 00:01:17] 4 GPU devices detected And the second core of the 5970 keeps showing OFF after 12-18 hrs running with this error [2012-02-04 03:37:42] Thread 2 idle for more than 60 seconds, GPU 2 declared SICK!
[2012-02-04 03:37:42] Attempting to restart GPU
[2012-02-04 03:37:42] Thread 4 still exists, killing it off
[2012-02-04 03:37:42] Thread 5 still exists, killing it off
[2012-02-04 03:37:42] Thread 4 restarted
[2012-02-04 03:37:43] Thread 5 restarted
[2012-02-04 03:37:44] Thread 4 being disabled
[2012-02-04 03:37:44] Thread 5 being disabled I first thought it was clocks, but it has been running for 5 months at the same clocks. I lowered them a few times anyway but still the same error. If I go back to 2.1.2 it runs fine, 24 + hours now.  |
|
|
|
|
If you use Ubuntu 11.10 there are built binaries that you just unzip and run, assuming you have Catalyst and SDK installed. Kano has step by step setup. Or just put BAMT on a USB and boot it on your Windows machine. Everything is installed already, just edit one config file and profit. (sorry for not adding links, posting from phone)
|
|
|
|
Sent 5 more  |
|
|
|
So what miner should I use to mine with a GPU (6950)?
I have 6 6950's using cgminer and eclipse. No problems. Check your config. |
|
|
|
|
You could just use the pre-built binaries on the fist page of cgminer thread......
|
|
|
|
Is there another pro BIP 17 pool out there? At least pool.itzod.ru, and you can use BIP 17-patched bitcoind with p2pool. I think EclipseMC might support BIP 17 as well, but I'm not sure if they have the patch deployed live yet. Inaba? |
|
|
|
|
I have a GD70 with a sempron, 2GB ram, and would be using BAMT, and 5970's on the way. Just have a 850W PSU though. I'll just pick up one of these Seasonics. Thanks.
|
|
|
|
|
That is nice. Have to get a couple. D&T how many watts your 3x5970 rig pull?
|
|
|
|
|
Unless you flashed your bios the 6xxx series has a memclock limit. If that is supposed to say 6950 your memclock can be no more than 125 less than engine clock.
|
|
|
|
"auto-gpu" : true, "gpu-engine" : "942", "auto-fan" : true - the card will throttle itself down to its stock speed on exceeding temp-overheat, mining threads will be disabled on exceeding "temp-cutoff". The fan will speed up to 100% on temp-overheat.
I don't think this is right. I use auto-gpu and auto-fan on a rig and if fan is at 85% gpu is throttled at target-temp (75 default) + temp-hysterisis (3 default). I think temp-overheat is just used to move the fan to 100% after other options fail. If that doesn't work temp-cutoff is the failsafe. |
|
|
|
Tried the --gpu-memclock on a 6950, it doesn't work. Memory clock doesn't change when i start cgminer.
While --gpu-engine work perfectly and change the core clock.
Oh well not a problem, i'll still use msi afterburner for changing clocks
Except that, cgminer work without problems.
6950's have a memclock limit of engine -125. Try setting --gpu-memdiff -125 or just make sure the mem clock is no more than 125 less then engine clock. |
|
|
|
+ "temp-cutoff" : "79",
The question is will temp-cutoff be enforced even if auto-gpu is false? What about temp-overheat? I think they are just would be good to get confirmation from the code before someone relies on that. From what I understand temp-overheat is only used to move the fan from 85% to 100% only when auto-fan is used. If auto-fan and auto-gpu are set then the gpu clocks will be lowered first before the fan jumps to 100%. Which would lead me to believe temp-cutoff is not set without auto-gpu. If I set auto-gpu and gpu-engine X (no range) will it keep a static engine speed? |
|
|
|
Only time I have seen OFF is when the card temp exceeded --temp-cutoff value. If you don't set a --temp-cutoff I am not sure what it defaults to.
--temp-cutoff <arg> Temperature where a GPU device will be automatically disabled, one value or comma separated list (default: 95) Will it still shut off without using --auto-gpu? I just realized I have a rig without --auto-gpu because I want the clocks fixed, but does that mean it will burn up when the AC breaks? |
|
|
|
I'd think 6 GPU's is pretty good! I only have 2 6950's  However ... DISPLAY is probably missing from that run? It would be better if they were mining  cgminer-2.2.1/cgminer -ndevs
[2012-01-31 22:27:22] CL Platform vendor: Advanced Micro Devices, Inc.
[2012-01-31 22:27:22] CL Platform name: AMD Accelerated Parallel Processing
[2012-01-31 22:27:22] CL Platform version: OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10)
[2012-01-31 22:27:22] GPU 0 AMD Radeon HD 6900 Series hardware monitoring enabled
[2012-01-31 22:27:22] Setting GPU 0 engine clock to 850
[2012-01-31 22:27:22] Setting GPU 0 memory clock to 725
[2012-01-31 22:27:22] GPU 1 AMD Radeon HD 6900 Series hardware monitoring enabled
[2012-01-31 22:27:22] Setting GPU 1 engine clock to 850
[2012-01-31 22:27:22] Setting GPU 1 memory clock to 725
[2012-01-31 22:27:22] GPU 2 AMD Radeon HD 6900 Series hardware monitoring enabled
[2012-01-31 22:27:22] Setting GPU 2 engine clock to 850
[2012-01-31 22:27:22] Setting GPU 2 memory clock to 725
[2012-01-31 22:27:22] GPU 3 AMD Radeon HD 6900 Series hardware monitoring enabled
[2012-01-31 22:27:22] Setting GPU 3 engine clock to 850
[2012-01-31 22:27:22] Setting GPU 3 memory clock to 725
[2012-01-31 22:27:22] GPU 4 AMD Radeon HD 6900 Series hardware monitoring enabled
[2012-01-31 22:27:22] Setting GPU 4 engine clock to 850
[2012-01-31 22:27:22] Setting GPU 4 memory clock to 725
[2012-01-31 22:27:22] GPU 5 AMD Radeon HD 6900 Series hardware monitoring enabled
[2012-01-31 22:27:22] Setting GPU 5 engine clock to 850
[2012-01-31 22:27:22] Setting GPU 5 memory clock to 725
[2012-01-31 22:27:22] 6 GPU devices detected
That's better (I think), but I tried to mine and it disabled a few cards then locked up  It's a remote rig so I'll have to look some more tomorrow. |
|
|
|
|
Show Posts
