If the chip number >32, the miner will config the blade with 48 chips, and it will not result in hash power reduce. For more info to support you, please send email to us with the picture of main page, thanks.
iBeLink™ DM384M ASIC Dash Miner Support Thread
- Thread starter iBeLink
- Start date
How do I switch pools ? the start/stop button on my second pool is not red like all the other buttons
Thanks
mine certainly does not do that I waited like 3 min's ,,, the start button on the second pool is greyed out ?
it's fixed now ,,,,,,,, I think you were right about pool communicating but time did the trick... I was trying to connect to nicehash but it took ages for communication to work ,,,this is something I did'nt notice at the time when i first loaded up zpool
cheers
iBelink, please check your pm. i'm still having issues with customs because of lack of information from your shipper. let me know what are my options.
Last edited:
Hi,
Just took my dual miner out of the box.
Powered right up and fans spin.
However, none of the lights on the front light up and,
cannot access it.
Any thoughts on what I should do to resolve problem
would be appreciated.
Thank you,
Ron (Woody2028).
Just took my dual miner out of the box.
Powered right up and fans spin.
However, none of the lights on the front light up and,
cannot access it.
Any thoughts on what I should do to resolve problem
would be appreciated.
Thank you,
Ron (Woody2028).
It seem some hardware issue in it.
Please make sure the connection line between Pi and LED lamp board is plugged in, it maybe loosed.
And double check the PI works normally, of course, do not forget check the network link is good status.
If possible, please replace the PI to test it.
Any more issue let us known, our email is [email protected]
Thanks
Got the same problem, they said to change out the Raspberry PI board, I'm going to order one this weekend and see if fixes this. I think it's a PS problem though.
note gaps are where the miner stopped today on nicehash:
Me too, Im thinking this maybe cause the nicehash it self, this is very random and from my 4 miners sometimes all 4 restarts in one time sometimes 2 of them and also any of them separately with different difficulty.
Important is that not the miner restarts as when you power it up just cgminer.
Or maybe our cgminer have extranonce bug?
Found this:
Found this:
In: https://www.dash.org/forum/threads/...-9-mh-s-releasing-in-mid-may-2016.8624/page-3
But the version listed in the program is cgminer-3.5.6, I didn't think that had the bug in it, otherwise it wouldn't run at all on nicehash, but then again, there is no way to verify what version of cgminer that is used....
Very strange and telling though if all of your miners went down at the same time, that opens a new can of worms...
Very strange and telling though if all of your miners went down at the same time, that opens a new can of worms...
About the miner restart phenomenon, please refer to FAQ
Why mining software automatically restart?
Mining software support self recovery from network fault and drive fault function, with watchdog monitoring for the whole system , when an anomaly is detected, the mining software will automatically restart, trying to self recovery from the fault, so mining software auto restart is a normal phenomenon.
General, restart phenomenon should be random, but if your local network break down, the miner at the same router may restart at the same time and try to recover the network link.
Of course, the remote pool bad status may cause the miner restart also.
Further more, if you config the temp monitor, the miner will shut down when the temp above the shutdown threshold, and you should restart it manually.
The nicehash extranonce bug already fixed at 3.5.6.
Why mining software automatically restart?
Mining software support self recovery from network fault and drive fault function, with watchdog monitoring for the whole system , when an anomaly is detected, the mining software will automatically restart, trying to self recovery from the fault, so mining software auto restart is a normal phenomenon.
General, restart phenomenon should be random, but if your local network break down, the miner at the same router may restart at the same time and try to recover the network link.
Of course, the remote pool bad status may cause the miner restart also.
Further more, if you config the temp monitor, the miner will shut down when the temp above the shutdown threshold, and you should restart it manually.
The nicehash extranonce bug already fixed at 3.5.6.
But the version listed in the program is cgminer-3.5.6, I didn't think that had the bug in it, otherwise it wouldn't run at all on nicehash, but then again, there is no way to verify what version of cgminer that is used....
Ok, but once it restarts, it always goes back and mines on pool 0, which is hard set and mines where to? Isn't there a way so that when it restarts, that it could go to a chosen backup pool? Or can it do that, let me know?
To do this, if you have list of pools you must DELETE all your pools details and rewrite it again in list accordingly to your priority! not good unfortunately,also you cant see pool details already in use so we have actually lot of headache because not always im using same user and password. I know, Ibelink said before that they did for safety reason ...
Please add option where on the list NEW pool should be placed 0-1-2-3-4-5etc, not only as last always.
Good suggestion, we will consider to add the function to configure the pool list more easy in the new version.
I switched pools recently. Got good performance for the first day on miningpoolhub, then the next day I get like 30-50% reject rate, and on my end its showing as discards. Is that the miner or the pool? I didn't have any of these issues on NiceHash.
It's funny, I had 2 solid days of mining on coinmine.pl where there were no restarts, now the problem is back again. Also, i cannot mine without the miner restarting on NiceHash every 2hrs or so. It may be the pool(s) after all...
I basically confirmed that it was a question of mining pool, while not the miner box, please refer to FAQ:
Why some mining pools rejection rate is very high?
Due to hash rate of the iBeLink mining machines is very high, dozens of times of general GPU, some mining pools are unfriendly to ASIC mining machine, cause to very high rejection rate. If mining pool can set the difficulty, please appropriately raise the difficulty of mining, reduce nonce average quantity, so as to reduce the rejection rate, or switch to the ASIC friendly mining pool.