Pages:
Author

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

full member
Activity: 174
Merit: 100
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 Undecided

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...


No worries man, we all know this could happen x) , I've set two high performance blowers to cooldown the hashboards, and they seem to be working now, go figure x)

Glad to help, and thanks a lot for the quick update, gonna try it now
newbie
Activity: 23
Merit: 0

But they're ribbed, I was always told that increased noise.

heh heh heh.
newbie
Activity: 7
Merit: 0
newbie
Activity: 23
Merit: 0
Just installed the latest version of the firmware, mine was a couple of days old I think, selected manual mode for the fans from the drop down box (didn't have that before) and applied, when it came back up the fans were running at 100% even though the speed was previously set at 35%, managed to fix it by deleting the 35 then retyping it and applying.  All seems to be good now.
newbie
Activity: 30
Merit: 0
Quote
Do your fans also run at different RPMs?

To keep the temps the same as the other batch d3's (80 degrees average during the day, 70 at night Silent Auto), 17.2 GHS average,  I have to run the latest batch d3 at "Default auto"

Fan speeds
Batch October/beginning November fans:
Daytime:   xxxx /3980 RPM  sound is concentrated on the inside of casing, less audible outside.  With stock firmware fans run at xxxx/4500+ RPM.
Nighttime: 2160/3210 RPM

Batch end November fans:
Daytime:   4xxx /5800 RPM  very loud, different sound than first model fans, like it's concentrated on the outside of the casing, sound is heard even at a distance.
Nighttime: 3090/4080 RPM

Quote
Good to hear your d3 is fine!  Grin

You can replace the fans with some other models. I actually run mine now with two Scythe Slip Stream Slim 2000rpm, 120mm. This is of course not the solution if you want to run at high hashrates, but for the lowest voltage setting and 15 to 16 Mh/s this is a real nice and quiet fan.
I also modded the PSU: I added a small fan controller to have it run at half the RPM. Now this combination is actually really silent. I can have it run it in my living room if I want to.

Thanks for the advice blissz, will definitely look into those fans as well, anything to help being able to live with these things lol.  I also bought some 6" inch and 12" Acoustic Ducting.  Plan to strap the 6 inch ducts to the fans and put the whole machine into the 12 inch duct as well and wire all the ends to separate windows to the outside with mesh over the openings (got some nice bug splatter already).
sr. member
Activity: 336
Merit: 258
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.

Good to hear your d3 is fine!  Grin

You can replace the fans with some other models. I actually run mine now with two Scythe Slip Stream Slim 2000rpm, 120mm. This is of course not the solution if you want to run at high hashrates, but for the lowest voltage setting and 15 to 16 Mh/s this is a real nice and quiet fan.
I also modded the PSU: I added a small fan controller to have it run at half the RPM. Now this combination is actually really silent. I can have it run it in my living room if I want to.
newbie
Activity: 10
Merit: 0
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.

Do your fans also run at different RPMs?
sr. member
Activity: 392
Merit: 250
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 Wink.
newbie
Activity: 30
Merit: 0
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.
sr. member
Activity: 362
Merit: 252
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  Cool
- 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 Wink)
- 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
sr. member
Activity: 362
Merit: 252
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
sr. member
Activity: 336
Merit: 258
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  Cool
- 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 Wink)
- 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....
sr. member
Activity: 336
Merit: 258
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
sr. member
Activity: 392
Merit: 250
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!
sr. member
Activity: 560
Merit: 253
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?
sr. member
Activity: 336
Merit: 258
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.
newbie
Activity: 28
Merit: 0
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 Wink

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.

member
Activity: 83
Merit: 10
Performing it is a better way of learning things
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.
sr. member
Activity: 336
Merit: 258
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  Cool
- 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 Wink)
- 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!
newbie
Activity: 22
Merit: 0
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.
Pages:
Jump to: