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

[blissz]

In fact, I also faced a much lower actual hashrate reported by the pool compared to what is shown in the Miner Status page. While Miner status shows >20.1GH/s average, the pool only showes ~17GH/s actual. It can be a luck factor, of course, but it was like that for several days in a row (and miner restart didn't change it). So I'm also looking forward to try v2.0 of your firmware...

If you do see a reduced hashrate on your pool I think this might help some of you:

• you're on an older firmware  which had a bug where it could not switch back to the main pool if it was down and it could hang for two hours in the dev pool.
• you only have one pool configured. If your main pool dies it will jump to the next alive pool (which is then the devfee pool)
• your main pool is not stable so it switches to the backup pool sometimes (which will cause that the hashrate is divided over two pools)
• you mine on a pool that scams you
• you have so many hardware errors / xxxx that kills your hashrate. (and have auto reboot disabled)
• you have an unstable internet connection: this will cause that you get the work packages late and you get a lot more then normal discarded shares, because they couldn't be delivered to the pool in time
• Same as the previous point, but then a bad connection on the pool operator side.
• For some other reason your d3 just doesn't like my firmware -> just flash back to stock ( I can't think of anything else then the above, but I am just a human...)

Ok so where to start: the kernel log will be really helpful if you experience problems. Furthermore you can run a ping on the pool for a few hours to see if you get lost packages. If you're still in doubt: just post your problem here (describe it good and post your kernel log) so myself or a fellow forum member can help you out.

[1714959406]

1714959406

[1714959406]

1714959406

[1714959406]

1714959406

[1714959406]

1714959406

[deezhere]

@Blissz

I really like what you have done modifiying the firmware but i have one suggestions, which i am pretty sure will ease the issue some ppl have when configuring theire miners regarding the dev fee.
I am all for it and i am pretty sure that others dont mind either that you get a fair share for your work.

I have 5 D3's myself and configuring those machines aint that easy, because each of them has different settings to be applied that the HW errors disappear.
The issue i have is, that after each reboot / configuration change (voltage, adresses, ....) you start mining on your dev pools (after some seconds), this makes it intense to check if my OWN settings are valid.

My suggestion is, please start mining your 1.5% fair share not at each and every reboot / configuration change, but once the miner has run for its 2 hours. So i am only asking you to change the first time you mine for yourself, after 2h you start with your rotation.

Thanks again.

He can't set it to 2 hrs before mining to his pool or people would just reboot their miners every 1 hr 59 min and only lose 13 min per day of mining (based on a 30 sec restart), versus him mining for 22 min a day (1 min 30 sec every 2 hrs like he stated). The breakeven point is about 33 minutes, so he could set it to 20 min and people could configure miners for some time without paying any excess fees.

22 min dev mining per day / 30 sec reboot = 44 restarts/day

24 hr/day / 44 restarts/day = 0.5454 hr/restart = approx 33 min/restart

If the reboot takes 90 sec, then he could set it to 1 hr 39 min, but ppl still might restart often just to spite the dev. So he sets a short amount of time before it mines to his pool.

Wouldn't it be easier to just edit the hosts file of the miner to trick it into thinking the devpool address is the same as the primary pool address?

My intention was not to circumvent anything, but just to explain why it's a short period of time before dev mines his pool. I fully support everything being done here, my miners are waaaay cooler and quieter, I'm very happy with the updates and responsiveness.

I'm leaving the dev fee enabled as well as I also want to support the efforts. Just simply pointing out that people timing reboots to stop the dev fee is silly when there are easier methods. I do hope that eventually blissz will give the option to either pay a 1 time fee upfront rather than a lifetime of dev fee mining. I also hope that this work will soon start to focus on isolating individual algos contained within X11 with the option to pick which of the 11 we would like to mine with so the profitability of these can be recovered. I know new algos won't happen but I don't see any reason we can't isolate and use only one of the 11 that these ASIC chips are already capable of.

[lashatatu]

reboot on high number asic failures does it reboot when u get high number of hw errors?

if it should do it then my miners doesnt do it, i noticed that it was rebooting yesterday but now it doesnt

[Friday13]

I'm running my two D3's on 400 Mhz, Voltage 2 and 20% Fanspeed.
So i have nearly 15 GH/s per miner and this is also shown in the antpool dashboard 30 GH/s +/- 3 GH/s so i have no Problems.
I also tried to run them on zpool over night and there i get max 20 GH/s, so i went back to antpool where i can use the full hashrate.

Go on with the good work blissz, love to see how this firmware and my D3's are getting better and better  

Greetings from Germany

[Monberg75]

I'm running my two D3's on 400 Mhz, Voltage 2 and 20% Fanspeed.
So i have nearly 15 GH/s per miner and this is also shown in the antpool dashboard 30 GH/s +/- 3 GH/s so i have no Problems.
I also tried to run them on zpool over night and there i get max 20 GH/s, so i went back to antpool where i can use the full hashrate.

Go on with the good work blissz, love to see how this firmware and my D3's are getting better and better  

Greetings from Germany

Take a look at this pool too.. I like the nice overview.

I have the same setup as you (400mhz at voltage 1 though) and get 1-1 on hashrate on the pool as in the mining software.. So it should be alright also.

I'm also VERY happy with this firmware.. 650W at the wall and fans running at below 2000RPM all the time

Greetings from Denmark.

[blissz]

Nice to read this guys! A beta version 2.0 is close. It adds quite some nice things which I will let you know soon

[microtechies]

Nice to read this guys! A beta version 2.0 is close. It adds quite some nice things which I will let you know soon

Can't wait !!! Any hints?

[CNumber]

Nice to read this guys! A beta version 2.0 is close. It adds quite some nice things which I will let you know soon

Thank you so much Blissz! Keep up the good work!

[Monberg75]

Nice to read this guys! A beta version 2.0 is close. It adds quite some nice things which I will let you know soon

Sounds awesome, can't wait to see the changes

Could you please give us som better information on the different settings in the doc/man file about the following.

Reboot at low hashrate: What does it mean, and when i the hashrate so low that a reboot is triggered
Reboot at HW Faults: When and how as with hashrate

Fan profiles, how are they controlled, what target temp is set at the different auto options?

I all works great, but I personally would love some clearance on it.

A 'Shutdown miner' option would be great, putting the miner to sleep before you turn it off, so you dont have to pull the plug with full load.

And the auto tune option would also be awesome, depending on different profiles for power/hashrate.

These are only suggestions.. You are doing a great job for us who bought a device we almost could trash when we got it. Now we can use it

Best regards:
Monberg75, Denmark

[funminer]

I'm running my two D3's on 400 Mhz, Voltage 2 and 20% Fanspeed.
So i have nearly 15 GH/s per miner and this is also shown in the antpool dashboard 30 GH/s +/- 3 GH/s so i have no Problems.
I also tried to run them on zpool over night and there i get max 20 GH/s, so i went back to antpool where i can use the full hashrate.

Go on with the good work blissz, love to see how this firmware and my D3's are getting better and better  

Greetings from Germany

Can confirm, have make the same test after people start saying that hashrate with blissz Firmware is less,

have monitored 2 Miners(24hours) with Blissz Firmware 16.5 & 16.8GH  on Prohasing from 14-18GH per miner.

On Zpool both Miners max hashrate was 32GH and the lowest was 10 , must say get a lot of disconnects 1-2 per hour,  Over 24 hours the Hashrate was 30% less, not shure that is the disconnects or when Zpool switch to other Coins what cause this. I try it with diff from 64 -92 and get not a big difference.
Granathash can´t test for me the pools are mosttime dead.
MiningPoolHub/Antpool - Stable near 15-20GH  Antpool middle 1h=16.7 & 17.05GH so blissz Firmware looks like work well.

i get Yesterday my last Ordered D3´s and take them down to 17.5GH testet on Zpool(12hours), same result as Blissz Firmware very instable Hashrates, last 6 hours runing on Antpool and hashrates from 16 - 23GH middle 1h= 17.7GH.
But looks like Bitmain change something, all miners i get before have 1000 of HW-Error when turn on the 1st time on frequency 537, but the new ones all start without any HW-Errors, only tune down for the Temp.
Now time to install Blissz Firmware and finetune 1100W on 17.5GH is still to much.

[Friday13]

Nice to read this guys! A beta version 2.0 is close. It adds quite some nice things which I will let you know soon

nice, and that before christmas is coming 

On Zpool both Miners max hashrate was 32GH and the lowest was 10 , must say get a lot of disconnects 1-2 per hour,  Over 24 hours the Hashrate was 30% less, not shure that is the disconnects or when Zpool switch to other Coins what cause this. I try it with diff from 64 -92 and get not a big difference.
Granathash can´t test for me the pools are mosttime dead.
MiningPoolHub/Antpool - Stable near 15-20GH  Antpool middle 1h=16.7 & 17.05GH so blissz Firmware looks like work well.

i dont tested other difficultys on zpool, but good to see that there are no differences and i saved much time with testing

so i stay on antpool untill nicehash is coming back online, so i can test what i get there.
but for now i am happy with my 9-10€ per day (daily payout) and hope that i can give some support to dash with mining this 

[mkmfins]

People. I keep wondering here.
I have already tested all methods to readjust this CHAIN # 1, but in all configurations it shows a high volume of HW error, I keep wondering.

Can I continue to use it this way and try to put a low temperature on this board?

It is because it will not be worth much I send it back to Bitmain, the loss of having bought it is already great, to send I will have to spend more money, in the end will only increase the loss ...

Could it be that with these errors, or trying to make a better readjustment possible, can I keep it going for a long time?

CHAIN #1 ~~~ HW ERRO :: https://i.imgur.com/MTAEmo6.png

WHAT DO YOU RECOMMEND TO ME

Can anyone explain or help me on this issue?

[hossamelsawy]

Nice to read this guys! A beta version 2.0 is close. It adds quite some nice things which I will let you know soon

I really appreciate your great work , my D3 is working now
thank you so much

[Monberg75]

People. I keep wondering here.
I have already tested all methods to readjust this CHAIN # 1, but in all configurations it shows a high volume of HW error, I keep wondering.

Can I continue to use it this way and try to put a low temperature on this board?

It is because it will not be worth much I send it back to Bitmain, the loss of having bought it is already great, to send I will have to spend more money, in the end will only increase the loss ...

Could it be that with these errors, or trying to make a better readjustment possible, can I keep it going for a long time?

CHAIN #1 ~~~ HW ERRO :: https://i.imgur.com/MTAEmo6.png

WHAT DO YOU RECOMMEND TO ME

Can anyone explain or help me on this issue?

That Chain is Faulty.. It should say 60 ASIC, and i doesn't.
I think you are missing some ASIC chips on the board.

Best regards: Monberg

[samshanna]

Guys BE CAREFUL updating Awesome Miner software.   If you are using profit switching it will automatically change the Bitcoin Address in each column that is NOT yours and probably the Awesome Miner Dev.  I made the mistake of mining 6 rigs x 2 days with his BTC address and just now caught it.   Makes me sick. 

[mkmfins]

People. I keep wondering here.
I have already tested all methods to readjust this CHAIN # 1, but in all configurations it shows a high volume of HW error, I keep wondering.

Can I continue to use it this way and try to put a low temperature on this board?

It is because it will not be worth much I send it back to Bitmain, the loss of having bought it is already great, to send I will have to spend more money, in the end will only increase the loss ...

Could it be that with these errors, or trying to make a better readjustment possible, can I keep it going for a long time?

CHAIN #1 ~~~ HW ERRO :: https://i.imgur.com/MTAEmo6.png

WHAT DO YOU RECOMMEND TO ME

Can anyone explain or help me on this issue?

That Chain is Faulty.. It should say 60 ASIC, and i doesn't.
I think you are missing some ASIC chips on the board.

Best regards: Monberg

Yes I know.
But my question is: Can I still use it anyway? Am I at risk of burning the whole machine?

Is that for me not worth sending back ..

[mkmfins]

Can anyone tell me if after having used the Blissz firmware, is it still possible to replace the defective board by sending it to the bitmain?

It's that with some faulty ones, but I used his firmware. 

[Festim]

I do not want this transfer to be done, how to stop it


https://scontent.fprx1-1.fna.fbcdn.net/v/t35.0-12/25346348_10209976642444678_352017190_o.jpg?oh=4e481e5d280911d8f0ea62cdcbb62fe2&oe=5A330042

[Friday13]

Can anyone tell me if after having used the Blissz firmware, is it still possible to replace the defective board by sending it to the bitmain?

It's that with some faulty ones, but I used his firmware. 

how could they find out? tehy just get the boards with the asic's and not the control board
or am i wrong?

[cryptonitro]

Can anyone tell me if after having used the Blissz firmware, is it still possible to replace the defective board by sending it to the bitmain?

It's that with some faulty ones, but I used his firmware.  

how could they find out? tehy just get the boards with the asic's and not the control board
or am i wrong?

right if you send only hashboard.

@festim dont mining on antpool ... darkside

@mkmfins ... yep probably burn some of ... lower frequency for long life ... worst default (way) of humanity -> "Ever want more". if everyone go to 400Mhz , we all get more profit cause difficulty lowering and watts to :s but it s a dream i think

And for some people asking if mods will come for L3+ or S9 , i m following this thread & dev since begining , and if i'm right : Blissz do not have those miners , so it's impossible to have some test to mod it unfortunalty for us ... i just connect one S9 it 's like ... euh ... plane reactor in my living  

and if some of you have break one or want to donate for the time to create mod , i 'm sure it's welcome