I have consumed a lot on the subject and have successfully mined. However, from other reports using a 750TI seem to suggest I should be somewhere around 6-8MH/S.
all three on one motherboard I see around 54mh/s that seems very low with this new ethminer build right ?
basically 17 mhs/s power use is really low though around 300 watts for the whole machine (seems lower than what it should be)
also I notice that the machine is really slow when mining cant do anything else unlike my AMD boxes which are quite usable in windows 10 when the cards are mining. All my miners use the dual core penntiums so are these Nvida cards more CPU dependant than AMD or something ?
I should be able to get closer to 20mhs per card right 17 seems really low even withoute the SMI fix.
without smi fix 17 is not low thats the max hashrate with the new build (if you working in pool) hm how many card connecting to the motherboard? cuse i have msi card and i have no problem with it. ihave one gpu. 21 mhs
@safi182 I have 3 cards connected to the board , but even with 1 card it was slow I'll try that Nvidia inspector tool when I get home from work I guess sucks though power usesage is great which is why I got these I have high cost eelectric around 18cents per kwh so I cant afford to run too many AMD cards.
Stratum is currently incompatible with Dwarfpools stratum?
The point is to remove support of getwork-protocol from genoil`s miner or to make a special key to deactivate it declared compatibility with coinotron are not proved - at least on my win7 x64 rig
I've been playing around with the options for hours but keep running into the following error when -U for CUDA is used, with -G it runs but far from optimal.
CUDA error in func 'init' at line 220 : out of memory. Cuda error in func 'set_header' at line 66 : out of memory.
@Genoil miner is working great! I was having such a difficult time mining till I found your miner. got ~36MHs on my 2x 970's windows 10 rig (the secret to windows 10 and 970s seems to be the 347.52 drivers as @mo35 suggested, with anything newer the hashrate drops to 16-17MHhs)
Stratum is currently incompatible with Dwarfpools stratum?
The point is to remove support of getwork-protocol from genoil`s miner or to make a special key to deactivate it declared compatibility with coinotron are not proved - at least on my win7 x64 rig
@Genoil miner is working great! I was having such a difficult time mining till I found your miner. got ~36MHs on my 2x 970's windows 10 rig (the secret to windows 10 and 970s seems to be the 347.52 drivers as @mo35 suggested, with anything newer the hashrate drops to 16-17MHhs)
if you got 36Mhz witch is first step , play around with NV inspector and try to tweak P0 state clocks , depends on individual card and luck (how your cards OCs) , but 2x970 should easely get you to ~40Mhz. i managed to OC my 2x950 and 1x970 setup from 36 to ~41Mhz
@safi182 I have 3 cards connected to the board , but even with 1 card it was slow I'll try that Nvidia inspector tool when I get home from work I guess sucks though power usesage is great which is why I got these I have high cost eelectric around 18cents per kwh so I cant afford to run too many AMD cards.
Solved my SMI problem on Windows 7. It seems the old driver thats recommend here does not allow SMI access on Windows 7, I updraft do the windowx7 box to the current driver for win 7 (602) or something and SMI state changing was possible.
I Also had to turn off Windows 7 aero on my dual core machine or the miner stutters like crazy and cpu usage was 100%
Now on the pool I see 50mhs to 63mhs max for my 3 970s around 20 to 21mhs per card
I have a really strange problem with my GTX 660Ti. When I'm using the latest version (1.0.4b3) I get an "Cuda error in func set_constants" error.
Then I tried it again with an older version and stumbled across a new problem. It now hashes properly without any error but it doesn't send any shares whatsoever. I ran it for over one hour without a single share beeing transmitted. It doesn't work with eth-proxy nor with the inline pool option. What makes it even stranger is that it does send shares when I use OpenCL (-G). As soon as I use the -U command I get much more Mh/s but it doesn't transmit anything.
I use the following command: ethminer --farm-recheck 200 -U --cuda-block-size 128 --cuda-schedule auto -F http://127.0.0.1:8080/rig1
Comments
http://cryptomining-blog.com/
i have been using
ethminer -F http://eth-us.dwarfpool.com/xxx/miner-05 -U --gpu-batch-size 20
the following [minor] success:
Using Windows 10 and a single GTX 750TI.
I have consumed a lot on the subject and have successfully mined. However, from other reports using a 750TI
seem to suggest I should be somewhere around 6-8MH/S.
Suggestions?
I feel like my GPU isn't working as hard as it could. The fan speed never goes above 42% and the GPU temp is steady under 40 C while mining.
I changed the --gpu-batch-size 20 to --gpu-batch-size 18 and it seemed to run much smoother.
I am happy with my 5-8mh/s on my gaming rig.
example:
[email protected]:~/cpp-ethereum# make -j4
[ 13%] Built target scrypt
[ 16%] Built target secp256k1
[ 45%] Built target devcore
[ 52%] Built target ethash
[ 56%] Building NVCC (Device) object libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
[ 65%] Built target devcrypto
[ 69%] Built target ethash-cl
nvcc fatal : redefinition of argument 'std'
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:207 (message):
Error generating
/home/gega/cpp-ethereum/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
libethash-cuda/CMakeFiles/ethash-cuda.dir/build.make:63: recipe for target 'libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o' failed
make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
CMakeFiles/Makefile2:487: recipe for target 'libethash-cuda/CMakeFiles/ethash-cuda.dir/all' failed
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
ETH_FATDB: 0
[ 69%] Built target BuildInfo.h
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
Please help
Right now I'm only get 16.5 Mhs using the newest binaries win 7 with the older driver suggested
any ideas?
this is the card
http://www.newegg.com/Product/Product.aspx?Item=N82E16814127832
I have two other EVGA cards
http://www.newegg.com/Product/Product.aspx?Item=N82E16814487207
all three on one motherboard I see around 54mh/s that seems very low with this new ethminer build right ?
basically 17 mhs/s power use is really low though around 300 watts for the whole machine (seems lower than what it should be)
also I notice that the machine is really slow when mining cant do anything else unlike my AMD boxes which are quite usable in windows 10 when the cards are mining. All my miners use the dual core penntiums so are these Nvida cards more CPU dependant than AMD or something ?
I should be able to get closer to 20mhs per card right 17 seems really low even withoute the SMI fix.
cuse i have msi card and i have no problem with it. ihave one gpu. 21 mhs
I'll try that Nvidia inspector tool when I get home from work I guess sucks though power usesage is great which is why I got these I have high cost eelectric around 18cents per kwh so I cant afford to run too many AMD cards.
declared compatibility with coinotron are not proved - at least on my win7 x64 rig
I've been playing around with the options for hours but keep running into the following error when -U for CUDA is used, with -G it runs but far from optimal.
CUDA error in func 'init' at line 220 : out of memory.
Cuda error in func 'set_header' at line 66 : out of memory.
Default example tried;
./ethminer -F http://eth-mine.suprnova.cc:3000/$USER.$INSTANCE/10 -U --cuda-extragpu-mem 0 --cuda-block-size 128 --cuda-grid-size 8192 --cuda-schedule auto
Only thing I could think of is that it didn't accept my GPU version on build and had to resort to lowest accepted value of 53.
CUDA toolkit shows Kepler as 30 or 32, so tried compiling in both but without further results.
Also adding 65 to CMakeLists.txt gives error on build.
Looks like I have a new challenge to compile this with the 6.5 toolkit
Does anybody have any other ideas?
I Also had to turn off Windows 7 aero on my dual core machine or the miner stutters like crazy and cpu usage was 100%
Now on the pool I see 50mhs to 63mhs max for my 3 970s around 20 to 21mhs per card
Then I tried it again with an older version and stumbled across a new problem. It now hashes properly without any error but it doesn't send any shares whatsoever. I ran it for over one hour without a single share beeing transmitted. It doesn't work with eth-proxy nor with the inline pool option. What makes it even stranger is that it does send shares when I use OpenCL (-G). As soon as I use the -U command I get much more Mh/s but it doesn't transmit anything.
I use the following command: ethminer --farm-recheck 200 -U --cuda-block-size 128 --cuda-schedule auto -F http://127.0.0.1:8080/rig1
Anyone with a similar problem?