>> Bitcoin Mining Power Could be Put to Better Use
If you want to mine Bitcoin then do it. If you want to do something else with your computing power then do that.
I'm tired of people telling us our hashing could be doing something better.
I'll be the one to decide how to use my personal resources. THANK YOU VERY MUCH. Sam
|
|
|
Anyone knows a solution without using dummy plugs?
Sure, find the catalyst version that doesn't need them.
|
|
|
updating to 3.1.1 got me a 5 mhash/s on my 7970 ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) ! is there a 3.1.1. for windows too? I can't find to download it. You could click on the link in the top post.
|
|
|
soryy about the post --temp-cutoff 75 it was just for testing purpose to see when cgminer cuts off gpu and if it will starts again when temperature drops.
--temp-target <arg> Target temperature when automatically managing fan and GPU speeds (default: 75) --temp-overheat <arg> Overheat temperature when automatically managing fan and GPU speeds (default: 85) --temp-cutoff <arg> Temperature where a device will be automatically disabled, one value or comma separated list (default: 95) As I said I think the temp cutoff requires manual interaction whereas the temp overheat is where it recovers from. So are you working yet? yes it works ok. thank you but as I said maybe developer will think about more auto setup cgminer which will lower gpu engine with fan settings or temperature settings cut off doesnt restart gpu Yes, that would be a great new feature. I wonder why he never thought of that. Anyway I'm glad your running without burning up your GPU(s). Good Luck, Sam
|
|
|
soryy about the post --temp-cutoff 75 it was just for testing purpose to see when cgminer cuts off gpu and if it will starts again when temperature drops.
--temp-target <arg> Target temperature when automatically managing fan and GPU speeds (default: 75) --temp-overheat <arg> Overheat temperature when automatically managing fan and GPU speeds (default: 85) --temp-cutoff <arg> Temperature where a device will be automatically disabled, one value or comma separated list (default: 95) As I said I think the temp cutoff requires manual interaction whereas the temp overheat is where it recovers from. So are you working yet?
|
|
|
I just tested this on my PC at home on radeon 6850 --auto-gpu --gpu-engine 200-960 --auto-fan --gpu-fan 50-85 --temp-target 75 --temp-overheat 85 --temp-cutoff 75 and device recovered to temperature below target, re enabling Stratum from pool 0 detected new block and I get 0.000 GPU 0: 31 oC 2516RPM | 0.000/86.27Mh/s | A:1 R:0 HW:0 U:0.11/m I:5
and that 0.000 stays on 0.000
OK, in your example above your temp target is 75, your temp overheat is 85 and your temp cutoff is 75. Your telling CGMiner to target 75 as the temp you want to run and then telling it to react to the temps at 85 and then telling it to cut off the GPU at 75. So you are basically telling CGMiner to turn your GPU off. Do this on this 6850 GPU --auto-gpu --gpu-engine 200- 850 --auto-fan --gpu-fan 50-85 --temp-target 75 --temp-overheat 85 --temp-cutoff 95850 Mhz seems to be the default for this GPU. 75C is the target temp you want to run at. The fan speeds will change to maintain this temp. 85C is the temp that it will start lowering the Engine Clock. 95C is the temp it will completely turn the GPU off to protect it. And I think it will require manual action to restart it.
|
|
|
I am doing this as a part of research, which will help me to decide what to (do not) do next.
What are you doing/not doing now?
|
|
|
thanks I will test new settings for now with this old-new settings no PC has shut down. I just didn't wan't to set gpu's clock range to leave it automatically, I will set and test.
Well if you don't believe me here it is from the CGMiner Primary author. Unless you give it a range of engine clock speeds, auto-gpu can only do one thing: Turn it off when it hits 95 degrees. Give it a range of engines for it clock it down.
Yes I belive you is not question of that. One question can I set gpu clock for example on PC with 6850 and for another pc with 7850 radeon like this? --auto-gpu --gpu-engine 300-960 --gpu-memclock 250 --auto-fan --gpu-fan 50-85 --temp-target 75 --temp-overheat 85 --temp-cutoff 95 So if I understand even if 6850 doesn't work on gpu-engine 960 it will work on slow range? Or it wil freeze and shuts down? Or I must sets separatelly for 6850 and 7850? Because I plan to put in mining two laptops too which have avout 120Mhash and really like to have for all pcs one settings. If you understand me. To be realistic your not going to be able to set all of your PC's to the same settings. Different GPU's will need different settings or you will have a HUGE performance deficit for your higher end GPU's. Even the same GPU's in different PC's will most likely have different settings because every card/GPU chip has it's own unique characteristics. For your 6850 this is *probably* ok --auto-gpu --gpu-engine 300-940 --gpu-memclock 300 --auto-fan --gpu-fan 50-85 --temp-target 75 --temp-overheat 85 --temp-cutoff 95 For your 7850 --auto-gpu --gpu-engine 300-960 --gpu-memdiff 150 --auto-fan --gpu-fan 50-85 --temp-target 75 --temp-overheat 85 --temp-cutoff 95 If you don't know what your GPU engines are running at then *before* you set --gpu-engine run with just --auto-gpu and go into CGMiner's GPU screen and see what it is running at by default and use that number for your upper limit. You can also use this hardware comparison chart to help you optimize each GPU, if you want. https://en.bitcoin.it/wiki/Mining_hardware_comparisonIf you set your GPU clock too high it will either go dead and/or get a bunch of hardware error's. Sam
|
|
|
thanks I will test new settings for now with this old-new settings no PC has shut down. I just didn't wan't to set gpu's clock range to leave it automatically, I will set and test.
Well if you don't believe me here it is from the CGMiner Primary author. Unless you give it a range of engine clock speeds, auto-gpu can only do one thing: Turn it off when it hits 95 degrees. Give it a range of engines for it clock it down.
|
|
|
os2sam thank you for helping. I am looking for "universal" for ati 6850 and ati 7770 and for ati 7850 -I d --auto-gpu --auto-fan --gpu-fan 60-80 --temp-overheat 85 --temp-cutoff 95
OK, the only similar hardware I have is my 5770 and here is what I use for it. Also I have a 5830 which is the first GPU and 5770 which is my 2nd and the 5770 is driving my display -I 8,d --auto-gpu --gpu-engine 300-960,300-920 --gpu-memclock 250 --auto-fan --gpu-fan 25-85 --temp-target 75 --temp-overheat 85 --temp-cutoff 95 You HAVE to put an Engine Clock RANGE so that CGMiner can clock down to meet the target temp when the fans have done all they can. Also if you want only one set of clock range's for all your GPU's you can do that, but, you will need to select the highest engine clock of your slowest GPU and then set your low engine clock range to 300 or some low number per what ckolivas said earlier. Sam
|
|
|
It looks like to me that they are selling a 2nd 2Ghs box for $100?!?
If that is true then that is a much better deal that the 300Mhs USB thingy for 2 BTC.
If it is a 2nd box then maybe they have a supply of rejects that don't meet the needed performance and are trying to recoup some of the loss in building them?
|
|
|
thanks I will read again the gpu-temp flags section. Just one thing, why --temp-cutoff doesn't work? It won't start mining again when temp drops.... The whole time it is "Device recovered to temperature below target, re-enabling" and nothing happends, or must be there another flag for starting mining again?
From the Top Post - https://bitcointalk.org/index.php?topic=28402.msg357369#msg357369>> --temp-cutoff <arg> Temperature where a device will be automatically disabled, one value or comma separated list (default: 95) To me that implies that the GPU is disabled permanently until you take action to re-enable it. Now the verbiage in your post does imply that it is *trying* to re-enable your GPU, so I don't know why it isn't. But I would use a reasonable Temp Target around 60C to 75C, Temp Overheat of 85C to 90C and a Temp Cutoff around 95C >> --temp-overheat <arg> Overheat temperature when automatically managing fan and GPU speeds (default: 85) >> --temp-target <arg> Target temperature when automatically managing fan and GPU speeds (default: 75) Why don't you post your CGMiner command line and tell us what GPU's you are using in this rig? Maybe we can come up with something that works better? Sam
|
|
|
Any chance of adding in a section that details the fee rules used by each pool? Although this is not totally relevant for most pools to the miners (as the pools generally keep the fees) it is relevant to site operators to understand what the fee rules are used by each pool. This is especially relevant now we have 0.8.2 with the dust ( https://github.com/bitcoin/bitcoin/pull/2577) and change from 0.0005 -> 0.0001 that mining pools may or may not implement. Started to do this before the hard fork - maybe now is the time to bring it up again? Is he/you referring to the block size policy for each pool? The fee and block size policy are related so that would be nice for someone to resume. But make it a separate thread I would think. Yes, I consider them similar issues. I also agree on another thread being appropriate. Not how it should be done though. Pools would have to volunteer the information. Doing research like Mr. Hearne was doing and posting the pools information without their input was prone to a high margin for error and wasn't fair to the pools.
|
|
|
It's a great idea. It isn't related to payout method. Just mine as many pools at the same time as possible so that good luck on one pool offsets bad luck on a different one so that your reach a neutral average all the time.
Sam
Well sort of. Doesn't apply to PPS at all. Well I guess there is sometimes variance in how I think about things and how they really work ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) To me, the reason to balance between several pools at the same time would be to offset bad luck on one pool with the good luck on another. Also I don't only consider my mining profitability but also the impact on the pool itself. So when a pool offers both PPS and another payout which lessens the possibility of a loss to the pool I always choose the other payout method. Sam
|
|
|
It's a great idea. It isn't related to payout method. Just mine as many pools at the same time as possible so that good luck on one pool offsets bad luck on a different one so that your reach a neutral average all the time.
Sam
|
|
|
Any chance of adding in a section that details the fee rules used by each pool? Although this is not totally relevant for most pools to the miners (as the pools generally keep the fees) it is relevant to site operators to understand what the fee rules are used by each pool. This is especially relevant now we have 0.8.2 with the dust ( https://github.com/bitcoin/bitcoin/pull/2577) and change from 0.0005 -> 0.0001 that mining pools may or may not implement. Started to do this before the hard fork - maybe now is the time to bring it up again? Is he/you referring to the block size policy for each pool? The fee and block size policy are related so that would be nice for someone to resume. But make it a separate thread I would think.
|
|
|
ati radeon 5800 and two 6800 series and one 7800 series
Uh, ok, your previous post said you had two GPU's now we're up to 4. You should have your 7800 series in a different machine that the 5xxx and 6xxx series GPU's. Did you read this threads top post yet? If you have multiple GPU's/types in the same machine you really need to set your clock ranges per GPU. The Top Post has easy to understand examples for that. I have readed alot but still there is no extra flag for GPU TEMP. I mean two GPUs in one graphic card. I have 3 graphic cards in one PC is there not possible to have one configuration for all of them? The safe one, for now I have regulated just a --gpu-fan 55-85 it wokrs ok for now U hope it won't turn off.... The easiest way it would be a GPU-TEMP if that rise for example over 85 oC it slows down mining.... Auto Fan and gpu fan with a fan speed range is only one part of temp control. You still need to set auto gpu with an engine clock range. And there are plenty of "GPU TEMP" flags in the readme, gpu readme and top post.
|
|
|
I run a 5870, a 6970 and a 7950 in one machine. I was also running a 7770 as well, but it died. They worked OK together.
These threads are full of the troubles and pitfalls with mixing 7xxx with 5 and 6xxx GPU's. This guy is having trouble regulating his temperature so I think mixing GPU types is a little above his head at the moment. Always start with the simplest configuration and get working then and ONLY then start adding complexity. Basic T/S techniques. Sam
|
|
|
Unconfirmed Credit has been stacking up for a day or two now. The confirmations don't seem to updating on the ozcoin site.
Is there an explanation or is something amiss?
Many thanks.
Looks about right to me. Block from over 24 hours ago has 100 confirmations. It takes 120 blocks to confirm the previous block to be sure it is safe to release the funds. You can always become a VIP member and not have to wait for those confirmations. Sam
|
|
|
|