Pages:
Author

Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 65. (Read 125911 times)

newbie
Activity: 84
Merit: 0
Guys

5 of my D3 got issue with Chain 1 Chip set temperature TOO HIGH !

Any advice

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


You have the latest 29/11 installed?

YES

latest 29/11... after reboot still same...
newbie
Activity: 2
Merit: 0
Hello everyone.

Many thanks to Blissz for this firmware, It definitely rocks.

It's my configuration, pretty usual.

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

And this is my kernel log.

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

I have a question to topic starter, could you please explain line with pool supernova.cc, because I don't have this pool in my configuration ?


Thank you in advance.


newbie
Activity: 14
Merit: 0
Guys

5 of my D3 got issue with Chain 1 Chip set temperature TOO HIGH !

Any advice

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


I have the same issue.  I believe that chip is not correctly reporting the temp and it's not the actual temp.   I've also seen it go to 20 before just by changing the ASIC voltage.  (And not necessarily on that chip, they all kind of affect each other).   So if this chain or any of the others don't have HW errors then bump down their volts a level (just 1 chain) and see if that fixes the temp.  or if a chain is getting more than 1 or 2 HW errs a min, bump it's level up.

Hope that helps.
newbie
Activity: 2
Merit: 0
This Firmware ROCKS !!!!
I had some issues with high temps and a lot of missing asic chips, this firmware solved everything.
Great job !
sr. member
Activity: 336
Merit: 258
Guys

5 of my D3 got issue with Chain 1 Chip set temperature TOO HIGH !

Any advice




You have the latest 29/11 installed?
sr. member
Activity: 336
Merit: 258
Hi Blissz,

I have 9 D3, and in that my 5 D3 fails to switch to my Pool dug that it just runs on your Pool, this error seems to happen when my main Pool dies. This error is very serious, my D3s run for hours on your pool.
I restarted a machine and took a picture of a D3 machine, here





I (and we) want you to show your pool to the Miner Status, so that we can track, you charge and we agree, the issue you should put out Miner Status, do not hide them.

The info is still in the kernel log, but I don't mind showing it, so I will add something to optionally add it back in one of the next versions if you guys want to see it.
The pool priority bug is solved a long time ago, but I just found out that it doesn't always properly switch back when your pools are offline during the switch. So there is a chance now it will mine for quite a while on my pool before switching back to your pool. I will fix this asap. I am very sorry. Sad

edit: testing the new version now.
newbie
Activity: 50
Merit: 0
Guys

5 of my D3 got issue with Chain 1 Chip set temperature TOO HIGH !

Any advice

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


I have 2 D3s, the first has an August firmware and runs flawlessly, the 2nd came stock with 11/2 firmware and had the issue of one chain showing super high or super low temps.  It would alternate on reboot.  For me, installing the bitmain 11/20 firmware fixed the issue, all 3 chains are within a few degrees of each other now.  Side note, the 2nd D3 that came with newer firmware by default seems louder, and the fan speed % doesn't result in the same rpm as the 1st.  rpms on the 2nd are always higher when set to the same % as the 1st D3.

Next step after I run them both for a while on stock firmware to make sure there aren't other issues is to install Blissz firmware to save some on power and noise.
hta
jr. member
Activity: 261
Merit: 6
A happy family is but an earlier heaven!
Hi Blissz,

I have 9 D3, and in that my 5 D3 fails to switch to my Pool dug that it just runs on your Pool, this error seems to happen when my main Pool dies. This error is very serious, my D3s run for hours on your pool.
I restarted a machine and took a picture of a D3 machine, here





I (and we) want you to show your pool to the Miner Status, so that we can track, you charge and we agree, the issue you should put out Miner Status, do not hide them.
newbie
Activity: 10
Merit: 0
Running 29/11 on 3 D3's. No issues as of yet. I was able to get a seemingly dead card back up and running by cranking the voltage and reducing the Mhz rating.

Later,
  Stephen
hta
jr. member
Activity: 261
Merit: 6
A happy family is but an earlier heaven!
Hi Blissz,

I have 9 D3, and in that my 5 D3 fails to switch to my Pool dug that it just runs on your Pool, this error seems to happen when my main Pool dies. This error is very serious, my D3s run for hours on your pool.
I restarted a machine and took a picture of a D3 machine, here



member
Activity: 112
Merit: 10
bitshit keep selling l3 and s9 to do what they did in d3

no one should deal with this company or its pool

 Undecided
member
Activity: 72
Merit: 10
Sorry, guys, but I need help because of Bitmain support completely useless.

With stock firmware and stock settings (537Mhz, 13 voltage) for 1&2 chain temperature is below 70C but for 3rd it's higher than 100C.
I think heatsink didn't properly place on chips.
https://www.dropbox.com/s/u8i0pkn70ks20t4/chain_3_103.png?dl=0

I tried latest Bitmain firmware and Blissz firmware - still overheating.

I tried to run it with only one 3rd chain (overheating) and got this:

Chain#   ASIC#   Frequency   GH/S(RT)   HW   Temp(PCB)   Temp(Chip)   ASIC status
3           60                537             6517.26           421        53                83   oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
Fan#   Fan1   Fan2
Speed (r/min)   5,220   5,760

So, even alone, with fans on 100%  its 83C and had 421 error during 20min test.

How do you think, guys, should I send defective chain to Bitmain for repair?
Thanks
First of all, reduce the stock frequency from 537 to say 400  before you burn the 3rd chain!, then check whether the 3rd chain shows cooler temperatures, if yes, install Blissz's firmware to tune the frequency for each chain to balance their temperatures, especially the 3rd chain should be reduced way under the other two. I would advise you to choose the highest fan speed to cool the 3rd chain down, you can also use Blissz's "Performance" mode for the fan.
Don't forget though that this might invalidate your warranty! But it's better having a functioning miner than dealing with hassles of sending it back to Bitmain.
Good luck!

Good advice.id do this but this will invalidate warranty. just ,make a decision before you start Smiley
newbie
Activity: 84
Merit: 0
Guys

5 of my D3 got issue with Chain 1 Chip set temperature TOO HIGH !

Any advice

https://i.imgur.com/c3b19Ce.png
member
Activity: 72
Merit: 10
Hiya,

D3s are all different.I have 2 i have overclocked now fine running at 21GH, the third I cant OC. the temps of chips are already at 78 Degrees as standard.
They are all 19.3 GH machines.

Can anyone confirm its around 80 degrees for ASIC chips before they start to burn and produce lots of errors?

Did anyone manage to get L3 miners tweaked? Im running mine at 619 MH for 3 days perfect. on th pool it reads as over 700. not bad for a 504 machine!

newbie
Activity: 42
Merit: 0
Tuning each card I discovered that changing the voltage on one of them also affects the number of HW errors I get on the other ones. I don't know if frequency has the same effect. This made it quite tricky to get the three cards tuned independently. Have others observed this? What would this happen?


Exactly what happends with me. Please guys, if you get good results, please share the settings you are running, and what batch of Antminer D3 you got. I will share mine as soon as I get decent results!

Any opinion on how much HW errors is acceptable? Does HW error affect mining performance? I dont see any speed changes with a lot of HW errors. Can you just ignore it if temp and everything is allright?


Every D3 is different, so there are no general settings that fit everybody. Even in a single D3, the boards can be very different, and this is the reason Blissz added the individual board tuning feature.

You should just follow these instructions (courtesy of Blissz):
Start with frequency of 400 and a "Low" voltage setting.
Then increase the frequency until you start seeing HW errors.
Now either reduce the frequency if you want to keep the lowest power consumption, or increase the voltage incrementally until the HW errors disappear altogether, or are not more than 12 per hour.
You should also keep an eye on chip temperatures of each board (or chain), and try to keep them under 80 deg. C. using the fan automatic profiles or fixing the fan speed at a certain percentage. I prefer personally to keep it on automatic.

As a rule of thumb (at least in my 19 GHs D3 batch from mid October), the highest frequency I can use without HW errors on "Low" voltage is 438, some boards cannot tolerate higher frequencies, and they start producing too many errors already at a frequency of 425 or even 419!
 
newbie
Activity: 23
Merit: 0
The Noctua NF-F12 3000PWM fans was replaced with stock fans.
The needed power of Noctua fans are not reached.  Sad

I'm running EK Furious Vardar 3000s on mine without issue, at 100% they are about as noisey as stock fans at 40%, they do a great job on auto fan.
newbie
Activity: 24
Merit: 0
Please help.
What's happening here? I tried rebooting the miner but it's either super low like in the pic here or it's something crazy like 110. It was fine for a while and I made increases to the frequency slowly. Is it possible the sensor is busted? Should I just try to gauge the temp by looking at the other two boards?
https://gyazo.com/8213b69a893fd79de5ac2efd9bf39f85
copper member
Activity: 10
Merit: 0
Tuning each card I discovered that changing the voltage on one of them also affects the number of HW errors I get on the other ones. I don't know if frequency has the same effect. This made it quite tricky to get the three cards tuned independently. Have others observed this? What would this happen?


Exactly what happends with me. Please guys, if you get good results, please share the settings you are running, and what batch of Antminer D3 you got. I will share mine as soon as I get decent results!

Any opinion on how much HW errors is acceptable? Does HW error affect mining performance? I dont see any speed changes with a lot of HW errors. Can you just ignore it if temp and everything is allright?

member
Activity: 140
Merit: 17
Tuning each card I discovered that changing the voltage on one of them also affects the number of HW errors I get on the other ones. I don't know if frequency has the same effect. This made it quite tricky to get the three cards tuned independently. Have others observed this? What would this happen?
newbie
Activity: 42
Merit: 0
Sorry, guys, but I need help because of Bitmain support completely useless.

With stock firmware and stock settings (537Mhz, 13 voltage) for 1&2 chain temperature is below 70C but for 3rd it's higher than 100C.
I think heatsink didn't properly place on chips.
https://www.dropbox.com/s/u8i0pkn70ks20t4/chain_3_103.png?dl=0

I tried latest Bitmain firmware and Blissz firmware - still overheating.

I tried to run it with only one 3rd chain (overheating) and got this:

Chain#   ASIC#   Frequency   GH/S(RT)   HW   Temp(PCB)   Temp(Chip)   ASIC status
3           60                537             6517.26           421        53                83   oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo
Fan#   Fan1   Fan2
Speed (r/min)   5,220   5,760

So, even alone, with fans on 100%  its 83C and had 421 error during 20min test.

How do you think, guys, should I send defective chain to Bitmain for repair?
Thanks
First of all, reduce the stock frequency from 537 to say 400  before you burn the 3rd chain!, then check whether the 3rd chain shows cooler temperatures, if yes, install Blissz's firmware to tune the frequency for each chain to balance their temperatures, especially the 3rd chain should be reduced way under the other two. I would advise you to choose the highest fan speed to cool the 3rd chain down, you can also use Blissz's "Performance" mode for the fan.
Don't forget though that this might invalidate your warranty! But it's better having a functioning miner than dealing with hassles of sending it back to Bitmain.
Good luck!
Pages:
Jump to: