 Show Posts
|
|
Pages: [1] 2 »
|
FTC pool down from 3 am UTC.
Phew! Same here UK. Showing last shares as 3am on LTC and 2:59 on PPC. Woke up this morning to beeping from the cellar and a noticeable "coolness" to the air. Thought it was just me! |
|
|
|
Hi guys Has anyone had any trouble updating cgminer in batch 9. for some reason after updating mine stop mining. also when i ssh into them and check the version I get "permission denied" all my other ants updated fine from other batches. heres a screen shot of how I did the update did I miss anything root@antMiner:~# cgminer -V cgminer 3.12.0 root@antMiner:~# cd /usr/bin root@antMiner:/usr/bin# mv cgminer cgminer.bak root@antMiner:/usr/bin# wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer Connecting to ck.kolivas.org (193.19.136.183:80) cgminer 100% |*******************************| 490k 0:00:00 ETA root@antMiner:/usr/bin# reboot root@antMiner:/usr/bin# Write failed: Broken piperoot@192.168.1.109's password: BusyBox v1.19.4 (2014-06-29 16:21:38 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _| |_______|| __|_____|__|__||________||__| |____| |__| W I R E L E S S F R E E D O M ----------------------------------------------------- BARRIER BREAKER (Bleeding Edge, r38031) ----------------------------------------------------- * 1/2 oz Galliano Pour all ingredients into * 4 oz cold Coffee an irish coffee mug filled * 1 1/2 oz Dark Rum with crushed ice. Stir. * 2 tsp. Creme de Cacao ----------------------------------------------------- alias: -l not found root@antMiner:~# cd /usr/bin root@antMiner:/usr/bin# cgminer -V -ash: cgminer: Permission denied root@antMiner:/usr/bin# any help would be great cheers Hey The error - Write failed: Broken... Usually happens when ssh times out. If that's the case the download may not have completed. Try renaming the cgminer.bak file to restore the original version. If it works you could try the update again  |
|
|
|
Hi all,
Hope someone can help in response to a problem I'm having with an RMA. I'd been through all the diags with Tim from Bitmain and he'd agreed to do an RMA for one of the hashing boards as its only hashing at 170-176Gh, the other is fine. I'd explained to Tim that I'd bought it from a reseller and was happy to purchase a board from them and then send the other back for a refund.
They advised that there was a 0.66BTC charge (I know!) for a hashing board but would be refunded when the other is returned so I was happy to do this. I filled the form in without the order number and reiterated that I bought from a reseller and I thought they'd be ok as I was paying for the board. But my request got rejected at the final hurdle and was told to go back to my reseller.
Sooooooo I emailed my reseller who advised that I need to send a screenshot in, which I did. It shows the unit on for about 14 hours with a hashrate of 387Ghs at stock speed.
The reseller has now been in touch and advised me that Bitmain are now refusing to do an RMA as it's within a +/- 10% threshold!
Anyone had anything similar happen? So frustrating!
Thought I'd post an update. My reseller (Briztech) has been awesome with this. He went back to Bitmain with the email trail I had from Tim and they've now agreed to do an RMA :O) sent the board back last week(weds) and am awaiting replacement. Thanks Briztech and Bitmain :O) I sent the board back to Bitmains UK distribution centre, anyone know how long they take to do an RMA? |
|
|
|
|
Hi all,
Hope someone can help in response to a problem I'm having with an RMA. I'd been through all the diags with Tim from Bitmain and he'd agreed to do an RMA for one of the hashing boards as its only hashing at 170-176Gh, the other is fine. I'd explained to Tim that I'd bought it from a reseller and was happy to purchase a board from them and then send the other back for a refund.
They advised that there was a 0.66BTC charge (I know!) for a hashing board but would be refunded when the other is returned so I was happy to do this. I filled the form in without the order number and reiterated that I bought from a reseller and I thought they'd be ok as I was paying for the board. But my request got rejected at the final hurdle and was told to go back to my reseller.
Sooooooo I emailed my reseller who advised that I need to send a screenshot in, which I did. It shows the unit on for about 14 hours with a hashrate of 387Ghs at stock speed.
The reseller has now been in touch and advised me that Bitmain are now refusing to do an RMA as it's within a +/- 10% threshold!
Anyone had anything similar happen? So frustrating!
|
|
|
|
I know the feeling. I was also debating buying S3s but now holding to see what happens. I'm still mining with 8 S1s and they're down to pulling in about 1 BTC a month. At my electricity cost of $0.13/kWh this cost me about $340/month. So I'm still making a small profit at the current BTC price. May upgrade using the kits, but not worth it yet. Waiting to see what happens.
You really need to look at the pencil mod of your S1's I did my 9 miners and now they mine at only 140GH but use @ 200 watts less apiece. So now my electric cost (.125kw) is about .51 day each. You will make more profit doing so. Then this also freed up PSU to run some S3's Not sure what you mean by pencil mod? I guess you mean lowering the frequency. I'll PuTTY in and try that. Thanks for the advice. It's this - https://bitcointa.lk/threads/guide-undervolt-antminer-s1-1-19w-gh-at-the-wall.286480/I've done it on my S1, works great. As aurel57 mentioned it'll increase your profit margin |
|
|
|
wouldnt running 340 watts at the wall constantly 24/7 cost about $5 aday to run, which is what these are making at today difficulty so why bother?
WOW! cost less than $0.50 a day here That's like $0.60 per Kwh! Can't be right. I'm in the UK and we're on a "cheap" tariff £0.12/$0.20 per Kwh (£0.97/$1.63) and I make about £4.60/$7.70 per day in total at the current BTC value. But I do it because its an extension of my computing/electronics hobbies |
|
|
|
Has to laugh at the s1 upgrade kit why would ya put all the parts in the kit to upgrade it to an s3 minus the 2nd fan when the s3 has the second fan there for a reason,,,, That very odd and strange not to have the 2nd fan in the upgrade kit
The parts list didn't include the case cover either. I could cynically suggest that the case cover has cosmetic value only. The omission of the second fan either demonstrates that the second fan is not really essential, or that Bitmain think that anyone upgrading would have previously overclocked their S1 and would therefore have fitted a second fan already. My vote goes for it being superfluous unless you overclock. The Bitmain website now includes a fan on the list  I've considered running it without the cover just to see if it helps with the cooling on mine as I can only get it to hash stably at 212.5. My thinking behind this was the location of the control board which is now above the heatsinks and I was wondering if it was overheating, further testing required! |
|
|
|
I have G-750 SeaSonic 80 gold powering up 2x S3 miners. After couple of hours, one of the antminer started getting some HW errors. Is this because one of the blades i connected with daisy chain?
what are some hw errors 5 10 100 1000 10000 1000 errors a day are not too bad. both have been running for 13h+ now, first one has 57 HW and second 166. ---------------------------------------------------- at atledenin you have the formula inverted I think but I just woke up LOL --------------------------------------------------- you are fine you are more then 99% good. take the formula hw / diffA +diffR +HW if it is under .005 you are better then 99 percent 926/23,716,864+32,744+926 = 926/23749534 = .000003899 x 100 = .0003899 that is .9996101 percent good see screen shot  How did you know, lol zzzzz |
|
|
|
I have G-750 SeaSonic 80 gold powering up 2x S3 miners. After couple of hours, one of the antminer started getting some HW errors. Is this because one of the blades i connected with daisy chain?
what are some hw errors 5 10 100 1000 10000 1000 errors a day are not too bad. both have been running for 13h+ now, first one has 57 HW and second 166. You can use this formula to calculate percentage of hardware errors, I generally consider <=0.3% an acceptable level when hashing at stock. (HW + DiffA + DiffR) / HW * 100 = %HW Ooops: HW / (HW + DiffA + DiffR) * 100 = HW% |
|
|
|
Well I'm going to try to overclock my s3 with just one 500w evga 80 plus.. Hopefully it works out!
Should be ok, quote from the EVGA page - "Supporting 40A on a single +12V rail" As far as I understand the S3's use about 28-30A at stock, so there's some headroom. I'd start at 225 and check the cables to see if they're getting toasty Rinse and repeat |
|
|
|
I like to tell another thing, my 2 PCI-E Power cables to S3 were a little hot.
My S3 hashrate was not stable at the rated 441Ghs but was averaging at 420. I ordered thermal paste.
Before thermal plates were arriving, I tried to plug two additional PCI-E power cables to S3.
The Antminer S3 is running at stock clocks 218.75 and PCI-E power cables are cool now.
The main reason for this post is to report that the miners stabilised at 441. Earlier it was 420.
Two thing I'm pointing out,
1. The miners plugged in continuously for 4 or 5 days and seems like it was running-in and stabilised at-last at 441.
2. Plugging the all four connectors even if you are not overclocking will some way help you.
Similar experience here. S3 clocked down to 212 as it would not stabilise at stock. Finally decided last night to have a fiddle as I had a bit of time on my hands. After removing the cover I did the following - Straightened out the heatsink fins as some were bent close to where the screws were. Tightened up one screw which was loose on one heatsink. Pushed the cables to make sure they were seated properly, they all looked ok, no "give" when pushing. Put the cover back on and instead of putting the cables into the sockets closest to the ethernet port I decided to try the other two. Hooked it back up, checked the results after a couple of hours and it was hashing at 420. Decided to put the clock back to stock and it's been hashing at 440 for the last 24 hours! Really strange as the only thing I felt I really did was swap the cables. Maybe it just needed a bit of TLC and me stroking its internals made it happy! OK so I'm back to square one with this! Went back to fluctuating between 380-410 after about 72 hours on stock setting. Reset it back to 212.5 and it's hashing steadily at 410 now. Just had a thought, has anyone ran one without the cover on? I'm thinking I might try it this weekend, wondering if the controller is getting too warm as its directly above the inside heatsinks and not to the side as with the S1. I understand the cover is required for decent airflow across the outside heat sinks so I'll either make some sides or blow air from another couple of fans on them. One of my miners seems to work best if I leave it running for long periods. Although, that one also seems to need anywhere from 3 to 8 reboots to come up strong, meaning that within 10 minutes of the reboot it hits the 440ish mark and has no x's. If I take the effort to repeatedly reboot until I seem to hit a good start it will chug along for days with decent hash rate. My other miner works best with frequent reboots because when I leave it running for extended periods it drops to sub-400 range and even if it was doing 450+ for hours before that, it eventually brings the average down sub-400 over a longer time. That one has a cron job that reboots it every 6 hours and that seems to keep the long term hash rate at 450ish. These are fickle little machines. I ran them both without the cover for more than a week but the first one I mentioned above now has the cover back on. The chips at the end of the second chain would sometimes go to x's either right after a reboot or within 5 to 10 minutes without the cover. Checking with my hand near the heatsinks (with cover off) I could feel that the end of the heatsink on one side really was getting warmer and not getting good air flow. These are both in a climate controlled server room with other fans blowing on or near them but even so this unit seems to like the cover on for those rear chips on that one side. My other one (the frequent rebooter) runs cover off and I almost never see x's on the chips. Full disclosure: the frequent rebooter is set to 225 freq and the one that does not like reboots is set to 250. Both also have queue set to 2 which keeps them busy without maxing the load levels. Thanks for the tips and the info around running with the cover off. I did have a cronjob reboot set for every 12 hours, think I'll try rebooting it a couple of times at stock freq as you've mentioned, see if I can get hashing back at 440! |
|
|
|
I won't encounter any issues putting a OC'd and a stock Antminer on the same power supply? Will the 2 different power draws effect anything? I don't think it will, but I am a noob and trying to help out a friend, I don't want him to blow his house up.  It won't affect anything, as long as it can supply the right amount of amps @ 12v it'll be fine. Now if I remember rightly you need around 30 amps for each miner on the 12v rail. This is not the supply from the wall but what the power supply will push to the miner. Check the specs on the power supply there should be a sticker with the info on it. Best type to use are the ones that have a single rail for 12v. |
|
|
|
I like to tell another thing, my 2 PCI-E Power cables to S3 were a little hot.
My S3 hashrate was not stable at the rated 441Ghs but was averaging at 420. I ordered thermal paste.
Before thermal plates were arriving, I tried to plug two additional PCI-E power cables to S3.
The Antminer S3 is running at stock clocks 218.75 and PCI-E power cables are cool now.
The main reason for this post is to report that the miners stabilised at 441. Earlier it was 420.
Two thing I'm pointing out,
1. The miners plugged in continuously for 4 or 5 days and seems like it was running-in and stabilised at-last at 441.
2. Plugging the all four connectors even if you are not overclocking will some way help you.
Similar experience here. S3 clocked down to 212 as it would not stabilise at stock. Finally decided last night to have a fiddle as I had a bit of time on my hands. After removing the cover I did the following - Straightened out the heatsink fins as some were bent close to where the screws were. Tightened up one screw which was loose on one heatsink. Pushed the cables to make sure they were seated properly, they all looked ok, no "give" when pushing. Put the cover back on and instead of putting the cables into the sockets closest to the ethernet port I decided to try the other two. Hooked it back up, checked the results after a couple of hours and it was hashing at 420. Decided to put the clock back to stock and it's been hashing at 440 for the last 24 hours! Really strange as the only thing I felt I really did was swap the cables. Maybe it just needed a bit of TLC and me stroking its internals made it happy! OK so I'm back to square one with this! Went back to fluctuating between 380-410 after about 72 hours on stock setting. Reset it back to 212.5 and it's hashing steadily at 410 now. Just had a thought, has anyone ran one without the cover on? I'm thinking I might try it this weekend, wondering if the controller is getting too warm as its directly above the inside heatsinks and not to the side as with the S1. I understand the cover is required for decent airflow across the outside heat sinks so I'll either make some sides or blow air from another couple of fans on them. |
|
|
|
It is recommended to use a new address every time - for privacy and for security. You can simply reuse the same receiving address but it is not best practice. Lots of people do it though.
Your Bitcoin Core wallet has already generated a pool of (100) addresses for you to use. Every time you hit "request payment" it shows you another one.
So if I post an address on a website and multiple people sent bitcoin to it I'll be OK? I'll get all the coin? 100 addresses? That's insane. That's like going to the bank and them giving you 100 checking account numbers. WTF? I thought it was safe to post and use an address? Rather look at those 100 addresses like you've been given 100 individually coded cheques |
|
|
|
I like to tell another thing, my 2 PCI-E Power cables to S3 were a little hot.
My S3 hashrate was not stable at the rated 441Ghs but was averaging at 420. I ordered thermal paste.
Before thermal plates were arriving, I tried to plug two additional PCI-E power cables to S3.
The Antminer S3 is running at stock clocks 218.75 and PCI-E power cables are cool now.
The main reason for this post is to report that the miners stabilised at 441. Earlier it was 420.
Two thing I'm pointing out,
1. The miners plugged in continuously for 4 or 5 days and seems like it was running-in and stabilised at-last at 441.
2. Plugging the all four connectors even if you are not overclocking will some way help you.
Similar experience here. S3 clocked down to 212 as it would not stabilise at stock. Finally decided last night to have a fiddle as I had a bit of time on my hands. After removing the cover I did the following - Straightened out the heatsink fins as some were bent close to where the screws were. Tightened up one screw which was loose on one heatsink. Pushed the cables to make sure they were seated properly, they all looked ok, no "give" when pushing. Put the cover back on and instead of putting the cables into the sockets closest to the ethernet port I decided to try the other two. Hooked it back up, checked the results after a couple of hours and it was hashing at 420. Decided to put the clock back to stock and it's been hashing at 440 for the last 24 hours! Really strange as the only thing I felt I really did was swap the cables. Maybe it just needed a bit of TLC and me stroking its internals made it happy! |
|
|
|
Every half hr, lol, thats waaaay too often.
Once a day or every 12 hrs should suffice.
is 12,00 * * * * /etc/init.d/cgminer restartthe command for restarting every 12 hours, then? could someone comment if this is OK to put this in <System> tasks instead of ssh-ing? The timing in cron works like this - * * * * * command to be executed - - - - - | | | | | | | | | +----- day of week (0 - 6) (Sunday=0) | | | +------- month (1 - 12) | | +--------- day of month (1 - 31) | +----------- hour (0 - 23) +------------- min (0 - 59) So you could set the reboot for 1am and 1pm by doing 0 1,13 * * * /etc/init.d/cgminer restartYes, you can add it via the web interface. http://en.wikipedia.org/wiki/Cron |
|
|
|
I'm also having the issue with the S3 hashrate dropping off. It generally starts around 435Gh but drops to around 390-400GHs. I'm at work now and I'm looking at my S3 on Slush's pool and I'm currently showing - Total average hash rate in last 60 minutes: 381070 Mhash/s  Has anyone found a solution to this or had word from BitMain? Some units do and some don't, try a lower clock such a 212.5 as others have identified. I have one that runs steady at 218.5 and another that does not like the stock clock but runs fine at 212.5, and is reliable at that speed. I'm also having the issue with the S3 hashrate dropping off. It generally starts around 435Gh but drops to around 390-400GHs. I'm at work now and I'm looking at my S3 on Slush's pool and I'm currently showing - Total average hash rate in last 60 minutes: 381070 Mhash/s Has anyone found a solution to this or had word from BitMain? Some units do and some don't, try a lower clock such a 212.5 as others have identified. I have one that runs steady at 218.5 and another that does not like the stock clock but runs fine at 212.5, and is reliable at that speed. this is the way to go. my 2 units run at 212.5 very well look at my charts solid at 430gh and 212.5 Note that dip was a T-storms caused blackout. gear auto -booted back to normal and 430gh  Thanks guys I'll give that a whirl this evening! Thanks Duce and philipma1957, clocking down to 212.5 works great. Hashing at 410 atm but at least its stable and doesn't end up at 380-390Ghs! Do you think it would be worth engaging Bitmain about this? Would really like that extra 30Ghs! |
|
|
|
I'm also having the issue with the S3 hashrate dropping off. It generally starts around 435Gh but drops to around 390-400GHs. I'm at work now and I'm looking at my S3 on Slush's pool and I'm currently showing - Total average hash rate in last 60 minutes: 381070 Mhash/s Has anyone found a solution to this or had word from BitMain? Some units do and some don't, try a lower clock such a 212.5 as others have identified. I have one that runs steady at 218.5 and another that does not like the stock clock but runs fine at 212.5, and is reliable at that speed. I'm also having the issue with the S3 hashrate dropping off. It generally starts around 435Gh but drops to around 390-400GHs. I'm at work now and I'm looking at my S3 on Slush's pool and I'm currently showing - Total average hash rate in last 60 minutes: 381070 Mhash/s Has anyone found a solution to this or had word from BitMain? Some units do and some don't, try a lower clock such a 212.5 as others have identified. I have one that runs steady at 218.5 and another that does not like the stock clock but runs fine at 212.5, and is reliable at that speed. this is the way to go. my 2 units run at 212.5 very well look at my charts solid at 430gh and 212.5 Note that dip was a T-storms caused blackout. gear auto -booted back to normal and 430gh Thanks guys I'll give that a whirl this evening! |
|
|
|
I'm also having the issue with the S3 hashrate dropping off. It generally starts around 435Gh but drops to around 390-400GHs. I'm at work now and I'm looking at my S3 on Slush's pool and I'm currently showing - Total average hash rate in last 60 minutes: 381070 Mhash/s Has anyone found a solution to this or had word from BitMain? |
|
|
|
I have a bit of a problem. Hoping someone can help, I'm fine with computers but have no clue when it comes to network addresses etc.
To start with, I couldn't change the routers subnet so I went through a direct PC connection. Logged into the Ant fine & changed to DCHP. The Ant still had 192.168.1.99/24 as the IPv4 address at that time.
Here's where I went wrong perhaps, I had to connect to the internet again to get details for my pool (having to disconnect from the Ants), and since then I haven't been able to re-login to the Antminers. I've tried resetting them and trying to find them via the router, but they are not there. Anyone have any idea what went wrong/how I can login to them again pls?
Download Advanced IP Scanner and run that. It should find your Ant. Good advice, but if you do find the IP address is still .1.99 and you can't log into it try a factory reset and plug directly in again. I had a similar problem with my S1 when I first got it. Played around with the settings and couldn't even connect directly to my lappy. I could see it using IP scanner, but couldn't get to the login page because of the different subnet. I just changed the IP on my miner after to suit my routers subnet (.0.99) Now doing a factory reset on an S3, I'm a B3'er so I have no idea if this is possible. On the S1 there was a tiny button on the logic board. I'd press it, then turn off at the power supply about 5 seconds after, power back up and it would be back to factory settings. Hope that helps |
|
|
|
|
