Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 149. (Read 6590565 times)
May 11, 2019, 10:47:38 AM
I am not sure if I am the only one but, with V14 my NVIDIA cards are completely ignored. I have a mixed rig of AMD and NVIDIA and the NVIDIA cards were ignored. It started the miner and said there was no NVIDIA cards detected. Windows saw them just fine. I went back to 12 and it works fine with them. I looked through the Readme to see if there was anything specific to enable NVIDIA with this version and I found nothing specific. Just curious if anyone has this issue.
May 11, 2019, 10:31:39 AM
thans for your reply. I'm using amd block chain driver 17.30.1029. the red dragon card is on GPU0, the other cards are red devil and it has no effect in hash.
Please remove your message or take log data in "code" tag, it's too large.
Try to press "0" key to disable mining on GPU0, wait about 10 seconds and then press "0" again to enable it - what hashrate do you see now?
May 11, 2019, 09:56:40 AM
I have powercolor red dragon rx570 4gb and running with claymore v12, its get 29Mh/s. when running with claymore v14, its get 22.5Mh/s. I'm using same setting for both version
claymore v14 decreased my hash power, how could this happen. is there still a bug?
claymore v14 decreased my hash power, how could this happen. is there still a bug?
I think is still in beta testing the latest version revision 14.I am sure Claymore will fix things in the upcoming days because I believe it is a bug in the miner and it will be sorted out soon.
I have powercolor red dragon rx570 4gb and running with claymore v12, its get 29Mh/s. when running with claymore v14, its get 22.5Mh/s. I'm using same setting for both version
claymore v14 decreased my hash power, how could this happen. is there still a bug?
claymore v14 decreased my hash power, how could this happen. is there still a bug?
What version of AMD drivers do you use? Start miner for a minute and send me the complete log file so I can check the details, for both v12 and v14.
thans for your reply. I'm using amd block chain driver 17.30.1029. the red dragon card is on GPU0, the other cards are red devil and it has no effect in hash.
May 11, 2019, 03:33:19 AM
Thanks for version revision 14 
May 11, 2019, 03:14:50 AM
I have powercolor red dragon rx570 4gb and running with claymore v12, its get 29Mh/s. when running with claymore v14, its get 22.5Mh/s. I'm using same setting for both version
claymore v14 decreased my hash power, how could this happen. is there still a bug?
claymore v14 decreased my hash power, how could this happen. is there still a bug?
What version of AMD drivers do you use? Start miner for a minute and send me the complete log file so I can check the details, for both v12 and v14.
May 11, 2019, 02:23:40 AM
I have powercolor red dragon rx570 4gb and running with claymore v12, its get 29Mh/s. when running with claymore v14, its get 22.5Mh/s. I'm using same setting for both version
claymore v14 decreased my hash power, how could this happen. is there still a bug?
claymore v14 decreased my hash power, how could this happen. is there still a bug?
I think is still in beta testing the latest version revision 14.I am sure Claymore will fix things in the upcoming days because I believe it is a bug in the miner and it will be sorted out soon.
May 10, 2019, 11:05:10 PM
@Claymore
Thank you for a long-lasting awesome miner..
One question/request: is it possible to adjust the timeout for -minspeed, which seems to be currently hardcoded at 5 mins? Would be really nice to be able to adjust that.
Thank you for a long-lasting awesome miner..
One question/request: is it possible to adjust the timeout for -minspeed, which seems to be currently hardcoded at 5 mins? Would be really nice to be able to adjust that.
May 10, 2019, 09:59:11 PM
I have powercolor red dragon rx570 4gb and running with claymore v12, its get 29Mh/s. when running with claymore v14, its get 22.5Mh/s. I'm using same setting for both version
claymore v14 decreased my hash power, how could this happen. is there still a bug?
claymore v14 decreased my hash power, how could this happen. is there still a bug?
May 10, 2019, 07:41:13 PM
Hey Claymore,
I'm pretty dang confused about some pretty basic stuff. I'm not sure if this means i am connected to stratum or not but,
[[ETH: Stratum - connecting to 'us2.ethpool.org' <172.65.214.179> port 3333 (unsecure)
ETH: Stratum - Connected (us2.ethpool.org:3333) (unsecure)]]
ive changed the ports to 4444 and 14444 on ethpool but couldnt connect
Been on it for a few days, but can't seem to connect to the stratum port.
any suggestions on where to punch in stratum+ssl://? tried it in config, epools, .bat or if what im doing is so backwards lol
thanks guys
I'm pretty dang confused about some pretty basic stuff. I'm not sure if this means i am connected to stratum or not but,
[[ETH: Stratum - connecting to 'us2.ethpool.org' <172.65.214.179> port 3333 (unsecure)
ETH: Stratum - Connected (us2.ethpool.org:3333) (unsecure)]]
ive changed the ports to 4444 and 14444 on ethpool but couldnt connect
Been on it for a few days, but can't seem to connect to the stratum port.
any suggestions on where to punch in stratum+ssl://? tried it in config, epools, .bat or if what im doing is so backwards lol
thanks guys
May 10, 2019, 06:37:17 AM
Hello ! I have a mine on the old r9 290 and r9 290x cards, can you tell me if you can apply it - strap to them?
No way, at least for now.
Claymore, do you know what a mess was when You was not so active ?
Like everyone started to release own miner program...
Like everyone started to release own miner program...
Anyway, i will get to the point.
Do You expect releasing Linux version of v14 and will it support applying custom straps or that will not be possible under linux ?
Right now we have tool called amdmemorytweak which can modify timings (straps) in Linux for example for Vega.
And it is working fine in SimpleMining.net OS under Linux. Yet Polaris is not so obvious for that tool.
Do You expect releasing Linux version of v14 and will it support applying custom straps or that will not be possible under linux ?
Right now we have tool called amdmemorytweak which can modify timings (straps) in Linux for example for Vega.
And it is working fine in SimpleMining.net OS under Linux. Yet Polaris is not so obvious for that tool.
Due to several reasons I'm not going to implement it for Linux. The main reason is that I don't have enough experience in Linux kernel/drivers and it would take too much time and efforts to get enough level of expertise; applying entire straps on the fly is rather hard magic.
Also may i ask ? You have more downloads for Windows versions or Linux versions ?
Oh wait, that is bad comparison.... In Plug&Play Operating System based on linux we are downloading miner once and then people are downloading those from our servers.
Can you tell me if you see that more users are USING windows version than linux version ?
I am really curious if people are still using windows for mining and this is why windows comes first or is it other factor ?
Oh wait, that is bad comparison.... In Plug&Play Operating System based on linux we are downloading miner once and then people are downloading those from our servers.
Can you tell me if you see that more users are USING windows version than linux version ?
I am really curious if people are still using windows for mining and this is why windows comes first or is it other factor ?
I don't have any good stats for Windows vs Linux downloads/using.
Yes I support Windows better, again the main reason that I have almost 20 years experience in Windows software development and almost zero experience in Linux.
May 10, 2019, 05:48:25 AM
Claymore, do you know what a mess was when You was not so active ?
Like everyone started to release own miner program...
Anyway, i will get to the point.
Do You expect releasing Linux version of v14 and will it support applying custom straps or that will not be possible under linux ?
Right now we have tool called amdmemorytweak which can modify timings (straps) in Linux for example for Vega.
And it is working fine in SimpleMining.net OS under Linux. Yet Polaris is not so obvious for that tool.
Also may i ask ? You have more downloads for Windows versions or Linux versions ?
Oh wait, that is bad comparison.... In Plug&Play Operating System based on linux we are downloading miner once and then people are downloading those from our servers.
Can you tell me if you see that more users are USING windows version than linux version ?
I am really curious if people are still using windows for mining and this is why windows comes first or is it other factor ?
Like everyone started to release own miner program...
Anyway, i will get to the point.
Do You expect releasing Linux version of v14 and will it support applying custom straps or that will not be possible under linux ?
Right now we have tool called amdmemorytweak which can modify timings (straps) in Linux for example for Vega.
And it is working fine in SimpleMining.net OS under Linux. Yet Polaris is not so obvious for that tool.
Also may i ask ? You have more downloads for Windows versions or Linux versions ?
Oh wait, that is bad comparison.... In Plug&Play Operating System based on linux we are downloading miner once and then people are downloading those from our servers.
Can you tell me if you see that more users are USING windows version than linux version ?
I am really curious if people are still using windows for mining and this is why windows comes first or is it other factor ?
May 10, 2019, 03:30:05 AM
Hello ! I have a mine on the old r9 290 and r9 290x cards, can you tell me if you can apply it - strap to them?
May 09, 2019, 07:24:19 AM
Hello CM dev is it possible with claymoreminer dual mining ethereum based coin and nimic coin?
May 09, 2019, 07:23:55 AM
Is it possible to mine etherum with RX 570 4GB
4 GB ram & Claymore V14 & Crimson-Blockchain-Workloads-Aug23 driver?
4 GB ram & Claymore V14 & Crimson-Blockchain-Workloads-Aug23 driver?
it is possible at least until now with Phoenixminer
May 09, 2019, 02:42:58 AM
Is it possible to mine etherum with RX 570 4GB
4 GB ram & Claymore V14 & Crimson-Blockchain-Workloads-Aug23 driver?
9:40:53:888 ad0 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:40:53:889 ad0 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
09:40:54:937 910 Setting DAG epoch #257 for GPU2
09:40:54:938 9a4 Setting DAG epoch #257 for GPU5
09:40:54:936 908 Setting DAG epoch #257 for GPU0
09:40:54:937 90c Setting DAG epoch #257 for GPU1
09:40:54:938 910 Create GPU buffer for GPU2
09:40:54:941 9a4 Create GPU buffer for GPU5
09:40:54:941 9a4 GPU5 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:941 968 Setting DAG epoch #257 for GPU4
09:40:54:943 910 GPU2 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:946 9a4 GPU5 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:940 954 Setting DAG epoch #257 for GPU3
09:40:54:942 968 Create GPU buffer for GPU4
09:40:54:947 910 GPU2 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:944 908 Create GPU buffer for GPU0
09:40:54:950 908 GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:951 968 GPU4 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:951 954 Create GPU buffer for GPU3
09:40:54:952 908 GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:945 90c Create GPU buffer for GPU1
09:40:54:954 90c GPU1 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:954 968 GPU4 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:956 954 GPU3 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:964 90c GPU1 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:966 954 GPU3 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:57:726 ad0 buf: {"id":0,"jsonrpc":"2.0","result":["0x9c719cc25c219332ef88dbbd73abf1e48fca42223aeb01f716a22bcf250e6c9b","0x93f354b70a7d7c61afe4207756333d6c82f83d8677d29045fa92846532cf8881","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x75df53"]}
09:40:57:730 ad0 ETH: 05/09/19-09:40:57 - New job from eu1.ethermine.org:4444
09:40:57:732 ad0 target: 0x0000000112e0be82 (diff: 4000MH), epoch 257(3.01GB)
09:40:57:735 ad0 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:40:57:738 ad0 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
09:40:57:948 9a4 Set global fail flag, failed GPU5
09:40:57:953 9a4 GPU 5 failed
09:40:57:950 910 Set global fail flag, failed GPU2
09:40:57:959 910 GPU 2 failed
09:40:57:961 91c Setting DAG epoch #257 for GPU2
09:40:57:955 908 Set global fail flag, failed GPU0
09:40:57:968 908 GPU 0 failed
09:40:57:958 968 Set global fail flag, failed GPU4
09:40:57:967 90c Set global fail flag, failed GPU1
09:40:57:976 90c GPU 1 failed
09:40:57:989 968 GPU 4 failed
09:40:57:991 91c GPU2, OpenCL error -38 - cannot write buffer for DAG
09:40:57:952 9a0 Setting DAG epoch #257 for GPU5
09:40:58:000 9a0 GPU5, OpenCL error -38 - cannot write buffer for DAG
09:40:57:989 8f4 Setting DAG epoch #257 for GPU1
09:40:58:002 8f4 GPU1, OpenCL error -38 - cannot write buffer for DAG
09:40:57:968 954 Set global fail flag, failed GPU3
09:40:57:975 964 Setting DAG epoch #257 for GPU4
09:40:58:006 964 GPU4, OpenCL error -38 - cannot write buffer for DAG
09:40:58:015 954 GPU 3 failed
09:40:58:006 860 Setting DAG epoch #257 for GPU0
09:40:58:015 950 Setting DAG epoch #257 for GPU3
09:40:58:016 950 GPU3, OpenCL error -38 - cannot write buffer for DAG
09:40:58:018 860 GPU0, OpenCL error -38 - cannot write buffer for DAG
09:40:59:252 1bd8 Quit, please wait...
4 GB ram & Claymore V14 & Crimson-Blockchain-Workloads-Aug23 driver?
9:40:53:888 ad0 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:40:53:889 ad0 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
09:40:54:937 910 Setting DAG epoch #257 for GPU2
09:40:54:938 9a4 Setting DAG epoch #257 for GPU5
09:40:54:936 908 Setting DAG epoch #257 for GPU0
09:40:54:937 90c Setting DAG epoch #257 for GPU1
09:40:54:938 910 Create GPU buffer for GPU2
09:40:54:941 9a4 Create GPU buffer for GPU5
09:40:54:941 9a4 GPU5 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:941 968 Setting DAG epoch #257 for GPU4
09:40:54:943 910 GPU2 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:946 9a4 GPU5 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:940 954 Setting DAG epoch #257 for GPU3
09:40:54:942 968 Create GPU buffer for GPU4
09:40:54:947 910 GPU2 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:944 908 Create GPU buffer for GPU0
09:40:54:950 908 GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:951 968 GPU4 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:951 954 Create GPU buffer for GPU3
09:40:54:952 908 GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:945 90c Create GPU buffer for GPU1
09:40:54:954 90c GPU1 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:954 968 GPU4 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:956 954 GPU3 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
09:40:54:964 90c GPU1 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:54:966 954 GPU3 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
09:40:57:726 ad0 buf: {"id":0,"jsonrpc":"2.0","result":["0x9c719cc25c219332ef88dbbd73abf1e48fca42223aeb01f716a22bcf250e6c9b","0x93f354b70a7d7c61afe4207756333d6c82f83d8677d29045fa92846532cf8881","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x75df53"]}
09:40:57:730 ad0 ETH: 05/09/19-09:40:57 - New job from eu1.ethermine.org:4444
09:40:57:732 ad0 target: 0x0000000112e0be82 (diff: 4000MH), epoch 257(3.01GB)
09:40:57:735 ad0 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:40:57:738 ad0 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
09:40:57:948 9a4 Set global fail flag, failed GPU5
09:40:57:953 9a4 GPU 5 failed
09:40:57:950 910 Set global fail flag, failed GPU2
09:40:57:959 910 GPU 2 failed
09:40:57:961 91c Setting DAG epoch #257 for GPU2
09:40:57:955 908 Set global fail flag, failed GPU0
09:40:57:968 908 GPU 0 failed
09:40:57:958 968 Set global fail flag, failed GPU4
09:40:57:967 90c Set global fail flag, failed GPU1
09:40:57:976 90c GPU 1 failed
09:40:57:989 968 GPU 4 failed
09:40:57:991 91c GPU2, OpenCL error -38 - cannot write buffer for DAG
09:40:57:952 9a0 Setting DAG epoch #257 for GPU5
09:40:58:000 9a0 GPU5, OpenCL error -38 - cannot write buffer for DAG
09:40:57:989 8f4 Setting DAG epoch #257 for GPU1
09:40:58:002 8f4 GPU1, OpenCL error -38 - cannot write buffer for DAG
09:40:57:968 954 Set global fail flag, failed GPU3
09:40:57:975 964 Setting DAG epoch #257 for GPU4
09:40:58:006 964 GPU4, OpenCL error -38 - cannot write buffer for DAG
09:40:58:015 954 GPU 3 failed
09:40:58:006 860 Setting DAG epoch #257 for GPU0
09:40:58:015 950 Setting DAG epoch #257 for GPU3
09:40:58:016 950 GPU3, OpenCL error -38 - cannot write buffer for DAG
09:40:58:018 860 GPU0, OpenCL error -38 - cannot write buffer for DAG
09:40:59:252 1bd8 Quit, please wait...
May 08, 2019, 10:21:38 PM
Same here 4gb Hynix - my straps better then miner straps. Will check for elpida and samsung.
May 08, 2019, 03:27:07 PM
Tried on rig with rx 580 8G hynix memory... All straps up to 4 gives lower speed than my straps with the max 2250MHz MC. Best variant is 2nd strap on 2250MHz. But it still a bit lower than my strap.
Notices:
1. Often if strap set to 0 for use straps from vbios, miner at start can hang the system. But if didn't use -straps option miner always start fine. In vbios flashed eth straps.
2. Often miner hangs system on close if -straps option used.
3. If I use my manual strap (96 symbols) miner can hang on start, and everytime hang on close. But if these strap flashed to vbios and didn't used -straps option, miner works fine.
Notices:
1. Often if strap set to 0 for use straps from vbios, miner at start can hang the system. But if didn't use -straps option miner always start fine. In vbios flashed eth straps.
2. Often miner hangs system on close if -straps option used.
3. If I use my manual strap (96 symbols) miner can hang on start, and everytime hang on close. But if these strap flashed to vbios and didn't used -straps option, miner works fine.
May 08, 2019, 03:23:30 PM
good lord, Claymore, I have rx480 8 gb samsung, using latest 14th ver and reaching only 28.8mh/s, any help to see those 33mh/s?
I use "-strap 1@2250" or even "-strap 3@2250" for these cards, read Readme for more details.
Hi Claymore what is the maximum strap number we can use? Above is 3, and I see in other of your posts 4.
Can we go beyond?
i have tested saphire rx480 8gb samsung with -strap 1@2250 and make 32.4 Mh but the only problem is that apears allot of GPU Memory Errors on HwiNfo
Claymore you don't have any errors with mcclock 2250 ?
May 08, 2019, 02:07:35 PM
good lord, Claymore, I have rx480 8 gb samsung, using latest 14th ver and reaching only 28.8mh/s, any help to see those 33mh/s?
I use "-strap 1@2250" or even "-strap 3@2250" for these cards, read Readme for more details.
Hi Claymore what is the maximum strap number we can use? Above is 3, and I see in other of your posts 4.
Can we go beyond?
later edit: nevermind, I found it - it is 5
May 08, 2019, 01:50:07 PM
I was on my way to testing v14 but first had to move my driver to 19.4.3. When I moved, I then restarted v12 just to make sure everything was still working. It turns out, I lost fan control under 19.4.3 and v12. So I've reverted my driver and have gone back to v12 for now.
I'm sure the fan stuff probably works in v14 with the newer driver but I don't have time to fight with it now. Maybe over the weekend.
EDIT: Re-read posts and see that AMD keeps changing the fan API out from under you. I'm back on v12 but will make a run at v14 later. Thanks for the work on dynamic strapping.
I'm sure the fan stuff probably works in v14 with the newer driver but I don't have time to fight with it now. Maybe over the weekend.
EDIT: Re-read posts and see that AMD keeps changing the fan API out from under you. I'm back on v12 but will make a run at v14 later. Thanks for the work on dynamic strapping.
Jump to: