Show Posts
Key value of Awesome Miner is to keep the miners running, yet I'm yet to see this work with GPU miners.
Here is a common use case I run into:
1. AwesomeMiner launches NsGpuCNMiner
2. NsGpuCNMiner hangs on start-up:
3. Mining stops. Hashrate is blank. Miner is never restarted by AwesomeMiner. Manually restarting the miner in AwesomeMiner typically brings it back to life. Sometimes a system reboot is necessary.
Adding custom rules like if hashing average is < 600kH/s for the past 2 minutes, restart miner (typical speed is 1kH/s+) doesn't work.
What I'd like is to detect when a GPU miner is no hashing, restart it a couple of times, and if that doesn't help, reboot the system. I also want to easy the history of rule executions (when the trigger acted, what was the action, and whether it succeeded).
What am I missing?
Best, Michael
Here is a common use case I run into:
1. AwesomeMiner launches NsGpuCNMiner
2. NsGpuCNMiner hangs on start-up:
Code:
╔════════════════════════════════════════════════════════════════╗
║ Claymore's CryptoNote AMD GPU Miner v10.2 Beta ║
╚════════════════════════════════════════════════════════════════╝
XMR: 1 pool is specified
Main Monero pool is us-east.cryptonight-hub.miningpoolhub.com:20596
At least 16 GB of Virtual Memory is required for multi-GPU systems
Make sure you defined GPU_MAX_ALLOC_PERCENT 100
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools
OpenCL initializing...
AMD Cards available: 3
GPU #0: Ellesmere, 8192 MB available, 36 compute units
GPU #0 recognized as Radeon RX 480/580
GPU #1: Ellesmere, 8192 MB available, 36 compute units
GPU #1 recognized as Radeon RX 480/580
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 algorithm ASM, -h 1800, -dmem 1 (Memory used: 7560MB)
3. Mining stops. Hashrate is blank. Miner is never restarted by AwesomeMiner. Manually restarting the miner in AwesomeMiner typically brings it back to life. Sometimes a system reboot is necessary.
Adding custom rules like if hashing average is < 600kH/s for the past 2 minutes, restart miner (typical speed is 1kH/s+) doesn't work.
What I'd like is to detect when a GPU miner is no hashing, restart it a couple of times, and if that doesn't help, reboot the system. I also want to easy the history of rule executions (when the trigger acted, what was the action, and whether it succeeded).
What am I missing?
Best, Michael
I used the accept progress rule to automatically restart the miner if it doesn't get any accepted work by the pool within a set amount of time. Have you tried it yet?
