 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
I just tried this and after building up to normal speed, the hashrate dropped back down to about 1.3GH/s a few minutes later. I checked the frequency and it was set as expected. The hashrate started increasing again, but quite slowly, so I decided to reflash to the previous firmware for now. Have you tried it yet? I've just updated the thread with a 24hr comparison of my previous OC @ 262.5 and the HW rate has drastically reduced. I can pretty much guarrantee that this will work for all BM1382 boards, it just depends on whether you want to do it. First, run it at a frequency within the bitmain spec (the black numbers in the last table) with the voltage set. The rate will take a while to settle and will at the very least match the spec rate (expected hash in the last table), but more likely beat it (as I have demonstrated). More important though, is the lower HW rate (and again, do not jump at conclusions after the first half hour, let it run for a few hours). If you feel the HW rate is low enough (even not and just feel like it!), turn up the freq within that voltage range (this is mine through my tests not bitmain's) and you should be OK. For the 262.5 freq test, the voltage setting is 0750, which is the datasheet voltage for freq 250. Start with 250 and I bet you'll get very few HW errors and a good hash speed, then if you feel like it, turn up the freq and watch your hash-speed increase, with still few HW errors. Thanks pekatete. Much appreciated. I'll try it again over the weekend.  Cheers. |
|
|
|
I just tried this and after building up to normal speed, the hashrate dropped back down to about 1.3GH/s a few minutes later. I checked the frequency and it was set as expected. The hashrate started increasing again, but quite slowly, so I decided to reflash to the previous firmware for now. Have you tried it yet? |
|
|
|
Wow,
We went down to 7.6 PH/s from 9.8 PH/s. Now we're back up to 8.5 PH/s. Sweeeeeeeeeet!
Must have been someone renting some cloud having power that had us up to 10 PH/s earlier.
A mighty big cloud!  |
|
|
|
Anyone else noticed the jump in pool Hashrate ?
What's the concensus --- is this poolhoppers or new hashpower ?
That has been steady to ~10Ph/s for the last few hrs, so I'm certain to a reasonable degree they are here to stay and not hoppers! Having said that, I can not see the supposed luck they could have brought with them as we've been at this block since forever! The extra hash power never seems to translate into quicker blocks, does it? |
|
|
|
Only bummer part is having your NEED TO KNOW info is all on different pages now and everything require 1-3 clicks to get where you need to get to.
Beta site displays much more information than old one, so it is nearly impossible to display everything on single page now. Actually new Dashboard has much more sense than old layout and it is mostly the matter of habit. But I agree that things can be still improved, that's why we released it as "beta" and old site is still available. After we get some feedback from our users, we'll definitely tune it up even more than it's now. I really like the new site myself. By way of feedback and I don't know whether this is even possible, it would be good if the data in the Rewards tab would update itself in real time. It would avoid having to refresh manually when we keep the page open. Edit: it took me a while to find the current block being worked on. Would be nice if at least some info from the current block was visible under Rewards too. |
|
|
|
Well, that's just too scarily accurate! |
|
|
|
Gotta love natural Canadian cooling. And it isn't even winter yet. If you're wondering, temps are showing 0 because S4's temp sensors don't register below 20c. So, how cold is it outside where you are? |
|
|
|
Even with the new cgminer file, my units are doing a little worse than with the previous one. I am guessing I am losing around 10-14 GH/s per device, which is not bad but when you have 11 of them it makes a slight difference.
Do you have the latest firmware on them? i had exactly the same experience with my batch 6 units and reverted to the stock cgminer, however (again as is documented in this thread), when I updated to the latest firmware, which I had to do when upgrading my S1's, I get the same result as the stock, or slightly better, but with the security flaws plugged. Yeah I have the latest firmware, it is dated 8/26/2014. My issue is probably the 5 batch 1 miners I have, even though some of my batch 5 units are a little slow as well. Yep, the earlier batches do not seem to be up to it. I suspect it is due to their poor temp handling and suggested to someone to re-do their heat paste; Though he had some good results using a conductive compound, he re-applied using a non conductive paste and has not reported their results. With several units .... that would be a day's work! Worth it? Not sure. Hi m8, not sure if it's me you're thinking of above, but I did have my best results with Arctic Silver conductive paste and my latest application of Zalman paste was a lot of effort for not much reward. I've just bought some Innovation Cooling IC Diamond 7-Carat thermal compound, so will give that a whirl when I have a chance. Still deliberating about doing the big central heatsinks - presumably this involves removing the blades? Is that a straightforward process? I get funny results with my asics at different frequencies: one 'x' always shows up at 225, but not at higher frequencies and similarly with some of the others, so although I always get an 'x' at higher frequencies somewhere, it's often in different places. Also, my hashrate is rubbish at higher freqs anyway now, it only goes quicker at 231 and that doesn't seem to last long. I tend to keep it at the default 118 now and main task is to stop my hashrate dwindling away, which gradually seems to happen on my problem s3. BTW, I've upgraded to ck's latest cgminer (4.6.1-141020) and seems ok so far - no restarts, etc. I also removed --queue 4096 and added --lowmem in the cgminer startup script, as recommended by ck. Yes moss, that was a reference to you, and thanks for updating us. Bummer about having to run at stock freqs ... Removing board from the heatsink does not involve much more than removing the top heatsink, just another set of screws then you slide it off (you do not have to unscrew the heatsinks from the braces). I have not tried adding the --lowmem switch yet as I do not readily know the process, but will dig around tonite (or tomorow) and try it. Thanks again for keeping us up to date. Hi m8. Another little update... I tried to do the big heatsinks between the boards, but could not remove one of the screws (as you know, they go through the board itself) whatever I tried - the others were very tight too, but I managed those. In the end, I gave up on that part of the plan. However, the rest of the plan seems to have worked well: I redid the outer heatsinks using Diamond 7-Carat thermal compound and I fitted little heatsinks on the DC-DC converter chips. Since doing that, the problem S3 has sat solidly at 440 Ghash/s for weeks. So a big result (so far...). Edit: Hmmm. My first forced reboot today (19th Nov) of the problem S3 since 'fixing' it. Average hash was heading south, after being rock solid for weeks. Didn't see that coming...  Edit2: Lost my average hash reading (again), so updated to latest firmware to see if that improved things. Ran reliably at 440 Ghash/s until 23rd Nov, when it suddenly stopped hashing and started beeping for 5 minutes. Couldn't find anything wrong via the web interface and it suddenly started working again - back at 440Ghash/s. Other S3 on same router not affected. Don't know what caused that...  |
|
|
|
Actually the duct work would be above our head in the garage tied into the existing duct work that feeds all the vents in the house. It will be a lot easier than one might think. The duct work is already visible in the garage to the eyes. So it doesn't matter to me if it's seen or not. No duct work will be visible in the house. Using existing duct work to feed the heat to the house.
With existing duct work, it's going to make it so much easier. A real opportunity to get even more payback. |
|
|
|
Thanks again for helping out. I couldn't resist! If my posting this offends members, I'll take it down shortly. Just wanted to show y'all what I was up to with my data/mining closet: As you can see, there is still some work to do. Still waiting on several 240V/30AMP outlets to get here from California [Ordered from Amazon]. This means I'm pulling out 5 of the 7 12/2 wiring to replace with 10 AWG for the new 240V/30AMP outlets. You see six (6) different colors of SF Cable, 6ft IEC C14 to C13 Power Extension Cord 10Amp 250V 18/3 AWG SJT. They will be used to plug into two (2) Tripp Lite PDUMV30HV PDU Metered 208V / 240V 30A 6 C19 24; C13 L6-30P Vertical 0URM's. One of them is to the right [Out of the box] and one is on the left [Still in the box]. The bottom shelf and the shelf above it will have to me removed temporarily to install the Tripp Lite PDU's on the back wall. The shelves will be repositioned [When re-installed] to allow enough space between the shelves to be able to turn S4's onto their sides to help me place more S4's in this closet than previously intended [25 S4's instead of 20]. [If y'all think they should not be positioned onto their sides, please let me know and why?]There is a 14 inch Can Fan Max with 1820 Cubic Feet per Minute (CFM) of suction for this 122 cubic feet closet. You also see a 16 inch return near the ceiling in the back where the 14 inch Can Fan Max is connected feeding into the garage. [Working on duct work to feed the hot air to the outside from the garage.] This is a youtube video on the 14 inch Can Fan Max: https://www.youtube.com/watch?v=4DxbWXo4dF4You also see an 8000 BTU Air Conditioner installed in the back wall coming from the garage. It is quiet and a helpful addition to keep this closet cool. You will also notice a 16" x 25" filtered grill in the closet door in the second picture. This allows the 14 inch Can Fan Max to pull in TONS of cool air from the recreation room downstairs. A window is open just to the right of that closet door in the recreation room to allow the fan in the closet to suck cool air into the closet. Enough air is sucked into this closet that it will blow your shirt over your head if you were standing in the closet without your shirt tucked into your pants. Hollow square metal rods will replace the wood bracing I have underneath the shelves I have soon. All wiring will be neater as well once the PDU's are installed and shelves are re-installed after proper spacing. A little bit of history with more photos [even of what is going on behind the closet wall in the garage] of what I've been doing through trial and error can be found here: https://bitcointalk.org/index.php?topic=766998.40I'm remodeling my recreation room. So, don't mind the base molding that has yet to be nailed on, primed and painted. re: the metal bracing, I'm just wondering whether you ought to consider fitting a central vertical support pillar on those shelves as well (from top one down to floor)? Also, is there any way that you could duct all that hot exhaust air around the building, instead of just into the garage? It would save on your heating bills in the winter and you could have a by-pass duct straight to the outside air for use in the summer (no need to run the aircon unit then). I appreciate that it's easier said than done and ducts aren't the nicest things to look at in living-rooms (perhaps you have ceiling and wall voids to hide them in), but it seems such a waste of valuable heat. |
|
|
|
I'm interested in tinkering with turning a couple S3's into space heaters now that it's getting colder.
The aim would get to get two of them quiet enough to run in a bedroom or office.
Could someone experienced offer any insight if stacking a few non PWM low speed fans in sequence, on each end of the miner, work to push enough air through the unit more quietly ? Any recommendations for fans to that end ?
Not sure about going for non PWM fans - surely they'll just run flat out and be even more noisy? On my S3s, I use a Corsair PWM SP120 High Performance 120mm on the inlet and a Thermalright PWM TY143 140mm on the outlet (screw holes fit 120mm spacing). This makes the S3s much quieter than with the standard fans. Temps are up by 1 or 2 degrees (those standard fans are powerful things) but it's an acceptable trade-off. Mine are in my office and this has been well worthwhile for me. Not sure if I would want them in my bedroom though - any fan will sound mighty loud in the wee small hours! You could always try doing just the one S3 to start with, to see if it gives the level of noise reduction that you want. |
|
|
|
The fee is due based on the transaction size, so if you need to transfer 5 BTC from small payouts 0.01 each you need to include 500 inputs in that transaction, which will very likely take more space = bigger fee
Also if you get a payout of 1 BTC, you can spend it (without fee) immediately on the next day, but if your payout is 0.1 BTC you will need to include a fee if you want to spend it before 10 days and for 0.01 it goes to 100 days
Many thanks for the explanation. It hadn't crossed my mind that it worked like that, but of course, it has to. I've adjusted my Slush send threshold accordingly. |
|
|
|
Why would you want so many tiny payouts? You are going to end up paying higher fees when you go to spend it. I get payouts once per week or twice per month, And usually don't pay any fees when spending it.
Hi m8, I wasn't aware of this. Do these higher fees on spending result from extra verification or something like that? |
|
|
|
Bitcoin Difficulty: 35,985,640,265
Estimated Next Difficulty: 39,290,252,296 (+9.18%)
Adjust time: After 487 Blocks, About 3.0 days
Hashrate(?): 310,130,836 GH/s
Block Generation Time(?):
1 block: 8.9 minutes
3 blocks: 26.7 minutes
6 blocks: 53.4 minutes
Updated: 22:25 (6.3 minutes ago)
It's now up to an estimated 9.92%.  |
|
|
|
Well, no blocks found today (UTC time) and current one is at 17.5 hours. BUT, the 1 day pool luck is at 186%. |
|
|
|
I'm still pissed because nobody laffed at my joke the other day> Looks like I deleted it Was it the one about the Ferengi wormhole? I replied to that... |
|
|
|
Even with the new cgminer file, my units are doing a little worse than with the previous one. I am guessing I am losing around 10-14 GH/s per device, which is not bad but when you have 11 of them it makes a slight difference.
Do you have the latest firmware on them? i had exactly the same experience with my batch 6 units and reverted to the stock cgminer, however (again as is documented in this thread), when I updated to the latest firmware, which I had to do when upgrading my S1's, I get the same result as the stock, or slightly better, but with the security flaws plugged. Yeah I have the latest firmware, it is dated 8/26/2014. My issue is probably the 5 batch 1 miners I have, even though some of my batch 5 units are a little slow as well. Yep, the earlier batches do not seem to be up to it. I suspect it is due to their poor temp handling and suggested to someone to re-do their heat paste; Though he had some good results using a conductive compound, he re-applied using a non conductive paste and has not reported their results. With several units .... that would be a day's work! Worth it? Not sure. Hi m8, not sure if it's me you're thinking of above, but I did have my best results with Arctic Silver conductive paste and my latest application of Zalman paste was a lot of effort for not much reward. I've just bought some Innovation Cooling IC Diamond 7-Carat thermal compound, so will give that a whirl when I have a chance. Still deliberating about doing the big central heatsinks - presumably this involves removing the blades? Is that a straightforward process? I get funny results with my asics at different frequencies: one 'x' always shows up at 225, but not at higher frequencies and similarly with some of the others, so although I always get an 'x' at higher frequencies somewhere, it's often in different places. Also, my hashrate is rubbish at higher freqs anyway now, it only goes quicker at 231 and that doesn't seem to last long. I tend to keep it at the default 118 now and main task is to stop my hashrate dwindling away, which gradually seems to happen on my problem s3. BTW, I've upgraded to ck's latest cgminer (4.6.1-141020) and seems ok so far - no restarts, etc. I also removed --queue 4096 and added --lowmem in the cgminer startup script, as recommended by ck. |
|
|
|
how i can check with pytty what version of cgminer i have?> /usr/bin/cgminer-api Quite a bit of output from this, so you'll have to scroll back up the screen, but it's in there. or u can do the below and see the version easier. cgminer-api | grep cgminer fyi no /usr/bin is needed since cgminer is in the executable path root@antMiner:~# echo $PATH /usr/bin:/usr/sbin:/bin:/sbin Yes, that's quite a lot better - thanks m8. |
|
|
|
how i can check with pytty what version of cgminer i have?> /usr/bin/cgminer-api Quite a bit of output from this, so you'll have to scroll back up the screen, but it's in there. |
|
|
|
^ that last invalid block may have been my fault  I had ordered a new Monoprice gold plated usb cable from Amazon and the minute it arrived at my house I plugged it in between my Rockminer and raspberry pi and immediately knew something was amiss. The first evidence? The small wormhole that appeared in our living room, right next to our holstein cowhide recliner. Peering into it I could discern the snarling face of a Ferengi, likely somewhere out in the Gamma quadrant. Then things got really hairy. Brad shouted from the kitchen that he was detecting elevated tachyon levels from our Vita-Mix, so we immediately diverted power to our forward Ronco Rotisserie array. Set it and forget it, indeed. Still no go. The wormhole continued to grow. So I did what anyone in this rather awkward situation would. I recalibrated our George Foreman Grill (about 10 picometers), ejected the warp core from our Dyson Ball Vac, and pulled back the freq's on all the antminer s3's in the house. Bingo. No more worm hole. I guess what I'm saying is that you can use this cable, but only if you have substantial Star Fleet training. http://www.monoprice.com/Search?keyword=5447Sorry to agree, but you ought to know better than to buy a Monoprice gold plated usb cable from Ferengi Amazon. It sounds like you came out of it ok, but I can't help feeling that wormhole event was a cheap Ferengi party trick to divert your attention from the temporal excursion that was undoubtedly the main target of this infiltration. The elevated tachyon levels provide ample evidence of this and if you check your security cameras, you will likely find that your S3s seemed to vanish for a split second, but were really being beamed several years back into the past, where they spent a few hours mining at least a million BTC into a Ferengi wallet. It's a clever trick to earn a bit of extra latinum and if they hadn't tried to control your Vita-Mix, they might have gotten away with it, but those Ferengi just can't resist a nice marshmallow smoothie... |
|
|
|
|
