After flashing to Blissz firmware then back to Bitmains, I still see Blissz logo ontop.
Is there any way I can remove that? I might have to send out a whole miner.
Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 23. (Read 125911 times)
One feature I'd like to see is the ability to solo mine...
Is There any possible way you can add that to your FW? To be able to mine into a local wallet address?
Is There any possible way you can add that to your FW? To be able to mine into a local wallet address?
This has probably been asked before, but are you perhaps considering a similar firmware for L3+? 
Are you ready do a gift the L3+ for BlissZ for this target?(without L3+ at-hand impossible do a FW for it)
What fecell is trying to say is that BlissZ doesn't own an L3+, so it would be very difficult to develop modded firmware for it.
Gen Tarkin of KNC Titan 3rd party firmware fame..said he looked at L3+ it is overclocked already, closed source too boot and
the only gains would be the miner software tweaks (cgmnier is it?), Thus no slack in the system.. I think that was the correct
interpretation of 'geek speak'as such...if my memory is correct...
w/o open source it is damn tough ..now if Bitmain would HELP someone him/you etc...fine
but we know THAT is never gonna happen
This has probably been asked before, but are you perhaps considering a similar firmware for L3+?
Are you ready do a gift the L3+ for BlissZ for this target?(without L3+ at-hand impossible do a FW for it)
What fecell is trying to say is that BlissZ doesn't own an L3+, so it would be very difficult to develop modded firmware for it.
This has probably been asked before, but are you perhaps considering a similar firmware for L3+?
Are you ready do a gift the L3+ for BlissZ for this target?(without L3+ at-hand impossible do a FW for it)
@blissz
I have an idea for new feature.
Fast switching priority of pools - by changing only priority number
I have an idea for new feature.
Fast switching priority of pools - by changing only priority number
This has probably been asked before, but are you perhaps considering a similar firmware for L3+?
Any ideas?
This way help me recover one blade (it give 200k HW / 30 minutes after freq and vcc changes):set default freq and vcc and reboot. after reboot wait 10-15 minutes and poweroff, plug off all connectors and place to warm temperature room for 1/2 hour (30-35 degrees Celsius), plug on all connectors, internet and powercord, and when power on, use with default settings 1-2 day. after power on the blade not be recovered right away, but soon it be self calibrated.
ps: now I have only 1008 HW for 1d20h28m1s. result so nice!
Turn the voltage of missing chain from 3-6 , it may appear . Look like lowest voltage & 1, 2 only work well with 220v D3
I switched back to Antminer-D3-20171210_0-blissz.tar on the D3 that has the dead/missing hashboard. It shows up now, but the hashrate and frequency don't really look right. The hashrate is way higher than it should be. It looks like the avg hashrate at the top of the status page reflects the true total speed, but there is some kind of bug/glitch for the first chain? I have another D3 that hasn't had any issues, but with the same Blissz firmware the first chain shows hashrate way higher than it should. Finally, I have a 3rd D3 that hasn't had any issues, and all chains show what look to be correct readings. I have included some screenshots.
D3 with questionable chain0 that doesn't show up with stock bitmain firmware:
https://i.imgur.com/YmMtzDm.png
D3 the doesn't have issues, but with blissz firmware shows incorrect chain0 hashrate:
https://i.imgur.com/PKGI0nK.png
Any ideas?
D3 with questionable chain0 that doesn't show up with stock bitmain firmware:
https://i.imgur.com/YmMtzDm.png
D3 the doesn't have issues, but with blissz firmware shows incorrect chain0 hashrate:
https://i.imgur.com/PKGI0nK.png
Any ideas?
Has anyone had to do a warranty return/repair? I have a hashboard that doesn't show up anymore on the status page.
This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead.
I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is?
This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead.
I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is?
Yes, I've had to ship back 5 hashboards so far. Don't listen to other posters saying it's worthless. If you're in the US the repair site is in California so shipping cost through fedex isn't bad. I've already received 1 board back and have 3 more on the way already. Average turn around time seems to be 2.5 to 3 weeks. If your board is dead you should absolutely open a ticket at support.bitmain.com and wait for a response. It cost me $9 in shipping costs for a single hashboard to be fully replaced. Bitmain then gave me a $9 coupon to use on their site. Get your board fixed or replaced, there's no reason not to.
I am running on very low electricity costs inside a DC where temps are from aircon. Any reason why I shouldn't let the fans run @ 100%? I mean nice for the D3's if the chips is sitting at 69-71 degrees Celsius. Lastly... any reason why I shouldn't push them a little harder if I can keep the temps below 79?
Thanks!
Thanks!
I am a solar miner so I change freqs once every afternoon to save at night.
I run at 100% Fan during the day. Played with it after I wrote down some of the tuning settings from the beta, that I thought were phenomenal, I get a strong 21.5 G/H During the day (12-14V settings) and pull 17.5 at night. (5-8V settings), under silent or default fan speeds depending on temps.
FYI,
M
blissz would you mind fixing the api after your version injection for proper json formatting:
"STATS": [{
"CGMiner": "4.10.0",
"Miner": "1.0.0.9",
"CompileTime": "Sat Dec 10 22:11:56 CST 2017",
"Type": "Antminer D3 Blissz v1.12"
} {
There should be a , in between those ending quotes... Run 'echo '{"command":"summary+stats+pools"}' | nc 4028' through a json validator if it doesn't make sense... It'd really make it a lot easier to parse if it was formatted correctly.
"STATS": [{
"CGMiner": "4.10.0",
"Miner": "1.0.0.9",
"CompileTime": "Sat Dec 10 22:11:56 CST 2017",
"Type": "Antminer D3 Blissz v1.12"
} {
There should be a , in between those ending quotes... Run 'echo '{"command":"summary+stats+pools"}' | nc
Yes, I've had to ship back 5 hashboards so far. Don't listen to other posters saying it's worthless. If you're in the US the repair site is in California so shipping cost through fedex isn't bad. I've already received 1 board back and have 3 more on the way already. Average turn around time seems to be 2.5 to 3 weeks. If your board is dead you should absolutely open a ticket at support.bitmain.com and wait for a response. It cost me $9 in shipping costs for a single hashboard to be fully replaced. Bitmain then gave me a $9 coupon to use on their site. Get your board fixed or replaced, there's no reason not to.
What did use the 9$ coupon for? Has anyone had to do a warranty return/repair? I have a hashboard that doesn't show up anymore on the status page.
This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead.
I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is?
This is what happened: I was running Blissz and it was showing me inflated hashrates on chain0 and failing with xxxx's. I rebooted and changed frequencies/voltages but nothing seemed to help. I switched back to the stock firmware and after some trial and error I was able to get chain0 to run normally. It ran for a couple of days and then just disappeared from the status page. I saw in the kernel log that it shows chain0 as having an asic count of 0 instead of 60. Also, I tried switching out the cables connecting the chain with cables that are known to work, and changing the slot it is connected to. I saw Bitmain also recommends reflashing the stock firmware and letting it run for 20 minutes, so I tried that as well. None of that worked, so it would seem the board is dead.
I don't know if I need to post on their support forum first asking for help, or if I can go ahead and create a help ticket, disassemble the D3 (removing chain0) and package up the faulty hashboard. Anyone know what the standard procedure is?
Yes, I've had to ship back 5 hashboards so far. Don't listen to other posters saying it's worthless. If you're in the US the repair site is in California so shipping cost through fedex isn't bad. I've already received 1 board back and have 3 more on the way already. Average turn around time seems to be 2.5 to 3 weeks. If your board is dead you should absolutely open a ticket at support.bitmain.com and wait for a response. It cost me $9 in shipping costs for a single hashboard to be fully replaced. Bitmain then gave me a $9 coupon to use on their site. Get your board fixed or replaced, there's no reason not to.
man ive got 2 units doing the same thing (one board on each unit gone and log shows 0 asics)
i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL
and the board I got sent back has missing o's ( 9 to be exact) so instead of like
oooooooo oooooooo
it shows
oooooooo oooo
great repair service
.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN
i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL
and the board I got sent back has missing o's ( 9 to be exact) so instead of like
oooooooo oooooooo
it shows
oooooooo oooo
great repair service
.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN
geeze...that sucks. Was it Bitmainwarranty.com that you sent it to? Also, did you go through Bitmain's ticket/support system and then they told you to ship it there, or you just paid to have the US facility fix it since shipping to and from China would take too long?I had the same issue and it's really annoying! But I was able to solve it somehow by setting this board to higher voltage settings - and I finally got rid of the problem.
I know it's not the best solution but it helps and if you're lucky it'll last a while...
what voltage did you up it to? so basically in blisz firmware you selected that board and only upped voltage on that one? and it came back from being disappeared ?
yes, with blissz fw I set voltage (this one board only) to >bitmain default - I think it was 15 or 16. This means gently overvolting this board, but it won't do any harm as long long as frequency and temp stays low. So I startet with freq 425 and went up a little.
It's up to you - but I'd try to set the voltage a little higher as usual and see if all ASICs come up again. It was the case in my situation.
Usually I used blissz fw to undervolt - but in this case it worked for me to do the opposite...
man ive got 2 units doing the same thing (one board on each unit gone and log shows 0 asics)
i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL
and the board I got sent back has missing o's ( 9 to be exact) so instead of like
oooooooo oooooooo
it shows
oooooooo oooo
great repair service
.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN
i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL
and the board I got sent back has missing o's ( 9 to be exact) so instead of like
oooooooo oooooooo
it shows
oooooooo oooo
great repair service
.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN
geeze...that sucks. Was it Bitmainwarranty.com that you sent it to? Also, did you go through Bitmain's ticket/support system and then they told you to ship it there, or you just paid to have the US facility fix it since shipping to and from China would take too long?I had the same issue and it's really annoying! But I was able to solve it somehow by setting this board to higher voltage settings - and I finally got rid of the problem.
I know it's not the best solution but it helps and if you're lucky it'll last a while...
what voltage did you up it to? so basically in blisz firmware you selected that board and only upped voltage on that one? and it came back from being disappeared ?
man ive got 2 units doing the same thing (one board on each unit gone and log shows 0 asics)
i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL
and the board I got sent back has missing o's ( 9 to be exact) so instead of like
oooooooo oooooooo
it shows
oooooooo oooo
great repair service
.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN
i had this issue a few weeks ago on another board and I sent it to the US facility and got it back repaired.. but now a different board is gone on each unit LOL
and the board I got sent back has missing o's ( 9 to be exact) so instead of like
oooooooo oooooooo
it shows
oooooooo oooo
great repair service
.. so now ill attempt to send the hash boards that are now disapearing and see what happens.. not sure if i should send back the one with missing chips AGAIN
geeze...that sucks. Was it Bitmainwarranty.com that you sent it to? Also, did you go through Bitmain's ticket/support system and then they told you to ship it there, or you just paid to have the US facility fix it since shipping to and from China would take too long?I had the same issue and it's really annoying! But I was able to solve it somehow by setting this board to higher voltage settings - and I finally got rid of the problem.
I know it's not the best solution but it helps and if you're lucky it'll last a while...
Warranty return is almost pointless when it comes to bitmain it will take you six months to get it back
Wonderful....
Assuming I'd have to pay shipping back to china, it would take a while for the D3 to pay back the shipping costs even if they fixed the board immediately. I guess it would be worthwhile then to take it apart and see if there is any way I could fix it myself.
open repair with bitmain, for US customers you ship to their US facility in CA
Thanks! I'm glad having it repaired in the US is an option. That should save enough on shipping costs to make it worthwhile to get it fixed. About how long did it take to get back?
takes a couple weeks
no after emailing barbara she walked me through the process of shipping the individual board
shes their tech support person that replies to emails
Jump to: