Pages:
Author

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

member
Activity: 301
Merit: 10
I wonder my temps are all normal at 400 freqs and auto default fans.

Miner 1

https://gyazo.com/a13448c8f0a287427681ddab9d87705a

Dec 13 09:18:52 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain0 Sensor0 temp offset : -3,
Dec 13 09:18:52 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain1 Sensor0 temp offset : -3,
Dec 13 09:18:53 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain2 Sensor0 temp offset : -3,

Miner 2

https://gyazo.com/c2b49943212d2d4afc7fa5a3156bc652

Dec 13 09:18:52 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain0 Sensor0 temp offset : -10,
Dec 13 09:18:52 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain1 Sensor0 temp offset : -5,
Dec 13 09:18:53 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain2 Sensor0 temp offset : -6,

Hey Blissz, temperature sensor reading for my second miner is a little off after reboot.

newbie
Activity: 19
Merit: 0
Thanks for this great firmware. I'm now able to run it in my house without the terrible noise.  And yes, I should have known about the noise before, but now it's perfect.
member
Activity: 88
Merit: 10
Living the dream...

Hey Blissz thx for your brilliant work. I have a few D3's at my place, the noise used to be unbearable but now with ur firmware it's much quieter and less heat/power usage. Really looking forward to 2.0! will it have autotune function? thx.
member
Activity: 88
Merit: 10
Living the dream...
hi what is the best diff setting for the D3?

Depends where you are mining, your Inet connex, and ping.

I use 24-48 for big coin mining (Dash), and 8 to 12 for small coin (Happy, Onyx, Mue, Italy Imp 2.0 pool).

Happy Coin!

Thanks buddy! so with a lower ping do you increase or decrease the diff? my connection is quite good but im mining in Asia so the ping might be in the hundreds sometimes.
newbie
Activity: 199
Merit: 0
did someone as the magic skill to shutdown the 100% default fan on every reboot or setting change ?
this make me crazy

until you buy it, you do not. so I bought, at the end of November, an aluminum brick heater, and so noisy.  Undecided
sr. member
Activity: 336
Merit: 258
Hi, if I upgrade with this firmware is possible to revert to stock bitmain firmware? Is the ssh access to the controller (linux firmware) still available after the upgrade?

Cheers W_M

Yes you can always just flash back to the original firmware like you upgraded to the custom firmware. (see the guide in the start topic)
legendary
Activity: 1018
Merit: 1001
Hi, if I upgrade with this firmware is possible to revert to stock bitmain firmware? Is the ssh access to the controller (linux firmware) still available after the upgrade?

Cheers W_M
sr. member
Activity: 336
Merit: 258
I get frequent restarts during periods, I have "restart on low hashrate" and high ASIC failures disabled.  In kernel Log:

Dec 13 03:00:53 (none) local0.err cgminer[20481]: low hashrate detection trigger: 13760.256000 Gh/s
Dec 13 03:00:53 (none) local0.notice cgminer[20481]: set voltage = 1308.407463  real:165 mv
Dec 13 03:00:54 (none) local0.notice cgminer[20481]: set_PIC16F1704_voltage_new ok, voltage = 0x9b
Dec 13 03:00:54 (none) local0.notice cgminer[20481]: set_PIC16F1704_voltage_new ok, voltage = 0x9b
Dec 13 03:00:55 (none) local0.notice cgminer[20481]: set_PIC16F1704_voltage_new ok, voltage = 0xe1
Dec 13 03:00:55 (none) local0.err cgminer[20481]: cgminer time error total_secs = 1513134055.437114 last_total_secs = 1.000000


"low hashrate detection trigger: 13760.256000 Gh/s"  <----  Does it force the trigger even though I have it disabled? Maybe it could be too sensitive as well.  Maybe the pool or rapid coin switching causing a temporary hash drop which triggers the restart too easily?

It will not reboot if it detects a hashrate below this if you disabled this, but will just give a warning in the kernel log
full member
Activity: 155
Merit: 100
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.
  Undecided

if u changed volts then u should return it to stock setting which is 13v, just to make sure and you will be fine, either way i dont think that there will be a problem
full member
Activity: 345
Merit: 131
So two of my D3's have the "Scission of chips repair", issue number 6 on the link below.  Would you guys suggesting flashing back to the original firmware and sending it to bitmain for repair? 

https://support.bitmain.com/hc/en-us/articles/220872007-Possible-problems-for-Antminer-Troubleshooting-for-S7-S9-L3-
newbie
Activity: 7
Merit: 0
The new update causing my 4 miners to stop mining. Status page is showing no entries/stats. HW errors also picking up alot. Reverted back to 29/11
jr. member
Activity: 137
Merit: 2
What is:
Dec 13 02:51:47 (none) local0.warn cgminer[2336]: API running in IP access mode on port 4028 (15)
web interface for http://YOU_MINER_IP/cgi-bin/minerStatus.cgi
newbie
Activity: 56
Merit: 0
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 Cool

Still only this issue of time for a restart since the dev. pool was down a few days ago.

ge_new ok, voltage = 0xaf
Dec 13 02:51:41 (none) local0.err cgminer[2336]: cgminer time error total_secs = 1513133501.390351 last_total_secs = 1.000000
Dec 13 02:51:41 (none) local0.warn cgminer[2336]: Pool 0 stratum+tcp://dash.coinmine.pl:6099 alive, testing stability
Dec 13 02:51:41 (none) local0.warn cgminer[2336]: Switching to pool 0 stratum+tcp://dash.coinmine.pl:6099
Dec 13 02:51:47 (none) local0.warn cgminer[2336]: API running in IP access mode on port 4028 (15)
Dec 13 02:53:16 (none) local0.warn cgminer[2336]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9991
Dec 13 02:55:06 (none) local0.warn cgminer[2336]: Switching to pool 0 stratum+tcp://dash.coinmine.pl:6099


Used to be 2 minutes 30 seconds till It mined for me.

Now it is 4 minutes.

Just FYI

M









What is:

 Dec 13 02:51:47 (none) local0.warn cgminer[2336]: API running in IP access mode on port 4028 (15)
newbie
Activity: 30
Merit: 0
I get frequent restarts during periods, I have "restart on low hashrate" and high ASIC failures disabled.  In kernel Log:

Dec 13 03:00:53 (none) local0.err cgminer[20481]: low hashrate detection trigger: 13760.256000 Gh/s
Dec 13 03:00:53 (none) local0.notice cgminer[20481]: set voltage = 1308.407463  real:165 mv
Dec 13 03:00:54 (none) local0.notice cgminer[20481]: set_PIC16F1704_voltage_new ok, voltage = 0x9b
Dec 13 03:00:54 (none) local0.notice cgminer[20481]: set_PIC16F1704_voltage_new ok, voltage = 0x9b
Dec 13 03:00:55 (none) local0.notice cgminer[20481]: set_PIC16F1704_voltage_new ok, voltage = 0xe1
Dec 13 03:00:55 (none) local0.err cgminer[20481]: cgminer time error total_secs = 1513134055.437114 last_total_secs = 1.000000


"low hashrate detection trigger: 13760.256000 Gh/s"  <----  Does it force the trigger even though I have it disabled? Maybe it could be too sensitive as well.  Maybe the pool or rapid coin switching causing a temporary hash drop which triggers the restart too easily?
newbie
Activity: 56
Merit: 0
hi what is the best diff setting for the D3?

Depends where you are mining, your Inet connex, and ping.

I use 24-48 for big coin mining (Dash), and 8 to 12 for small coin (Happy, Onyx, Mue, Italy Imp 2.0 pool).

Happy Coin!
newbie
Activity: 56
Merit: 0
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 Cool

Still only this issue of time for a restart since the dev. pool was down a few days ago.

Dec 13 02:51:13 (none) local0.err cgminer: Miner compile time: Sat Dec 10 22:11:56 CST 2017 type: Antminer D3 Blissz v1.12
Dec 13 02:51:13 (none) local0.warn cgminer: Started cgminer 4.10.0
Dec 13 02:51:13 (none) local0.warn cgminer[2336]: bitmain_DASH_init
Dec 13 02:51:13 (none) local0.warn cgminer[2336]: check_fan_speed OK
Dec 13 02:51:13 (none) local0.notice cgminer[2336]: detected at /sys/class/gpio/gpio51/value  chain 0
Dec 13 02:51:13 (none) local0.notice cgminer[2336]: detected at /sys/class/gpio/gpio48/value  chain 1
Dec 13 02:51:13 (none) local0.notice cgminer[2336]: detected at /sys/class/gpio/gpio47/value  chain 2
Dec 13 02:51:13 (none) local0.notice cgminer[2336]: detect total chain num 3
Dec 13 02:51:13 (none) local0.notice cgminer[2336]: i2c init ok
Dec 13 02:51:13 (none) local0.notice cgminer[2336]: check_whether_need_update_pic_program
Dec 13 02:51:14 (none) local0.notice cgminer[2336]: reset_PIC16F1704_pic_new ok
Dec 13 02:51:15 (none) local0.notice cgminer[2336]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 13 02:51:16 (none) local0.notice cgminer[2336]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 13 02:51:17 (none) local0.notice cgminer[2336]: reset_PIC16F1704_pic_new ok
Dec 13 02:51:18 (none) local0.notice cgminer[2336]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 13 02:51:19 (none) local0.notice cgminer[2336]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 13 02:51:20 (none) local0.notice cgminer[2336]: reset_PIC16F1704_pic_new ok
Dec 13 02:51:21 (none) local0.notice cgminer[2336]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 13 02:51:22 (none) local0.notice cgminer[2336]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 13 02:51:22 (none) local0.notice cgminer[2336]: every_chain_reset_PIC16F1704_pic_new
Dec 13 02:51:24 (none) local0.notice cgminer[2336]: reset_PIC16F1704_pic_new ok
Dec 13 02:51:25 (none) local0.notice cgminer[2336]: reset_PIC16F1704_pic_new ok
Dec 13 02:51:27 (none) local0.notice cgminer[2336]: reset_PIC16F1704_pic_new ok
Dec 13 02:51:27 (none) local0.notice cgminer[2336]: every_chain_jump_from_loader_to_app_PIC16F1704_new
Dec 13 02:51:28 (none) local0.notice cgminer[2336]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 13 02:51:28 (none) local0.notice cgminer[2336]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 13 02:51:29 (none) local0.notice cgminer[2336]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 13 02:51:29 (none) local0.notice cgminer[2336]: every_chain_enable_PIC16F1704_dc_dc_new
Dec 13 02:51:29 (none) local0.notice cgminer[2336]: pic_heart_beat_func_new
Dec 13 02:51:29 (none) local0.notice cgminer[2336]: enable_PIC16F1704_dc_dc_new ok
Dec 13 02:51:29 (none) local0.notice cgminer[2336]: enable_PIC16F1704_dc_dc_new ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: enable_PIC16F1704_dc_dc_new ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: reset_all_hash_board
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: tty_init
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: tty_init chainid = 0
Dec 13 02:51:30 (none) local0.err cgminer[2336]: create rx read thread for /dev/ttyO1 ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: Start A New Asic Response.Chain Id:[0]
Dec 13 02:51:30 (none) local0.err cgminer[2336]: create tx read thread for /dev/ttyO1 ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: tty_init chainid = 1
Dec 13 02:51:30 (none) local0.err cgminer[2336]: create rx read thread for /dev/ttyO2 ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: Start A New Asic Response.Chain Id:[1]
Dec 13 02:51:30 (none) local0.err cgminer[2336]: create tx read thread for /dev/ttyO2 ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: tty_init chainid = 2
Dec 13 02:51:30 (none) local0.err cgminer[2336]: create rx read thread for /dev/ttyO4 ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: Start A New Asic Response.Chain Id:[2]
Dec 13 02:51:30 (none) local0.err cgminer[2336]: create tx read thread for /dev/ttyO4 ok
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: open device over
Dec 13 02:51:30 (none) local0.notice cgminer[2336]: check_every_chain_asic_number
Dec 13 02:51:30 (none) local0.warn cgminer[2336]: check_asic_reg: Chain0 has 60 ASICs
Dec 13 02:51:31 (none) local0.warn cgminer[2336]: check_asic_reg: Chain1 has 60 ASICs
Dec 13 02:51:31 (none) local0.warn cgminer[2336]: check_asic_reg: Chain2 has 60 ASICs
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: calculate_address_interval: temp_asic_number = 64, addrInterval = 1
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: calculate_address_interval: CHIP_OFFSET = 0x04000000, CORE_OFFSET = 0x00800000
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: set_ticket_mask ticket_mask = 0x0000001b
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: set_frequency: frequency = 425
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: set_frequency: frequency = 425
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: set_frequency: frequency = 412
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: set_frequency: frequency = 412
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: software_set_address: chain 0 has 60 ASIC, and addrInterval is 1
Dec 13 02:51:31 (none) local0.notice cgminer[2336]: Now Set
  • Chain Address
Dec 13 02:51:32 (none) local0.notice cgminer[2336]: software_set_address: chain 1 has 60 ASIC, and addrInterval is 1
Dec 13 02:51:32 (none) local0.notice cgminer[2336]: Now Set [1] Chain Address
Dec 13 02:51:33 (none) local0.notice cgminer[2336]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Dec 13 02:51:33 (none) local0.notice cgminer[2336]: Now Set [2] Chain Address
Dec 13 02:51:34 (none) local0.notice cgminer[2336]: software_set_address: chain 3 has 0 ASIC, and addrInterval is 1
Dec 13 02:51:34 (none) local0.notice cgminer[2336]: enable_read_temperature_from_asic: reg_value = 0x07007a61
Dec 13 02:51:34 (none) local0.notice cgminer[2336]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 13 02:51:35 (none) local0.warn cgminer[2336]: set_temperature_offset_value
Dec 13 02:51:35 (none) local0.notice cgminer[2336]: set_temperature_offset_value: Chain0 Sensor0 temp offset : -3,
Dec 13 02:51:36 (none) local0.notice cgminer[2336]: set_temperature_offset_value: Chain1 Sensor0 temp offset : -2,
Dec 13 02:51:36 (none) local0.notice cgminer[2336]: set_temperature_offset_value: Chain2 Sensor0 temp offset : -3,
Dec 13 02:51:36 (none) local0.notice cgminer[2336]: frequency = '531'
Dec 13 02:51:36 (none) local0.notice cgminer[2336]: dev.timeout = 568692 us
Dec 13 02:51:36 (none) local0.notice cgminer[2336]: open_core
Dec 13 02:51:39 (none) local0.err cgminer[2336]: low hashrate detection trigger: 13235.856000 Gh/s
Dec 13 02:51:39 (none) local0.notice cgminer[2336]: set voltage = 1399.777148  real:115 mv
Dec 13 02:51:40 (none) local0.notice cgminer[2336]: set_PIC16F1704_voltage_new ok, voltage = 0xb9
Dec 13 02:51:40 (none) local0.notice cgminer[2336]: set_PIC16F1704_voltage_new ok, voltage = 0xb9
Dec 13 02:51:41 (none) local0.notice cgminer[2336]: set_PIC16F1704_voltage_new ok, voltage = 0xaf
Dec 13 02:51:41 (none) local0.err cgminer[2336]: cgminer time error total_secs = 1513133501.390351 last_total_secs = 1.000000
Dec 13 02:51:41 (none) local0.warn cgminer[2336]: Pool 0 stratum+tcp://dash.coinmine.pl:6099 alive, testing stability
Dec 13 02:51:41 (none) local0.warn cgminer[2336]: Switching to pool 0 stratum+tcp://dash.coinmine.pl:6099
Dec 13 02:51:47 (none) local0.warn cgminer[2336]: API running in IP access mode on port 4028 (15)
Dec 13 02:53:16 (none) local0.warn cgminer[2336]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9991
Dec 13 02:55:06 (none) local0.warn cgminer[2336]: Switching to pool 0 stratum+tcp://dash.coinmine.pl:6099


Used to be 2 minutes 30 seconds till It mined for me.

Now it is 4 minutes.

Just FYI

M






newbie
Activity: 16
Merit: 0
after running my two d3's with 400Mhz since 2 Days, im getting tousands of HW in a few hours.
i rised the voltage already to 2 but its dont getting better.
but it dont affects the hashrate or the asics, so can i keep it running or should i rise the voltage further?

try to set default voltage (13) to test then lower 2 by 2 to see ... whats your ambiant temp ?
if you have less than 12~15 hw / hour it s ok

yeah i rised the voltage to 3 and see what happens, if needed i go further.
my ambient temp.... they stay in a basement and i think its somewhere between 15 an 20°C and i placed a little vent in front of them
the chiptemps are between 64 and 72°C

Yeah.
I think next year she can become a great miner, but it's complicated. I spent a lot of money on an investment that was great, but it fell so deep that it totally discouraged. And now these defective badges have discouraged me even more ...

Now I do not know if I get that bad shit or if I wrap it up for them to fix.

The problem is that they never reply to me in the support, and when they respond, I just send CTRL + C and CTRL + V, it's complicated.

I will try to test the reset button you said ... It's a very small hole that stays in the machine right?

do a factory reset and re-flash the firmware again
newbie
Activity: 30
Merit: 0
after running my two d3's with 400Mhz since 2 Days, im getting tousands of HW in a few hours.
i rised the voltage already to 2 but its dont getting better.
but it dont affects the hashrate or the asics, so can i keep it running or should i rise the voltage further?

try to set default voltage (13) to test then lower 2 by 2 to see ... whats your ambiant temp ?
if you have less than 12~15 hw / hour it s ok

yeah i rised the voltage to 3 and see what happens, if needed i go further.
my ambient temp.... they stay in a basement and i think its somewhere between 15 an 20°C and i placed a little vent in front of them
the chiptemps are between 64 and 72°C

Yeah.
I think next year she can become a great miner, but it's complicated. I spent a lot of money on an investment that was great, but it fell so deep that it totally discouraged. And now these defective badges have discouraged me even more ...

Now I do not know if I get that bad shit or if I wrap it up for them to fix.

The problem is that they never reply to me in the support, and when they respond, I just send CTRL + C and CTRL + V, it's complicated.

I will try to test the reset button you said ... It's a very small hole that stays in the machine right?
newbie
Activity: 56
Merit: 0
is it advised to increase voltage above 13? because i get hw errors on 13 on first 2 boards 3rd seems, running on 525

Hi,

When I am on OC (performance) mode, I go as high as 15 on one chain that gets hot faster than the other two.

It looks like this

1- 13V 531

2- 14V 544

3- 15V 525

Over 15 never helps for me, But I have not tried the over 500 Freq's, I do not know enough.

But I run one chain at 15v every day when the sun is out. As the above is my standard 20.5 G/H setting.

Works for me,

thanks Blissz!



Only problem is Just since dev pool outage caused this thing to take 4-5 min's to restart ever since, no complaints, just cannot wait for 2.0!


OH, And about the DEV POOL first on restart!

If someone were to go and restart every two hours to avoid paying developer's fee.... they would lose 5 minutes doing so,

So it would be a net loss to restart to avoid dev. fee. So, IT CAN BE AFTER EVERY 2 HRS, and not after every restart.


I am learning pools, playing with different pools, temps, frequencies, fan speeds, all in an effort to help make this better.

But it makes me restart more often now,

....later, i will be over it.

Thanks again Blissz, for existing!

Gin's on me~!

M

newbie
Activity: 50
Merit: 0
biggest addition I would like would be a max temperature setting for silent mode.  For some reason m D3s sometimes jump up in temp after rebooting, it seems to happen more when it starts mining the dev pool but that could be unrelated.  No other changes though and the temp jumps up to 83-85 and never goes back down unless I reboot...
Pages:
Jump to: