|
v14.7:
- now the miner driver does not require switching Windows to Test Mode. If you want to turn Test Mode off, use "-driver uninstall" option (with admin rights) and reboot,
then start miner with admin rights to install new driver automatically when necessary (or use "-driver install" option directly).
If you have any problems with signed driver you can use "-driver install_test" option, it uses old approach: enables Test Mode (reboot is required) and installs unsigned driver.
- added "-showpower" option for stats about GPU power consumption, press "s" to see it. Both AMD and Nvidia cards are supported, except Linux gpu-pro drivers and Radeon7 cards.
- updated Remote Manager to show total power consumption.
- fixed issue with "-logsmaxsize" option when "-logfile" option is used to specify directory for log files.
- a few minor bug fixes and improvements.
|
|
|
|
Thanks, I had a good laugh here  Unfortunately, I don't have 13 p104 cards to test it. So 12 cards work fine and 13 fail, right? There is no difference for miner if you use 12 or 13 cards so it must be something else, try "-gser 2" option to see if it helps. hmm, yes. 12 cards are working. you definitely do not like this number) and 13 with with -gser 2 option, too. but very slow startup. with -gser 1 does not. and I found in syslog this [27382.925779] Out of memory: Kill process 10880 (ethdcrminer64) score 684 or sacrifice child
[27382.925822] Killed process 10880 (ethdcrminer64) total-vm:321404352kB, anon-rss:1346268kB, file-rss:1308172kB, shmem-rss:133120kB
[27382.948105] oom_reaper: reaped process 10880 (ethdcrminer64), now anon-rss:0kB, file-rss:1313400kB, shmem-rss:133120kB
sorry, forgot to take a look there earlier hope this help to trace the problem v11.9 also works without -gser. It seems drivers are unstable at this number of cards. If 11.9 works fine you can try to add "-eres 2" option, miner will use old-style DAG generation (since v12 it tries to reduce GPU memory used for DAG in most cases, non-zero "-eres" option value disables it). |
|
|
|
That's a lot of p104s....
Shhh! He do not like this number Thanks, I had a good laugh here Unfortunately, I don't have 13 p104 cards to test it. So 12 cards work fine and 13 fail, right? There is no difference for miner if you use 12 or 13 cards so it must be something else, try "-gser 2" option to see if it helps. |
|
|
|
ok thanks. Is working with command line. Is recognised by epools.txt ? It is set in my epools.txt on that pool but seems to be ignored. -allcoins is global option so you cannot set it per pool in epools.txt, it must be used only in command line or in config.txt. |
|
|
|
@Claymore
i'm trying to run v14.6 against my testpool ( ropsten network ) but doesn't work
...
15:16:38:510 a9ff3700 Probably you are trying to mine Ethereum fork. Please specify "-allcoins 1" or "-allpools 1" option. Check "Readme" file for details.
... If you want to mine some ETH fork, always specify "-allcoins 1", it will work in all versions. If you don't do it, it may work in some old versions and won't work in recent versions. |
|
|
|
Claymore,
Any update / progress on possible timing tweaks for RTX GPUs with GDDR6 by any chance? Would be nice to see what these puppies would be able to achieve...
It will take some time, sorry. You can try to ask other devs here, may be they can do it faster hello, -minspeed minimal speed for ETH, in MH/s. If miner cannot reach this speed for 5 minutes for any reason (you can change this timeout with "-minspeedtime" option), miner will be restarted (or "reboot.bat" will be executed if "-r 1" is set). Default value is 0 (feature disabled).
You can also specify negative values if you don't want to restart miner due to pool connection issues; for example, "-minspeed 50" will restart miner only if it cannot reach 50Mh/s at good pool connection.
Either there is a typo or I didn't understand. Didin't you mean "-minspeed -50" with a minus for negative value? thx Fixed. |
|
|
|
|
I have uploaded Linux build again, please use it, it must write "b737" in the log at the beginning which means latest build number.
|
|
|
|
on linux(hiveos),P106-100 droped hashrate from 24.7m(12.0) to 24.2m(14.6) with same oc。
nvidia driver version:418.56
Ubuntu 18.04 with latest driver. P104-100 on 13 card rig drop from 510 MH/s to 500 MH/s. I just confirmed this issue, it's related only to Linux build and Nvidia. I will upload an update within an hour. |
|
|
|
|
v14.6 - Supercharged Edition:
- now "-rxboost" option also supports old AMD cards (Hawaii, Tonga, Tahiti, Pitcairn), use "-rxboost 1" to improve hashrate up to 5% by applying some additional memory timings.
- now "-rxboost" option supports all AMD drivers.
- now "-strap" for AMD cards also supports AMD blockchain drivers.
- some changes to further reduce stale shares a bit.
- added "-minspeedtime" option.
- added statistics for shares accepting time (min/max/average), press "s" to see it.
- updated Remote Manager to show shares accepting time.
- Linux version build with some performance improvements.
- a few minor bug fixes and improvements.
NOTE: "-strap" and "-rxboost" options don't work in Linux build!
|
|
|
|
First, great work @Claymore!
But I face one problem ... if I mine with two instances and use for both the "-stripe" option, in my case, one instance for AMD and one instance for nVidia, the miner post the "driver in use" failure message by start the second instance. And then the miner will not use the additional speed increasing for the second instance at all.
Is that already known?
There is no way to fix it currently, two miner instances cannot use same driver at once. what '-driver install' do? *Driver installed successfully *reboot *GPU-Z show the same driver version  This option installs/uninstalls the miner driver, not AMD video driver. |
|
|
|
Back again with this stuttering problem, i was running to these days the BC driver but tried to update to 19.4.3 and same stuttering again. None of the drivers work after 18.?.? Rig works with 4 cards but after connecting fifth or sixth card, it starts to lag and cant run claymore and again BC driver works perfecly but can't use -strap option  Does anyone know fix for this? Ok I will add blockchain driver support in upcoming version. |
|
|
|
Claymore, would you be able to write some near download links that 14.5 is for windows only and for linux there is v12 ?  I get like like 10-15 requestes per day "when i will upload claymore-eth v14.5" and the answer is "there is no v14.5 for linux"  ... What do You think ? Done |
|
|
|
To enable compute mode on all cards: start miner as admin, press "y" key and reboot. BTW, miner shows the note about "y" key during startup, but almost all people skip it |
|
|
|
Simplemining just implemented Rxboost on linux  It's rather simple adjustment that I discovered a few days ago, so it's easy to clone it It works for old AMD cards too, so "-rxboost" option will also support old cards in next update. The real magic is to apply straps on latest Nvidia (Turing), Nvidia protected these cards from such tricks, I have a solution for it too, but need some time to implement it properly before including into miner. What rxboost actually doing? It increases refresh interval: https://en.wikipedia.org/wiki/Memory_refreshThis setting is not included in AMD straps so you cannot change it with straps. |
|
|
|
Simplemining just implemented Rxboost on linux It's rather simple adjustment that I discovered a few days ago, so it's easy to clone it It works for old AMD cards too, so "-rxboost" option will also support old cards in next update. The real magic is to apply straps on latest Nvidia (Turing), Nvidia protected these cards from such tricks, I have a solution for it too, but need some time to implement it properly before including into miner. |
|
|
|
I tested the rxboost and really works well. Some cards easily reach 32mhs however it hangs over a period of time.
Tried it on all 8 of my 12 card AMD rigs and each hangs on intermittent times.
Going to give some time for dev to get miner stable.
Great job so far.
Miner is stable, you should play with "-rxboost" option to find stable values for your cards. |
|
|
|
v14.5 Beta - Supercharged Edition:
- added "-rxboost" option for AMD Polaris cards, use "-rxboost 1" to improve hashrate by about 5% by applying some additional memory timings. You can use your own straps or use "-strap" option, you will get boost anyway.
See Readme for additional information.
- fixed issue with overclock reset for Nvidia cards.
Thanx! Does -rxboost still need driver install? Yes, this magic requires the driver. What about Turing NVIDIA? I did not have time for it yet, I can release new versions once a day, not often |
|
|
|
v14.5 Beta - Supercharged Edition:
- added "-rxboost" option for AMD Polaris cards, use "-rxboost 1" to improve hashrate by about 5% by applying some additional memory timings. You can use your own straps or use "-strap" option, you will get boost anyway.
See Readme for additional information.
- fixed issue with overclock reset for Nvidia cards.
Thanx! Does -rxboost still need driver install? Yes, this magic requires the driver. |
|
|
|
|
v14.5 Beta - Supercharged Edition:
- added "-rxboost" option for AMD Polaris cards, use "-rxboost 1" to improve hashrate by about 5% by applying some additional memory timings. You can use your own straps or use "-strap" option, you will get boost anyway.
See Readme for additional information.
- fixed issue with overclock reset for Nvidia cards.
|
|
|
|
|
I know I'm annoying, but I have another update...
|
|
|
|
|
Show Posts
