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

caliel

newbie

Activity: 13

Merit: 0

Quote from: caliel on December 10, 2017, 09:23:39 PM

Dec 11 02:19:23 (none) local0.err cgminer[362]: cgminer time error total_secs = 1512958763.148932 last_total_secs = 1.000000
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Failed to resolve (?wrong URL) nicehash:80
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Dec 11 02:19:29 (none) local0.warn cgminer[362]: API running in IP access mode on port 4028 (15)
Dec 11 02:20:58 (none) local0.err cgminer[362]: No mining pools available, restarting...
Dec 11 02:20:58 (none) local0.warn cgminer[362]: Attempting to restart cgminer 4.10.0

I have a bad URL in my first loop's address (nicehash:80), the second address is correct, but I am getting constant reboots. This wasn't happening until this very latest version of firmware

Yeah, this is happening even when I have solid addresses in each pool... across 11 different D3s..

Dec 11 02:36:33 (none) local0.err cgminer[362]: cgminer time error total_secs = 1512959793.733065 last_total_secs = 1.000000
Dec 11 02:36:33 (none) local0.warn cgminer[362]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:36:33 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Dec 11 02:36:34 (none) local0.warn cgminer[362]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:36:34 (none) local0.warn cgminer[362]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Dec 11 02:36:39 (none) local0.warn cgminer[362]: API running in IP access mode on port 4028 (15)
Dec 11 02:38:09 (none) local0.err cgminer[362]: No mining pools available, restarting...
Dec 11 02:38:09 (none) local0.warn cgminer[362]: Attempting to restart cgminer 4.10.0

[EDIT] This is happening because both of the dev pools were down at the time. Appears to be a bug introduced into the latest firmware.

caliel

newbie

Activity: 13

Merit: 0

Dec 11 02:19:23 (none) local0.err cgminer[362]: cgminer time error total_secs = 1512958763.148932 last_total_secs = 1.000000
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Failed to resolve (?wrong URL) nicehash:80
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Dec 11 02:19:23 (none) local0.warn cgminer[362]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Dec 11 02:19:29 (none) local0.warn cgminer[362]: API running in IP access mode on port 4028 (15)
Dec 11 02:20:58 (none) local0.err cgminer[362]: No mining pools available, restarting...
Dec 11 02:20:58 (none) local0.warn cgminer[362]: Attempting to restart cgminer 4.10.0

I have a bad URL in my first loop's address (nicehash:80), the second address is correct, but I am getting constant reboots. This wasn't happening until this very latest version of firmware

[EDIT] This is happening because both of the dev pools were down at the time. Appears to be a bug introduced into the latest firmware.

mkmfins

newbie

Activity: 30

Merit: 0

Quote from: mkmfins on December 10, 2017, 08:56:32 PM

I have this difficulty still.
My CHAIN # 1 card does not show in ASIC status, but it is still working in the pool showing an increase that CHAIN 2 and 3 did not show.

When I turn it off completely the GH / S decreases a lot.
What can this be?

If I let her work this way, is there any chance of something worse going on?

If there's anything I can do to get her on, because it's no good for me to send her back to bitmain, because I'm going to pay a high freight rate and if I do, I'll have to pay the customs as well. In the end you will not give me any profit and only lose ... But than I've lost when buying that shit.

IMAGES: https://i.imgur.com/pFfLXlb.png
IMAGES: https://i.imgur.com/lGaRBNE.png

KERNEL LOG: https://ghostbin.com/paste/uxy4j

Now she appeared ...
IMAGE: https://i.imgur.com/G0bO35u.png

mkmfins

newbie

Activity: 30

Merit: 0

I have this difficulty still.
My CHAIN # 1 card does not show in ASIC status, but it is still working in the pool showing an increase that CHAIN 2 and 3 did not show.

When I turn it off completely the GH / S decreases a lot.
What can this be?

If I let her work this way, is there any chance of something worse going on?

If there's anything I can do to get her on, because it's no good for me to send her back to bitmain, because I'm going to pay a high freight rate and if I do, I'll have to pay the customs as well. In the end you will not give me any profit and only lose ... But than I've lost when buying that shit.

IMAGES: https://i.imgur.com/pFfLXlb.png
IMAGES: https://i.imgur.com/lGaRBNE.png

KERNEL LOG: https://ghostbin.com/paste/uxy4j

may142012

member

Activity: 301

Merit: 10

Blissz, can you focus on D3 but not L3+ nor S9? Those two are making good money, but D3 is different, please?

david916

newbie

Activity: 22

Merit: 0

Quote from: llanaio on December 10, 2017, 06:54:36 PM

Thanks for the update. To those who suggest the dev isn't responsive, I say, what do you call new updates every few days? It's one guy working on this, making our D3s more useful for us, whether our concern is noise, heat, or max hashrate. I expect he has a life and real job too. Blissz, thanks for the development. Awesome Miner integration is a priority for me, since that's my main administration tool. I think that people have a point that mining the devfee soon after a restart does increase the amount of devfee mining. However, I expect if you wait too long then a few people will restart their miners to prevent your fee. What about mining the devfee after 45 minutes as a happy medium? That would ensure that the miners were running and stable for owners, but probably not be worth it to them to constantly restart to avoid your fee.

I think you'll find the point is, the dev isn't responsive on this subject. For instance, you've suggested something. Don't expect a substantive response on this subject. As a result, people are finding workarounds. It would have been easier and more profitable to be responsive as it relates to the fees when people first brought forward their concerns. But alas, people learn in different ways.

dgwayne

newbie

Activity: 11

Merit: 0

Quote from: dgwayne on December 10, 2017, 07:18:17 PM

Looking into modify the antminer as well. I don't mind blissz taking fees. I have basic linux file modification skills. I just want to know where they are "hardcoded". I will figure it out sooner or later

https://ibb.co/fyXHkG

Seems to be hardcoded and a recompile to be performed in order to change some of the things that are in there. Not going to mess with it right now.

taserz

sr. member

Activity: 808

Merit: 294

Created AutoTune to saved the planet! ~USA

Quote from: david916 on December 10, 2017, 01:56:58 PM

Quote from: taserz on December 10, 2017, 01:54:23 PM

Quote from: keksik on December 10, 2017, 01:48:59 PM

Hi Blissz,

please can you change your fee to be mined not every i think 2 hours for minute or so, but better once per day for couple minutes? i dont like that my miner disconnect every two hours and start mining again..what you think?
- autotuning option will be great!lets say, i will set my miner fan to 25% and temperature to 75degree or so. and it will start tune each board separately..one by one.. this will be awesome really.
- what about new firmware for L3 or S9 miners?

thanks

Go in your firewall and block the pool he uses. Easy solution now it won't eve mine for him!

This is what happens when the dev is not open to people's concerns regarding the fee and even the transparency of it. People can come on and defend the dev all they want, and nip and paw at anyone who complains, but at the end of the day, if the concerns of users are not addressed (or appear to be dismissed), things like this will happen. I'm not endorsing this. But it is reality. Dev, come on, just address these concerns a little.

Just make it optional most users are to dumb to uncheck boxes anyways

dgwayne

newbie

Activity: 11

Merit: 0

Looking into modify the antminer as well. I don't mind blissz taking fees. I have basic linux file modification skills. I just want to know where they are "hardcoded". I will figure it out sooner or later

https://ibb.co/fyXHkG

reimon85

newbie

Activity: 39

Merit: 0

With latest firmware im getting more hw errors, i just lowered freq to avoid but something seems poorer that 2 versions ago firmware that i was running

llanaio

newbie

Activity: 58

Merit: 0

Thanks for the update. To those who suggest the dev isn't responsive, I say, what do you call new updates every few days? It's one guy working on this, making our D3s more useful for us, whether our concern is noise, heat, or max hashrate. I expect he has a life and real job too.

Blissz, thanks for the development. Awesome Miner integration is a priority for me, since that's my main administration tool. I think that people have a point that mining the devfee soon after a restart does increase the amount of devfee mining. However, I expect if you wait too long then a few people will restart their miners to prevent your fee. What about mining the devfee after 45 minutes as a happy medium? That would ensure that the miners were running and stable for owners, but probably not be worth it to them to constantly restart to avoid your fee.

qctechno

sr. member

Activity: 307

Merit: 250

Quote from: blissz on December 10, 2017, 05:25:50 PM

v1.12 :: 10/12 :: recommended update

Download:
https://mega.nz/#!ylJX0LCQ!8JWryI0jDhgMvPdH2mrOvybkXCtrpYtQpxu0akdxU1s

Changes 10/12:
- Improved awesome miner / other mining managers compatibility (setting the priority was not working)
- fix kernel log window height (saves you double scrolling...)
- added permanent antbleed fix (prevent remote control of your miner by bitmain Roll Eyes

) -> for details see http://www.antbleed.com/

happy mining!

* By the way I am very close to a first test version with some new features (including autotune), but let's fix the stable version first Wink

*

You save my day ! I updated my D3 to latest firmware and 1 board failed to hash after update.
I used your hacked firmware and I was able to fine tune my problematic chain 1.
I'm running v1.11 from the last 4hrs, work strong again.

Chain 1 : 412MHz / 11 Asic Voltage --- 1017 HW --- Buggy chain with Bitmain Firmware
Chain 2 : 400Mhz / 10 Asic Voltage --- 0
Chain 3 : 400Mhz / 10 Asic Voltage --- 0

Super appreciated.

clyjr

newbie

Activity: 50

Merit: 0

Yeah, looks like we were both confused. I knew I had seen people say to try and stay 75-80 Temp(Chip), and knew the guide said 85 shutdown but thought that was the chip temp. Either way, if blissz and others say to try and stay below 80 (Chip), then that's what I'm going to do, just means there is more shutdown overhead than I thought since the PCB is way below 80 when the chip is at 80...

Quote from: david916 on December 10, 2017, 05:28:39 PM

Quote from: clyjr on December 10, 2017, 05:12:02 PM

Quote from: david916 on December 10, 2017, 04:43:06 PM

Quote from: clyjr on December 10, 2017, 04:26:59 PM

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up.
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F. I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA. With no current way to remove the air from my garage, I'm stuck running them a little slower. I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

Got it, thank you! To clarify, is there a different level of importance on the two temperature identifiers? Temp(PCB) Temp(Chip). In other words, my current temps are:

Temp(PCB) Temp(Chip)
51 77
49 74
52 78

Does this mean I can ramp them up even more until the Temp(PCB) gets near 80, and I can disregard Temp(Chip)?

Unless I'm confused, the 85 degree limit is on Temp(Chip), I don't think you need to focus on the Temp(PCB) value. Maybe someone else can chime in to verify, but I'm pretty sure that's correct.

Well that means I'm very confused, because from Bitmain's installation guide quote: "Note: The miner will stop running when the PCB temperature is over 85°C" No note about the Temp(Chip). Clarification from anyone who knows about this would be appreciated by all, I'm sure.

blissz

sr. member

Activity: 336

Merit: 258

Quote from: jackfirth on December 10, 2017, 05:36:04 PM

good work, just updating now, thanks for the priority fix - so quickly.

what about L3+ can we get firmware for that?

You're welcome Wink

regarding the L3+: I will try to get my hands on one, as I got some time to kill around the Christmas days Wink

But first I want to have a stable auto tune functionality for the D3.

blissz

sr. member

Activity: 336

Merit: 258

Quote from: david916 on December 10, 2017, 05:28:39 PM

Well that means I'm very confused, because from Bitmain's installation guide quote: "Note: The miner will stop running when the PCB temperature is over 85°C" No note about the Temp(Chip). Clarification from anyone who knows about this would be appreciated by all, I'm sure.

The installation guide is a bit vague then... Form what I know from code: fans will run at 100% when above 85 °C chip temps. High temperature shutdown protection is not yet build in, but would be a good feature actually.
My advice: don't run your chip temperature above 80 °C for a longer period as it will definitely harm the lifetime on long term.

jackfirth

newbie

Activity: 31

Merit: 0

Quote from: blissz on December 10, 2017, 05:25:50 PM

v1.12 :: 10/12 :: recommended update

Download:
https://mega.nz/#!ylJX0LCQ!8JWryI0jDhgMvPdH2mrOvybkXCtrpYtQpxu0akdxU1s

Changes 10/12:
- Improved awesome miner / other mining managers compatibility (setting the priority was not working)
- fix kernel log window height (saves you double scrolling...)
- added permanent antbleed fix (prevent remote control of your miner by bitmain Roll Eyes

) -> for details see http://www.antbleed.com/

happy mining!

* By the way I am very close to a first test version with some new features (including autotune), but let's fix the stable version first Wink

*

good work, just updating now, thanks for the priority fix - so quickly.

what about L3+ can we get firmware for that?

david916

newbie

Activity: 22

Merit: 0

Quote from: clyjr on December 10, 2017, 05:12:02 PM

Quote from: david916 on December 10, 2017, 04:43:06 PM

Quote from: clyjr on December 10, 2017, 04:26:59 PM

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up.
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F. I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA. With no current way to remove the air from my garage, I'm stuck running them a little slower. I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

Got it, thank you! To clarify, is there a different level of importance on the two temperature identifiers? Temp(PCB) Temp(Chip). In other words, my current temps are:

Temp(PCB) Temp(Chip)
51 77
49 74
52 78

Does this mean I can ramp them up even more until the Temp(PCB) gets near 80, and I can disregard Temp(Chip)?

Unless I'm confused, the 85 degree limit is on Temp(Chip), I don't think you need to focus on the Temp(PCB) value. Maybe someone else can chime in to verify, but I'm pretty sure that's correct.

Well that means I'm very confused, because from Bitmain's installation guide quote: "Note: The miner will stop running when the PCB temperature is over 85°C" No note about the Temp(Chip). Clarification from anyone who knows about this would be appreciated by all, I'm sure.

blissz

sr. member

Activity: 336

Merit: 258

...

clyjr

newbie

Activity: 50

Merit: 0

Quote from: david916 on December 10, 2017, 04:43:06 PM

Quote from: clyjr on December 10, 2017, 04:26:59 PM

before switching to 220v I didn't want to stress my 15 amp circuit and wanted some headroom for the 85 degree limit in case my garage started to heat up.
Currently my garage is staying around 73F with an outside temp of 45F, last week outside temps were 70F+ and the garage was up to 83F. I also want to keep the noise down as much as possible as to not piss of my neighbors or HOA. With no current way to remove the air from my garage, I'm stuck running them a little slower. I'll probably start ramping them up after a few days to find the best noise / fan speed / hashrate combo though.

Got it, thank you! To clarify, is there a different level of importance on the two temperature identifiers? Temp(PCB) Temp(Chip). In other words, my current temps are:

Temp(PCB) Temp(Chip)
51 77
49 74
52 78

Does this mean I can ramp them up even more until the Temp(PCB) gets near 80, and I can disregard Temp(Chip)?

Unless I'm confused, the 85 degree limit is on Temp(Chip), I don't think you need to focus on the Temp(PCB) value. Maybe someone else can chime in to verify, but I'm pretty sure that's correct.

blissz

sr. member

Activity: 336

Merit: 258

Quote from: bcn2048 on December 10, 2017, 05:01:16 PM

Quote from: bcn2048 on December 09, 2017, 04:21:57 PM

hi, Blissz, I'm going to flash your firmware over my D3 to try to improve its working.

I have 19,3 GHs model and first thing was to lower the frequency. I set it to 506 Mhz where I get average 18200 GHs, the power consumption is around 1130W. I find those settings are the sweetspot regarding HW errors.

HW errors appears mostly in the second hashboard, arround 200 a day, also third hashboard is around 4 Celsius degrees hotter than first and second - can these be fixed with changing voltage ?

I heard from some folks, that undervolting the graphical cards for mining could harm them in longterm (if this is true at all) - do you think it is the same with asics ? I'm mainly conserned about loosing warranty - can Bitmain obtain any info from my D3 if there are any custom firmwares (antbleed is probably history now) ?

thanks in advance for answers,

best regards to you and to the rest of community

Blissz , anybody ?

It's the opposite: Undervolting will extend the lifetime of your miner as there is less heat produced and there is less stress on all the electric components. Furthermore it will simply saves you energy / money and a complaining wife because of the noise in case you got a wife Wink

But no kidding: what I would do in your case: set the frequency of the second hashboard a bit lower (10 -20 Mhz) compared to the other boards (a hashboard is called chain in the advanced UI). The HW errors will drop and so will the temperature of that board. The hashrate will drop slightly but it's probably worth it

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