Quote from: Claymore on March 09, 2017, 04:23:05 PM

Quote from: Tomintx on March 09, 2017, 03:52:47 PM

Issues with Version 12.3:
- Some rigs will not run all GPUs since v12.0. With 12.0 and later, some GPUs report 0.00H/s rate. One of rigs has 7990, only uses one core. Have not tried 12.3 version on this unit, it runs 12.0 fine.
- Option -di detect will run very long time on a couple rigs. Would love to know a procedure to do this manually by switching GPUs on and off. How to map default GPU order to -di GPU order? This is an issue because miner will reduce intensity on the wrong card, leaving the hot card to keep getting hotter and eventually stop or crash the rig. Does the ordering need to be recalculated for different versions?
Linux rigs seem more stable than Wndows rigs.
Thanks for a great miner.

1. Set more virtual memory, use less "-i" value.
2. Use "-di detect" only once to get indexes, then specify them in "-di" option. Use 0...9 keys to enable-disable GPUs if you want to find physical GPU from its index.
GPU indexes are related to hardware/drivers only, the order is the same for all versions of all my miners because they just use OpenCL order.

Thanks - It's just the one rig that will get stuck in -di detect for more than an hour. I've got indexes set on all of the rigs as provided by -di detect. It's just the one that won't finish it. I've been able to mostly guess at doing my own detection manually by switching GPUs off and on with 0..9 command and watching which one cools down/stops running and trying to create my own list. If you have advice for doing that - it would be great.