I have added some pull requests from a user called t-nelson. Hopefully the crash on ctrl+c is gone now.
Need to test some more. The head version on git might be unstable on windows.
Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 984. (Read 2347664 times)
Submitted another optimalisation in lyra2v2. This change was based on the change tvpruvot did in his fork (skein256 and bmw256),
but I also removed the stack usage, reduced the registercount and threads per block.
lyra2v2 +100KHASH on 970 and 50khash on 750ti (1.1% faster)
but I also removed the stack usage, reduced the registercount and threads per block.
lyra2v2 +100KHASH on 970 and 50khash on 750ti (1.1% faster)
nice - will test today ...
will be going into the office today whether sick or not ... been away from it and working for three weeks now due to illness ...
if i cant make it through today - ill be out for another week ...
the work for the donation links are all there ... just needs community testing and use ...
tanx for the great work ...
#crysx
Try -i 22.9 . You should get 6mhash with.release 61
would that be the sweetspot for the 750ti? ...
i just suggested what thefarm maxes out at before scanhash errors start ...
what would you suggest the -X parameter at sp? ...
#crysx
Submitted another optimalisation in lyra2v2. This change was based on the change tvpruvot did in his fork (skein256 and bmw256),
but I also removed the stack usage, reduced the registercount and threads per block.
lyra2v2 +100KHASH on 970 and 50khash on 750ti (1.1% faster)
but I also removed the stack usage, reduced the registercount and threads per block.
lyra2v2 +100KHASH on 970 and 50khash on 750ti (1.1% faster)
Release 61
Just downloaded the new release and I get "Cuda error in func 'scanhash_lyra2v2' at line 127 : out of memory." on my 6X750Ti rig, running lyra2v2.
Never had this error before.
And some donations from VTC income for the hard working devs in this great community:
- @sp_ : 6fbe32c66687bd5d4c7935b7810e1e0afe8e34e4eef6a8842e754b1cd0f16f76
- @djm34 : 9bb440455556ca17d660f4b896c1c6f66e10654e8f66181e73aeed5b9d6f7c21
- @pallas : 340dc9a0730d0f42f2c1741cd12558d9b41a87c6aacf5bf6c7f22c8681fc23d5
Just downloaded the new release and I get "Cuda error in func 'scanhash_lyra2v2' at line 127 : out of memory." on my 6X750Ti rig, running lyra2v2.
Never had this error before.
And some donations from VTC income for the hard working devs in this great community:
- @sp_ : 6fbe32c66687bd5d4c7935b7810e1e0afe8e34e4eef6a8842e754b1cd0f16f76
- @djm34 : 9bb440455556ca17d660f4b896c1c6f66e10654e8f66181e73aeed5b9d6f7c21
- @pallas : 340dc9a0730d0f42f2c1741cd12558d9b41a87c6aacf5bf6c7f22c8681fc23d5
Thanks very much sir!
I'll test, thanks a lot Sp_!
Gonna send my beer this week, no choice
Gonna send my beer this week, no choice
Try -i 22.9 . You should get 6mhash with.release 61
thanks for the info!
Don't really know what is the X factor neither, I've read the last pages and still not sure about it.
Actually Running on G3220 @ 3.00GHz × 2 with 16 GB Ram (DDR3-1600) for both my 750 ti RIG (x6) and 960 RIG (x6)
I'll try -I 24!
Don't really know what is the X factor neither, I've read the last pages and still not sure about it.
Actually Running on G3220 @ 3.00GHz × 2 with 16 GB Ram (DDR3-1600) for both my 750 ti RIG (x6) and 960 RIG (x6)
I'll try -I 24!
Hi all!
I was wondering what was your setting with a 750 ti and 960 rigs on quark. For the moment I'm still trying to find a good intensity. I'm getting 5-5.5 MH per 750 and roughly 8-9 MH per 960...
Thanks a lot!
I was wondering what was your setting with a 750 ti and 960 rigs on quark. For the moment I'm still trying to find a good intensity. I'm getting 5-5.5 MH per 750 and roughly 8-9 MH per 960...
Thanks a lot!
that depends quite a lot on the hardware itself - but our gigabyte 750ti oc lp cards max out at -i 24 ...
dont know what the -X parameter is - as ive been out commission for almost three weeks now sick - so no tests have been done on the xintensity ...
dont have any 960 cards - so cant help with that one ...
#crysx
Hi all!
I was wondering what was your setting with a 750 ti and 960 rigs on quark. For the moment I'm still trying to find a good intensity. I'm getting 5-5.5 MH per 750 and roughly 8-9 MH per 960...
Thanks a lot!
I was wondering what was your setting with a 750 ti and 960 rigs on quark. For the moment I'm still trying to find a good intensity. I'm getting 5-5.5 MH per 750 and roughly 8-9 MH per 960...
Thanks a lot!
Thanks for your support.
To solve the out of memory issue Increase the virtual memory on your windows installation to 16GB.
you can also try to mine with a lower intensity. Add -I 19 to the commandline
To solve the out of memory issue Increase the virtual memory on your windows installation to 16GB.
you can also try to mine with a lower intensity. Add -I 19 to the commandline
Release 61
Just downloaded the new release and I get "Cuda error in func 'scanhash_lyra2v2' at line 127 : out of memory." on my 6X750Ti rig, running lyra2v2.
Never had this error before.
And some donations from VTC income for the hard working devs in this great community:
- @sp_ : 6fbe32c66687bd5d4c7935b7810e1e0afe8e34e4eef6a8842e754b1cd0f16f76
- @djm34 : 9bb440455556ca17d660f4b896c1c6f66e10654e8f66181e73aeed5b9d6f7c21
- @pallas : 340dc9a0730d0f42f2c1741cd12558d9b41a87c6aacf5bf6c7f22c8681fc23d5
Just downloaded the new release and I get "Cuda error in func 'scanhash_lyra2v2' at line 127 : out of memory." on my 6X750Ti rig, running lyra2v2.
Never had this error before.
And some donations from VTC income for the hard working devs in this great community:
- @sp_ : 6fbe32c66687bd5d4c7935b7810e1e0afe8e34e4eef6a8842e754b1cd0f16f76
- @djm34 : 9bb440455556ca17d660f4b896c1c6f66e10654e8f66181e73aeed5b9d6f7c21
- @pallas : 340dc9a0730d0f42f2c1741cd12558d9b41a87c6aacf5bf6c7f22c8681fc23d5
--ethminer and 750ti on windows--
In a rig with one 970 and one 750ti:
Loading only the 970 with -t 1:
- when running -M (benchmark mode), memory controller load is at 100%, rig is hashing at 18.4Mh/s;
- when running without -M (mining mode), memory controller load is at 100%, rig is hashing at 18.4Mh/s;
Loading 970+750ti with -t 2:
- when running -M, memory controller load for both cards is at 100%, rig is hashing at 27.2Mh/s thus giving 8.8Mh/s for the 750ti;
- when running without -M, memory controller load is at 100% for 970 card and 11%! for 750ti, and rig is hashing at 19.4Mh/s, thus giving only 0.968Mh/s for 750ti (exactly 11% from 100% memory controller load).
I have to say that I have no coding skills, I just noticed this while playing with the switches and looking at Afterburner & GPU-Z readings.
Maybe some of the great coders from here can make something out of this so we can hash at full speed with the 750ti on windows.
EDIT: when adding another 960 memory controller load (for 750ti) drops one bit to 10%, with two 960 stays at 10% and when adding the third 960 (with -t 5), memory controller load for the 750ti drops to 5%.
In a rig with one 970 and one 750ti:
Loading only the 970 with -t 1:
- when running -M (benchmark mode), memory controller load is at 100%, rig is hashing at 18.4Mh/s;
- when running without -M (mining mode), memory controller load is at 100%, rig is hashing at 18.4Mh/s;
Loading 970+750ti with -t 2:
- when running -M, memory controller load for both cards is at 100%, rig is hashing at 27.2Mh/s thus giving 8.8Mh/s for the 750ti;
- when running without -M, memory controller load is at 100% for 970 card and 11%! for 750ti, and rig is hashing at 19.4Mh/s, thus giving only 0.968Mh/s for 750ti (exactly 11% from 100% memory controller load).
I have to say that I have no coding skills, I just noticed this while playing with the switches and looking at Afterburner & GPU-Z readings.
Maybe some of the great coders from here can make something out of this so we can hash at full speed with the 750ti on windows.
EDIT: when adding another 960 memory controller load (for 750ti) drops one bit to 10%, with two 960 stays at 10% and when adding the third 960 (with -t 5), memory controller load for the 750ti drops to 5%.
Funny thing is a few weeks ago I had no problem mining with 2 cards per rig at 8.7mhs per card (that was the max because of CPU usage , 750 Ti's) and literally nothing happened other than block number, newly generated DAGGER files and timestamp and I started to mine with 1-2 mhs per card even with 1 card on all of my rigs. It's not even about disk I/O as I have SSDs in my rigs and their monitored usage is very low - although windows 7 is notorious about terrible file caching.
Today's share sent
djm34: 374808cfd3135fc1e9b302a0c6480ca79e7f8cc7ed81169addc01d1d75f38567
pallas: e42ef59736a03b87dfd1946de7911d4d5bf6f36e3cfdabb180a1733579aa9589
sp_: 66c08edeccebc6f028801dd6aafe6de761dc7fbc1911cbce42917052533015b0
This will be last donation for now. I will keep sending more whenever possible. Thanks to all the devs for awesome work!!
djm34: 374808cfd3135fc1e9b302a0c6480ca79e7f8cc7ed81169addc01d1d75f38567
pallas: e42ef59736a03b87dfd1946de7911d4d5bf6f36e3cfdabb180a1733579aa9589
sp_: 66c08edeccebc6f028801dd6aafe6de761dc7fbc1911cbce42917052533015b0
This will be last donation for now. I will keep sending more whenever possible. Thanks to all the devs for awesome work!!
EDIT: ccminer-lyra, the djm34 fork, should work with older cards but, afaik, only compute 3.5 and up.
I'm working quark on the 660 as well with it.
Heck one 660 or 760 out does 2x R270's time and half with the latest sgminer for those.
I have 4xR270. and a few 5850 and 6870 setting doing nothing. Pair of GTX480 collecting dust on the shelf.
@ --scryptr I've already looked around and already have the most updated ones I could find. downloaded, thanks.
If you want to try it:
https://dl.dropboxusercontent.com/u/34410241/ccminer.exe
RE-RELEASE dot 61--
After mining on NiceHash for about 90 minutes, the re-release of dot 61 apparently performs with a slightly higher hash rate and a correct poolside report of the hash rate. My six-card 750ti FTW rig now hashes Quark at 39.5Mh/s, whereas before it was hashing at about 38.8 Mh/s. Thank you for the hard work! --scryptr
What driver are you using for your 750Ti:s ?After mining on NiceHash for about 90 minutes, the re-release of dot 61 apparently performs with a slightly higher hash rate and a correct poolside report of the hash rate. My six-card 750ti FTW rig now hashes Quark at 39.5Mh/s, whereas before it was hashing at about 38.8 Mh/s. Thank you for the hard work! --scryptr
I am trying to get five cards running on my win8 systems but i only manage to get four of them going at the same time.
LINUX DRIVERS--
I am running Linux for this rig. My driver is older, 340.x, can't remember. Hash rate might be higher with the latest driver... --scryptr
EDIT: Windows? I have one rig on Win 8 with the very latest 355.60 drivers. Windows had no problem recognizing all of my cards on installation, that was several driver versions ago. I have 6 cards on the rig. If you are running CCminer, use the "--devices 0,1,2,3,4" command line switch. See the CCminer help file; if you run "ccminer -h >> help.txt" you get a copy of the help file that you can open in notepad.
One other thing! Is your power supply big enough? --scryptr
EDIT: One other thing, EVGA PrecisionX 16 will only allow you to overclock 4 cards on Windows. Look for nVidia Inspector, an overclocking utility that will allow you to monitor/adjust 6 cards. Should pop up in a Google search.
--scryptr
I use the latest driver from Nvidia.
I never had any issues putting five AMD gpu:s in these rigs before but this was a real hazzle to get working.
Now one rig is mining with five gpus and the other one with four of five gpu:s. I will give that rig another go tomorrow.
I had to move cards around in loads of configurations to finally get five cards found in windows. I spent like five hours straight this evening to get them up and running.
Now they are running smooth and cool anyway
I have Corsair RM850 psu:s in these 750Ti rigs. It should be enough, the rigs are pulling like 320w each @ X11
I use Afterburner to overclock the gpu:s, i think it works pretty good. I will check out Inspector tomorrow, thanks for the tip.
EDIT: ccminer-lyra, the djm34 fork, should work with older cards but, afaik, only compute 3.5 and up.
I'm working quark on the 660 as well with it.
Heck one 660 or 760 out does 2x R270's time and half with the latest sgminer for those.
I have 4xR270. and a few 5850 and 6870 setting doing nothing. Pair of GTX480 collecting dust on the shelf.
@ --scryptr I've already looked around and already have the most updated ones I could find. downloaded, thanks.
If you want to try it:
https://dl.dropboxusercontent.com/u/34410241/ccminer.exe
Will there be problems if running that at server lyra2rev2.usa.nicehash.com:3347
seen a few boo's right off, but also some accepts?
Edit: Maybe a post of your config line flags would help. This is what I'm using to get it to work for me at the moment.
ccminer.exe -a lyra2v2 -o stratum+tcp://lyra2rev2.usa.nicehash.com:3347 -u 18tvS3deKZK5q4eTtPRWYeEMWmGmuErHgz -p x -d 1 --api-bind 0 --cpu-priority 2 -i 19
Edit2: Dropping -19.4 to -i 19 seems to have fix any boo's.
1237 kh/s on stock clocks with the 760... thanks for posting...!
EDIT: ccminer-lyra, the djm34 fork, should work with older cards but, afaik, only compute 3.5 and up.
I'm working quark on the 660 as well with it.
Heck one 660 or 760 out does 2x R270's time and half with the latest sgminer for those.
I have 4xR270. and a few 5850 and 6870 setting doing nothing. Pair of GTX480 collecting dust on the shelf.
@ --scryptr I've already looked around and already have the most updated ones I could find. downloaded, thanks.
Good to hear I'll keep a watch out for your post of when that happens and will upgrade accordingly.
Thanks!
RE-RELEASE dot 61--
After mining on NiceHash for about 90 minutes, the re-release of dot 61 apparently performs with a slightly higher hash rate and a correct poolside report of the hash rate. My six-card 750ti FTW rig now hashes Quark at 39.5Mh/s, whereas before it was hashing at about 38.8 Mh/s. Thank you for the hard work! --scryptr
What driver are you using for your 750Ti:s ?After mining on NiceHash for about 90 minutes, the re-release of dot 61 apparently performs with a slightly higher hash rate and a correct poolside report of the hash rate. My six-card 750ti FTW rig now hashes Quark at 39.5Mh/s, whereas before it was hashing at about 38.8 Mh/s. Thank you for the hard work! --scryptr
I am trying to get five cards running on my win8 systems but i only manage to get four of them going at the same time.
LINUX DRIVERS--
I am running Linux for this rig. My driver is older, 340.x, can't remember. Hash rate might be higher with the latest driver... --scryptr
EDIT: Windows? I have one rig on Win 8 with the very latest 355.60 drivers. Windows had no problem recognizing all of my cards on installation, that was several driver versions ago. I have 6 cards on the rig. If you are running CCminer, use the "--devices 0,1,2,3,4" command line switch. See the CCminer help file; if you run "ccminer -h >> help.txt" you get a copy of the help file that you can open in notepad.
One other thing! Is your power supply big enough? --scryptr
EDIT: One other thing, EVGA PrecisionX 16 will only allow you to overclock 4 cards on Windows. Look for nVidia Inspector, an overclocking utility that will allow you to monitor/adjust 6 cards. Should pop up in a Google search.
--scryptr
RE-RELEASE dot 61--
After mining on NiceHash for about 90 minutes, the re-release of dot 61 apparently performs with a slightly higher hash rate and a correct poolside report of the hash rate. My six-card 750ti FTW rig now hashes Quark at 39.5Mh/s, whereas before it was hashing at about 38.8 Mh/s. Thank you for the hard work! --scryptr
What driver are you using for your 750Ti:s ?After mining on NiceHash for about 90 minutes, the re-release of dot 61 apparently performs with a slightly higher hash rate and a correct poolside report of the hash rate. My six-card 750ti FTW rig now hashes Quark at 39.5Mh/s, whereas before it was hashing at about 38.8 Mh/s. Thank you for the hard work! --scryptr
I am trying to get five cards running on my win8 systems but i only manage to get four of them going at the same time.
Jump to: