CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1058.

CapnBDL

hero member

Activity: 1064

Merit: 500

MOBU

Quote from: sp_ on June 17, 2015, 11:29:52 AM

Quote from: CapnBDL on June 17, 2015, 09:37:47 AM

@sp

Quark algo:

Testing release_53. This version is running faster by ~25kh & so far very stable. Your 7z unzipped to be 18369kb in size while my Win Visual compile sized at 18381kb. Not sure why the difference. What I have found is that the older releases took up to 50 solved shares before reaching 'full speed', while this release ramped up after ~10 shares. All of this, of course, is variable due to network speeds, algo, etc. Using -i 22.9 -r 5 -R 10 --cpu-priority 2 switches. vRam usage is low and my intensity could be increased, but I like it as is. I am basing this info while mining 'quark' on WestHash (usa.nicehash.com). Getting ready to try on donation link.

ASUS i7 z77 intelchip, Win8.1, 16GB ram, ASUS 750Ti-Series_54 2G, GPUTweak OCed.

LOOKIN' GOOD sp_, djm, & gang.

@sp_, djm34
edit: I keep getting 'failure to connect' on this; donate-sp.granitecoin.com:7919 for quark algo. Is there another?

Thx

I have compiled with the 31/5/2015 driver. Different drivers give different code sizes. And old drivers can crash the miner

Yup...I know about tuning...I was just letting you know. I have the latest nVidia drivers, but would like to know if this code was written with Cuda6.5 or 7? I am still using 6.5. I can see I'll have to make some switch changes. Going to default, for now.

edit: never mind...I see it's 6.5.

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: bensam1231 on June 16, 2015, 01:38:05 PM

Quote from: bathrobehero on June 16, 2015, 03:54:33 AM

Quote from: bensam1231 on June 16, 2015, 03:23:07 AM

Quote from: djm34 on June 15, 2015, 02:28:37 PM

Quote from: bensam1231 on June 15, 2015, 11:57:41 AM

Bugreport for Neoscrypt. Running 5 970s on the same system causes it to spit out "Cuda error in func 'scanhash-neoscrypt' at line 67 : out of memory."

Limiting it to any 4 devices with -d eliminates the problem. Tried running separate instances with different devices, doesn't work. System memory is fine. DJM's miner has the same problem.

you need more memory... or pagefile... (which is required to allocate that memory to the gpu...)
alternatively you can lower the intensity, that should free up some memory
other alternative, try to start 1 or 2 ccminer session

As mentioned running more then one instance does not fix this, system memory is fine. It doesn't get maxed out or anywhere close to it while monitoring it. I'll throw some more memory into the system and see what happens though. Currently it's at 4GB.

Haven't tried a lower intensity, this seems more like a bug then anything if that's the case.

Memory is not necessary, pagefile will most likely work. I have 14GB (!) of pagefile on my rigs because I think there was a cudaminer algo that only ran if I had tons of pagefile but it never used more than a few megabytes.
Same goes for sgminer to a certain degree, although I was never able to run it with more than 4 cards enabled.

I will try a bigger pagefile. The pagefile sits at the smallest possible size when the miner is in use and starting up, just like memory. I don't know why this will fix it. My current pagefile already maxes out at 8192, but sits at 1024.

In order to run 5 AMD cards you need to be on W8.1. W7 only allows 4. 6 cards requires a lot of hacking about to make it work no matter what.

Tripled the amount of memory and it fixed it. I assume just adding a extra gig would've done it too. The PC had 4GB in it and four cards ran on it, 5GB probably would've worked. Pagefile was the same size. Makes me wonder if the pagefile idea would've fixed it. I remember something similar when I used to mine Monero coin, even though it never really used the system memory, it still had to preload it through it.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: CapnBDL on June 17, 2015, 09:37:47 AM

@sp

Quark algo:

Testing release_53. This version is running faster by ~25kh & so far very stable. Your 7z unzipped to be 18369kb in size while my Win Visual compile sized at 18381kb. Not sure why the difference. What I have found is that the older releases took up to 50 solved shares before reaching 'full speed', while this release ramped up after ~10 shares. All of this, of course, is variable due to network speeds, algo, etc. Using -i 22.9 -r 5 -R 10 --cpu-priority 2 switches. vRam usage is low and my intensity could be increased, but I like it as is. I am basing this info while mining 'quark' on WestHash (usa.nicehash.com). Getting ready to try on donation link.

ASUS i7 z77 intelchip, Win8.1, 16GB ram, ASUS 750Ti-Series_54 2G, GPUTweak OCed.

LOOKIN' GOOD sp_, djm, & gang.

@sp_, djm34
edit: I keep getting 'failure to connect' on this; donate-sp.granitecoin.com:7919 for quark algo. Is there another?

Thx

I have compiled with the 31/5/2015 driver. Different drivers give different code sizes. And old drivers can crash the miner

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: CapnBDL on June 17, 2015, 10:25:11 AM

Testing Release_53

x13 algo: error; " Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 714 : an illegal instruction was encountered. "

I made no changes to previous setup being used with switches; -i 18.9 -r 5 -R 10 --cpu-priority 2 -a x13
required a graphics driver reinstall or reboot.

x11 algo: error " Cuda error in func 'quark_blake512_cpu_setBlock_80_multi' at line 706 : an illegal instruction was encountered. "

Again, no changes from previous switches; -g 2 -i 18.3 -r 5 -R 10 --cpu-priority 2 -a x11
required graphics driver reinstall or reboot.

OK...that's all the testing I can do today. Am going back to 51.

later-

Each release have different optimal intensity. You need to retune or run with default intensities.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: CapnBDL on June 17, 2015, 09:37:47 AM

@sp

Quark algo:

Testing release_53. This version is running faster by ~25kh & so far very stable. Your 7z unzipped to be 18369kb in size while my Win Visual compile sized at 18381kb. Not sure why the difference. What I have found is that the older releases took up to 50 solved shares before reaching 'full speed', while this release ramped up after ~10 shares. All of this, of course, is variable due to network speeds, algo, etc. Using -i 22.9 -r 5 -R 10 --cpu-priority 2 switches. vRam usage is low and my intensity could be increased, but I like it as is. I am basing this info while mining 'quark' on WestHash (usa.nicehash.com). Getting ready to try on donation link.

ASUS i7 z77 intelchip, Win8.1, 16GB ram, ASUS 750Ti-Series_54 2G, GPUTweak OCed.

LOOKIN' GOOD sp_, djm, & gang.

@sp_, djm34
edit: I keep getting 'failure to connect' on this; donate-sp.granitecoin.com:7919 for quark algo. Is there another?

Thx

its back up and running ...

the vps seemed to have a spat and locked the java threads that run the proxies ...

all good now ...

will look more indepth at them tomorrow ...

we are also running through these donation links ...

https://bitcointalksearch.org/topic/a-chainworks-industries-cwi-project-donate-by-mining-dbm-1089744 ...

#crysx

CapnBDL

hero member

Activity: 1064

Merit: 500

MOBU

Testing Release_53

x13 algo: error; " Cuda error in func 'quark_blake512_cpu_setBlock_80' at line 714 : an illegal instruction was encountered. "

I made no changes to previous setup being used with switches; -i 18.9 -r 5 -R 10 --cpu-priority 2 -a x13
required a graphics driver reinstall or reboot.

x11 algo: error " Cuda error in func 'quark_blake512_cpu_setBlock_80_multi' at line 706 : an illegal instruction was encountered. "

Again, no changes from previous switches; -g 2 -i 18.3 -r 5 -R 10 --cpu-priority 2 -a x11
required graphics driver reinstall or reboot.

OK...that's all the testing I can do today. Am going back to 51.

later-

flipclip

member

Activity: 111

Merit: 10

Quote from: hashbrown9000 on June 16, 2015, 11:48:25 PM

any linux guys having trouble with commit # 829?

If I try to run the newest miner, the command prompt drops to a "#" (pound sign) and no mining happens. Reverting to an earlier version of the miner shows the same results as well.

I compiled and ran fine at commit #829 (that is "Optimized Jh512 from the Tanguy Pruvot branch" correct?) last night (Ubuntu 14.04). Are you running it with a bunch of switches? Have you tried just running ccminer or ccminer --help? to see if it runs.

CapnBDL

hero member

Activity: 1064

Merit: 500

MOBU

@sp

Quark algo:

Testing release_53. This version is running faster by ~25kh & so far very stable. Your 7z unzipped to be 18369kb in size while my Win Visual compile sized at 18381kb. Not sure why the difference. What I have found is that the older releases took up to 50 solved shares before reaching 'full speed', while this release ramped up after ~10 shares. All of this, of course, is variable due to network speeds, algo, etc. Using -i 22.9 -r 5 -R 10 --cpu-priority 2 switches. vRam usage is low and my intensity could be increased, but I like it as is. I am basing this info while mining 'quark' on WestHash (usa.nicehash.com). Getting ready to try on donation link.

ASUS i7 z77 intelchip, Win8.1, 16GB ram, ASUS 750Ti-Series_54 2G, GPUTweak OCed.

LOOKIN' GOOD sp_, djm, & gang.

@sp_, djm34
edit: I keep getting 'failure to connect' on this; donate-sp.granitecoin.com:7919 for quark algo. Is there another?

Thx

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

done

djm34

legendary

Activity: 1400

Merit: 1050

could you remove the cudareset from the main ?
It takes forever to start (especially if there is another miner running on an other card) and it interacts with other mining session.
Not mentionning you are doing it at the start of every algo...

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Make sure to delete this file if it's old:

(in the ccminer folder)

cudart32_65.dll

I had some problems on one of my rigs with release 53 and old drivers...

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

-Faster x11
-Faster quark

1.5.53(sp-MOD) is available here: (17-06-2015)

https://github.com/sp-hash/ccminer/releases/tag/1.5.53

The sourcecode is available here:

https://github.com/sp-hash/ccminer

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: Angora on June 16, 2015, 08:43:28 PM

Hmmm..... sp mod 52 crashed when I tried algo x15 intensity 22.
...
this is on EVGA 750ti running @ stock
...
Intensity 19 is the best @ 3175 khs. 20 gave a net loss of 150k per hash vs no setting.

x15? THe hashrate you are getting is closer to x11 performance. X15 should be around 2100 khash on this card.

hashbrown9000

sr. member

Activity: 427

Merit: 250

any linux guys having trouble with commit # 829?

If I try to run the newest miner, the command prompt drops to a "#" (pound sign) and no mining happens. Reverting to an earlier version of the miner shows the same results as well.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: Angora on June 16, 2015, 08:43:28 PM

Hmmm..... sp mod 52 crashed when I tried algo x15 intensity 22.

error msg : cuda erron in func 'x11_simd512_cpu_init' line 614: unknown error.

testing to see if intensity setting changes hash rate. w/o it, hash is 3100 ksh

this is on EVGA 750ti running @ stock

edit: error poped up again on intensity 21. this time it said out of memory. mystery solved.

intensity 17 card keeps getting work but shows no hashing and then stratum fails and disconnects.

Intensity 19 is the best @ 3175 khs. 20 gave a net loss of 150k per hash vs no setting.

Does the PCI-e slot type have any bearing on hash rate? It is PCI-ex16 2.0

no - the data that goes through teh pci slot is small for mining ...

ALL of our farm cards ( nvidia and amd ) run off x1 risers ...

so you should have no issues at all with data in and out of any of the pcie ports ...

the x15 algo seems to work with our ones at -i 25 - BUT - that does not mean it is the best setting for it ...

dont forget - nicethash have categorically stated ( on the donation thread ) that if there is no work orders on the site - the link gets dropped automatically ...

i am not sure if that has any bearing to ccminer crashing or not - but the lack of work to the miner itself 'may' have bearing on it IF there is an issue with ccminer / x15 not receiving any work or dropping links to the site ...

of course - these are just contemplations 'out there' - and not based on factual tests ...

#crysx

Angora

full member

Activity: 241

Merit: 100

Hmmm..... sp mod 52 crashed when I tried algo x15 intensity 22.

error msg : cuda erron in func 'x11_simd512_cpu_init' line 614: unknown error.

testing to see if intensity setting changes hash rate. w/o it, hash is 3100 ksh

this is on EVGA 750ti running @ stock

edit: error poped up again on intensity 21. this time it said out of memory. mystery solved.

intensity 17 card keeps getting work but shows no hashing and then stratum fails and disconnects.

Intensity 19 is the best @ 3175 khs. 20 gave a net loss of 150k per hash vs no setting.

Does the PCI-e slot type have any bearing on hash rate? It is PCI-ex16 2.0

5w00p

hero member

Activity: 644

Merit: 502

Very good info and great idea, bathrobehero.

GeForce GTX 900-series power consumption discussion thread: https://bitcointalksearch.org/topic/geforce-gtx-900-series-power-consumption-discussion-thread-1091755

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

Quote from: joblo on June 16, 2015, 10:35:58 AM

TDP

Quote from: 5w00p on June 16, 2015, 12:41:37 PM

TDP

Yes, it's not how much a card can pull but TDP does correlate fairly well to that amount (at least it did until the 900-series) and we don't have better figures from the specs. (Linus' explaination: https://www.youtube.com/watch?v=yDWO177BjZY )

I downloaded some random stock BIOSes from here and opened them in Maxwell II BIOS Tweaker to check their maximum ~~TD..~~ I mean power consumption using this image to translate the figures and here are the results (in watts):

Code:

Bios				Flavor		Maximum	Target
Asus.GTX970.4096.141028		Strix OC	250	163.46-193.152
EVGA.GTX970.4096.141020		FTW		250	170-187
Galaxy.GTX970.4096.140912	EXOC		200	200-250
Gigabyte.GTX970.4096.141105	Windforce OC	250	250-280
Gigabyte.GTX970.4096.141910_1	G1 Gaming	250	250-280
MSI.GTX970.4096.141029		Gaming		250	200-220
NVIDIA.GTX970.4096.140826	Reference?	250	151.2-160.3
Palit.GTX970.4096.140903	Standard	250	151.2-160.3
Palit.GTX970.4096.140910	JetStream OC	250	180-200
PNY.GTX90.4096.140912		VCGGTX9704XPB	250	151.2-160.3
Zotac.GTX970.4096.141024	Standard	196	151.2-160-3
Zotac.GTX970.4096.141910	AMP Omega	350	325-345
...
Gigabyte GTX 980		G1 Gaming	250	300-366
Gigabyte GTX 980  		Windforce OC	250	270-300

I added two 980 (CBA to add more) to the list to show the figures does seem to be correct - at least compared to a stress test from a Tom's hardware review:

Ps: we should really have more threads instead of flooding this one with everything

antonio8

legendary

Activity: 1400

Merit: 1000

Quote from: bensam1231 on June 16, 2015, 01:38:05 PM

Quote from: bathrobehero on June 16, 2015, 03:54:33 AM

Quote from: bensam1231 on June 16, 2015, 03:23:07 AM

Quote from: djm34 on June 15, 2015, 02:28:37 PM

Quote from: bensam1231 on June 15, 2015, 11:57:41 AM

Bugreport for Neoscrypt. Running 5 970s on the same system causes it to spit out "Cuda error in func 'scanhash-neoscrypt' at line 67 : out of memory."

Limiting it to any 4 devices with -d eliminates the problem. Tried running separate instances with different devices, doesn't work. System memory is fine. DJM's miner has the same problem.

you need more memory... or pagefile... (which is required to allocate that memory to the gpu...)
alternatively you can lower the intensity, that should free up some memory
other alternative, try to start 1 or 2 ccminer session

As mentioned running more then one instance does not fix this, system memory is fine. It doesn't get maxed out or anywhere close to it while monitoring it. I'll throw some more memory into the system and see what happens though. Currently it's at 4GB.

Haven't tried a lower intensity, this seems more like a bug then anything if that's the case.

Memory is not necessary, pagefile will most likely work. I have 14GB (!) of pagefile on my rigs because I think there was a cudaminer algo that only ran if I had tons of pagefile but it never used more than a few megabytes.
Same goes for sgminer to a certain degree, although I was never able to run it with more than 4 cards enabled.

I will try a bigger pagefile. The pagefile sits at the smallest possible size when the miner is in use and starting up, just like memory. I don't know why this will fix it. My current pagefile already maxes out at 8192, but sits at 1024.

In order to run 5 AMD cards you need to be on W8.1. W7 only allows 4. 6 cards requires a lot of hacking about to make it work no matter what.

I am no pro by any means but I had one rig with 5 AMD cards and had no issues with it at all on Windows 7.

I just didn't like having to change core or memory clocks for different algo's. Became to much of a job. Now that one is just down to a 280x and just waiting to see what the new 300 series does.

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: bathrobehero on June 16, 2015, 03:54:33 AM

Quote from: bensam1231 on June 16, 2015, 03:23:07 AM

Quote from: djm34 on June 15, 2015, 02:28:37 PM

Quote from: bensam1231 on June 15, 2015, 11:57:41 AM

Bugreport for Neoscrypt. Running 5 970s on the same system causes it to spit out "Cuda error in func 'scanhash-neoscrypt' at line 67 : out of memory."

Limiting it to any 4 devices with -d eliminates the problem. Tried running separate instances with different devices, doesn't work. System memory is fine. DJM's miner has the same problem.

you need more memory... or pagefile... (which is required to allocate that memory to the gpu...)
alternatively you can lower the intensity, that should free up some memory
other alternative, try to start 1 or 2 ccminer session

As mentioned running more then one instance does not fix this, system memory is fine. It doesn't get maxed out or anywhere close to it while monitoring it. I'll throw some more memory into the system and see what happens though. Currently it's at 4GB.

Haven't tried a lower intensity, this seems more like a bug then anything if that's the case.

Memory is not necessary, pagefile will most likely work. I have 14GB (!) of pagefile on my rigs because I think there was a cudaminer algo that only ran if I had tons of pagefile but it never used more than a few megabytes.
Same goes for sgminer to a certain degree, although I was never able to run it with more than 4 cards enabled.

I will try a bigger pagefile. The pagefile sits at the smallest possible size when the miner is in use and starting up, just like memory. I don't know why this will fix it. My current pagefile already maxes out at 8192, but sits at 1024.

In order to run 5 AMD cards you need to be on W8.1. W7 only allows 4. 6 cards requires a lot of hacking about to make it work no matter what.

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1058. (Read 2347601 times)