Xardas2014
|
|
October 14, 2016, 08:33:59 PM |
|
For Ethereum mining it's more about the memory speed not the processor. Both of those 8 GB cards you linked have Effective Memory Clock: 8000 MHz. If you look at the specifications for the 4 GB version it only has 7000 MHz memory. For gaming (which you said you do) you would want the higher core clock rate. So the second one would overall be better. (IMHO) Buy me one and send me one for gaming and I'll let you know I got the overclocked one. OCing the memory speed helps ETH more than the GPU speed? I noticed it helped SIA/LBRY, but not much for ETH. I got it up to 1360 and stable it seems at 1150 cvddc. 25 ETH 45 LBRY What should my memory speed, core speed, and cv/mvddc be do you think? Electric is cheap, and I need the heat any way, so going for as much speed as possible without hurting the card. Temps are staying around 77c. I run 1342MHz (stock OC for card) @1030mv. Undervolting will allow card to maintain boost clocks, increasing performance (without setting crazy power limit). Use GPU-Z to check actual core clocks.... Less power means less stress on VRMs, GPU, fans, and possibly PSU. I prefer ~70-73C temps, which I get with ~60% fan, and 80F ambient. Cards all on risers. Night they run like 64C @50% fan (~60F ambient). Thanks, what rates do you get? I'm using LBRY, with dcri 40 25ETH 44LBRY in the miner. Any editing of memory clock and volts? I'm running 2150 and auto for the volts. https://forum.ethereum.org/discussion/9650/sapphire-rx-480-nitro-oc-8gb-11260-01-20g-modded-bios-29-mh-downvolt
|
|
|
|
xeridea
|
|
October 14, 2016, 08:39:29 PM |
|
For Ethereum mining it's more about the memory speed not the processor. Both of those 8 GB cards you linked have Effective Memory Clock: 8000 MHz. If you look at the specifications for the 4 GB version it only has 7000 MHz memory. For gaming (which you said you do) you would want the higher core clock rate. So the second one would overall be better. (IMHO) Buy me one and send me one for gaming and I'll let you know I got the overclocked one. OCing the memory speed helps ETH more than the GPU speed? I noticed it helped SIA/LBRY, but not much for ETH. I got it up to 1360 and stable it seems at 1150 cvddc. 25 ETH 45 LBRY What should my memory speed, core speed, and cv/mvddc be do you think? Electric is cheap, and I need the heat any way, so going for as much speed as possible without hurting the card. Temps are staying around 77c. I run 1342MHz (stock OC for card) @1030mv. Undervolting will allow card to maintain boost clocks, increasing performance (without setting crazy power limit). Use GPU-Z to check actual core clocks.... Less power means less stress on VRMs, GPU, fans, and possibly PSU. I prefer ~70-73C temps, which I get with ~60% fan, and 80F ambient. Cards all on risers. Night they run like 64C @50% fan (~60F ambient). Thanks, what rates do you get? I'm using LBRY, with dcri 40 25ETH 44LBRY in the miner. Any editing of memory clock and volts? I'm running 2150 and auto for the volts. I get ~22MHEth 50MH LBRY with higher DCRI. I do Sia though, 24.3MH, 475MH. Stock 2000MHz memory. Most my cards I run 1260MHz and like 980mv, some down to 960mv (need to lower memory voltage, not sure what this does though).
|
Profitability over time charts for many GPUs - http://xeridea.us/chartsBTC: bc1qr2xwjwfmjn43zhrlp6pn7vwdjrjnv5z0anhjhn LTC: LXDm6sR4dkyqtEWfUbPumMnVEiUFQvxSbZ Eth: 0x44cCe2cf90C8FEE4C9e4338Ae7049913D4F6fC24
|
|
|
scryptr
Legendary
Offline
Activity: 1797
Merit: 1028
|
|
October 14, 2016, 11:56:59 PM |
|
It is true that you can't mine with 2 GB ram?
YOU CAN STILL MINE WITH 2GB RAM-- Unless your card is a GTX 750ti. I have 4 AMD R7 265 cards with 2 GB RAM, and they mine Dagger-Hashimoto at 12+ MH/s. The GTX 750ti is crippled by the way it accesses memory, and will only mine at 0.5-1.0 MH/s with Dagger-Hashimoto. The 750ti would mine scrypt twice as fast as the R7 265 card, and was considered to be in the same tier. My R7 265 cards finally paid for themselves mining Ethereum (ETH). They can mine Expanse (EXP) at almost 15MH/s. Sometime within a year or so, 2GB cards will not be able to mine ETH, but they will likely be able to mine EXP for some time. EXP is only on Epoch 13. --scryptr
|
|
|
|
GabryRox
|
|
October 15, 2016, 01:42:50 AM |
|
@Claymore, few questions:
1) -cclock: you wrote "you can overclock only", but it seems not to be true for, at least, Windows and Polaris. My 470x can be underclocked (GPU set to 1150 for all states). 2) Any chance to support -cclock and -mclock on Linux for amdgpu-pro drivers (for Polaris)? It is not said "unsupported on Linux", but does not work for me (mem can't be set to 1950 using this). 3) Any chance to support -cvddc and -mvddc on Linux for amdgpu-pro drivers? 4) Are older cards like 7950/7970 supported using amdgpu-pro drivers on Linux? 5) There is an issue on Windows when used -*clock commands: they are applied at some init stage, but for my 470x it instantly changes hashrates only for the card with monitor connected. I can stop and resume other cards for changes to take effect (and show correct/new hashrate), but probably makes sense to fix it somehow, so miner shows correct hashrates after applying values. Of course, if you run it for 2+ time, drivers keep settings and there is no that effect. Still, it is surprising when you run minr with some value and it is not reflected in hashrates.
1. AMD disabled underclocking in theri drivers in past. May be it enabled it again in recent drivers, I did not check it. 2. Linux requires root access for it, I remember someone said that even sudo is not working. 3. Did not check if it is possible. 4. I did not check it. 5. So if I take two 4xx cards, start miner with -*clock option and it will change clocks only for one card? 5. No. In short: changing memory clock using any tool does not change displayed hashrate until miner restarted or card stopped/resumed. Except a card with monitor connected: for it new hashrate is shown instantly. When I change memory freq using any tool (WattTool) for a single card while miner is running, it instantly changes displayed hashrate only if the card has connected monitor (tested on Rx470). For headless cards the hashrate shown is not changed until miner restarted or card stopped/resumed. That seems to be a feature (@All: please confirm, but I saw someone complained for the same issue). When you change freq using miner cmdline, and previous freq was not the same, miner sets freq but shows hashrate for old freq until restarted. 5. Some cards I have, wattman doesn't allow changing clocks/voltages unless I pause miner. I didn't think of if monitor was connected. I have some display emulators I got for $15 that helps with VNC, but not sure it would be worth it for more than that... It is very strange for me because sometimes displayed hashrate changing when I change ram frequency, sometimes it doesn't react sometimes it react for gpu frequency though So, I have been using CDM 7.2 for about 5 days now on my W7 system. I was finally able to reduce my wattage pull through Wattman setting (and disabling dual mining), but am still stuck on a paltry 20.75 Mh/s on ETH per each of my MSI RX 470's. I have tried everything on the CDM side, such as setting ETH intensity to the max of 16 in my command line, adding in all 5 of the recommended setx lines, set my virtual memory to 24GB, etc. None of this moved the needle at all.
So, I am now trying the overclocking route before getting into modding the bios on these. A few things are perplexing though. In my Wattman, each of the 4 GPU's can only be increased from 1650 default to 1700. These seems like a very low limit to me and setting all 4 to 1700 had zero impact.
So, using Afterburner, it actually gave me the option to raise Memory Clock all the way to 2100. I only tried 1850 and applied to all 4 GPUs but yet again, absolutely NO impact... all 4 still mining at exactly 20.75. So, my question is, am I doing something wrong? Shouldn't raising the the clock speed on these yield at least a 5-10% bump in mining hash-rate? Or am I completely off base here?
I know of many people using these cards that have achieved 23+ right out of the box, so still trying to figure out why I cannot get close to that mark.
Please update your driver version.. I have same issue with my rx 480 before update drivers I was able only to increase RAM frequency from 2000 to 2100Mhz, after update I can set 2250Mhz in Wattman Thanks, but I updated to Crimson 16.9.2 over a week ago and it had zero impact. However, I was finally able to at least get a little HR increase by setting to 1700 in Wattman. Unfortunately, this put my wattage usage through the roof! Increased it 50-60W at the wall (although strangely, Afterburner showed steady wattage at around 74 with no increase after moving to 1700 and I can't figure out why). And, this was for only 1 GPU... doing to all 4 pushed my up to around 750 (from 625 before)... all for a measly increase from 20.75 to 21.45, so clearly not worth the extra power drain. I since reset everything in Wattman, tweaked down the GPU mV settings in states 6 & 7 and I'm back down in the 620 range with each of the 4 470's hashing a pretty pathetic 20.7. Bottom line is that a bunch of others here got 23+ out of the box on these cards... no modding, no OCing, nothing. So, I guess I just got really unlucky with my batch. I guess a pseudo-silver-lining is that this makes my decision really easy on modding the bios on these. I had previously thought that if I got 23 out of the box and could OC 1-2 more, then I wouldn't risk modding. But now, it's a no-brainer since there is no way I'm going to ever be happy running this rig getting less than 21 per card, nor will it likely ever be profitable that way. So, hopefully after modding I can at least get in the 25-26 range. If not, then I don't see much point in adding a 5th card to this rig. My next rig though will not be built with MSI cards, that's for sure!
|
|
|
|
xeridea
|
|
October 15, 2016, 02:37:41 AM |
|
@Claymore, few questions:
1) -cclock: you wrote "you can overclock only", but it seems not to be true for, at least, Windows and Polaris. My 470x can be underclocked (GPU set to 1150 for all states). 2) Any chance to support -cclock and -mclock on Linux for amdgpu-pro drivers (for Polaris)? It is not said "unsupported on Linux", but does not work for me (mem can't be set to 1950 using this). 3) Any chance to support -cvddc and -mvddc on Linux for amdgpu-pro drivers? 4) Are older cards like 7950/7970 supported using amdgpu-pro drivers on Linux? 5) There is an issue on Windows when used -*clock commands: they are applied at some init stage, but for my 470x it instantly changes hashrates only for the card with monitor connected. I can stop and resume other cards for changes to take effect (and show correct/new hashrate), but probably makes sense to fix it somehow, so miner shows correct hashrates after applying values. Of course, if you run it for 2+ time, drivers keep settings and there is no that effect. Still, it is surprising when you run minr with some value and it is not reflected in hashrates.
1. AMD disabled underclocking in theri drivers in past. May be it enabled it again in recent drivers, I did not check it. 2. Linux requires root access for it, I remember someone said that even sudo is not working. 3. Did not check if it is possible. 4. I did not check it. 5. So if I take two 4xx cards, start miner with -*clock option and it will change clocks only for one card? 5. No. In short: changing memory clock using any tool does not change displayed hashrate until miner restarted or card stopped/resumed. Except a card with monitor connected: for it new hashrate is shown instantly. When I change memory freq using any tool (WattTool) for a single card while miner is running, it instantly changes displayed hashrate only if the card has connected monitor (tested on Rx470). For headless cards the hashrate shown is not changed until miner restarted or card stopped/resumed. That seems to be a feature (@All: please confirm, but I saw someone complained for the same issue). When you change freq using miner cmdline, and previous freq was not the same, miner sets freq but shows hashrate for old freq until restarted. 5. Some cards I have, wattman doesn't allow changing clocks/voltages unless I pause miner. I didn't think of if monitor was connected. I have some display emulators I got for $15 that helps with VNC, but not sure it would be worth it for more than that... It is very strange for me because sometimes displayed hashrate changing when I change ram frequency, sometimes it doesn't react sometimes it react for gpu frequency though So, I have been using CDM 7.2 for about 5 days now on my W7 system. I was finally able to reduce my wattage pull through Wattman setting (and disabling dual mining), but am still stuck on a paltry 20.75 Mh/s on ETH per each of my MSI RX 470's. I have tried everything on the CDM side, such as setting ETH intensity to the max of 16 in my command line, adding in all 5 of the recommended setx lines, set my virtual memory to 24GB, etc. None of this moved the needle at all.
So, I am now trying the overclocking route before getting into modding the bios on these. A few things are perplexing though. In my Wattman, each of the 4 GPU's can only be increased from 1650 default to 1700. These seems like a very low limit to me and setting all 4 to 1700 had zero impact.
So, using Afterburner, it actually gave me the option to raise Memory Clock all the way to 2100. I only tried 1850 and applied to all 4 GPUs but yet again, absolutely NO impact... all 4 still mining at exactly 20.75. So, my question is, am I doing something wrong? Shouldn't raising the the clock speed on these yield at least a 5-10% bump in mining hash-rate? Or am I completely off base here?
I know of many people using these cards that have achieved 23+ right out of the box, so still trying to figure out why I cannot get close to that mark.
Please update your driver version.. I have same issue with my rx 480 before update drivers I was able only to increase RAM frequency from 2000 to 2100Mhz, after update I can set 2250Mhz in Wattman Thanks, but I updated to Crimson 16.9.2 over a week ago and it had zero impact. However, I was finally able to at least get a little HR increase by setting to 1700 in Wattman. Unfortunately, this put my wattage usage through the roof! Increased it 50-60W at the wall (although strangely, Afterburner showed steady wattage at around 74 with no increase after moving to 1700 and I can't figure out why). And, this was for only 1 GPU... doing to all 4 pushed my up to around 750 (from 625 before)... all for a measly increase from 20.75 to 21.45, so clearly not worth the extra power drain. I since reset everything in Wattman, tweaked down the GPU mV settings in states 6 & 7 and I'm back down in the 620 range with each of the 4 470's hashing a pretty pathetic 20.7. Bottom line is that a bunch of others here got 23+ out of the box on these cards... no modding, no OCing, nothing. So, I guess I just got really unlucky with my batch. I guess a pseudo-silver-lining is that this makes my decision really easy on modding the bios on these. I had previously thought that if I got 23 out of the box and could OC 1-2 more, then I wouldn't risk modding. But now, it's a no-brainer since there is no way I'm going to ever be happy running this rig getting less than 21 per card, nor will it likely ever be profitable that way. So, hopefully after modding I can at least get in the 25-26 range. If not, then I don't see much point in adding a 5th card to this rig. My next rig though will not be built with MSI cards, that's for sure! What card do you have? The better 470 4GB cards have 7GHz (1750), will do 22MH memory, the 8GB cards have 8GHz (2000) memory (except the terrible MSI ones....) and will do 24.6 (stock, I don't OC them). The best are the Sapphire Nitro, good memory, best undervolting from the ones I have tested. The 470 4GB with 6.6 or 6.7GHz memory you should avoid, also MSI 8GB, only has 6.7GHz, should be 8GHz, since it costs same as the Sapphire, but it has bottom of the barrel memory. Edit, I see you have MSI 470s.... well, that's unfortunate. I didn't buy any of them, even early on and supply was hard to find, because their memory is slow (always look at specs on cards... newegg usually has all the details). Nitro 8GB Sapphires on sale right now @ newegg...
|
Profitability over time charts for many GPUs - http://xeridea.us/chartsBTC: bc1qr2xwjwfmjn43zhrlp6pn7vwdjrjnv5z0anhjhn LTC: LXDm6sR4dkyqtEWfUbPumMnVEiUFQvxSbZ Eth: 0x44cCe2cf90C8FEE4C9e4338Ae7049913D4F6fC24
|
|
|
maxmad_x
Sr. Member
Offline
Activity: 546
Merit: 250
It takes a lot to build but not much to lose
|
|
October 15, 2016, 03:45:58 AM |
|
Anyone please want to help me with this ? As far as I can see , I dont see an error. No usual OpenCL call error exit... I can't see the error but the miner reboots !
I have 3 rx480s, Win 10, Crimson 16.9.3 and as you can see , for first few lines it has been working at 30.6MH each. then something has happened and the miner crashes. Can someone please help?
20:27:29:198 1590 parse packet: 247 20:27:29:198 1590 eth: job changed 20:27:29:214 1590 new buf size: 0 20:27:29:214 1590 ETH: 10/14/16-20:27:29 - New job from us1.ethpool.org:3333 20:27:29:214 1590 target: 0x0000000112e0be82 (diff: 4000MH), epoch #81 20:27:29:230 1590 ETH - Total Speed: 92.021 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00 20:27:29:230 1590 ETH: GPU0 30.688 Mh/s, GPU1 30.634 Mh/s, GPU2 30.699 Mh/s 20:27:30:042 1590 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57b652a", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}
20:27:30:089 1590 ETH: checking pool connection... 20:27:30:089 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:30:136 1590 got 39 bytes 20:27:30:136 1590 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:27:30:136 1590 parse packet: 38 20:27:30:151 1590 new buf size: 0 20:27:30:230 1590 got 248 bytes 20:27:30:230 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:30:245 1590 parse packet: 247 20:27:30:245 1590 eth: job is the same 20:27:30:261 1590 new buf size: 0 20:27:30:808 17d0 recv: 51 20:27:30:823 17d0 srv pck: 50 20:27:30:870 17d0 srv bs: 0 20:27:30:886 17d0 sent: 162 20:27:35:824 117c recv: 51 20:27:35:824 117c srv pck: 50 20:27:35:871 117c srv bs: 0 20:27:35:871 117c sent: 162 20:27:40:121 1590 ETH: checking pool connection... 20:27:40:121 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:40:215 1590 got 248 bytes 20:27:40:215 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:40:231 1590 parse packet: 247 20:27:40:231 1590 eth: job is the same 20:27:40:246 1590 new buf size: 0 20:27:40:824 1468 recv: 51 20:27:40:840 1468 srv pck: 50 20:27:40:887 1468 srv bs: 0 20:27:40:887 1468 sent: 162 20:27:45:825 514 recv: 51 20:27:45:841 514 srv pck: 50 20:27:45:888 514 srv bs: 0 20:27:45:903 514 sent: 162 20:27:47:372 1580 ETH: put share nonce 4ef7ab1c0ff574f1 20:27:47:372 1580 ETH round found 1 shares 20:27:47:388 1590 ETH: 10/14/16-20:27:47 - SHARE FOUND - (GPU 1) 20:27:47:403 1590 send: {"id":4,"method":"eth_submitWork","params":["0x4ef7ab1c0ff574f1","0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xf70b5bbcbe4143debf392fc7bb00587fa0901077d9e2652f967a15d56e33db83"]}
20:27:47:497 1590 got 39 bytes 20:27:47:497 1590 buf: {"id":4,"jsonrpc":"2.0","result":true}
20:27:47:497 1590 parse packet: 38 20:27:47:513 1590 ETH: Share accepted (110 ms)!
20:27:47:513 1590 new buf size: 0 20:27:50:060 1590 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57bb1bb", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}
20:27:50:138 1590 got 39 bytes 20:27:50:138 1590 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:27:50:154 1590 parse packet: 38 20:27:50:154 1590 new buf size: 0 20:27:50:169 1590 ETH: checking pool connection... 20:27:50:185 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:50:263 1590 got 248 bytes 20:27:50:263 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:50:279 1590 parse packet: 247 20:27:50:279 1590 eth: job is the same 20:27:50:294 1590 new buf size: 0 20:27:50:841 740 recv: 51 20:27:50:857 740 srv pck: 50 20:27:50:904 740 srv bs: 0 20:27:50:904 740 sent: 162 20:27:51:060 1414 GPU0 t=76C fan=40%, GPU1 t=70C fan=32%, GPU2 t=76C fan=40% 20:27:51:060 1414 em hbt: 0, fm hbt: 62, 20:27:51:060 1414 watchdog - thread 0, hb time 187 20:27:51:060 1414 watchdog - thread 1, hb time 500 20:27:51:076 1414 watchdog - thread 2, hb time 562 20:27:51:076 1414 watchdog - thread 3, hb time 250 20:27:51:076 1414 watchdog - thread 4, hb time 328 20:27:51:076 1414 watchdog - thread 5, hb time 15
|
|
|
|
knightkon
|
|
October 15, 2016, 05:46:53 AM |
|
I'm running a 750Ti, which claymore miner should i be using. also is there anywhere i can find a step by step guide for installing the claymore miner? thanks in advance for the help.
|
|
|
|
van2367
Newbie
Offline
Activity: 1
Merit: 0
|
|
October 15, 2016, 08:15:28 AM |
|
Dear, you can add a miner Vcash (XVC)?
|
|
|
|
scryptr
Legendary
Offline
Activity: 1797
Merit: 1028
|
|
October 15, 2016, 11:59:11 AM |
|
I'm running a 750Ti, which claymore miner should i be using. also is there anywhere i can find a step by step guide for installing the claymore miner? thanks in advance for the help.
CLAYMORE'S MINER IS RELEASED AS BINARIES-- You merely copy them to a directory and execute. Intstructions are on the first page of this thread, and in the readme file However, a GTX 750ti card is not considered a good choice for Dagger-Hashimoto (Ethereum) mining. The card does not perform well due to memory access limitations. Although the card was once able to mine ETH at ~8MH/s, the DAG file grew too large for this particular memory architecture to handle. Mining ETH now will likely be at 0.5 to 1.0MH/s. There are many posts in multiple threads regarding the limitations of the GTX 750ti when mining ETH. --scryptr
|
|
|
|
GH
Member
Offline
Activity: 117
Merit: 10
|
|
October 15, 2016, 12:36:57 PM |
|
I'm running a 750Ti, which claymore miner should i be using. also is there anywhere i can find a step by step guide for installing the claymore miner? thanks in advance for the help.
CLAYMORE'S MINER IS RELEASED AS BINARIES-- You merely copy them to a directory and execute. Intstructions are on the first page of this thread, and in the readme file However, a GTX 750ti card is not considered a good choice for Dagger-Hashimoto (Ethereum) mining. The card does not perform well due to memory access limitations. Although the card was once able to mine ETH at ~8MH/s, the DAG file grew too large for this particular memory architecture to handle. Mining ETH now will likely be at 0.5 to 1.0MH/s. There are many posts in multiple threads regarding the limitations of the GTX 750ti when mining ETH. --scryptr That's not the full truth. That may be right for ETH, but my 750tis (Gainward Golden Samples) perform at around 10 MH/s with Dagger Hashimoto. It's only a question of DAG size. (=currency choice) Note: Results may be different for CDM. And BTW, thanks for helping the newbies.
|
|
|
|
aaronsace
|
|
October 15, 2016, 01:03:37 PM |
|
In version 7.2, '-ttdcr' is using the temperature from GPU#1 but adjusting GPU#0: -ttdcr 85 -mode 1-1 -dcri 60
GPU#1 is always at 90C so GPU#0 is effectively always reduced.
|
|
|
|
maxmad_x
Sr. Member
Offline
Activity: 546
Merit: 250
It takes a lot to build but not much to lose
|
|
October 15, 2016, 01:28:38 PM |
|
In version 7.2, '-ttdcr' is using the temperature from GPU#1 but adjusting GPU#0: -ttdcr 85 -mode 1-1 -dcri 60
GPU#1 is always at 90C so GPU#0 is effectively always reduced.
The sequence of GPUs in temp and Hashrate is not same. It has been discussed before. You will have to find the GPU number of the one which is high and change ttdcr for that. Thank you
|
|
|
|
aaronsace
|
|
October 15, 2016, 01:51:58 PM Last edit: October 15, 2016, 11:12:31 PM by aaronsace |
|
In version 7.2, '-ttdcr' is using the temperature from GPU#1 but adjusting GPU#0: -ttdcr 85 -mode 1-1 -dcri 60
GPU#1 is always at 90C so GPU#0 is effectively always reduced.
The sequence of GPUs in temp and Hashrate is not same. It has been discussed before. You will have to find the GPU number of the one which is high and change ttdcr for that. Thank you I already know about that problem with the order; that isn't what I said. I figured out how to fix it when I was testing disabling one card. If you enable both the cards manually but the other way around, then it seems to fix it: "-di 10"
|
|
|
|
knightkon
|
|
October 15, 2016, 03:20:02 PM |
|
I'm running a 750Ti, which claymore miner should i be using. also is there anywhere i can find a step by step guide for installing the claymore miner? thanks in advance for the help.
CLAYMORE'S MINER IS RELEASED AS BINARIES-- You merely copy them to a directory and execute. Intstructions are on the first page of this thread, and in the readme file However, a GTX 750ti card is not considered a good choice for Dagger-Hashimoto (Ethereum) mining. The card does not perform well due to memory access limitations. Although the card was once able to mine ETH at ~8MH/s, the DAG file grew too large for this particular memory architecture to handle. Mining ETH now will likely be at 0.5 to 1.0MH/s. There are many posts in multiple threads regarding the limitations of the GTX 750ti when mining ETH. --scryptr I am currently using it on minergate and I am getting 1.34 Mh/s for ETH/ETC (When it was up and running). I was told if I use claymore, it would get better Mh/s than what I am getting at minergate.
|
|
|
|
adamvp
|
|
October 15, 2016, 03:21:45 PM |
|
Anyone please want to help me with this ? As far as I can see , I dont see an error. No usual OpenCL call error exit... I can't see the error but the miner reboots !
I have 3 rx480s, Win 10, Crimson 16.9.3 and as you can see , for first few lines it has been working at 30.6MH each. then something has happened and the miner crashes. Can someone please help?
20:27:29:198 1590 parse packet: 247 20:27:29:198 1590 eth: job changed 20:27:29:214 1590 new buf size: 0 20:27:29:214 1590 ETH: 10/14/16-20:27:29 - New job from us1.ethpool.org:3333 20:27:29:214 1590 target: 0x0000000112e0be82 (diff: 4000MH), epoch #81 20:27:29:230 1590 ETH - Total Speed: 92.021 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00 20:27:29:230 1590 ETH: GPU0 30.688 Mh/s, GPU1 30.634 Mh/s, GPU2 30.699 Mh/s 20:27:30:042 1590 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57b652a", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}
20:27:30:089 1590 ETH: checking pool connection... 20:27:30:089 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:30:136 1590 got 39 bytes 20:27:30:136 1590 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:27:30:136 1590 parse packet: 38 20:27:30:151 1590 new buf size: 0 20:27:30:230 1590 got 248 bytes 20:27:30:230 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:30:245 1590 parse packet: 247 20:27:30:245 1590 eth: job is the same 20:27:30:261 1590 new buf size: 0 20:27:30:808 17d0 recv: 51 20:27:30:823 17d0 srv pck: 50 20:27:30:870 17d0 srv bs: 0 20:27:30:886 17d0 sent: 162 20:27:35:824 117c recv: 51 20:27:35:824 117c srv pck: 50 20:27:35:871 117c srv bs: 0 20:27:35:871 117c sent: 162 20:27:40:121 1590 ETH: checking pool connection... 20:27:40:121 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:40:215 1590 got 248 bytes 20:27:40:215 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:40:231 1590 parse packet: 247 20:27:40:231 1590 eth: job is the same 20:27:40:246 1590 new buf size: 0 20:27:40:824 1468 recv: 51 20:27:40:840 1468 srv pck: 50 20:27:40:887 1468 srv bs: 0 20:27:40:887 1468 sent: 162 20:27:45:825 514 recv: 51 20:27:45:841 514 srv pck: 50 20:27:45:888 514 srv bs: 0 20:27:45:903 514 sent: 162 20:27:47:372 1580 ETH: put share nonce 4ef7ab1c0ff574f1 20:27:47:372 1580 ETH round found 1 shares 20:27:47:388 1590 ETH: 10/14/16-20:27:47 - SHARE FOUND - (GPU 1) 20:27:47:403 1590 send: {"id":4,"method":"eth_submitWork","params":["0x4ef7ab1c0ff574f1","0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xf70b5bbcbe4143debf392fc7bb00587fa0901077d9e2652f967a15d56e33db83"]}
20:27:47:497 1590 got 39 bytes 20:27:47:497 1590 buf: {"id":4,"jsonrpc":"2.0","result":true}
20:27:47:497 1590 parse packet: 38 20:27:47:513 1590 ETH: Share accepted (110 ms)!
20:27:47:513 1590 new buf size: 0 20:27:50:060 1590 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57bb1bb", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}
20:27:50:138 1590 got 39 bytes 20:27:50:138 1590 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:27:50:154 1590 parse packet: 38 20:27:50:154 1590 new buf size: 0 20:27:50:169 1590 ETH: checking pool connection... 20:27:50:185 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:50:263 1590 got 248 bytes 20:27:50:263 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:50:279 1590 parse packet: 247 20:27:50:279 1590 eth: job is the same 20:27:50:294 1590 new buf size: 0 20:27:50:841 740 recv: 51 20:27:50:857 740 srv pck: 50 20:27:50:904 740 srv bs: 0 20:27:50:904 740 sent: 162 20:27:51:060 1414 GPU0 t=76C fan=40%, GPU1 t=70C fan=32%, GPU2 t=76C fan=40% 20:27:51:060 1414 em hbt: 0, fm hbt: 62, 20:27:51:060 1414 watchdog - thread 0, hb time 187 20:27:51:060 1414 watchdog - thread 1, hb time 500 20:27:51:076 1414 watchdog - thread 2, hb time 562 20:27:51:076 1414 watchdog - thread 3, hb time 250 20:27:51:076 1414 watchdog - thread 4, hb time 328 20:27:51:076 1414 watchdog - thread 5, hb time 15
Do you have -dbg 1 enabled?
|
I am looking for signature campaign pm me
|
|
|
Nippy-ua
Newbie
Offline
Activity: 48
Merit: 0
|
|
October 15, 2016, 06:09:19 PM |
|
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͻ ▒ Claymore's Dual ETH + DCR/SC/LBC GPU Miner v7.1 ▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ͼ
ETH: 1 pool is specified No AMD cards in the list.
where is that list ?
|
|
|
|
shadabahmed
|
|
October 15, 2016, 06:12:11 PM Last edit: October 15, 2016, 06:36:34 PM by shadabahmed |
|
GPU2, OpenCL error 36 cannot write buffer for DAG
what does that mean? than miner restarts
|
Am I spamming? Report me!
|
|
|
knightkon
|
|
October 15, 2016, 08:19:22 PM |
|
I am sorry, I could use some more help than what is listed here that I can find. I downloaded the Claymore's file and extracted it. I then read the readme file and nowhere in there does it tell me how to set things up and all. I do not understand. Are there step by step instructions out there that can assist me?
|
|
|
|
Raja_MBZ
Legendary
Offline
Activity: 1862
Merit: 1505
|
|
October 15, 2016, 08:29:02 PM |
|
I am sorry, I could use some more help than what is listed here that I can find. I downloaded the Claymore's file and extracted it. I then read the readme file and nowhere in there does it tell me how to set things up and all. I do not understand. Are there step by step instructions out there that can assist me?
Edit the "start" file of the miner, it's actually nothing more than a couple of commands written there. Then check out the Read-Me file, you should find some important stuff to type in at the start file with the help of FAQ's given there.
|
|
|
|
maxmad_x
Sr. Member
Offline
Activity: 546
Merit: 250
It takes a lot to build but not much to lose
|
|
October 15, 2016, 08:49:50 PM |
|
yes thats why I am getting the log buddy Anyone please want to help me with this ? As far as I can see , I dont see an error. No usual OpenCL call error exit... I can't see the error but the miner reboots !
I have 3 rx480s, Win 10, Crimson 16.9.3 and as you can see , for first few lines it has been working at 30.6MH each. then something has happened and the miner crashes. Can someone please help?
20:27:29:198 1590 parse packet: 247 20:27:29:198 1590 eth: job changed 20:27:29:214 1590 new buf size: 0 20:27:29:214 1590 ETH: 10/14/16-20:27:29 - New job from us1.ethpool.org:3333 20:27:29:214 1590 target: 0x0000000112e0be82 (diff: 4000MH), epoch #81 20:27:29:230 1590 ETH - Total Speed: 92.021 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00 20:27:29:230 1590 ETH: GPU0 30.688 Mh/s, GPU1 30.634 Mh/s, GPU2 30.699 Mh/s 20:27:30:042 1590 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57b652a", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}
20:27:30:089 1590 ETH: checking pool connection... 20:27:30:089 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:30:136 1590 got 39 bytes 20:27:30:136 1590 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:27:30:136 1590 parse packet: 38 20:27:30:151 1590 new buf size: 0 20:27:30:230 1590 got 248 bytes 20:27:30:230 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:30:245 1590 parse packet: 247 20:27:30:245 1590 eth: job is the same 20:27:30:261 1590 new buf size: 0 20:27:30:808 17d0 recv: 51 20:27:30:823 17d0 srv pck: 50 20:27:30:870 17d0 srv bs: 0 20:27:30:886 17d0 sent: 162 20:27:35:824 117c recv: 51 20:27:35:824 117c srv pck: 50 20:27:35:871 117c srv bs: 0 20:27:35:871 117c sent: 162 20:27:40:121 1590 ETH: checking pool connection... 20:27:40:121 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:40:215 1590 got 248 bytes 20:27:40:215 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:40:231 1590 parse packet: 247 20:27:40:231 1590 eth: job is the same 20:27:40:246 1590 new buf size: 0 20:27:40:824 1468 recv: 51 20:27:40:840 1468 srv pck: 50 20:27:40:887 1468 srv bs: 0 20:27:40:887 1468 sent: 162 20:27:45:825 514 recv: 51 20:27:45:841 514 srv pck: 50 20:27:45:888 514 srv bs: 0 20:27:45:903 514 sent: 162 20:27:47:372 1580 ETH: put share nonce 4ef7ab1c0ff574f1 20:27:47:372 1580 ETH round found 1 shares 20:27:47:388 1590 ETH: 10/14/16-20:27:47 - SHARE FOUND - (GPU 1) 20:27:47:403 1590 send: {"id":4,"method":"eth_submitWork","params":["0x4ef7ab1c0ff574f1","0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xf70b5bbcbe4143debf392fc7bb00587fa0901077d9e2652f967a15d56e33db83"]}
20:27:47:497 1590 got 39 bytes 20:27:47:497 1590 buf: {"id":4,"jsonrpc":"2.0","result":true}
20:27:47:497 1590 parse packet: 38 20:27:47:513 1590 ETH: Share accepted (110 ms)!
20:27:47:513 1590 new buf size: 0 20:27:50:060 1590 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x57bb1bb", "0x000000000000000000000000000000000000000000000000000000009563b0cb"]}
20:27:50:138 1590 got 39 bytes 20:27:50:138 1590 buf: {"id":6,"jsonrpc":"2.0","result":true}
20:27:50:154 1590 parse packet: 38 20:27:50:154 1590 new buf size: 0 20:27:50:169 1590 ETH: checking pool connection... 20:27:50:185 1590 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
20:27:50:263 1590 got 248 bytes 20:27:50:263 1590 buf: {"id":3,"jsonrpc":"2.0","result":["0x78c1694f033caa2116ca25d4d5b99cd7de8f1b0eeef909a511164d263cf4434f","0xbf544f3a8adce8002e4ec2a0af5fc0615ae1508d746c330510cde6f239796be6","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x2544f9"]}
20:27:50:279 1590 parse packet: 247 20:27:50:279 1590 eth: job is the same 20:27:50:294 1590 new buf size: 0 20:27:50:841 740 recv: 51 20:27:50:857 740 srv pck: 50 20:27:50:904 740 srv bs: 0 20:27:50:904 740 sent: 162 20:27:51:060 1414 GPU0 t=76C fan=40%, GPU1 t=70C fan=32%, GPU2 t=76C fan=40% 20:27:51:060 1414 em hbt: 0, fm hbt: 62, 20:27:51:060 1414 watchdog - thread 0, hb time 187 20:27:51:060 1414 watchdog - thread 1, hb time 500 20:27:51:076 1414 watchdog - thread 2, hb time 562 20:27:51:076 1414 watchdog - thread 3, hb time 250 20:27:51:076 1414 watchdog - thread 4, hb time 328 20:27:51:076 1414 watchdog - thread 5, hb time 15
Do you have -dbg 1 enabled?
|
|
|
|
|