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

[SteganoS888]

http://i.da.am/6938.jpg  http://i.da.am/6940.jpg  

[1714956578]

1714956578

[1714956578]

1714956578

[1714956578]

1714956578

[1714956578]

1714956578

[Mattithyahu]

Too small image, tiny resolution, mate....








Can anyone answer these two questions?


How does the HW errors impact mining speed/hashrate etc?


How does the HW errors impact the lifespan of the hashboard/chain?

[piliff]

Can anyone answer these two questions?


How does the HW errors impact mining speed/hashrate etc?


How does the HW errors impact the lifespan of the hashboard/chain?

+1

In my opinion (and with some experience) HW errors do not affect the process. One of hashing boards in my D3 showed more than 300,000 errors per hour, but the hashrate was exactly the same as on other devices.

But I don't know about device lifetime. Maybe if it has so much errors, chain board will die soon. Maybe not. 

[Sidifotoskwa]

I set ASIC Voltage to 1 instead of lowest on CHain #2 and HW's are at 0 now. 

[Gritch]

got a D3 from bitmain and CHain #3 isn't showing.  Should I wait for warranty reply from bitmain before flashing with Blissz firmware?

I had the same problem, you have to reboot

[ruptan]

v1.02 :: 30/11 :: recommended update

Download:
*removed link due to temperature reading problems with chain 0*

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down


know issues:
- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!

Thanks mate. I am still using your 11/21 and it is rocking for me. I have no intention to change it for now unless you change the algorithm. Great job by the way. You rock!

[Sidifotoskwa]

got a D3 from bitmain and CHain #3 isn't showing.  Should I wait for warranty reply from bitmain before flashing with Blissz firmware?

I had the same problem, you have to reboot

Rebooted and restored but same issue.  I should try blissz firmware and see it shows up...

[blissz]

got a D3 from bitmain and CHain #3 isn't showing.  Should I wait for warranty reply from bitmain before flashing with Blissz firmware?

I had the same problem, you have to reboot

Rebooted and restored but same issue.  I should try blissz firmware and see it shows up...

wait a little bit more. I am currently testing a version which can help in case you've chains not showing up. / temperature reading problems

[Gritch]

got a D3 from bitmain and CHain #3 isn't showing.  Should I wait for warranty reply from bitmain before flashing with Blissz firmware?

I had the same problem, you have to reboot

Rebooted and restored but same issue.  I should try blissz firmware and see it shows up...

wait a little bit more. I am currently testing a version which can help in case you've chains not showing up. / temperature reading problems

Since I reboot my ASIC status is different !!

https://www.dropbox.com/s/o9za781tuf5lzvd/error%20D3.jpg?dl=0

What is the problem ??

Thx

[blissz]

v1.02 (beta) :: 30/11 :: test version

This version hopefully helps the D3's that have missing chains problems / temperature reading problems.
Please give me some feedback on this version: If it doesn't work for you please let me know if it works ok for you on the stock or on another version of the custom firmware.
thank you!

Download:
https://mega.nz/#!fwBylL6C!Wt3tZYpnGVjJY4Zz5MjVszg3DZ9I1L9dj-aLT9FuXPU

Changes 30/11:
- slows down the detection of the chains after enabling them. It might help people that have sometimes an unrecognized chain issue.
- (hopefully) improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down


know issues:
- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!

[Ubersonic]

You da man Blissz, keep up the good work!

[jbmod]

Congratulations @blissz,

The version 29/11 seems really stable already. Running for hours now, 462MHz on all boards with power settings to 8. No significant HW errors for now. Lower voltage settings result in higher HW errors - this is what I found out so far... Fans running at 25% (manual mode), still the original ones - temps are always below 80°C.

I now tried your newest version to medicate my other D3, this one has a Chain#1 problem and sometimes sees only 55 of 60 asics, sometimes it doesn't start at all. Your new FW is not changing this behavior instantly but I was able to bring Chain#1 back into 60 asics and 0HW errors by gently overpowering chain#1.
So this D3 runs like:
Chain#1: 400MHz, Power: 15
Chain#2: 462MHz, Power: 9
Chain#3: 462MHz, Power: 9

This setup is stable for now and I really appreciate your work, because with default bitmain fw those custom treatment wouldn't be possible at all. This makes this D3 hashing at almost 17GH/s while fans stay below 3000rpm.

After dealing with 3 D3, all machines turned out to be really different. So I wouldn't recommend any precise configurations because everyone needs to find out how his miner is doing best. And it seems that bitmain has a lot of fluctuations in there production line - otherwise we wouldn't see those big differences here...

[Gritch]

Guys,

Since today, every 40 minutes or so, my status are dead ...

https://www.dropbox.com/s/eoc2j7srpmi9o06/before%20rebbot.jpg?dl=0

I have to reboot manually otherwise it will not Hashrate...

https://www.dropbox.com/s/394ty4bkiqcftsp/after%20reboot.jpg?dl=0


Anyone know why?

Bliss your firmware can solve this problem?

THX

[jbmod]

Guys,

Since today, every 40 minutes or so, my status are dead ...

https://www.dropbox.com/s/eoc2j7srpmi9o06/before%20rebbot.jpg?dl=0

I have to reboot manually otherwise it will not Hashrate...

https://www.dropbox.com/s/394ty4bkiqcftsp/after%20reboot.jpg?dl=0


Anyone know why?

Bliss your firmware can solve this problem?

THX

This should be solved by the most recent bitmain firmware as well - are you using the latest one (download from bitmain)?
I experienced this one before too (every 10 hours or so - not that often like you), I downloaded the latest firmware from bitmain but still - sometimes the machine was stuck with all asics xxx'ed.
I switched to blissz firmware, this performs an auto reboot if this problem occurs...

[Gritch]

Guys,

Since today, every 40 minutes or so, my status are dead ...

https://www.dropbox.com/s/eoc2j7srpmi9o06/before%20rebbot.jpg?dl=0

I have to reboot manually otherwise it will not Hashrate...

https://www.dropbox.com/s/394ty4bkiqcftsp/after%20reboot.jpg?dl=0


Anyone know why?

Bliss your firmware can solve this problem?

THX

This should be solved by the most recent bitmain firmware as well - are you using the latest one (download from bitmain)?
I experienced this one before too (every 10 hours or so - not that often like you), I downloaded the latest firmware from bitmain but still - sometimes the machine was stuck with all asics xxx'ed.
I switched to blissz firmware, this performs an auto reboot if this problem occurs...

Thank for your respond

I have the last D3 (sub-model 19.3 gh / s) I think have the last FW of bitmain.
I'm thinking of trying Blissz's FW, but will the warranty work?

And I also an another problem with my second D3 :

https://www.dropbox.com/s/15tqz58g1h1d5j3/ASIC%20PROBLEM.jpg?dl=0

My ASIC status is not good, I have 54/60 ASIC since I restarted ...

Someone knows what to do?

This D3 have just one day ...

Thx

[JimmyFish]

Hi Blissz

Been enjoying your firmware for a while now - Thanks.

I am however experiencing a major problem recently, I am using zpool,  but it seems the stats there show my D3 has not been hashing there for most of the time - though it has been on 24/7. Payout reduced to about 1/8 of normal.

Are you aware of any issue - I suspect I have spent 7/8 of the time mining on your pool.

I am now trying the latest Beta, hope it fixes the issue!!

Have you noticed a great increase in your earnings  

The issue seemed to start after the previous update (the one before the one you removed)

Or maybe others have noticed a problem on Zpool?

[crackfoo]

Hi Blissz

Been enjoying your firmware for a while now - Thanks.

I am however experiencing a major problem recently, I am using zpool,  but it seems the stats there show my D3 has not been hashing there for most of the time - though it has been on 24/7. Payout reduced to about 1/8 of normal.

Are you aware of any issue - I suspect I have spent 7/8 of the time mining on your pool.

I am now trying the latest Beta, hope it fixes the issue!!

Have you noticed a great increase in your earnings  

The issue seemed to start after the previous update (the one before the one you removed)

Or maybe others have noticed a problem on Zpool?

I'm using blissz's mod and pointed at my pool (zpool) and I haven't noticed this.... Here are my miners:

http://zpool.ca/?address=1LDQNsknrP6VUDdd1aqGWxoW9HBgYezEyZ

[JimmyFish]

Thank you kindly.

I just rebooted my D3, logged back into zpool and hash rate showed 493 GH/s!!

Maybe I have set diff level too high, I have been trying d=32000.

http://zpool.ca/?address=XsLW9WBh2qz9bHGDeFh4nH7oJPeuoccQqd

[crackfoo]

Thank you kindly.

I just rebooted my D3, logged back into zpool and hash rate showed 493 GH/s!!

Maybe I have set diff level too high, I have been trying d=32000.

http://zpool.ca/?address=XsLW9WBh2qz9bHGDeFh4nH7oJPeuoccQqd

That diff is waaaay to high for x11. Try something between 40-100 or so.

[JimmyFish]

I will give that a go - thanks