cbuchner1 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 16, 2013, 03:18:52 PM Last edit: July 16, 2013, 03:39:21 PM by cbuchner1 |
|
there have been some updates to the github repo today.
The only remaining problem I find with the current state of the github repo is that the 64 bit compilation on 64bit Linux machines does not appear to produce working code. I get runtime errors about "thread <ID> create failed."
So the only way to get it working is to cross-compile for 32bit like this
./configure --build=i686-pc-linux-gnu "CFLAGS=-m32 -O3" "CXXFLAGS=-m32 -O3" "LDFLAGS=-m32" --with-cuda=/usr/local/cuda-5.0
(i386 dependencies required, such as g++-multilib, ia32-libs, libcurl4-openssl-dev:i386)
Christian
|
|
|
|
sigesang
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 84
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 16, 2013, 04:38:55 PM |
|
... $ autogen <-- completes, no messages ....
should do ./autogen.sh ... not autogenNot tried any, but autogen and ./autogen.sh is not the same
|
BTC 1basemmmcpVWVfzZMyLA1r2DJMTMnZYoX LTC LiTeTipdGNcXRjTw5pVnMXjB5FFoEfxPAZ
|
|
|
Nemo1024
Legendary
Offline
Activity: 1680
Merit: 1014
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 16, 2013, 08:44:11 PM |
|
Can't download the source from Mega: it just stays at 0% with "Starting download". Are there any other mirrors?
|
“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.” “We are only as strong as we are united, as weak as we are divided.” “It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
|
|
|
mrm0
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 89
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 16, 2013, 10:02:35 PM |
|
... $ autogen <-- completes, no messages ....
should do ./autogen.sh ... not autogenNot tried any, but autogen and ./autogen.sh is not the same I did autogen.sh, but erased the '.sh' part when adding '<-- ' description....
|
1BUcKJVz5n34VwuiyiLtPud1PGn3BLkcPb :-)
|
|
|
mrm0
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 89
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 16, 2013, 10:16:00 PM |
|
there have been some updates to the github repo today.
The only remaining problem I find with the current state of the github repo is that the 64 bit compilation on 64bit Linux machines does not appear to produce working code. I get runtime errors about "thread <ID> create failed."
Pulled the newest master. Configured as before. Making... $ make [...] nvcc -O3 -arch=compute_10 --maxrregcount=124 --ptxas-options=-v -I./compat/jansson -o salsa_kernel.o -c salsa_kernel.cu ./salsa_kernel.cu(174): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(180): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(180): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(192): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(198): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(174): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(174): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(174): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(174): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(180): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(192): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(198): Warning: Cannot tell what pointer points to, assuming global memory space ./salsa_kernel.cu(174): Warning: Cannot tell what pointer points to, assuming global memory space [...]
nvcc -O3 -arch=compute_11 --maxrregcount=124 --ptxas-options=-v -I./compat/jansson -o spinlock_kernel.o -c spinlock_kernel.cu ./spinlock_kernel.cu(207): Warning: Cannot tell what pointer points to, assuming global memory space ./spinlock_kernel.cu(213): Warning: Cannot tell what pointer points to, assuming global memory space ./spinlock_kernel.cu(227): Warning: Cannot tell what pointer points to, assuming global memory space [...]
nvcc -O3 -arch=compute_35 --maxrregcount=64 --ptxas-options=-v -I./compat/jansson -o titan_kernel.o -c titan_kernel.cu nvcc fatal : Value 'compute_35' is not defined for option 'gpu-architecture' make[2]: *** [titan_kernel.o] Error 255 make[2]: Leaving directory `/tmp/CudaMiner-master' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/CudaMiner-master' make: *** [all] Error 2
This last one is expected, as I am on CUDA 4.2 $ nvcc --version nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2012 NVIDIA Corporation Built on Thu_Apr__5_02:05:07_PDT_2012 Cuda compilation tools, release 4.2, V0.2.1221
|
1BUcKJVz5n34VwuiyiLtPud1PGn3BLkcPb :-)
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 16, 2013, 11:35:35 PM |
|
nvcc fatal : Value 'compute_35' is not defined for option 'gpu-architecture' you need CUDA 5 for that ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
mrm0
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 89
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 06:54:42 AM |
|
nvcc fatal : Value 'compute_35' is not defined for option 'gpu-architecture' you need CUDA 5 for that ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Umm.. yes, I thought I have said just that, although less directly? ;-)
|
1BUcKJVz5n34VwuiyiLtPud1PGn3BLkcPb :-)
|
|
|
Nemo1024
Legendary
Offline
Activity: 1680
Merit: 1014
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 07:39:25 AM |
|
Can't download the source from Mega: it just stays at 0% with "Starting download". Are there any other mirrors?
Anyone? I need to download and compile it on Windows. Tried both FireFox and IE and Mega would not start download in either.
|
“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.” “We are only as strong as we are united, as weak as we are divided.” “It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
|
|
|
mrm0
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 89
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 08:03:17 AM |
|
Can't download the source from Mega: it just stays at 0% with "Starting download". Are there any other mirrors?
Anyone? I need to download and compile it on Windows. Tried both FireFox and IE and Mega would not start download in either. $ wget https://github.com/cbuchner1/CudaMiner/archive/master.zip
This URL should work with a standard browser too.
|
1BUcKJVz5n34VwuiyiLtPud1PGn3BLkcPb :-)
|
|
|
Nemo1024
Legendary
Offline
Activity: 1680
Merit: 1014
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 08:21:29 AM Last edit: July 17, 2013, 01:52:41 PM by Nemo1024 |
|
Thank you. EDIT: Build problems. Building on cygwin: $ ./autogen.sh configure.ac:116: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
This one runs ok: $ ./autogen.sh m4_pattern_allow
$ ./configure gives: ...... checking for json_loads in -ljansson... no checking for pthread_create in -lpthread... yes ./configure: line 6032: syntax error near unexpected token `,' ./configure: line 6032: `LIBCURL_CHECK_CONFIG(, 7.15.2, ,'
Before that I've successfully run ./configure && make && make install on curl-7.29.0
Now, deleted all files an started afresh without running autogen.sh.
./configure finished fine, but the new hiccup is in make:
EDIT: Seems I didn't have nVidia GPU Computing Tooltik installed. It should have been linked to from OP https://developer.nvidia.com/cuda-downloads?sid=311699
Still compile problems, though:
nvcc -g -O2 -arch=compute_10 --maxrregcount=124 --ptxas-options=-v -I./compat/jansson -o salsa_kernel.o -c salsa_kernel.cu nvcc : fatal error : Cannot find compiler 'cl.exe' in PATH Makefile:922: recipe for target `salsa_kernel.o' failed make[2]: *** [salsa_kernel.o] Error 127 make[2]: Leaving directory `/d/CudaMiner-master'
[/s] EDIT: this is getting tedious. I've added path to cl.exe Luckily I still had Visual Studio 2008 installed as cl.exe from VS2012 was not accepted. Now to the next hurdle: nvcc -g -O2 -arch=compute_10 --maxrregcount=124 --ptxas-options=-v -I./compat/jansson -o salsa_kernel.o -c salsa_kernel.cu salsa_kernel.cu salsa_kernel.cu(16) : fatal error C1083: Cannot open include file: 'sys/time.h': No such file or directory Makefile:922: recipe for target `salsa_kernel.o' failed make[2]: *** [salsa_kernel.o] Error 2 make[2]: Leaving directory `/d/CudaMiner-master' Makefile:472: recipe for target `all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/d/CudaMiner-master' Makefile:276: recipe for target `all' failed make: *** [all] Error 2
Still asking: Any alternative venues for building this on Windows? Maybe there are precompiled binaries, the way pooler distributes his cpuminer for Windows? Also, could you provide Windows compile instructions in either OP or in README.txt?!
|
“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.” “We are only as strong as we are united, as weak as we are divided.” “It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
|
|
|
crunchy
Newbie
Offline
Activity: 19
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 10:01:11 AM |
|
it looks very nice :
*** CudaMiner for nVidia GPUs by Christian Buchner *** This is version 2013-07-13 (alpha) based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler Cuda additions Copyright 2013 Christian Buchner My donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
[2013-07-17 11:52:35] 1 miner threads started, using 'scrypt' algorithm. [2013-07-17 11:52:42] GPU #0: GeForce GTX 660 Ti with compute capability 3.0 [2013-07-17 11:52:42] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 1 [2013-07-17 11:52:42] GPU #0: Performing auto-tuning (Patience...) [2013-07-17 11:53:47] GPU #0: 200.69 khash/s with configuration S98x2 [2013-07-17 11:53:47] GPU #0: using launch configuration S98x2 [2013-07-17 11:53:47] GPU #0: GeForce GTX 660 Ti, 6272 hashes, 0.09 khash/s [2013-07-17 11:53:47] GPU #0: GeForce GTX 660 Ti, 6272 hashes, 57.34 khash/s [2013-07-17 11:53:48] GPU #0: GeForce GTX 660 Ti, 119168 hashes, 119.16 khash/s [2013-07-17 11:53:50] GPU #0: GeForce GTX 660 Ti, 238336 hashes, 120.09 khash/s [2013-07-17 11:53:52] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 122.30 khash/s [2013-07-17 11:53:54] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 122.30 khash/s [2013-07-17 11:53:56] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 120.41 khash/s [2013-07-17 11:53:58] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 124.24 khash/s [2013-07-17 11:54:00] GPU #0: GeForce GTX 660 Ti, 250880 hashes, 122.56 khash/s [2013-07-17 11:54:02] GPU #0: GeForce GTX 660 Ti, 250880 hashes, 126.42 khash/s [2013-07-17 11:54:04] GPU #0: GeForce GTX 660 Ti, 257152 hashes, 121.90 khash/s [2013-07-17 11:54:06] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 121.35 khash/s [2013-07-17 11:54:08] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 121.35 khash/s [2013-07-17 11:54:10] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 126.24 khash/s [2013-07-17 11:54:12] GPU #0: GeForce GTX 660 Ti, 257152 hashes, 121.90 khash/s [2013-07-17 11:54:14] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 123.26 khash/s [2013-07-17 11:54:16] GPU #0: GeForce GTX 660 Ti, 250880 hashes, 125.43 khash/s [2013-07-17 11:54:18] GPU #0: GeForce GTX 660 Ti, 250880 hashes, 124.46 khash/s [2013-07-17 11:54:20] GPU #0: GeForce GTX 660 Ti, 250880 hashes, 121.63 khash/s [2013-07-17 11:54:29] GPU #0: GeForce GTX 660 Ti, 244608 hashes, 122.30 khash/s
great benchmark number, yet it commes nowhere near when it commes to actual running. How why what and when happend, i no longer get result does not validate as with the previous version but alltogether it is
WAAY slower then the 17/04/2013 version.
NUTS, it used to be around 165 kh/sec. now it just promisses more to return less. i'm boggled.
|
|
|
|
cbuchner1 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 02:55:23 PM Last edit: July 17, 2013, 06:39:59 PM by cbuchner1 |
|
Nemo1024, cygwin build problems will be mostly caused my choice of using #if WIN32 to decide whether to use Microsoft Visual C++ specific features and compatibility headers from the "compat" folder. Try replacing it with a preprocessor macro that identifies a Visual C++ version.
Also note that nVidia doesn't support gcc as a backend for the nvcc compiler in Windows. This would be the showstopper.
I recommend Visual C++ 2010 Express for the job.
Christian
|
|
|
|
cbuchner1 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 02:56:28 PM |
|
crunchy, that's puzzling because the CUDA code hasn't changed a single bit.
For speed comparisons, try to give the same launch parameter that was chosen in the 04-30 version. Is also the -i flag the same as back then?
Christian
|
|
|
|
cbuchner1 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 03:10:26 PM |
|
those running cudaMiner on linux systems equipped with nVidia Optimus need to install bumblebee (or comparable software packages) and run
optirun cudaminer
instead of just
cudaminer
Or depending on the software package used to select the GPU, some other program may be required (not optirun, but e.g. primusrun)
Christian
|
|
|
|
minerapia
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 10:02:12 PM |
|
ubuntu 13.04 (and all depencies) = git clone https://github.com/cbuchner1/CudaMiner.gitcd CudaMiner chmod 700 autogen.sh ./autogen.sh ./configure make = working cudaminer even tho I got loads of ./spinlock_kernel.cu(154): Warning: Cannot tell what pointer points to, assuming global memory space ./spinlock_kernel.cu(155): Warning: Cannot tell what pointer points to, assuming global memory space ./spinlock_kernel.cu(156): Warning: Cannot tell what pointer points to, assuming global memory space
|
donations -> btc: 1M6yf45NskQxWXknkMTzQ8o6wShQcSY4EC ltc: LeTpCd6cQL26Q1vjc9kJrTjjFMrPhrpv6j
|
|
|
cbuchner1 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 17, 2013, 10:30:17 PM |
|
I am working towards a more modular design of the CUDA code now. I will support kernels of these types:
L: legacy devices (compute 1.x) (I've removed that one in late April, now it's back). F: Fermi class devices (compute 2.x) K/S: Kepler class devices with compute 3.0 T: Titan devices and other Kepler based devices with compute 3.5 (even a cheap GT640 might qualify)
Autotune always tunes the kernel matching the graphics card, but I will allow a manual override
Some work in progress is already in my cpuminer fork repo on github (check the cbuchner1 account).
|
|
|
|
Nemo1024
Legendary
Offline
Activity: 1680
Merit: 1014
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 18, 2013, 09:04:27 AM |
|
cbuchner1, I stopped trying to build as I finally managed to download your pre-built archive from Mega.co.nz after trying 5 different machines what felt like 500 times. Could you release the prebuilt archive on some other file sharing service? Now, some results: Run on laptop with Quaddro FX 880M. Really nice. I can't compare to CgMiner as it always crashed on all my nVidia cards, but for comparison, poclbm doing SHA-256 managed to give max 12MHs on the same card: *** CudaMiner for nVidia GPUs by Christian Buchner *** This is version 2013-07-13 (alpha) based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler Cuda additions Copyright 2013 Christian Buchner My donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
[2013-07-18 10:36:45] 1 miner threads started, using 'scrypt' algorithm. [2013-07-18 10:36:45] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333 [2013-07-18 10:36:50] GPU #0: Quadro FX 880M with compute capability 1.2 [2013-07-18 10:36:50] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:36:50] GPU #0: Performing auto-tuning (Patience...) [2013-07-18 10:37:08] GPU #0: 15.67 khash/s with configuration 12x6 [2013-07-18 10:37:08] GPU #0: using launch configuration 12x6 [2013-07-18 10:37:28] accepted: 1/1 (100.00%), 15.29 khash/s (yay!!!) [2013-07-18 10:37:41] accepted: 2/2 (100.00%), 15.24 khash/s (yay!!!) [2013-07-18 10:37:52] accepted: 3/3 (100.00%), 15.26 khash/s (yay!!!) Ctrl-C [2013-07-18 10:38:31] workio thread dead, waiting for workers... [2013-07-18 10:38:31] worker threads all shut down, exiting.
--texture-cache 1 reduced the speed to 9.79kh/s (9.79 khash/s with configuration S6x5) --texture-cache 2 reduced the speed to 9.90kh/s (9.90 khash/s with configuration 12x5) A small bug report. I added -t 8 argument just for fun and got the followign. Maybe better error handling is in order? *** CudaMiner for nVidia GPUs by Christian Buchner *** This is version 2013-07-13 (alpha) based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler Cuda additions Copyright 2013 Christian Buchner My donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
[2013-07-18 10:39:05] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333 [2013-07-18 10:39:05] 8 miner threads started, using 'scrypt' algorithm. [2013-07-18 10:39:06] GPU #2: ÙTÐ☻ with compute capability 56620564.257475133 [2013-07-18 10:39:06] GPU #1: øSÐ☻ with compute capability 53605140.257475133 [2013-07-18 10:39:06] GPU #5: {TÐ☻ with compute capability 62911316.257475133 [2013-07-18 10:39:06] GPU #2: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #1: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #7: ♂TÐ☻ with compute capability 66581652.257475133 [2013-07-18 10:39:06] GPU #4: {ÿ║☻ with compute capability 61667220.257475133 [2013-07-18 10:39:06] GPU #0: Quadro FX 880M with compute capability 1.2 [2013-07-18 10:39:06] GPU #5: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #6: +SÐ☻ with compute capability 64352468.257475133 [2013-07-18 10:39:06] GPU #7: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #4: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #6: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #3: Ùÿ║☻ with compute capability 58782612.257475133 [2013-07-18 10:39:06] GPU #3: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 10:39:06] GPU #2: Performing auto-tuning (Patience...) [2013-07-18 10:39:06] GPU #2: 0.00 khash/s with configuration 0x0 [2013-07-18 10:39:06] GPU #2: using launch configuration 0x0 [2013-07-18 10:39:06] GPU #1: Performing auto-tuning (Patience...) [2013-07-18 10:39:06] GPU #1: 0.00 khash/s with configuration 0x0 [2013-07-18 10:39:06] GPU #1: using launch configuration 0x0 [2013-07-18 10:39:06] GPU #5: Performing auto-tuning (Patience...) [2013-07-18 10:39:06] GPU #5: 0.00 khash/s with configuration 0x0 [2013-07-18 10:39:06] GPU #5: using launch configuration 0x0 [2013-07-18 10:39:06] GPU #7: Performing auto-tuning (Patience...) [2013-07-18 10:39:06] GPU #7: 0.00 khash/s with configuration 0x0 [2013-07-18 10:39:06] GPU #7: using launch configuration 0x0 [2013-07-18 10:39:06] GPU #4: Performing auto-tuning (Patience...) [2013-07-18 10:39:06] GPU #4: 0.00 khash/s with configuration 0x0 [2013-07-18 10:39:06] GPU #4: using launch configuration 0x0 [2013-07-18 10:39:06] GPU #3: Performing auto-tuning (Patience...) [2013-07-18 10:39:06] GPU #3: 0.00 khash/s with configuration 0x0 [2013-07-18 10:39:06] GPU #3: using launch configuration 0x0 [2013-07-18 10:39:06] GPU #6: Performing auto-tuning (Patience...) [2013-07-18 10:39:06] GPU #6: 0.00 khash/s with configuration 0x0 [2013-07-18 10:39:06] GPU #6: using launch configuration 0x0
I'll report my GeForce 560Ti experience later (with different overclocking settings)
|
“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.” “We are only as strong as we are united, as weak as we are divided.” “It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
|
|
|
cbuchner1 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 18, 2013, 11:55:36 AM |
|
> Maybe better error handling is in order?
ANY kind of error handling is in order.
|
|
|
|
|
Nemo1024
Legendary
Offline
Activity: 1680
Merit: 1014
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 18, 2013, 04:53:01 PM Last edit: July 18, 2013, 07:40:09 PM by Nemo1024 |
|
The promised report on 560Ti: Voltage/GPU Clock/Memory Clock: 1012/880/2100 -> [2013-07-18 18:33:53] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333 [2013-07-18 18:33:53] 1 miner threads started, using 'scrypt' algorithm. [2013-07-18 18:34:05] GPU #0: GeForce GTX 560 Ti with compute capability 2.1 [2013-07-18 18:34:05] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 18:34:05] GPU #0: Performing auto-tuning (Patience...) [2013-07-18 18:34:45] GPU #0: 146.28 khash/s with configuration 16x8 [2013-07-18 18:34:45] GPU #0: using launch configuration 16x8 [2013-07-18 18:40:46] accepted: 1/1 (100.00%), 135.61 khash/s (yay!!!)
1025/940/2300 -> [2013-07-18 18:41:35] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333 [2013-07-18 18:41:35] 1 miner threads started, using 'scrypt' algorithm. [2013-07-18 18:41:38] GPU #0: GeForce GTX 560 Ti with compute capability 2.1 [2013-07-18 18:41:38] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 18:41:38] GPU #0: Performing auto-tuning (Patience...) [2013-07-18 18:42:18] GPU #0: 157.53 khash/s with configuration 16x8 [2013-07-18 18:42:18] GPU #0: using launch configuration 16x8 [2013-07-18 18:42:24] accepted: 1/1 (100.00%), 144.97 khash/s (yay!!!)
1062/980/2400 -> [2013-07-18 19:02:25] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333 [2013-07-18 19:02:25] 1 miner threads started, using 'scrypt' algorithm. [2013-07-18 19:02:27] GPU #0: GeForce GTX 560 Ti with compute capability 2.1 [2013-07-18 19:02:27] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 19:02:28] GPU #0: Performing auto-tuning (Patience...) [2013-07-18 19:03:07] GPU #0: 161.27 khash/s with configuration 63x2 [2013-07-18 19:03:07] GPU #0: using launch configuration 63x2 [2013-07-18 19:03:21] accepted: 1/1 (100.00%), 146.76 khash/s (yay!!!) [2013-07-18 19:03:44] accepted: 2/2 (100.00%), 146.83 khash/s (yay!!!)
1112/1000/2450 -> [2013-07-18 19:05:24] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333 [2013-07-18 19:05:24] 1 miner threads started, using 'scrypt' algorithm. [2013-07-18 19:05:26] GPU #0: GeForce GTX 560 Ti with compute capability 2.1 [2013-07-18 19:05:26] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 19:05:26] GPU #0: Performing auto-tuning (Patience...) [2013-07-18 19:06:07] GPU #0: 166.05 khash/s with configuration 16x8 [2013-07-18 19:06:07] GPU #0: using launch configuration 16x8 [2013-07-18 19:06:08] accepted: 1/1 (100.00%), 151.70 khash/s (yay!!!) [2013-07-18 19:06:18] accepted: 2/2 (100.00%), 156.03 khash/s (yay!!!)
1150/1010/2300 (max on all) -> [2013-07-18 19:08:51] Starting Stratum on stratum+tcp://stratum.give-me-ltc.com:3333 [2013-07-18 19:08:51] 1 miner threads started, using 'scrypt' algorithm. [2013-07-18 19:08:52] GPU #0: GeForce GTX 560 Ti with compute capability 2.1 [2013-07-18 19:08:52] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 0 [2013-07-18 19:08:52] GPU #0: Performing auto-tuning (Patience...) [2013-07-18 19:09:30] GPU #0: 163.83 khash/s with configuration 16x8 [2013-07-18 19:09:30] GPU #0: using launch configuration 16x8 [2013-07-18 19:10:46] Stratum detected new block [2013-07-18 19:11:31] Stratum detected new block [2013-07-18 19:11:32] accepted: 0/1 (0.00%), 150.18 khash/s (booooo) [2013-07-18 19:12:12] accepted: 1/2 (50.00%), 155.28 khash/s (yay!!!) [2013-07-18 19:12:54] accepted: 2/3 (66.67%), 154.59 khash/s (yay!!!)
Playing around with core and memory clock settings individually, I see that memory clock plays the most important role. --texture-cache setting did not affect performance. --interactive 0 gave me additional 10kh/s I ended up using 1012/880/2350 I have tried out CudaMiner with my GUI front-end, Crypto Miners in Tray, and it is fully compatible. Christian, I am sending 1 LTC your way as a thank-you token.
|
“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.” “We are only as strong as we are united, as weak as we are divided.” “It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
|
|
|
|