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

Quote from: pallas on July 14, 2015, 03:22:05 PM

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Set -i 17.5

Thanks but same validation error.
Besides, the segfault is on all algos.

what os and drivers?

Ubuntu 15.04 with distribution cuda toolkit (6.5 and compute 5.0)

hi pallas ...

this may help with all future cards ...

https://developer.nvidia.com/cuda-gpus/ ...

#crysx

hashbrown9000

sr. member

Activity: 427

Merit: 250

@sp_ , what is the default intensity for neoscrypt algo on a 750ti? do you have any optimal settings? one of my cards crashed @ +80 MHz GPU clock

joblo

legendary

Activity: 1470

Merit: 1114

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Set -i 17.5

Thanks but same validation error.
Besides, the segfault is on all algos.

Ubuntu 15.04 with distribution cuda toolkit (6.5 and compute 5.0)

Lyra2 works on a 970 for me (compiled for 5.2). Segfaults on ^C still occur but don't appear to have any
residual effect.

I've noticed the default intensity is too high for some cards/algos. Ive also noticed some odd behaviour
with intensity. Quark would initially run with -i 23.5. The next time i started it it failed at -i 23.5 but
ran at 23. Then 23 failed and I lowered it to 22.5. 970 + 780ti.

Slava_K

hero member

Activity: 677

Merit: 500

Quote from: pallas on July 14, 2015, 03:22:05 PM

Quote from: Slava_K on July 14, 2015, 03:15:56 PM

Quote from: Slava_K on July 14, 2015, 03:15:56 PM

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Set -i 17.5

Thanks but same validation error.
Besides, the segfault is on all algos.

what os and drivers?

Ubuntu 15.04 with distribution cuda toolkit (6.5 and compute 5.0)

Nv have a patch for 6.5 for 5.2 - gtx970 is 5.2 card (may be problem is here)

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Set -i 17.5

Thanks but same validation error.
Besides, the segfault is on all algos.

what os and drivers?

Ubuntu 15.04 with distribution cuda toolkit (6.5 and compute 5.0)

Slava_K

hero member

Activity: 677

Merit: 500

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Set -i 17.5

Thanks but same validation error.
Besides, the segfault is on all algos.

what os and drivers?

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Set -i 17.5

Thanks but same validation error.
Besides, the segfault is on all algos.

Slava_K

hero member

Activity: 677

Merit: 500

Quote from: sp_ on July 14, 2015, 01:37:19 PM

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Set -i 17.5

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

-Quark +200khash on the gtx 970 +300khash on the gtx 980
-Lyra2 fixed on the gtx960
-Fixed bufferoverflow(stack) in neoscrypt
-Can be compiled with cuda 7.5 but cuda 6.5 is still the fastest.

1.5.55(sp-MOD) is available here: (14-07-2015)

https://github.com/sp-hash/ccminer/releases/tag/1.5.55

The sourcecode is available here:

https://github.com/sp-hash/ccminer

Thanks! It is indeed faster on 970, but lyra doesn't work, it doesn't validate on CPU. It also segfaults at times when exiting. Both problems where present on the previous version as well.
Need some debug info?

Slava_K

hero member

Activity: 677

Merit: 500

Quote from: sp_ on July 14, 2015, 01:37:19 PM

-Quark +200khash on the gtx 970 +300khash on the gtx 980
-Lyra2 fixed on the gtx960
-Fixed bufferoverflow(stack) in neoscrypt
-Can be compiled with cuda 7.5 but cuda 6.5 is still the fastest.

1.5.55(sp-MOD) is available here: (14-07-2015)

https://github.com/sp-hash/ccminer/releases/tag/1.5.55

The sourcecode is available here:

https://github.com/sp-hash/ccminer

Can`t compile last commit - errores after this line in cuda_noescrypt.cu // neoscrypt_gpu_hash_orig << > >(threads, startNounce, d_NNonce[thr_id]); (expectet an expression)
PS. Problem is solved. My PSU is not enough for 2x980 and 960 + 100% load for CPU... :,(

johnambush

full member

Activity: 228

Merit: 100

Quote from: djm34 on July 14, 2015, 06:38:20 AM

Quote from: sp_ on July 14, 2015, 02:10:08 AM

Quote from: johnambush on July 13, 2015, 12:54:29 PM

Quote from: joblo on July 14, 2015, 06:21:38 AM

If you have flooded the pool with rejected shares the pool might ban your ip adress. Change the ip

It may be the reason. I forgot about that. I can't do it right now but I will report you if it was or not soon as I check it. Thank you. Two heads are often smarter than one

EDIT: But I also tried to mine on Suprnova (for the first time with neoscrypt) and had same result. I doubt it banned my ip Undecided

Look's like neoscrypt is broken in release 54.
I suspect there are some errors in the vector implementation done in the lyra2re rewrite since they share some code.

if there are errors they are not from me... Grin

(and the current public version of neoscrypt use different verctor types...)

Obviously my ip was banned. I relocated miner to another router and it established connection with pool immediately. But reason for ban ip may be flooding pool with bad shares due to broken neoscrypt. Works fine now

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

-Quark +200khash on the gtx 970 +300khash on the gtx 980
-Lyra2 fixed on the gtx960
-Fixed bufferoverflow(stack) in neoscrypt
-Can be compiled with cuda 7.5 but cuda 6.5 is still the fastest.

1.5.55(sp-MOD) is available here: (14-07-2015)

https://github.com/sp-hash/ccminer/releases/tag/1.5.55

The sourcecode is available here:

https://github.com/sp-hash/ccminer

rednoW

legendary

Activity: 1510

Merit: 1003

Neoscrypt works well for me in release 54.

Yes, git compiled from this commit https://github.com/sp-hash/ccminer/commit/4958b610a77e5a54d5c9cf1e2d18ca0b48513b9c neoscrypt works just fine at nicehash and hamsterpool

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: sp_ on July 14, 2015, 02:10:08 AM

Quote from: johnambush on July 13, 2015, 12:54:29 PM

Quote from: sp_ on July 14, 2015, 02:10:08 AM

If you have flooded the pool with rejected shares the pool might ban your ip adress. Change the ip

It may be the reason. I forgot about that. I can't do it right now but I will report you if it was or not soon as I check it. Thank you. Two heads are often smarter than one

EDIT: But I also tried to mine on Suprnova (for the first time with neoscrypt) and had same result. I doubt it banned my ip Undecided

Look's like neoscrypt is broken in release 54.
I suspect there are some errors in the vector implementation done in the lyra2re rewrite since they share some code.

if there are errors they are not from me... Grin

(and the current public version of neoscrypt use different verctor types...)

joblo

legendary

Activity: 1470

Merit: 1114

Look's like neoscrypt is broken in release 54.
I suspect there are some errors in the vector implementation done in the lyra2re rewrite since they share some code.

Neoscrypt works well for me in release 54.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: johnambush on July 13, 2015, 12:54:29 PM

Quote from: johnambush on July 13, 2015, 12:54:29 PM

If you have flooded the pool with rejected shares the pool might ban your ip adress. Change the ip

It may be the reason. I forgot about that. I can't do it right now but I will report you if it was or not soon as I check it. Thank you. Two heads are often smarter than one

EDIT: But I also tried to mine on Suprnova (for the first time with neoscrypt) and had same result. I doubt it banned my ip Undecided

Look's like neoscrypt is broken in release 54.
I suspect there are some errors in the vector implementation done in the lyra2re rewrite since they share some code.

joblo

legendary

Activity: 1470

Merit: 1114

If you have flooded the pool with rejected shares the pool might ban your ip adress. Change the ip

It may be the reason. I forgot about that. I can't do it right now but I will report you if it was or not soon as I check it. Thank you. Two heads are often smarter than one

EDIT: But I also tried to mine on Suprnova (for the first time with neoscrypt) and had same result. I doubt it banned my ip Undecided

You haven't mentioned what versions you are using but I suggest you stick with the one that used to
work and troubleshoot from there. Make sure you are in fact using the intended version. If it used to
work but now doesn't the problem is not with the miner. More detail about the failure would also be useful.

I have a Windows machine that I need to reboot once in a while because it fails to connect to westhash
quark (retry loop). That's the only affected pool/algo. After the reboot everything is ok again. Updating
drivers hasn't solved it. There is something peculiar about Nice/Westhash as it always fails to connect
on the first attempt. ffpool doesn't have this problem and neither did yaamp. I'm using 1.5.52.

I need to come up with a new compile strategy because VS Community (the free one, not the trial)
refuses to start after 30 days. Then I can instrument ccminer to focus in on the connection failure.

johnambush

full member

Activity: 228

Merit: 100