CCminer(SP-MOD) Modded GPU kernels.

[pallas]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)

Compute 5.2 has bether launchconfigurations.

OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain!
but now lyra works and I get about 700 Kh/s more on a single 970 :-)

[chrysophylax]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)

Compute 5.2 has bether launchconfigurations.

OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain!
but now lyra works and I get about 700 Kh/s more on a single 970 :-)

awesome ...

where do you get the 5.2 patch for cuda 6.5? ...

i still have to manually edit the Makefile.am to stop it trying to compile compute 5.2 ...

great work though ...

#crysx

[pallas]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)

Compute 5.2 has bether launchconfigurations.

OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain!
but now lyra works and I get about 700 Kh/s more on a single 970 :-)

awesome ...

where do you get the 5.2 patch for cuda 6.5? ...

i still have to manually edit the Makefile.am to stop it trying to compile compute 5.2 ...

great work though ...

#crysx

- tried the deb file and failed
- downloaded the run file for cuda 6.5 9xx cards from nvidia website
- had to manually install the latest driver using the run file, downloaded separately (the one provided in the toolkit isn't compatible with the latest kernels)
- had to remove everything nvidia related on the system and other cleanups
- had to install gcc-4.7 and modify the Makefile.am in order to use it

and probably some other things I forgot....

[chrysophylax]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)

Compute 5.2 has bether launchconfigurations.

OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain!
but now lyra works and I get about 700 Kh/s more on a single 970 :-)

awesome ...

where do you get the 5.2 patch for cuda 6.5? ...

i still have to manually edit the Makefile.am to stop it trying to compile compute 5.2 ...

great work though ...

#crysx

- tried the deb file and failed
- downloaded the run file for cuda 6.5 9xx cards from nvidia website
- had to manually install the latest driver using the run file, downloaded separately (the one provided in the toolkit isn't compatible with the latest kernels)
- had to remove everything nvidia related on the system and other cleanups
- had to install gcc-4.7 and modify the Makefile.am in order to use it

and probably some other things I forgot....

yup ... welcome to linux ...

but once you get it running ... you wont have to do much else to it again ...

until the next version of course ...

ill stick to manually editing sp's Makefile.am ...

too much work for me at the moment ...

tanx ...

#crysx

[djm34]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)

Compute 5.2 has bether launchconfigurations.

OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain!
but now lyra works and I get about 700 Kh/s more on a single 970 :-)

awesome ...

where do you get the 5.2 patch for cuda 6.5? ...

i still have to manually edit the Makefile.am to stop it trying to compile compute 5.2 ...

great work though ...

#crysx

- tried the deb file and failed
- downloaded the run file for cuda 6.5 9xx cards from nvidia website
- had to manually install the latest driver using the run file, downloaded separately (the one provided in the toolkit isn't compatible with the latest kernels)
- had to remove everything nvidia related on the system and other cleanups
- had to install gcc-4.7 and modify the Makefile.am in order to use it

and probably some other things I forgot....

the easiest way is to compile cuda directly (the run file ?) with --override because gcc is never the one used by nvidia

[bensam1231]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)

Compute 5.2 has bether launchconfigurations.

Will you be selling your private version at any point in the future?

[joblo]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)

Compute 5.2 has bether launchconfigurations.

OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain!
but now lyra works and I get about 700 Kh/s more on a single 970 :-)

awesome ...

where do you get the 5.2 patch for cuda 6.5? ...

i still have to manually edit the Makefile.am to stop it trying to compile compute 5.2 ...

great work though ...

#crysx

pallas:

I prefer using the run file because it gives the option not to install the drivers. With the dist package
you get the included drivers whether you want them or not, and the're usually old.

crysx:

The 5.2 version of cuda is a full package, not a patch, that adds support for compute 5.2. Whether you
choose to use 5.2 it is still determined by Makefile.am. There's no harm in compiling for 5.2 when you
don't need it as long as you also include the compute versions you do need. It just takes longer to compile
and the executable is larger.

[bensam1231]

Anyone know if there is a new miner or private miner out right now? All the algos are taking a crap right now.

[pallas]

The deb doesn't include the drivers but it depends on them, and a specific version. That was the problem.

[sp_]

I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)
Compute 5.2 has bether launchconfigurations.

OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain!
but now lyra works and I get about 700 Kh/s more on a single 970 :-)

If you look in the code you will see that DJM34 made 2 kernals. One for compute 5.0 devices and one for compute 3.5 and 5.2. I have modded both of them and gained around 7% (reduced the codesize and some unroll tweaks)

[pokeytex]

Does anyone have a whirlpoolx working config without crashing?  I am using 1.5.55 with (9) 750ti's, (3) 970's, and (1) 960.  I am having a hard time getting the miner to run without driver crashes.  Quark runs like a champ.

Thanks - pokeytex

[Schleicher]

Does anyone have a whirlpoolx working config without crashing?  I am using 1.5.55 with (9) 750ti's, (3) 970's, and (1) 960.  I am having a hard time getting the miner to run without driver crashes.  Quark runs like a champ.

Seem to work here (under Windows), but then I'm only using one card, not 13.

[hashbrown9000]

does anyone else have problems in a multi-gpu rig with gpu 0 consistently crashing when mining neoscrypt algo?  it's only gpu 0, the rest are fine and hash away reliably.

[pokeytex]

Does anyone have a whirlpoolx working config without crashing?  I am using 1.5.55 with (9) 750ti's, (3) 970's, and (1) 960.  I am having a hard time getting the miner to run without driver crashes.  Quark runs like a champ.

Seem to work here (under Windows), but then I'm only using one card, not 13.

What is your config please?  I would like to check it against mine:

ccminer -a whirlpoolx -o stratum+tcp://vnl.suprnova.cc:1111 -u xxxxx.xxx -p x

[joblo]

does anyone else have problems in a multi-gpu rig with gpu 0 consistently crashing when mining neoscrypt algo?  it's only gpu 0, the rest are fine and hash away reliably.

I don't think I've seen a single GPU crash, usually it's the driver or the miner.
Try swapping GPU0 with another to see if the same card crashes in it's new slot.
Also see if the card will mine at a lower intensity.

[pokeytex]

Yeah - just confirmed on my three rigs I cannot run Whirlpoolx for some reason.  It starts to mine - even shows up on Suprnova and then the driver crashes.  Each rig - weird.  Any help or ideas?

thanks - pokeytex

edit: Am running Windows 8.1 pro on all machines - ?  maybe OS limitation?

edit2: Am compiling Trupvot's 1.5.3 version to try it out now.

[antonio8]

Yeah - just confirmed on my three rigs I cannot run Whirlpoolx for some reason.  It starts to mine - even shows up on Suprnova and then the driver crashes.  Each rig - weird.  Any help or ideas?

thanks - pokeytex

edit: Am running Windows 8.1 pro on all machines - ?  maybe OS limitation?

edit2: Am compiling Trupvot's 1.5.3 version to try it out now.

I have a mixed rig also and on some algos I have to put the same cards on it's own bat. Try running them that way and see what it does.

EDIT: This is a another option but PITA. Run one card at a time and see if it crashes. I just went through some bad risers causing crashes.

[pokeytex]

Yeah - just confirmed on my three rigs I cannot run Whirlpoolx for some reason.  It starts to mine - even shows up on Suprnova and then the driver crashes.  Each rig - weird.  Any help or ideas?

thanks - pokeytex

edit: Am running Windows 8.1 pro on all machines - ?  maybe OS limitation?

edit2: Am compiling Trupvot's 1.5.3 version to try it out now.

I have a mixed rig also and on some algos I have to put the same cards on it's own bat. Try running them that way and see what it does.

EDIT: This is a another option but PITA. Run one card at a time and see if it crashes. I just went through some bad risers causing crashes.

Hrmm that would make sense to me however (2) of the rigs are only 750ti's.  Regarding the risers wouldn't the other algos crash if the risers were bad?

[antonio8]

Yeah - just confirmed on my three rigs I cannot run Whirlpoolx for some reason.  It starts to mine - even shows up on Suprnova and then the driver crashes.  Each rig - weird.  Any help or ideas?

thanks - pokeytex

edit: Am running Windows 8.1 pro on all machines - ?  maybe OS limitation?

edit2: Am compiling Trupvot's 1.5.3 version to try it out now.

I have a mixed rig also and on some algos I have to put the same cards on it's own bat. Try running them that way and see what it does.

EDIT: This is a another option but PITA. Run one card at a time and see if it crashes. I just went through some bad risers causing crashes.

Hrmm that would make sense to me however (2) of the rigs are only 750ti's.  Regarding the risers wouldn't the other algos crash if the risers were bad?

The miner kept crashing so I put each card on it's own bat and the same card kept crashing. I kept switching cards to make sure the card was good and every card I put on the riser crashed. I had ordered some (even some new ones was bad) but now I have just about everything back to normal.

So try and run each card on it's own bat and see if the same one keeps crashing.

Easiest way I found was individual bats.

[pokeytex]

Yeah - just confirmed on my three rigs I cannot run Whirlpoolx for some reason.  It starts to mine - even shows up on Suprnova and then the driver crashes.  Each rig - weird.  Any help or ideas?

thanks - pokeytex

edit: Am running Windows 8.1 pro on all machines - ?  maybe OS limitation?

edit2: Am compiling Trupvot's 1.5.3 version to try it out now.

I have a mixed rig also and on some algos I have to put the same cards on it's own bat. Try running them that way and see what it does.

EDIT: This is a another option but PITA. Run one card at a time and see if it crashes. I just went through some bad risers causing crashes.

Hrmm that would make sense to me however (2) of the rigs are only 750ti's.  Regarding the risers wouldn't the other algos crash if the risers were bad?

The miner kept crashing so I put each card on it's own bat and the same card kept crashing. I kept switching cards to make sure the card was good and every card I put on the riser crashed. I had ordered some (even some new ones was bad) but now I have just about everything back to normal.

So try and run each card on it's own bat and see if the same one keeps crashing.

Easiest way I found was individual bats.

Ok will try that now - what os are you/were you running?