CCminer(SP-MOD) Modded GPU kernels.

[chrysophylax]

Maybe your drivera are too old? Bugs have been fixed by NVIDIA in the latest versions.

they are all the same sp ...

all these installed have exactly the same installation procedures and apps ...

same os - same cuda - same components ... the only thing different between thses ystems are the motherboards and cpu ( i think ) ...

the installation of both these mchines ar exactly the same as well ...

this is the main reason i want to finish the hardware 'upgrade' of the systems - so that they are EXACTLY the same hardware also ...

ill be doing fresh installs on ALL the machines when the frames are finished ...

its quite baffling ... but they process the same though - so its all good on a hashing level ...

#crysx

[pallas]

Maybe your drivera are too old? Bugs have been fixed by NVIDIA in the latest versions.

they are all the same sp ...

all these installed have exactly the same installation procedures and apps ...

same os - same cuda - same components ... the only thing different between thses ystems are the motherboards and cpu ( i think ) ...

the installation of both these mchines ar exactly the same as well ...

this is the main reason i want to finish the hardware 'upgrade' of the systems - so that they are EXACTLY the same hardware also ...

ill be doing fresh installs on ALL the machines when the frames are finished ...

its quite baffling ... but they process the same though - so its all good on a hashing level ...

#crysx

maybe different gpu firmware or firmware version.

[chrysophylax]

Maybe your drivera are too old? Bugs have been fixed by NVIDIA in the latest versions.

they are all the same sp ...

all these installed have exactly the same installation procedures and apps ...

same os - same cuda - same components ... the only thing different between thses ystems are the motherboards and cpu ( i think ) ...

the installation of both these mchines ar exactly the same as well ...

this is the main reason i want to finish the hardware 'upgrade' of the systems - so that they are EXACTLY the same hardware also ...

ill be doing fresh installs on ALL the machines when the frames are finished ...

its quite baffling ... but they process the same though - so its all good on a hashing level ...

#crysx

maybe different gpu firmware or firmware version.

thats whta i thought - but i cant check it right now ...

these cards were all bought together from the same sales batch ... but that does not necessarily mean they were from the same manufacturing batch ...

that maybe a possibility - but one i cannot confirm until i come back in two days ...

all the others done have this issue - just these two machines ...

i have a great deal to do this week - so i cant even look into it ...

maybe will see what happens with the next revision of ccminer-spmod ... if it does the same thing with the same two machines - then its got to be with the machines themselves ...

ill bid you all goodnight - and will be back day after tomorrow ...

awesome work guys ...

#crysx

[scryptr]

My 6x 750ti rig is now solo-mining across my LAN to my Win 7 x64 work computer.

According to the CoinWarz calculator, My 36Mh/s VTC rig should find a block every 0.72 days at the current difficulty (~520)

Hi scryptr, if i missed something, your card in lyra2v2 can do 36/6=6mh\s each?   EVGA FTW cards?

MATH ERROR--

Sorry, I usually run Quark.  My 750ti cards get 4.5Mh/s each, my 960 gets 6Mh/s.  Total in 33-35Mh/s for both the rig and the 960.       --scryptr

[qqqq]

My 6x 750ti rig is now solo-mining across my LAN to my Win 7 x64 work computer.

According to the CoinWarz calculator, My 36Mh/s VTC rig should find a block every 0.72 days at the current difficulty (~520)

Hi scryptr, if i missed something, your card in lyra2v2 can do 36/6=6mh\s each?   EVGA FTW cards?

MATH ERROR--

Sorry, I usually run Quark.  My 750ti cards get 4.5Mh/s each, my 960 gets 6Mh/s.  Total in 33-35Mh/s for both the rig and the 960.       --scryptr

Do you know which release hasn't solo bug for the quark algo ?

[scryptr]

My 6x 750ti rig is now solo-mining across my LAN to my Win 7 x64 work computer.

According to the CoinWarz calculator, My 36Mh/s VTC rig should find a block every 0.72 days at the current difficulty (~520)

Hi scryptr, if i missed something, your card in lyra2v2 can do 36/6=6mh\s each?   EVGA FTW cards?

MATH ERROR--

Sorry, I usually run Quark.  My 750ti cards get 4.5Mh/s each, my 960 gets 6Mh/s.  Total in 33-35Mh/s for both the rig and the 960.       --scryptr

Do you know which release hasn't solo bug for the quark algo ?

SOLO-MINE ATTEMPTS--

I have succesfully solo-mined Ether Coin (ETH), and sucessfully set-up for solo-mining VertCoin (VTC).  VTC did not work because of the bug.  I haven't tried to setup Quark for solo-miniing any coin.  I have not been able to set up Feathercoin for solomining, the wallet communication does not work.  I get only errors on launch.
 
I don't know which version of CCminer will solo-mine Quark.       --scryptr

[t-nelson]

Nothing fixed, just extra logging added.  Linux bin is built on Ubuntu 14.04 x86_64 against CUDA 6.5.
https://github.com/t-nelson/ccminer/releases/tag/untagged-9e8e19fde7b511b5a726

ERROR LOGGING--
How to write the error log file?  Please give an example command flag string, short and long form.  I use a *.conf file (long form) in Windows, and flags in Linux.  Thank you!
--scryptr

I just forced the "dump protocol" command line flag and added another log line.  It will just be on the console with the regular output.  Go ahead and pass -D though.  Can't have too much logging in these cases.

Solo mining is working in release 61, so something must have happened. Check the checkin logs..

It may be the case that it WAS working, but the fact remains that there is no hard repro case and that "fixes" since then only seem to cover up the issue on occasion.  I don't waste time covering up issues.  I learn about them, understand them and fix them for real.  There is brittle code somewhere and it needs hardening.

Besides, most commit messages read more like a marketing/PR campaign than describing the change.  The tree is so volatile with guess and check commit/reverts for "performance enhancements" that the history is more of a labyrinth than the story it ought to be.

[djm34]

Nothing fixed, just extra logging added.  Linux bin is built on Ubuntu 14.04 x86_64 against CUDA 6.5.
https://github.com/t-nelson/ccminer/releases/tag/untagged-9e8e19fde7b511b5a726

ERROR LOGGING--
How to write the error log file?  Please give an example command flag string, short and long form.  I use a *.conf file (long form) in Windows, and flags in Linux.  Thank you!
--scryptr

I just forced the "dump protocol" command line flag and added another log line.  It will just be on the console with the regular output.  Go ahead and pass -D though.  Can't have too much logging in these cases.

Solo mining is working in release 61, so something must have happened. Check the checkin logs..

It may be the case that it WAS working, but the fact remains that there is no hard repro case and that "fixes" since then only seem to cover up the issue on occasion.  I don't waste time covering up issues.  I learn about them, understand them and fix them for real.  There is brittle code somewhere and it needs hardening.

Besides, most commit messages read more like a marketing/PR campaign than describing the change.  The tree is so volatile with guess and check commit/reverts for "performance enhancements" that the history is more of a labyrinth than the story it ought to be.

sshhh 

[zTheWolfz]

Nothing fixed, just extra logging added.  Linux bin is built on Ubuntu 14.04 x86_64 against CUDA 6.5.
https://github.com/t-nelson/ccminer/releases/tag/untagged-9e8e19fde7b511b5a726

ERROR LOGGING--
How to write the error log file?  Please give an example command flag string, short and long form.  I use a *.conf file (long form) in Windows, and flags in Linux.  Thank you!
--scryptr

I just forced the "dump protocol" command line flag and added another log line.  It will just be on the console with the regular output.  Go ahead and pass -D though.  Can't have too much logging in these cases.

Solo mining is working in release 61, so something must have happened. Check the checkin logs..

It may be the case that it WAS working, but the fact remains that there is no hard repro case and that "fixes" since then only seem to cover up the issue on occasion.  I don't waste time covering up issues.  I learn about them, understand them and fix them for real.  There is brittle code somewhere and it needs hardening.

Besides, most commit messages read more like a marketing/PR campaign than describing the change.  The tree is so volatile with guess and check commit/reverts for "performance enhancements" that the history is more of a labyrinth than the story it ought to be.

sshhh  

Let me rephrase my comment "Neoscrypt has not solo mined" from r57 forward for me.
r56 and below work.

[t-nelson]

Nothing fixed, just extra logging added.  Linux bin is built on Ubuntu 14.04 x86_64 against CUDA 6.5.
https://github.com/t-nelson/ccminer/releases/tag/untagged-9e8e19fde7b511b5a726

ERROR LOGGING--
How to write the error log file?  Please give an example command flag string, short and long form.  I use a *.conf file (long form) in Windows, and flags in Linux.  Thank you!
--scryptr

I just forced the "dump protocol" command line flag and added another log line.  It will just be on the console with the regular output.  Go ahead and pass -D though.  Can't have too much logging in these cases.

Solo mining is working in release 61, so something must have happened. Check the checkin logs..

It may be the case that it WAS working, but the fact remains that there is no hard repro case and that "fixes" since then only seem to cover up the issue on occasion.  I don't waste time covering up issues.  I learn about them, understand them and fix them for real.  There is brittle code somewhere and it needs hardening.

Besides, most commit messages read more like a marketing/PR campaign than describing the change.  The tree is so volatile with guess and check commit/reverts for "performance enhancements" that the history is more of a labyrinth than the story it ought to be.

sshhh  

Let me rephrase my comment "Neoscrypt has not solo mined" from r57 forward for me.
r56 and below work.

I'm dubious of the hash algo having anything to do with the solo mining issue.  I want to see the protocol communications as are enabled with the bins I posted in https://bitcointalk.org/index.php?topic=826901.msg12486340#msg12486340

[djm34]

Nothing fixed, just extra logging added.  Linux bin is built on Ubuntu 14.04 x86_64 against CUDA 6.5.
https://github.com/t-nelson/ccminer/releases/tag/untagged-9e8e19fde7b511b5a726

ERROR LOGGING--
How to write the error log file?  Please give an example command flag string, short and long form.  I use a *.conf file (long form) in Windows, and flags in Linux.  Thank you!
--scryptr

I just forced the "dump protocol" command line flag and added another log line.  It will just be on the console with the regular output.  Go ahead and pass -D though.  Can't have too much logging in these cases.

Solo mining is working in release 61, so something must have happened. Check the checkin logs..

It may be the case that it WAS working, but the fact remains that there is no hard repro case and that "fixes" since then only seem to cover up the issue on occasion.  I don't waste time covering up issues.  I learn about them, understand them and fix them for real.  There is brittle code somewhere and it needs hardening.

Besides, most commit messages read more like a marketing/PR campaign than describing the change.  The tree is so volatile with guess and check commit/reverts for "performance enhancements" that the history is more of a labyrinth than the story it ought to be.

sshhh 

Let me rephrase my comment "Neoscrypt has not solo mined" from r57 forward for me.
r56 and below work.

well... use my release, it has always worked... (must admit however that solo gets block accepted however several are also rejected, which is probably an issue min target... )

[hashbrown9000]

@sp_ my entire farm is 750ti cards.

i haven't ever tried solomining a quark algo coin. only VTC on lyra2re which didn't work. had to use djm's miner for soloing.  then the diff on VTC rose, and i'm back to quark

[t-nelson]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

[scryptr]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  If each different algo uses a separate communication protocol, this may not be true.  FeatherCoin (FTC) won't generate hash, I cannot get CCminer to communicate with the wallet at all.      --scryptr

[AliMan]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

-Whirlcoin
-Quark
-Nist5
-keccak
-luffa
-pentablake

[djm34]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

-Whirlcoin
-Quark
-Nist5
-keccak
-luffa
-pentablake

so what's left ?  

to be honest I am not sure there is much to mine with wirlcoin,nist5,keccak,pentablake (and probably luffa) even less in solo

[djm34]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  

please precise ccminer from sp... my releases have no problem, tpruvot releases neither... so please don't generalize to every ccminer release.
That's in part why I am rather unhappy about the situation. myself and other have busted our asses on ccminer while the most publicised version which mostly uses the code we developed gets broken on a daily basis, feature gets removed, not even possible to run in debug mod without recompiling etc...).

no offence sp, it is time you get your shit together and stop releasing 4 untested releases a day...

[scryptr]

Does anyone have a list of coins where soloing is known to be broken?  Maybe one with low diff?

SecureCoin (SRC) was suggested.  It is a Quark coin. Another miner posted that it has the same error message on finding a block (crashing) as VertCoin (VTC).  CCminer will generate Quark hash with SRC; SRC has very rapid blocks at low difficulty.

Currently, I do not think solo-mining will work with any algo using CCminer.  

please precise ccminer from sp... my releases have no problem, tpruvot releases neither... so please don't generalize to every ccminer release.
That's in part why I am rather unhappy about the situation. myself and other have busted our asses on ccminer while the most publicised version which mostly uses the code we developed gets broken on a daily basis, feature gets removed, not even possible to run in debug mod without recompiling etc...).

no offence sp, it is time you get your shit together and stop releasing 4 untested releases a day...

PRECISE--

OK, you have a point, DJ.  I was posting in sp_'s thread, however.  I DO try to be clear about OS, version, hash rates, clock rates, spelling and punctuation, etc.  I've groaned about the bleeding edge speed before, myself, but sp_ has brought my 750ti cards from 5.5+ Mh/s to 6.1Mh/s mining Quark within the last 20 releases.

Maybe a few releases should focus on code clean-up and standardization rather than speed.  Future improvements would then be on a stronger base.       --scryptr

[sp_]

djm34, why do you care about the broken solomining? Release 68 is more stable than ever, and everybody is using my mod because it is the fastest opensource in the world. Optimizing for the Maxwell is not straight forward because there are so many different cards with different properties. There are different operating systems with different adressmodes and drivers. But my modded kernals are the fastest on all the cards and operating systems.

The solomining bug can be fixed. T Nelson is looking at it. If you think solomining is important for you should donate some mBTC to him to motivate.


Some time ago when quark was paying 0.7BTC/GHASH:

[impulse2000]

Fired my poor gtx750 1gb again, 1500/1600 = 6300kh/s (release 68, quark)

GTX750TI-OC-2GD5 - 7250kh/s - Clocks +180Mhz/+180Mhz (release 68, quark)

Pretty good, but how much is the consumption? Hash/watt

The 1gb 750 has a TDP of just 35W in the bios.
And on standard clocks it uses around 40Watts to produce 5 MHASH of quark. (125KHASH per watt).
A 970 gigabyte windforce gaming will do around 17MHASH in 180 watts. (94.444444444444KHASH per watt)


So the junior card is 32% bether is hash/watt, but you need alot more cards/motherboards/ram/cpu's/psu's So I guess none of you are mining with the gtx 750 ?

I dont know. This my home comp, not rig. Son watches YouTube + ccminer with -i 16-17. If not -i 22.9.
Q8300 / P5K-SE-EPU / 2GB / Win7x86 / GTX750Ti-2GB