Pages:
Author

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

newbie
Activity: 31
Merit: 0
Hi,

Do you have support for awesome miner software?

I use this to profit switch between pools. but it cant seem to apply my Group of pools to the miner?

Jack


I have just realized you do, but it wont let me prioritise a specific pool, the priority button doesnt do anything? im stuck on my default pool
newbie
Activity: 31
Merit: 0
Hi,

Do you have support for awesome miner software?

I use this to profit switch between pools. but it cant seem to apply my Group of pools to the miner?

Jack
sr. member
Activity: 491
Merit: 250
I'll be running about 15 D3s on this firmware in the next couple of days, thanks!

Why you guys bought so many of D3s? You know its not that much profitable any more? Bitmain tricked us and bombarded us with these equipment that is not making much now a days. Stop buying Bitmain D3s guys.
newbie
Activity: 56
Merit: 0
Autotune would be very nice!!!

I've much problems to setup the boards. If i fix one board near 0 HW, than the next board will setup, the same board produces much HW errors.  Huh
full member
Activity: 224
Merit: 102
Too Many Miners Not Enough Electricity
I posted a thread about this but got no answer so ill ask it here.

What does a TON of HW errors and VERY high DiffA do to profits because thats whats happening to mine now.
sr. member
Activity: 336
Merit: 258
I don't know, but it is related with missing / undetected ASIC's. I also found out that there are certain frequency holes where the ASIC's are not happy at all.

i.e. at frequency 381Mhz I have lot's of problems, but at 400 Mhz it's fine again. The autotune algorithm that I work on, will cope with that as well.
BDM
newbie
Activity: 1
Merit: 0
Hi what does this kernel log mean with the Headers are not corret?? Where are the lost asics onboard one and two? Does anybady know?

Dec  9 13:50:21 (none) local0.err cgminer[375]: create rx read thread for /dev/ttyO1 ok
Dec  9 13:50:21 (none) local0.notice cgminer[375]: Start A New Asic Response.Chain Id:[0]
Dec  9 13:50:21 (none) local0.err cgminer[375]: create tx read thread for /dev/ttyO1 ok
Dec  9 13:50:21 (none) local0.notice cgminer[375]: tty_init chainid = 1
Dec  9 13:50:21 (none) local0.err cgminer[375]: create rx read thread for /dev/ttyO2 ok
Dec  9 13:50:21 (none) local0.notice cgminer[375]: Start A New Asic Response.Chain Id:[1]
Dec  9 13:50:21 (none) local0.err cgminer[375]: create tx read thread for /dev/ttyO2 ok
Dec  9 13:50:21 (none) local0.notice cgminer[375]: tty_init chainid = 2
Dec  9 13:50:21 (none) local0.err cgminer[375]: create rx read thread for /dev/ttyO4 ok
Dec  9 13:50:21 (none) local0.notice cgminer[375]: Start A New Asic Response.Chain Id:[2]
Dec  9 13:50:21 (none) local0.err cgminer[375]: create tx read thread for /dev/ttyO4 ok
Dec  9 13:50:21 (none) local0.notice cgminer[375]: open device over
Dec  9 13:50:21 (none) local0.notice cgminer[375]: check_every_chain_asic_number
Dec  9 13:50:21 (none) local0.warn cgminer[375]: check_asic_reg: Chain0 has 54 ASICs
Dec  9 13:50:22 (none) local0.warn cgminer[375]: check_asic_reg: Chain1 has 54 ASICs
Dec  9 13:50:22 (none) local0.warn cgminer[375]: check_asic_reg: Chain2 has 60 ASICs
Dec  9 13:50:22 (none) local0.notice cgminer[375]: every_chain_disable_PIC16F1704_dc_dc_new
Dec  9 13:50:24 (none) local0.notice cgminer[375]: every_chain_enable_PIC16F1704_dc_dc_new
Dec  9 13:50:24 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:24 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0xf0, Header2 = 0x00 rp = 541
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xf0, Header1 = 0x00, Header2 = 0x00 rp = 542
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x18 rp = 543
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x18, Header2 = 0xcd rp = 544
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x18, Header1 = 0xcd, Header2 = 0x00 rp = 545
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xcd, Header1 = 0x00, Header2 = 0x1e rp = 546
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x1e, Header2 = 0x76 rp = 547
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x1e, Header1 = 0x76, Header2 = 0x57 rp = 548
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x76, Header1 = 0x57, Header2 = 0x00 rp = 549
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x57, Header1 = 0x00, Header2 = 0xeb rp = 550
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0xeb, Header2 = 0x00 rp = 551
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xeb, Header1 = 0x00, Header2 = 0xec rp = 552
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0xec, Header2 = 0xac rp = 553
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xec, Header1 = 0xac, Header2 = 0x18 rp = 554
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xac, Header1 = 0x18, Header2 = 0x57 rp = 555
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x18, Header1 = 0x57, Header2 = 0x00 rp = 556
Dec  9 13:50:24 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:24 (none) local0.notice cgminer[375]: reset_all_hash_board
Dec  9 13:50:24 (none) local0.notice cgminer[375]: check_every_chain_asic_number
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xe0 rp = 487
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0xe0, Header2 = 0x00 rp = 488
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0xe0, Header1 = 0x00, Header2 = 0x00 rp = 489
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 490
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xaa rp = 491
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0xaa, Header2 = 0x55 rp = 492
Dec  9 13:50:24 (none) local0.warn cgminer[375]: check_asic_reg: Chain0 has 54 ASICs
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 487
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 488
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xaa rp = 489
Dec  9 13:50:24 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0xaa, Header2 = 0x55 rp = 490
Dec  9 13:50:25 (none) local0.warn cgminer[375]: check_asic_reg: Chain1 has 54 ASICs
Dec  9 13:50:25 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x57, Header1 = 0xff, Header2 = 0xaa rp = 557
Dec  9 13:50:25 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xff, Header1 = 0xaa, Header2 = 0x55 rp = 558
Dec  9 13:50:25 (none) local0.warn cgminer[375]: check_asic_reg: Chain2 has 60 ASICs
Dec  9 13:50:25 (none) local0.notice cgminer[375]: recheck_asic_num DONE!
Dec  9 13:50:25 (none) local0.notice cgminer[375]: every_chain_disable_PIC16F1704_dc_dc_new
Dec  9 13:50:26 (none) local0.notice cgminer[375]: every_chain_enable_PIC16F1704_dc_dc_new
Dec  9 13:50:26 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:27 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0xf0, Header2 = 0x00 rp = 1099
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xf0, Header1 = 0x00, Header2 = 0x1d rp = 1100
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x1d, Header2 = 0x08 rp = 1101
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x1d, Header1 = 0x08, Header2 = 0x00 rp = 1102
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x08, Header1 = 0x00, Header2 = 0x00 rp = 1103
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x9e rp = 1104
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x9e, Header2 = 0x6b rp = 1105
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x9e, Header1 = 0x6b, Header2 = 0x00 rp = 1106
Dec  9 13:50:27 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:27 (none) local0.notice cgminer[375]: reset_all_hash_board
Dec  9 13:50:27 (none) local0.notice cgminer[375]: check_every_chain_asic_number
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xe0 rp = 979
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0xe0, Header2 = 0x00 rp = 980
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0xe0, Header1 = 0x00, Header2 = 0x00 rp = 981
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 982
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xaa rp = 983
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0xaa, Header2 = 0x55 rp = 984
Dec  9 13:50:27 (none) local0.warn cgminer[375]: check_asic_reg: Chain0 has 54 ASICs
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 977
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 978
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xaa rp = 979
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0xaa, Header2 = 0x55 rp = 980
Dec  9 13:50:27 (none) local0.warn cgminer[375]: check_asic_reg: Chain1 has 54 ASICs
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x6b, Header1 = 0x00, Header2 = 0xf9 rp = 1107
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0xf9, Header2 = 0x9e rp = 1108
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xf9, Header1 = 0x9e, Header2 = 0x8c rp = 1109
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x9e, Header1 = 0x8c, Header2 = 0x98 rp = 1110
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x8c, Header1 = 0x98, Header2 = 0xaa rp = 1111
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x98, Header1 = 0xaa, Header2 = 0xf8 rp = 1112
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xaa, Header1 = 0xf8, Header2 = 0xaa rp = 1113
Dec  9 13:50:27 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xf8, Header1 = 0xaa, Header2 = 0x55 rp = 1114
Dec  9 13:50:28 (none) local0.warn cgminer[375]: check_asic_reg: Chain2 has 60 ASICs
Dec  9 13:50:28 (none) local0.notice cgminer[375]: recheck_asic_num DONE!
Dec  9 13:50:28 (none) local0.notice cgminer[375]: every_chain_disable_PIC16F1704_dc_dc_new
Dec  9 13:50:29 (none) local0.notice cgminer[375]: every_chain_enable_PIC16F1704_dc_dc_new
Dec  9 13:50:29 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:29 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0xf0, Header2 = 0x00 rp = 1655
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xf0, Header1 = 0x00, Header2 = 0x00 rp = 1656
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x18 rp = 1657
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x18, Header2 = 0x5d rp = 1658
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x18, Header1 = 0x5d, Header2 = 0x00 rp = 1659
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x5d, Header1 = 0x00, Header2 = 0x9e rp = 1660
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x9e, Header2 = 0xf6 rp = 1661
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x9e, Header1 = 0xf6, Header2 = 0x9c rp = 1662
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xf6, Header1 = 0x9c, Header2 = 0xfe rp = 1663
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x9c, Header1 = 0xfe, Header2 = 0x9e rp = 1664
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xfe, Header1 = 0x9e, Header2 = 0xac rp = 1665
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x9e, Header1 = 0xac, Header2 = 0x98 rp = 1666
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xac, Header1 = 0x98, Header2 = 0xd5 rp = 1667
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x98, Header1 = 0xd5, Header2 = 0x00 rp = 1668
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xd5, Header1 = 0x00, Header2 = 0x08 rp = 1669
Dec  9 13:50:29 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x00, Header1 = 0x08, Header2 = 0xd4 rp = 1670
Dec  9 13:50:29 (none) local0.notice cgminer[375]: enable_PIC16F1704_dc_dc_new ok
Dec  9 13:50:29 (none) local0.notice cgminer[375]: reset_all_hash_board
Dec  9 13:50:30 (none) local0.notice cgminer[375]: check_every_chain_asic_number
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xe0 rp = 1471
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0xe0, Header2 = 0x00 rp = 1472
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0xe0, Header1 = 0x00, Header2 = 0x00 rp = 1473
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 1474
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xaa rp = 1475
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0xaa, Header2 = 0x55 rp = 1476
Dec  9 13:50:30 (none) local0.warn cgminer[375]: check_asic_reg: Chain0 has 54 ASICs
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 1467
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 1468
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0xaa rp = 1469
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 1 Headers are not corret! Header0 = 0x00, Header1 = 0xaa, Header2 = 0x55 rp = 1470
Dec  9 13:50:30 (none) local0.warn cgminer[375]: check_asic_reg: Chain1 has 54 ASICs
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0x08, Header1 = 0xd4, Header2 = 0xd5 rp = 1671
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xd4, Header1 = 0xd5, Header2 = 0xff rp = 1672
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xd5, Header1 = 0xff, Header2 = 0xaa rp = 1673
Dec  9 13:50:30 (none) local0.err cgminer[375]: get_asic_response: 2 Headers are not corret! Header0 = 0xff, Header1 = 0xaa, Header2 = 0x55 rp = 1674
Dec  9 13:50:30 (none) local0.warn cgminer[375]: check_asic_reg: Chain2 has 60 ASICs
Dec  9 13:50:30 (none) local0.notice cgminer[375]: recheck_asic_num DONE!
Dec  9 13:50:30 (none) local0.notice cgminer[375]: calculate_address_interval: temp_asic_number = 64, addrInterval = 1
Dec  9 13:50:30 (none) local0.notice cgminer[375]: calculate_address_interval: CHIP_OFFSET = 0x04000000, CORE_OFFSET = 0x00800000
Dec  9 13:50:30 (none) local0.notice cgminer[375]: set_ticket_mask ticket_mask = 0x0000001b
Dec  9 13:50:31 (none) local0.notice cgminer[375]: every_chain_get_PIC16F1704_freq_new
Dec  9 13:50:32 (none) local0.notice cgminer[375]: set_frequency: frequency = 494
Dec  9 13:50:32 (none) local0.notice cgminer[375]: set_frequency: frequency = 494
Dec  9 13:50:32 (none) local0.notice cgminer[375]: set_frequency: frequency = 537
Dec  9 13:50:32 (none) local0.notice cgminer[375]: set_frequency: frequency = 537
Dec  9 13:50:32 (none) local0.notice cgminer[375]: software_set_address: chain 0 has 54 ASIC, and addrInterval is 1
Dec  9 13:50:32 (none) local0.notice cgminer[375]: Now Set
  • Chain Address
Dec  9 13:50:33 (none) local0.notice cgminer[375]: software_set_address: chain 1 has 54 ASIC, and addrInterval is 1
Dec  9 13:50:33 (none) local0.notice cgminer[375]: Now Set [1] Chain Address
Dec  9 13:50:34 (none) local0.notice cgminer[375]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Dec  9 13:50:34 (none) local0.notice cgminer[375]: Now Set [2] Chain Address
Dec  9 13:50:35 (none) local0.notice cgminer[375]: software_set_address: chain 3 has 0 ASIC, and addrInterval is 1
Dec  9 13:50:35 (none) local0.notice cgminer[375]: enable_read_temperature_from_asic: reg_value = 0x07007a61
Dec  9 13:50:35 (none) local0.notice cgminer[375]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0
Dec  9 13:50:36 (none) local0.warn cgminer[375]: set_temperature_offset_value
Dec  9 13:50:36 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain0 Sensor0 temp offset : -3,
Dec  9 13:50:37 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain1 Sensor0 temp offset : -3,
Dec  9 13:50:37 (none) local0.notice cgminer[375]: set_temperature_offset_value: Chain2 Sensor0 temp offset : -3,
Dec  9 13:50:37 (none) local0.notice cgminer[375]: frequency = '537'
Dec  9 13:50:37 (none) local0.notice cgminer[375]: dev.timeout = 562356 us
Dec  9 13:50:37 (none) local0.notice cgminer[375]: open_core
Dec  9 13:50:40 (none) local0.err cgminer[375]: low hashrate detection trigger: 15994.200000 Gh/s
Dec  9 13:50:40 (none) local0.notice cgminer[375]: set voltage = 1381.503211  real:125 mv
Dec  9 13:50:41 (none) local0.notice cgminer[375]: set_PIC16F1704_voltage_new ok, voltage = 0x73
Dec  9 13:50:41 (none) local0.notice cgminer[375]: set_PIC16F1704_voltage_new ok, voltage = 0x73
Dec  9 13:50:42 (none) local0.notice cgminer[375]: set_PIC16F1704_voltage_new ok, voltage = 0x7d
Dec  9 13:50:42 (none) local0.err cgminer[375]: cgminer time error total_secs = 1512827442.321036 last_total_secs = 1.000000
Dec  9 13:50:42 (none) local0.err cgminer[375]: WTF No pool 3 found!
Dec  9 13:50:42 (none) local0.err cgminer[375]: WTF No pool 3 found!
Dec  9 13:50:43 (none) local0.err cgminer[375]: D1 0: work 7f not find error
Dec  9 13:50:43 (none) local0.err cgminer[375]: D1 0: work 7f not find error
Dec  9 13:50:43 (none) local0.err cgminer[375]: D1 0: work 7f not find error
sr. member
Activity: 336
Merit: 258
Worse than ever. 20 minutes of mining then WHAM.. stuck on Dev Fee mining?

How many pools you have configured? Please post a screenshot of the miner status window and post your kernel log.
newbie
Activity: 5
Merit: 0
Worse than ever. 20 minutes of mining then WHAM.. stuck on Dev Fee mining?
newbie
Activity: 67
Merit: 0
Hi Blissz,

I think there is a bug in your latest firmware 08/12 v1.11. On the Miner Status page, the chains are numbered 2, 3, 4, but on the Miner Advanced Configuration page, they are numbered 1, 2, 3. Any changes made to chain 2 on the Miner Configuration page will be applied to chain 3 on the Miner Status page, and any changes to chain 3 will be applied to chain 3 and 4. Changes to chain 1 on the Miner Configuration page doesn't seem to affect anything.

As an experiment, I set the global frequency at 450M, chain 1 at 444M, chain 2 at 438M and chain 3 at 425M. Below is an excerpt from kernel log:

Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 444
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 438
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 0 has 0 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 1 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: Now Set [1] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [2] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 3 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [3] Chain Address

On the Miner Status page, it shows that the frequency of chain 2, 3, and 4 are 438M, 425M, and 425M respectively.

check the connections on the hashboard. mine had 1,2, and 4. bitmain connected hashboard 3 wrong, into port 4. maybe port 1 is empty?
newbie
Activity: 32
Merit: 0
Hi Blissz,

I think there is a bug in your latest firmware 08/12 v1.11. On the Miner Status page, the chains are numbered 2, 3, 4, but on the Miner Advanced Configuration page, they are numbered 1, 2, 3. Any changes made to chain 2 on the Miner Configuration page will be applied to chain 3 on the Miner Status page, and any changes to chain 3 will be applied to chain 3 and 4. Changes to chain 1 on the Miner Configuration page doesn't seem to affect anything.

As an experiment, I set the global frequency at 450M, chain 1 at 444M, chain 2 at 438M and chain 3 at 425M. Below is an excerpt from kernel log:

Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 444
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 438
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 0 has 0 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 1 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: Now Set [1] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [2] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 3 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [3] Chain Address

On the Miner Status page, it shows that the frequency of chain 2, 3, and 4 are 438M, 425M, and 425M respectively.
newbie
Activity: 33
Merit: 0
Tell them you aren’t scamming us Blissz. Say it ain’t so.

Most of you know better, but let's try to be helpful Smiley
Look at the kernel log / connect whattomine / look at your mining stats and you will all see how it works:

every two hours it will mine exactly 1 minute and 50 seconds on one of the dev pools I hardcoded. This goes automatically / independent of the pools you have configured yourself. After that it will mine 2 hours on your pools again etc....

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.

edit: added the last line, which is a possibility of course :')


Thanks for the thorough explanation. Great job on the firmware buddy. I appreciate the work you have done to improve our space heaters’ efficiency.
sr. member
Activity: 336
Merit: 258
Tell them you aren’t scamming us Blissz. Say it ain’t so.

Most of you know better, but let's try to be helpful Smiley
Look at the kernel log / connect whattomine / look at your mining stats and you will all see how it works:

every two hours it will mine exactly 1 minute and 50 seconds on one of the dev pools I hardcoded. This goes automatically / independent of the pools you have configured yourself. After that it will mine 2 hours on your pools again etc....

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.

edit: added the last line, which is a possibility of course :')
sr. member
Activity: 336
Merit: 258
Hi Blissz, does your firmware have a protection to shut down the miner if my internet gets disconnected? You know the hashboards keep running when there is no internet connection.

It does not shutdown directly. It will try to solve the current block. It is just operating as normal actually. I have plans to add a timeout. I.e. if more then 5 minutes no internet, shut it down until there is internet again as it's a bit of an energy waste now...
newbie
Activity: 29
Merit: 0
Quote
Changes 08/12:
- fixed pool priority issue after a pool temporary died.

Thanks for this! I'll be testing priority changes at the new version.
newbie
Activity: 33
Merit: 0
Tell them you aren’t scamming us Blissz. Say it ain’t so.
newbie
Activity: 50
Merit: 0
Asking how the fee is obtained, and complaining that the fee is hidden from people are two different things.  If you are saying that you think the fee isn't really 1.5% as blissz says, then you should make it clear that that is your concern. 
As for how to put the stock firmware back on, you flash it the same way you flash any of the blissz firmware versions...

Based on nicehash going down and the sorry state of most other pools I've tried, I for one can't say that the fee is truly 1.5%.  If you are really concerned the fee is pulling more than 1.5%, you would need to mine the same pool for long enough on the bitmain firmware, then the blissz firmware and compare the results.   
I'm pretty sure the fee is 1.5% of your time and was mentioned earlier in the thread, but I guess it could be added on the first post to help avoid confusion.
My understanding of the way pool switching payouts works though isn't that great, so by taking 1.5% of your hashing time, it may take more than 1.5% of your payout?  To say he is hiding the fee is inaccurate. (unless of course it turned out the fee was actually higher than expected), it was clearly discussed before the first firmware was released.

For me though, I was on nicehash prior to using the blissz firmware, now I'm using antpool, so I don't have a good stock firmware vs blissz firmware comparison.  I can say that I have had a hell of a time getting the stated payouts on my gpu miners though, and after switching from a multi algo switching pool to mining a single algorithm I get better results.  As far as I've seen all of the dev fees I've run across work the same way, the developer adds in code that switches to mine to their pool for X amount of time...


blissz, please add the dev pool back so it's obvious to the blundering idiots that can't read the first post, or read through the thread a little bit before blindly flashing new firmware on their antminer.

I for one thought it was obvious by reading the first post that there was a 1.5% dev pool, I don't believe blissz was trying to hide anything.  Also, my two D3s were running at 14.5 - 15GH/s at around 1050 watts on the stock bitmain firmware.  Now they are running at ~18 GH at 980 watts on blissz firmware.  So I'll gladly pay a 1.5% fee for a 20% bump in hashing power at a slightly lower power usage....

Appreciate the work blissz,  (careful, sarcasm ahead..) maybe you should create a pro version of the firmware without the fee and charge $50 upfront for it?  No wait, that wouldn't work because people would just pass around the firmware to make extra profit off of your hard work...  Guess it makes sense to just add a small fee into the firmware...



Here is a thought,

Tell us how it is calculated! Tell us how you arrive at 1.5%??

Because as I watch my miner fade away from the mining site every two hours for 10 minutes....

10 minutes out of 120...hmmmm 8.3%

I am thinking, this is Blissz...

Is there any way I can be sure there is not more than 1.5% being mined for you. So far all other miners on treasurequarry get 0.0013 average per share, and I am getting 0.0042 average per share.

Same machine, and I make sure I am faster than the other two, and I still get one third of the other miners.

So please, tell me how the 1.5% is calculated, and I will leave you alone about it. This is why this is all in this forum, BECAUSE IT IS NOT CLEAR!

i cannot help to think it is not exactly 1.5%. AND I think disconnecting from my pool every two hours fucks me in some way with the psow or w/e the fuk./they call it

Just tell me, how is it (1.5%) calculated. That is why this question comes up, because "how" is not clear, not the "what". We all get the 1.5, its the HOW, we do not get....

The other two miners on treasurequarry have orig firmware, they stay 18-20G/H all day, MINE?, well every time I look at it it says 13G/H, and slowly creeps back to 19, then back to 13.....Cards fine, Miner fine,

Blissz, I think there is more to this,

Is there?

M

PS

It is just so frigging aggravating to check at the mining site, and see my miner (I call him lil' 13 G-because the sites always say I am mining 13G/H, not the 19 or 21 that my maching does.)ALWAYS doing worse than the others.

WAY WORSE, NOT 1.5% worse! we are talking 35-75% worse...

But I will keep learning.

Learn me Dis:

How do I properly put the original FW back on my machine?

Now that I am mining 50% what others get, I can go deaf, and at least make what they do...

Otherwise Love the software, and If I had your ability, I WOULD NOT OF THOUGHT OF IT AS A WAY OF MAKING MONEY< rather helping others. What an idea, helping others.

Greed and Vanity are sins. They are sins for a reason.

How do I get back to original FW please kind sir.

M
member
Activity: 123
Merit: 10
Hello,

Thanks for taking time to solve this D3 problem. I am quiet ready to download and install this firmware. I do have a few questions. How does the Dev Pool work? Do you have a mining Pool I must connect too? Are all X11 coins available on this Dev Pool.

That's already baked-in, you don't need to do anything, the miner will automatically stop mining for you and start mining for the dev a few minutes every couple of hours. Don't listen to the idiots that complain about 1.5% To make it clear to see, if you're getting a hashrate of 19300, you get instead 19010, who cares?

Thanks the explanation I will be flashing my first D3 watch it for a week and then the others.
member
Activity: 140
Merit: 17
Hello,

Thanks for taking time to solve this D3 problem. I am quiet ready to download and install this firmware. I do have a few questions. How does the Dev Pool work? Do you have a mining Pool I must connect too? Are all X11 coins available on this Dev Pool.

That's already baked-in, you don't need to do anything, the miner will automatically stop mining for you and start mining for the dev a few minutes every couple of hours. Don't listen to the idiots that complain about 1.5% To make it clear to see, if you're getting a hashrate of 19300, you get instead 19010, who cares?
member
Activity: 123
Merit: 10
Hello,

Thanks for taking time to solve this D3 problem. I am quiet ready to download and install this firmware. I do have a few questions. How does the Dev Pool work? Do you have a mining Pool I must connect too? Are all X11 coins available on this Dev Pool.
Pages:
Jump to: