Contents of the default asic-freq file (located in /etc/config/) (same location as S1) config 'asic-freq' 'default'
#option 'freq_value' '0982' #225M
#option 'chip_freq' '250'
#option 'timeout' '16'
#option 'freq_value' '1286' #237.5M
#option 'chip_freq' '237.5'
#option 'timeout' '17'
#option 'freq_value' '0882' #225M
#option 'chip_freq' '225'
#option 'timeout' '18'
option 'freq_value' '1106' #218.75M
option 'chip_freq' '218.75'
option 'timeout' '18'
#option 'freq_value' '1086' #212.5M
#option 'chip_freq' '212.5'
#option 'timeout' '18'
#option 'freq_value' '0782' #200M
#option 'chip_freq' '200'
#option 'timeout' '20'
#option 'freq_value' '1f07' #196M
#option 'chip_freq' '196'
#option 'timeout' '20'
#option 'freq_value' '0f03' #193M
#option 'chip_freq' '193'
#option 'timeout' '20'
#option 'freq_value' '0d83' #175M
#option 'chip_freq' '175'
#option 'timeout' '23'
#option 'freq_value' '0b83' #150M
#option 'chip_freq' '150'
#option 'timeout' '27'
#option 'freq_value' '0983' #125M
#option 'chip_freq' '125'
#option 'timeout' '33'
Looks like a typo on that top one. Looks like it should be labelled #250M. So there are three OC options already in the config then. |
|
|
|
Allright, i feel like i will try to push one of mine to 225 mhz... let's see  Up and running ... more to come 22 mins in 445 Gh/s (still going up) Fan speed is pretty much the same .. temp also 38-40. It looks like we could push those more with the correct DC/DC component replacement. 50 mins in, 450 Gh/s for the first one. 30 mins in, 409 Gh/s (only) for my second. End of test for now, back to normal freq. Thank you for the test. So am I right in understanding that hash rate went down on one of them when you stepped it up to 225? Yes, both of them on 225 Mhz. Take in consideration that the second unit at 409 only had 30 mins. A fair test would be like 24 hours but i don't want to risk my miners yet ^_^ I don't know, a 30 minute average should be pretty close to where it would be at 24. You might see some variation but the difference between 409 and 450 is larger than I would expect to see in 24 hours. Sounds like there are quite a few under-performing miners in this first batch even after the lowered expectations from Bitmain. |
|
|
|
Allright, i feel like i will try to push one of mine to 225 mhz... let's see Up and running ... more to come 22 mins in 445 Gh/s (still going up) Fan speed is pretty much the same .. temp also 38-40. It looks like we could push those more with the correct DC/DC component replacement. 50 mins in, 450 Gh/s for the first one. 30 mins in, 409 Gh/s (only) for my second. End of test for now, back to normal freq. Thank you for the test. So am I right in understanding that hash rate went down on one of them when you stepped it up to 225? |
|
|
|
|
Alright lets hear some OC'ing stories.
|
|
|
|
Can someone help me double-check my math?
.75-(.75*.077)=0.69225 BTC # Cost each by going for the 7.7% refund
((.75*2)+((.725-.075)*2))/4=0.7 BTC # Cost each by going for the 10%-off coupon on Batch 4
Price required for 10% coupon to be a better deal than the 7.7% refund: ((.75*2)+((.7094-.075)*2))/4=.7094 BTC
So if my math is right, for taking on the added risk of buying twice the hardware we've already purchased, the price per MOQ would have to drop to 1.4188 BTC to be a better deal than just taking the refund.
That's a price drop of 0.0156 BTC/each, so probably the next batch. But when will that next batch ship, and will it have improved DC/DC components? These are questions that really need to be answered by Bitmain before I take their coupon. That, or they need to be more aggressive with their coupon offer, otherwise I'm leaning toward opting for the refund, since the chances of me being able to order double what I've already ordered are slim. My primary hope would be to resell the coupons for more than .05775 BTC, which I doubt will be likely unless something extra-ordinary happens to the price of BTC for the duration of the coupon.
Anyway, how does my math and conclusion look to you guys?
Your third line has the wrong value at the end. Should be: Price required for 10% coupon to be a better deal than the 7.7% refund: ((.75*2)+((.7094-.075)*2))/4=. 6922 BTC Otherwise it looks about right. How did you arrive at .7094? There is probably a slightly higher cost that would yield .692249 which would really be the point at which it becomes cheaper but you don't show how you got .7094 as your price point. |
|
|
|
I've got this great idea! If everyone who got a B1 or B2 order waited until the 20th to fire up their S3's, then us poor schlubs who ordered from B3 would have a shot at decent difficulty, and we can all start up our machines together! Just kidding folks, of course. I moved too slowly and am jealous. Looking forward to hearing the first impressions, problems, etc. Hopefully you early birds can work out the initial kinks for us slowpokes  We should be seeing some in the wild by Thursday, according to above shipping dates. I can't wait to get my hands on my B1s - I'll be doing a full breakdown setup guide, tons of pics and vids. I'm sure plenty of others will be doing the same! Are you going to OC? I want to hear about OC experiences. I am in batch two so I expect right about the time you all are receiving them mine will be shipping. |
|
|
|
So I need some help here peoples. I do fly in fly out work with a 3 week on roster. So im going to be away from home when the miners arrive. My girl is home but is absolutely computer illiterate. I have setup the power supply ready for when they arrive with labelling for which cables go where so she can just plug them in. But as far as setting it up goes would i be able to setup the miners remotely with teamviewer with another computer set up at home? Reading about the S1 seems the internet has to be disconnected and then connect the compter directly to the miner. Is this true with the s3 do you think? Does anyone have any ideas how I could set up the miners remotely? Thanks  If you put two NIC's in your PC you can preconfigure one to talk to the miner (with crossover cable) and leave the other one to connect to your network. Then all she has to do initially is power the miner and plug it into the crossover cable. You can then remote in and configure it. If you set the IP as the last bit of configuration, she can then just change the ethernet cable to put it on your main network. |
|
|
|
When we were doing the first mass production, we found that not all of the S3’s DC/DC module could be stable enough to support the 478GH/s speed. After long time testing, all of the S3 run stably at 441GH/s...
...Many of the customers may be lucky to find that their S3 can be overclocked to 478GH/s.
I wish I knew what the instability was exactly. I think like most people the first thing I intend to do is OC it. Do I need to be watching it for crashing? Fire? I mean assuming it doesn't immediately start smoking or throwing huge numbers of HW errors. did you ever tried to overclock S1? in 24 hours you can see which one could handle it and which one could not-blades start to accumulate XX, sometimes miner becomes usntable with hashing speed fluctuating wildly. however, this time it is a different component (edit: resistors, thanks not chips themselves), so I would do it cautiously if at all. I only have one S1 and it OC'd without any issues. In fact, based on what I read about other people's experiences I got a good one because the HW error rate is exceptionally low even OC'd. The X's accumulate in the web interface from time to time but it doesn't effect hashing rate at all on mine. |
|
|
|
When we were doing the first mass production, we found that not all of the S3’s DC/DC module could be stable enough to support the 478GH/s speed. After long time testing, all of the S3 run stably at 441GH/s...
...Many of the customers may be lucky to find that their S3 can be overclocked to 478GH/s.
I wish I knew what the instability was exactly. I think like most people the first thing I intend to do is OC it. Do I need to be watching it for crashing? Fire? I mean assuming it doesn't immediately start smoking or throwing huge numbers of HW errors. |
|
|
|
There are only two cables but each cable has two PCI-e connectors for a total of four. |
|
|
|
Thank for the bug report. I will look at it. (Could you post the error message if it happens again ?)
I will but I also put the computer on a UPS so it's not likely to happen again for me. |
|
|
|
|
I had a power outage and after I restarted the proxy would not run. It had a bunch of errors (which I did not record - sorry). I recopied the original files and deleted the database folder and it is working again. I am guessing it was the deleting of the database folder which actually fixed it but you may want to code for that kind of crash. You might even be able to reproduce it by killing the proxy miner processes.
|
|
|
|
same here but it's just the front end to the site all mining is still working fine.
Seems to be true for scrypt multiport but not for x11 multiport. |
|
|
|
Why for pool all down?  |
|
|
|
|
Off hand I would say try a different driver version. Also is your cooling sufficient? You should be able to go higher intensity than 13 on scrypt, scrypt-n, and x11 at least from what I have seen but if your ambient temps are already summertime high then the card will get hot fast. Although usually an overheat causes a blue screen from what I have seen. But something to pay attention to anyway.
BTW I don't have that specific card but I do have a few different kinds of AMD cards in my farm so I am talking from my experience with those.
|
|
|
|
To open a, not so old wound, it looks like Multipool may have some vindication. It's been 5 days since Koi has solved a block. Luck may just be luck since no one is going to question his equipment.
I guess that's why even someone with Koi's hash power mines at a pool.
Yup. Looks like about 6 days now. |
|
|
|
Under statistics I see an unconfirmed balance for GUE. Can I assume this is an error?
GUE take forever to confirm. But days? We haven't mined it in days. And now the announcement is that it is being dropped from the pool. I don't want to cash out if I really do have an unconfirmed balance but I suspect it is not actually true based on how long it has been since we mined any. |
|
|
|
|
Under statistics I see an unconfirmed balance for GUE. Can I assume this is an error?
|
|
|
|
|
My SVR has been over the threshold I set but hasn't paid out for more than 12 hours now.
EDIT: Nevermind, even though it is telling me that it is setting to .5 I see it is actually changing it to 1. Usually when there is a minimum on the coin and you set it below the minimum it tells you that it set it to that minimum instead of whatever you entered. In this case it says it is setting it to what I entered but really it isn't.
|
|
|
|
|
My x11 proxy stopped working all of a sudden. Are you changing something? Hopefully not permanently...
EDIT: back in business already
|
|
|
|
|
Show Posts
