CCminer(SP-MOD) Modded GPU kernels.

[SDFG]

khash/s ))

[chrysophylax]

well we have had the donation miner running via the donation link on westahsh without any major issues that we can speak of ...
obviously issues arise here and then - but westhash is a lot more stable that yaamp ...
it really looks like a yaamp stratum issue - so we will keep the donation for quark on westhash until yaamp can fix it ...
x11 had been running for hours and the stratum proxy is still connected with yaamp ...
so - agreed ... its a yaamp pool issue ...
anyone know anyone there to inform them? ... or just a support ticket ...
btw - havent had time to setup the other algos - but they will be up within the next day ... too much on my plate unfortunately ...
#crysx

Westhash is looking good, thanks alot for your support.

all good sp ...

tanx so much for putting a great deal of effort into this highly optimized miner ...

when the official domain ( granitecoin.com ) propagates - we will have the systems permanently setup for donations to you and the other awesome devs ...

so the only change that will be required from these test systems is to drop the 'x' on granitecoinx.com ... everything else will be the same ...

im actually quite interested in the spreadx11 algo ... the private miner works really well and works seamlessly with the pool we mine on ( nonce-pool ) ...

you have incorporated the spread algo into ccminer - but this just refuses to mine with the pool altogether ...

are you going to have this supported with ccminer and working with the pool ( like the private spreadminer ) with all the optimizations? ...

#crysx

[sp_]

khash/s ))

This fork only works for the latest NVIDIA cards. Compute 5.0 or newer

http://en.wikipedia.org/wiki/CUDA

Compute 3.5 might work, but it is not tested in a while. (you need to build your own binaries and add compute_35 in the projectfile/makefile)

[chrysophylax]

khash/s ))

This fork only works for the latest NVIDIA cards. Compute 5.0

http://en.wikipedia.org/wiki/CUDA

Compute 3.5 might work, but it is not tested in a while. (you need to build your own binaries and add compute_35 in the projectfile/makefile)

arent 750ti cards compute 5.0? ...

#crysx

[sp_]

all good sp ...
im actually quite interested in the spreadx11 algo ... the private miner works really well and works seamlessly with the pool we mine on ( nonce-pool ) ...

It's been a while since the last private spreadcoin miner. I might release build 8 to the donators this weekend

[sp_]

khash/s ))

This fork only works for the latest NVIDIA cards. Compute 5.0
http://en.wikipedia.org/wiki/CUDA
Compute 3.5 might work, but it is not tested in a while. (you need to build your own binaries and add compute_35 in the projectfile/makefile)

arent 750ti cards compute 5.0? ...
#crysx

yes they are.  But the 660Ti is compute 3.0.

[SDFG]

Thank you)

[chrysophylax]

khash/s ))

This fork only works for the latest NVIDIA cards. Compute 5.0
http://en.wikipedia.org/wiki/CUDA
Compute 3.5 might work, but it is not tested in a while. (you need to build your own binaries and add compute_35 in the projectfile/makefile)

arent 750ti cards compute 5.0? ...
#crysx

yes they are.  But the 660Ti is compute 3.0.

ok - agreed ... but 75% of the farm we have are gigabyte 750ti oc lp cards ...

the spread algo in this ccminer fork wont work with the pool - but the private spreadminer does - and that is built for compute 5.0 also isnt it? ...

or am i missing the point here ... as i am really tired right this minute ...

#crysx

[sp_]

ok - agreed ... but 75% of the farm we have are gigabyte 750ti oc lp cards ...
the spread algo in this ccminer fork wont work with the pool - but the private spreadminer does - and that is built for compute 5.0 also isnt it? ...
or am i missing the point here ... as i am really tired right this minute ...
#crysx

You are mixing threads here. There was a guy who asked if he could use this version to mine on the gtx660ti.
Your gigabytes will work just fine, and I will make you richer. he-he

[chrysophylax]

ok - agreed ... but 75% of the farm we have are gigabyte 750ti oc lp cards ...
the spread algo in this ccminer fork wont work with the pool - but the private spreadminer does - and that is built for compute 5.0 also isnt it? ...
or am i missing the point here ... as i am really tired right this minute ...
#crysx

You are mixing threads here. There was a guy who asked if he could use this version to mine on the gtx660ti.
Your gigabytes will work just fine, and I will make you richer. he-he

not mixing threads at all sp ... there is -a spread algo in your fork - and i tried using it only to find it will not run with the pool that we mine ( which is nonce-pool ) ...

the private ( paid ) spreadminer that you optimized and forked from tsiv works just fine with the pool ...

what i was wondering is whether the -a spread algo that in THIS fork of ccminer ( that doesnt work with pool mining ) is going to be replaced with the optimized version that you sent privately ( which works flawlessly with the pool ) and will be incorporated into this fork? ...

that would be fantastic if this is so ... and we would have no issue donating much more hashpower to see that happen ...

#crysx

[sp_]

what i was wondering is whether the -a spread algo that in THIS fork of ccminer ( that doesnt work with pool mining ) is going to be replaced with the optimized version that you sent privately ( which works flawlessly with the pool ) and will be incorporated into this fork? ...
that would be fantastic if this is so ... and we would have no issue donating much more hashpower to see that happen ...

Ok. I can merge the kernals into the latest branch. Still private for the donators.

[chrysophylax]

what i was wondering is whether the -a spread algo that in THIS fork of ccminer ( that doesnt work with pool mining ) is going to be replaced with the optimized version that you sent privately ( which works flawlessly with the pool ) and will be incorporated into this fork? ...
that would be fantastic if this is so ... and we would have no issue donating much more hashpower to see that happen ...

Ok. I can merge the kernals into the latest branch. Still private for the donators.

if you want to keep it private - that is entirely up to you ...

but that would be great if you could ...

the last one we compiled here works great - and you have done some great work with the optimizations ...

that is so much appreciated sp ...

tanx ...

#crysx

[antonio8]

what i was wondering is whether the -a spread algo that in THIS fork of ccminer ( that doesnt work with pool mining ) is going to be replaced with the optimized version that you sent privately ( which works flawlessly with the pool ) and will be incorporated into this fork? ...
that would be fantastic if this is so ... and we would have no issue donating much more hashpower to see that happen ...

Ok. I can merge the kernals into the latest branch. Still private for the donators.

Any updates soon on the private cryptonight miner soon?

[sp_]

I think cryptonight should be merged into ccminer as well.

[chrysophylax]

I think cryptonight should be merged into ccminer as well.

this fork is going to be one hell of a miner ... you could say a forking hell of a miner ...

tanx so much sp ...

donations still mining for you ... will add the other algos tomorrow afternoon adelaide time ...

westhash is running fine with quark - which confirms it is a yaamp issue ...

#crysx

[flipclip]

Which improvement we could expect on QUBIt with GTX970/750Ti

...
Especially when I have both of the cards on same rig - its total mess using the "g" parameter...

Couldn't you start up two instances of ccminer utilizing the -d?  One instance would be for your 970 the other instance for your 750Ti, and you could set the -i -g parameters per instance.

[tbearhere]

I have a question, if sometimes on yaamp the connection is lost and isn't restarting, i would like to add another pool. How can i do this. (with last ccminer1.5.47)
Am i the only one who lost connection on yaamp?
For now i use :
ccminer.exe -R 5 -T 5 -q -a quark -o stratum+tcp://yaamp.com:4033 -u 5LA1mw7JZKKVf3LK9KLAJSzQZzNwU9Z3Rp -p d=0.002

Can someone explain me what i should add to insert another pool after this one? (round robin, failover or someting else)

P.S sometime if i closed ccminer and restart it im able to log again and mine ...

Thanks for the help

LOOPER--

This is how:

:loop

ccminer.exe -r 1 -R 5 -a quark   -o stratum+tcp://us-west01.miningrigrentals.com:3333 -u me -p x  -d 0,1,2

taskkill -t -f /im ccminer*
timeout -t 1

ccminer.exe -r 1 -R 5 -a quark   -o stratum+tcp://us-central01.miningrigrentals.com:3333 -u me  -p x  -d 0,1,2

taskkill -t -f /im ccminer*
timeout -t 1

goto loop

This is a slight revision of Bathrobehero's script.  Use the "-R" switch, and the "-r" switch.  The script above puts in a 5 second delay (-R 5) before switching to the lower pool in the batch file, and to try to reconnect once (-r 1).  Yaamp uses it to switch between algos.  As used above, it switches between pools.  Yamp.com has an example script linked on the homepage for algo switching.

If you execute the command "ccminer --help >> help.txt" in a windows command box, you will get a text file explaining all the ccminer commands.

--scryptr

This looks good to me but the problem still is at the goto loop I think.  Again at the crash line ( goto loop ) it says can't find ccminer. Or is it the 1 second time delay that may keep it from crashing ?

CRASHES--

I think that may be the intention for "-t 1", but now I wonder if crashes are because of overclocking ccminer for performance.  The batch file works, but ccminer triggers the "program stopped working" error messages.  I don't know if ccminer is supposed to stay runing between connection attempts.       --scryptr

My pool just went down and ccminer crashed on my other 2 computers. This one didn't and never does and all computers are overclocked. Ones that crashed are vista and windows 8.1 and this one is windows 8.1. Now I'll try the -t 1 right before the goto loop to see if that helps. That  * right after ccminer* is the same as .exe like this   ccminer*  same as  ccminer.exe  ??  
Thx
EDIT: I just disconnected my ithernet cable and it went through the commands .. but in the command window it says ccminer.exe can't be found. But it didn't crash that way.
ps What cbuchner1 put in cudaminer needs to be put into ccminer. With cudaminer these bat files will work..even a 1 bat file restart like...

:start
cudaminer.exe -l T5x24 -C 2 -i 0 -o stratum+tcp://us.coinium.org:3340 -u me -p x -d 0 --time-limit 900
goto start

[DragonSlayer]

Which improvement we could expect on QUBIt with GTX970/750Ti

...
Especially when I have both of the cards on same rig - its total mess using the "g" parameter...

Couldn't you start up two instances of ccminer utilizing the -d?  One instance would be for your 970 the other instance for your 750Ti, and you could set the -i -g parameters per instance.

To the best of my knowledge, -g does not work with -d parameters.  I hope someone can prove me wrong.

[flipclip]

Which improvement we could expect on QUBIt with GTX970/750Ti

...
Especially when I have both of the cards on same rig - its total mess using the "g" parameter...

Couldn't you start up two instances of ccminer utilizing the -d?  One instance would be for your 970 the other instance for your 750Ti, and you could set the -i -g parameters per instance.

To the best of my knowledge, -g does not work with -d parameters.  I hope someone can prove me wrong.

I just got the idea from what sp_ posted earlier:

Can the g parameter be used per device, example two cards set differently with -g 4,3 ?  (per if you are running a mix of cards)

you have to do

-d 3,4 and then -g x

Not sure it works.

[bathrobehero]

Offtopic: Just as a reminder for people with TDP modded Gigabyte 750 Ti OC (GV-N75TOC-2GI) cards; expect your cards to die. Out of 6, now 2 of them died on me in 11 months (no fan, no screen, nothing). And I 'only' increased the TDP to 45W (instead of the usual 60W) and only after 3-4 months of stock use. I usually had +140 to +170 mhz on the core with stock mem clocks. Temps were always around 60°C with the max temp target set to 65°C.

I read about others with similar issues a couple of times. An old post but this was close by:

blahij
May 11th, 2014 at 03:08
I had 6 flashed hashing @ 300kh for a month or two. Had two burn themselves out day before and then another the next day.
Temps were fine and I can see some discoloring on the back and one component looks blown-out?
Mine were Gigbyte and I used the posted BIOS on this site.

Quote from http://cryptomining-blog.com/1014-how-to-increase-the-geforce-gtx-750-ti-power-target-limit/