Quote from: RooiWillie on March 28, 2018, 10:26:08 AM

Quote from: PhoenixMiner on December 26, 2017, 07:14:26 AM

Hardware control options (AMD cards only; use comma to specify different values for each GPU):
-tt Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards,
1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n %)

Setting -tt 4 as per the quote above, only shows the GPU Temp and fan speed line every 120 seconds. Is the same possible for the GPU hashrate stats lines?

No, the speeds are shown every 5 seconds or so. If there is enough requests for such feature, we can add it.

Quote from: pooparknoty on March 29, 2018, 01:06:20 AM

Running 2.8b, One of my GPU's after finding a share its hashrate drops to 0.0mh, it starts at >30mh then as soon as a share is submitted with that particular card it drops out. I have two models of this card, same memory, both with stable overclock. One runs fine with 2.8b, the other has the issue. I have tried changing my -mi for that specific card lower and the problem persists. Running previous PM versions the card runs fine. Is there a way within the same prompt to individually designate which kernal a specific card runs on? If so is there an example config for my bat?

You can use the -clnew 0 to revert to the old kernels. If you want to use the old kernels on specific GPUs only, use -clnew 1,1,0,1,1 for example to use the old kernels on the third GPU on a five GPU rig. Note that there are some changes in the new kernels in 2.8c, which may solve the problem with the hashrate drop after found share. Also note that -clnew is only available in 2.8c (not in 2.8b).

Quote from: M0ndialu on March 29, 2018, 09:14:11 AM

"-eres 0" no work.. cuda error persist (same on claymore) for gtx 1060 3gb.....any solution?

-eres 0 was always going to be just a temporary solution. The real solution is to switch to Windows 7, which reserves less than 5% of the GPU memory unlike Windows 10. This is a long-standing problem with Windows 10 and despite the numerous requests from users, it is unlikely that Microsoft will resolve it. Note that some miners report success with Windows Server but we haven't tested this personally.

Quote from: j2james on March 29, 2018, 01:16:24 PM

Hi. Excellent miner! The very good work. I used Claymore before, but new versions of Claymore beginning from 11.0 work not fine on my NVIDIA rig (some people say the same). Las good worked version is 10.6, but even this one sometime works bad Sad

I tried to use PhoenixMiner and I like what I can see for now. It is very strange, but hashrate in PhoenixMiner is more then in Claymore! I need some time to see the result in pool statistics.

Can you add some little feature? I use good android app Claymore's Monitor https://play.google.com/store/apps/details?id=com.clay.ua to see how my rig work and some information is absent in PhoenixMiner which is present in Claymore. Can you provide information by which card share was found? Something like what claymore does in log:

ETH: 03/14/18-14:13:14 - SHARE FOUND - (GPU 0)

Thank you!

We print the GPU which finds the share in the log and in the console like this (in this instance GPU1 has found the share):

Code:

Eth: GPU1: ETH share found!
Eth: Share actual difficulty: 2364 MH
Eth: Share accepted in 52 ms

Quote from: peterboy1 on March 29, 2018, 02:11:30 PM

hey dev, i suggest you not to follow claymore's path such as increasing intensity, lowering cpu load or whatever he makes in his miner.

its getting unstable.

The new kernels should be more stable as this was one of our design goals. You can use -mi 10 to get the same intensity as before, or revert back to old kernels with -clnew 0

Quote from: MinerCano on March 29, 2018, 06:10:40 PM

Perhaps folks can possibly help me as I'm stumped:
Few months back, I was getting an average of 240-250mhs with my 8 card rig. Same Bios and setup at the time.
As of recently though I'm averaging about 18-19 per card with one random gpu showing 30ish.

I've tried to reinstall windows, turn off auto updates (heard that fall creators update can slow the hashes down).
I tried the blockchain drivers, was pushing 150mhs for the same 8 card rig, and installed the new adrenaline drivers and enabled compute (that's where I got that extra 10mhs with the one random card).

I thought the difficulty went up and that's why they were running worse, but I'm reading people are still pulling about 30mhs with their Powercolor Red Devil RX580's 8GB models. (I have 16 with hynix memory and 12 with micron memory. Both groups have modded bios, which before allowed them to each run around 28-30mhs each).

Any insight as to why they would've dropped? I picked Phoenix Miner because I've heard good things about them, and the lower dev fee.

Here is a pic of one of the 8 rigs for example:
https://www.dropbox.com/s/dlavivnwdfy7fkj/MHS.PNG?dl=0

Have you turned on Compute mode on all cards? It is on card-by-card basis, unfortunately there is no way to turn on the compute mode for all cards at once, so you have to do it one by one. The difficulty has nothing to do with your hashrate, so this is not the reason for the slower speed.

Quote from: rboer on March 29, 2018, 07:34:10 PM

When this happens, what do you guys do?

Check the overclock settings on GPU2 as it seems that the problems start from there.