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

[hta]

Hi Blissz,

Did you fix it? The bug continues. Although Pool 1 has survived, the machine continues to run on your pool forever.

[blissz]

Hi Blissz,

Did you fix it? The bug continues. Although Pool 1 has survived, the machine continues to run on your pool forever.

It's fixed in the beta firmware, a few pages back, but you can also wait on the next stable firmware (probably today / tommmorow).

[mendo]

hello.

i'm rnning blissz firmware on a D3-504.

any suggstion or experience for voltage, trying to keep highest hashrate?

i want to keep mining DASH.

tnx

[evilfatone]

Great software Blissz, very useful for me I keep my miners in house in the cavity under the stairs, this software allows me to goto silent mode at night not disturbing the kids and performance during day to balance my overall daily hash rate at same time as save electric, great work

[Marvell2]

tried this software

chain 1 shows a low pcb temp but temps on chip

never go below 100 unless i really reduce the freqency  all the way below 350

fans are set to auth performace and my room is very cool

all the other chain temps are low even at 500+ freqncy and 8 - 9 voltage

[caymanguy]

what the over clock for d3 and l3

is there is the same firmware for l3

[clyjr]

blissz,
  FYI, I had the 1 chain high/low temp issue on my miner that had the stock 11/2 firmware, updated to stock 11/20 and it fixed the issue for several days.  Now I updated to blissz 11/29 and the issue is back.  I'm going to try the release before 11/29 and see if it has the issue also. 
Also, it would be nice if you could leave the links to the last several versions in the first post if possible. thanks

[clyjr]

blissz,
  FYI, I had the 1 chain high/low temp issue on my miner that had the stock 11/2 firmware, updated to stock 11/20 and it fixed the issue for several days.  Now I updated to blissz 11/29 and the issue is back.  I'm going to try the release before 11/29 and see if it has the issue also. 
Also, it would be nice if you could leave the links to the last several versions in the first post if possible. thanks

Followup, tried all the way back to 11/26 version and still has the temp issue.  I'm going to reflash the latest, and unplug it for a few minutes to test it out again...

[clyjr]

blissz,
  FYI, I had the 1 chain high/low temp issue on my miner that had the stock 11/2 firmware, updated to stock 11/20 and it fixed the issue for several days.  Now I updated to blissz 11/29 and the issue is back.  I'm going to try the release before 11/29 and see if it has the issue also. 
Also, it would be nice if you could leave the links to the last several versions in the first post if possible. thanks

Followup, tried all the way back to 11/26 version and still has the temp issue.  I'm going to reflash the latest, and unplug it for a few minutes to test it out again...

After reflashing 11/29, unplugging for several minutes now all temps are reading close to the same.  I did lose one board after changing voltage but it came back on reboot.  Playing around with the speed/voltage now.  Is there a guideline to how many HW errors over a time period is ok?

[micairvas]

There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?

[blissz]

There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?

The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well

[Marvell2]

so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...

then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,

flashed back to orig FW and tried the freqency trick again no luck

any tips ?

[blissz]

Hello. This firmware contain DevFee? Or not? If I will replace my original firmware to this, I will lose my warrantly? Thanks!

1,5% dev fee. Actually I don't think you loose warranty as the firmware is not visible in the mining boards. The controller you can flash back if you want before sending it back to bitmain, but I am not 100% sure on this. Therefore the warning on the topic start.

[blissz]

so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...

then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,

flashed back to orig FW and tried the freqency trick again no luck

any tips ?

Lower the frequency a bit more on that board. set it to 300 for example

[micairvas]

There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?

The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well

I updated Bitmain firmware on 1 D3 device which making mi problem with dead board. Why after flashing Bitmain FW I still have Blissz stamp on top left corner? I already spoke with bitmain i need to send them device on chio replacement? Will this void my warranty, why I cant just install Bitmain FW back?

[blissz]

There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?

The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well

I updated Bitmain firmware on 1 D3 device which making mi problem with dead board. Why after flashing Bitmain FW I still have Blissz stamp on top left corner? I already spoke with bitmain i need to send them device on chio replacement? Will this void my warranty, why I cant just install Bitmain FW back?

It's your browser cache. Just press ctrl + f5 on your browser and it looks like normal again

[jbmod]

Hi @all,

as probably some of you have exchanged fans - what kind of model / type would you guys recommend? How many RPM fans are you using to get the D3 quiet?
Mine are currently running at 2500-3000rpm with original fans. Any recommendations?

And thanks Blissz, for starting this and still working on an even better custom FW. :-)

I run it with the 120mm 2000rpm Scythe Slip Stream fans, but that only works if you run it at the lowest voltage setting. A relative silent 2500 to 3000rpm would be better. Anybody got suggestions?

Yes, I think I found one:
http://noctua.at/en/products/product-line-industrial/nf-f12-industrialppc-3000-pwm

This one looks quite promising actually. I just ordered some (they are not cheap!) and I'll give them a try over the weekend...

So...
New fans (noctua industrial line 3000rpm) installed on front and back side. Here are the results...

First of all I thought something is not working as I was only hearing the PSU. Then I remembered that my fans were previously set to 25% manual mode. With this setting the noctua fans are almost not noticeable. When running fans at 100% (3000rpm) they are comparable to the original bitmain fans running around 20%.

My one D3 runs now with the following settings:
Noctua fans front and back side, AUTO Performance Setting
Hashing at 16.5GH/s, fans running at 2300rpm (inlet) and 2400rpm (outlet) with custom voltage and MHZ set for each chain. Running for more than one hour now, keeping temp around 80°C each chain, while running at 18°C environment temp... So, regarding the noise - it's not completely silent of course but there is huge difference to the original fans.

But besides the fact that the noctua fans are quite pricy there are limits of course, they can't go higher than 3000rpm so high performance (>18GH/s) hashing seems unrealistic with those but if you want to get a more silent miner, the noctua fans are a good option. And no, I'm not getting payed to write that here. :-)

[Marvell2]

so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...

then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,

flashed back to orig FW and tried the freqency trick again no luck

any tips ?

Lower the frequency a bit more on that board. set it to 300 for example

300 still nothing on that chain 1 board

even as low as 137 still dead

really strange as this board worked at 400 on the stock FW

[micairvas]

There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?

The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well

I updated Bitmain firmware on 1 D3 device which making mi problem with dead board. Why after flashing Bitmain FW I still have Blissz stamp on top left corner? I already spoke with bitmain i need to send them device on chio replacement? Will this void my warranty, why I cant just install Bitmain FW back?

It's your browser cache. Just press ctrl + f5 on your browser and it looks like normal again

Huh, thx for tip .
Can I normally send D3 device back on warranty? They can not see that I used custom FW, after I flash Bitmain fw and void my warranty?

[jbmod]

so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...

then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,

flashed back to orig FW and tried the freqency trick again no luck

any tips ?

Lower the frequency a bit more on that board. set it to 300 for example

300 still nothing on that chain 1 board

even as low as 137 still dead

really strange as this board worked at 400 on the stock FW

what is your voltage setting? have you tried to send more juice to that chain, try 15 or 16 on the power settings...