Quote from: janding on March 06, 2018, 02:21:43 PM

Yes. Using 2.7c
The Freeze with the "E" on the screen happens to me any time I try to scroll back.
Have to exit miner and restart it.

We will look into this, the problem is that it doesn't happen on our test rigs but we will find a way to reproduce and fix it.

Quote from: aardria on March 06, 2018, 11:48:11 AM

...
I've been running the miner now for a few weeks and it's superb, except for the mentions below:

1) the miner doesn't seem to be optimized for the RX550's as attempts your miner with them the resulting hashrate is ~7+, while Claymore gets ~10+. Is it optimized for them and I'm doing something wrong, or can the you make it compatible if it's not?
...

Well, we don't actually have any RX550 cards here Embarrassed

so it is probably running the generic kernels, which are slower. We will try get some and make better kernels for them for the next release.

Quote from: pigseye on March 06, 2018, 07:53:36 PM

Hi All,
Just want to say thanks to the developers for this mining SW. It is working GREAT on my 12 card rig that uses a Biostar TB250 BTC-Pro motherboard.

I have one simple request.

How can I pause mining on cards 10, 11, and 12 or higher?

if you could add a feature where a=10, b=11, c=12, ... or something like that it would be great for rig trouble shooting that is related to hardware.

Thanks!

We can do it for example like this: type 010 for card 10, 011 for card 11, etc. The variant with letters will work too (and it is easier with just one key press), but it takes too much of the available letters for other commands. Thanks for the request, will try to include it in 2.8.

Quote from: weenston on March 06, 2018, 10:32:33 PM

Hello,

Every 24 hours or so I get this;

17596:15:34:21.877: GPU2 CUDA error in CudaProgram.cu:437 : the launch timed out and was terminated (702)
17596:15:34:21.933: GPU1 CUDART error in CudaProgram.cu:434 : the launch timed out and was terminated (6)
17596:15:34:21.972: GPU2 GPU2 search error: the launch timed out and was terminated
17596:15:34:21.972: GPU1 GPU1 search error: the launch timed out and was terminated

I'm assuming it's power draw or OC related (both are not aggressive so I'm assuming it must be the power limit), however from this can you deduce that GPU 2 is the culprit or is it too hard to tell?

Thanks!

Try to lower the memory overclock on GPU2 (or increase the core voltage if you are undervolting it).

Quote from: Yellow_donkey on March 07, 2018, 02:27:25 AM

Dev, solo is here you da man! BUT I do have a couple of comments:

1. Your example at the top of your 2.7c release says -coin Vic and Akroma, but down in the list you don't list either of those. Can you please amend or tell us a full and accurate list of coins that work under the -coin feature please.

2. I am using drivers on my AMD cards that run like a bat out of hell speed wise on low DAG coins but once I go back to high DAG coins it goes to sheet. But I only mine low DAG coins so it does not matter to me. But an issue I ran into is that I have all along used -minspeed in clay to reset my miner and re-apply my OCs when they fail and whatnot, but because the dev DAG is high by default, the -minRigSpeed calculates the devfree speeds into its feature, thus, unless I mine a -coin I cannot use -minRigSpeed because the DAG lowers my MHS during the devfree periods and calls up my -r function. Even though my own mining is at a nice and high tweaked speed. Clay does not calculate the DevFree periods into the -minspeed totals.

3. I am switching to solo Vic now so will try the -coin Vic to avoid the DAG switching high and impacting the -minRigSpeed mis-calulations for a work around for now. (more of a statement). My last coin was not available under the -coin feature thus I could not use the -minRigSpeed feature and had numerous OC drops were I went periods un-optimized by a card or two.

4. Am I wrong or is the capitalization for the command lines are required. If it is spelled out as -minRigSpeed in the instructions then you have to use -minRigSpeed as -minrigspeed wont be recognized. Seems kind of trivial and I am sure causing more folks then just myself a headache. unless I am wrong and this was just a 4AM sleep issue.

1. Done, thanks for noticing.
2. We don't mind excluding the DAG generation from the average speed to avoid this problem. Will try to fix this in 2.8.
4. Yes, the command-line options are case-sensitive. We will fix this too in 2.8, you are absolutely right that there is no need for them to be.

Quote from: cdrx on March 07, 2018, 10:18:19 AM

Stable. but fans are loosing settings for AMD after some time and goes higher up to 95% fan speed then back, then up. I opened afterburner and use its fan setting - all is good when I use AB.

Code:

-tt 55 -fanmin 55 -fanmax 85

Could you tell us the driver version? There is nothing wrong with sticking with AB, if you are happy with it.

Quote from: Teress on March 07, 2018, 11:47:40 PM

Hi devs, LOT of people are still waiting for linux version Sad

Sad...

We know, we are working on it Embarrassed

Quote from: Tibone18 on March 08, 2018, 03:49:06 AM

Hi, I cannot do anything because Windows defender detect a virus and delete everything.https://ibb.co/iBhNDS
Is it possible to fix it in 2.8 please ?

The best way to fix the problem is to add the folder(s) where you keep (and download) the miner software to the Windows Defender exceptions as specified here: https://support.microsoft.com/en-us/help/4028485/windows-10-add-an-exclusion-to-windows-defender-antivirus. As a last resort, you can turn off the Windows Defender real-time protection then turn it back on after unzipping the archive and adding the folder as an exception (besides its brain-dead attempts to delete PhoenixMiner, Windows Defender can be useful in detecting real threats).

Quote from: blackwhite5674 on March 08, 2018, 05:13:44 AM

Has anyone been able to get an improvement in hashrate when adjusting the -gt parameter? In most cases, my hashrate goes down significantly when going very high, or stays the same when adjusting slightly.

Does it affect shares found or reduce stales, or is it just meant to give a slight boost in overall hashrate and performance? What exactly is the -gt parameter for?

No, the only benefit from non-standard GT value(s) is the potentially increased hashrate as it is printed on the console every few seconds. Yes, the default GT value is the best for most cases but not always - if you can't increase the hashrate by changing GT, leave it as it is by default and forget about it.