Bitcoin Forum
May 06, 2024, 01:07:11 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: What feature you want to see next?
auto tune each mining board - 45 (35.7%)
3 profile switch support (low noise, normal, high performance mode) - 13 (10.3%)
day / night speed schedule - 10 (7.9%)
pool balance / quota option - 9 (7.1%)
v2 configurable reboot on low hashrate / HW errors - 16 (12.7%)
DONE: cgminer v4.10 update - 4 (3.2%)
miner shutdown (+ on high temps) - 11 (8.7%)
better pool management - 9 (7.1%)
DONE:better awesome miner compatibility - 3 (2.4%)
move FAN settings to advanced page - 2 (1.6%)
<your idea> - 4 (3.2%)
Total Voters: 126

Pages: « 1 ... 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 [62] 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 ... 126 »
  Print  
Author Topic: Antminer D3 Blissz firmware (10/12 v1.12 update)  (Read 125816 times)
clyjr
Newbie
*
Offline Offline

Activity: 50
Merit: 0


View Profile
November 30, 2017, 12:40:36 PM
 #1221

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.
1714957631
Hero Member
*
Offline Offline

Posts: 1714957631

View Profile Personal Message (Offline)

Ignore
1714957631
Reply with quote  #2

1714957631
Report to moderator
1714957631
Hero Member
*
Offline Offline

Posts: 1714957631

View Profile Personal Message (Offline)

Ignore
1714957631
Reply with quote  #2

1714957631
Report to moderator
Activity + Trust + Earned Merit == The Most Recognized Users on Bitcointalk
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714957631
Hero Member
*
Offline Offline

Posts: 1714957631

View Profile Personal Message (Offline)

Ignore
1714957631
Reply with quote  #2

1714957631
Report to moderator
1714957631
Hero Member
*
Offline Offline

Posts: 1714957631

View Profile Personal Message (Offline)

Ignore
1714957631
Reply with quote  #2

1714957631
Report to moderator
blissz (OP)
Sr. Member
****
Offline Offline

Activity: 336
Merit: 258


View Profile
November 30, 2017, 12:43:58 PM
Last edit: November 30, 2017, 01:30:33 PM by blissz
 #1222

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.
blissz (OP)
Sr. Member
****
Offline Offline

Activity: 336
Merit: 258


View Profile
November 30, 2017, 12:45:11 PM
 #1223

Guys

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

Any advice




You have the latest 29/11 installed?
sebyk
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 30, 2017, 01:25:25 PM
 #1224

This Firmware ROCKS !!!!
I had some issues with high temps and a lot of missing asic chips, this firmware solved everything.
Great job !
Sfitzjava
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
November 30, 2017, 01:33:46 PM
 #1225

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.
pomivan
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 30, 2017, 01:44:16 PM
 #1226

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.


cscheat
Newbie
*
Offline Offline

Activity: 84
Merit: 0


View Profile
November 30, 2017, 02:12:25 PM
 #1227

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...
Monberg75
Copper Member
Newbie
*
Offline Offline

Activity: 109
Merit: 0


View Profile
November 30, 2017, 02:48:39 PM
 #1228

Why?

I don't have any problems, and are hashing 13-14GH at 650W, so I'm quite happy.
blissz (OP)
Sr. Member
****
Offline Offline

Activity: 336
Merit: 258


View Profile
November 30, 2017, 03:51:58 PM
Last edit: November 30, 2017, 07:48:23 PM by blissz
 #1229

*removed version due to stability problems*
silvioraof
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
November 30, 2017, 03:58:06 PM
 #1230

Hi good guys,
We are in the same boat..so let´s share our know... thanks for helping us Blissz
So, what pool do you use?
Does anyone tried to mine another coins in X11 algo?
streetcredit
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
November 30, 2017, 04:16:26 PM
 #1231

yea same the temp on chain 1 is 24 with voltage set to lowest and frequency 400
caliel
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
November 30, 2017, 04:27:34 PM
 #1232

v1.02 :: 30/11 :: recommended update

Download:
https://mega.nz/#!zl4CBQDQ!fMrZZc9wA76vEXpA4XhelVDGDgidOEvk4pSQ45Wg_xs

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down


know issues:

- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!
FYI, multiple miners are showing a HUGE difference between temps of board 1 versus boards 2 and 3.. like 40 degrees difference.  Looks like the logic you applied has put the number out of whack in the opposite direction..

blissz (OP)
Sr. Member
****
Offline Offline

Activity: 336
Merit: 258


View Profile
November 30, 2017, 04:56:43 PM
 #1233

v1.02 :: 30/11 :: recommended update

Download:
https://mega.nz/#!zl4CBQDQ!fMrZZc9wA76vEXpA4XhelVDGDgidOEvk4pSQ45Wg_xs

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down


know issues:

- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!
FYI, multiple miners are showing a HUGE difference between temps of board 1 versus boards 2 and 3.. like 40 degrees difference.  Looks like the logic you applied has put the number out of whack in the opposite direction..



You were ok on the previous firmware? I will pull back this update till I found out what's wrong.
ducdev
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
November 30, 2017, 05:08:30 PM
 #1234

Any solution for overheatting D3 ? I tried many ways but no hope.
COINKING84
Full Member
***
Offline Offline

Activity: 264
Merit: 100


View Profile
November 30, 2017, 05:22:29 PM
 #1235

v1.02 :: 30/11 :: recommended update

Download:
https://mega.nz/#!zl4CBQDQ!fMrZZc9wA76vEXpA4XhelVDGDgidOEvk4pSQ45Wg_xs

Changes 30/11:
- improved temperature sensor reading stability of all chains
- fixed an issue where the miner could hang mining the dev fee if your first pool is down


know issues:

- switching pools can sometimes cause the miner to wait for work for ~5 seconds. (improved from ~10 seconds)
- loosing network connection doesn't stop the mining boards properly (this is default bitmain behavior, but I don't like it, so it will be changed in the future)

happy mining!
FYI, multiple miners are showing a HUGE difference between temps of board 1 versus boards 2 and 3.. like 40 degrees difference.  Looks like the logic you applied has put the number out of whack in the opposite direction..



You were ok on the previous firmware? I will pull back this update till I found out what's wrong.

bliss how do i get this? i want to put this on d3
Mattithyahu
Copper Member
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
November 30, 2017, 05:47:41 PM
 #1236

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!
 

Thank you for useful information mate. I will try to tweak it as good as I can. How does the HW errors impact the mining?Do you or anyone here really know? Does it only affect the lifespan of the chain/board and not the performance? Maybe Blissz can answear, I never really had any HW errors before on my miners before I got the D3.
Renanxx1
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
November 30, 2017, 05:54:44 PM
 #1237

What about new algo?
SteganoS888
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
November 30, 2017, 06:07:19 PM
Last edit: November 30, 2017, 06:29:12 PM by SteganoS888
 #1238

I ask you to help with the solution of the problem:
http://i.da.am/6938.jpg
http://i.da.am/6940.jpg
[SPOILER][ 4054.090223] omap_i2c 4819c000.i2c: controller timed out
.................................
[ 5268.813681] omap_i2c 4819c000.i2c: controller timed out
[ 5269.821536] omap_i2c 4819c000.i2c: controller timed out
[ 5272.067710] omap_i2c 4819c000.i2c: controller timed out
[ 5273.073586] omap_i2c 4819c000.i2c: controller timed out
[ 5274.079488] omap_i2c 4819c000.i2c: controller timed out
[ 5275.087332] omap_i2c 4819c000.i2c: controller timed out
[ 5276.093248] omap_i2c 4819c000.i2c: controller timed out
[ 5277.099118] omap_i2c 4819c000.i2c: controller timed out
[ 5278.204859] omap_i2c 4819c000.i2c: controller timed out
Nov 30 17:39:13 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init chainid = 0
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create rx read thread for /dev/ttyO1 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: Start A New Asic Response.Chain Id:[0]
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create tx read thread for /dev/ttyO1 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init chainid = 1
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create rx read thread for /dev/ttyO2 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: Start A New Asic Response.Chain Id:[1]
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create tx read thread for /dev/ttyO2 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: tty_init chainid = 2
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create rx read thread for /dev/ttyO4 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: Start A New Asic Response.Chain Id:[2]
Nov 30 17:39:14 (none) local0.err cgminer[2489]: create tx read thread for /dev/ttyO4 ok
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: open device over
Nov 30 17:39:14 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:39:15 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:39:15 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:39:15 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:39:15 (none) local0.notice cgminer[2489]: every_chain_disable_PIC16F1704_dc_dc_new
Nov 30 17:39:26 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:39:26 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:39:35 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:39:44 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:39:56 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:39:56 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:40:05 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:06 (none) local0.notice cgminer[2489]: every_chain_enable_PIC16F1704_dc_dc_new
Nov 30 17:40:17 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:40:17 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:40:26 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:39 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:40:39 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:40:48 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:57 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:40:57 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:40:58 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:40:58 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:40:58 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:40:58 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:40:58 (none) local0.notice cgminer[2489]: recheck_asic_num DONE!
Nov 30 17:40:58 (none) local0.notice cgminer[2489]: every_chain_disable_PIC16F1704_dc_dc_new
Nov 30 17:41:09 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:41:09 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:41:18 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:41:31 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:41:31 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:41:40 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:41:52 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:41:52 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:42:01 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:42:02 (none) local0.notice cgminer[2489]: every_chain_enable_PIC16F1704_dc_dc_new
Nov 30 17:42:14 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:42:14 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:42:23 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:42:35 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:42:35 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:42:44 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:42:57 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:42:57 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:43:06 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:43:06 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:43:06 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:43:07 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:43:07 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:43:07 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:43:07 (none) local0.notice cgminer[2489]: recheck_asic_num DONE!
Nov 30 17:43:07 (none) local0.notice cgminer[2489]: every_chain_disable_PIC16F1704_dc_dc_new
Nov 30 17:43:19 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:43:19 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:43:28 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:43:40 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:43:40 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:43:49 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:44:01 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:44:01 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:44:11 (none) local0.err cgminer[2489]: disable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:44:12 (none) local0.notice cgminer[2489]: every_chain_enable_PIC16F1704_dc_dc_new
Nov 30 17:44:24 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:44:24 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:44:33 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:44:45 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:44:45 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:44:54 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:45:06 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:45:06 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:45:15 (none) local0.err cgminer[2489]: enable_PIC16F1704_dc_dc_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:45:16 (none) local0.notice cgminer[2489]: reset_all_hash_board
Nov 30 17:45:16 (none) local0.notice cgminer[2489]: check_every_chain_asic_number
Nov 30 17:45:16 (none) local0.warn cgminer[2489]: check_asic_reg: Chain0 has 0 ASICs
Nov 30 17:45:16 (none) local0.warn cgminer[2489]: check_asic_reg: Chain1 has 0 ASICs
Nov 30 17:45:17 (none) local0.warn cgminer[2489]: check_asic_reg: Chain2 has 0 ASICs
Nov 30 17:45:17 (none) local0.notice cgminer[2489]: recheck_asic_num DONE!
Nov 30 17:45:17 (none) local0.err cgminer[2489]: calculate_address_interval: temp_asic_number = -1, set addrInterval = '7'
Nov 30 17:45:17 (none) local0.notice cgminer[2489]: set_ticket_mask ticket_mask = 0x0000001d
Nov 30 17:45:17 (none) local0.notice cgminer[2489]: every_chain_get_PIC16F1704_freq_new
Nov 30 17:45:29 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:45:29 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:45:41 (none) local0.err cgminer[2489]:  --- get_PIC16F1704_freq_new failed!
Nov 30 17:45:53 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:45:53 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:46:06 (none) local0.err cgminer[2489]:  --- get_PIC16F1704_freq_new failed!
Nov 30 17:46:18 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new failed!
Nov 30 17:46:18 (none) local0.err cgminer[2489]: heart_beat_PIC16F1704_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0, read_back_data[5] = 0x0
Nov 30 17:46:31 (none) local0.err cgminer[2489]:  --- get_PIC16F1704_freq_new failed!
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.warn cgminer[2489]: error freq,set default freq(200M) instead
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: set_frequency: frequency = 0
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: software_set_address: chain 0 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:31 (none) local0.notice cgminer[2489]: Now Set
  • Chain Address
Nov 30 17:46:32 (none) local0.notice cgminer[2489]: software_set_address: chain 1 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:32 (none) local0.notice cgminer[2489]: Now Set [1] Chain Address
Nov 30 17:46:32 (none) local0.notice cgminer[2489]: software_set_address: chain 2 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:32 (none) local0.notice cgminer[2489]: Now Set [2] Chain Address
Nov 30 17:46:33 (none) local0.notice cgminer[2489]: software_set_address: chain 3 has 0 ASIC, and addrInterval is 7
Nov 30 17:46:33 (none) local0.notice cgminer[2489]: enable_read_temperature_from_asic: reg_value = 0x07007a61
Nov 30 17:46:33 (none) local0.notice cgminer[2489]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0
Nov 30 17:46:35 (none) local0.warn cgminer[2489]: set_temperature_offset_value
Nov 30 17:46:36 (none) local0.notice cgminer[2489]: set_temperature_offset_value: Chain0 Sensor0 temp offset : 00,
Nov 30 17:46:37 (none) local0.notice cgminer[2489]: set_temperature_offset_value: Chain1 Sensor0 temp offset : 00,
Nov 30 17:46:38 (none) local0.notice cgminer[2489]: set_temperature_offset_value: Chain2 Sensor0 temp offset : 00,
Nov 30 17:46:38 (none) local0.notice cgminer[2489]: frequency = '0'
Nov 30 17:46:43 (none) local0.err cgminer: Miner compile time: Tue Nov 29 12:03:56 CST 2017 type: Antminer D3 Blissz v1.01
Nov 30 17:46:43 (none) local0.warn cgminer: Started cgminer 4.10.0
Nov 30 17:46:43 (none) local0.warn cgminer[2712]: bitmain_DASH_init
Nov 30 17:46:43 (none) local0.warn cgminer[2712]: check_fan_speed OK
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detected at /sys/class/gpio/gpio51/value  chain 0
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detected at /sys/class/gpio/gpio48/value  chain 1
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detected at /sys/class/gpio/gpio47/value  chain 2
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: detect total chain num 3
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: i2c init ok
Nov 30 17:46:43 (none) local0.notice cgminer[2712]: check_whether_need_update_pic_program
Nov 30 17:46:52 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:00 (none) local0.err cgminer[2712]: jump_from_loader_to_app_PIC16F1704_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:12 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new failed!
Nov 30 17:47:12 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0
Nov 30 17:47:21 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:30 (none) local0.err cgminer[2712]: jump_from_loader_to_app_PIC16F1704_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:41 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new failed!
Nov 30 17:47:41 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0
Nov 30 17:47:50 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:47:59 (none) local0.err cgminer[2712]: jump_from_loader_to_app_PIC16F1704_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:10 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new failed!
Nov 30 17:48:10 (none) local0.err cgminer[2712]: get_PIC16F1704_software_version_new: read_back_data[0] = 0xff, read_back_data[1] = 0x0, read_back_data[2] = 0x0, read_back_data[3] = 0x0, read_back_data[4] = 0x0
Nov 30 17:48:10 (none) local0.notice cgminer[2712]: every_chain_reset_PIC16F1704_pic_new
Nov 30 17:48:19 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:29 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:38 (none) local0.err cgminer[2712]: reset_PIC16F1704_pic_new failed! read_back_data[0] = 0xff, read_back_data[1] = 0x00
Nov 30 17:48:38 (none) local0.notice cgminer[2712]: every_chain_jump_from_loader_to_app_PIC16F1704_new
Nov 30 17:48:43 (none) local0.warn cgminer[2712]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9995[/SPOILER]
piliff
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
November 30, 2017, 06:13:42 PM
 #1239

HW: 31 on CHain#2
Please, how to reduce HW's? 
Thank you

What for? Is your hashrate ok? If that, what problem with HW?
funminer
Full Member
***
Offline Offline

Activity: 218
Merit: 100


View Profile
November 30, 2017, 06:25:07 PM
 #1240

HW: 31 on CHain#2
Please, how to reduce HW's? 
Thank you

What for? Is your hashrate ok? If that, what problem with HW?

31 HW-Error´s is not much depend the time you have the miner runing.

most hw error´s come from not enough power, you have 2 Options
Lower frequency or higher Voltage on this chain.
Pages: « 1 ... 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 [62] 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 ... 126 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!