Claymore
Hi. I have this issue on our pool:
Looks like an issue with either our stratum server implementation or your client code. I've sent you a PM with additional details.
Ok I'll check it within 24 hours. |
|
|
|
Hi Gents,
Anyone using Claymore v11.6 on ethOS 1.3.1?
Since the latest update of the miner to v11.6 I am loosing connectivity for monitoring the miner on port 3333 after 15-21 hours of mining.
While Claymore keeps mining with no troubles only the monitoring is an issue. If I restart the mining process the monitoring is restored. I had no issue with the previous updates.
Tried to set the port manually but the problem still exist.
Anyone else experiencing this issue or has a solution?
Thanks in advance.
I just confirmed this issue and uploaded a fix: "Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.6 - LINUX - quickfix.tar.gz" To confirm that you use updated version, find "b573" in the beginning of the log file (original v11.6 writes "b571"). This issue is related to Linux version only. |
|
|
|
my claymore show this
"Failed to set new Power Control treshold for GPU #"
what is that?
what i have to do?
i just add my script with this ( -a 1 -powlim 50)
need info
thanks
Not all GPUs support +50, so try -powlim 20 or -powlim 30. |
|
|
|
No CN-heavy, no old GPUs, sorry, I just don't have time for it. something has changed for Aeon between 11.2 and 11.3
I did not check Aeon so I could break it when I added pow7. I will check and fix it when I have some time. |
|
|
|
|
v11.3:
- removed devfee, miner is completely free now.
- added "-pow7" option to support Monero hardfork, use "-pow7 1" value to enable it.
- reduced CPU usage for systems with a lot of GPUs.
|
|
|
|
Hi,
please consider adding some devfee pools other than nicehash, because nicehash is blocking some countries and also there are some countries who are blocking this pool only( I don't know why ).
I'm not sure about the latest release, however on version 1.0 which the awesome miner is still using, the miner works fine on MPH,dutchpool,zergpool,.... But when it comes to devfee it fails trying to connect to nicehash pools and there's nothing I can do because it's being blocked either by nicehash or my isp so it continues with mining and retries every 20 sec with no luck.
Any other devfee pool is fine except for nicehash.
Thanks for your efforts and good luck.
I know about this issue, however, I cannot add other pools because it's not easy for me, there are many NeoScrypt-based coins and pools, they are rather small and therefore I cannot select what coin to mine in long-term. Nicehash selects best coin and I don't have to create any local wallets for these coins. You can use "-nofee" option if nicehash does not work for you. |
|
|
|
Hi everyone, i was use "y" in runtime miner, restart PC, and after reboot something wrong.
What need press for remove "y" flag in windows 10? In manual not have it how to.(
Open regedit, open key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}" and remove "KMD_EnableInternalLargePage" parameter in every subkey "0000", "0001" etc. Then reboot. If it's too difficult for you, just use amdcleanuputility and reinstall drivers. In next update I will improve this feature so you can disable compute mode as well, though I'd like to know more details about cases when "y" key causes any problems. |
|
|
|
|
4.0
- removed devfee, miner is completely free now.
- added "-pow7" option to support Monero hardfork, use "-pow7 1" value to enable it.
|
|
|
|
Anyone tried rx550? Hash rates?
Bad as expected: about 200KH/s for stock RX550. Neoscrypt uses both memory and core, so this card is too weak for it. |
|
|
|
|
v1.2:
- improved stratum routines to support more pools.
- added RX550 card support.
|
|
|
|
When new versions with v7 algo support???
In a few days. |
|
|
|
|
v1.1:
- fixed issue with rejected shares.
- reduced CPU usage for systems with a lot of GPUs.
|
|
|
|
|
v11.6:
- improved hashrate for weak Nvidia cards by about 1%.
- zero devfee for 3GB cards in Windows 10, same as for all 2GB cards.
- applied some tricks to increase available memory for 3GB cards in Windows 10 so you can mine ETH a bit longer.
- now you can press "y" key to turn on "Compute Mode" in AMD drivers for all cards (Windows only).
- Linux version: removed openssl library dependency.
- improved "-logfile" option, now you can use it to specify a folder for log files, use slash at the end to do it, for example, "-logfile logs\".
- added "-epoolsfile" and "-dpoolsfile" options.
- remote management: now "miner_getstat2" command also returns PCI bus index for every GPU.
- a few minor bug fixes and improvements.
|
|
|
|
Yes I find shares too but as soon as it switches on FTC, it rejects.
Try that, it's the only FTC port and for GUn (3615) idem.
NeoScryptMiner -pool stratum+tcp://neoscrypt.mining-dutch.nl:3347 -wal lezartnono19.R9280x -psw x
Ok now I see. It must be something related to stratum, I will check it soon. |
|
|
|
NeoScryptMiner -pool stratum+tcp://neoscrypt.mining-dutch.nl:9991 -wal lezartnono19.R9280x -psw x
This command line works fine for me, just found 16 shares, zero rejected. The reason can be in overclock, my miner requires more power than nsgminer because it's faster. |
|
|
|
|
It seems 3GB cards won't be able to mine ETH/ETC in Windows10 soon because this OS reserves about 20% of GPU memory size and there is no way to fix it (at least easily).
In next update I will set zero devfee for these cards (same as I did for 2GB) so you can mine ETH forks.
If you still want to mine ETH/ETC on 3GB cards you should use Windows7 or Linux.
|
|
|
|
Hi, what about the rx550?
Ok I will add it in next update, no ETA though. Good evening, I mine in multiport on mining dutch and the FTC and GUN is rejected each time, the other currencies are mined. Why ? With nsgminer, I do not have this problem.
Merci d'avance.
I'd like to see full command lines for both my miner and nsgminer so I can check it. |
|
|
|
Im facing a curious issue Claymore. I am running 13 x RX 460 cards on an Asus B250 MiningExpert under Windows 10 (1709).
If I try to run the Miner with all 13 GPU's it just BSOD's right after it lists out all GPU's and starts showing ASM mode for them.
If however, I run two instances of the miner and split the GPU's into groups of 6 and 7 using -di, the two instances run perfectly fine.
I thought you had already optimized the miner for 9+ GPU's? Any Idea why this could be happening?
While two instances of the miner work fine for me, its sub optimal as a solution.
I have a rig based on H110 Pro BTC+ motherboard with 12 GPUs, it works fine (v11.5, latest drivers, Windows 10). Miner itself cannot cause BSOD, it must be something related to PSU (try "-gser 2"), hardware or drivers. If you think that the reason is the miner, try some other miners to confirm it. |
|
|
|
Has anyone experienced hashrate drop in what seems to be a quite consistent matter?
I'm not talking about my rock solid RX570 rigs, they've been absolute beasts for a year now. But I'm struggling with the Vega rig.
All GPUs will hash at ~41MH/s until one decides to drop to 26 for a minute. Then goes back up to 41. This happens regularly.
Surely if it were temp throttling (which seems unlikely as I have the fans running at pretty much 100%) the hashrate reduction would be more gradual... and not bam!... down to 26?
Any clues? I'm on v11.4, latest Adrenalin, Vega56@64, safe softPP table with specific clocks and voltages set in Claymore miner.
Got the same issue but with my rx580 rig, all 7 cards running stable at 31 mh/s. From time to time gpu0 suddenly crashes to a rate around 5-10 mh/s and after a few minutes hits back to 31. There are no error logs showing up, also no incorrect shares and temps are fine. Card has also the same setup as other cards (no oc), kinda strange since it just appeared lately, running currently v 11.5 same issue here are you using stock rom with no oc? In addition to the above, Mr Claymore, your miner reboots my rig every hour. Almost without fail. There's no error in the log, no watchdog issue with GPUs OpenCL issues, nothing. I'm baffled. 1. Unstable speed - I see this issue sometimes on different cards, but I have no idea about the reason - miner executes jobs on GPUs in the same way all the time, but sometimes GPU becomes slower for some time. I noticed that often different "-ethi" value helps, try "-ethi 4" or "-ethi 12" and see if it helps. I think that it must be something related to AMD drivers but I cannot confirm it yet. 2. I have a few rigs on v11.5 and they are working for days until I restart miner to perform some new tests, but I always use non-overclocked cards and default bioses, I have to do it to exclude everything except miner in case of any problems. When you use miner on overclocked/unstable rig you cannot be sure that the reason of the problems is the miner, but of course you will blame it  Try to reduce "-ethi" value, if it does not help you can use the version that works fine for you. |
|
|
|
Hi claymore any chance you will update this miner with the new monero algo?
Your miner works best cpu wise, while mining with gpu's
Yes I will update both CPU and GPU miners. |
|
|
|
|
Show Posts
