Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[Bojcha]

I see 14.6 is on smos now.

anyone know commands to enable straps?

tried -strap 1 in config nothing.
tried strap 1 in advanced overclock, nothing.

NOTE: "-strap" and "-rxboost" options don't work in Linux build!

[se2ingu]

semi true.

rxboost works in smos

[ciprianveg]

1660 ti is not working on linux with 14.6 ( hiveos).. strange as pheonix miner works.

[Er0l]

semi true.

rxboost works in smos

„Rxboost“ works on every linux distro not just smos,

But the command line option from claymore doesnt work in linux.

[br2459]

help me my gpu rx580 max M/h 14 please

https://i.hizliresim.com/QPEbYy.jpg

Same trouble. 6*rx484, 13.6 each. On old BC drivers without strap 29.6 each

You have to reboot into "Test Mode" after running the start.bat file with administrative permissions. Also need to make sure you set the cards in compute mode. Add -y 1 to your config and it will do it automatically and then reboot. If not you can just hit Y and then reboot. It's key to reboot in between setting compute mode and running as administrator.

[storman2]

Where I can find straps from claymore 14.5 ? I want flash it to rx580 4gb and use in linux

[DrX]

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!

So now we can use -straps and -rxboost on win 7, if needed?

[ustcstone]

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

[Hostels]

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.

[Claymore]

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.

[Claymore]

I have uploaded Linux build again, please use it, it must write "b737" in the log at the beginning which means latest build number.

[Hostels]

I have uploaded Linux build again, please use it, it must write "b737" in the log at the beginning which means latest build number.

All fine! Hashrate up from 510 MH/s(12.0) to 520 MH/s(14.6)!

[dragonmike]

I have uploaded Linux build again, please use it, it must write "b737" in the log at the beginning which means latest build number.

Claymore, how close are you to getting a mem timing boost option for nVidia RTX cards with GDDR6?
I believe I read you were looking at it a while ago.

[WARMANGALAXY]

Hello, confirm on 1660Ti GDDR6 not working Claymore 14.6 cuda old version

[davith75]

Hello Everybody,

Since the 14,3 + regarding the VegaStrap.

I'm having error strapping the 56 especially (which are flashed to 64).
While it do works perfectly on the Vega64 natively 64.

The behavior is that on a 56 flashed to 64, the straps said it's applied, but the DAG is never completed and it stays at 0.0mh/s

I'm guessing is that since the miner detect the GPU as 56 compute unit, it apply the Vega 56 timing on it (maybe ?)
So I'm trying to force the 64 Strapping on the 56 with Samsung memory.

But which is the nomenclature of it ?
From the Readme exemple which is POL8S1

I'm trying :

-strap VEGS1 -> wrong strap format
-strap VEG8S1 -> failed, error 1015
-strap VEGAS1 -> failed, error 1015
-strap V64S1 -> wrong strap format

EDIT :
It works when I export the V64 Strap 1 timer, and that I inject them manually on the Vega56 once the miner is starter without strapping.
I can get 48 49 on the Vega56 this way.

[ciprianveg]

Hello, confirm on 1660Ti GDDR6 not working Claymore 14.6 cuda old version

also not working with nvidia driver version:418.56 with 1660ti

[haliavshik]

i have a mixed rig with rx570 and gtx1070 in it strap 1 gives 1070 2.5mh; rxboost 1 gives  rxs 0.5 mh if i run them in 1 copy of claymore rxs dont get this 0.5mh from rxboost if i run 2 copies of claymore 1 copy cant use straps due to driver is already in use.

[nlhk]

I have uploaded Linux build again, please use it, it must write "b737" in the log at the beginning which means latest build number.

Linux CentOS 7.6 + GTX 1060 (Driver : 410.48):
v12.0              :      19.9 Mh/s
v14.6 original  :      19.2 Mh/s
v14.6 updated :      20.2 Mh/s

Thanks.

[MostWanted]

Hi!

Problem with Miner 14.X versions. I use one rig for several clients. For example:
1) 8 x 1060 in one rig;
2) 3 x 1060 - one client;
3) 5 x 1060 - second client.

With 12.0 Miner everything is simple. One instance of Miner (-di 012) and the second instance of Miner (-di 34567). All works fine.

Now I want to use parameters STRAP and SINTENSITY in both instances. But one instance executes fine, and another with error:
Driver is in use, try to start miner with "-driver uninstall" parameter.

Question: how to use one driver name in one instance and another driver name in other instance?

I have 2, 3, 4 instances of Miner and parameters STRAP and SINTENSITY need to in all instances.

[ethashpool]

Hi Claymore Team,

Are you able to add our config setting to your sample usage list on page 1 of this post?

EthDcrMiner64.exe -epool stratum+tcp://eth.ethashpool.com:3939 -ewal WALLET_ADDRESS -eworker RIG_ID -epsw x -esm 0 -allpools 1 -mode 1

Let me know if there are other information I can provide.

Thanks!