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

[nhirsch]

Kinda new to ETH mining. I have 3 miners on Nvidia and just built one using AMD MSI RX 580 8g Gaming X cards. All are running Claymore in ETH only mode, Nvidias on 9.8 and AMD on 10.0. I'm in process of optimizing the hashrates on the RX 580s. I've modded the bios using the PolarisBiosMod Editor (new one that automatically copies the values from 1750 to others) and I've updated to latest AMD blockchain drivers. Increased hashrate from 21.3 to 26.7 but I see others doing upwards of 30. I've downloaded latest beta of MSI Afterburner and can't seem to improve the hashrate like I could on the Nvidias. I see people doing some tweeking with WattMan but I don't know if it works on RX 580s and if so, where to find it?

[Yohow]

Please, all that have a RX 480 8GB (Shappire Nitro + 8GB) can post the best values for "-dcri"? For now I set "-dcri 23" cause I think that when I increase it to 24, 25 or more Claymore seems unstable and sometimes my hashrate fluctuates. Many thanks in advance

[aarons6]

i read the first page and i searched and nothing came up.
using dpools and epools text config.. how do i set the coin to lbry?
i tried , DCOIN: lbc but its still showing dcr.

[VladimirT]

i read the first page and i searched and nothing came up.
using dpools and epools text config.. how do i set the coin to lbry?
i tried , DCOIN: lbc but its still showing dcr.

Show us your bat and config files.

[patofet]

i read the first page and i searched and nothing came up.
using dpools and epools text config.. how do i set the coin to lbry?
i tried , DCOIN: lbc but its still showing dcr.

Here you have an example o fmining lbry and eth:

EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorkerName -epsw x -dpool stratum+tcp://lbry.suprnova.cc:6256 -dwal Redhex.my -dpsw x -dcoin lbc


You can read the first pages and the FAQ for more information

[osnwt]

@Claymore: BUG REPORT.

TL;DR: please run reboot.bat by -minspeed if r>=1 (not only with r=1).


Win10, miner 10.0, latest blockchain drivers (23 Aug). It does not reboot if -minspeed not reached and -r X set (X>1), just restarts miner.
This, formally speaking, is not a bug (since README says it reboots if r=1). But by logic, if one sets r>1 (that is, wants reboot on either error or by timer), seems reasonable to reboot also by -minspeed.

The real use case: unstable rig instance after miner restart (first boot ok but any miner restart may fail).
1) pool drops connection every 24h (some pools)
2) miner reconnects, but system hangs and reboots
3) AMD driver resets clocks to default
4) miner starts with default clocks and has low hashrate (AMD driver changes it only after miner restarted)
5) miner restarts by -minspeed, rates set to ok, but unstable system hangs and reboots again...
6) loop to 3 (default clocks again)

If miner reboots on -minspeed instead of restart, all would be ok (since new clocks are already set, and reboot is by command, not by driver error).

Using AB/Trixx to preset clocks will resolve the issue, but I prefer to set rates in the miner.


ANOTHER ISSUE: does anybody have reboots on Linux with NVIDIA on OpenCL error? I set -r1 but even if some card has 0 H/s, and/or -minspeed is set, miner does not react and does not reboot neither restart. Anybody to confirm?

[jang430]

Hi.  Need some clarifications.  I heard when using RX cards, to achieve high hashrate, Bios mod is essential.  I already did, and am hashing about 30 MH/s on my Gigabyte Aorus RX 580s Hynix 8 GB.  My problem is, the bios mod I flashed resulted to very high power consumption.  A few questions below:

1. Is it natural go get a higher power consumption after bios mod increasing hashrate?
2. Do you guys undervolt directly onto bios mod?  Or is it only the hashrate everyone is after?
3. Can you undervolt as effectively in Claymore as in bios mod?
4. What are the things to tackle to undervolt in Claymore?  -mvddc, -cvddc?  Does -cclock affect power consumption?

Thanks

[osnwt]

Higher clocks => higher power, yes.

To undervolt there are few ways:
- change powerplay table voltages (in BIOS or at runtime)
- change DPM states (use lower states = lover volts with high clocks)
- change VDDC voltage offsets (either fix BIOS tables, or patch VDDC offsets into BIOS tables, or use I2C at runtime)

The issue is that different drivers and platforms behave differently. Say, some ignore BIOS voltage tables, some use driver defaults, etc, etc. So there is no single "right" way to downvolt any card.

On Windows the best way could be to use WattTool to change VDDC offset, it uses i2c to update hardware voltage offset. But every voltage regulator requires own commands. WattTool was great and worked with many cards but its author disappeared. Still, even with latest drivers WattTool does not work with powerplay tables but can change VDDC offset. I2C method is better than -cvddc since it allows to set VDDC lesser than MVDDC. Changing VDDC sets it to max(MVDDC, VDDC).

Linux used by big farms, and no one wants to share the technology with public for free. They usually want 1-5-10 BTC for that (and actually different cards, different patches).

On Windows I use any tool (AB, Trixx, -mclock) to set memory clocks, and use WattTool to downvolt via VDDC offset. It gives best results but requires settings VDDC offset at runtime once after boot (not an issue). Linux tools similar to WattTool are not available freely, AFAIK.

On Linux the simplest way is to set higher clocks for lower DPM states (4, 5, 6, 7) and force lower state (4-6) to use lower voltages. All can be done at boot. Runtime voltage changes usually show successful changes, but actually do not change real wattage (from the wall). And BIOS changes ofter are ignored by Linux drivers.

[supu]

Thanks for the new version. 

[qqqq]

Hello Claymore, could you add rejected statistics shares for each gpu individual in Ethman so we can see which exact working bad ?

[Poldi-1]

Trying ethOS for the first time and after installing claymore I get these "JsonRpcException" errors https://i.imgur.com/M6pJaEv.jpg

Any help?

[TRexMcStubyArms]

Oc the gpu's to much? Check for memory errors with something like hwinfo64 or try lowering your dcr intensity? "You can change the intensity in runtime with "+" and "-" keys and check current statistics with "s" key."

I tried going stock by turning off Afterbuner, no help.  I swung the intensity in both directions and I checked for memory errors of which there were none.

Still 100% reject rate.  I tried it in dual mining for straight ETH, still no dice.  Like I said I'm at a complete loss.

[burgla7711]

i posted this awhile ago.. did we ever find a reason or fix behind this error?

https://imgur.com/a/wLb39

[P00P135]

i posted this awhile ago.. did we ever find a reason or fix behind this error?

https://imgur.com/a/wLb39

I think that might be running two instances of claymore?  Check your processes you have running.

[general100]

Will there be new calymore miner version before Byzantium?

[Nokia555]

Added Claymore v10 to EthControl Linux. Remote console, bulk configs etc.. https://github.com/JamesSmith2/EthControlLinux

[dukemc]

I see it positve that Claymore always bring newer Mining Versions - and the DEV Fee he have honored for this

[olajos]

Please, all that have a RX 480 8GB (Shappire Nitro + 8GB) can post the best values for "-dcri"? For now I set "-dcri 23" cause I think that when I increase it to 24, 25 or more Claymore seems unstable and sometimes my hashrate fluctuates. Many thanks in advance

for me -dcri 8 is the best

[two_btc]

Is there any difference in Claymore working proccess if the share difficulty is set to 5G or 50000G while mining ETH?

[Havane]

Please, all that have a RX 480 8GB (Shappire Nitro + 8GB) can post the best values for "-dcri"? For now I set "-dcri 23" cause I think that when I increase it to 24, 25 or more Claymore seems unstable and sometimes my hashrate fluctuates. Many thanks in advance

for me -dcri 8 is the best

The dcri depends of the second coin. For DCR, I set -dcri 30