Author

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 968. (Read 2347664 times)

newbie
Activity: 16
Merit: 0
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.
legendary
Activity: 1764
Merit: 1024
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.
sr. member
Activity: 427
Merit: 250
I mentioned these solo mining problems a few pages back.  have to use djm's miner to do any solo mining for now.
member
Activity: 81
Merit: 10
 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.
full member
Activity: 231
Merit: 150

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:

full member
Activity: 140
Merit: 100

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
full member
Activity: 231
Merit: 150

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?
full member
Activity: 140
Merit: 100

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 ?
full member
Activity: 231
Merit: 150

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.
full member
Activity: 140
Merit: 100
 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
full member
Activity: 231
Merit: 150
 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
member
Activity: 81
Merit: 10
  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. 
member
Activity: 70
Merit: 10
 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
legendary
Activity: 3164
Merit: 1003
 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.
member
Activity: 70
Merit: 10
Application dont exit after pool disconnect (-r 3 -R 10). Terminating thread and wait for somthing. -q dont work. I am using win10.

Mind pasting(or screenshot) the exact output at exit?  How long are you waiting?  I've seen the GPU threads take 10-15s to exit without an additional ctrl+c to abort them (Linux).
More then 30 minutes. Last string is "terminating workio threads". Ctrl+C works good. Thats all...

I'm sorry, I don't seem to be comprehending the issue.  It sounds like it is working as intended.  Maybe you could post the entire output from the first "CTRL_C_EVENT received, ..." line to the end?

The design behavior is on first ctrl+c, we signal all threads to exit and wait for them to do so on their own.  Since it may take quite some time for the current hash job to finish, a second ctrl+c will signal to abort GPU work.  The application should exit very quickly after the second ctrl+c.


Though I see now that we're killing the threads in the wrong order.  The work from allowing the GPU threads to finish is just thrown away...  Something more for the TODO list. Smiley
[2015-09-01 23:36:03]←[31m Stratum connection failed: Failed to connect to cnote.mine-pool.net port 3800: Timed out←[0m
[2015-09-01 23:36:03]←[31m ...terminating workio thread←[0m
[2015-09-01 23:41:09] CTRL_C_EVENT received, exiting once miner jobs complete. Ctrl+C again to abort miner jobs←[0m
[2015-09-01 23:41:10] workio thread dead, exiting.←[0m


Yup, looks good.  Looks like there are a lot of blind sleeps might be unnecessarily holding us up in various cases.  One more for the TODO.
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
Can you display a screenshot?
Just a lot of per thread hashrate lines, at least 10 times the normal output.
I'm experiencing reduced performance on the pool as well, tried neoscrypt and x11.
The power meter shows recurring short periods of lower usage.
Really weird...

I checked in another fix. Seems to increase the hashrate. The flooding was causing a drop in hashrate.

About the excessive output: now it's improved, still more than previous versions.
About hashrate and power usage: not sure it's related, maybe a hardware problem, will be watching it closely.
full member
Activity: 173
Merit: 100
Which brothers to help me set up 750TI quarks and lyra2v2 the .bat? Thank you.

BATCH FILE--

:loop

ccminer -a lyra2v2 -i 19 -o stratum+tcp:\\poolspecificaddress:port -u username.worker1 -p pswd

pause
goto loop

Or, for quark, substitute the following command line:

ccminer -a quark -i 24 -o stratum+tcp:\\poolspecificaddress:port -u username.worker1 -p pswd

You can simply run the batch without the loop structure, but the loop makes small changes in the command line simple. That is, while the loop is paused, you could change the command line with notepad, save, and then trigger the loop and re-run the batch file.

--scryptr

[/quoteThank you very much.]
hero member
Activity: 677
Merit: 500
Application dont exit after pool disconnect (-r 3 -R 10). Terminating thread and wait for somthing. -q dont work. I am using win10.

Mind pasting(or screenshot) the exact output at exit?  How long are you waiting?  I've seen the GPU threads take 10-15s to exit without an additional ctrl+c to abort them (Linux).
More then 30 minutes. Last string is "terminating workio threads". Ctrl+C works good. Thats all...

I'm sorry, I don't seem to be comprehending the issue.  It sounds like it is working as intended.  Maybe you could post the entire output from the first "CTRL_C_EVENT received, ..." line to the end?

The design behavior is on first ctrl+c, we signal all threads to exit and wait for them to do so on their own.  Since it may take quite some time for the current hash job to finish, a second ctrl+c will signal to abort GPU work.  The application should exit very quickly after the second ctrl+c.


Though I see now that we're killing the threads in the wrong order.  The work from allowing the GPU threads to finish is just thrown away...  Something more for the TODO list. Smiley
[2015-09-01 23:36:03]←[31m Stratum connection failed: Failed to connect to cnote.mine-pool.net port 3800: Timed out←[0m
[2015-09-01 23:36:03]←[31m ...terminating workio thread←[0m
[2015-09-01 23:41:09] CTRL_C_EVENT received, exiting once miner jobs complete. Ctrl+C again to abort miner jobs←[0m
[2015-09-01 23:41:10] workio thread dead, exiting.←[0m
legendary
Activity: 1764
Merit: 1024
What sort of incentive is there to use a fee based miner when the current version is free, besides it's doing the right thing? And are you really bitching about having to do a little bit of work to earn money?It really isn't that hard to setup a pool and you know it, you just don't want to have to do the tiniest bit extra work to make it happen (which shows the whole reason we're stuck where we are right now).


Actually, if the miner is good enough, this is kind of bad. One pool getting MASSIVE hashrate, or multiple pools controlled by one person? It's a very quick road to centralization.

2% hashrate isn't massive.

That aside, a developer doesn't even need to make their own pool. They just need A pool. You don't even need to do any work on this besides write in the extra code to divert 2 shares every 100 (although there is still the Lyra difficulty issue that hasn't been resolved yet).

I really don't think a united green team would case an issue related to centralization but even then, we could cross that bridge once we get there.
I think I'm just talking to the wall once again as I got used to being ignored when it comes to serious discussions but what the hell, I'll bite once again; so really as many people are working on optimizing (cuda based) miners there really isn't any improvements towards monetizing it. Personally, I'm using a closed source ccminer fork for about six months now so I'm not really bothered by what's going on with the open source scheme but still, I think there should have been some improvements regarding monetization. Unfortunately there was none.

There's always the argument towards open source fee based miners but there wasn't even a (major) release to at least try the freaking thing. In reality, we, in this thread are in the tiny minority when it comes to nvidia based mining and sites like cryptominingblog and several other sites are the ones distributing the software towards potentially thousands of miners who might not even know what BCT is or might not even speak English. Surely, an open source fee based miner would at least worth a try by now to see how much would it earn from both dedicated and imbecile miners - even if it's a compelte failure - but there wasn't any (major) release of it. Just look at how many people would donate to tsiv towards his/her lyra2rev2 miner.

And then there's yaamp which got open sourced not so recently and even that opportunity got ignored. Maybe I'm just oversimplifying it, but a yaamp based multipool with decent fees and full transparency would really motivate coders to improve code especially if their fee was based on their measured improvements (%) on a per algo basis after an established baseline.

I really think the coders of the community should put their heads together and come up with something reasonable because I'm sure appreciative fans wouldn't mind paying for improvements.

Definitely... It's not just improvements. It seems like Nvidia coders are starting to stop distributing their kernels and optimizations as they don't receive enough back.'I don't get enough donations' seems to be common place now days. I don't want that to happen. A continual fee based system should offer incentive over time. A donation system will ALWAYS be sporadic and will never be enough for some people, that's when it's time to change to something else.

It's also true that a fee based system hasn't been really tried. It STILL works for Claymore and there are still people mining with his miner. That's a perfect example of it working properly. He's still at 2% or 2.5%. Claymore also updated his miner quite regularly during the hay days of Cryptonote. That's what people want if there is a percentage fee associated with it (features wouldn't hurt either).

And yeah, it seems like people like complaining about not getting enough money here, but not doing anything about it. Maybe then because it seems like they're offering a product and then would have to support it? A obligation?

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).
member
Activity: 70
Merit: 10
Application dont exit after pool disconnect (-r 3 -R 10). Terminating thread and wait for somthing. -q dont work. I am using win10.

Mind pasting(or screenshot) the exact output at exit?  How long are you waiting?  I've seen the GPU threads take 10-15s to exit without an additional ctrl+c to abort them (Linux).
More then 30 minutes. Last string is "terminating workio threads". Ctrl+C works good. Thats all...

I'm sorry, I don't seem to be comprehending the issue.  It sounds like it is working as intended.  Maybe you could post the entire output from the first "CTRL_C_EVENT received, ..." line to the end?

The design behavior is on first ctrl+c, we signal all threads to exit and wait for them to do so on their own.  Since it may take quite some time for the current hash job to finish, a second ctrl+c will signal to abort GPU work.  The application should exit very quickly after the second ctrl+c.


Though I see now that we're killing the threads in the wrong order.  The work from allowing the GPU threads to finish is just thrown away...  Something more for the TODO list. Smiley
Jump to: