Hello fellow miners
I've got 3 miners, one of witch is acting weird. I have a gekko usb hub with 120W PS and active cooling of course. I run the miners with the following start line on cgminer's 4.12 version: --gekko-compacf-freq 420 --gekko-start-freq 350 --gekko-mine2 --gekko-tune2 85
Two of the miners running smoothly and stable on 420 MHz with an avg. of 275 GH/s.
The 3rd miner however was stable for a good while on this frequency but than it begun to destabilize itself.
Example line from CGminer for the "healthy" sticks:
0: GSF 1005xxxx: BM1397:01+ 420.00MHz T:420 P:420 (30:15) | 100% WU: 100% | 313.1G / 273.7Gh/s WU:3823.6/m
Example line from CGminer for the problematic stick:
2: GSF 1005xxxx: BM1397:01+
420.00MHz T:420 P:384 (30:15) |
100% WU: 100% |
274.1G / 237.5Gh/s WU:3274.1/m
The first Mhz value and the "T" (I assume it means target value) lines up with each other, but the "P" (I have no clue what it could be, maybe power or performance?) never reaches the first two anymore and remains always below them. The "P" comes to a halt either around at 384/386 or sometimes at 404/416. (The performace depends on this, therfore the reduced hashing power.) Both percentages are sitting on 100%.
The stick must be okay, because it can reach the "healthy" sticks' hashrate within the 5s time window, otherwise it couldn't get to it at all.
I've noticed, if I put this problematic miner in pair (gekko USB-port-wise) with an other, it may destablize the one I put it in pair with. Sometimes, after several restarts (hotplug-out and plug-in back after waiting 10+ sec/or hours, or complete cgminer restart) very-very rarely the "P" value reaches the "T" but some times later it restarts itself and never reaches the "T" again.
I've tried every single angle with the slightest turns of the little knob in the right bottom of the stick, every single usb-port or variation but nothing helps. I fresh and re-installed, both the CG-miner and RPi op.sys several times, no changes there. I tried different pools, just to see whether the pool's algorythm has any effect on the performance but this wasn't the answer either.
This isn't rocket science, even so cannot solve the problem.
Can you please tell me what "P" stands for and how could I get this value lined up with the others?
It really would be great if I could get this stick working again. Thanks so much for your suggestions in andvance.