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

[fecell]

alternative D3 web interface with BlissZ firmware.



Cool!

[zerp86]

i have some question.. i'm still newbie..
1. how much hw error per hour count normal. example under 100/hour?
2. if pool 1 down/dead.. then it will switch to next pool2.. but if pool1 back online/alive.. it's will change pool1 immediately or it will mining pool2 until restart or and count timer also before it switch to priority pool1 ?

[blissz]

alternative D3 web interface with BlissZ firmware.



Cool!

Looks really cool! I send you a PM

[BitAntonius]

hello there,
I am mining from zpool stratum+tcp://x11.mine.zpool.ca:3533 adress.
After than a few hours of working it says "dead". an switching to my second pool which is antpool.
I was never faced this kind of "dead" status when i was working with stock firmware. any comment?

Thanks
TG

It's not because of the firmware. Just the connection with the pool. It can work for a week without any "dead" status, and one day you get "dead" pool for several minutes or hours.

[sovereign120]

Is it possible to switch algorithms by modifying the firmware? Or is that just wishful thinking?

[solo__]

hello there,
I am mining from zpool stratum+tcp://x11.mine.zpool.ca:3533 adress.
After than a few hours of working it says "dead". an switching to my second pool which is antpool.
I was never faced this kind of "dead" status when i was working with stock firmware. any comment?

Thanks
TG

It's not because of the firmware. Just the connection with the pool. It can work for a week without any "dead" status, and one day you get "dead" pool for several minutes or hours.

Exactly you are right. but I haven't faced with it before and it gets some doubt at my head.
Just want to ask, anybody else who is mining with zapool has the same problem or not?

[maxisthemax]

alternative D3 web interface with BlissZ firmware.

https://forum.bits.media/uploads/monthly_2017_12/dashboard.PNG.a67e14a901be2d6219bbfc91cf08a690.PNG

Cool!

is this legit?

[Crypto Pants]

Hi Guys!

I have done a YouTube vid on the firmware and also done some profit vs power costs!

Please have a look and leave a like or comment if you have any feedback.

Thanks Blissz for this incredible firmware!

https://www.youtube.com/watch?v=Am6LSf8RxDI&feature=youtu.be

[thiec]

i have some question.. i'm still newbie..
1. how much hw error per hour count normal. example under 100/hour?
2. if pool 1 down/dead.. then it will switch to next pool2.. but if pool1 back online/alive.. it's will change pool1 immediately or it will mining pool2 until restart or and count timer also before it switch to priority pool1 ?

1. There is no normal hw error, as long you dont get xxx in your asic than its good. If you have 100/hour is 24hours your asic will have xxx
2. Normallnya its will back to pool1

[zerp86]

thank for your info

a few my d3 reach temp 126.. after a few reboot.. it go low.. sometime temp around 30 - 50..
it will go back to temp 126 if my d3 doing some auto reboot(sometime pool down/internet problem and reboot)
if i reboot and it change to temp 30.. its will affect to chip or hash board? i already got 2board burned because of this higher temp(before change to bliss fw)

for example
Temp  17  78  79

higher temp
126
78
80

after i upgrade to blissz fw.. i have to change freq down to 200 - 250 to make my temp just go around 85 below

[Wananavu99]

i have some question.. i'm still newbie..
1. how much hw error per hour count normal. example under 100/hour?
2. if pool 1 down/dead.. then it will switch to next pool2.. but if pool1 back online/alive.. it's will change pool1 immediately or it will mining pool2 until restart or and count timer also before it switch to priority pool1 ?

I wouldn't worry too much until you stop getting hashing power and your boards start showing xxxxx.  I ran one of mine that had over 1 million hw's for a whole day.  Reflashed with original software from bitmain and it fixed itself and then flashed with blissz's firmware.  

[zerp86]

i have some question.. i'm still newbie..
1. how much hw error per hour count normal. example under 100/hour?
2. if pool 1 down/dead.. then it will switch to next pool2.. but if pool1 back online/alive.. it's will change pool1 immediately or it will mining pool2 until restart or and count timer also before it switch to priority pool1 ?

I wouldn't worry too much until you stop getting hashing power and your boards start showing xxxxx.  I ran one of mine that had over 1 million hw's for a whole day.  Reflashed with original software from bitmain and it fixed itself and then flashed with blissz's firmware.  

wow nice..
before i just run also without taking any caution for this hw error..
just want to build some basic knowledge.. sometime learn from people much better than read a book..it make me dizzy

[UnluckyD3Miner]

Has anyone had to do a warranty return/repair? I have a hashboard that doesn't show up anymore on the status page.

This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead.

I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is?

[deathless]

Has anyone had to do a warranty return/repair? I have a hashboard that doesn't show up anymore on the status page.

This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead.

I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is?

Warranty return is almost pointless when it comes to bitmain it will take you six months to get it back

[blissz]

Hi Guys!

I have done a YouTube vid on the firmware and also done some profit vs power costs!

Please have a look and leave a like or comment if you have any feedback.

Thanks Blissz for this incredible firmware!

https://www.youtube.com/watch?v=Am6LSf8RxDI&feature=youtu.be

awesome video mate! Very useful for beginners. I will share it on the main page if you're ok with that. (and keep an eye on your BTC donation address )

[Crypto Pants]

Hi Guys!

I have done a YouTube vid on the firmware and also done some profit vs power costs!

Please have a look and leave a like or comment if you have any feedback.

Thanks Blissz for this incredible firmware!

https://www.youtube.com/watch?v=Am6LSf8RxDI&feature=youtu.be

awesome video mate! Very useful for beginners. I will share it on the main page if you're ok with that. (and keep an eye on your BTC donation address )

Absolutely, will be really glad if the video helps you get more users. This firmware really is the D3 savoir 

[UnluckyD3Miner]

Warranty return is almost pointless when it comes to bitmain it will take you six months to get it back

Wonderful.... 

Assuming I'd have to pay shipping back to china, it would take a while for the D3 to pay back the shipping costs even if they fixed the board immediately. I guess it would be worthwhile then to take it apart and see if there is any way I could fix it myself.

[sanitariu]

I suggest you try flash again with blissz firmware. Then return all voltage to normal default. I think it is 13 also the fan to high
or whatever the default is.
Then reboot and reflash with original firmware.
There is really no high temp protection currently even in the original firmware but at least fans there are
auto.
This protection is critical for me and as far as i know it will be in the next release.
Maybe on Christmas gift ?

[-droid-]

Has anyone had to do a warranty return/repair? I have a hashboard that doesn't show up anymore on the status page.

This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead.

I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is?

man ive got 2 units doing the same thing (one board on each unit gone and log shows 0 asics)

i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL

and the board I got sent back has missing o's ( 9 to be exact) so instead of like

oooooooo oooooooo
it shows
oooooooo oooo

great repair service  

.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN

[UnluckyD3Miner]

man ive got 2 units doing the same thing (one board on each unit gone and log shows 0 asics)

i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL

and the board I got sent back has missing o's ( 9 to be exact) so instead of like

oooooooo oooooooo
it shows
oooooooo oooo

great repair service  

.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN

  geeze...that sucks. Was it Bitmainwarranty.com that you sent it to? Also, did you go through Bitmain's ticket/support system and then they told you to ship it there, or you just paid to have the US facility fix it since shipping to and from China would take too long?