Only problem is, my miner stops mining because bfg goes weird, or unexpectedly quits about 4 times a day. If I can't check the stats I don't know if it's working or not:(
How about reporting the crash info? :p |
|
|
|
Let's all donate to wizkid057 to help get the stat's back up! Anyone know his donation address?
1StatsgBq3C8PbF1SJw487MEUHhZahyvR |
|
|
|
Hi Luke,
I think that the KnCMiner is in your plans.
Do you have an estimation when you release the KncMiner version?
Thank you very much for your contribution to Cryptocoin Mining!!!
The next major version will support KnC units. You can see the (working) code-in-progress in the git "knc" branch. |
|
|
|
|
What DDoS? Just webserver problems, no big deal.
|
|
|
|
Ah dude, every time I go out my miner stops working. It's a bfl 60gh. Usually it says something like this Bugs don't get fixed unless they're reported  Can you run BFGMiner in valgrind? It'll use a lot more CPU time, but it will also give a lot more info. valgrind --leak-check=full --track-origins=yes bfgminer YOUR OPTIONS --debuglog 2>valgrind.log |
|
|
|
Luke, sorry for a n00b question, but seriously....
I haz bfl pr0ductz.
Stratum, GBT or Getwork? (I'm using bfgminer on ubuntu).
(Also, my miner just stops working all the time, the application crashes in terminal, or it just randomly fills the screen with gibberish and I have to close bfgminer and start again- anyone else get this? If I'm out I have to rush home in order to preserve my 1337 hashr4t3)
Stratum for now. I'll get back to finishing GBT up later. |
|
|
|
Oh, OK, so you're changing the terms, because classically a stratum proxy (like slush's one) allows a getwork client to mine on a stratum pool. Slush's Stratum proxy refers only to the upstream protocol. It supports both getwork and Stratum clients. So, back to the question - is the getwork proxy available on OpenWRT?
Should be. |
|
|
|
The stratum proxy is fully supported on all platforms, including Win64.
It's only the getwork proxy that can't do Win64.
 There's a difference? Surely: stratum proxy is for allowing getwork clients to mine on a stratum pool? getwork proxy is for allowing getwork clients to mine on a stratum pool? Confused. Stratum proxy is for allowing stratum clients to mine on stratum pool(s). getwork proxy is for allowing getwork clients to mine on any pool(s). |
|
|
|
Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner? IIRC, it should be there in 3.3.0? OK, cool. I didn't see anything specific in the READMEs about it being added, so assumed it was still not on OpenWRT, like it's still not on Win64 version. I'll give it a spin sometime on OpenWRT... The stratum proxy is fully supported on all platforms, including Win64. It's only the getwork proxy that can't do Win64. |
|
|
|
./bfgminer: --http-port: unrecognized option This means libmicrohttpd wasn't found when you ran configure. |
|
|
|
I'm thinking of getting a refund for November. I have a feeling I am going to be battling that one. Sam was such a nice person back in May. (When I had money of course) Now they all seem like a bunch of dicks. They are probably just busy engineers but it sucks seeing how they don't really want to work with people anymore. They seem to be pretty open to working with people still IMO. I wouldn't pay too much attention to the troll(s). (Not to say KnC is The Perfect Company, but they seem to be getting a lot of FUD and exaggerations...) |
|
|
|
Can't hurt. Eligius doesn't pay for stale shares, but cgminer doesn't detect stale shares correctly anyway.
Could you please explain further? Specifically how cgminer doesn't do this correctly. With getwork (and GBT?), it assumes a work update (longpoll) always makes the previous job(s) stale. Result: cgminer thinks shares are stale that aren't. With stratum, it doesn't act on work updates unless the server tells it previous jobs are now stale. Result: cgminer keeps mining jobs long after they've been replaced, getting close to (and possibly beyond) their expiration time. There is in fact no reliable way for mining software to know when previous jobs are in fact stale. Stratum provides a hint, which works in one case (but not others). GBT also provides hints that cover some other cases (but not the one case stratum hints about). BFGMiner will take these hints into account, but otherwise only assumes a job is stale if the previous-block-hash has changed (ie, the job is considered globally stale to the Bitcoin network). |
|
|
|
Quick question: Can we / should we set cgminer to submit stale shares here? Do they count?
Thanks.
Can't hurt. Eligius doesn't pay for stale shares, but cgminer doesn't detect stale shares correctly anyway. |
|
|
|
- makes 90-bit strong and easy-to-remember passphrases (this can be modified if needed) Contradiction? How is 90-bit strong when the norm is 256-bit? And usually "easy-to-remember" and "strong" are inherently opposites... |
|
|
|
Luke-Jr:
Any reason why the extended-core information for BFL's (seeing all cores per Single, for example) went away from 3.2.90 to 3.3.0 via the API?
I used to get all 16 cores per single, now I see only summary information.
Per README.RPC... API V2.0 (BFGMiner v3.3.0)
Removed API commands:
'devdetail' - Use newer 'devdetails' for same information.
Modified API commands:
'devs' - display status of each full device only (not processors)
'pga' - lookup and display device by device (not processor) number
'pgacount' - count only full devices (not processors)
'pgaenable' - enable all processors for a numbered full device
'pgadisable' - disable all processors for a numbered full device
'pgaidentify' - choose first processor of numbered full device
'pgaset' - choose first processor of numbered full device
Added API commands:
'procs'
'proc'
'proccount'
'procenable'
'procdisable'
'procidentify'
'procset' |
|
|
|
Luke-Jr, have you any idea if/when you'll be adding the stratum proxy module to the OpenWRT version of BFGMiner? IIRC, it should be there in 3.3.0? |
|
|
|
|
Show Posts
