Is 11.1 can handle fan/temp/clocks info/control with new adrenalin 17.12.x drivers?
No. Fix from AMD is required, we have to wait it. Or I will have to do their job again and find some workaround. Is this the same as the one you posted earlier (updated) or is 11.1 different?
It's different, a bit better.
|
|
|
There's an issue with nicehash causing segmentation fault under Linux. I've had to stop using your miner because of it.
Ok I'll check it.
|
|
|
v11.1
- fixed issue with stale shares, now effective hashrate must be higher. - a few minor improvements.
PS. Linux version will be available in a few days.
|
|
|
@claymore about 1 month ago you said that you updated your miner, and lowered the devfee, but we have no news about it
Yeah +1 for the question from me. Any news? Yes I will do it but I did not promise any timeframes, right now I'm busy with XMR miner update (bug fixes mostly), I will release it very soon. Then I will update dual miner because some things must be updated. After that I will update this miner and this update will include less devfee as promised.
|
|
|
Yeah here too nanopool reports 8500hs and claymore 9400hs
Hmmm. +1 Claymore, what can you say about this? Check GPU load in gpu-z (must be 100% all the time). I will do some tests in 1-2 days to confirm that the miner produces correct number of shares, though I already did it for v11. UPD: It seems I found the reason, when pool sends new job, v11.0 drops old job too late (loses 1-2 sec). I have fixed this bug but it will take 1-2 days to test it properly and release an update. However, you can test a fix right now if you want and tell me if it helps: https://mega.nz/#!TlYQAJSZ!291Swk4GbJLC5JYmax_fc-tLWjfwKsFTnOUSVGqsDlA
|
|
|
For most cases, miner applies the best "-h" and "-dmem" values automatically. But you can find the best value manually: 1. Use "-dmem 0" and try several "-h" values to find the best hashrate. For example, you found that "-dmem 0 -h 512" is the best. It will require about 1GB GPU RAM. 2. Now set "-dmem 1" and divide "-h" value by two: "-dmem 1 -h 256". It will require about 1GB GPU RAM too. 3. Also try "-dmem 1 -h 512" if GPU has enough RAM, it will require about 2GB GPU RAM. Note that using almost all available GPU memory usually causes slow working because drivers allocate memory incorrectly, reduce "-h" in this case. In my tests "-dmem 1" must be used for all GPUs for best speed, except Vega which is not optimized properly yet.
|
|
|
For tahiti and Pitcairn it seems still 9.7 is fastest Very good speedup on Polaris!, 20-30h/s per card or even more Hmm, in my tests v11 is a bit faster for both Tahiti and Pitcairn, or at least the same. May be you use not optimal settings. still no support for old HD 7700/7800 cards (don't say anything about 9.7 version please, which doesn't have magical "-allcoins" option) Sorry, I don't not support very old cards anymore.
|
|
|
v11.0:
- improved speed by 1-3%, depends on GPU model. - fixed issue with invalid shares. - added CryptoNight-Lite support, use "-lite 1" option to mine AEON. - improved stability. - adjusted default "-h" values for various GPUs for better performance, check your settings. - fixed critical issues in remote management feature (attacker could crash miner even in read-only mode). - fixed issue with possible GPU crash during miner shutdown. - updated pools for devfee. - several minor improvements and fixes.
|
|
|
v3.9
- fixed issue with devfee failover. - fixed critical issues in remote management feature (attacker could crash miner even in read-only mode). - added "-mpsw" parameter.
ClaymoreIs it possible to accelerate Monero CPU-mining via VIA Padlock? The VIA PadLock Security Engine is implemented in most recent VIA x86 processors. It contains at least a hardware random number generator. The C5P core gained AES acceleration on top of the random number generator, using a different instruction set than Intel AES-NI. The C5J "Esther" core has SHA-1 and SHA-256 acceleration and a Montgomery multiplier as well. A Montgomery modular multiplier can be used to speed up asymmetric encryption such as RSA signing and decryption. Finally the C5P "Esther" core also contains NX bit security which VIA considers a component of the PadLock suite. The difference with the other features is that it doesn't provide additional functionality to the user. Currently I don't have enough time for it, sorry, I'm too busy with other miners.
|
|
|
Miner uses the list of devfee pools if you specified "-allpools 1" option, it selects pool randomly, so it will find a good pool after a few attempts anyway, you don't lose anything because miner mines for you during these attempts. In next update (2-3 days) I will update this list of pools and exclude nicehash.
Today is the day? I also added CryptoNight-Lite support (AEON), it took some additional time. I will release new version within 48 hours.
|
|
|
Note about latest drivers version: I confirmed that AMD broke fan management again. I have contacted them and hope they will fix it soon. Right now don't use 17.12.1 drivers if you want to manage GPU fan/temperature.
|
|
|
Miner uses the list of devfee pools if you specified "-allpools 1" option, it selects pool randomly, so it will find a good pool after a few attempts anyway, you don't lose anything because miner mines for you during these attempts. In next update (2-3 days) I will update this list of pools and exclude nicehash.
|
|
|
In 2-4 days I will release new version with a bit better hashrate, improved stability, also I have fixed the issue with invalid shares on some cards.
|
|
|
It seems this pool has wonderful level of support - all my tickets hang for two months with no response. Other pools answer my questions much, much faster.
Sorry for the inconvenience, what's the number of your request? The most recent is "Ticket N55965". Unfortunately, due to high volume of requests it may take our support up to a week to reply. I forward your ticket number directly to our technical team. Please kindly wait for them to answer Don't worry, this ticket was created on September 26 and still no response, so I don't care anymore...
|
|
|
It seems this pool has wonderful level of support - all my tickets hang for two months with no response. Other pools answer my questions much, much faster.
Sorry for the inconvenience, what's the number of your request? The most recent is "Ticket N55965".
|
|
|
It seems this pool has wonderful level of support - all my tickets hang for two months with no response. Other pools answer my questions much, much faster.
|
|
|
v3.9
- fixed issue with devfee failover. - fixed critical issues in remote management feature (attacker could crash miner even in read-only mode). - added "-mpsw" parameter.
|
|
|
@Claymore, I am trying to solo mine ETH fork using Parity node . It works well with GetWork protocol, but since 1.6 Parity offers Stratum protocol support. I was unable to configure your miner to work using Parity stratum. All ESM modes (0,1,2) did not authenticate properly and returned protocol errors. Does this miner support Parity stratum solo mining or not? If it does, how to configure it?
Ok I will check it and will probably add in next update.
|
|
|
Claymore, I have a minor bug report (or maybe an improvement suggestion) for the Web interface of EthMan. The "More Details" button currently links to "http://<IP>:PORT/detail". Can you please change it to just "/detail", omitting the <IP>:PORT ? This will allow to maintain proper URL in case if special routing / DNS name is used to access the web page. Thanks!
Ok, it will be improved in next update.
|
|
|
|