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

Perfetc, we can manually test if your switches work .. we are here to help and beta test

Hi guys,

After flashing this firmware I started getting the following lines in the kernel log:

Jan  1 00:07:51 (none) local0.err cgminer[31311]: get_asic_response: 0 Headers are not corret! Header0 = 0x00, Header1 = 0x00, Header2 = 0x00 rp = 16

Should I worry about it and how can I possibly fix it?

Regards,
Svet

After install Blissz Firmare ,
I tried to use ANTpool setting

But the pool always Dead !

But any other pool are live

Are bitmain block the miner from using their pool ?

Help Please

Hi guys,

I really would like to have other algorithm support on the D3 as well, so here is an update from what I've experienced so far:

I tried to isolate a single algorithm / other algorithms, but not yet succeeded. There are some parameters to tweak with, which seem to change something in the ASICS, but the problem is that even if it switches to another algorithm (which I am not 100% sure), you can't know which one... It's also not that straightforward to change the linux part to support another algorithm, so it's easy to make a small mistake there as well.
If I had some inside information that for example groestl is 100% for sure supported then it would be easier to go 100% for that. Now there are too many variables to play with.
I still have some ideas left to try: I want to build an automated matrix test that tries all parameter combinations and tries to verify it against all known algorithms. It will be quite an effort to build this, but I think it's the only possibility to find out if it's possible.

this is some sort of an idea, maybe plausible or not:

since x11 is a combination of 11 algorithms, can anyone change the codes on the D3 to change into any of those algos?
that would be a very great innovation or anything you can call that.

Any new update??

Blissz, is there any way that we can move on from simply messing with fan speeds and voltage to actually trying to isolate and mine a single algo from X11? People have previously dismissed this idea but I yet to see any reason why it shouldn't be possible even if it is at a severely lower hashrate. For instance these D3's are already mining and support the groestl algorithm which is one of the 11 algorithms contained in X11. If the D3 could be modded to mine only that specific algorithm even at 500Mh/s @ 1200 watts then that would bring the profitability back to nearly $30 per 24hr.

What do we need to do to look at this more seriously? Do we need to pool together and get you another D3 to test with?

This firmware is to reduce noise and power.
I do not pay attention to errors too much and i still have good hash rate.
I am doing around 50 per second on of my board. It seems to have some problems
and lowering voltage/freq does not really help. I just left it working with 55 asics
and i have hashrate on the websites although these errors.
I think it is from some of the capacitors and i will change when it goes really really
bad. I am using beta 2.05 version. Just used autotune for 20-30 minutes.
Then i put the best values and forget for my miners
Playing everyday with it just lowers your revenue...

Easy enough, thank you

clear your browser cache.

Flashed back to Bitmain Firmware and it still shows the Blissz logo on the top, any way to get rid of that?

(forgive my english, I use a translator)
I've been following this topic for a long time, since I have 2 pieces of D3.
Yesterday I decided to try this firmware, and I would like to share the result and maybe get help.
I sat almost all day to set up one of my D3 on this firmware. I wanted to get the best performance, since noise for me is not important.
(on all my devices fans are set to 85% in manual mode)

Factory firmware on two D3 is set to 475Mgts - while it consumes 1050W and produces an average of 17 GH/S, and the total number of errors from all boards = about 20-40 per day.

At first I tried the beta firmware.
I tried to configure everything manually, without the use of automatic settings. Within 5 hours I was not able to achieve the work of D3 without a lot of errors, even at a speed of 18.5 GH/S.
Because of the constant reset of the number of errors, it is difficult to understand how stable the device works.
View error statistics, you can use the Awesome Miner.

With the firmware version 1.12, everything turned out better, but the final result is not very happy.
After a long search of the frequency and voltage settings for each card separately, the best I've got are:
1 boards - 487 MHz - voltage 14 (this is the worst of the boards for quality)
2 boards - 531Mhz - voltage 15
3 boards - 531MHz - voltage 13 (this is the best board for quality)
At the same time, the production rate was about 19.2 GH/S
But the number of errors is about 2 per minute or even more.

I want to ask the developer why it happens, if you restart the mining (or reboot completely), without changing the settings, just click "save&apply"(or reboot), every time after this, the number of errors is DIFFERENT!
I tried so several times, and the number of errors was from 1 per minute to 10-15 per minute! With absolutely unchanged settings!

Can someone tell me what my mistake is?
Why can not I configure the higher performance on this firmware?
Or this firmware will not help me achieve better performance without errors - compared with the firmware?
Will it only reduce the consumption of power and noise at the same performance?

Here is the result of which I achieved:
http://picua.org/img/2018-01/09/grpcd0o7oi6a7mcebi1rv4rh1.png

if anyone's selling their D3 in the USA, pm with your price.

I was able to set it up with prohashing, but it doesn't work for profit switching... you could set it up in the pool/d3 and just click to change the priority when you want to swap pools. It does make it easier to change the order of the pools. but I think without the profit switching it might set them back after the devfee.

Yup, waiting to get the green light from bitmain to get another board. Instant sell once i get the replacement. Never again with Bitmain

Rubbish coin. Payout is the worst ive come across. Dont be fooled by these calculators.

Thanks, I tried, but problem with Prohashing is options in Password field, not Miner name separated with dot after Worker Name. I did not find any description of Vars to fill Password field like "a=x11 n=%WorkerName% w=1300 p=0.08". For monitoring AwesomeMiner is pretty good.

I'm still on 1.12 and I found I can add the extra pools but after the devfee mining they seem to disappear... I know on all of them they disappear after a reboot but with the D3 it seems to disappear after the devfee also. again, not that big of a deal but it would be nice to have them stick. 

When I order my D3's (15 ) i order spare PSU so I tested and no change.

is the PSU outputting power?