I would like to see a comment from KANO or -CK
I never passed judgement on the GPL violation issue because I never looked at fubly's previous project(s) (but I've heard all about it from Kano.) All I was suggesting was that the S9 driver be ported to master cgminer and inherit the fixes that were put into the S1/2/3 drivers - diff up what changes went from S3 to S9 and work that way instead of porting the core cgminer code to their fork. The issue with bitmain's fork is both the core cgminer code and their driver. High CPU usage, throwing away shares, getting best share wrong, massive wasteful work queues that add to latencies are the things I recall off the top of my head. Unfortunately I don't have the time to do the driver myself so I would welcome anyone from the community doing it; don't think I'm singling out fubly. As for not working on Kano's ckpool I don't think that's anything to do with fubly's code since he can mine on solo ckpool. His actions may have put him on an IP blacklist for kano.is in the past (which may say something in itself.) |
|
|
|
Posting on page 1000 was something I wanted to do.
1000 pages and I just hit 10000 posts (Kano is not far behind.) |
|
|
|
And another Friday lottery player here  I have some little rentals at MRR running here right now, and smth odd is happening - one of the rented s9's located in Germany is constantly switching from solo.ckpool.org and de.ckpool.org to a backup pool showing this: "One of your pools is reporting an excessive amount of rejected shares. In order to assist the failover, we've temporarily disabled this pool." All other gear is hashing normally. What could it be? The dodgy extra mining protocol put into the S9s purely to work with antpool. Solo doesn't have code to ignore the extra protocol data from those S9s and rejects them as invalid shares. Looks like they have the very early S9 firmware or something like that. |
|
|
|
besides testing successfully I am looking for kano and ck to bless this so to speak.
I'm sorry to disappoint you but that's unlikely for either of us. We already briefly posted our issues on this thread but no one seemed to respond to our criticism and we didn't want to rain on fubly's parade when everyone is excited by it so did not push the issue further. If you want to move forward with his code and give him the bounty, you're on your own on deciding whether you're happy or not. -ck as I recall Fubly said that this CGminer 4.9.2 should fulfill the GPLv3 license... I really do not hope I smell some kind of "We are the only ones" kind of thingy  I look through the whole thread again and I cant find any issues re. Fubly having no intentions to fulfill the GPLv3 license. If I got this wrong, please correct me. I hoped you as the last person ever, would kill a community project, making a lucked product open for everyone and get rid of Bitmain`s BMminer who broke the GPLv3 license ? Sad, really sad I never said anything about GPL - that's Kano's concern about fubly's other project and how that code is being applied here. Read my comment about driver changes. Porting cgminer is only half the work |
|
|
|
besides testing successfully I am looking for kano and ck to bless this so to speak.
I'm sorry to disappoint you but that's unlikely for either of us. We already briefly posted our issues on this thread but no one seemed to respond to our criticism and we didn't want to rain on fubly's parade when everyone is excited by it so did not push the issue further. If you want to move forward with his code and give him the bounty, you're on your own on deciding whether you're happy or not. |
|
|
|
|
Please put your long pastes in code tags (I did it for you on the previous post.)
|
|
|
|
Ok now im stuck, and lost anyone know what .conf i need to edit? -ck? Thank you  ckpool -A -p [2016-08-31 22:42:16.579] ckproxy stratifier starting [2016-08-31 22:42:16.579] ckproxy generator starting [2016-08-31 22:42:16.581] ckproxy connector starting [2016-08-31 22:42:16.581] ckproxy stratifier ready [2016-08-31 22:42:16.582] ckproxy connector ready [2016-08-31 22:42:16.778] Proxy 0:0 solo.ckpool.org:3333 failed to authorise in auth_stratum, got: {"id":42,"error":null,"result":false,"node.method":"auth.result"} [2016-08-31 22:42:16.778] Failed initial authorise to solo.ckpool.org:3333 with user: ! You need to add a valid workername for the pool you're trying to mine to in the ckproxy.conf file (in this case a valid workername is a bitcoin address with any worker extension such as 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.proxy ). I do not see where to add worker name in the ckproxy.conf file. would it be in the ckpool.conf file? this is all i see in ckproxy.conf, where would it go? { "proxy" : [ { "url" : "ckpool.org:3333", "auth" : "user", "pass" : "pass" }, { "url" : "backup.ckpool.org:3333", "auth" : "user", "pass" : "pass" } ], "update_interval" : 30, "serverurl" : "192.168.1.100:3334", "mindiff" : 1, "startdiff" : 42, "logdir" : "logs" } Comments from here on are ignored. auth is your workername |
|
|
|
Ok now im stuck, and lost anyone know what .conf i need to edit? -ck? Thank you ckpool -A -p [2016-08-31 22:42:16.579] ckproxy stratifier starting [2016-08-31 22:42:16.579] ckproxy generator starting [2016-08-31 22:42:16.581] ckproxy connector starting [2016-08-31 22:42:16.581] ckproxy stratifier ready [2016-08-31 22:42:16.582] ckproxy connector ready [2016-08-31 22:42:16.778] Proxy 0:0 solo.ckpool.org:3333 failed to authorise in auth_stratum, got: {"id":42,"error":null,"result":false,"node.method":"auth.result"} [2016-08-31 22:42:16.778] Failed initial authorise to solo.ckpool.org:3333 with user: ! You need to add a valid workername for the pool you're trying to mine to in the ckproxy.conf file (in this case a valid workername is a bitcoin address with any worker extension such as 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.proxy ). |
|
|
|
The version of cgminer you are using is very old and even if you had the latest you still wouldn't be able to mine with it as the gekkoscience hardware needs a custom forked version of cgminer to work. Here is the support thread for that device: https://bitcointalk.org/index.php?topic=1173963.0You also cannot mine solo unless you have the full bitcoin core client so you'd need to either find a way to get that working on your hardware or mine on a pool instead. |
|
|
|
|
You cannot mine bitcoins with a computer by itself no matter how powerful the computer is. All bitcoins are mined today with dedicated ASIC hardware and unless you buy some you cannot meaningfully mine bitcoin in any capacity.
|
|
|
|
I think i got ckproxy setup, i run ckpool -A -p and i get this. any "help" would be appreciated -A -p [2016-08-31 00:23:29.100] ckproxy generator starting [2016-08-31 00:23:29.100] ckproxy stratifier starting [2016-08-31 00:23:29.101] ckproxy connector starting [2016-08-31 00:23:29.104] ckproxy connector ready [2016-08-31 00:23:29.105] ckproxy stratifier ready [2016-08-31 00:23:49.335] Failed initial subscribe to solo.ckpool.org:80 ! There is no stratum server at solo.ckpool.org:80 ... (hint, port) |
|
|
|
|
The original poster's question was far too vague and you're all responding thinking he was talking about what physical location which I doubt - it was more a "how do I make money using services" question I believe. Please stop responding unless he comes back to clarify what the question was otherwise I'll just lock the thread.
|
|
|
|
build with cgminer 4.9.3 is ready for S7 and works well
There is no such thing as cgminer 4.9.3 at this time. Please don't make people think that your resync creates a new official version. Furthermore, the actual problems in the bitmain drivers go far deeper than just the core cgminer code and porting the rest of the code does not fix the driver itself. |
|
|
|
Hello Kano, I am not recieved the payment for 2 days mining, my account is monaculo , please help me with this payment issue
Best
Read this first: https://kano.is/index.php?k=payout |
|
|
|
Just a brief notification that the redirection gateway at solo.ckpool.org will be going down for maintenance approximately 36 hours from now. The DNS has been updated to direct miners to the stratum server so if you are connected on port 3334 or your miners don't support redirection, they will disconnect when this maintenance begins but assuming your mining software properly rechecks dns then they will automatically reconnect to the stratum server without any interruption.
Miners already connected to the stratum server (which is most miners except for rentals) will not be affected by this downtime.
In short, most of you won't notice anything but I will notify once more when this maintenance is over.
The maintenance has been put off for another 3 weeks so this no longer applies. |
|
|
|
My family and i we live in a terrible economic situation
so i need the solution and i think this is it
If you are in a terrible economic situation, then do NOT start mining bitcoin. It is NOT a guaranteed way to make money. There is a good chance you will more likely lose money especially as a newcomer to mining. |
|
|
|
Hi folks. In expect of bitcoin core v0.13 with segwit, will the cgminer be updated in part of solo mining? Guess that there may be also a changes in RPC part of bitcoin core.
Unlikely. The demand and utility for plain cgminer and the need for solo mining to work on it these days is somewhat pointless so there's no desire on my part to provide said update unless someone wants to contribute code pushes it to git and asks me to pull their request. The only new hardware coming out that will use official cgminer code will be upcoming avalon hardware and that will be running on low power controllers that won't be capable of solo mining in any meaningful capacity. |
|
|
|
Hey CK?
is the solo pool doing ok? think maybe we need a restart?
i cant seem to get above a 3 bill share and its been a few days
usually now i would have gotten a 30-0 bill share
"shares": 74543943647, "bestshare": 3978622537.9785938, "bestever": 41869949505
Solo pool's fine, it's only up to 73% diff this "round". Restart is bullshit. I don't help people live out their superstitions, sorry. |
|
|
|
|
Show Posts
