Antminer D3 Blissz firmware (10/12 v1.12 update)

[clyjr]

Found a major bug on the firmware.

If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...

Fried two of them on one D3.... gonna try RMA them

Actually, replicated this on another D3 , and it verifies

I assume on the stock firmware the fans keep running if you lose network, but the D3 keeps running trying to hash?

Hopefully blissz can get that bug fixed, really looking forward to trying the firmware since these mofos are louder than I expected...

[blissz]

Found a major bug on the firmware.

If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...

Fried two of them on one D3.... gonna try RMA them

Actually, replicated this on another D3 , and it verifies

Which firmware? I am testing this on the latest now as this is a serious bug

[tperalta82]

Found a major bug on the firmware.

If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...

Fried two of them on one D3.... gonna try RMA them

Actually, replicated this on another D3 , and it verifies

I assume on the stock firmware the fans keep running if you lose network, but the D3 keeps running trying to hash?

Hopefully blissz can get that bug fixed, really looking forward to trying the firmware since these mofos are louder than I expected...

On the original, when there's a network loss, the fans spinup like crazy until they find a working pool, hence it's safer, although louder
Going to revert to original firmware for now

[setherplatform]

Is investment in a D3 still justified as of now ? what is the estimated ROI ?

[blissz]

Found a major bug on the firmware.

If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...

Fried two of them on one D3.... gonna try RMA them

Actually, replicated this on another D3 , and it verifies

I assume on the stock firmware the fans keep running if you lose network, but the D3 keeps running trying to hash?

Hopefully blissz can get that bug fixed, really looking forward to trying the firmware since these mofos are louder than I expected...

On the original, when there's a network loss, the fans spinup like crazy until they find a working pool, hence it's safer, although louder
Going to revert to original firmware for now

I can confirm the bug. Testing the solution right now. Many thanks for at least take the time filling this bug. I'm very sorry for the loss

edit: with the automatic reboot on low hashrate function it won't burn out, but that was was not working on the previous firmware version...

[clyjr]

Found a major bug on the firmware.

If by any chance there's a network loss, the fans will stop (since they are not hashing), and the hashing boards willl burnout...

Fried two of them on one D3.... gonna try RMA them

Actually, replicated this on another D3 , and it verifies

I assume on the stock firmware the fans keep running if you lose network, but the D3 keeps running trying to hash?

Hopefully blissz can get that bug fixed, really looking forward to trying the firmware since these mofos are louder than I expected...

On the original, when there's a network loss, the fans spinup like crazy until they find a working pool, hence it's safer, although louder
Going to revert to original firmware for now

I just saw a post about an S7 saying to make sure to use a manual fan percentage since if the internet went out it may burn them up.  Not sure if they were referencing the fans since they would be full blast, or the boards.  Either way, looks like blissz is looking into it, so hopefully he gets a fix soon

[blissz]

Solved it a few minutes ago. Now testing the new package

[david916]

Solved it a few minutes ago. Now testing the new package

I see two firmware updates for today (25 Nov), do these include the fix?  It alludes to a fix for this issue, but not entirely sure.  Ty.

[blissz]

26/11 MUST HAVE UPDATE!!!

This fixes a major bug so you must upgrade guys!!!

Download:
https://mega.nz/#!f5hhlKzQ!b9I4qRJfROD9trRuJ5IH-B3FZcPe_-FjZRJS7u_tWRE

Changes 26/11:
- Solved an issue where loosing your network connection for a longer time could burn out your hashing boards as the fans run at a very low RPM.

Changes 25/11:
- Hashrate calculation is now according bitmain stock firmware (displayed  hashrate is ~3% higher now)
- + ~1% performance improvment by providing the work faster to the ASICs  
- removed dev pool from miner status page to speed up webinterface and avoid confusion (exact dev mining details are visible in the kernel log)
- fixed auto reboot on low hashrate / xxxx
- fixed issue where temperature readings could be wrong
- fixed fan error on some units
- improved stability
- allows for zero RPM fan (all custom fans should work now)
- increased upper limit frequency for overclocking. (not recommended though )
- dev fee kicks in a bit later now after changing settings


know issues:
- switching pools can sometimes cause the miner to wait for work for 10 seconds.

happy mining!

[dalu1]

Thanks for the quick fix.  I just flashed with the new version. It worked great.

Even though the new status page is much cleaner, I still like the devfee on the status page. It gives a transparent feeling. it might be just my opinion.

[heythorp]

Thanks for the quick fix.  I just flashed with the new version. It worked great.

Even though the new status page is much cleaner, I still like the devfee on the status page. It gives a transparent feeling. it might be just my opinion.

Nope I agree. I have always appreciated his transparency

I don't like asking for new features. So I won't

But if people are that worried about UI speed (I'm not) could just be a check box to say show or hide dev pools.

[blissz]

Thanks for the quick fix.  I just flashed with the new version. It worked great.

Even though the new status page is much cleaner, I still like the devfee on the status page. It gives a transparent feeling. it might be just my opinion.

If more people want to see it, I will add an option in the next version to show it or not to show it. Personally I think it doesn't make much sense to show it. It's still visible in the kernel log if you do want to see it.

Actually I;m more worried by the fact that not all the people have the 26/11 fix installed, so please share it to others if you can.

[thesavoyard]

Hi, does installing this firmware void the warranty? Also, anyone wants to share their configurations? I'd like to reduce my power cost since I live in the Netherlands.

Anyone living here wants to do a miner's co-op and find some industrial power rates?

[bearsworth]

Would it be okay to get some Frequency/ASIC voltage data going? Would be really helpful for people just perusing to see what they can push with the right settings.

I'm not sure if this is average, but here is what I have going so far:

Hash: Frequency/ASIC : Watts
15.6 MH/s: 437M/lowest : 780-790W


Please add to the list. Thank you!

[blissz]

Would it be okay to get some Frequency/ASIC voltage data going? Would be really helpful for people just perusing to see what they can push with the right settings.

I'm not sure if this is average, but here is what I have going so far:

Hash: Frequency/ASIC : Watts
15.6 MH/s: 437M/lowest : 780-790W


Please add to the list. Thank you!

good idea, maybe also nice to tell on which firmware version you mine and on which batch

[blissz]

26/11 MUST HAVE UPDATE!!!

This fixes a major bug so you must upgrade guys!!!

Download:
https://mega.nz/#!f5hhlKzQ!b9I4qRJfROD9trRuJ5IH-B3FZcPe_-FjZRJS7u_tWRE

Changes 26/11:
- Solved an issue where loosing your network connection for a longer time could burn out your hashing boards as the fans run at a very low RPM.

Changes 25/11:
- Hashrate calculation is now according bitmain stock firmware (displayed  hashrate is ~3% higher now)
- + ~1% performance improvment by providing the work faster to the ASICs  
- removed dev pool from miner status page to speed up webinterface and avoid confusion (exact dev mining details are visible in the kernel log)
- fixed auto reboot on low hashrate / xxxx
- fixed issue where temperature readings could be wrong
- fixed fan error on some units
- improved stability
- allows for zero RPM fan (all custom fans should work now)
- increased upper limit frequency for overclocking. (not recommended though )
- dev fee kicks in a bit later now after changing settings


know issues:
- switching pools can sometimes cause the miner to wait for work for 10 seconds.

happy mining!

sorry for spamming again, but please update guys....

[JPP1972]

Would it be okay to get some Frequency/ASIC voltage data going? Would be really helpful for people just perusing to see what they can push with the right settings.

I'm not sure if this is average, but here is what I have going so far:

Hash: Frequency/ASIC : Watts
15.6 MH/s: 437M/lowest : 780-790W


Please add to the list. Thank you!

Batch:      Hash:  Frequency/ASIC :     Watts

Batch 1    14.77   MH/s 400M/lowest:  699-704 W

[JPP1972]

26/11 MUST HAVE UPDATE!!!

This fixes a major bug so you must upgrade guys!!!

Download:
https://mega.nz/#!f5hhlKzQ!b9I4qRJfROD9trRuJ5IH-B3FZcPe_-FjZRJS7u_tWRE

Changes 26/11:
- Solved an issue where loosing your network connection for a longer time could burn out your hashing boards as the fans run at a very low RPM.

Changes 25/11:
- Hashrate calculation is now according bitmain stock firmware (displayed  hashrate is ~3% higher now)
- + ~1% performance improvment by providing the work faster to the ASICs  
- removed dev pool from miner status page to speed up webinterface and avoid confusion (exact dev mining details are visible in the kernel log)
- fixed auto reboot on low hashrate / xxxx
- fixed issue where temperature readings could be wrong
- fixed fan error on some units
- improved stability
- allows for zero RPM fan (all custom fans should work now)
- increased upper limit frequency for overclocking. (not recommended though )
- dev fee kicks in a bit later now after changing settings


know issues:
- switching pools can sometimes cause the miner to wait for work for 10 seconds.

happy mining!

sorry for spamming again, but please update guys....

I post in the GranatGas whatsapp Group

[phila]

Thank you for the fan fix blissz, couldn't replicate the problem, but had a feeling it had to do with when there's a network interruption, much relieved it's fixed.  Had chips go to 114 degrees on one machine before I noticed and quickly intervened.  Error rate was higher than normal after that on that machine even after restarting, but after a short cooldown period they are working perfectly again, guess I dodged a bullet.

Also received my end Nov batch d3 and the fans on this model is of a poorer quality, different model, lower amp and much louder than the fans on other batches, a shame since my other d3's were all much quieter with the custom firmware and now the new machine just tops out the overall noise level again.

[bearsworth]

Would it be okay to get some Frequency/ASIC voltage data going? Would be really helpful for people just perusing to see what they can push with the right settings.

I'm not sure if this is average, but here is what I have going so far:

Hash: Frequency/ASIC : Watts
15.6 MH/s: 437M/lowest : 780-790W


Please add to the list. Thank you!

good idea, maybe also nice to tell on which firmware version you mine and on which batch

Thanks blissz. Also appreciate the nice firmware. Really awesome .