Claymore - thanks for adding the new API to enable and disable individual GPU's. I've added support for that in Awesome Miner. Would it also be possible to extend the API to include accepted / rejected shares per GPU? Thanks! It will require some changes in Stratum implementation (in all supported versions) because I will have to use several IDs in share submit requests to identify GPU in server response. I would not like to change that code because it can break compatibility with some pools, I will do it but I need to do a lot of tests to check compatibility with all pools. No ETA for now though. |
|
|
|
Claymore, I noticed the front page of the thread with the new release links no longer mentions the issues with Nvidia 9xx and new drivers on Windows 10. Has that been resolved and Maxwell cards can mine at full hashrate with latest drivers in windows 10?
I removed it because latest drivers solved issues for Pascal cards. Well, may be I should return these notes back, though need to find them somewhere to do it... How long does the devfee usually take?
Claymore claim that he take 1%, but in fact he took more. You can watch the status of mining, every devfee mining, he is always get the share. He is cheating on 1%. I think he takes at least 3%. In fact you don't understand mining details. Some people think like you and tried to check fee rate in my miners technically, for example: https://bitcointalk.org/index.php?topic=1681108.0About number of shares: I explained it several times, then added to FAQ here: https://bitcointalk.org/index.php?topic=1670733.0Here it is again: ..... Q: Why do I see more shares for devfee than in my mining for the same time? A: Most pools support variable diff, they change "target share" after some time after connection. For example, you have very powerful rig, after connection you will send shares very often. It takes some CPU time to check your shares so after some time pool will send higher share target and miner will send less shares (but they will have more value). When pool updates share target you will see "Pool sets new share target" line in the miner. This way pool can adjust the number of shares that miner sends and balance its load. So check the log or console text to see current target for main mining thread and for devfee thread. For example: DevFee: Pool sets new share target: 0x0083126e (diff: 500H) - this is for devfee mining connection Pool sets new share target: 0x0024fa4f (diff: 1772H) - this is for main mining connection As you can see, target share for main mining is higher in about 3.5 times, so for main mining miner sends in 3 times less shares (but they have 3x more value) than for devfee mining. ..... For ETH most popular pools don't use vardiff, but if you see many shares in devfee it means that you use such pool. So if you see that devfee mining gets more shares - check in the log what share target is used for devfee, it will be much lower than for main mining, so these shares are much cheaper. Of course you can forget about all these complex technical details and continue think that I fool entire community and take 3% or 5% or 7%... I write miners for a long time and a lot of people use them, such thing would be discovered quickly because there are ways to check real devfee mining rate. |
|
|
|
Claymore, have you got any idea of what might be impacting memory controller load? One of my cards has load going up and down wildly (all the other 13 are fine at 100%). I've tried raising/lowering voltage, memory voltage, tdp, everything. I've even tried tweaking -dcri but it actually did not change anything. Ironically it's my card with the highest asic (90.5). I'm out of ideas...
Is it Polaris card? I still see strange memory load fluctuations in dual mode, mostly on Polaris cards, it is something related to hardware, but currently I have no ideas what exactly. |
|
|
|
Sooooo was Claymore hacked last night (UK time)? Connection dropped on mine and my housemate's rigs for about 15 mins, we were getting the failed to connect, retrying after 20s error. Since then, for the past 8 hours, my Ether balance has not increased.
CLAYMORE GOT HACKED CONFIRMED! Nice first post! /s Claymore is hacked by tons of newbies. Attacked by them in PM too. Maybe I need to create another FAQ for newbies, but most of them will not read it. Just some quick answers to recent questions: 1. If you think that the miner will mine even if you turn off the router, wait a couple of minutes more, it will stop. 2. Place all command line arguments in .BAT file in a single line. Arguments from the second line will be ignored. 3. Use latest version if you have problems with DCR or SIA. 4. I don't have any private versions with +50% speed. 5. I'm a software developer, so I think I cannot help you to build your mining rig properly or provide you with the list of necessary parts, please ask this question here on forum or search here, there are many threads related to hardware. 6. Please read Readme.txt or original post of this thread for command line samples, options description and FAQ. 7. I don't have miners for Tesla, IBM CPUs, Phi or for very old GPUs. 8. Mining on laptops is a bad idea. 9. You will not see full hashrate on pool immediately, you have to wait for 24 hours at least. 10. If miner cannot generate DAG file, check environment variables (see Readme), check if your GPU has 3GB memory at least, and check if you have enough virtual memory (pagefile). If all this does not help, try to install more physical RAM. And sometimes I see really interesting messages. Recently I got PM from a newbie account, he found the issue with Pascal nonces from the log file. I was impressed. |
|
|
|
Claymore,
the problem with ETHMan 3.1 + Dualminer 9.5
If some rig go down, and then after some time goes up, it dosent restore in ETHMan, on screenshot you see that miner restarted and work, i launched web console and it works already 2 minutes, but ETHMan still show "lost ****". Even after 10 minutes ETHMan dosent see rig. So as it was with ETHMan 3.0, I need restart it to see all rigs stats again.
If you included cryptography and https, then maybe here some trouble with ssl? need to update certificate if connection was lost?
Can confirm this, same problem here.
The last update of EthMan improved the 100% lock after a warning, but a rig which was offline and comes back up is not (always?) shown as alive until EthMan is restarted.
Also the batch action is still not retriggered in case of a persisting failure.
I spent half a day in attempts to reproduce it, but it works fine for me, weird. If you can 100% reproduce this issue I can prepare debug version with logging and send it to you so I can get more info. PM me if you want to participate. Retriggering: if a rig was lost, BAT file will be executed. If rig is back again and then again will be lost, BAT will be executed again. What's wrong exactly? |
|
|
|
According to what I observed, it may be legitimate misreporting of Eth hashrate whilst dual-mining.
Probably you mean that different GPU rounds take different time in your tests, am I correct? There are two reasons for it at least: 1. You started two separate miners, both try to load GPU completely so different GPU rounds will have different time. My miner uses different approach. You can press "s" key to see hashrate for latest GPU round, press it many times and see if there are fluctuations, for Polaris card you should notice them but they are related to item #2 below. 2. At some circumstances GPU can be slower for a second or so, then work a few seconds at 100%, and so on. Especially Polaris cards. It was a problem in v9.0 but I've almost fixed it in recent versions, these fluctuations are low and rare now even on Polaris. v8 is free of this issue, but has lower speed for second coin. Anyway, may be I should also show additional counter that measures hashrate for a minute when "s" is pressed, I will try to add it in next update. |
|
|
|
Can't seem to find api.txt - anyone knows if documentation for Claymore API can be found anywhere?
Download v9.5 for Windows, unpack it and check "Remote manager" folder. |
|
|
|
Hi all, I have an issue in regards to mining SIA. Here is my batch file: EthDcrMiner64.exe -epool us2.ethermine.org:14444 -ewal address.worker -epsw x -dpool stratum+tcp://sia-us-east1.nanopool.org:7777 -dwal address.worker -dcoin sc I have read the readme file and have also tried the different sia hosts/pools such as siamining, but they all still produce the same error. Any help or suggestions are appreciated! Miner thinks that you mine DCR, not SIA. PM me the log file. |
|
|
|
@Claymore
Whats the criteria for the GPU Identification? How does claymore determines who is GPU 0 1 2 3 etc?
I need to apply -cvddc to two gpus but not the other 5
Check "KNOWN ISSUES" section in Readme. Voltage/clocks settings are related to ADL, i.e. to the list of fan/temperatures. Disable GPUs one by one (by pressing 0..9 keys) and see temperatures after a while, it will show what GPU you disabled. |
|
|
|
@claymore: Sir, maybe I found a bug. If I start Ethman and there is any temperature or fan speed warning, then Ethman doesn't show any info about that rig, only rig name and IP:port. (If the warning "happens" later, there is no problem.)
Also @claymore: First thanks for your work, EthMan ist going exactly the direction we need. BUT: The above mentioned behaviour is even worse: If a rig is in a warning state (tested only with mining speed) - it will NOT detect when the rig goes completely offline and so not trigger the notificatian and external reset. This makes it quite useless in a (not so unusual) number of cases. Another (maybe related point) is the fact that it does not retrigger the events. Say if the first restart happens and the rig is still offline (i.e. Windows booting into "repair mode") it does not perform a second reset and the rig will stay offline until manual intervention. Could you please have a look into it? Thank you! Confirmed, fixed. Since I don't have separate archive for EthMan, I've re-uploaded v9.5 with updated EthMan, please re-download it. In next version I will process all warnings separately and will add own options in GUI for every event, so for example you can setup warning for fan speed to see it in the list of miners, but disable starting .BAT or/and email for this event. |
|
|
|
hello, Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.5 bug, not connet servers ethermine pool
Bug is somewhere else  Please open ethermine.org in browser and read "How to Connect" help section, there is no "-esm 2" option there... Anyone having issues when the miner reboots due to a GPU having an open cl issue?
From time to time this happens and when the miner is restarted automatically its stuck at doing dags or something and never gets mining again..
I have noticed when I kill the actual window in windows and click the bat file again it works.
@Claymore is their a way for it to completely kill the window and wait a few secs before launching again. I believe on some hangs this would help out.
1. Often when OpenCL fails, you have to reboot the system, not just restart miner. Sometimes even soft reboot won't work and you have to press Reset button. It is because the fail is at drivers level, Windows does not like such things and drivers too. 2. Miner cannot kill itself, then wait a few seconds and start itself again. Because it needs to be running to start anything. But you can create some .BAT file for it, for example, you can wait and start miner again in reboot.bat if you use "-r 1" option. |
|
|
|
How do i get the settings from ethman from 9.4 to 9.5? So i don't have to type all in again.
Just copy "Options.ini" file. |
|
|
|
I tried to use v9.5 - first time it recognized it as a virus, so I am unable to even download it  Win 10, tried both from Mega and Google. I think that's not the point. I disabled AV, downloaded your ZIP, unzipped, tried to run. But after restart Windows again removed some malicous files and since that time I even cannot run v9.5. It simply closes itself right after double click on my .bat. It works fine on my Windows 10 system. But I disabled autoupdates, defender etc a long time ago. |
|
|
|
I tried to use v9.5 - first time it recognized it as a virus, so I am unable to even download it Win 10, tried both from Mega and Google. It seems I will have to use RAR or 7ZIP archive with some password soon... Or may be these paranoid AVs just check filename. |
|
|
|
- EthMan: added ability to enable/disable GPUs remotely (see API.txt for tech details).
Claymore, I tried to send commands to EthDcrMiner64.exe and got a reply from EthDcrMiner64 telling, "Remote management: read-only mode, command control_gpu ignored", Any idea as to why I can't use the remote management command? I wonder how can i get full access. Just read "-mport" option description in Readme. |
|
|
|
|
v9.5:
- fixed issue with PASC, miner could check some nonces twice. Effective hashrate must be a bit higher now.
- improved SIA support for Nicehash, added "mining.extranonce.subscribe" and "client.reconnect" commands support. Effective hashrate must be a bit higher now.
- a few minor bug fixes and improvements.
- EthMan: added ability to enable/disable GPUs remotely (see API.txt for tech details).
- EthMan: added notification for too high fan speed.
- EthMan: several minor bug fixes and improvements.
|
|
|
|
I use this miner to mine Musicoin on an R9 270x (2gb) which works great as it manages to still work in the 2GB available (while ethereum no longer does).
Every time the dev fee kicks in it tries to mine ethereum and fails, at which point the program restarts itself.
Is there a way to configure it so the devfee is also mined using musicoin as I would like to be able to donate the time to the devfee and for claymore to get it (which as it currently stands he isn't).
Add "-allcoins exp -allpools 1". |
|
|
|
I'm getting a lot of issues with the Claymore miner within NiceHash in the past week, anyone else getting this?
This happens on 3 separate rigs running different cards, Furys, 280 and 390.
What often happens is periods of rejected shares even though the cards are rock solid stable and periods of disconnects/timeouts, I've tried switching regions but the same issue. If I switch miners I get no issues, but of course Claymore is the best performing.
Getting the same. My idea is there is a new coin out there that is not properly supported by CM miner, hence the rejects. Hush? Zencash? Please PM me the log file so I can check the reason. |
|
|
|
Linux version not working because of using old ssl library
libssl.so.1.0.0
Since you use Linux, it should not be a problem for you to get required version of OpenSSL. But I will check if I can link it statically in next update. Why my RIG with AMD R280 Saphire suddenly shutdown when start mining with v12.5
windows 7 64 bit RAM 4Gb
need advice please
Usually it means that your PSU is weak. |
|
|
|
|
Advice: keep it as is, don't specify it, it is good by default. If you want more technical details about this parameter: it defines how many nonces will be checked in a single GPU round.
Then probably I would need to explain what is nonces, what is GPU round, what is optimal GPU round time for ETH for most cases, etc... It's a lot of text if describe it properly. After all you will understand that default value is good.
So just use default value.
PS. If you are curious, you can find this in readme:
...
You can also specify negative values, for example, "-ethi -8192", it exactly means "global work size" parameter which is used in official miner.
...
and investigate what is "global work size" parameter of official ETH miner, it is the same.
|
|
|
|
|
Show Posts
