Quote from: rboer on March 22, 2018, 10:13:49 AM

HI, is there an option to have my rig reboot i the speed drops below a set point?

I see that you can restart the miner but i want to restart the rig.

thanks, Robin

You can combine the -minRigSpeed option with -rmode 2. This will shut down the miner and execute the reboot.bat file, which must be provided by you with the necessary command(s) to restart the rig (e.g. shutdown /r /t 00).

Quote from: janding on March 22, 2018, 08:07:51 PM

@PhoenixMiner

I really like the stability and the speed, here it comes, but,
The stale share rate is really bad.
I have all AMD cards, on another miner I get <1 % stale shares.
PhoenixMiner gets 5% to 10% stale shares.

This really needs to be looked at. The additional hash rate that I get using Phoenix is eaten up
with stale shares. I'm loosing .35% of 5 to 10% of all the shares submitted.

I know this can be solved, I've seen it solved elsewhere.

thanks

The new AMD kernels in 2.8b will address both the hashrate and the stale shares. Don't expect miracles but there will be tangible improvements in both areas. With that being said, we (or any other miner) can only lower the stale shares that are caused by the kernel latency (and this is the number reported by PhoenixMiner). It can't be 10% for a long period of time - the highest we have seen is 4% with -mi 12 and 2% with the default -mi 10. With the new kernels it will be at or below 1% with -mi 12.

Quote from: opeth2112 on March 23, 2018, 02:30:48 AM

Is there a guide somewhere for exactly how the -gt option affects things? What does it make changes to, and to what degree?

Thanks for the work!

No guide, but it affects the rearrangement of instructions in attempt to hide the latency of the memory. You can try each value for a minute or so (until the hashrate stabilizes), then try with 10 more or less, and so on. Once you found the two best values, try each value between them to find the best one. It is kind of long process and should be repeated for each card unless they are identical and with the same overclocking settings and BIOS-es.

Quote from: nitrobg on March 23, 2018, 06:14:52 AM

Can you implement Claymore's auto tuning for best intensity per card?

We can implement something similar but only if it works more reliable. In our testing, Claymore's auto-tuning find the right -dcri option in his miner in only one from 10-15 attempts. With such success rate we feel that it is better to stick with the default value or tune manually.

Quote from: timbojames on March 23, 2018, 07:17:03 AM

Ive been trying PM 2.7c on a standalone desktop with R9 390 8GB (XFX). I know this miner is focused on RX cards (which I have many of) but I have a fair number of R9 390s and I'm having a lot of hardware control problems.

I'm getting 'failure to set -tt error -1', but setting a static fan speed works. However, the fan speed sticks even after I close the miner. Similarly, my clocks and voltages will set (watching in GPU-Z), but they won't reset when the miner closes. This is a big problem since when I try to launch a second time, it seems like a negative voltage offset stacks with the first and I get BSOD, driver crash, etc. Regardless, I pretty much have to reboot to get it to start 'fresh'. It definitely seems faster when I can get it to run, but I have some machines that need to start and stop on demand.

MSI AB works for all my hardware settings, but I really would like the miner to handle it all and go back to stock settings when it stops. I have a few standalone desktops with one or two GPUs that I actually use and I like them to mine when idle (scheduled task) and stop when I sit down. I also have one dedicated rig that I run on a schedule to control heat midday. I've been running ethminer like this; scheduled task based on idle or time. I was about to jump to Claymore on my idle use machines simply because of the hardware control features (which ethminer lacks) so I don't have to keep switching MSI AB profiles, and that's when I discovered PhoenixMiner.

I'm just curious if these hardware control issues may be on my end or are a known issue with R9 series cards. I have tried 3 drivers in the 18 series, but I haven't gone back to 17. I've tried it with MSI AB reset to defaults, MSI AB completely uninstalled, AMD settings running and AMD settings not-running. I've lowered mining intensity and slowed DAG generation and all that, but the crashes really seem to be due to ridiculously low voltages on the second run of the miner, like PM is trying to stack a negative offset each time. Bottom line is PM doesn't release the hardware settings when it closes, at least it doesn't on this GPU and I feel like that's where my problems are coming from. I can run PM, close it, then run something like FurMark and all my clocks and voltages are still stuck on the PM settings.

I don't mean to sound high maintenance, just want to figure this out. If it's a known issue, hopefully it's one that will get fixed, but no big deal. Any input would be appreciated.

PhoenixMiner resets the OC settings if it is closed "gracefully" with Ctrl+C in the console (but not if it is closed by clicking the X button in the top right corner of the console). However, there is no definitive (i.e. fully documented) way to reset the OC settings, so it may not work with some cards (it does work with Polaris cards and 18.x.x drivers). Note that when we apply clocks and voltages, it is always with absolute values and not offsets. A possible workaround is to add command-line option -resetoc that will force PhoenixMiner to reset the OC settings at startup. We are also considering resetting the OC settings even when the miner is closed forcibly but this may cause problems if some of the GPUs are frozen and the miner is trying to restart.

Quote from: janding on March 23, 2018, 05:19:42 PM

...
@PhoenxiMiner
Please implement the auto tune feature in a release soon.
It's a big deal.

IF it works properly. And to do this, it must work much longer than 30 seconds (like at least 10 minutes).