pallas
Legendary
 Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
 |
September 22, 2015, 10:54:21 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" |
|
|
|
|
|
|
|
|
Even in the event that an attacker gains more than 50% of the network's
computational power, only transactions sent by the attacker could be
reversed or double-spent. The network would not be destroyed.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
tbearhere
Legendary
Offline
Activity: 3136
Merit: 1003
|
|
September 22, 2015, 11:19:54 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.  |
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2814
Merit: 1091
--- ChainWorks Industries ---
|
|
September 22, 2015, 11:41:46 AM
Last edit: September 22, 2015, 11:53:18 AM by chrysophylax |
|
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 |
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2898
Merit: 1087
Team Black developer
|
|
September 22, 2015, 11:54:10 AM |
|
Maybe your drivera are too old? Bugs have been fixed by NVIDIA in the latest versions.
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2814
Merit: 1091
--- ChainWorks Industries ---
|
|
September 22, 2015, 11:58:55 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 |
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
September 22, 2015, 12:10:27 PM |
|
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
Offline
Activity: 2814
Merit: 1091
--- ChainWorks Industries ---
|
|
September 22, 2015, 12:17:17 PM |
|
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
Legendary
Offline
Activity: 1793
Merit: 1028
|
|
September 22, 2015, 04:00:06 PM |
|
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
Legendary
Offline
Activity: 1596
Merit: 1011
|
|
September 22, 2015, 04:04:32 PM |
|
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
Offline
Activity: 1793
Merit: 1028
|
|
September 22, 2015, 04:26:37 PM |
|
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
Member
Offline
Activity: 70
Merit: 10
|
|
September 22, 2015, 04:34:01 PM |
|
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. |
BTC: 1K4yxRwZB8DpFfCgeJnFinSqeU23dQFEMu
DASH: XcRSCstQpLn8rgEyS6yH4Kcma4PfcGSJxe
|
|
|
djm34
Legendary
Offline
Activity: 1400
Merit: 1050
|
|
September 22, 2015, 04:57:18 PM |
|
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  |
djm34 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
|
zTheWolfz
|
|
September 22, 2015, 05:31:26 PM |
|
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
Member
Offline
Activity: 70
Merit: 10
|
|
September 22, 2015, 05:51:51 PM |
|
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 |
BTC: 1K4yxRwZB8DpFfCgeJnFinSqeU23dQFEMu
DASH: XcRSCstQpLn8rgEyS6yH4Kcma4PfcGSJxe
|
|
|
djm34
Legendary
Offline
Activity: 1400
Merit: 1050
|
|
September 22, 2015, 06:02:58 PM |
|
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... ) |
djm34 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
|
hashbrown9000
|
|
September 22, 2015, 09:38:42 PM |
|
@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
|
Pinkcoin:
ETH:
VTC:
BTC:
|
|
|
t-nelson
Member
Offline
Activity: 70
Merit: 10
|
|
September 22, 2015, 10:14:29 PM |
|
Does anyone have a list of coins where soloing is known to be broken? Maybe one with low diff?  |
BTC: 1K4yxRwZB8DpFfCgeJnFinSqeU23dQFEMu
DASH: XcRSCstQpLn8rgEyS6yH4Kcma4PfcGSJxe
|
|
|
scryptr
Legendary
Offline
Activity: 1793
Merit: 1028
|
|
September 22, 2015, 10:21:12 PM
Last edit: September 22, 2015, 11:14:44 PM by 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
|
|
September 22, 2015, 11:28:14 PM |
|
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
Legendary
Offline
Activity: 1400
Merit: 1050
|
|
September 23, 2015, 12:06:27 AM |
|
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 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
|
