AzzAz
Legendary
Offline
Activity: 1030
Merit: 1006
|
|
September 21, 2018, 09:01:33 PM |
|
Fellow users of Claymore, I need some help
I have 1 miner with 6x AMD RX580 mining on Linux Mint 18.3, Kernel 4.13.0-41, amdgpu-pro driver 17.50, Claymore 11.9
The miner is running stable 175Mhs but still need some fine tuning.
I have modified the BIOS of the RX580 to achieve near 30MHs just by copying the bootstraps. Did not change values on the voltage.
Since I am achieving 175MHs means I am close to the 180MHs that is the standard for these RX580. So the MHs is not the issue.
The issue (where I need help) is related with Claymore software:
1 - No matter what changes I do in Claymore parameters -cclock and -mclock it has no effect whatsoever on the mining hash that is constant at 175MHs. This is what I do not understand. It seems the miner Claymore has no control over the GPU's clocks (core and memory)
2 - When running same miner on Windows 10 Pro I can adjust power usage (undervolting) to reach less power consumption by using OverdriveNTool and adjust voltages for 800 and 875 thus running the miner at lower temperatures and lower power consumption. I was expecting reach the same good results by adjusting the Claymore parameters to -cdvvc=800 and -mdvvc=875 but it does not work. It seems the miner Claymore has no control over the GPUs voltage (core and memory)
Here is my start.sh:
#!/bin/bash export GPU_MAX_ALLOC_PERCENT=100 ./ethdcrminer64 -epool ssl://eu1.ethermine.org:5555 -ewal xxx -epsw x -eworker xxx -etha 2 -asm 1 -mode 1 -wd 1 -tt 65 -cclock 1150 -mclock 2030 -cvddc 800 -mvddc 875 -platform 1 -y 1
Unless I am forgetting to do some adjustment I am reaching the conclusion the Claymore software is useless to adjust clock and voltage on Linux. It seems that the parameters -cclock -mclock -cdvvc -mdvvc are useless on Linux. Can this conclusion be correct?
noticed that on Windows too, 18.5.2 driver. Maybe some drivers working some no?
|
|
|
|
hackyminer
Newbie
Offline
Activity: 50
Merit: 0
|
|
September 23, 2018, 06:43:58 AM |
|
Claymore + Cygwin or MSYS2 console case => much slower console output + no color supported. Please fix this bug and thank you for this greate miner!!
|
|
|
|
pubix
Member
Offline
Activity: 154
Merit: 10
|
|
September 23, 2018, 10:03:52 AM |
|
Mining ETC with nvidia 3GB cards not possible anymore? This is my .bat: EthDcrMiner64.exe -epool etc-eu1.nanopool.org:19999 -ewal 0x9999999999.workername/email@email.com -epsw x -mode 1 -ftime 10
|
|
|
|
NiklasFalk
Jr. Member
Offline
Activity: 94
Merit: 1
|
|
September 23, 2018, 11:33:07 AM |
|
Mining ETC with nvidia 3GB cards not possible anymore? Then don't use Win10, the suggestion in the message is reasonable readable.
|
|
|
|
carlo_0000
Legendary
Offline
Activity: 1281
Merit: 1003
|
|
September 23, 2018, 02:02:10 PM |
|
hey i have an other problem with all my nvidia ring and msi afterburner msi after burner has a bug ? the max temp limit does not work , it s on 72°c in afternoon but when it s hot some gpu goes to 90° it s working fine on the amd https://ibb.co/b0TBuz (pic) Maybe try adding command -fanmin, -fanmax or -tt in your Claymore miner. For example -tt 70 should set your target gpu temperature to 70°C. Or even better, set fixed fan speed to e.g. 70% by adding command -tt -70 I know this works on AMD cards, but I am not sure it will work on nvidia, but you can try it out. problem i use multipolminer and use more miners
|
|
|
|
|
tg88
Legendary
Offline
Activity: 2436
Merit: 1412
|
|
September 25, 2018, 02:16:43 PM |
|
how to set claymore to choose next available servers, when primary server is down? for instance if us server is down, it will automatically changes to europe server. And after us server is up, it will go back to us server.
FAILOVER Use "epools.txt" and "dpools.txt" files to specify additional pools. These files have text format, one pool per line. Every pool has 3 connection attempts. Miner disconnects automatically if pool does not send new jobs for a long time or if pool rejects too many shares. Pool specified in the command line is "main" pool, miner will try to return to it every 30 minutes if it has to use some different pool from the list. If no pool was specified in the command line then first pool in the failover pools list is main pool. You can change 30 minutes time period to some different value with "-ftime" option, or use "-ftime 0" to disable switching to main pool. Is it normal that so many viruses have found?
This is normal, several antivirus programs detect it as a virus.
|
|
|
|
krnlx
|
|
September 25, 2018, 02:46:10 PM |
|
Not working on turing RTX 2080 card ????????????????????????????????????????????????????????????????ͻ ? Claymore's Dual GPU Miner - v11.9 ? ? ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK ? ????????????????????????????????????????????????????????????????ͼ
ETH: 1 pool is specified Main Ethereum pool is eu2.ethermine.org:4444 AMD OpenCL platform not found Be careful with overclocking, use default clocks for first tests Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU CUDA initializing...
NVIDIA Cards available: 4 CUDA Driver Version/Runtime Version: 10.0/8.0 GPU #0: GeForce RTX 2080, 7951 MB available, 46 compute units, capability: 7.5 (pci bus 1:0:0) GPU #1: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 2:0:0) GPU #2: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 3:0:0) GPU #3: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 4:0:0) Total cards: 4
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1) ETH: qtminer stratum mode Watchdog enabled Remote management (READ-ONLY MODE) is enabled on port 3333
ETH: Stratum - connecting to 'eu2.ethermine.org' <35.198.171.229> port 4444 (unsecure) ETH: Stratum - Connected (eu2.ethermine.org:4444) (unsecure) ETH: Authorized Setting DAG epoch #213... Setting DAG epoch #213 for GPU2 Setting DAG epoch #213 for GPU1 Setting DAG epoch #213 for GPU3 Create GPU buffer for GPU3 Setting DAG epoch #213 for GPU0 Create GPU buffer for GPU0 Create GPU buffer for GPU2 Create GPU buffer for GPU1 GPU 0, GpuMiner cu_kd failed 8 (0), invalid device function GPU 0, Calc DAG failed! GPU 3, GpuMiner cu_kd failed 8 (0), invalid device function GPU 3, Calc DAG failed! GPU 1, GpuMiner cu_kd failed 8 (0), invalid device function GPU 1, Calc DAG failed! GPU 2, GpuMiner cu_kd failed 8 (0), invalid device function GPU 2, Calc DAG failed! Linux, Driver Version: 410.57
|
|
|
|
AzzAz
Legendary
Offline
Activity: 1030
Merit: 1006
|
|
September 25, 2018, 11:57:48 PM |
|
Not working on turing RTX 2080 card ????????????????????????????????????????????????????????????????ͻ ? Claymore's Dual GPU Miner - v11.9 ? ? ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK ? ????????????????????????????????????????????????????????????????ͼ
ETH: 1 pool is specified Main Ethereum pool is eu2.ethermine.org:4444 AMD OpenCL platform not found Be careful with overclocking, use default clocks for first tests Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU CUDA initializing...
NVIDIA Cards available: 4 CUDA Driver Version/Runtime Version: 10.0/8.0 GPU #0: GeForce RTX 2080, 7951 MB available, 46 compute units, capability: 7.5 (pci bus 1:0:0) GPU #1: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 2:0:0) GPU #2: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 3:0:0) GPU #3: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 4:0:0) Total cards: 4
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1) ETH: qtminer stratum mode Watchdog enabled Remote management (READ-ONLY MODE) is enabled on port 3333
ETH: Stratum - connecting to 'eu2.ethermine.org' <35.198.171.229> port 4444 (unsecure) ETH: Stratum - Connected (eu2.ethermine.org:4444) (unsecure) ETH: Authorized Setting DAG epoch #213... Setting DAG epoch #213 for GPU2 Setting DAG epoch #213 for GPU1 Setting DAG epoch #213 for GPU3 Create GPU buffer for GPU3 Setting DAG epoch #213 for GPU0 Create GPU buffer for GPU0 Create GPU buffer for GPU2 Create GPU buffer for GPU1 GPU 0, GpuMiner cu_kd failed 8 (0), invalid device function GPU 0, Calc DAG failed! GPU 3, GpuMiner cu_kd failed 8 (0), invalid device function GPU 3, Calc DAG failed! GPU 1, GpuMiner cu_kd failed 8 (0), invalid device function GPU 1, Calc DAG failed! GPU 2, GpuMiner cu_kd failed 8 (0), invalid device function GPU 2, Calc DAG failed! Linux, Driver Version: 410.57 Cool, now you just have to find someone to write miner for you....Maybe send one to Claymore
|
|
|
|
Intristing
|
|
September 26, 2018, 08:35:38 AM |
|
Not working on turing RTX 2080 card ????????????????????????????????????????????????????????????????ͻ ? Claymore's Dual GPU Miner - v11.9 ? ? ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK ? ????????????????????????????????????????????????????????????????ͼ
ETH: 1 pool is specified Main Ethereum pool is eu2.ethermine.org:4444 AMD OpenCL platform not found Be careful with overclocking, use default clocks for first tests Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU CUDA initializing...
NVIDIA Cards available: 4 CUDA Driver Version/Runtime Version: 10.0/8.0 GPU #0: GeForce RTX 2080, 7951 MB available, 46 compute units, capability: 7.5 (pci bus 1:0:0) GPU #1: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 2:0:0) GPU #2: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 3:0:0) GPU #3: GeForce RTX 2080, 7952 MB available, 46 compute units, capability: 7.5 (pci bus 4:0:0) Total cards: 4
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1) ETH: qtminer stratum mode Watchdog enabled Remote management (READ-ONLY MODE) is enabled on port 3333
ETH: Stratum - connecting to 'eu2.ethermine.org' <35.198.171.229> port 4444 (unsecure) ETH: Stratum - Connected (eu2.ethermine.org:4444) (unsecure) ETH: Authorized Setting DAG epoch #213... Setting DAG epoch #213 for GPU2 Setting DAG epoch #213 for GPU1 Setting DAG epoch #213 for GPU3 Create GPU buffer for GPU3 Setting DAG epoch #213 for GPU0 Create GPU buffer for GPU0 Create GPU buffer for GPU2 Create GPU buffer for GPU1 GPU 0, GpuMiner cu_kd failed 8 (0), invalid device function GPU 0, Calc DAG failed! GPU 3, GpuMiner cu_kd failed 8 (0), invalid device function GPU 3, Calc DAG failed! GPU 1, GpuMiner cu_kd failed 8 (0), invalid device function GPU 1, Calc DAG failed! GPU 2, GpuMiner cu_kd failed 8 (0), invalid device function GPU 2, Calc DAG failed! Linux, Driver Version: 410.57 Cool, now you just have to find someone to write miner for you....Maybe send one to Claymore You may try the Phonex miner.
|
|
|
|
BTC22
Newbie
Offline
Activity: 322
Merit: 0
|
|
September 28, 2018, 07:17:26 PM |
|
Can anyone help here? Its been working fine for months. I had to reset my PC and now Im getting this:
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. GPU 4 failed Setting DAG epoch #213 for GPU4 GPU 2 failed Setting DAG epoch #213 for GPU2 GPU 5 failed Setting DAG epoch #213 for GPU1 GPU 4, CUDA error 11 - cannot write buffer for DAG Setting DAG epoch #213 for GPU5 GPU 1 failed GPU 2, CUDA error 11 - cannot write buffer for DAG GPU 1, CUDA error 11 - cannot write buffer for DAG GPU 5, CUDA error 11 - cannot write buffer for DAG GPU3 DAG creation time - 5891 ms Setting DAG epoch #213 for GPU3 done GPU6 DAG creation time - 6316 ms Setting DAG epoch #213 for GPU6 done GPU 4 failed GPU 1 failed GPU 5 failed GPU 2 failed
|
|
|
|
ScalperBTC
Newbie
Offline
Activity: 35
Merit: 0
|
|
September 29, 2018, 04:29:28 AM |
|
Something long ago there was no new version and new algorithms for dual mining ... Did someone hear something about the release of the new version?
|
|
|
|
twente-mining
Member
Offline
Activity: 176
Merit: 10
|
|
September 29, 2018, 04:58:09 PM |
|
I have got one rig with 2x 1070ti and 4x1070 ....
Claymore Software will not run.
It is working on other software, like the miner for Bitcoin Gold. ( ewbf )
Is there something i can do to make it work with those 2 different cards on one rig with claymore ?
|
▄▄▄▄▄▄▄▄▄▄▄▄
|
|
|
outbreak198x
Newbie
Offline
Activity: 10
Merit: 0
|
|
September 30, 2018, 09:08:56 AM |
|
Hello, i'm using claymore for a long time, and very happy with it, there is just a small thing i don't understand, on some of my miners. when i reboot the rig, windows logs on automatically, miner start automatically but... it don't create DAG and mine, afer connecting with RDP or another software DAG is created, and everything starts, without clicking on somehting... any idea why? because this depens on all i think 12 rigs in one location - all other rigs starting full, without this small bug. (don't think claymore is the problem)
|
|
|
|
|
carlo_0000
Legendary
Offline
Activity: 1281
Merit: 1003
|
|
October 01, 2018, 02:39:21 AM |
|
Can anyone help here? Its been working fine for months. I had to reset my PC and now Im getting this:
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. GPU 4 failed Setting DAG epoch #213 for GPU4 GPU 2 failed Setting DAG epoch #213 for GPU2 GPU 5 failed Setting DAG epoch #213 for GPU1 GPU 4, CUDA error 11 - cannot write buffer for DAG Setting DAG epoch #213 for GPU5 GPU 1 failed GPU 2, CUDA error 11 - cannot write buffer for DAG GPU 1, CUDA error 11 - cannot write buffer for DAG GPU 5, CUDA error 11 - cannot write buffer for DAG GPU3 DAG creation time - 5891 ms Setting DAG epoch #213 for GPU3 done GPU6 DAG creation time - 6316 ms Setting DAG epoch #213 for GPU6 done GPU 4 failed GPU 1 failed GPU 5 failed GPU 2 failed
i did same and getting similar kind of error "GPU failed" do you have last version? i notice that too on one of my ring, i notice i had an old version of the miner there
|
|
|
|
deadsix
|
|
October 01, 2018, 10:03:45 AM |
|
Can anyone help here? Its been working fine for months. I had to reset my PC and now Im getting this:
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions. GPU 4 failed Setting DAG epoch #213 for GPU4
i did same and getting similar kind of error "GPU failed" do you have last version? i notice that too on one of my ring, i notice i had an old version of the miner there Try increasing your Paging file size to the maximum possible.
|
|
|
|
raske
Member
Offline
Activity: 154
Merit: 14
|
|
October 01, 2018, 10:44:55 AM |
|
anyone here using MSI Armor 570 8GB not bios modded, with the lastest driver and compute mode on?
Yes...? can I please ask you for a little help what -cclock -mclock -powlim -cvddc -mvddc are you using to get the best stable config?
|
|
|
|
huntingthesnark
|
|
October 02, 2018, 11:01:16 AM |
|
Does anybody (Claymore?) know if the Sia fork will be dual-mineable? Or is an update needed/not worth the hassle?
|
|
|
|
raske
Member
Offline
Activity: 154
Merit: 14
|
|
October 02, 2018, 11:04:24 AM |
|
Does anybody (Claymore?) know if the Sia fork will be dual-mineable? Or is an update needed/not worth the hassle?
what Sia fork are you writing about?
|
|
|
|
|