Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 10. (Read 125911 times)

Hey guys , I update my miners to v1.12 all looks good , but after 2 days I lost one of my miners on network, when I went on site i found that Red LED = OFF and Green LED = OFF .
Try to reboot/ shut down , perform hard button reset. Nothing still no luck.
Any idea what I can do? is there any fix ? or I need to send to Bitmain (late Nov batch)
Some of my other miners don't show all chains, and some are 54 ASIC only.
Funny enough that after changing from Prohashing to Nicehash 4 out of 10 cards come right ...
Any help will be welcome :-)
Will the new Beta FW help?

anybody mine moneci (XMCC)?
https://coinmarketcap.com/currencies/monacocoin/

What Firmware from Blissz you use?
I´am still on 1.12 and i don´t have this problem, i can add as many pools i want, after restart must only wait the 1st time dev mining, that the API is not more blocked and then i can add the pools.

or just use Awesome Miner and it will change the pools for you on all of your D3s to the best option at the time. I found with Blissz FW it works well to switch between the 3 pools and on my L3s and S9s I can add a lot more than just the three pools... FYI Blissz if I add more pools to the D3 in Awesome Miner when your DEVFEE mines it removes the other two pools I added... not that big of a deal for me as 3 pools are normally enough but I use 5 pools on my other antminers.

These connection configuration goes "from the box", of course I will reconnect to 1-2-3, when I will have phisical access, but now solution for me is downgrade firmware.

BTW - is it possible to make changing Pool Priority more easy? I have 18 pcs of D3 and changing pools takes a lot of time if needed.
The easiest way that I found for me now is next:
1) PROHASHING - main pool, NICEHASH - backup
xx11.eu.nicehash.com:3336#xnsub  - always DEAD
prohashing.com:3333
x11.eu.nicehash.com:3336#xnsub

And when I need to change priority:
1) NICEHASH - main pool, PROHASHING - backup
x11.eu.nicehash.com:3336#xnsub  - always LIVE
prohashing.com:3333
x11.eu.nicehash.com:3336#xnsub

Hi Blissz

Thanks for all your hard work - much appreciated !

With the latest beta releas, I cannot connect to the Prohashing pool ......   stratum+tcp://prohashing.com:3333
The Miner Status shows the pool as Dead, but on the prev release I can connect without issues.

Regards


Hi Blissz

After searching some forums I found a link that suggested that this is a random error/issue :
https://forums.prohashing.com/viewtopic.php?f=5&t=2796

I rebooted the miners a few times and can now connect again ;-)

Good to hear it works well now. v1.12 is lacking some features that the beta does have, but it's the most stable version right now. I did make minor changes / compilation improvements between those versions which might helped making v1.12 more stable then v1.11.

Hi, thanks for pointing this out on the beta version. I do advice to always connect your chains to 1,2 and 3 and leave connection 4 unconnected, but I will have a look if I can make it compatible if you don't connect it correct.

I was using v1.11 and my miner rebooted every few hours, but both checkboxes for automatic reboot are unchecked. HW errors were reasonable, but a chain would go XXXX sometimes and I had to restart the miner.

Yesterday I upgraded to v1.12 keeping same configuration and it has behaved perfectly for 15 hours: 0 HW errors, no reboots. I see nothing in the release notes for v1.12 that explains it, maybe it's just a coincidence? (These machines tend to wake up with a different mood every time).

@blissz Any changes between these two versions that can explain this?

Have an issue with several miners - when blade connected to 4th connector - Hashrate decreased to 2.2-2.3 GH per blade
https://yadi.sk/i/abCxiksm3RFidN
2.04 and 2.06 firmware tested
1.12 works correct:
https://yadi.sk/d/-dF5iKyc3RFizz

++ Thank 

+1!

Also could it be possible to put the asic voltage show on the miner status, would save me a lot of time when im setting the machines, thanks.

agree make it mine your dev fee all at once after 5 min or so, i bet everyone must think the same.

Have to say the D3 boards are not so stable quality wise. I am quite lucky with mine, but quite a lot of D3 boards (partly) fail after a while.
 I do think the custom firmware helps to improve the lifetime when you run them at a lower voltage / lower temperatures.

by the way  you got a PM now

Having problems over here. A few un-modded ones are having issues with their boards. Glad we're still in warranty for them.

Blissz, have you gotten my PM's or noted my posts? I'm having some issues, but would like to submit the kernel logs to you and the PMs have a text limit size.

does anyone else have D3 blades crapping out left and right???  (even ones NOT modded)

If anybody would like to sell their D3 please message me.

v2.06 beta :: 05/01 :: test version

Download:
https://mega.nz/#!mxwhmCZb!8Xsj5c2bfvuaK_fSI2av3zrqv3dFz-w3AoSt7W-MD8U

Changes 05/01:
- more stable autotune / reset of ASIC chains (HW errors will be reset to zero after changing a board's frequency)
- ~15 to 20 seconds faster startup of the miner after changing a setting
- optimized cgminer binary size
- fixed browser caching issue when changing between stock and blissz firmware

Changes 22/12:
- reboots the D3 on high temperatures (> 85 deg PCB temp). This feature will save your unit in case your fans will fail.
- improved auto tune algorithm stability
- Increased the chip starting frequency of the autotune algorithm for higher voltages.

Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected


Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status


Important: The autotune feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:

set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log, or if it doesn't fit, focus on the last part
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information

Thank you!