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

Can't wait !!! Any hints?

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

Take a look at this pool too.. I like the nice overview.

I have the same setup as you (400mhz at voltage 1 though) and get 1-1 on hashrate on the pool as in the mining software.. So it should be alright also.

I'm also VERY happy with this firmware.. 650W at the wall and fans running at below 2000RPM all the time

Greetings from Denmark.

I'm running my two D3's on 400 Mhz, Voltage 2 and 20% Fanspeed.
So i have nearly 15 GH/s per miner and this is also shown in the antpool dashboard 30 GH/s +/- 3 GH/s so i have no Problems.
I also tried to run them on zpool over night and there i get max 20 GH/s, so i went back to antpool where i can use the full hashrate.

Go on with the good work blissz, love to see how this firmware and my D3's are getting better and better  

Greetings from Germany

reboot on high number asic failures does it reboot when u get high number of hw errors?

if it should do it then my miners doesnt do it, i noticed that it was rebooting yesterday but now it doesnt

I'm leaving the dev fee enabled as well as I also want to support the efforts. Just simply pointing out that people timing reboots to stop the dev fee is silly when there are easier methods. I do hope that eventually blissz will give the option to either pay a 1 time fee upfront rather than a lifetime of dev fee mining. I also hope that this work will soon start to focus on isolating individual algos contained within X11 with the option to pick which of the 11 we would like to mine with so the profitability of these can be recovered. I know new algos won't happen but I don't see any reason we can't isolate and use only one of the 11 that these ASIC chips are already capable of.

If you do see a reduced hashrate on your pool I think this might help some of you:

• you're on an older firmware  which had a bug where it could not switch back to the main pool if it was down and it could hang for two hours in the dev pool.
• you only have one pool configured. If your main pool dies it will jump to the next alive pool (which is then the devfee pool)
• your main pool is not stable so it switches to the backup pool sometimes (which will cause that the hashrate is divided over two pools)
• you mine on a pool that scams you
• you have so many hardware errors / xxxx that kills your hashrate. (and have auto reboot disabled)
• you have an unstable internet connection: this will cause that you get the work packages late and you get a lot more then normal discarded shares, because they couldn't be delivered to the pool in time
• Same as the previous point, but then a bad connection on the pool operator side.
• For some other reason your d3 just doesn't like my firmware -> just flash back to stock ( I can't think of anything else then the above, but I am just a human...)

Ok so where to start: the kernel log will be really helpful if you experience problems. Furthermore you can run a ping on the pool for a few hours to see if you get lost packages. If you're still in doubt: just post your problem here (describe it good and post your kernel log) so myself or a fellow forum member can help you out.

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

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

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

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

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 !

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

[/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

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.

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

So, What do you want? Not clear.

Heard that be4?

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

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.