CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1215.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: SavellM on December 01, 2014, 04:27:29 AM

Would that be like this?
ccminer52.exe -q -r 14 -R 10 -a x11

Or like:
ccminer52.exe -q -r 3 -R 14 -a x11
Or how would you do it?
Whats the diff between r and R?

The R option is to ensure that the miner try to reconnect when it fails to connect. For some reason the q option give higher hashrates with less load on the cpu if you have more than 1 card in the rig. I need to look into that. The -i parameter is important, The defaults might not be good for your card. Start with -i 19 , -i 19.5 etc. untill you find the best.

jpouza

legendary

Activity: 2716

Merit: 1116

Quote from: SavellM on December 01, 2014, 04:27:29 AM

Quote from: jpouza on December 01, 2014, 01:56:16 AM

Little pump with r14, 980 at 1466MHz now doing 9,7MH/s X11.

Would that be like this?
ccminer52.exe -q -r 14 -R 10 -a x11

Or like:

ccminer52.exe -q -r 3 -R 14 -a x11

Or how would you do it?

Whats the diff between r and R?

Hum?

r14 I mean release14...
I use -i 20.5 for intensity

SavellM

sr. member

Activity: 305

Merit: 250

Quote from: jpouza on December 01, 2014, 01:56:16 AM

Little pump with r14, 980 at 1466MHz now doing 9,7MH/s X11.

Would that be like this?
ccminer52.exe -q -r 14 -R 10 -a x11

Or like:

ccminer52.exe -q -r 3 -R 14 -a x11

Or how would you do it?

Whats the diff between r and R?

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

The default projectfile from github only contain compute_50 and sm_50 (750ti) You need to add compute_52 and sm_52 in the cuda prefs in the project file.

coinut

full member

Activity: 253

Merit: 100

got beta 14 up and running

Problem was still there.

changed to another pool and now showing full hashrate Grin

running nice and smooth.

Also tried my hand at compiling your miner sp from your Github

downloaded vs 2010/12/13 cuda 6.0 and 6.5

after trying one night i could only get your code to compile with vs 2013. It spat out a ccminer roughly the same size as the ccminer52 in your releases.
Jammed the compiled ccminer into my rig and I just got error failed to start or close to. I suspect that I compiled a version of your code compatible with gtx 970/980
not sure though.

How do you compile your code to work with 750 ti ?

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: coinut on December 01, 2014, 02:37:00 AM

No problem

Thanks for the reply
downloading beta 14 now, if I still have problems I will test out that command

Release 13 has a bug in x11 as well. No block's will be found. Solomining doesn't work. And x13/x15 got alot of HW errors. Release 14 should fix this.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: jpouza on December 01, 2014, 02:42:53 AM

Not every pool support diff. adjustment via command line I think.
Here I use d=0.16 and d=0.32 as recommended by the pool, big hash => more diff.

Yes, on 970/980 cards where the intesity is high, a higher diff is bether.

jpouza

legendary

Activity: 2716

Merit: 1116

Not every pool support diff. adjustment via command line I think.

Here I use d=0.16 and d=0.32 as recommended by the pool, big hash => more diff.

coinut

full member

Activity: 253

Merit: 100

No problem

Thanks for the reply

downloading beta 14 now, if I still have problems I will test out that command

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: coinut on December 01, 2014, 02:14:37 AM

Was just trying out your miner last night and today, got my 6x 750ti rig running your beta 13 release.
My cards are all flashed and overclocked running x11 mining darkcoin all last night to test your miner out and I seem to have a problem with the pool not showing the hashrate that I see on my end.
I have my bat file setup to run all cards in the one miner and it reads about 18,100 khash on x11
Just then I had a look at the hashrate graph in the pool and it seems to read on average 11,000 khash after about 12 hours hashing
anyone have this problem?
anyone got any ideas on a fix?

PS
SP I just sent you a donation of 2 drk man, great work and thank you

Tnx

First, upgrade to release 14.

Your difficulty might have been set too high. With a high diff the rates will fluctate alot.
You can try to use the password -p d=0.02 to try to force the difficulty on the pool to be lower.

jpouza

legendary

Activity: 2716

Merit: 1116

Quote from: coinut on December 01, 2014, 02:14:37 AM

Was just trying out your miner last night and today, got my 6x 750ti rig running your beta 13 release.

My cards are all flashed and overclocked running x11 mining darkcoin all last night to test your miner out and I seem to have a problem with the pool not showing the hashrate that I see on my end.

I have my bat file setup to run all cards in the one miner and it reads about 18,100 khash on x11

Just then I had a look at the hashrate graph in the pool and it seems to read on average 11,000 khash after about 12 hours hashing

anyone have this problem?

anyone got any ideas on a fix?

PS

SP I just sent you a donation of 2 drk man, great work and thank you

I don't have this issue here, throwing 35MH/s x11 avg hash rate, pool reporting about 32-33MH/s avg, I think it is normal.

3x980+1x750Ti RIG#1 plus 1x750Ti alone another PC, I think this is a pool related problem, don't know for sure.

share image

coinut

full member

Activity: 253

Merit: 100

Was just trying out your miner last night and today, got my 6x 750ti rig running your beta 13 release.

My cards are all flashed and overclocked running x11 mining darkcoin all last night to test your miner out and I seem to have a problem with the pool not showing the hashrate that I see on my end.

I have my bat file setup to run all cards in the one miner and it reads about 18,100 khash on x11

Just then I had a look at the hashrate graph in the pool and it seems to read on average 11,000 khash after about 12 hours hashing

anyone have this problem?

anyone got any ideas on a fix?

PS

SP I just sent you a donation of 2 drk man, great work and thank you

jpouza

legendary

Activity: 2716

Merit: 1116

Little pump with r14, 980 at 1466MHz now doing 9,7MH/s X11.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: grendel25 on December 01, 2014, 12:47:21 AM

could folks share there command line? this is mine:

Code:

ccminer.exe -q -r 3 -R 10 -a x13 --no-color -o stratum+tcp://yaamp.com:3633 -u xxx -p xxx

grendel25

legendary

Activity: 2296

Merit: 1031

could folks share there command line? this is mine:

Code:

ccminer.exe -t 3 --algo=x11 -o stratum+tcp://us-west01.miningrigrentals.com:3333 -u euser.9 -p x

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Uploaded new binaries. x13 and x15 fixed, and should be a littlebit faster than before. fugue +2%. Benchmark mode is abit uncorrect. I get higher x13 rates with low difficulty. When mining on a pool, rates are bether

http://www.filedropper.com/release14.

Bombadil

hero member

Activity: 644

Merit: 500

Quote from: sp_ on November 30, 2014, 08:36:28 AM

New build from github.

-x15 fixed for 970/980 cards
-less GPU xx result for xx is not in range (hardware)

http://www.filedropper.com/release13

Can you update to tpruvot's latest API? (Like poolinfo etc). I'm using that in my monitoring tool ^^
Nice work btw! Seems like my donation earlier was worth it ^^"
Too bad my gtx760 doesn't work anymore Sad

Guess you kicked out compute 3.0 Wink

jpouza

legendary

Activity: 2716

Merit: 1116

r13 is fine here, giving 9,6MH/s w/ no hw errors at all on my 980s at 1466MHz@58ºC stock voltage , 490/490 accepted, flawless till now.

Cheers

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Looks like Schleicher has submitted a bugfix. Will try it out.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

yes, the last version is broken in x13 and x15. I am working on a fix

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