I pretty much run my machines clocked down to save power.
16,400 @ 800W 1-2v
Today I thought I would fiddle around a bit.
Running at 19,300 @1100w 13v(bitmain stock)
So its an increase of 18% in speed and 37.5% increase in power consumption. Its not worth it!.
Power mode Im at 500-525. Some boards will run 550 but I start creaping to 1250w. I have run it stable at 21GH but its not worth it.
in quiet mode I really have to fiddle with the settings but its mostly around 450. one board wont run low volts unless i put it down to 400.
Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 59. (Read 125931 times)
Any chance we can get the fan setting on the advance setting page?
THat way you only have to reboot once when switching from performance/quiet setting.
Thanks
THat way you only have to reboot once when switching from performance/quiet setting.
Thanks
so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
Lower the frequency a bit more on that board. set it to 300 for example
300 still nothing on that chain 1 board
even as low as 137 still dead
really strange as this board worked at 400 on the stock FW
what is your voltage setting? have you tried to send more juice to that chain, try 15 or 16 on the power settings...
voltage was default , i tried 15 and 17 voltage on 400 freqency , maybe shut the miner down ?
I'd try to shut the miner down, wait for 5min, check all cables and connection, then power up again... Try this a few times.
If one board is really not visible and you tried everything from settings, the reason might be a defective controller board. In this case, I'd suggest to flash back original FW, make screenshots and start a support ticket with bitmain.
so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
Lower the frequency a bit more on that board. set it to 300 for example
300 still nothing on that chain 1 board
even as low as 137 still dead
really strange as this board worked at 400 on the stock FW
what is your voltage setting? have you tried to send more juice to that chain, try 15 or 16 on the power settings...
voltage was default , i tried 15 and 17 voltage on 400 freqency , maybe shut the miner down ?
I'd try to shut the miner down, wait for 5min, check all cables and connection, then power up again... Try this a few times.
If one board is really not visible and you tried everything from settings, the reason might be a defective controller board. In this case, I'd suggest to flash back original FW, make screenshots and start a support ticket with bitmain.
It's more silent than fan on the Bitmain power adapter
True, I noticed the same - now PSU is making most of the noise actually...
so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
Lower the frequency a bit more on that board. set it to 300 for example
300 still nothing on that chain 1 board
even as low as 137 still dead
really strange as this board worked at 400 on the stock FW
what is your voltage setting? have you tried to send more juice to that chain, try 15 or 16 on the power settings...
voltage was default , i tried 15 and 17 voltage on 400 freqency , maybe shut the miner down ?
Hello everyone.
I've installed two Noctua fans (in and out) 14" PPC http://noctua.at/en/nf-a14-industrialppc-3000-pwm/specification
And 2 fan's adapters https://www.amazon.com/Bgears-Cooling-Fan-Adapter-140mm-Black/dp/B0043GMY1U
Room temp ~21 C
FAN Mode - Auto default
After 2 hours
Temp(Chip) ~77 C
Fan1 ~1,830 r/min (dynamic)
Fan2 ~1,740 r/min (dynamic)
It's more silent than fan on the Bitmain power adapter
I've installed two Noctua fans (in and out) 14" PPC http://noctua.at/en/nf-a14-industrialppc-3000-pwm/specification
And 2 fan's adapters https://www.amazon.com/Bgears-Cooling-Fan-Adapter-140mm-Black/dp/B0043GMY1U
Room temp ~21 C
FAN Mode - Auto default
After 2 hours
Temp(Chip) ~77 C
Fan1 ~1,830 r/min (dynamic)
Fan2 ~1,740 r/min (dynamic)
It's more silent than fan on the Bitmain power adapter
so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
Lower the frequency a bit more on that board. set it to 300 for example
300 still nothing on that chain 1 board
even as low as 137 still dead
really strange as this board worked at 400 on the stock FW
what is your voltage setting? have you tried to send more juice to that chain, try 15 or 16 on the power settings...
There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well
I updated Bitmain firmware on 1 D3 device which making mi problem with dead board. Why after flashing Bitmain FW I still have Blissz stamp on top left corner? I already spoke with bitmain i need to send them device on chio replacement? Will this void my warranty, why I cant just install Bitmain FW back?
It's your browser cache. Just press ctrl + f5 on your browser and it looks like normal again
Huh, thx for tip
.Can I normally send D3 device back on warranty? They can not see that I used custom FW, after I flash Bitmain fw and void my warranty?
so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
Lower the frequency a bit more on that board. set it to 300 for example
300 still nothing on that chain 1 board
even as low as 137 still dead
really strange as this board worked at 400 on the stock FW
Hi @all,
as probably some of you have exchanged fans - what kind of model / type would you guys recommend? How many RPM fans are you using to get the D3 quiet?
Mine are currently running at 2500-3000rpm with original fans. Any recommendations?
And thanks Blissz, for starting this and still working on an even better custom FW. :-)
as probably some of you have exchanged fans - what kind of model / type would you guys recommend? How many RPM fans are you using to get the D3 quiet?
Mine are currently running at 2500-3000rpm with original fans. Any recommendations?
And thanks Blissz, for starting this and still working on an even better custom FW. :-)
I run it with the 120mm 2000rpm Scythe Slip Stream fans, but that only works if you run it at the lowest voltage setting. A relative silent 2500 to 3000rpm would be better. Anybody got suggestions?
Yes, I think I found one:
http://noctua.at/en/products/product-line-industrial/nf-f12-industrialppc-3000-pwm
This one looks quite promising actually. I just ordered some (they are not cheap!) and I'll give them a try over the weekend...
So...
New fans (noctua industrial line 3000rpm) installed on front and back side. Here are the results...
First of all I thought something is not working as I was only hearing the PSU. Then I remembered that my fans were previously set to 25% manual mode. With this setting the noctua fans are almost not noticeable. When running fans at 100% (3000rpm) they are comparable to the original bitmain fans running around 20%.
My one D3 runs now with the following settings:
Noctua fans front and back side, AUTO Performance Setting
Hashing at 16.5GH/s, fans running at 2300rpm (inlet) and 2400rpm (outlet) with custom voltage and MHZ set for each chain. Running for more than one hour now, keeping temp around 80°C each chain, while running at 18°C environment temp... So, regarding the noise - it's not completely silent of course but there is huge difference to the original fans.
But besides the fact that the noctua fans are quite pricy there are limits of course, they can't go higher than 3000rpm so high performance (>18GH/s) hashing seems unrealistic with those but if you want to get a more silent miner, the noctua fans are a good option. And no, I'm not getting payed to write that here. :-)
There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well
I updated Bitmain firmware on 1 D3 device which making mi problem with dead board. Why after flashing Bitmain FW I still have Blissz stamp on top left corner? I already spoke with bitmain i need to send them device on chio replacement? Will this void my warranty, why I cant just install Bitmain FW back?
It's your browser cache. Just press ctrl + f5 on your browser and it looks like normal again
There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well
I updated Bitmain firmware on 1 D3 device which making mi problem with dead board. Why after flashing Bitmain FW I still have Blissz stamp on top left corner? I already spoke with bitmain i need to send them device on chio replacement? Will this void my warranty, why I cant just install Bitmain FW back?
so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
Lower the frequency a bit more on that board. set it to 300 for example
Hello. This firmware contain DevFee? Or not? If I will replace my original firmware to this, I will lose my warrantly? Thanks!
1,5% dev fee. Actually I don't think you loose warranty as the firmware is not visible in the mining boards. The controller you can flash back if you want before sending it back to bitmain, but I am not 100% sure on this. Therefore the warning on the topic start.
so a funny thing another D3 chain one was dead, using default FW i set freq to 400 in preparation of upgrading to blitz , chain 1 comes alive...
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
then i upgrade and no matter what power or lower freqency i set chain 1 still only shows 14 asics alive and stays dead,
flashed back to orig FW and tried the freqency trick again no luck
any tips ?
There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
The latest beta posted a few pages back contains a fix for this, but a new stable will be released today / tommorow containing the fix as well
There is some bug with pools. Part of my miners hashing on backup pool without reason, primary pool working fine, how to fix this?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
Every one hour few miners start to hashing on backup pool, than come back to primary pool?
blissz,
FYI, I had the 1 chain high/low temp issue on my miner that had the stock 11/2 firmware, updated to stock 11/20 and it fixed the issue for several days. Now I updated to blissz 11/29 and the issue is back. I'm going to try the release before 11/29 and see if it has the issue also.
Also, it would be nice if you could leave the links to the last several versions in the first post if possible. thanks
FYI, I had the 1 chain high/low temp issue on my miner that had the stock 11/2 firmware, updated to stock 11/20 and it fixed the issue for several days. Now I updated to blissz 11/29 and the issue is back. I'm going to try the release before 11/29 and see if it has the issue also.
Also, it would be nice if you could leave the links to the last several versions in the first post if possible. thanks
Followup, tried all the way back to 11/26 version and still has the temp issue. I'm going to reflash the latest, and unplug it for a few minutes to test it out again...
blissz,
FYI, I had the 1 chain high/low temp issue on my miner that had the stock 11/2 firmware, updated to stock 11/20 and it fixed the issue for several days. Now I updated to blissz 11/29 and the issue is back. I'm going to try the release before 11/29 and see if it has the issue also.
Also, it would be nice if you could leave the links to the last several versions in the first post if possible. thanks
FYI, I had the 1 chain high/low temp issue on my miner that had the stock 11/2 firmware, updated to stock 11/20 and it fixed the issue for several days. Now I updated to blissz 11/29 and the issue is back. I'm going to try the release before 11/29 and see if it has the issue also.
Also, it would be nice if you could leave the links to the last several versions in the first post if possible. thanks
Followup, tried all the way back to 11/26 version and still has the temp issue. I'm going to reflash the latest, and unplug it for a few minutes to test it out again...
Jump to: