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

zTheWolfz

full member

Activity: 231

Merit: 150

Quote from: djm34 on September 22, 2015, 11:57:18 AM

Quote from: t-nelson on September 22, 2015, 11:34:01 AM

Quote from: sp_ on September 22, 2015, 04:21:39 AM

Quote from: t-nelson on September 21, 2015, 05:15:39 PM

Quote from: scryptr on September 21, 2015, 05:09:46 PM

Quote from: t-nelson on September 21, 2015, 04:54:06 PM

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.

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: t-nelson on September 22, 2015, 11:34:01 AM

Quote from: sp_ on September 22, 2015, 04:21:39 AM

Quote from: t-nelson on September 21, 2015, 05:15:39 PM

Quote from: scryptr on September 21, 2015, 05:09:46 PM

Quote from: t-nelson on September 21, 2015, 04:54:06 PM

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

t-nelson

member

Activity: 70

Merit: 10

Quote from: sp_ on September 22, 2015, 04:21:39 AM

Quote from: t-nelson on September 21, 2015, 05:15:39 PM

Quote from: scryptr on September 21, 2015, 05:09:46 PM

Quote from: t-nelson on September 21, 2015, 04:54:06 PM

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.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: qqqq on September 22, 2015, 11:04:32 AM

Quote from: scryptr on September 22, 2015, 11:00:06 AM

Quote from: serg_25 on September 22, 2015, 05:44:59 AM

Quote

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

qqqq

legendary

Activity: 1596

Merit: 1011

Quote from: scryptr on September 22, 2015, 11:00:06 AM

Quote from: serg_25 on September 22, 2015, 05:44:59 AM

Quote

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

legendary

Activity: 1797

Merit: 1028

Quote from: serg_25 on September 22, 2015, 05:44:59 AM

Quote

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

chrysophylax

legendary

Activity: 2940

Merit: 1091

--- ChainWorks Industries ---

Quote from: pallas on September 22, 2015, 07:10:27 AM

Quote from: chrysophylax on September 22, 2015, 06:58:55 AM

Quote from: sp_ on September 22, 2015, 06:54:10 AM

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

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: chrysophylax on September 22, 2015, 06:58:55 AM

Quote from: sp_ on September 22, 2015, 06:54:10 AM

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

legendary

Activity: 2940

Merit: 1091

--- ChainWorks Industries ---

Quote from: sp_ on September 22, 2015, 06:54:10 AM

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

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

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

chrysophylax

legendary

Activity: 2940

Merit: 1091

--- ChainWorks Industries ---

Quote from: pallas on September 22, 2015, 05:54:21 AM

Quote from: chrysophylax on September 22, 2015, 05:37:27 AM

Quote from: pallas on September 22, 2015, 05:35:18 AM

Quote from: tbearhere on September 22, 2015, 05:32:05 AM

Does C work on the 750ti. I can't get it to work. thx

It's a very simple call, similar to what it does for fan speed which works, so I don't think there is a fix for it in ccminer code.
If it never works on 750, I or Sp may add a check to show it only if compute >= 5.2
Anyone with 750 and working clock logging?

sorry - just popped in ...

clock logging? ...

i can compile the latest and test - if you let me know what im looking for ...

tanx ...

#crysx

the gpu hashrate line has been enhanced with current clocks reading (along with already available fan speed and temperature).
you must have nvml working, of course.
if you are on linux and nvml isn't enabled, try compiling with "--with-nvml"

i see this happening on most of the machines in thefarm - but two machines are showing zero ... even though the temperature IS showing ...

all the rest of the systems are showing their respective clock rates ... this is VERY kool ...

stumped as to why the two that are not showing it ... maybe they are the teh 'other' 750ti oc - and not the lp cards ...

ill post back in a few minutes ...

btw - all of the compiles are done with the same os ( f20x64 ) and c6.5 ... all with nvml ...

edit - nup ... i dont know what is happening with those two systems ... they are gigabyte 750ti oc lp - compiled with nvml active ...

nothing wrong with the others - all showing the clock and fan rates ...

#crysx

tbearhere

legendary

Activity: 3164

Merit: 1003

Quote from: pallas on September 22, 2015, 05:35:18 AM

Quote from: tbearhere on September 22, 2015, 05:32:05 AM

Does C work on the 750ti. I can't get it to work. thx

It's a very simple call, similar to what it does for fan speed which works, so I don't think there is a fix for it in ccminer code.
If it never works on 750, I or Sp may add a check to show it only if compute >= 5.2
Anyone with 750 and working clock logging?

Thx pallas.

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: chrysophylax on September 22, 2015, 05:37:27 AM

Quote from: pallas on September 22, 2015, 05:35:18 AM

Quote from: tbearhere on September 22, 2015, 05:32:05 AM

Does C work on the 750ti. I can't get it to work. thx

It's a very simple call, similar to what it does for fan speed which works, so I don't think there is a fix for it in ccminer code.
If it never works on 750, I or Sp may add a check to show it only if compute >= 5.2
Anyone with 750 and working clock logging?

sorry - just popped in ...

clock logging? ...

i can compile the latest and test - if you let me know what im looking for ...

tanx ...

#crysx

the gpu hashrate line has been enhanced with current clocks reading (along with already available fan speed and temperature).
you must have nvml working, of course.
if you are on linux and nvml isn't enabled, try compiling with "--with-nvml"

serg_25

newbie

Activity: 51

Merit: 0

Quote

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?

chrysophylax

legendary

Activity: 2940

Merit: 1091

--- ChainWorks Industries ---

Quote from: pallas on September 22, 2015, 05:35:18 AM

Quote from: tbearhere on September 22, 2015, 05:32:05 AM

Does C work on the 750ti. I can't get it to work. thx

It's a very simple call, similar to what it does for fan speed which works, so I don't think there is a fix for it in ccminer code.
If it never works on 750, I or Sp may add a check to show it only if compute >= 5.2
Anyone with 750 and working clock logging?

sorry - just popped in ...

clock logging? ...

i can compile the latest and test - if you let me know what im looking for ...

tanx ...

#crysx

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: tbearhere on September 22, 2015, 05:32:05 AM

Does C work on the 750ti. I can't get it to work. thx

It's a very simple call, similar to what it does for fan speed which works, so I don't think there is a fix for it in ccminer code.
If it never works on 750, I or Sp may add a check to show it only if compute >= 5.2
Anyone with 750 and working clock logging?

tbearhere

legendary

Activity: 3164

Merit: 1003

Does C work on the 750ti. I can't get it to work. thx

qqqq

legendary

Activity: 1596

Merit: 1011

Quote from: sp_ on September 22, 2015, 05:12:29 AM

R61 should work for lyra2v2

Can't check this cause too much time for block needed. Can't waste 1 day.

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

R61 should work for lyra2v2

qqqq

legendary

Activity: 1596

Merit: 1011

Quote from: sp_ on September 22, 2015, 04:39:56 AM

Quote from: zTheWolfz on September 22, 2015, 04:30:05 AM

Quote from: sp_ on September 22, 2015, 04:21:39 AM

Quote from: t-nelson on September 21, 2015, 05:15:39 PM

Quote from: scryptr on September 21, 2015, 05:09:46 PM

Quote from: t-nelson on September 21, 2015, 04:54:06 PM

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..

last version I am able to get to solo mine is r56. here is the error code I get with every version after release 56.

Code:

[2015-09-22 04:27:13] JSON inval data
[2015-09-22 04:27:13] json_rpc_call failed, retry after 30 seconds

Solomining was fixed in R61 and was broken again in R62

http://cryptomining-blog.com/5477-updated-windows-binary-of-the-ccminer-1-5-61-git-fork-by-sp-for-maxwell/

Just tried ver 61 for SRC (quark) and got crash with

Code:

JSON-RPC call failed: invalid parameter submit_upstream_work json_rpc_call failed

testing ver56 right now...

same error and crash (quark algo).

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