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

[dgwayne]

Looking into modify the antminer as well. I don't mind blissz taking fees. I have basic linux file modification skills. I just want to know where they are "hardcoded". I will figure it out sooner or later

https://ibb.co/fyXHkG

Seems to be hardcoded and a recompile to be performed in order to change some of the things that are in there. Not going to mess with it right now.

[1714941506]

1714941506

[david916]

Thanks for the update. To those who suggest the dev isn't responsive, I say, what do you call new updates every few days? It's one guy working on this, making our D3s more useful for us, whether our concern is noise, heat, or max hashrate. I expect he has a life and real job too. Blissz, thanks for the development. Awesome Miner integration is a priority for me, since that's my main administration tool. I think that people have a point that mining the devfee soon after a restart does increase the amount of devfee mining. However, I expect if you wait too long then a few people will restart their miners to prevent your fee. What about mining the devfee after 45 minutes as a happy medium? That would ensure that the miners were running and stable for owners, but probably not be worth it to them to constantly restart to avoid your fee.

I think you'll find the point is, the dev isn't responsive on this subject.  For instance, you've suggested something.  Don't expect a substantive response on this subject.  As a result, people are finding workarounds.  It would have been easier and more profitable to be responsive as it relates to the fees when people first brought forward their concerns.  But alas, people learn in different ways.

[may142012]

Blissz, can you focus on D3 but not L3+ nor S9? Those two are making good money, but D3 is different, please?

[mkmfins]

I have this difficulty still.
My CHAIN # 1 card does not show in ASIC status, but it is still working in the pool showing an increase that CHAIN 2 and 3 did not show.

When I turn it off completely the GH / S decreases a lot.
What can this be?

If I let her work this way, is there any chance of something worse going on?

If there's anything I can do to get her on, because it's no good for me to send her back to bitmain, because I'm going to pay a high freight rate and if I do, I'll have to pay the customs as well. In the end you will not give me any profit and only lose ... But than I've lost when buying that shit.


IMAGES: https://i.imgur.com/pFfLXlb.png
IMAGES: https://i.imgur.com/lGaRBNE.png

KERNEL LOG: https://ghostbin.com/paste/uxy4j

[mkmfins]

I have this difficulty still.
My CHAIN # 1 card does not show in ASIC status, but it is still working in the pool showing an increase that CHAIN 2 and 3 did not show.

When I turn it off completely the GH / S decreases a lot.
What can this be?

If I let her work this way, is there any chance of something worse going on?

If there's anything I can do to get her on, because it's no good for me to send her back to bitmain, because I'm going to pay a high freight rate and if I do, I'll have to pay the customs as well. In the end you will not give me any profit and only lose ... But than I've lost when buying that shit.


IMAGES: https://i.imgur.com/pFfLXlb.png
IMAGES: https://i.imgur.com/lGaRBNE.png

KERNEL LOG: https://ghostbin.com/paste/uxy4j

Now she appeared ...
IMAGE: https://i.imgur.com/G0bO35u.png

[caliel]

Dec 11 02:19:23 (none) local0.err cgminer[362]: cgminer time error total_secs = 1512958763.148932 last_total_secs = 1.000000
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Failed to resolve (?wrong URL) nicehash:80
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Dec 11 02:19:29 (none) local0.warn cgminer[362]: API running in IP access mode on port 4028 (15)
Dec 11 02:20:58 (none) local0.err cgminer[362]: No mining pools available, restarting...
Dec 11 02:20:58 (none) local0.warn cgminer[362]: Attempting to restart cgminer 4.10.0

I have a bad URL in my first loop's address (nicehash:80), the second address is correct, but I am getting constant reboots.  This wasn't happening until this very latest version of firmware

[EDIT] This is happening because both of the dev pools were down at the time.  Appears to be a bug introduced into the latest firmware.

[caliel]

Dec 11 02:19:23 (none) local0.err cgminer[362]: cgminer time error total_secs = 1512958763.148932 last_total_secs = 1.000000
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Failed to resolve (?wrong URL) nicehash:80
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Dec 11 02:19:29 (none) local0.warn cgminer[362]: API running in IP access mode on port 4028 (15)
Dec 11 02:20:58 (none) local0.err cgminer[362]: No mining pools available, restarting...
Dec 11 02:20:58 (none) local0.warn cgminer[362]: Attempting to restart cgminer 4.10.0

I have a bad URL in my first loop's address (nicehash:80), the second address is correct, but I am getting constant reboots.  This wasn't happening until this very latest version of firmware

Yeah, this is happening even when I have solid addresses in each pool... across 11 different D3s..

Dec 11 02:36:33 (none) local0.err cgminer[362]: cgminer time error total_secs = 1512959793.733065 last_total_secs = 1.000000
Dec 11 02:36:33 (none) local0.warn cgminer[362]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:36:33 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Dec 11 02:36:34 (none) local0.warn cgminer[362]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:36:34 (none) local0.warn cgminer[362]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Dec 11 02:36:39 (none) local0.warn cgminer[362]: API running in IP access mode on port 4028 (15)
Dec 11 02:38:09 (none) local0.err cgminer[362]: No mining pools available, restarting...
Dec 11 02:38:09 (none) local0.warn cgminer[362]: Attempting to restart cgminer 4.10.0

[EDIT] This is happening because both of the dev pools were down at the time.  Appears to be a bug introduced into the latest firmware.

[Bajula]

Chain#   ASIC#   Frequency   GH/S(RT)   HW   Temp(PCB)   Temp(Chip)   ASIC status
1   60   537   6583.55   6   53   73   oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2   60   537   6291.02   753   51   69   oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo  
3    where is chani 3  
  
 in other mines show 3 Chain#  

Try with lower frequency 537 is to much, don´t know why bitmain do it, but there are to much HW-Errors and the Miner get mostime to hot, too

When you run the Miner with 220-240V then try 506
with 120V try something around 450

can't help but throw this in again, doesn't matter if you are 240 or 120 it matters what your psu can do without strain. *IF* you are using an old server psu where at 220 it is producing 1200w and at 110 it is producing 900 w THAT will make a difference - but if you have a 1500w psu that can run on either, then 1500 is the max you are looking at.. the 220 vs 110 is only going to change the amps going *IN* to the psu (less heat on your cord or ability to use a smaller cord maybe less strain on the psu in the way of heat) but that will in no way affect what setting you can put on the miner itself, from the psu out 12v at whatever amps is going to be 12v at whatever amps.. doesn't matter AT ALL if it is 110 or 220 coming in. - thickness of the individual wires in the 6-pin makes a difference, the amps your psu can handle on it's 12v rail makes a difference.. but the miner doesn't care at all. not even the tiniest bit- if you have issues at 120v with 537 then either you have a miner with issues (plenty of them out there) or you need a better psu.

When i wrote it, i have the orig. Bitmain PSU in mind, and this is to small on 120V with frequency 537

I have strange problem
after 4 hours it gives me xxxxxxxxxxxxxxx again
so do I need to decrease the frequency as i have 537 with 220 v
please anyone help

yeah decrease the freq, or increase the voltage -on the chain with the firmware but is has NOTHING to do with incoming voltage. did you even read what you replied to? or do you just disagree? If the chain dies at a certain freq or beyond, do you really not see that you need to adjust something? At least you didn't say "I set myself on fire should I put it out?"  Wait you were messing with me right?

[rageprone]

Hello, my miner has been like this and after a few seconds everything goes to "X".
Can anyone tell me what to do?

https://i.imgur.com/KNPutSz.png

See if the information here helps : https://support.bitmain.com/hc/en-us/articles/220872007-Possible-problems-for-Antminer-Troubleshooting-for-S7-S9-L3-

[mkmfins]

Hello, my miner has been like this and after a few seconds everything goes to "X".
Can anyone tell me what to do?

https://i.imgur.com/KNPutSz.png

See if the information here helps : https://support.bitmain.com/hc/en-us/articles/220872007-Possible-problems-for-Antminer-Troubleshooting-for-S7-S9-L3-

This machine has the 3 defective plates.

There will be no other way to get her back to Bitmain, but their support is horrible in every way, they do not give a hand to this dung machine.

[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

[caliel]

v1.12 :: 10/12 :: recommended update

Download:
https://mega.nz/#!ylJX0LCQ!8JWryI0jDhgMvPdH2mrOvybkXCtrpYtQpxu0akdxU1s

Changes 10/12:
- Improved awesome miner / other mining managers compatibility (setting the priority was not working)
- fix kernel log window height (saves you double scrolling...)
- added permanent antbleed fix (prevent remote control of your miner by bitmain ) -> for details see http://www.antbleed.com/

happy mining!

* By the way I am very close to a first test version with some new features (including autotune), but let's fix the stable version first *

Blissz.. when both of the dev fee pools are down you go into constant reboot mode.  Is this intended?  Seems like a bug

[SimpleCoin8]

Doe it matter if I get hundreds of HW, but 1 reject?

[davemanet]

Hi I have a D3 on zpool with stock firmware.  My hash rate fluctates, is this normal?  Will this custom firmware help?
http://zpool.ca/?address=13tu1TeLmuDwJGgHnWPNxkH58QfZQUYng8

[blissz]

Blissz.. when both of the dev fee pools are down you go into constant reboot mode.  Is this intended?  Seems like a bug

Thanks for reporting, I will have a look at it.

[blissz]

Hi I have a D3 on zpool with stock firmware.  My hash rate fluctates, is this normal?  Will this custom firmware help?
http://zpool.ca/?address=13tu1TeLmuDwJGgHnWPNxkH58QfZQUYng8

This is normal as luck is the random factor how many shares you will find. The custom firmware helps for a lot things, but not for the fluctuating hashrate. If you want it a bit more stable you can try to decrease the difficulty manually by setting "d=8" as password.

[blissz]

Blissz, can you focus on D3 but not L3+ nor S9? Those two are making good money, but D3 is different, please?

Don't worry, main focus will be on D3 as indeed it needs the help the most

[tentenone1]

hi what is the best diff setting for the D3?

[Daimon888]

hi what is the best diff setting for the D3?

I would like to know that too.

[mine_x]

Blissz.. when both of the dev fee pools are down you go into constant reboot mode.  Is this intended?  Seems like a bug

Thanks for reporting, I will have a look at it.

Hi there,

I am running v1.1, thanks for your good job.
The only problem I found at the moment is - very late delay between the ASIC became "xxx xxxx" and miner restart. The restart has been executed only after 5 hours of the XXX XXX appearing on problematic chain

some inputs for analysis of such delayed restart:

1. The problematic chain is showing No. of ASICs = 60 (looks all healthy :-)
2. The problematic chain showing around 4000 HW errors and all XXXXXXXXXXXX
3. The true hashing speed is around 1/2 of normal one

All this information from miner management console. After auto- restart all correct... yet. I just lower frequency of the problematic chain a bit.

So on this status of clear needs to restart miner due to trouble with one chain (xxx , low hashrate) - the automatic restart has been done only after 5 hours (
Probably you should initiate restart of miner in 1 minute after the number of XXXXXXXXX has exceeded, let's say 10? I know some people are modifying stock firmware
in such way and it works well. From my practice if D3 chain is starting collect XXXXXXXXX, this chain very soon becomes obsolete and restart is a must.
Just IMHO.

Waiting for reply and patched version!

Good luck!