ffthomas
|
|
August 27, 2019, 09:20:15 AM |
|
test it with: EthDcrMiner64.exe -benchmark 2
it will use just ~1GB of ram for DAG maybe rx5700 can show real speed under some memory footprint
The problem is on driver level and it isn't related to DAG size - as far as I know. I tried to run a benchmark but the result is nearly the same (instead of 3,5MH/s I got 3,6MH/s )
|
|
|
|
|
|
|
|
TalkImg was created especially for hosting images on bitcointalk.org: try it next time you want to post an image
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
minzak
Newbie
Offline
Activity: 2
Merit: 0
|
|
August 27, 2019, 10:47:35 AM |
|
After run ethdcrminer64 latest v15 i got message: NVIDIA NVML library not found, temperature monitoring for NVIDIA GPUs disabled.CUDA initializing...
NVIDIA Cards available: 1 CUDA Driver Version/Runtime Version: 10.1/8.0 GPU #0: GeForce GTX 1050 Ti, 4039 MB available, 6 compute units, capability: 6.1 (pci bus 1:0:0) Total cards: 1
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.
NVIDIA NVML library not found, temperature monitoring for NVIDIA GPUs disabled. ETH: Stratum - connecting to 'eu1.ethermine.org' <172.65.207.106> port 4444 (unsecure) ETH: Stratum - Connected (eu1.ethermine.org:4444) (unsecure) ETH: Authorized ETHEREUM-ONLY MINING MODE ENABLED (-mode 1) It is impossible, because nvidia-smi is fine worked. root@debian:~# nvidia-smi Tue Aug 27 13:32:38 2019 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 418.74 Driver Version: 418.74 CUDA Version: 10.1 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GTX 105... On | 00000000:01:00.0 Off | N/A | | 60% 29C P8 N/A / 75W | 60MiB / 4039MiB | 0% Default | +-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | 0 545 G /usr/lib/xorg/Xorg 18MiB | | 0 625 G /usr/bin/gnome-shell 39MiB | +-----------------------------------------------------------------------------+
Also needed library are present in system: root@debian:/opt/claymore# ldconfig -p | grep nvidia-ml libnvidia-ml.so.1 (libc6,x86-64) => /lib/x86_64-linux-gnu/libnvidia-ml.so.1
What is wrong? How to fix it?
|
|
|
|
MATHReX
|
|
August 27, 2019, 11:09:19 AM |
|
what exactly does -driver uninstall why should I do it and then restart?
It injects performance-related tweaks in the AMD driver which is not possible without modifying it, thus requiring administrator privileges and the parameter -driver uninstall which is essential when using parameters such as -strap or -rx boost
|
|
|
|
cmrho13
Newbie
Offline
Activity: 3
Merit: 0
|
|
August 27, 2019, 05:16:34 PM |
|
Does anyone know the last Linux compatible version of Claymore's miner? I'm running Ethos and it hasn't updated since v12.0. Thanks in advance.
|
|
|
|
webgkv
Newbie
Offline
Activity: 57
Merit: 0
|
|
August 27, 2019, 06:10:01 PM |
|
I will release v14.8 within a few days, it will set environment variables automatically too, right now you can use b747 if you have problems with DAG on 4GB AMD cards.
Hi! Can we expect in v14.8 straps for linux? Is this even possible? Linux is out of deal again
|
|
|
|
adaseb
Legendary
Offline
Activity: 3752
Merit: 1710
|
|
August 28, 2019, 05:09:15 AM |
|
Wow been a while since I've seen a new version of Claymore coming out. Looks like V15.0 has been released for over about a day and only about 20 posts followed the launch. This is actually pretty low compared to the good old days of 2017 where whenever Claymore released a new version usually about 5-10 pages would happened in the following hours after the launch. His ZEC miner was also pretty popular during those days.
Its sad to see GPU mining going downhill where many people have moved onto something else. Really hoping that ETH devs do something and get ProgPOW added to the Q1 2020 fork and we might see a comeback of miners.
But right now in my area, I am getting barely a quarter a day of net profit with a single GPU. Sure wish the days of $1/day/GPU would come back.
|
|
|
|
justoiurii
Newbie
Offline
Activity: 103
Merit: 0
|
|
August 28, 2019, 08:28:53 AM |
|
Claymore's Dual Ethereum + Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak AMD+NVIDIA GPU Miner.
Hello, DEV) Is it possible dual mining SIA? For a long time SIA is being mined only with obelisk asic. Why you keep wrong information on the topic? Or am I wrong?
|
|
|
|
Branko
|
|
August 28, 2019, 08:33:58 AM |
|
Claymore's Dual Ethereum + Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak AMD+NVIDIA GPU Miner.
Hello, DEV) Is it possible dual mining SIA? For a long time SIA is being mined only with obelisk asic. Why you keep wrong information on the topic? Or am I wrong? I think its possible, although you'll only earn about 1 cent per 97 years (minus cost for electricity)
|
|
|
|
Eliovp
Legendary
Offline
Activity: 1050
Merit: 1293
Huh?
|
|
August 28, 2019, 11:40:46 AM |
|
Wow been a while since I've seen a new version of Claymore coming out. Looks like V15.0 has been released for over about a day and only about 20 posts followed the launch. This is actually pretty low compared to the good old days of 2017 where whenever Claymore released a new version usually about 5-10 pages would happened in the following hours after the launch. His ZEC miner was also pretty popular during those days.
Its sad to see GPU mining going downhill where many people have moved onto something else. Really hoping that ETH devs do something and get ProgPOW added to the Q1 2020 fork and we might see a comeback of miners.
But right now in my area, I am getting barely a quarter a day of net profit with a single GPU. Sure wish the days of $1/day/GPU would come back.
ProgPow is not going to solve that. On the contrary. The algorithm is designed to make it easier for FPGA's to join the game. I hope i'm wrong.
|
|
|
|
crypsy
|
|
August 28, 2019, 03:51:51 PM |
|
Hi, I have a few r9 380 4gb and they are only getting 13mh/s . I have -y 1 but can't apply straps for some reason .Windows 10 and latest version of claymore miner. please advise
|
btc: 183ZdPA9c5XkGgacaN9q7aJY93asV2BnKt eth: 0x144c3b9d9c3c6e465d4cfe136d318440e81bb39e
|
|
|
crypsy
|
|
August 28, 2019, 06:21:15 PM |
|
Same with r9 390, only 20mhs... that is not working correctly .
|
btc: 183ZdPA9c5XkGgacaN9q7aJY93asV2BnKt eth: 0x144c3b9d9c3c6e465d4cfe136d318440e81bb39e
|
|
|
Andrew_Tassel
Newbie
Offline
Activity: 32
Merit: 0
|
|
August 28, 2019, 06:47:17 PM |
|
Same with r9 390, only 20mhs... that is not working correctly .
No, this is correct hashrate for 290/390 now. Were are no blockchain drivers and calculator mode for 290/390 on Windows. You must use Linux (HiveOS) to get 29 mh/s on ETH/ETC or mine other coins with lesser DAG file.
|
|
|
|
Darcendsun
Newbie
Offline
Activity: 5
Merit: 0
|
|
August 28, 2019, 07:48:42 PM |
|
When the directions say this... For AMD cards, set the following environment variables, especially if you have 2...4GB cards:
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
Does that mean to put those environment variables inside the start.bat somewhere? If so, how exactly so that the syntax is correct? For now, my start.bat simply looks like this: EthDcrMiner64.exe -epool ssl://us2.ethermine.org:5555 -eworker Rig2 -ewal 0xC42D3d4a31d7aeEbFd25e51858F45172B6047F50 -epsw x Thanks in advance, Darcendsun
|
|
|
|
MahaBTC
Newbie
Offline
Activity: 24
Merit: 0
|
|
August 28, 2019, 10:38:21 PM |
|
When the directions say this... For AMD cards, set the following environment variables, especially if you have 2...4GB cards:
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
Does that mean to put those environment variables inside the start.bat somewhere? If so, how exactly so that the syntax is correct? For now, my start.bat simply looks like this: EthDcrMiner64.exe -epool ssl://us2.ethermine.org:5555 -eworker Rig2 -ewal 0xC42D3d4a31d7aeEbFd25e51858F45172B6047F50 -epsw x Thanks in advance, Darcendsun It should look like this: 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 ssl://us2.ethermine.org:5555 -eworker Rig2 -ewal 0xC42D3d4a31d7aeEbFd25e51858F45172B6047F50 -epsw x You should also try at least: -rxboost 1 if you have rx card that is
|
|
|
|
adaseb
Legendary
Offline
Activity: 3752
Merit: 1710
|
Wow been a while since I've seen a new version of Claymore coming out. Looks like V15.0 has been released for over about a day and only about 20 posts followed the launch. This is actually pretty low compared to the good old days of 2017 where whenever Claymore released a new version usually about 5-10 pages would happened in the following hours after the launch. His ZEC miner was also pretty popular during those days.
Its sad to see GPU mining going downhill where many people have moved onto something else. Really hoping that ETH devs do something and get ProgPOW added to the Q1 2020 fork and we might see a comeback of miners.
But right now in my area, I am getting barely a quarter a day of net profit with a single GPU. Sure wish the days of $1/day/GPU would come back.
ProgPow is not going to solve that. On the contrary. The algorithm is designed to make it easier for FPGA's to join the game. I hope i'm wrong. The long ProgPOW audit which is being conducted by a 3rd party is suppose to investigate that isn't it. Because right now we have say 50% ASICs and 50% GPUs mining on the old DaggerHashimoto algo. If ProgPOW will turn it into a haven for FPGA's where 90% FPGA and 10% GPUs then most likely the algo will never get changed since in my opinion FPGA's depending on the supplier, can become more centralized than ASICs themselves. No idea when this audit will come out, was suppose to be due end of August according to ethermine pool.
|
|
|
|
MATHReX
|
|
August 29, 2019, 02:12:08 PM |
|
Claymore's Dual Ethereum + Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak AMD+NVIDIA GPU Miner.
Hello, DEV) Is it possible dual mining SIA? For a long time SIA is being mined only with obelisk asic. Why you keep wrong information on the topic? Or am I wrong? There is no wrong information in the ANN. SIA and all the other dual mining coins that are available in the miner can be mined using Claymore. The question is, Is it profitable to mine them? Not at all. So, yes, dual mining is possible but not profitable.
|
|
|
|
zoid009
Newbie
Offline
Activity: 6
Merit: 0
|
|
August 29, 2019, 03:50:58 PM |
|
Hi, Did you solve the problem? I'm having trouble running claymore on RTX cards. Something is wrong with the DAG file. It doesn’t matter which pool, the version of nvidia drivers, the version of Claymore, fork of ETH. GPU 0, GpuMiner cu_kd failed 8 (0), invalid device function GPU 0, Calc DAG failed! OS Version: 4.13.16-hiveos Drivers: N430.40 16:31:11:160 e95fd740 Check and remove old log files... 16:31:11:160 e95fd740 args: -mport -3333 -r 1 -logfile /var/log/miner/claymore/lastrun_noappend.log -tt 68 -ttli 76 -tstop 82 -mode 1 -allcoins etc -allpo 16:31:11:160 e95fd740 16:31:11:160 e95fd740 ................................................................ͻ 16:31:11:160 e95fd740 . Claymore's Dual GPU Miner - v15.0 . 16:31:11:160 e95fd740 . ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK . 16:31:11:160 e95fd740 ................................................................ͼ 16:31:11:160 e95fd740 16:31:11:160 e95fd740 b755 16:31:11:360 e95fd740 no address specified - ignore 16:31:11:360 e95fd740 ETH: 1 pool is specified 16:31:11:360 e95fd740 Main Ethereum pool is b2g.baikalmine.com:3377 16:31:12:045 e95fd740 OpenCL platform: NVIDIA CUDA 16:31:12:045 e95fd740 AMD OpenCL platform not found 16:31:12:078 e95fd740 CUDA initializing...
16:31:12:078 e95fd740 NVIDIA Cards available: 2 16:31:12:078 e95fd740 CUDA Driver Version/Runtime Version: 10.1/8.0 16:31:12:081 e95fd740 GPU #0: GeForce RTX 2070, 7951 MB available, 36 compute units, capability: 7.5 (pci bus 3:0:0) 16:31:12:081 e95fd740 GPU #1: GeForce RTX 2060, 5904 MB available, 30 compute units, capability: 7.5 (pci bus 4:0:0) 16:31:12:081 e95fd740 Total cards: 2 16:31:16:083 e95fd740 You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.
16:31:17:085 e95fd740 NVML version: 10.418.74 16:31:17:348 b9fff700 ETH: Stratum - connecting to 'b2g.baikalmine.com' <194.87.205.37> port 3377 (unsecure) 16:31:17:350 b9fff700 sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xb2f44ee55fb579040470ca9fcb116c42698c5912.z03", "x"], "id": 2, "method": "
16:31:17:350 b9fff700 ETH: Stratum - Connected (b2g.baikalmine.com:3377) (unsecure) 16:31:17:360 b9fff700 buf: {"id":2,"jsonrpc":"2.0","result":true}
16:31:17:360 b9fff700 ETH: Authorized 16:31:17:360 b9fff700 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
16:31:17:371 b9fff700 buf: {"id":3,"jsonrpc":"2.0","result":["0x178dc0b48e863f3716b5d8add18824a34e4537b1ba5490c6d6a679b293b8dd24","0x3a619bccb58fc05648705
16:31:17:447 e95fd740 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
16:31:17:447 e95fd740 ETH: eth-proxy stratum mode 16:31:17:447 e95fd740 "-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details. 16:31:17:447 e95fd740 Watchdog enabled 16:31:17:447 e95fd740 Remote management (READ-ONLY MODE) is enabled on port 3333 16:31:17:447 e95fd740 16:31:17:535 d6ffd700 Setting DAG epoch #101(1.79GB)... 16:31:19:604 d6ffd700 Setting DAG epoch #101 for GPU0 16:31:19:604 d0ffd700 Setting DAG epoch #101 for GPU1 16:31:19:604 d6ffd700 Create GPU buffer for GPU0 16:31:19:604 d0ffd700 Create GPU buffer for GPU1 16:31:19:630 d6ffd700 GPU 0, GpuMiner cu_kd failed 8 (0), invalid device function 16:31:19:630 d6ffd700 GPU 0, Calc DAG failed! 16:31:19:630 d0ffd700 GPU 1, GpuMiner cu_kd failed 8 (0), invalid device function 16:31:19:630 d0ffd700 GPU 1, Calc DAG failed! 16:31:22:453 b17fe700 srv_thr cnt: 1, IP: 127.0.0.1 16:31:22:453 b17fe700 recv: 51 16:31:22:453 b17fe700 srv pck: 50 16:31:22:455 b17fe700 srv bs: 0 16:31:22:455 b17fe700 sent: 207 16:31:23:130 d0ffd700 Set global fail flag, failed GPU1 16:31:23:130 d6ffd700 Set global fail flag, failed GPU0 16:31:23:131 d6ffd700 GPU 0 failed 16:31:23:131 d0ffd700 GPU 1 failed 16:31:23:131 d1fff700 Setting DAG epoch #101 for GPU0 16:31:23:131 d17fe700 Setting DAG epoch #101 for GPU1 16:31:23:152 d17fe700 GPU 1, GpuMiner cu_kd failed 8 (0), invalid device function 16:31:23:152 d17fe700 GPU 1, Calc DAG failed! 16:31:23:152 d1fff700 GPU 0, GpuMiner cu_kd failed 8 (0), invalid device function 16:31:23:152 d1fff700 GPU 0, Calc DAG failed! 16:31:26:652 d1fff700 Set global fail flag, failed GPU0 16:31:26:652 d1fff700 GPU 0 failed 16:31:26:652 d17fe700 Set global fail flag, failed GPU1 16:31:26:653 d17fe700 GPU 1 failed 16:31:27:372 b9fff700 ETH: checking pool connection... 16:31:27:372 b9fff700 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
16:31:27:375 b9fff700 buf: {"id":3,"jsonrpc":"2.0","result":["0x178dc0b48e863f3716b5d8add18824a34e4537b1ba5490c6d6a679b293b8dd24","0x3a619bccb58fc05648705
16:31:31:278 d17fe700 srv_thr cnt: 1, IP: 127.0.0.1 16:31:31:278 d17fe700 recv: 51 16:31:31:278 d17fe700 srv pck: 50 16:31:31:280 d17fe700 srv bs: 0 16:31:31:280 d17fe700 sent: 207 16:31:37:373 b9fff700 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x0000000000000000000000000000000000000000000000000000
16:31:37:374 b9fff700 ETH: checking pool connection... 16:31:37:374 b9fff700 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
16:31:37:375 b9fff700 buf: {"id":6,"jsonrpc":"2.0","result":true}
16:31:37:380 b9fff700 buf: {"id":3,"jsonrpc":"2.0","result":["0x178dc0b48e863f3716b5d8add18824a34e4537b1ba5490c6d6a679b293b8dd24","0x3a619bccb58fc05648705
16:31:41:373 e6cca700 GPU0 t=27C fan=16% P=8W, GPU1 t=27C fan=0% P=4W 16:31:41:373 e6cca700 Total GPUs power consumption: 12 Watts 16:31:41:408 e74cb700 em hbt: 1, fm hbt: 19, 16:31:41:408 e74cb700 watchdog - thread 0 (gpu0), hb time 17756 16:31:41:408 e74cb700 watchdog - thread 1 (gpu0), hb time 17756 16:31:41:408 e74cb700 watchdog - thread 2 (gpu1), hb time 17756 16:31:41:408 e74cb700 watchdog - thread 3 (gpu1), hb time 17756 16:31:41:408 e74cb700 WATCHDOG: GPU error, you need to restart miner :( 16:31:41:408 e74cb700 Rebooting
|
|
|
|
Binary100100
Member
Offline
Activity: 180
Merit: 10
|
|
August 29, 2019, 04:50:32 PM |
|
Not sure what that has to do with this thread. Good luck though.
|
|
|
|
l30z1n
Newbie
Offline
Activity: 46
Merit: 0
|
|
August 29, 2019, 06:27:57 PM |
|
After AMD resolves the driver issue, how many Mhs at 5700/5700 XT are expected?
|
|
|
|
WhackOBill
Jr. Member
Offline
Activity: 73
Merit: 3
|
|
August 29, 2019, 09:06:02 PM |
|
After AMD resolves the driver issue, how many Mhs at 5700/5700 XT are expected?
Claymore might be able to say, but otherwise we're just guessing. I'm going with 54Mh/s for a 5700XT.
|
|
|
|
|