|
Still... 56J/TH vs. BItmain's claim of ~40J/Th (29% less power).
Can't competitively buy anything compliments of the Trump Tax, and refuse to buy anything from Bitmain ever again, so guess I'll just have to wait for a power competitive product. *sigh*
|
|
|
|
At some point you should be seriously scheduling this. I got an independent report from a miner that reached 78t/w on S9s using BraiinsOS. You have a serious profit incentive to do so... And the longer you take, the more you lose.
I've come close to that number three times using the firmware-that-shall-not-be-named (or my post will get deleted, which it likely will anyhow): 550MHz at 8.0V yielded 11,486GH/sec using 905 Watts at the wall for 78.8 J/TH 475MHz at 8.2V yielded 10,300GH/sec using 800 Watts at the wall for 77.7 J/Th 475Mhz at 8.1V yielded 10,100GH/sec using 775 Watts at the wall for 76.7 J/Th - I was shooting for 75J/TH but never made it. Note that only a few of my S9s can pull 550Mhz at 8.0Vs off, most have at least one hash card that simply needs more voltage. 550MHz at 8.2 volts is generally stable on most 14TH machines, with an rare but occasional card needing 8.3V to avoid auto-tuning significant numbers of chips to a lower frequency. 8.3V is pretty commonly needed on my 13.5TH machines, and 8.3-8.5V on my 13TH machines (later batches, not the original early batches). |
|
|
|
Here is an update regarding the S9 March 2019 firmware.
as far as the firmware goes, all of my gears have been running smoothly without an issue, temps are fine, hashrate reported by the pool is good, nothing really to complain about.
but as far as the downgrading of the firmware, i have tried every possible solution at my disposal with no luck, not that i "need" to flash another firmware, but i don't like that fact that i have to be stuck with this firmware. it is really annoying.
I have contacted Bitmain, they were pretty straight forward and said there is nothing they would about it, in other orders they said "you have to live with it".
Which is not true. You can downgrade via the sdhc card as outlined at the Bitmain site. We have down well over 20 downgrades without a hitch, more almost every day. https://support.bitmain.com/hc/en-us/articles/360019493654-S9-series-S9-S9i-S9j-S9-Hydro-Control-Board-Program-Recovery |
|
|
|
That sucks. Considering how it's possible to design an ASIC miner for any kind of PoW algorithm, decentralized mining could be just a dream. If a cryptocurrency which claims to be ASIC-resistant becomes extremely popular, there's nothing stopping manufacturers from devising their own ASIC machines. Of course, ASICs greatly strengthen the security of Blockchain networks, but their biggest flaw is that they leave the small miners out of the equation. I believe that CPU-only mining is the only way to go towards being decentralized in any way possible.
Despite this, it seems that only yescypt coins are CPU-only mineable (for now). That leaves us with Cryply as one of the best (if not the only one) CPU-only mineable coins within the crypto space. Aside from that, there's the option of PoS coins which are much more accessible than PoW, IMO. But their security is highly questionable relative to PoW coins. :-\
What about big memory coins, like IMACredit use to be? It was n-scrypt based with N=16 requiring 16MB of memory per thread back in 2014. The best scrypt ASICs back then (like the advertised but never delivered GAW Vaultbreaker) could only handle N=14. IMACredit was tested to work with an N up to 20, although that reduced it to hashs per hour back then instead of hashs per second. It is my understanding that most ASICs excel because of the parallelism they have, with each chip running lots of threads. Use an algo that eats memory and the ASIC becomes impossibly expensive, since memory is not cheap. Right? |
|
|
|
Electricity Fee $ 48.50 = $0.0970/T/Day × 50T × 10Days
Says bitdeer site. These guys are crazy. Its almost like a kickstarter in disguise if you really break it down.
Taking cost of production into consideration this is insane.
$0.0970/T/Day Currently 1TH a day makes about $0.20- a day right?
let me check that More-or-less, yes, my miners are showing about $0.20/TH/day right now of earnings, a lot less than that in profit of course. But your spending money up front and buying a multi-month contract. As difficulty changes every 2 weeks, the longer the contract, the higher the risk. For instance, using rough numbers, in 2017 the difficulty rose by 7X. If you bought their 1 year contract at $0.0705/t/day, that would start out as $0.13/day in profit, and drop to $0.04/day in loss by the end of the year. Obviously rough math, but I think it illustrates the point. |
|
|
|
The best I was able to do on the 851 is 102, I was able to get 94 a few firmware versions ago.
I might be able to get better as I haven't gone to the lower limits of the frequencies yet.
Make sure your running the new April 04th 2019 firmware in LowPower mode. |
|
|
|
Wanted to share my early experience with this new Pi firmware and matching MMC update. FYI: Download from https://canaan.io/downloads/software/avalon841/Right order appears to be to upgrade your Raspberry Pi first using system->flash firmware and specifying the .img image downloaded. After that, use status->cgminer configuration and select LowPower mode Then use status->mmupgrade to load the .mcs file downloaded. Based on a single test, prior to using this firmware one of my 841s used 1285Ws to perform at 13.3TH/s for an efficiency of 96.4 J/TH. After upgrading and selecting LowPower Mode, the same 841 is using 750Ws to perform at an average of 9TH/s for an efficiency of 83.3 J/TH. This brings the 841 into alignment with Bitmain S9s running their 2019 firmware in terms of efficiency. I'm guessing the 841 is NOT using ASIC Boost. If it could, the numbers would presumably improve more. Has anyone else seen different results or tweaked beyond this? |
|
|
|
Maybe it won't affect most folks directly. But the precedent should still cheese us off.
And it has... I refuse to by any new Bitmain gear and have been removing the 2019 firmware as I do annual maintenance on machines. |
|
|
|
The only valid reason IMO for wanting access is to fix the API access, but you can get around that also by changing the software to use what is available.
If your miner needs rebooting via the API every few hours, then there's something wrong with the miner.
SSH is also very handy for issuing "poweroff". Since S9s have no indicator function, powering off a miner via SSH allows you to locate it, or a batch of "its", simply by looking for the S9s that do not have a blinking green light. |
|
|
|
I'm sorry i didn't catch this earlier. DO NOT upgrade to Bitmain's firmware from 2019, it removes SSH access!!!
Ah... Yeah... Going through the rather time consuming process of resetting via SD-Card now. At least it gives me an excuse to clean each machine.
Have all the troubled 13TH Antminers working again. Key was to boost the voltage up a bit per card. Didn't have to do that with the 13.5s or 14s, but it was a regular event on the 13s. Oh, for what its worth: while I had my workbench setup for recovery, I grabbed a stack of "broken" S9 controllers. Wanted to see if they would respond to being reset via the sdhc card. Of (6) tried, all reset without problem. I now have (2) of them running 14TH S9 that burned up their controllers during a snow storm last November. (2) of the others had real problems: one wouldn't bring up the ethernet adapter, the other would not recognize a fan as existing (fan we running, but I'm guessing it couldn't sense the speed. Fan is working fine with another controller.) But still, managed to at least rescue 2, and the other two are maybes. |
|
|
|
|
Its not pool related - I have over 70 other 13.5TH and 14TH S9s mining against the same pool without issue.
|
|
|
|
Here is the same machine without LPM and LPEM enabled.  Short form: It behaves fine. Tried just enabling LPM mode, and the unit works fine. Been watching it since it rebooted with both LPM and LPEM enabled. Hashrate started out at a respectable 9TH, but within 15 minutes was down to 5TH and dropping. |
|
|
|
Tried the "do it quickly after IP Button" approach using Chrome (Windows 7 though) without luck, but thanks for the reference. Trying the SD-Slot now.
Been running for a few days now. Firmware seems to be reliable on 13.5TH and 14TH machines, but having problems with most of my 13TH boxes. This is typical:  Any clues on what might be happening or how to get their hashrates back up? 7 of my 10 13TH boxes are doing this, 3 appear fine. |
|
|
|
Yes, all three fail. All three do, however, reset the mining pools back to Bitmain defaults (which isn't a bad way to know what one ties did take). I have a ticket into Bitmain requesting a procedure to allow me to backlevel to the November release. Think I'll try just going back to December and see if it allows that. Update: Nope, the 1218 firmware results in the same "Cannot find signature" error that other previous releases I've tried die with. |
|
|
|
|
Hmmm, have to think about this. I actually changed the default pools (which requires SSH) PRIOR to upgrading the firmware, so perhaps not. Most of these machine have been unplugged since last November and had old pool choices. Knowing the machines would be rebooted when I changed firmware, I elected for change the pools first. So its possible SSH has been disabled since upgrading.
Rebooted does NOT enable SSH. Reverting via the web interface also fails after a few moments with a "Cannot find signature" error, at least with the 1117 and prior versions. It will let me reflash the current version.
I've notified Patrik over at Awesome Miner, since this seriously cripples his software with S9s. Hoping he has come across this and has a work around (like they switched SSH ports or something). Hmmm, a portscan of a miner could prove interesting. Back with those results later.
Update: Only 3 ports now open:
80 - HTTP web interface
4028 - Standard API port for monitoring
6060 ???
Bitmain ticket opened.
|
|
|
|
Been running this fw in 21 miners for 1 month and no issues so far, I recommend it  Any problems SSHing into your boxes? Other than 2/~90 I had problems with last night, all allowed it yesterday, but this morning, they are all blocking it. This is hobbling Awesome Miner.
Based on 12 hours of running, I'm happy to confirm the need to reboot is gone. I'm not seeing ANY dip in performance over that time period. However, the disabling of SSH functionality, and apparently the ability to downgrade, even through the web app, is rather concerning. The Bitmain page indicates this release: 2.Add security firmware feature, enhance antminer security ability
I suppose this is what they mean by that. |
|
|
|
This isn't any suggestion but more of a question on the other S9's. Does ssh work one the others?
Yes, its works on all but two, so (88) Yes. (2) No. This prevents Awesome Miner from having configuration access btw. And since I can't SSH in, I can't manually add access. Update: This morning all the upgraded machines are refusing SSH access, which means I have no way to remotely poweroff, and tools like Awesome Miner can't change pools. |
|
|
|
Think I read on the Bitcoin Support page that Low Power Enhanced mode implies Low Power Mode.
Having a bit of a problem with a few machines that previously were back leveled and set with fixed frequencies. Those don't work well with the new system.
ok, updated about 90 machines, most went without issue. ONE is running at a fixed frequency, 600 MHz, and I can't seem to get it to down speed even though Low Power Enhanced Mode is toggled. Any suggestions? Should I just manually downclock it via minerAdvanced.cgi? Have another one that I can't SSH into. The web interface works, but SSH does not. Any suggestions? |
|
|
|
|
Show Posts
