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

[Festim]

I do not want to tranfer automatic my money from account dash transfer to Jaxx every 24 hours. sorry for my english.
how to solve this help me.  

[1714956931]

1714956931

[1714956931]

1714956931

[1714956931]

1714956931

[heythorp]

Thanks for all the support, I am working hard on the background to improve things. As I also do respect all your opinions I decided the following for the next versions:

• My intention is not to discourage you to change / play with the settings, so the dev mining will start after 5 minutes instead of 2 minutes. This will give you time to grab a coffee / check your settings / correct it if you see a lot of HW errors / do multiple settings at once after a restart before it starts mining on the dev pool.
• The dev fee pools are shown again in the mining status overview (light grey colored) and also in the kernel log, so everybody can check / see what's going on. If you still have questions about it, please ask friendly in this topic.

Well done! Nice to see an honest person on the net .

Thanks

Just installed the 12/10 version. I was able to tweek my boards a bit better. I was able to get an extra G.

Out of my 2 machines I'm getting a total of 30.5G using under 1500w combined.

[caliel]

Thanks for all the support, I am working hard on the background to improve things. As I also do respect all your opinions I decided the following for the next versions:

• My intention is not to discourage you to change / play with the settings, so the dev mining will start after 5 minutes instead of 2 minutes. This will give you time to grab a coffee / check your settings / correct it if you see a lot of HW errors / do multiple settings at once after a restart before it starts mining on the dev pool.
• The dev fee pools are shown again in the mining status overview (light grey colored) and also in the kernel log, so everybody can check / see what's going on. If you still have questions about it, please ask friendly in this topic.

Did you remove the reboot code if the dev pools are down?  This is something that can happen from time to time and I would prefer not having my D3s spin off into reboots.

Thanks for your hard work!

[lhajnal]

Why do say everybody Mhs instead Ghs. This machine can mine with 17-20Ghs.

@Blissz
Swhat is your opinion from the expand of other algos? This will be possible?

[deathless]

Why do say everybody Mhs instead Ghs. This machine can mine with 17-20Ghs.

@Blissz
Swhat is your opinion from the expand of other algos? This will be possible?

No it wont happen The ASIC chips are made to mine x11 algos only it will never happen.

[BitcoinPappi]

Cannot seem to remove D3 Blissz firmware no matter how many times we click upgrade.  I would like to restore the Bitmain original firmware without the fee. Can you please advise on how to restore to the factory firmware since flashing and using the instructions in the post does not help

[SimpleCoin8]

Cannot seem to remove D3 Blissz firmware no matter how many times we click upgrade.  I would like to restore the Bitmain original firmware without the fee. Can you please advise on how to restore to the factory firmware since flashing and using the instructions in the post does not help

It probably is removed. It’s usually a browser cache issue. Hit refresh after you upgrade to the bitmain firmware.

[LiteMine]

@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.

[lashatatu]

Why do say everybody Mhs instead Ghs. This machine can mine with 17-20Ghs.

@Blissz
Swhat is your opinion from the expand of other algos? This will be possible?

No it wont happen The ASIC chips are made to mine x11 algos only it will never happen.

can you walk using your hands?
can you eat using your legs?
probably not, same goes for x11, it cant mine another algos. it will be like walking using your hands or eating using your legs, surely somebody can do eat using legs and walk using hands it but if it even possible it wont be as effective, if somebody really manages to mine another algos it will not be 17-20-ghs, most likely it will be 20khs, not kidding 20khz
stop asking this question

[martyshmoo]

@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.

Heard that be4?

[martyshmoo]

I do not want to tranfer automatic my money from account dash transfer to Jaxx every 24 hours. sorry for my english.
how to solve this help me.  

So, What do you want? Not clear.

[martyshmoo]

Thanks for all the support, I am working hard on the background to improve things. As I also do respect all your opinions I decided the following for the next versions:

• My intention is not to discourage you to change / play with the settings, so the dev mining will start after 5 minutes instead of 2 minutes. This will give you time to grab a coffee / check your settings / correct it if you see a lot of HW errors / do multiple settings at once after a restart before it starts mining on the dev pool.
• The dev fee pools are shown again in the mining status overview (light grey colored) and also in the kernel log, so everybody can check / see what's going on. If you still have questions about it, please ask friendly in this topic.

Hi Blissz,

After the smooth upgrade to 10/12:

I get this on restarts:

ec 12 05:56:01 (none) local0.notice cgminer[15007]: set_frequency: frequency = 512
Dec 12 05:56:01 (none) local0.notice cgminer[15007]: set_frequency: frequency = 519
Dec 12 05:56:01 (none) local0.notice cgminer[15007]: set_frequency: frequency = 487
Dec 12 05:56:01 (none) local0.notice cgminer[15007]: set_frequency: frequency = 487
Dec 12 05:56:01 (none) local0.notice cgminer[15007]: software_set_address: chain 0 has 60 ASIC, and addrInterval is 1
Dec 12 05:56:01 (none) local0.notice cgminer[15007]: Now Set

• Chain Address

Dec 12 05:56:02 (none) local0.notice cgminer[15007]: software_set_address: chain 1 has 60 ASIC, and addrInterval is 1
Dec 12 05:56:02 (none) local0.notice cgminer[15007]: Now Set [1] Chain Address
Dec 12 05:56:02 (none) local0.notice cgminer[15007]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Dec 12 05:56:02 (none) local0.notice cgminer[15007]: Now Set [2] Chain Address
Dec 12 05:56:03 (none) local0.notice cgminer[15007]: software_set_address: chain 3 has 0 ASIC, and addrInterval is 1
Dec 12 05:56:03 (none) local0.notice cgminer[15007]: enable_read_temperature_from_asic: reg_value = 0x07007a61
Dec 12 05:56:03 (none) local0.notice cgminer[15007]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 12 05:56:04 (none) local0.warn cgminer[15007]: set_temperature_offset_value
Dec 12 05:56:05 (none) local0.notice cgminer[15007]: set_temperature_offset_value: Chain0 Sensor0 temp offset : -3,
Dec 12 05:56:05 (none) local0.notice cgminer[15007]: set_temperature_offset_value: Chain1 Sensor0 temp offset : -2,
Dec 12 05:56:06 (none) local0.notice cgminer[15007]: set_temperature_offset_value: Chain2 Sensor0 temp offset : -3,
Dec 12 05:56:06 (none) local0.notice cgminer[15007]: frequency = '531'
Dec 12 05:56:06 (none) local0.notice cgminer[15007]: dev.timeout = 568692 us
Dec 12 05:56:06 (none) local0.notice cgminer[15007]: open_core
Dec 12 05:56:09 (none) local0.err cgminer[15007]: low hashrate detection trigger: 15920.784000 Gh/s
Dec 12 05:56:09 (none) local0.notice cgminer[15007]: set voltage = 1399.777148  real:115 mv
Dec 12 05:56:09 (none) local0.notice cgminer[15007]: set_PIC16F1704_voltage_new ok, voltage = 0x87
Dec 12 05:56:10 (none) local0.notice cgminer[15007]: set_PIC16F1704_voltage_new ok, voltage = 0x87
Dec 12 05:56:10 (none) local0.notice cgminer[15007]: set_PIC16F1704_voltage_new ok, voltage = 0x7d
Dec 12 05:56:11 (none) local0.err cgminer[15007]: cgminer time error total_secs = 1513058171.033079 last_total_secs = 1.000000
Dec 12 05:56:17 (none) local0.warn cgminer[15007]: API running in IP access mode on port 4028 (15)
Dec 12 05:57:45 (none) local0.warn cgminer[15007]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9991
Dec 12 05:59:35 (none) local0.warn cgminer[15007]: Switching to pool 0 stratum+tcp://italyiimp.com:3533


It now takes 5 (4:35) minutes to get to my pool and start mining on a restart.

Since your pool was down a couple days ago, It said WTF! no pool. I thought that was funny, but its not.

It started this api program, to find a way to mine dev. i think?

It does this at every restart since.

thanks for your help.

All other options working fine,

M

[tsojin]

@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.

Heard that be4?

The simple reason he doesn't mine at the end of the 2hour period is that it is incredibly easy to configured something that would restart the miner at 1hr 59mins and thus circumvent the dev pool fee.

[martyshmoo]

[/quote]

Hi Blissz,

After the smooth upgrade to 10/12:


It now takes 5 (4:35) minutes to get to my pool and start mining on a restart.

Since your pool was down a couple days ago, It said WTF! no pool. I thought that was funny, but its not.

It started this api program, to find a way to mine dev. i think?

It does this at every restart since.

thanks for your help.

All other options working fine,

M


[/quote]

what is this api ?

Time for me to reboot:

Dec 12 06:16:46 (none) local0.err cgminer: Miner compile time: Sat Dec 10 22:11:56 CST 2017 type: Antminer D3 Blissz v1.12
Dec 12 06:16:46 (none) local0.warn cgminer: Started cgminer 4.10.0
Dec 12 06:16:46 (none) local0.warn cgminer[13132]: bitmain_DASH_init
Dec 12 06:16:46 (none) local0.warn cgminer[13132]: check_fan_speed OK
Dec 12 06:16:46 (none) local0.notice cgminer[13132]: detected at /sys/class/gpio/gpio51/value  chain 0
Dec 12 06:16:46 (none) local0.notice cgminer[13132]: detected at /sys/class/gpio/gpio48/value  chain 1
Dec 12 06:16:46 (none) local0.notice cgminer[13132]: detected at /sys/class/gpio/gpio47/value  chain 2
Dec 12 06:16:46 (none) local0.notice cgminer[13132]: detect total chain num 3
Dec 12 06:16:46 (none) local0.notice cgminer[13132]: i2c init ok
Dec 12 06:16:46 (none) local0.notice cgminer[13132]: check_whether_need_update_pic_program
Dec 12 06:16:47 (none) local0.notice cgminer[13132]: reset_PIC16F1704_pic_new ok
Dec 12 06:16:48 (none) local0.notice cgminer[13132]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 12 06:16:49 (none) local0.notice cgminer[13132]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 12 06:16:51 (none) local0.notice cgminer[13132]: reset_PIC16F1704_pic_new ok
Dec 12 06:16:51 (none) local0.notice cgminer[13132]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 12 06:16:52 (none) local0.notice cgminer[13132]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 12 06:16:54 (none) local0.notice cgminer[13132]: reset_PIC16F1704_pic_new ok
Dec 12 06:16:54 (none) local0.notice cgminer[13132]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 12 06:16:55 (none) local0.notice cgminer[13132]: get_PIC16F1704_software_version_new ok, version = 0x81
Dec 12 06:16:55 (none) local0.notice cgminer[13132]: every_chain_reset_PIC16F1704_pic_new
Dec 12 06:16:57 (none) local0.notice cgminer[13132]: reset_PIC16F1704_pic_new ok
Dec 12 06:16:58 (none) local0.notice cgminer[13132]: reset_PIC16F1704_pic_new ok
Dec 12 06:17:00 (none) local0.notice cgminer[13132]: reset_PIC16F1704_pic_new ok
Dec 12 06:17:00 (none) local0.notice cgminer[13132]: every_chain_jump_from_loader_to_app_PIC16F1704_new
Dec 12 06:17:01 (none) local0.notice cgminer[13132]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 12 06:17:02 (none) local0.notice cgminer[13132]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 12 06:17:02 (none) local0.notice cgminer[13132]: jump_from_loader_to_app_PIC16F1704_new ok
Dec 12 06:17:02 (none) local0.notice cgminer[13132]: every_chain_enable_PIC16F1704_dc_dc_new
Dec 12 06:17:02 (none) local0.notice cgminer[13132]: pic_heart_beat_func_new
Dec 12 06:17:02 (none) local0.notice cgminer[13132]: enable_PIC16F1704_dc_dc_new ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: enable_PIC16F1704_dc_dc_new ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: enable_PIC16F1704_dc_dc_new ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: reset_all_hash_board
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: tty_init
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: tty_init chainid = 0
Dec 12 06:17:03 (none) local0.err cgminer[13132]: create rx read thread for /dev/ttyO1 ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: Start A New Asic Response.Chain Id:[0]
Dec 12 06:17:03 (none) local0.err cgminer[13132]: create tx read thread for /dev/ttyO1 ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: tty_init chainid = 1
Dec 12 06:17:03 (none) local0.err cgminer[13132]: create rx read thread for /dev/ttyO2 ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: Start A New Asic Response.Chain Id:[1]
Dec 12 06:17:03 (none) local0.err cgminer[13132]: create tx read thread for /dev/ttyO2 ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: tty_init chainid = 2
Dec 12 06:17:03 (none) local0.err cgminer[13132]: create rx read thread for /dev/ttyO4 ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: Start A New Asic Response.Chain Id:[2]
Dec 12 06:17:03 (none) local0.err cgminer[13132]: create tx read thread for /dev/ttyO4 ok
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: open device over
Dec 12 06:17:03 (none) local0.notice cgminer[13132]: check_every_chain_asic_number
Dec 12 06:17:04 (none) local0.warn cgminer[13132]: check_asic_reg: Chain0 has 60 ASICs
Dec 12 06:17:04 (none) local0.warn cgminer[13132]: check_asic_reg: Chain1 has 60 ASICs
Dec 12 06:17:04 (none) local0.warn cgminer[13132]: check_asic_reg: Chain2 has 60 ASICs
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: calculate_address_interval: temp_asic_number = 64, addrInterval = 1
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: calculate_address_interval: CHIP_OFFSET = 0x04000000, CORE_OFFSET = 0x00800000
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: set_ticket_mask ticket_mask = 0x0000001b
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: set_frequency: frequency = 512
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: set_frequency: frequency = 519
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: set_frequency: frequency = 487
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: set_frequency: frequency = 487
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: software_set_address: chain 0 has 60 ASIC, and addrInterval is 1
Dec 12 06:17:04 (none) local0.notice cgminer[13132]: Now Set

• Chain Address

Dec 12 06:17:05 (none) local0.notice cgminer[13132]: software_set_address: chain 1 has 60 ASIC, and addrInterval is 1
Dec 12 06:17:05 (none) local0.notice cgminer[13132]: Now Set [1] Chain Address
Dec 12 06:17:06 (none) local0.notice cgminer[13132]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Dec 12 06:17:06 (none) local0.notice cgminer[13132]: Now Set [2] Chain Address
Dec 12 06:17:07 (none) local0.notice cgminer[13132]: software_set_address: chain 3 has 0 ASIC, and addrInterval is 1
Dec 12 06:17:07 (none) local0.notice cgminer[13132]: enable_read_temperature_from_asic: reg_value = 0x07007a61
Dec 12 06:17:07 (none) local0.notice cgminer[13132]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0
Dec 12 06:17:08 (none) local0.warn cgminer[13132]: set_temperature_offset_value
Dec 12 06:17:08 (none) local0.notice cgminer[13132]: set_temperature_offset_value: Chain0 Sensor0 temp offset : -2,
Dec 12 06:17:09 (none) local0.notice cgminer[13132]: set_temperature_offset_value: Chain1 Sensor0 temp offset : -2,
Dec 12 06:17:09 (none) local0.notice cgminer[13132]: set_temperature_offset_value: Chain2 Sensor0 temp offset : -3,
Dec 12 06:17:09 (none) local0.notice cgminer[13132]: frequency = '531'
Dec 12 06:17:09 (none) local0.notice cgminer[13132]: dev.timeout = 568692 us
Dec 12 06:17:09 (none) local0.notice cgminer[13132]: open_core
Dec 12 06:17:13 (none) local0.err cgminer[13132]: low hashrate detection trigger: 15920.784000 Gh/s
Dec 12 06:17:13 (none) local0.notice cgminer[13132]: set voltage = 1399.777148  real:115 mv
Dec 12 06:17:13 (none) local0.notice cgminer[13132]: set_PIC16F1704_voltage_new ok, voltage = 0x87
Dec 12 06:17:13 (none) local0.notice cgminer[13132]: set_PIC16F1704_voltage_new ok, voltage = 0x87
Dec 12 06:17:14 (none) local0.notice cgminer[13132]: set_PIC16F1704_voltage_new ok, voltage = 0x7d
Dec 12 06:17:14 (none) local0.err cgminer[13132]: cgminer time error total_secs = 1513059434.574409 last_total_secs = 1.000000
Dec 12 06:17:20 (none) local0.warn cgminer[13132]: API running in IP access mode on port 4028 (16)
Dec 12 06:18:49 (none) local0.warn cgminer[13132]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9991
Dec 12 06:20:39 (none) local0.warn cgminer[13132]: Switching to pool 0 stratum+tcp://italyiimp.com:3533

It used to take two minutes, to start mioning, now it takes 4:50.

Thanks,

M

[lashatatu]

I do not want to tranfer automatic my money from account dash transfer to Jaxx every 24 hours. sorry for my english.
how to solve this help me.  

So, What do you want? Not clear.

just add your jaxx wallet to you payment options and you will receive coins on jaxx

[kristikun]

Wow wasted lots of time on blizs firmware  trying to utilize 23gh OC but in the end i found out Its not cut to OC d3  my hashrates we never even close to bitmains firmware even with 23gh on blissz firmware my share ratio was around 15gh becouse the fluctuations   tried lots of pools but in the end switched back to stock firmware where  19,3 stable   24/7  , SO my personal idea ppl who wants to OC dont use this firmware its waste of profit , undervolting is another thing  50%  less energry and i got same 15gh ratio with undervoloting as with OC !

[evilfatone]

blissz,
  I have one D3 that was running pretty well at about 79 degrees on each Temp(Chip) reading for around 15 hrs, then it rebooted this morning and two chains were above 80 (81, 86) when I woke up.  It's running on Auto Silent fan mode, my understanding was that the silent mode keeps it around 80 degrees, is that incorrect?  I usually monitor the D3s ever few hours just in case, but this reboot happened overnight so it worries me a little that I might wake up with a burnt board...

Silent mode will only let the fans go so high so it depends of ur settings if u have it running 17.5gh+  silent mode might not be enough to keep it cool, but if ur running it lower it should be enough to keep it cool depending on ambient temperature of room

[blissz]

Wow wasted lots of time on blizs firmware  trying to utilize 23gh OC but in the end i found out Its not cut to OC d3  my hashrates we never even close to bitmains firmware even with 23gh on blissz firmware my share ratio was around 15gh becouse the fluctuations   tried lots of pools but in the end switched back to stock firmware where  19,3 stable   24/7  , SO my personal idea ppl who wants to OC dont use this firmware its waste of profit , undervolting is another thing  50%  less energry and i got same 15gh ratio with undervoloting as with OC !

Thanks for this information. It seems to really differ for each d3 then. Some have had good results overclocking with this firmware.
FYI: I am working on a complete rebuild of the firmware. It is based of the latest official firmware and I made some nice improvements on stability (also when overclocking). It would be nice if you could  test the 2.0 versions which I will start releasing soon on your d3. Thanks

[blissz]

It now takes 5 (4:35) minutes to get to my pool and start mining on a restart.

Can you double check it in the miner status overview? To see if it's not mining on pool 0 after startup. It might be just the logging actually...

[Experimenter]

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...