CCminer(SP-MOD) Modded GPU kernels.

[flipclip]

The new gtx 960 might fail on the default settings because the intensity is set to high for compute 5.2 devices. How much memory are they planning to ship with the new cards?

The fix will be to set the intensity manually with the -i parameter. f.eks -i 19

For people with mixed cards (or thinking about mixing in a 960) in their rigs, the -i parameter is not a per card setting, so they'll either need to run seperate ccminer instances or hope the same -i parameter works across cards  .  Just something for people to think about.

[flipclip]

Quark:
v28= ~11,160 kH/s
v30= ~11,441 kH/s

x11:
v28= ~5,730 kH/s
v30= ~5,850 kH/s

lyra2:
v28= ~1,350 kH/s
v30= ~1,350 kH/s

Mjollnir:
v30=~21,000 MH/s

(2 750Ti's, no overclock)

[djm34]

anyone knows how, with visual studio, to get the "release" directory with less crap in it (I still need the ptx though...) ?

[Bombadil]

anyone knows how, with visual studio, to get the "release" directory with less crap in it (I still need the ptx though...) ?

Shift-delete the crap

[djm34]

anyone knows how, with visual studio, to get the "release" directory with less crap in it (I still need the ptx though...) ?

Shift-delete the crap

yeah but it comes back...

[Bombadil]

anyone knows how, with visual studio, to get the "release" directory with less crap in it (I still need the ptx though...) ?

Shift-delete the crap

yeah but it comes back...

Euh.. Nuke it?

[scryptr]

SP_ v30-

Both rigs increased their hash rates by about 900kh/s each mining quark.       --scryptr

EDIT:  Both rigs still running steady, nearing 1000 accepts each at about 1% error rate.       --scryptr

[sp_]

I just submitted groestl speedup part 2. quark is up another 30KHASH. x11 around 15-20KHASH. x13 -10KHASH

Also submitted 7KHASH more in x14 making it a total for x14 around 16KHASH boost.

All on the 750ti.

edit: perhaps a bit early checkin groestl coin is broken :/

[chrysophylax]

I just submitted groestl speedup part 2. quark is up another 30KHASH. x11 around 15-20KHASH. x13 -10KHASH

Also submitted 7KHASH more in x14 making it a total for x14 around 16KHASH boost.

All on the 750ti.

edit: perhaps a bit early checkin groestl coin is broken :/

sp - the miner seems to running stable since i set them mining quark last night ...

is it wise to stay mining with the previous compile - or compile a new one with these increases and restart the quark mining donation?

im just worried about stability at the moment - thats all ...

what do you think?

#crysx

[sp_]

The latest checkin breaks the hash. So please wait.  Tried to solve it, but went to the pub instead cheers

[chrysophylax]

The latest checkin breaks the hash. So please wait.  Tried to solve it, but went to the pub instead cheers

hehehe - all good - still mining for a few more beers for you mate ...

have you checked how its going with yaamp / quark? ... happy with what you see with the latest build and hashrates? ...

njoi ...

#crysx

[jpouza]

Quark:
v28= ~11,160 kh/s
v30= ~11,441 kh/s
x11:
v28= ~5,730 kh/s
v30= ~5,850 kh/s
lyra2:
v28= ~1,350 kh/s
v30= ~1,350 kh/s
(2 750Ti's, no overclock)

Try groestl or diamondgroestl.  

You can see on the commit on github that this is groestl speedup part 1. I have part 2 soon ready for checkin, but it is currently mixing the bits, and produce wrong results. Lyra is not using the bitslice groestl (killer groestl)
so my improvements will not have an effect. But I guess if I swap the implementation, Lyra2 will get a boost as well. Did you try that DJM34?

About the spreadcoinminer:

I will integrate and optimize TSIV's spreadcoin implementation into the latest fork of ccminer. I will send out beta versions for a fee of 0.1 BTC. The beta will be a windows executable.
I might send out more than one exe in the testing phase, if I manage to optimize more.
I will publish the sourcecode after one month of betatesting. (When I publish the sourcecode, the spreadcoin will spread bether, and secure the coin)
 
The current speed will be announced when the exefile is released. Hopefully next weekend 25-26 january.

The estimated speed increase is 30-40% on the 980 cards

If you want a early seat, you can start donating to my BTC  or DRK adress in my signature.The current speed will be announced when the exefile is released. Hopefully next weekend 25-26 january.

For the SpreadX11 opt. miner beta:

d1bf1798d350a590b056758975cae0a9cc3a724a083c48cc3d26f05e03758c39

Just waiting to get it and compensate my 2x750Ti lost.

[sp_]

I have now fixed the groestl speedup 2 on github. Klaus_t has been optimizing quark, so I am waiting for a pull request, and then build release 31.

[Bombadil]

I have now fixed the groestl speedup 2 on github. Klaus_t has been optimizing quark, so I am waiting for a pull request, and then build release 31.

Didn't you say release 30 was the last one? J/k, not complaining ^^"
Know the feel too of not being able to let a project go, still so much to do

[sp_]

I have now fixed the groestl speedup 2 on github. Klaus_t has been optimizing quark, so I am waiting for a pull request, and then build release 31.

Didn't you say release 30 was the last one? J/k, not complaining ^^"
Know the feel too of not being able to let a project go, still so much to do

No, still more hash to make. Found some pickings in the x13 algo(fugue) but will have to wait.
I am moving the spreadcoin fork into my ccminer fork.

[chrysophylax]

I have now fixed the groestl speedup 2 on github. Klaus_t has been optimizing quark, so I am waiting for a pull request, and then build release 31.

Didn't you say release 30 was the last one? J/k, not complaining ^^"
Know the feel too of not being able to let a project go, still so much to do

No, still more hash to make. Found some pickings in the x13 algo(fugue) but will have to wait.
I am moving the spreadcoin fork into my ccminer fork.

yay yay yay ...

ok - im calm ... im calm ...



#crysx

[crzyblue]

[2015-01-17 10:44:32] NVAPI GPU monitoring enabled.
[2015-01-17 10:44:32] 1 miner thread started, using 'x11' algorithm.
[2015-01-17 10:44:32] Stratum difficulty set to 0.01
Cuda error in func 'x11_simd512_cpu_init' at line 641 : invalid texture referenc
e.

I get this error every time I try to use release 30

[sp_]

Your card is too old. Release30 is compiled for compute 5.0 and 5.2 only

[crzyblue]

GTX 650 too old?

[Bombadil]

[2015-01-17 10:44:32] NVAPI GPU monitoring enabled.
[2015-01-17 10:44:32] 1 miner thread started, using 'x11' algorithm.
[2015-01-17 10:44:32] Stratum difficulty set to 0.01
Cuda error in func 'x11_simd512_cpu_init' at line 641 : invalid texture referenc
e.

I get this error every time I try to use release 30

Thought so already IIRC, you're skipping compute3.0 since release 10-ish?
Been using the tpruvot branch for my 760, is also a bit more up to date with api etc

GTX 650 too old?

Yep, seems like it. You can't blame sp_, the improvements he makes, make use of features not existing in cards with a compute lower than 5.0, so just keep on using the best older one for those cards.