Nope, never seen comm errors here. Although the U3 does like to randomly die :/
Yea, I'm familiar with the random deaths, but this one isn't dying. It spits out the errors several per second, but not continuously, and it hashes away just fine, but at some point its hash drops from the pool despite bfgminer showing it hashing away just fine. |
|
|
|
|
The new site looks good, but the English translations are worse than on the old site. Several things are unclear or worded poorly. I suggest someone who knows English well go through the translated version and give it a polishing.
Meanwhile my btc continues to grow here, and I like to think that some of the new truck fulls of miners are part of my investment.
|
|
|
|
|
Luke-Jr, any ideas on the comms errors I've reported above? My U3 seems to be running fine in all other aspects, but it seems the comms errors cause it to drop off the pool I have it pointed to (or the pool boots it off, not sure). Thank you.
|
|
|
|
|
That's the first I've heard of powering the fan with external power, I wonder if that contributed to the stability you had? Very interesting, something else to tinker with.
|
|
|
|
hello, izanagi..
i am a Jr. Member now..
please update the google doc..
thanks
You have to update your signature, too. |
|
|
|
|
Unfortunately the price seems to be keeping pace with the change in diff, and it's hovering around $277 right now. We always see swings in the diff right at the end, so hopefully the price swings back up as well.
|
|
|
|
LOL.. Did you guys see the Southpark Episode where they totally rip on Gingers ? Cracked me up.  "The" episode? Cartman rags on Kyle all the time for being ginger. But more importantly, BLOCK + confirms! |
|
|
|
I think the saturation idea is stupid. That would hinder adoption effectively and would kill bitcoin in the long run. The fees needed to, for exampl back up the block halving through that way, are way too high to let bitcoin survive. Following that idea would be plain stupid.
I don't think fee saturation is necessary/beneficial until the block solve reward has halved several more times. Right now fees are such a small percentage of the total block reward that they could, essentially, be ignored. |
|
|
|
You'd be looking at significantly less than pennies a day, more like decimals of decimals of a penny per day. There are many calculators that will answer your first question. The second questions is likely answered in any documentation that comes with the stick, and I believe in the review thread for the sticks as well. |
|
|
|
|
Well we do know that Bitmain is unplugging S5s to sell as "new" to make way for the real new gear, so a small drop can be expected while this swap occurs.
|
|
|
|
|
Welcome to the world that is the U3. There is no rhyme, there is no reason. If you get them working, for the love of god DON'T TOUCH THEM, but this you have learned too late.
|
|
|
|
Must we continue this 'Battle of the Pool'? It really comes down to choice. I choose kano.is. Battle over, I win!
Seconded, everybody does there own research and chooses a pool based on what he finds. If you don't like this pool then go find another one! Yeah I said that to him in the first post in all this  Further evidence my ignoring that user was a well-timed exercise. Nice to see the "orphan" get backed up by a couple real blocks, gogo kano ck pool! |
|
|
|
Our first 'almost' block - but it wasn't good enough.
ckpool submits the share as a block if it is within a small amount of being a block just to be sure.
So it shows up on the web site, but alas not good enough.
share block was: 52123573961.901596
but current diff is: 52278304845.59168243
It will show up as an orphan, but I guess I need to label it as something else later since it's not an orphan.
I saw that on the block page on your website and wondered, thanks for the clarification. I recall a similar thing happening on the ck solo pool, where a "close" block solve was submitted but ultimately reject. Close but no cigar! |
|
|
|
most of my mining time point to this pool but after i looke back and review my payout its getting worse.
If your hash rate stays the same and more hash is added to the pool then your payouts will decrease. |
|
|
|
|
Holy cow, you did it! I posted on the first page of your thread because I use one S3+ in the summer at ck's solo pool. Glad to know it's possible (however unlikely it may be).
|
|
|
|
ended when I stopped trying to use cgminer and bmsc options
If you were using bmsc options with cgminer then you were using an old, outdated version of cgminer. You should try again with version 4.9.2 and the proper --au3 command line options from the ASIC README (volt 800 and freq 250 usually give about the max rated GH/s). and used bfgminer with the following command line
-S antminer:all --set antminer:voltage=x820 --set antminer:clock=x0982
Do you use --set antminer:timing as well, or omit it entirely from your command line? |
|
|
|
and then it hits 2 blocks. This is solo mining, there's no "it", it's a "they". A person solved it, not "the solo pool". |
|
|
|
it's a passion for me than money ...
My hat off to you, sir; a very impressive set-up! I like the hand-made look of it all, you can tell it's a labor of love and not some cold data center. |
|
|
|
Hello,
Got an U3, trying to make it work but no success yet (windows 7/64) with cgminer 4.9.2
Check out the ASIC README file and use the appropriate U3 commands (--au3-volt --au3-freq). |
|
|
|
|
Show Posts
