Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1178. (Read 6590565 times)
August 14, 2016, 08:34:37 AM
August 14, 2016, 08:10:02 AM
hi claymore
[WISHLIST]
[NICE TO HAVE]
can you have the output to the current terminal device list the -cclock value every so often. it would save me checking TRIXX in windows and ssh into ubuntu. i have it set to 1000 mhz in config and it changes every once in a while. i have no idea why.
and i do like doing "localhost:8080" in a browser but it doesnt have the clocks. bonus points if its there too.
also: -cclock value is not in the log file?
[WISHLIST]
[NICE TO HAVE]
can you have the output to the current terminal device list the -cclock value every so often. it would save me checking TRIXX in windows and ssh into ubuntu. i have it set to 1000 mhz in config and it changes every once in a while. i have no idea why.
and i do like doing "localhost:8080" in a browser but it doesnt have the clocks. bonus points if its there too.
also: -cclock value is not in the log file?
August 14, 2016, 07:10:12 AM
I use a headless linux rig, well... I try to use lunix in all my PCs
At the end I solved that problem installing X, but only the core.
Then add the enviroment variable DISPLAY.
Code:
export DISPLAY=:0
[/quote]
What do you mean the by core X ? The xorg-server package?
So you can run claymore from ssh for example, not inside X, and have ADL working?
August 14, 2016, 12:13:55 AM
Thanks for the help...but still does not work
I have no problems using NiceHash's GUI software I usually get 54.7mh/s...
wanted to try to use Claymore and focus on Eth for myself.
Reconfigured both the Start and config files, already have pagefile more than 16gb.
I tried both ways on the esm 0 and 3 still get these errors
I have no problems using NiceHash's GUI software I usually get 54.7mh/s...
wanted to try to use Claymore and focus on Eth for myself.
Reconfigured both the Start and config files, already have pagefile more than 16gb.
I tried both ways on the esm 0 and 3 still get these errors
Code:
00:09:18:804 e44 args: -epool eth-us-east1.nanopool.org:9999 -ewal 0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB -epsw x -esm 0 -estale 0 -dpool http://dcr.maxminers.net:7728 -dwal alexmobile.alexmobile -dpsw 0311 -mode 0 -tt 80
00:09:18:805 e44
00:09:18:806 e44 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
00:09:18:806 e44 º Claymore's Dual ETH + DCR/SC AMD GPU Miner v5.3 Beta º
00:09:18:807 e44 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
00:09:18:807 e44
00:09:19:007 e44 ETH: 1 pool is specified
00:09:19:008 e44 Main Ethereum pool is eth-us-east1.nanopool.org:9999
00:09:19:009 e44 DCR: 1 pool is specified
00:09:19:009 e44 Main Decred pool is dcr.maxminers.net:7728
00:09:20:775 e44 OpenCL platform: AMD Accelerated Parallel Processing
00:09:20:776 e44
Cards available: 4
00:09:20:776 e44 GPU #0: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:776 e44 GPU #1: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:777 e44 GPU #2: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:777 e44 GPU #3: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:777 e44 Total cards: 4
00:09:20:777 e44 Initializing...
00:09:20:777 e44 GPU #0 recognized as Radeon 270/270X
00:09:20:778 e44 GPU #1 recognized as Radeon 270/270X
00:09:20:778 e44 GPU #2 recognized as Radeon 270/270X
00:09:20:778 e44 GPU #3 recognized as Radeon 270/270X
00:09:20:778 e44 POOL/SOLO version
00:09:20:778 e44 b176
00:09:20:804 e44 start building OpenCL program...
00:09:39:262 e44 done
00:09:39:263 e44 GPU #0: set -etha as 1 (ETH algo for slow cards)
00:09:39:263 e44 GPU #1: set -etha as 1 (ETH algo for slow cards)
00:09:39:263 e44 GPU #2: set -etha as 1 (ETH algo for slow cards)
00:09:39:263 e44 GPU #3: set -etha as 1 (ETH algo for slow cards)
00:09:39:424 b20 ETH: Stratum - connecting to 'eth-us-east1.nanopool.org' <45.55.155.113> port 9999
00:09:39:455 e44 DUAL MINING MODE ENABLED: ETHEREUM+DECRED
00:09:39:455 e44 ETH: eth-proxy stratum mode
00:09:39:455 e44 Watchdog enabled
00:09:39:455 e44 Remote management is enabled on port 3333
00:09:39:456 e44
00:09:39:456 3d0 DCR - connecting to dcr.maxminers.net:7728
00:09:39:456 3d0 http send request: {"method": "getwork", "params": [], "id":0}
00:09:39:466 b20 send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB", "x"], "id": 2, "method": "eth_submitLogin"}
00:09:39:466 b20 ETH: Stratum - Connected (eth-us-east1.nanopool.org:9999)
00:09:39:567 3d0 http got answer: {"result":{"data":"01000000f4af4e4667548b12a3c5487c7346b7b92cd1708fcfd7045603130000000000008ff1e94757cd23ff3a88e4f78d0eaad794ae07bfaa7cda0e06f9300d13d920b06fe6b82325e861de5f7f5a7411f42b52145c9d10114f5661ecf1e24b677d239b0100af8114c798db0500000090a300009f62141a8aec30e70000000037d400006e0f000029efaf57000000000000000000000000000000000000000000000000000000000000000000000000000000008000000100000000000005a0","target":"ffffffffffffffffffffffffffffffffffffffffffffffffffffff3f00000000"},"id":0,"error":null}
00:09:39:567 3d0 DCR: Connected (dcr.maxminers.net:7728)
00:09:39:567 3d0 DCR job updated
00:09:39:687 b20 got 282 bytes
00:09:39:687 b20 buf: {"jsonrpc":"2.0","id":2,"result":true}
{"jsonrpc":"2.0","id":0,"result":["0x418107c5c15fb00abb0eca602a23123a6e0c1cae3b63e6498956820d157d2122","0xdeb13fd7c8eb5b6e43fe49e77f32c5e38fd7679be198414e839c7e1b83f17dc5","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
00:09:39:687 b20 parse packet: 38
00:09:39:687 b20 ETH: Authorized
00:09:39:688 b20 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
00:09:39:688 b20 remove first packet 243
00:09:39:688 b20 new buf size: 243
00:09:39:688 b20 parse packet: 242
00:09:39:688 b20 eth: job changed
00:09:39:688 b20 new buf size: 0
00:09:39:710 dac Setting DAG epoch #68...
00:09:39:814 b20 got 243 bytes
00:09:39:814 b20 buf: {"jsonrpc":"2.0","id":0,"result":["0x418107c5c15fb00abb0eca602a23123a6e0c1cae3b63e6498956820d157d2122","0xdeb13fd7c8eb5b6e43fe49e77f32c5e38fd7679be198414e839c7e1b83f17dc5","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
00:09:39:814 b20 parse packet: 242
00:09:39:814 b20 eth: job is the same
00:09:39:814 b20 new buf size: 0
00:09:41:927 e18 Setting DAG epoch #68 for GPU #1
00:09:41:927 e18 Create GPU buffer for GPU #1
00:09:41:927 e18 OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:41:927 4b0 Setting DAG epoch #68 for GPU #2
00:09:41:928 4b0 Create GPU buffer for GPU #2
00:09:41:928 4b0 OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:41:928 b9c Setting DAG epoch #68 for GPU #3
00:09:41:928 b9c Create GPU buffer for GPU #3
00:09:41:929 b9c OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:41:929 dac Setting DAG epoch #68 for GPU #0
00:09:41:929 dac Create GPU buffer for GPU #0
00:09:41:929 dac OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:42:494 e44 OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
00:09:42:497 e44 OC v5, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
00:09:42:499 e44 OC v5, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst
00:09:42:502 e44 OC v5, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst
00:09:18:805 e44
00:09:18:806 e44 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
00:09:18:806 e44 º Claymore's Dual ETH + DCR/SC AMD GPU Miner v5.3 Beta º
00:09:18:807 e44 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
00:09:18:807 e44
00:09:19:007 e44 ETH: 1 pool is specified
00:09:19:008 e44 Main Ethereum pool is eth-us-east1.nanopool.org:9999
00:09:19:009 e44 DCR: 1 pool is specified
00:09:19:009 e44 Main Decred pool is dcr.maxminers.net:7728
00:09:20:775 e44 OpenCL platform: AMD Accelerated Parallel Processing
00:09:20:776 e44
Cards available: 4
00:09:20:776 e44 GPU #0: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:776 e44 GPU #1: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:777 e44 GPU #2: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:777 e44 GPU #3: name: Pitcairn, 2048 MB available, 20 compute units
00:09:20:777 e44 Total cards: 4
00:09:20:777 e44 Initializing...
00:09:20:777 e44 GPU #0 recognized as Radeon 270/270X
00:09:20:778 e44 GPU #1 recognized as Radeon 270/270X
00:09:20:778 e44 GPU #2 recognized as Radeon 270/270X
00:09:20:778 e44 GPU #3 recognized as Radeon 270/270X
00:09:20:778 e44 POOL/SOLO version
00:09:20:778 e44 b176
00:09:20:804 e44 start building OpenCL program...
00:09:39:262 e44 done
00:09:39:263 e44 GPU #0: set -etha as 1 (ETH algo for slow cards)
00:09:39:263 e44 GPU #1: set -etha as 1 (ETH algo for slow cards)
00:09:39:263 e44 GPU #2: set -etha as 1 (ETH algo for slow cards)
00:09:39:263 e44 GPU #3: set -etha as 1 (ETH algo for slow cards)
00:09:39:424 b20 ETH: Stratum - connecting to 'eth-us-east1.nanopool.org' <45.55.155.113> port 9999
00:09:39:455 e44 DUAL MINING MODE ENABLED: ETHEREUM+DECRED
00:09:39:455 e44 ETH: eth-proxy stratum mode
00:09:39:455 e44 Watchdog enabled
00:09:39:455 e44 Remote management is enabled on port 3333
00:09:39:456 e44
00:09:39:456 3d0 DCR - connecting to dcr.maxminers.net:7728
00:09:39:456 3d0 http send request: {"method": "getwork", "params": [], "id":0}
00:09:39:466 b20 send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB", "x"], "id": 2, "method": "eth_submitLogin"}
00:09:39:466 b20 ETH: Stratum - Connected (eth-us-east1.nanopool.org:9999)
00:09:39:567 3d0 http got answer: {"result":{"data":"01000000f4af4e4667548b12a3c5487c7346b7b92cd1708fcfd7045603130000000000008ff1e94757cd23ff3a88e4f78d0eaad794ae07bfaa7cda0e06f9300d13d920b06fe6b82325e861de5f7f5a7411f42b52145c9d10114f5661ecf1e24b677d239b0100af8114c798db0500000090a300009f62141a8aec30e70000000037d400006e0f000029efaf57000000000000000000000000000000000000000000000000000000000000000000000000000000008000000100000000000005a0","target":"ffffffffffffffffffffffffffffffffffffffffffffffffffffff3f00000000"},"id":0,"error":null}
00:09:39:567 3d0 DCR: Connected (dcr.maxminers.net:7728)
00:09:39:567 3d0 DCR job updated
00:09:39:687 b20 got 282 bytes
00:09:39:687 b20 buf: {"jsonrpc":"2.0","id":2,"result":true}
{"jsonrpc":"2.0","id":0,"result":["0x418107c5c15fb00abb0eca602a23123a6e0c1cae3b63e6498956820d157d2122","0xdeb13fd7c8eb5b6e43fe49e77f32c5e38fd7679be198414e839c7e1b83f17dc5","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
00:09:39:687 b20 parse packet: 38
00:09:39:687 b20 ETH: Authorized
00:09:39:688 b20 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
00:09:39:688 b20 remove first packet 243
00:09:39:688 b20 new buf size: 243
00:09:39:688 b20 parse packet: 242
00:09:39:688 b20 eth: job changed
00:09:39:688 b20 new buf size: 0
00:09:39:710 dac Setting DAG epoch #68...
00:09:39:814 b20 got 243 bytes
00:09:39:814 b20 buf: {"jsonrpc":"2.0","id":0,"result":["0x418107c5c15fb00abb0eca602a23123a6e0c1cae3b63e6498956820d157d2122","0xdeb13fd7c8eb5b6e43fe49e77f32c5e38fd7679be198414e839c7e1b83f17dc5","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
00:09:39:814 b20 parse packet: 242
00:09:39:814 b20 eth: job is the same
00:09:39:814 b20 new buf size: 0
00:09:41:927 e18 Setting DAG epoch #68 for GPU #1
00:09:41:927 e18 Create GPU buffer for GPU #1
00:09:41:927 e18 OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:41:927 4b0 Setting DAG epoch #68 for GPU #2
00:09:41:928 4b0 Create GPU buffer for GPU #2
00:09:41:928 4b0 OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:41:928 b9c Setting DAG epoch #68 for GPU #3
00:09:41:928 b9c Create GPU buffer for GPU #3
00:09:41:929 b9c OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:41:929 dac Setting DAG epoch #68 for GPU #0
00:09:41:929 dac Create GPU buffer for GPU #0
00:09:41:929 dac OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
00:09:42:494 e44 OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
00:09:42:497 e44 OC v5, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
00:09:42:499 e44 OC v5, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst
00:09:42:502 e44 OC v5, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst
August 13, 2016, 11:59:00 PM
set pagefile to 16gb, remove # from esm line and have more than 2gb gpu's.
so this is your start.bat
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe
and this your config.txt
-epool eth-us-east1.nanopool.org:9999
-ewal 0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB
-epsw x
-esm 0
-estale 0
-dpool http://dcr.maxminers.net:7728
-dwal alexmobile.alexmobile
-dpsw 0311
-mode 0
-tt 80
if dcr doesn't start, change esm values, from 0 to 3, see which is good for that pool
so this is your start.bat
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe
and this your config.txt
-epool eth-us-east1.nanopool.org:9999
-ewal 0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB
-epsw x
-esm 0
-estale 0
-dpool http://dcr.maxminers.net:7728
-dwal alexmobile.alexmobile
-dpsw 0311
-mode 0
-tt 80
if dcr doesn't start, change esm values, from 0 to 3, see which is good for that pool
August 13, 2016, 11:40:05 PM
Good morning
Couldn't get Claymore to function figured it maybe the pools I chose my start.bat file is as follows but I am getting errors like crazy.
Hopefully someone has some ideas I am at a Loss
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe
-epool eth-us-east1.nanopool.org:9999
-ewal 0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB
-epsw x
#-esm 0
-estale 0
-dpool http://dcr.maxminers.net:7728
-dwal alexmobile.alexmobile
-dpsw 0311
-mode 0
-tt 80
Errors I am receiving...
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
23:24:19:108 d04 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
23:24:19:109 d04 DCR - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
23:24:19:111 d04 DCR: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
Setting DAG epoch #68 for GPU #0
23:24:21:169 c1c Create GPU buffer for GPU #0
23:24:21:171 c1c OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
23:24:21:172 d1c Setting DAG epoch #68 for GPU #3
23:24:21:174 d1c Create GPU buffer for GPU #3
23:24:21:177 d1c OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
23:24:21:178 538 Setting DAG epoch #68 for GPU #2
23:24:21:181 538 Create GPU buffer for GPU #2
23:24:21:183 538 OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
23:24:21:186 cfc Setting DAG epoch #68 for GPU #1
23:24:21:187 cfc Create GPU buffer for GPU #1
and this as well
DCR job updated
23:24:24:175 b84 Setting DAG epoch #68 for GPU #0
23:24:24:181 b84 GPU 0, OpenCL error -38 - cannot write buffer for DAG
23:24:24:186 d74 Setting DAG epoch #68 for GPU #3
23:24:24:192 d74 GPU 3, OpenCL error -38 - cannot write buffer for DAG
23:24:24:198 e68 Setting DAG epoch #68 for GPU #2
23:24:24:203 e68 GPU 2, OpenCL error -38 - cannot write buffer for DAG
23:24:24:207 3d0 Setting DAG epoch #68 for GPU #1
23:24:24:211 3d0 GPU 1, OpenCL error -38 - cannot write buffer for DAG
Couldn't get Claymore to function figured it maybe the pools I chose my start.bat file is as follows but I am getting errors like crazy.
Hopefully someone has some ideas I am at a Loss
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe
-epool eth-us-east1.nanopool.org:9999
-ewal 0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB
-epsw x
#-esm 0
-estale 0
-dpool http://dcr.maxminers.net:7728
-dwal alexmobile.alexmobile
-dpsw 0311
-mode 0
-tt 80
Errors I am receiving...
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
23:24:19:108 d04 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
23:24:19:109 d04 DCR - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
23:24:19:111 d04 DCR: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s
Setting DAG epoch #68 for GPU #0
23:24:21:169 c1c Create GPU buffer for GPU #0
23:24:21:171 c1c OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
23:24:21:172 d1c Setting DAG epoch #68 for GPU #3
23:24:21:174 d1c Create GPU buffer for GPU #3
23:24:21:177 d1c OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
23:24:21:178 538 Setting DAG epoch #68 for GPU #2
23:24:21:181 538 Create GPU buffer for GPU #2
23:24:21:183 538 OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
23:24:21:186 cfc Setting DAG epoch #68 for GPU #1
23:24:21:187 cfc Create GPU buffer for GPU #1
and this as well
DCR job updated
23:24:24:175 b84 Setting DAG epoch #68 for GPU #0
23:24:24:181 b84 GPU 0, OpenCL error -38 - cannot write buffer for DAG
23:24:24:186 d74 Setting DAG epoch #68 for GPU #3
23:24:24:192 d74 GPU 3, OpenCL error -38 - cannot write buffer for DAG
23:24:24:198 e68 Setting DAG epoch #68 for GPU #2
23:24:24:203 e68 GPU 2, OpenCL error -38 - cannot write buffer for DAG
23:24:24:207 3d0 Setting DAG epoch #68 for GPU #1
23:24:24:211 3d0 GPU 1, OpenCL error -38 - cannot write buffer for DAG
August 13, 2016, 09:53:00 PM
EthDcrMiner64.exe
-epool -epool eth-eu.dwarfpool.com:8008
-ewal 0xEDa996a87AAaF6fa15580ADa4da6Da235bea21eB
-epsw x
-esm 0
-estale 0
-dpool http://dcr.suprnova.cc:9111
-dwal DsVTU7gM65rWtz6SSSZFLRfH7MkFQMNBMTZ
-dpsw x
-mode 0
-tt 70
You are repeating the parameter "-epool"
August 13, 2016, 08:24:32 PM
I am trying to get a headless (without X) system running with manjaro Linux.
The mining works, but when I start claymore's miner I get this error between the lines:
ADL Initialization Error!
And because of this I can't have temperature monitoring/management.
Claymore or anyone else with linux knowledge, is it possible to have ADL (AMD Display Library) working without X installed ?
The mining works, but when I start claymore's miner I get this error between the lines:
ADL Initialization Error!
And because of this I can't have temperature monitoring/management.
Claymore or anyone else with linux knowledge, is it possible to have ADL (AMD Display Library) working without X installed ?
I use a headless linux rig, well... I try to use lunix in all my PCs
At the end I solved that problem installing X, but only the core.
Then add the enviroment variable DISPLAY.
Code:
export DISPLAY=:0
Don't forget add the information in the X file conf:
Code:
amdconfig --adapter=all --initial
Reboot, and see if your problem is solved.
August 13, 2016, 07:57:19 PM
Is the explicit check for "AMD hardware" (through the OpenCL provider, it seems) really necessary?
I was curious how the new in-tree opensource "amdgpu" Linux driver with Mesa's OpenCL 1.x implementation might performs but your miner refused to start.
It's supposed to handle mining workloads (the Mesa wiki explicitly mentions mining) unless you have OpenCL >1.2 code. The 4.5-RC1 kernel is also supposed to be able to control things like GPU and RAM clock speeds through sysfs variables (so, ADL won't be mandatory either, although I guess the number of the available controls is very limited at this point, so ADL should probably be preferred for now).
I was curious how the new in-tree opensource "amdgpu" Linux driver with Mesa's OpenCL 1.x implementation might performs but your miner refused to start.
It's supposed to handle mining workloads (the Mesa wiki explicitly mentions mining) unless you have OpenCL >1.2 code. The 4.5-RC1 kernel is also supposed to be able to control things like GPU and RAM clock speeds through sysfs variables (so, ADL won't be mandatory either, although I guess the number of the available controls is very limited at this point, so ADL should probably be preferred for now).
I am trying to get a headless (without X) system running with manjaro Linux.
I saw many claiming it's possible. I use a dead HDTV motherboard as a phantom display (one HDMI cable per system should suffice, so one board might provide for 3-4 "rigs" and you can pull one from any dead TV). I think those who succeeded might use some older VGAs which still have internal DAC (digital/analog converter for analog D-sub output) and they automatically claimed the DAC as their phantom display.Thanks for the reply, but by headless I meant a system without the X server installed, not without a monitor connected. I think there are ways to trick the driver into thinking there is a monitor connected once you have the X server running.
August 13, 2016, 06:48:43 PM
Is the explicit check for "AMD hardware" (through the OpenCL provider, it seems) really necessary?
I was curious how the new in-tree opensource "amdgpu" Linux driver with Mesa's OpenCL 1.x implementation might performs but your miner refused to start.
It's supposed to handle mining workloads (the Mesa wiki explicitly mentions mining) unless you have OpenCL >1.2 code. The 4.5-RC1 kernel is also supposed to be able to control things like GPU and RAM clock speeds through sysfs variables (so, ADL won't be mandatory either, although I guess the number of the available controls is very limited at this point, so ADL should probably be preferred for now).
I was curious how the new in-tree opensource "amdgpu" Linux driver with Mesa's OpenCL 1.x implementation might performs but your miner refused to start.
It's supposed to handle mining workloads (the Mesa wiki explicitly mentions mining) unless you have OpenCL >1.2 code. The 4.5-RC1 kernel is also supposed to be able to control things like GPU and RAM clock speeds through sysfs variables (so, ADL won't be mandatory either, although I guess the number of the available controls is very limited at this point, so ADL should probably be preferred for now).
I am trying to get a headless (without X) system running with manjaro Linux.
I saw many claiming it's possible. I use a dead HDTV motherboard as a phantom display (one HDMI cable per system should suffice, so one board might provide for 3-4 "rigs" and you can pull one from any dead TV). I think those who succeeded might use some older VGAs which still have internal DAC (digital/analog converter for analog D-sub output) and they automatically claimed the DAC as their phantom display. August 13, 2016, 06:28:51 PM
I am trying to get a headless (without X) system running with manjaro Linux.
The mining works, but when I start claymore's miner I get this error between the lines:
ADL Initialization Error!
And because of this I can't have temperature monitoring/management.
Claymore or anyone else with linux knowledge, is it possible to have ADL (AMD Display Library) working without X installed ?
The mining works, but when I start claymore's miner I get this error between the lines:
ADL Initialization Error!
And because of this I can't have temperature monitoring/management.
Claymore or anyone else with linux knowledge, is it possible to have ADL (AMD Display Library) working without X installed ?
August 13, 2016, 05:13:04 PM
WHAT IS XCRI? --
My GTX 960 cards are happily mining ETH just now. Please let me know some more about XCRI. --scryptr
XCN, I remember 750ti did 5MH on djm´s miner, 960 could be profitable if it is doing more. Nethash is already 3GH but still could be worth checking.
Claymores miner does 8-9MH on 290x so nice nvidia advantage there, atleast on 750ti.
XCN JUST HAD A PRICE SPIKE--
I checked it out, looked at the thread, and tried to find a current CCminer for it. DJM34's work is from 2014, about v1.02 of CCminer. I found a CudaMineer binary, but haven't been able to launch it yet. Claymore's miner for XCN has recent.y been updated for Win10, and sits at v2.2; his is the most current GPU miner available. SuprNova pool for XCN just re-opened.
I will fiddle with it later, I have a rig to build. --scryptr
August 13, 2016, 01:51:27 PM
BTW - which GPU is the most powerfull for ETH mining and what is the hash speed of it??
390X or 1080? Or something else...?
390X or 1080? Or something else...?
Go for MSI 390 - 270-280 dollars - 30 Mhs Eth + 600 Mhs Sia
Avoid Gigabyte
far cheapear them 1080 and almost the same for eth
390s are also very stable & solid performer esp. those MSI ones.
But beware..... 390s are gas-guzzlers! They can suck the life out of your PSU.
Always undervolt - I get 30.xxMhs per card after -96mV/1040/1125 in AB.
I under volt to 990 mV of the core voltage and can get 27.5 MH/s with 978/1000 MHz. The power consumption is about 160W on the wall.
But that is still less efficient than the AMD RX 480. If you have higher power price, it is better to use 480.
August 13, 2016, 09:36:28 AM
WHAT IS XCRI? --
My GTX 960 cards are happily mining ETH just now. Please let me know some more about XCRI. --scryptr
XCN, I remember 750ti did 5MH on djm´s miner, 960 could be profitable if it is doing more. Nethash is already 3GH but still could be worth checking.
Claymores miner does 8-9MH on 290x so nice nvidia advantage there, atleast on 750ti.
August 13, 2016, 08:09:05 AM
Over 48 hours Rx 470 mining 21.5 mhs with genoil 1.1.7 in the 110 branch of github latest 16.8.1 hot fix drivers. So def is claymore miner. I Just run three 390x with claymore and rx470 In separate instance with genoil. If you get xfx 390x they are unlocked and can be undervolted for significant gains in efficiency with no loss in mining speed.
Best Regards
d57heinz
Best Regards
d57heinz
August 13, 2016, 07:02:00 AM
Hey Guys,
i need a bit help.. i am just switching my rigs to mine with Claymores mining (i do have alot of R9 Nanos).. for testing purpose i started moving 1 rig with 5 R9 Nanos to mine with Claymores Miner.. i justed to mine with EthMiner on local proxy with hashrate around 125Mh.. no moving to Claymore Miner i only get 82Mh and 4900Mh on Sia.. i was setting global and local worksize when i was connecting with Ethminer to the proxy.
is such difference normal form 125Mh to 82Mh.. if not does anyone have pointer?
Thnx!
ps on ethminer with proxy the card where getting close to 80c now they are at 70 and even some cooler.. so it seems the cards aren't going all out?
i need a bit help.. i am just switching my rigs to mine with Claymores mining (i do have alot of R9 Nanos).. for testing purpose i started moving 1 rig with 5 R9 Nanos to mine with Claymores Miner.. i justed to mine with EthMiner on local proxy with hashrate around 125Mh.. no moving to Claymore Miner i only get 82Mh and 4900Mh on Sia.. i was setting global and local worksize when i was connecting with Ethminer to the proxy.
is such difference normal form 125Mh to 82Mh.. if not does anyone have pointer?
Thnx!
ps on ethminer with proxy the card where getting close to 80c now they are at 70 and even some cooler.. so it seems the cards aren't going all out?
August 13, 2016, 05:59:34 AM
Some news:
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
There is a driver that works. You need the latest Windows 10 update (anniversary edition 1607) and then you need to update the driver through windows (weird I know, nvidia hasn't published it yet).
You can find the details here: https://forum.ethereum.org/discussion/2227/cuda-miner/p64
Then the 10xx series will work with Win 10.
I'd like to test it on Win7 firstly, I don't like Win10 with its paranoid defender, updates, two control panels, etc. Anyway, I will try to make it work in Win7, if it fails I'll try Win10.
Ya, the fix seems to be exclusive to Win10 but people are getting 30+mh/s now with the 1070s.
I have a GTX 960 in my desktop system and the only way to get more than 3mh/s is to use a build of Genoil's miner on CUDA 6.5 and use the older 347 nvidia drivers. Then I get around 10mh/s with it.
GTX 960 MAKES ~10MH/s MINING ETH--
I have a five card GTX 960 rig on Ubunto 14.04 and it makes about 52MH/s total. A properly configured GTX 1060 will do twice that, 18-20MH/s, same as a good GTX 970. --scryptr
Sorry again for OT but scryptr, have you tried xcn with those 960's?
WHAT IS XCRI? --
My GTX 960 cards are happily mining ETH just now. Please let me know some more about XCRI. --scryptr
August 13, 2016, 05:56:46 AM
BTW - which GPU is the most powerfull for ETH mining and what is the hash speed of it??
390X or 1080? Or something else...?
390X or 1080? Or something else...?
Go for MSI 390 - 270-280 dollars - 30 Mhs Eth + 600 Mhs Sia
Avoid Gigabyte
far cheapear them 1080 and almost the same for eth
390s are also very stable & solid performer esp. those MSI ones.
But beware..... 390s are gas-guzzlers! They can suck the life out of your PSU.
Always undervolt - I get 30.xxMhs per card after -96mV/1040/1125 in AB.
I under volt to 990 mV of the core voltage and can get 27.5 MH/s with 978/1000 MHz. The power consumption is about 160W on the wall.
August 12, 2016, 10:51:48 PM
Some news:
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
There is a driver that works. You need the latest Windows 10 update (anniversary edition 1607) and then you need to update the driver through windows (weird I know, nvidia hasn't published it yet).
You can find the details here: https://forum.ethereum.org/discussion/2227/cuda-miner/p64
Then the 10xx series will work with Win 10.
I'd like to test it on Win7 firstly, I don't like Win10 with its paranoid defender, updates, two control panels, etc. Anyway, I will try to make it work in Win7, if it fails I'll try Win10.
Ya, the fix seems to be exclusive to Win10 but people are getting 30+mh/s now with the 1070s.
I have a GTX 960 in my desktop system and the only way to get more than 3mh/s is to use a build of Genoil's miner on CUDA 6.5 and use the older 347 nvidia drivers. Then I get around 10mh/s with it.
GTX 960 MAKES ~10MH/s MINING ETH--
I have a five card GTX 960 rig on Ubunto 14.04 and it makes about 52MH/s total. A properly configured GTX 1060 will do twice that, 18-20MH/s, same as a good GTX 970. --scryptr
Ya I know 10mh/s is about all a 960 will get, just saying it requires me to use an older driver and CUDA version to get it unfortunately.
August 12, 2016, 07:54:19 PM
Some news:
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
There is a driver that works. You need the latest Windows 10 update (anniversary edition 1607) and then you need to update the driver through windows (weird I know, nvidia hasn't published it yet).
You can find the details here: https://forum.ethereum.org/discussion/2227/cuda-miner/p64
Then the 10xx series will work with Win 10.
I'd like to test it on Win7 firstly, I don't like Win10 with its paranoid defender, updates, two control panels, etc. Anyway, I will try to make it work in Win7, if it fails I'll try Win10.
Ya, the fix seems to be exclusive to Win10 but people are getting 30+mh/s now with the 1070s.
I have a GTX 960 in my desktop system and the only way to get more than 3mh/s is to use a build of Genoil's miner on CUDA 6.5 and use the older 347 nvidia drivers. Then I get around 10mh/s with it.
GTX 960 MAKES ~10MH/s MINING ETH--
I have a five card GTX 960 rig on Ubunto 14.04 and it makes about 52MH/s total. A properly configured GTX 1060 will do twice that, 18-20MH/s, same as a good GTX 970. --scryptr
Sorry again for OT but scryptr, have you tried xcn with those 960's?
Jump to: