CCminer(SP-MOD) Modded GPU kernels.

[t-nelson]

 sp  could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx    

I didn't remove it, not sure why it isn't working..

He's probably talking about wallet mining with GBT - coins are moving to newer BTC codebases, which have getwork removed.

This works with release43  but not with release 62 for wallet mining.

ccminer.exe -a quark  -q -o http://localhost:port           < computer  1
ccminer.exe -a quark  -q  -o http://192.168.0.102:port  <  computer 2   Both on the same hub.

Somewhere after release43 it stopped working. Maybe around release50.

Since you have a good and bad release number, you can narrow this down pretty quickly by bisecting.

1) good_rev = 43
2) bad_rev = 62
3) test_rev = (bad_rev - good_rev) / 2; (ie. (62-43)/2 = 19/2 = 9)
4) Try test_rev.
5) If it succeeds, good_rev = test_rev.  If it fails, bad_rev = test_rev.
6) Repeat 3-6 until you've narrowed it down.

If you're building from scratch and are handy with git, you can do one better and narrow it down to the commit.  http://git-scm.com/docs/git-bisect

[1714683898]

1714683898

[1714683898]

1714683898

[1714683898]

1714683898

[1714683898]

1714683898

[GarlukKY]

  sp  could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx   

I didn't remove it, not sure why it isn't working..

He's probably talking about wallet mining with GBT - coins are moving to newer BTC codebases, which have getwork removed.

This works with release43  but not with release 62 for wallet mining.

ccminer.exe -a quark  -q -o http://localhost:port           < computer  1
ccminer.exe -a quark  -q  -o http://192.168.0.102:port  <  computer 2   Both on the same hub.

Somewhere after release43 it stopped working. Maybe around release50.

Build 54 is the last sp_ build that will solo mine against your wallet.  I have not tried B63, but I'm assuming it will also fail.  I have tried every build from 54 to 62. 

[zTheWolfz]

 sp  could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx    

I didn't remove it, not sure why it isn't working..

He's probably talking about wallet mining with GBT - coins are moving to newer BTC codebases, which have getwork removed.

This works with release43  but not with release 62 for wallet mining.

ccminer.exe -a quark  -q -o http://localhost:port           < computer  1
ccminer.exe -a quark  -q  -o http://192.168.0.102:port  <  computer 2   Both on the same hub.

Somewhere after release43 it stopped working. Maybe around release50.

Build 54 is the last sp_ build that will solo mine against your wallet.  I have not tried B63, but I'm assuming it will also fail.  I have tried every build from 54 to 62.  

My solo test shows it still works in r56 but fails in r57
ccminer.exe -a neoscrypt --no-gbt --no-longpoll -o 127.0.0.1:3333 -u phoenixcoinpc -p x -d 0 -i 10 -l T16x2
I tested r54,r55,r56 & r57. never downloaded r58

[kama]

 sp  could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx    

I didn't remove it, not sure why it isn't working..

He's probably talking about wallet mining with GBT - coins are moving to newer BTC codebases, which have getwork removed.

This works with release43  but not with release 62 for wallet mining.

ccminer.exe -a quark  -q -o http://localhost:port           < computer  1
ccminer.exe -a quark  -q  -o http://192.168.0.102:port  <  computer 2   Both on the same hub.

Somewhere after release43 it stopped working. Maybe around release50.

Build 54 is the last sp_ build that will solo mine against your wallet.  I have not tried B63, but I'm assuming it will also fail.  I have tried every build from 54 to 62.  

My solo test shows it still works in r56 but fails in r57
ccminer.exe -a neoscrypt --no-gbt --no-longpoll -o 127.0.0.1:3333 -u phoenixcoinpc -p x -d 0 -i 10 -l T16x2
I tested r54,r55,r56 & r57. never downloaded r58

you should keep your related wallet open me 2 faced with this problem and solved it like i said

[zTheWolfz]

you should keep your related wallet open me 2 faced with this problem and solved it like i said

Not sure what your saying, but my wallet is never closed and I've mined to this same wallet with many different miners
using the same config or command line depending on the type of miner software used. Nothing has changed with my
wallet config, only different miner software have been changed/used or upgraded.

[kama]

you should keep your related wallet open me 2 faced with this problem and solved it like i said

Not sure what your saying, but my wallet is never closed and I've mined to this same wallet with many different miners
using the same config or command line depending on the type of miner software used. Nothing has changed with my
wallet config, only different miner software have been changed/used or upgraded.

did you changed your related .conf file ?

[zTheWolfz]

you should keep your related wallet open me 2 faced with this problem and solved it like i said

Not sure what your saying, but my wallet is never closed and I've mined to this same wallet with many different miners
using the same config or command line depending on the type of miner software used. Nothing has changed with my
wallet config, only different miner software have been changed/used or upgraded.

did you changed your related .conf file ?

Still don't follow what your asking?

[kama]

you should keep your related wallet open me 2 faced with this problem and solved it like i said

Not sure what your saying, but my wallet is never closed and I've mined to this same wallet with many different miners
using the same config or command line depending on the type of miner software used. Nothing has changed with my
wallet config, only different miner software have been changed/used or upgraded.

did you changed your related .conf file ?

Still don't follow what your asking?

okay im sorry have a good night

[zTheWolfz]

you should keep your related wallet open me 2 faced with this problem and solved it like i said

Not sure what your saying, but my wallet is never closed and I've mined to this same wallet with many different miners
using the same config or command line depending on the type of miner software used. Nothing has changed with my
wallet config, only different miner software have been changed/used or upgraded.

did you changed your related .conf file ?

Still don't follow what your asking?

okay im sorry have a good night

My command line matches sgminer/cgmimmer/ccminer.conf to my wallet .conf = phoenixcoin.conf
as long as those matches it should work weather its a actual wallet address:Pn18tqfzFNPUcFjJRq1GRYdYDJjKTBNGpq
or just something random you pick.
Pretty much like I setup here:

Code:

server=1
daemon=1
defaultkey=1
logtimestamps=1
dns=1
addnode=prometheus.phoenixcoin.org:9555
addnode=menoetius.phoenixcoin.org:9555
addnode=atlas.phoenixcoin.org:9555
rpcuser=phoenixcoinpc
rpcpassword=x
rpcport=3333
rpcconnect=127.0.0.1
rpcallowip=192.168.*.*

and wola look what happen while I was typing this message:

[GarlukKY]

 sp  could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx    

I didn't remove it, not sure why it isn't working..

He's probably talking about wallet mining with GBT - coins are moving to newer BTC codebases, which have getwork removed.

This works with release43  but not with release 62 for wallet mining.

ccminer.exe -a quark  -q -o http://localhost:port           < computer  1
ccminer.exe -a quark  -q  -o http://192.168.0.102:port  <  computer 2   Both on the same hub.

Somewhere after release43 it stopped working. Maybe around release50.

Build 54 is the last sp_ build that will solo mine against your wallet.  I have not tried B63, but I'm assuming it will also fail.  I have tried every build from 54 to 62.  

My solo test shows it still works in r56 but fails in r57
ccminer.exe -a neoscrypt --no-gbt --no-longpoll -o 127.0.0.1:3333 -u phoenixcoinpc -p x -d 0 -i 10 -l T16x2
I tested r54,r55,r56 & r57. never downloaded r58

Maybe I should say I've not been able to solo mine on Quark algo since b54.  I just tried b56, it just sits there doing nothing.... just like in your screenshot.  B57 does not generate an error message for me, but it also just sits there doing nothing.

[hashbrown9000]

I mentioned these solo mining problems a few pages back.  have to use djm's miner to do any solo mining for now.

[bensam1231]

Well, imagine I develop the miner and the pool, and I lock my miner to one pool. If my miner is fast enough, people will switch to it, otherwise they will be at a severe disadvantage. This causes a miner monopoly, and since the pool is locked in the miner, it creates a pool monopoly. Now, one pool easily will have well over 50% hashrate, allowing them to attack the chain if they so choose.

You don't need to have all the shares being submitted to the same pool. Claymore allowed the use of your personal pool and 2 shares would be submitted to a pool of his choosing.

There is also nothing stopping developers from stopping support of such a miner and making their own branch if they hate it. This was the whole reason I suggested a pilot program with 10% increase in hash (SPs private Quark is much faster as is TSIVs Lyra2v2) and 2% fee to see where it goes.

yeah, I agree about not locking a miner to the pool, I was just interested about the closed source. I assume its to ensure receiving compensation for the effort of coding, which I also agree with, but I was just curious if there's anything more.

My only experience is the Monero, and its black and white comparing what has happened with nvidia vs. amd mining - claymore has updated his software constantly, whereas tsivs miner not so much. And, as he stated, its probably because the donations haven't been pouring in.

Oh, closed source only cause otherwise people take out the fee and redistribute it.

I've thought about that as well. Assumedly there will be continued development on such a miner. Just open source a couple versions behind if they so choose. So it's antiquated and not really competitive, but the community can still value from it. Claymore even offered a option where you could use his miner without donations, but lost like 5% of the hashrate if you were hell bent on it (of course the fee was only 2.5% so...).

Such a miner is a good opportunity for developers to make money as well. If they want to work on a complete rewrite, they'll be rewarded for it (as long as the miner isn't a 'only us' crew and snubs other developers that want to help).

Well, I'll be damned. I don't disagree.

Well that's a start... All we need now is more developers who think this is a decent idea and actually give it a try.

[squadbox]

I wrote a script to manually control fan speeds on headless linux boxes.  It's adapted from another source online, but modified for newer drivers.

https://gist.github.com/squadbox/e5b5f7bcd86259d627ed

The script can be called after using the coolbits flag as dominuspro mentioned a couple of posts ago to set up X.

You could use the same format and adapt it to manually Over/Underclock or Over/Undervolt cards on linux using:

Code:

GPUGraphicsClockOffset[0]
GPUMemoryTransferRateOffset[0]
GPUOverVoltageOffset

where the number in square brackets is the performance level.

I haven't yet used it to adjust OC.

[scryptr]

OLD BUGS--

I'd like to thank the coders (t-nelson and sp_) that have finally squashed the ctrl-c bug under Windows.  If only Yaamp were still up and running, I could use my Yaamp-protocol profit switching batch file without Windows hiccuping and destroying the effectiveness of the simple switching method.

And, several miners are clarifying a solo-mining bug that has crept in.  I'm sure that it will get worked out soon.

There was also a cpu-load "bug" just a few CCminer editions back.  The bug used a lot of CPU power, but also increased the hash rate.  It is only with the most recent releases that CCminer can achieve the same or better hash rates.

I'd like to see a command line switch that would allow the miner to engage the CPU for greater hash rates.  On my dedicated rigs I'd engage the CPU, and benefit from the greater hash rate.  On my work computer, I'd leave it out so that my desktop would not freeze.

There was a similar switch in CudaMiner, and it was sometimes effective in mining script.  If the CPU "bug" was ironed out and taught to behave well, I am sure that miners would use it when appropriate.       --scryptr

[zTheWolfz]

Maybe I should say I've not been able to solo mine on Quark algo since b54.  I just tried b56, it just sits there doing nothing.... just like in your screenshot.  B57 does not generate an error message for me, but it also just sits there doing nothing.

Solo mining is unlike pool mining you will not see any output like a pool gives in solo.
Only once you have found a block will it show any output, well you can use -P if you'd
like to see a little more info about what is happening in the background.



The Good The Bad and The Ugly
good: yay!!! bad: hash rate The Ugly: boooo  
Only after a yay or booo does it start to give other readings in solo.

[pallas]

There was also a cpu-load "bug" just a few CCminer editions back.  The bug used a lot of CPU power, but also increased the hash rate.  It is only with the most recent releases that CCminer can achieve the same or better hash rates.

I'd like to see a command line switch that would allow the miner to engage the CPU for greater hash rates.  On my dedicated rigs I'd engage the CPU, and benefit from the greater hash rate.  On my work computer, I'd leave it out so that my desktop would not freeze.

There was a similar switch in CudaMiner, and it was sometimes effective in mining script.  If the CPU "bug" was ironed out and taught to behave well, I am sure that miners would use it when appropriate.       --scryptr

I guess you are referring to the "bug" I introduced when initially submitted the improved neoscrypt kernel.
I removed this:

cudaSetDeviceFlags(cudaDeviceScheduleBlockingSync);

Which looked to induce a little speed gain, without noticing it also produced 100% cpu load.

We could add a commandline option to disable it, but personally I think the hassle and additional power usage doesn't justify less-than-one-percent hashrate gain.
Still if it's optional, I see no reason not to include it (provided that what it does is well explained).
BTW ethereum cudaminer has a similar option.

[sp_]

Maybe I should say I've not been able to solo mine on Quark algo since b54.  I just tried b56, it just sits there doing nothing.... just like in your screenshot.  B57 does not generate an error message for me, but it also just sits there doing nothing.

Solo mining is unlike pool mining you will not see any output like a pool gives in solo.
Only once you have found a block will it show any output, well you can use -P if you'd
like to see a little more info about what is happening in the background.

Tvpruvot has added some stats in the solominer lite total network hashrate in ccminer 1.6.6. I think I will refork and replace all the kernals, but it will take some time. If you donate some more I will do it..

(borring merge work)

[sp_]

There was also a cpu-load "bug" just a few CCminer editions back.  The bug used a lot of CPU power, but also increased the hash rate.  It is only with the most recent releases that CCminer can achieve the same or better hash rates.
I'd like to see a command line switch that would allow the miner to engage the CPU for greater hash rates.  On my dedicated rigs I'd engage the CPU, and benefit from the greater hash rate.  On my work computer, I'd leave it out so that my desktop would not freeze.
There was a similar switch in CudaMiner, and it was sometimes effective in mining script.  If the CPU "bug" was ironed out and taught to behave well, I am sure that miners would use it when appropriate.       --scryptr

I guess you are referring to the "bug" I introduced when initially submitted the improved neoscrypt kernel.
I removed this:
cudaSetDeviceFlags(cudaDeviceScheduleBlockingSync);
Which looked to induce a little speed gain, without noticing it also produced 100% cpu load.
We could add a commandline option to disable it, but personally I think the hassle and additional power usage doesn't justify less-than-one-percent hashrate gain.
Still if it's optional, I see no reason not to include it (provided that what it does is well explained).
BTW ethereum cudaminer has a similar option.

And 50Watt more power on the rig.. So 50 watt for 1KHASH gain

[tbearhere]

  sp  could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx   

I didn't remove it, not sure why it isn't working..

He's probably talking about wallet mining with GBT - coins are moving to newer BTC codebases, which have getwork removed.

This works with release43  but not with release 62 for wallet mining.

ccminer.exe -a quark  -q -o http://localhost:port           < computer  1
ccminer.exe -a quark  -q  -o http://192.168.0.102:port  <  computer 2   Both on the same hub.

Somewhere after release43 it stopped working. Maybe around release50.

Build 54 is the last sp_ build that will solo mine against your wallet.  I have not tried B63, but I'm assuming it will also fail.  I have tried every build from 54 to 62. 

That you GarlukKY.
Now if sp can look into that and add it back in, that would be great.

[tbearhere]

 sp  could you please put the http protocol back in the source code. I can't wallet mine. And djm lyra2v2 is the same. thx    

I didn't remove it, not sure why it isn't working..

He's probably talking about wallet mining with GBT - coins are moving to newer BTC codebases, which have getwork removed.

This works with release43  but not with release 62 for wallet mining.

ccminer.exe -a quark  -q -o http://localhost:port           < computer  1
ccminer.exe -a quark  -q  -o http://192.168.0.102:port  <  computer 2   Both on the same hub.

Somewhere after release43 it stopped working. Maybe around release50.

Build 54 is the last sp_ build that will solo mine against your wallet.  I have not tried B63, but I'm assuming it will also fail.  I have tried every build from 54 to 62.  

My solo test shows it still works in r56 but fails in r57
ccminer.exe -a neoscrypt --no-gbt --no-longpoll -o 127.0.0.1:3333 -u phoenixcoinpc -p x -d 0 -i 10 -l T16x2
I tested r54,r55,r56 & r57. never downloaded r58

you should keep your related wallet open me 2 faced with this problem and solved it like i said

Yes kama  ..absolutely ones wallet must be open and fully synced.