CCminer(SP-MOD) Modded GPU kernels.

[t-nelson]

It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

It makes you wonder? Definitely the latter, you guys seems to have garages full of vidcards and cheap electricity. There is seriously no question.

More like a spare bedroom, one GTX960, one GTX750Ti and 0.10USD/kWh power.  Amateur at best.

[t-nelson]

Anybody knows a proper request to monitoring API, like IP:port and command (getsummary for ex) ? A remeber cgminer has

Code:

The JSON request format required is '{"command":"CMD","parameter":"PARAM"}'

but as i understand ccminer api dosn't support Json api request and answers.

ccminer has NO control API of any kind.  It's just a config/text log app.

[qqqq]

Anybody knows a proper request to monitoring API, like IP:port and command (getsummary for ex) ? A remeber cgminer has

Code:

The JSON request format required is '{"command":"CMD","parameter":"PARAM"}'

but as i understand ccminer api dosn't support Json api request and answers.

ccminer has NO control API of any kind.  It's just a config/text log app.

Hmm, so what is this ?

Code:

-b, --api-bind        IP/Port for the miner API (default: 127.0.0.1:4068) 
    --api-remote      Allow remote control

[scryptr]

Anybody knows a proper request to monitoring API, like IP:port and command (getsummary for ex) ? A remeber cgminer has

Code:

The JSON request format required is '{"command":"CMD","parameter":"PARAM"}'

but as i understand ccminer api dosn't support Json api request and answers.

EPSYLON3--

Check out tpruvot/epsylon3's work.  The details of the API are explained in his documentation.  That sort of stuff is one of his CCminer specialties.  Also, KBomba uses the API in his CCmonitor, and in his MinerControl branch.  You can find both of them on GitHub, and tpruvot has his own forum on BTC form (here).

--scryptr

[zTheWolfz]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

Sorry if it came across as a complaint was only noting it wasn't working and hadn't been for quite sometime.

Thanks for your hard work, more donations to come when I get more to spare.
A few GPU's where down for a day or so and set me back some.

Cheers

[zTheWolfz]

Hi

after the neoscrypt update from t-nelson I test it
the error is gone but i don´t get any status update from ccminer is this normal ?

best regards

Even when it worked before you didn't get any status update until it actually found a block, weather good or bad.
So no hashrate is posted until it finds a block, then afterwards it starts posting hasrate for the cards.

The way to see if its working is something like GPUZ to see if the cards are under a load or not. on the status page.
If the GPU shows a load 60/99% then its doing work.

[qqqq]

Anybody knows a proper request to monitoring API, like IP:port and command (getsummary for ex) ? A remeber cgminer has

Code:

The JSON request format required is '{"command":"CMD","parameter":"PARAM"}'

but as i understand ccminer api dosn't support Json api request and answers.

EPSYLON3--

Check out tpruvot/epsylon3's work.  The details of the API are explained in his documentation.  That sort of stuff is one of his CCminer specialties.  Also, KBomba uses the API in his CCmonitor, and in his MinerControl branch.  You can find both of them on GitHub, and tpruvot has his own forum on BTC form (here).

--scryptr

Thank you, i found a proper request it's just "summary". So http://localhost:4068/summary shows that's what i needed

NAME=ccminer;VER=1.5.68-git(SP-MOD);API=1.3;ALGO=lyra2v2;GPUS=3;KHS=25592.25;ACC=0;REJ=0;ACCMN=0.000;DIFF=125460.864079;UPTIME=11276;TS=1443301389

"threads" shows

GPU=0;BUS=11;CARD=GeForce GTX 970;TEMP=74.0;FAN=72;RPM=1816;FREQ=1240500;KHS=8718.79;HWF=0;I=19.6;THR=851968|GPU=1;BUS=7;CARD=GeForce GTX 970;TEMP=74.0;FAN=73;RPM=1836;FREQ=1240500;KHS=8494.52;HWF=0;I=19.6;THR=851968|GPU=2;BUS=13;CARD=GeForce GTX 970;TEMP=80.0;FAN=86;RPM=2171;FREQ=1240500;KHS=8362.02;HWF=0;I=19.6;THR=851968|

Unfortunately it's not a json format. But it's ok also. And unfortunately it's only localhost bind API ability. Any chance to fix this ? I mean -b 192.168.X.X doesn't work, only 127.0.0.1 

With the -b parameter you can open your ccminer to your network, use -b 0.0.0.0:4068 if required.

[t-nelson]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

Sorry if it came across as a complaint was only noting it wasn't working and hadn't been for quite sometime.

Thanks for your hard work, more donations to come when I get more to spare.
A few GPU's where down for a day or so and set me back some.

Cheers

Not at all.  You actually sped things up by posting output.  It saved me waiting around on my piddly setup.  We're past even by my book.

[scryptr]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

Sorry if it came across as a complaint was only noting it wasn't working and hadn't been for quite sometime.

Thanks for your hard work, more donations to come when I get more to spare.
A few GPU's where down for a day or so and set me back some.

Cheers

Not at all.  You actually sped things up by posting output.  It saved me waiting around on my piddly setup.  We're past even by my book.

2-BITS--

I sent you 2-bits.  And, thank you!  Please communicate with the neoscrypt wallet devs.  The wallet behavior is not normal.       --scryptr

[bensam1231]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

I did mention no one uses pool mining except for giant farms and they're unlikely to actually donate as they probably have their own devs they employ.

I also said that the miner would be better off with a miner fee split among developers or a company which could manage such things.

I will also, also point out the people who were complaining were mainly other devs.


Honestly I really don't understand this. It's like developers like putting themselves in the corner and then complaining about miners too. What's wrong with a mining fee? We've went over this multiple times. You could easily get paid for your work. You could even make it optional to test it out or a release candidate with miner improvements and a fee to see how it turns out.

It's already been done successfully with Claymore.

[pallas]

Miner with fee: this had been discussed tens of times.
Most devs can't do it because you need to write your own stratum client, GPU interface etc.
It takes too much time. It's not worth the effort.

Miners complaining: if you want nvidia miners stay opensource so you can continue mining with a profit, you know what to do. Otherwise, in a couple months nvidia will be just like amd.

[djm34]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

I did mention no one uses pool mining except for giant farms and they're unlikely to actually donate as they probably have their own devs they employ.

I also said that the miner would be better off with a miner fee split among developers or a company which could manage such things.

I will also, also point out the people who were complaining were mainly other devs.


Honestly I really don't understand this. It's like developers like putting themselves in the corner and then complaining about miners too. What's wrong with a mining fee? We've went over this multiple times. You could easily get paid for your work. You could even make it optional to test it out or a release candidate with miner improvements and a fee to see how it turns out.

It's already been done successfully with Claymore.

you sound like a broken record bensam...

[fenomenhaa]

Nicehash lyrav2 currently paying     2.6896btc ..Dropped to 0.50

[sp_]

Nicehash lyrav2 currently paying     2.6896btc ..Dropped to 0.50

Up to 0.9296 now..


https://www.nicehash.com/index.jsp?p=miners&a=14&l=0

The top miner just switched from mining quark to lyra2v2 5,4 gigash all NVIDIA. I wonder if he is using the DJM-34 version or the sp-mod.

This farm is making 3.274 BTC a day on this adress..
Pretty good..
No donations to the developers.
If you release your faster lyra2v2 kernal djm34, he will upgrade and the profit will go away.

Massive hashrate...

equal to around 1300 750ti's @ 40watt (52,000 watt)

But I think this company has some older compute cards. So the power usage is probobly twice as much as the competition. And all the rigs are linux based.

[djm34]

Nicehash lyrav2 currently paying     2.6896btc ..Dropped to 0.50

Up to 0.9296 now..


https://www.nicehash.com/index.jsp?p=miners&a=14&l=0

The top miner just switched from mining quark to lyra2v2 5,4 gigash all NVIDIA. I wonder if he is using the DJM-34 version or the sp-mod.

who cares... 

[rednoW]

My poor gtx750 hashes only 3750khs/s on lyra2v2 and sp_mod r69. Is it normal?

[t-nelson]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

Sorry if it came across as a complaint was only noting it wasn't working and hadn't been for quite sometime.

Thanks for your hard work, more donations to come when I get more to spare.
A few GPU's where down for a day or so and set me back some.

Cheers

Not at all.  You actually sped things up by posting output.  It saved me waiting around on my piddly setup.  We're past even by my book.

2-BITS--

I sent you 2-bits.  And, thank you!  Please communicate with the neoscrypt wallet devs.  The wallet behavior is not normal.       --scryptr

Much appreciated, sir!

Which coins are you having wallet trouble with specifically? PhoenixCoin is fixed in their master branch, so should be OK whenever they cut a new release.  I opened an issue for FeatherCoin at here.  You can use the --broken-neo-wallet flag until they sort things out.


I also wanted to clarify that by "closed," I meant "closed source."  That is the only way to enforce something like a small fee.  Generally in open source I don't care about such things because, for someone else to monetize my work, they have to put in some effort on their own.  However, with a miner its just; start program, profit!

EDIT: I checked sources for Feather, Pheonix, Orbit, UFO and Halcyon.  They're all correct except for Feather, which I already reported and UFO, which I've reported here.

[scryptr]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

Sorry if it came across as a complaint was only noting it wasn't working and hadn't been for quite sometime.

Thanks for your hard work, more donations to come when I get more to spare.
A few GPU's where down for a day or so and set me back some.

Cheers

Not at all.  You actually sped things up by posting output.  It saved me waiting around on my piddly setup.  We're past even by my book.

2-BITS--

I sent you 2-bits.  And, thank you!  Please communicate with the neoscrypt wallet devs.  The wallet behavior is not normal.       --scryptr

Much appreciated, sir!

Which coins are you having wallet trouble with specifically? PhoenixCoin is fixed in their master branch, so should be OK whenever they cut a new release.  I opened an issue for FeatherCoin at https://github.com/FeatherCoin/Feathercoin/issues/77.  You can use the --broken-neo-wallet flag until they sort things out.


I also wanted to clarify that by "closed," I meant "closed source."  That is the only way to enforce something like a small fee.  Generally in open source I don't care about such things because, for someone else to monetize my work, they have to put in some effort on their own.  However, with a miner its just; start program, profit!

ORBITCOIN (ORB)--

And Feathercoin.  I attempted to use release dot 69 (prior to the wallet flag) with the wallet and it just sat there, no card hashing reports.  I then used DJM34's CCminer for NeoScrypt, with debugging on and quiet off, and got this:


Error messages when attempting to solo-mine with OrbitCoin wallet (NeoScrypt).

At that point I stopped attempting to solo-mine with NeoScrypt.  I'll wait for the compiled Windows release with the wallet flag.  I have compiled on Windows, but not for a while.

--scryptr

[t-nelson]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

Sorry if it came across as a complaint was only noting it wasn't working and hadn't been for quite sometime.

Thanks for your hard work, more donations to come when I get more to spare.
A few GPU's where down for a day or so and set me back some.

Cheers

Not at all.  You actually sped things up by posting output.  It saved me waiting around on my piddly setup.  We're past even by my book.

2-BITS--

I sent you 2-bits.  And, thank you!  Please communicate with the neoscrypt wallet devs.  The wallet behavior is not normal.       --scryptr

Much appreciated, sir!

Which coins are you having wallet trouble with specifically? PhoenixCoin is fixed in their master branch, so should be OK whenever they cut a new release.  I opened an issue for FeatherCoin at https://github.com/FeatherCoin/Feathercoin/issues/77.  You can use the --broken-neo-wallet flag until they sort things out.


I also wanted to clarify that by "closed," I meant "closed source."  That is the only way to enforce something like a small fee.  Generally in open source I don't care about such things because, for someone else to monetize my work, they have to put in some effort on their own.  However, with a miner its just; start program, profit!

ORBITCOIN (ORB)--

And Feathercoin.  I attempted to use release dot 69 (prior to the wallet flag) with the wallet and it just sat there, no card hashing reports.  I then used DJM34's CCminer for NeoScrypt, with debugging on and quiet off, and got this:


Error messages when attempting to solo-mine with OrbitCoin wallet (NeoScrypt).

At that point I stopped attempting to solo-mine with NeoScrypt.  I'll wait for the compiled Windows release with the wallet flag.  I have compiled on Windows, but not for a while.

--scryptr

I've updated my previous post with what I've found regarding neoscrypt wallet status.  If you're having issues with one that's already fixed, then you need a newer version of the wallet.  That may require waiting for their devs to cut a release.  Of the two that are reported, I'd suggest posting in the GH issue thread links I've posted.

As for output, did you see zTheWolfz's post a while back?  Apparently that's how it's always worked.  It could be something in the kernel.

[djm34]

I'm not sure it matters how many ways to donate we have. Miners seem to be way better at complaining than donating.  I had my all of my GPUs pointed at broken soloing for nearly a week and have only received two donations (thanks again myagui and zTheWolfz!) since the fix went in.  That's despite there being at least a half dozen people on here complaining about the issue.  It really makes me wonder whether my time would be better spent fixing ccminer or teaming up with some of the kernel guys and doing something closed from scratch...

Sorry if it came across as a complaint was only noting it wasn't working and hadn't been for quite sometime.

Thanks for your hard work, more donations to come when I get more to spare.
A few GPU's where down for a day or so and set me back some.

Cheers

Not at all.  You actually sped things up by posting output.  It saved me waiting around on my piddly setup.  We're past even by my book.

2-BITS--

I sent you 2-bits.  And, thank you!  Please communicate with the neoscrypt wallet devs.  The wallet behavior is not normal.       --scryptr

Much appreciated, sir!

Which coins are you having wallet trouble with specifically? PhoenixCoin is fixed in their master branch, so should be OK whenever they cut a new release.  I opened an issue for FeatherCoin at https://github.com/FeatherCoin/Feathercoin/issues/77.  You can use the --broken-neo-wallet flag until they sort things out.


I also wanted to clarify that by "closed," I meant "closed source."  That is the only way to enforce something like a small fee.  Generally in open source I don't care about such things because, for someone else to monetize my work, they have to put in some effort on their own.  However, with a miner its just; start program, profit!

ORBITCOIN (ORB)--

And Feathercoin.  I attempted to use release dot 69 (prior to the wallet flag) with the wallet and it just sat there, no card hashing reports.  I then used DJM34's CCminer for NeoScrypt, with debugging on and quiet off, and got this:


Error messages when attempting to solo-mine with OrbitCoin wallet (NeoScrypt).

At that point I stopped attempting to solo-mine with NeoScrypt.  I'll wait for the compiled Windows release with the wallet flag.  I have compiled on Windows, but not for a while.

--scryptr

not sure what version you are using... since my original neoscrypt never included  gbt support...
anyhow you need to turn-off gbt support, (see help menu for that)  which is off in most of my release.

edit: actually if you are using the lyra2 version, it probably include the bug sp introduced...
since it is based on the sp fork. (and I don't use this one to mine neoscrypt)