Sigh.. He should stop building binaries 2 days before my releases...
Will double check / delay the release a bit more... On which card ?
I added sm 2.1 support only a few days ago : https://github.com/tpruvot/ccminer/commits/windows/x11/cuda_x11_simd512_sm2.cuh
Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 153. (Read 500193 times)
hey epsylon3 your latest git code performs bad with cuda 2.1 qubit's speed is down too much penta too.
Is that a joke ? Qubit was not working before on 2.1
no in this git http://cryptomining-blog.com/6172-updated-ccminer-1-7-dev-fork-by-tpruvot-from-git-for-windows/ qubit works good
in this git http://cryptomining-blog.com/6205-updated-ccminer-1-7-dev-fork-by-tpruvot-from-git-for-windows-2/ qubit works bad,
hey epsylon3 your latest git code performs bad with cuda 2.1 qubit's speed is down too much penta too.
Is that a joke ? Qubit was not working before on 2.1
hey epsylon3 your latest git code performs bad with cuda 2.1 qubit's speed is down too much penta too.
this really is great work epsylon3 ...
a rotational pool switch has been missing from ccminer for a LONG time ...
tanx ...
#crysx
a rotational pool switch has been missing from ccminer for a LONG time ...
tanx ...
#crysx
max-time doesn't exist... i wanted something explicit about duration (its also used in benchmark to do short tests)
all max- flags are related to conditional mining (wait), time-limit is more... terminate
all max- flags are related to conditional mining (wait), time-limit is more... terminate
time-limit != max-time ?
this sample show 2 of them, the max-xxxx and the time limit, there is also the failover (pool down)
I will maybe add some more explicit flags for that, like "pool-rotate-on-wait"
But these new features also make new problems to handle, like the intensity. I will maybe create a special config file for that (algo/card default throughput)
I will maybe add some more explicit flags for that, like "pool-rotate-on-wait"
But these new features also make new problems to handle, like the intensity. I will maybe create a special config file for that (algo/card default throughput)
Great work tpruvot! :-)
What events can trigger a pool/algo switch?
What events can trigger a pool/algo switch?
Else, i can confirm the GT720 DDR5 is SM 3.5
I'm about to release the 1.7, this capture show some of the new possible features :
Config used for this (full night) test
I'm about to release the 1.7, this capture show some of the new possible features :
Code:
[2015-11-03 10:46:44] GPU #0: MSI GTX 960, 1795.23 kH/s
[2015-11-03 10:46:56] GPU #0: MSI GTX 960, 1814.05 kH/s
[2015-11-03 10:46:56] Stratum difficulty set to 0.013
[2015-11-03 10:46:56] zr5 block 340182, diff 10.245
[2015-11-03 10:46:56] network diff too high, waiting...
[2015-11-03 10:46:56] Switch to stratum pool 1: Wood pool
[2015-11-03 10:46:56] Stratum difficulty set to 0.00390625
[2015-11-03 10:46:56] skein2 block 256693, diff 9.484
....
Config used for this (full night) test
Code:
{
"pools":[{
"name": "Ziftr pool",
"algo" : "zr5",
"url": "stratum+tcp://yiimp.ccminer.org:5533",
"user": "ZNMBZDU9tNqcqxGkpHP7Qcb8mbzTA4efA6",
"pass": "x",
"max-diff": 10.0,
"scantime": 20,
"disabled": false
},
{
"name": "Wood pool",
"algo" : "skein2",
"url": "stratum+tcp://wood.suprnova.cc:1158",
"user": "tpruvot.skein2",
"pass": "x",
"time-limit": 150,
"max-diff": 20.0,
"disabled": false
}],
"//algo" : "zr5",
"show-diff" : true,
"api-remote" : true,
"api-bind" : "0.0.0.0"
}
I've always gone with what was stated in the wiki. I'm pretty sure the same info is stated on the nVidia web site as well. I will gladly try compiling for 3.0 and see if it works. Probably not till tomorrow though. Will report back my results. thanks all for chipping in to help.
Z
Z
no, only a few 7xx cards are 3.5
the wiki seems to be wrong : https://en.wikipedia.org/wiki/CUDA#Supported_GPUs
edit: indeed there seems to be one : https://developer.nvidia.com/cuda-gpus but that look like an error to me, they say the GDDR3 is 2.1
the wiki seems to be wrong : https://en.wikipedia.org/wiki/CUDA#Supported_GPUs
edit: indeed there seems to be one : https://developer.nvidia.com/cuda-gpus but that look like an error to me, they say the GDDR3 is 2.1
after the Makefile.am edit, you need to do a proper build, the fastest way is to use ./build.sh
please give me the output of ccminer -n
GPU #0: SM 3.0 GeForce GT 640please give me the output of ccminer -n
The 640 GDDR5 is supposed to be 3.5, but apparently this one isn't. I presume you'll
try compiling for 3.0.
SM 3.0 is not SM 3.5 ! Are you sure about your compilation options there bud ?
And the algo ? Quark i guess... I will receive a sm3 device soon... Will try to fix it for the 1.7 release
after the Makefile.am edit, you need to do a proper build, the fastest way is to use ./build.sh
please give me the output of ccminer -n
GPU #0: SM 3.0 GeForce GT 640 please give me the output of ccminer -n
after the Makefile.am edit, you need to do a proper build, the fastest way is to use ./build.sh
please give me the output of ccminer -n
please give me the output of ccminer -n
Still no joy. 
The error you're seeing usualy means ccminer can't find a valid cuda GPU. This often occurs
if ccminer is not compiled for the proper compute version but can have other causes such as an
unconfigured card, a faulty card, etc. If the following doesn't work I'm stumped.
The 640 has a monitor attached or is otherwise configured?
It is listed in nvidia-settings?
It is in fact the GDDR5 variation? (GDDR3 is compute 2.1)
You have up to date drivers?
You have cuda 6.5 installed and are configured to use it?
You start with freshly unzipped source?
You edit Makefile.am to ensure code is generated for compute 3.5?
Compiler output confirms 3.5 code is generated?
Have you tried other algos?
Edit: another thought, did you disable the nouveau driver and are use nvidia's proprietary driver?
I dont see any reason... pentablake has nothing special and works on pools
Pentablake solomining seem to be broken in 1.7 beta
Jump to: