Blissz.. when both of the dev fee pools are down you go into constant reboot mode. Is this intended? Seems like a bug
Thanks for reporting, I will have a look at it.
Hi there,
I am running v1.1, thanks for your good job.
The only problem I found at the moment is - very late delay between the ASIC became "xxx xxxx" and miner restart. The restart has been executed only after 5 hours of the XXX XXX appearing on problematic chain
some inputs for analysis of such delayed restart:
1. The problematic chain is showing No. of ASICs = 60 (looks all healthy :-)
2. The problematic chain showing around 4000 HW errors and all XXXXXXXXXXXX
3. The true hashing speed is around 1/2 of normal one
All this information from miner management console. After auto- restart all correct... yet. I just lower frequency of the problematic chain a bit.
So on this status of clear needs to restart miner due to trouble with one chain (xxx , low hashrate) - the automatic restart has been done only after 5 hours
(Probably you should initiate restart of miner in 1 minute after the number of XXXXXXXXX has exceeded, let's say 10? I know some people are modifying stock firmware
in such way and it works well. From my practice if D3 chain is starting collect XXXXXXXXX, this chain very soon becomes obsolete and restart is a must.
Just IMHO.
Waiting for reply and patched version!
Good luck!