Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1158. (Read 6590565 times)

Can anyone point me to a link, article, or some simple instructions on how to give Claymore a shot at SOLO mining?  Thanks!

Throttling is from power usage or thermals.  You can increase power limit, and check temps.  I would recommend undervolting (if card allows).  I can easily save ~20%+ power usage on 470, really stable.  Also can boost performance since card will throttle less (doesn't matter much for Eth, but for sia/dcr/other, and gaming it does). Undervolting is a lot easier on 4xx cards though.

As far as the miner is concerned, there is -li to lower intensity (higher number, lower intensity), -ethi (default 8 ), can be set per card for etherium.  Also -dcri (default 30) for sia/dcr.  It is documented well on page 1 of thread....

It turns out I have to change "POWERLIMIT"?
Ubuntu itself is limited, and therefore jumps heshrate. She does not respond to the settings which are stitched in the BIOS. With windows no such problems.

I going too be releasing the benchmarking setting for Dualmining ETH and SC with Claymore's Dualminer for AMD GPU's, for 200 series and 300 series GPUs.

Just posting test settings and hardware setups:

1) Phenom 555 dual core processer, 1 core disabled and overclocked to 3.5Ghz.
2) Asus Crosshair Formula IV motherboard
3) Antec PSU 850watts
4) 8GB DDR3 running at 1066mhz (faulty memory controller on Phenom and can only run memory at the lower speed).

Firstly, running the CPU at 3.5Ghz does result in more shares accepted per hour, when dualmining, but above 3.5Ghz their is no extra shares found per hour. By disabling 1 core in motherboard bios, you can bring the electricity usage back down to an acceptable level.

Window 7 OS

Special settings:

1) Aero graphics disabled and put into High Contrast Black.
2) "Desktop Manager" disabled via "Services".
3) Crimson Edition 16.8.2 Hotfix - latest drivers

GPUs

1) earliest iteration of R9 290 (ASUS) - overclocked to 1100mhz and memory 1300mhz. Powerlimit 20% Sweet Spot for Mining ETH and SC.

*Powerlimit above or below 20% produce less shares accepted per hour.
*Can be overclocked to 1150mhz with 50mvolts, but produces less shares per hour, then when no extra voltage is added for solo mining.
*Dual mining can be overclocked 1130mhz with 50mvolts, but produces less shares per hour, then when no extra voltage is added for dual mining.

2) XFX Radeon R7 370 2GB Double Dissipation - overclocked too 1180mhz and memory overclocked too 1500mhz, Powerlimit 20% Sweet Spot for Mining ETH and SC.

No options on MSI Afterburner to change Powerlimit above 20% or add extra mvolts.

Notes: These 2 GPUs produce 8.5% less shares accepted per an hour on Intel Chipsets and CPUs. Opencl appears to be primarily coded for AMD chipsets and CPUs.

The Benchmarks for AMD GPUs has taken 2 weeks of testing - so I'm not going to do a similarly benchmark to find the sweet point for dual mining ETH and DECRED.

Those benchmarks will be posted in a couple of hours, just rerunning another session of mining.  

Hey, how and where to you change voltages under linux with amdgpu driver ?
somewhere in /sys/class/drm/cardX  ?

Can I set my GPU load to 80%? If I mine with 100% my GPU throttles a lot
It's a r9290 gigabyte.

Any other idea how can I reduce throttling?

Yes you can. just mine using your BTC address instead of DCR.

Yes,  here you have:

I have the impression that claymore handles unstable pool somewhat conservative comparing to genoil+mining proxy(dwarfpool version), the issue is with going back to original pool when connection is recovered, is there any way to change setting so it goes back to primary pool as soon as possible.

I'm checking this issue in Linux, so I will have some news in a few hours.

Thanks for the Linux support!

I'm on Ubuntu 16.04 and amdgpu-pro_16.30.3-315407 with a RX 480 ref
No ADL installed - so its fine that I get an error for that when I start the miner.

... and continues with a hashrate like this

tail /var/log/syslog

so it seems the same like for the other linux folk over here with RX* cards. Genoil Ethminer is running fine though.

same Problem here.
Also tried  Kernel 4.8 RC2 , same issue.

Do you guys mine at normal speed when seeing this issue ?
With Claymore's miner have realy bad mining results (arround 5 MH/s)

I have this exact same issue, causes CPU to be tagged to 100% from all the error logging.

There was short break in mining 2hours ago:http://etc.nanopool.org/account/0xbc2e6739781028ebcac5dd81c60f85470d26c621
In sia too.
I have two rigs: linux and CDM 5.3 which resumed after that break
And Windows with CDM 6.2 which hanged with whole rig...

Additionaly : now I switched to eth  only Mode on epool.  Works fine but I have no worker on stats page:
I have such line  in epool. Txt
:, :  , : x,

I can't go on nanopool's website, but mining is fine...

I suppose a big error... I have noticed if pool goes offline (like nanopool now) miner hangs with my whole rig...

Besides I noticed yesterday that 6.2 version shows only 32celsius on one card, restart helps

I'm having problems with temperature control under ubuntu 14.04.5 and claymore 6.2 beta 2. The  miner is working but no fan and temp are displayed, nor -tt command is working.
Please let me know what to do in order to fix this problem.

And how will you test gpu running stable for hours in all different states ? When Claymore add such Options the Miner will be more complicated to use and bound to current AMD-Drivers (Wattman - 7 States). I use a fixed GPU Frequency with Powerlimit + to disable Throtteling and then I will undervolt to get less Powerdrain. The Powerlimit Option is only a Limiter.

cg

Gary

At this point you might as well edit the BIOS and flash all your GPUs.

Thank you for the voltage new feature! Its really useful for the memory. But if we use only one voltage value for the gpu, we lose the option to undervolt more if the gpu throttles. For example, if the cpu throttles between 1075mhz and 1145mhz we can go also from 860mV to 900mV. But using only one voltage value, this value needs to be the biggest value for the higher frequency.

This doesn't matter if you use a fixed gpu frequency, but when using all the gpu power states may be will be interesting to add a voltage table according to that gpu states.

Anyway, seems that from state 3 to 7 the voltage scalability is lineal, so, maybe its easyer to implement a method to add/subtract voltage to all states.