Pages:
Author

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

member
Activity: 140
Merit: 17

How you write the password commands? for me d=64 work
my line looks like this:
a=x11 d=64 p=3.5 w=827 n=d326

and don´t forget, the diff must be power of 2

You pay $3.5 per kWh Huh I read their help and I think it's supposed to be expressed in $ per kWh. However I tried p=0.12 and the electricity cost in their statistics is crap...
sr. member
Activity: 336
Merit: 258
Is Blissz still supporting his FW? If not just tell me so i can revert back to Bitmain's FW.

Don't worry Smiley much to come mate.

currently testing the fix for some pools
member
Activity: 301
Merit: 10
Is Blissz still supporting his FW? If not just tell me so i can revert back to Bitmain's FW.
full member
Activity: 218
Merit: 100
I use Prohash, ZPool, GranatGas, coinmine, Miningpoolhub and antpool.
and for the poolswitching using Awesome Miner with profitswitch.
but Prohash must be switch manual, not working with the profitswitch in Awesomeminer i use prohash mostly only when i want to get paid in other Coins then DASH or BTC, the payout are not so good in the last weeks
Hi,
I use Awesome Miner with profitswitch.
But I don't understand how to enter the parameters for the password since there are no password fields in autoprofit.
The only solutiion is enter the parameters for the password since there are no password fields in autoprofit.
The only solution I see, is create pools and not use autoprofit.
Create the pools and add them to the miner, when profitswitching is Active the programm use all pool in the miner list for switching.
The problem with Prohashing is, that Awesomeminer detect the ALGO over the stratum Address and make the API calls to get the Actual paying and this is not working correct, but sometimes Awesomeminer switch to prohashing, too.
The Dev from Awesomeminer wrote that for the difference how Prohashing work he will not support it.
Think with using of MiningPoolHub, Zpool, GranatGas, Antpool and Coinmine you get a good Profit, better then only mine DASH.
newbie
Activity: 63
Merit: 0
I use Prohash, ZPool, GranatGas, coinmine, Miningpoolhub and antpool.
and for the poolswitching using Awesome Miner with profitswitch.
but Prohash must be switch manual, not working with the profitswitch in Awesomeminer i use prohash mostly only when i want to get paid in other Coins then DASH or BTC, the payout are not so good in the last weeks
Hi,
I use Awesome Miner with profitswitch.
But I don't understand how to enter the parameters for the password since there are no password fields in autoprofit.
The only solutiion is enter the parameters for the password since there are no password fields in autoprofit.
The only solution I see, is create pools and not use autoprofit.
newbie
Activity: 19
Merit: 0
I still can't find a stable freq/voltage and not get HW errors all the time. I just checked my miners this evening and one of them was on for 2 hours and had THOUSANDS of HW's. voltage 13 freq 512 global.
full member
Activity: 218
Merit: 100

How you write the password commands? for me d=64 work
my line looks like this:
a=x11 d=64 p=3.5 w=827 n=d326

and don´t forget, the diff must be power of 2

Thanks mate, works now so simple!! I was using , instead of space. Feel properly stupid now. Grin
No problem it´s not stupid the , you use on a lot of other pools, but prohash is in a lot of config things special, look only the way they use for the ALGO, think it´s the only pool that use the password commands to define the ALGO all other pools use the Stratum.
full member
Activity: 218
Merit: 100
Not trying to thread jack, can someone tell me why my d3 defaults to 65536.0000 difficulty on prohashing? Doesn't make a difference what I use for d=??

Appreciate any info, was going to try flashing back to stock but have not seen anyone complain about this issue.

My miner seems to stay on prohashing if I don't have any backup configured.

How you write the password commands? for me d=64 work
my line looks like this:
a=x11 d=64 p=3.5 w=827 n=d326

and don´t forget, the diff must be power of 2

Seems like a lot of you are using prohash?  Is that the way to go with D3?   Any advice would be appreciated.  Also I'm fairly new to the D3 scene so if you could give me the prohash settings I would really appreciate it!   Thanks!

I use Prohash, ZPool, GranatGas, coinmine, Miningpoolhub and antpool.
and for the poolswitching using Awesome Miner with profitswitch.
but Prohash must be switch manual, not working with the profitswitch in Awesomeminer i use prohash mostly only when i want to get paid in other Coins then DASH or BTC, the payout are not so good in the last weeks
newbie
Activity: 8
Merit: 0

How you write the password commands? for me d=64 work
my line looks like this:
a=x11 d=64 p=3.5 w=827 n=d326

and don´t forget, the diff must be power of 2

Thanks mate, works now so simple!! I was using , instead of space. Feel properly stupid now. Grin
newbie
Activity: 15
Merit: 0
Dont use prohashing for X11 and mine pure DASH only with any D3 !

How can we mine pure dash??  Whats the best way??  Settings??
newbie
Activity: 15
Merit: 0
Not trying to thread jack, can someone tell me why my d3 defaults to 65536.0000 difficulty on prohashing? Doesn't make a difference what I use for d=??

Appreciate any info, was going to try flashing back to stock but have not seen anyone complain about this issue.

My miner seems to stay on prohashing if I don't have any backup configured.

How you write the password commands? for me d=64 work
my line looks like this:
a=x11 d=64 p=3.5 w=827 n=d326

and don´t forget, the diff must be power of 2

Seems like a lot of you are using prohash?  Is that the way to go with D3?   Any advice would be appreciated.  Also I'm fairly new to the D3 scene so if you could give me the prohash settings I would really appreciate it!   Thanks!
member
Activity: 75
Merit: 10
Dont use prohashing for X11 and mine pure DASH only with any D3 ! I always have disconect from prohashing with any original firmware or Blissz and always have problems wit xxxx board. Thats why i mine pure dash and dont have any problem for more with 2 weeks with this firmware.
full member
Activity: 218
Merit: 100
Not trying to thread jack, can someone tell me why my d3 defaults to 65536.0000 difficulty on prohashing? Doesn't make a difference what I use for d=??

Appreciate any info, was going to try flashing back to stock but have not seen anyone complain about this issue.

My miner seems to stay on prohashing if I don't have any backup configured.

How you write the password commands? for me d=64 work
my line looks like this:
a=x11 d=64 p=3.5 w=827 n=d326

and don´t forget, the diff must be power of 2
newbie
Activity: 8
Merit: 0
Not trying to thread jack, can someone tell me why my d3 defaults to 65536.0000 difficulty on prohashing? Doesn't make a difference what I use for d=??

Appreciate any info, was going to try flashing back to stock but have not seen anyone complain about this issue.

My miner seems to stay on prohashing if I don't have any backup configured.
newbie
Activity: 4
Merit: 0
I'm having the same issue as others regarding prohasing and blissz's firmware, had to revert back to stock firmware, really disappointed, I'd be happy throw him a few bucks on each development but the dev fee switching now makes prohashing unusable. I wasn't seeing this impact with Nicehash so it didn't really bother me. I hope he can find another way.
newbie
Activity: 9
Merit: 0
Need some assistance/advice with my brand new Antminer D3.

I'm not trying to waste anyone's time so I'm going to try and be as detailed as possible so people can diagnose the problems I have.


Alright, the first day I get the miner. Runs for about 3-4 hours. Has red "fault light flash"--> check and see every chip has a red "x" restart and the entire board 3 just no longer showed up on the page.

I went and upgraded firmware and now all three are back up but the third only shows "54" chips while the rest show 60. I am unsure why this is.

It's been going well on Antpool now for about 24 hours but I've noticed it's got millions... MILLIONS of hardware errors. I am unsure how to fix this or what it means.



Here's my situation: Miner is a room with ac + window open. (80F- 60F at night). The power supply is the APW3++ from Bitmain. I'm in USA so I believe it's 120 volts if that matters.

Everything else seems to be set to default. You can see my recent miner status here: It seems to have improved hash rate for the time being?



https://imgur.com/oqT12Hf


Plus on a side note, it randomly hits 0.00 hash or something on antpool charts: https://imgur.com/a/d54aG


Anyways, should I try to use my warranty to get it fixed? What are the benefits of using this "firmware" and how is it possible that it would be quieter faster hashing, and less power? Can't Bitmain just update theirs? I'm very new to this and would love to learn so all advice is greatly appreciated.
When have installed on 120V you get only 1000-1100W out of a Bitmain PSU.
The HW Errors is a fault from Bitmain, they put the frequency so high only to label the miner with 19.3GH, try in the settings to reduce the frequency to 506. this was my magic number on the last 2 D3 i get from Bitmain.

Blissz, change the Firmware you can setup for all 3 hashboards independent the Power and frequency, how you see in your pic the last hashboard is hotter, lot HW-Errors.
With this Firmware you can tweak your D3 to get the best out of all 3 Hashboards



Thank you for that understanding, but my question is what exactly does it mean to get "hardware errors" it just means it's too hot? Hasn't even hit over 70C yet on a board? Plus, If I reduce the "frequency" what exactly does that do to my hash speed? Would it result in a reduced speed or no? what're the benefits?




I have the same problem :

https://www.dropbox.com/s/tstpxhj3jm4kpg8/Chips%20problem.jpg?dl=0

Many HW and lost 6 chips in few hours...

I contacted bitmain support's I' m waitting their respons

But sometime I recover one chip and the second chain disappear ...

https://www.dropbox.com/s/ng8w9cy86xlxe5c/55%20chips.jpg?dl=0

keep me updated. Thanks Cheesy

/quote]

Bitmain's response :
 
Dear ...,

Please try reloading the firmware:

https://shop.bitmain.com/support.htm?pid=00720170915192851224mJ36J1ap066E

Run the miner for 20 minutes after loading.

If it still does not work please test each hash board separately to determine which one is defective.

To test each hash board separately: keep the PSU connectors and controller cable on one of the hash boards connected and disconnect the cables from the other two hash boards. With the miner running you can see the status of the connected hash board.

Here is more detail: http://support.bitmain.com/hc/en-us/articles/226142788-Testing-hash-board-one-by-one

On the miner status screen defective chips are displayed as "xxx", "---" or " ASIC≠72

Once you know which part is defective please create a Repair ticket and ship the part back to us according to these instructions: https://shop.bitmain.com/workOrderGuide.htm

http://support.bitmain.com/hc/en-us/articles/222648028-How-to-disassemble-miners

Please pack the hash boards carefully. If the PINs are lost due to shipping damage it will void the warranty. Here is a video demonstrating how to pack the boards: https://youtu.be/Z0LdykALhxI

Please let us know if you have additional questions or concerns.

Best regards,
Barbara
Bitmain
full member
Activity: 240
Merit: 100
Can you fix the bug with Dev Fee miners please where if pools 1, 2 & 3 are unavailable that it mines Dev Fees the whole time?

My miners have been mining Dev Fees for the last 12+ hours using a very large amount of electricity because it was unable to connect to a pool...?

I would rather have it idle if it is unable to connect to a pool.


Who will not like to undermine for Blissz, (which I see is only interested in its profit ...) as a recommendation ... try to undermine with other pools that are different from those set by blissz and ... the pools that you want to  not pass out of your network, block access with rules in the firewall of the routers, and the work is done ...  nobody can be the master of your money ...

Code:
Jan  1 00:00:36 (none) local0.err cgminer[375]: WTF No pool 3 found!
Jan  1 00:00:36 (none) local0.warn cgminer[375]: Switching to pool 3 stratum+tcp://dash.suprnova.cc:9995
  Cheesy Cheesy Cheesy

in the original firmware the NTP worked instead in this does not work ... (another thing that has never been resolved)
newbie
Activity: 48
Merit: 0
blissz when you will fix the problem about prohashing ans some other site diff problem. Still miners without any reason going to backup pool. Setting static diff also not solving the problem.

Seems this issue got really bad with all of the miners looking for new homes.  I just switched back to official firmware for now until the dust settles.  When I looked at my graphs for prohash and zpool both seemed by affected by this issue.

Whats crazy is Blissz isn't even acknowledging there is a problem here.   This is a MAJOR problem.   By skipping around like this I'm quite sure he is making out like a bandit with miners mining only for him

That's not entirely true.  He ack'd the issue and said he has a fix pending for it.  In all fairness the instability in most pools got a lot worse in the last couple days since nicehash hack and that's not helping ANYone.   

I'm sure he will post a fix as soon as it's been tested/verified.
newbie
Activity: 15
Merit: 0
blissz when you will fix the problem about prohashing ans some other site diff problem. Still miners without any reason going to backup pool. Setting static diff also not solving the problem.

Seems this issue got really bad with all of the miners looking for new homes.  I just switched back to official firmware for now until the dust settles.  When I looked at my graphs for prohash and zpool both seemed by affected by this issue.

Whats crazy is Blissz isn't even acknowledging there is a problem here.   This is a MAJOR problem.   By skipping around like this I'm quite sure he is making out like a bandit with miners mining only for him
newbie
Activity: 48
Merit: 0
blissz when you will fix the problem about prohashing ans some other site diff problem. Still miners without any reason going to backup pool. Setting static diff also not solving the problem.

Seems this issue got really bad with all of the miners looking for new homes.  I just switched back to official firmware for now until the dust settles.  When I looked at my graphs for prohash and zpool both seemed by affected by this issue.
Pages:
Jump to: