BrewCrewFan
|
|
August 07, 2014, 10:55:03 PM |
|
You're killing your performance using I:20 and worksize:128, go down to I:17 and worksize:64
platinum4, thank you! It was a test with different intensity values, really I use 17-18. My 7850 have a little bit higher hashrate with worksize 128, than with 64. Does worksize 128 have a hidden disadvantages, for example higher reject rate, or not? If anybody interested, I obtain the following results for my 7850 (at engine clock is 1180 MHz): x11 - 2,3 Mh/s (worksize:128, I:18, gpu-threads:2) x13 - 1,8 Mh/s (worksize:128, I:17, gpu-threads:2) x15 - 1,5 Mh/s (worksize:128, I:17, gpu-threads:2) Its funny. I have a bunch of 270x among a few other cards, and they run so much better @ I 16 WS 64. If I bump either one of those the hash goes down. Like with that setting I can get around 3 MH on x11 per card with those settings.... if I bump up the I.... it goes down to 2.9.... and 2.8 if I just bump up the WS... I dont know why.
|
|
|
|
|
|
|
|
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
chadwickx16
|
|
August 07, 2014, 11:39:30 PM |
|
You're killing your performance using I:20 and worksize:128, go down to I:17 and worksize:64
platinum4, thank you! It was a test with different intensity values, really I use 17-18. My 7850 have a little bit higher hashrate with worksize 128, than with 64. Does worksize 128 have a hidden disadvantages, for example higher reject rate, or not? If anybody interested, I obtain the following results for my 7850 (at engine clock is 1180 MHz): x11 - 2,3 Mh/s (worksize:128, I:18, gpu-threads:2) x13 - 1,8 Mh/s (worksize:128, I:17, gpu-threads:2) x15 - 1,5 Mh/s (worksize:128, I:17, gpu-threads:2) Its funny. I have a bunch of 270x among a few other cards, and they run so much better @ I 16 WS 64. If I bump either one of those the hash goes down. Like with that setting I can get around 3 MH on x11 per card with those settings.... if I bump up the I.... it goes down to 2.9.... and 2.8 if I just bump up the WS... I dont know why. Thanks for that. I'll be trying that today.
|
|
|
|
ozzy1926
|
|
August 08, 2014, 01:56:14 AM |
|
is there anyone with a decent 290 profiles.conf ?
|
|
|
|
|
bullus
|
|
August 08, 2014, 06:06:35 PM |
|
|
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
ozzy1926
|
|
August 08, 2014, 10:45:46 PM |
|
ty but i want to see .bat for a 290 not x
|
|
|
|
badman74
|
|
August 08, 2014, 11:37:38 PM Last edit: August 09, 2014, 12:04:33 AM by badman74 |
|
ty but i want to see .bat for a 290 not x the only real difference is your clock speeds.... and if you want to have everything in just a bat file it's gonna get really complicated when you start adding multiple pools and algo's to it for instance this is for my 290's { "pools" : [ { "name" : "X11P2P.com", "url" : "http://x11p2p.com:7903", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt+.02", "pass" : "x", "priority" : "0", "no-extranonce" : true, "profile": "x11" }, { "name" : "Kick-Ass.net DRK P2Pool", "url" : "stratum+tcp://darkcoin.kicks-ass.net:7903", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt+.02", "pass" : "x", "priority" : "0", "no-extranonce" : true, "profile": "x11" }, { "name" : "MineP.it DRK", "url" : "STRATUM+TCP://DRK.MINEP.IT:3333", "user" : "badman74.2", "pass" : "x", "priority" : "1", "profile": "x11" }, { "name" : "Xpool X11", "url" : "stratum+tcp://mine.xpool.ca:8888", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt", "pass" : "x", "priority" : "2", "profile": "x11" }, { "name" : "Xpool Scrypt", "url" : "stratum+tcp://mine.xpool.ca:7777", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt", "pass" : "x", "priority" : "3", "profile": "scrypt" } ], "profiles" : [ { "name" : "x11", "algorithm" : "x11" }, { "name" : "x13", "algorithm" : "x13" }, { "name" : "x15", "algorithm" : "x15" }, { "name" : "NIST5", "algorithm" : "nist5" }, { "name" : "scrypt", "lookup-gap" : "2", "gpu-threads": "1", "algorithm" : "zuikkis" }, { "name" : "nscrypt", "lookup-gap" : "2", "algorithm" : "zuikkis", "nfactor" : "11" }, { "name" : "keccak", "intensity" : "12", "gpu-threads": "4", "algorithm" : "keccak" }, { "name" : "qubit", "algorithm" : "qubitcoin" }, { "name" : "quark", "algorithm" : "quarkcoin" } ], "intensity" : "16", "worksize": "64", "hamsi-expand-big" : "1", "hamsi-short" : true, "blake-compact" : true, "keccak-unroll" : "8", "luffa-parallel" : true, "gpu-fan" : "50-100", "gpu-engine": "1075", "gpu-memclock" : "1375", "gpu-threads" : "2", "failover-only" : true, "temp-cutoff" : "94", "temp-overheat" : "92", "temp-target" : "88", "auto-fan" : true, "auto-gpu" : false, "api-listen" : true, "api-allow" : "W:127.0.0.1", "api-port" : "4028", "expiry" : "1", "gpu-dyninterval" : "7", "hotplug" : "5", "log" : "5", "net-delay" : true, "queue" : "0", "scan-time" : "1", "temp-hysteresis" : "5", "shares" : "0", "no-submit-stale" : false, "no-restart" : false, "failover-switch-delay" : "30", "show-coindiff" : true, "kernel-path" : "/usr/local/bin" }
and this is for my 290x's { "pools" : [ { "name" : "X11P2P.com", "url" : "http://x11p2p.com:7903", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt+.02", "pass" : "x", "priority" : "0", "no-extranonce" : true, "profile": "x11" }, { "name" : "Kick-Ass.net DRK P2Pool", "url" : "stratum+tcp://darkcoin.kicks-ass.net:7903", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt+.02", "pass" : "x", "priority" : "0", "no-extranonce" : true, "profile": "x11" }, { "name" : "MineP.it DRK", "url" : "STRATUM+TCP://DRK.MINEP.IT:3333", "user" : "badman74.1", "pass" : "x", "priority" : "1", "profile": "x11" }, { "name" : "Xpool X11", "url" : "stratum+tcp://mine.xpool.ca:8888", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt", "pass" : "x", "priority" : "2", "profile": "x11" } ], { "profiles" : [ { "name" : "x11", "xintensity" : "64", "algorithm" : "x11" }, { "name" : "x13", "algorithm" : "x13" }, { "name" : "x14", "algorithm" : "x14" }, { "name" : "x15", "algorithm" : "x15" }, { "name" : "NIST5", "algorithm" : "nist5" }, { "name" : "scrypt", "lookup-gap" : "2", "gpu-engine": "1000,1000", "gpu-memclock" : "1250,1250", "gpu-powertune" : "0", "gpu-threads": "1", "algorithm" : "zuikkis" }, { "name" : "nscrypt", "lookup-gap" : "2", "gpu-engine": "1000,1000", "gpu-memclock" : "1250,1250", "gpu-powertune" : "0", "algorithm" : "zuikkis", "nfactor" : "11" }, { "name" : "keccak", "intensity" : "12", "gpu-threads": "4", "algorithm" : "keccak" }, { "name" : "qubit", "intensity" : "14", "algorithm" : "qubitcoin" }, { "name" : "quark", "intensity" : "14", "algorithm" : "quarkcoin" } ], "intensity" : "16", "worksize": "64", "hamsi-expand-big" : "7", "hamsi-short" : true, "blake-compact" : true, "keccak-unroll" : "8", "luffa-parallel" : true, "gpu-fan" : "50-100", "gpu-engine": "1040,1040", "gpu-memclock" : "1375,1375", "gpu-threads" : "2", "failover-only" : true, "temp-cutoff" : "96", "temp-overheat" : "94", "temp-target" : "85", "auto-fan" : true, "auto-gpu" : false, "api-allow" : "W:127.0.0.1", "api-listen" : true, "api-port" : "4028", "expiry" : "1", "gpu-dyninterval" : "7", "hotplug" : "5", "net-delay" : true, "queue" : "0", "scan-time" : "1", "temp-hysteresis" : "5", "shares" : "0", "no-submit-stale" : false, "no-restart" : false, "failover-switch-delay" : "30", "show-coindiff" : true, "remove-disabled" : true }
i pointed to those as i have only optimized x11 on my configs
|
|
|
|
lsss
Newbie
Offline
Activity: 27
Merit: 0
|
|
August 09, 2014, 12:27:12 AM |
|
@ badman...
Could you tell me what each of these do, and to which algo's each applies to?
"hamsi-expand-big" : "7", "hamsi-short" : true, "blake-compact" : true, "keccak-unroll" : "8", "luffa-parallel" : true,
I used all 5 and it helped my X11 a bit, but hurt X13 more than it helped X11.
I haven't tried any other algo's yet.
|
|
|
|
badman74
|
|
August 09, 2014, 12:32:46 AM |
|
@ badman...
Could you tell me what each of these do, and to which algo's each applies to?
"hamsi-expand-big" : "7", "hamsi-short" : true, "blake-compact" : true, "keccak-unroll" : "8", "luffa-parallel" : true,
I used all 5 and it helped my X11 a bit, but hurt X13 more than it helped X11.
I haven't tried any other algo's yet.
the hamsi ones are for x13 blake, keccak, and luffa are for all x algo's plus a few more and the settings for them are dependent on the card i.e old cards need most of them to be set to 0 or false while some need hamsi-expand-big to be set to 1 or 4 my settings generally work for 290's and 290x's while my 7750's need everything set to 0 or off luffa-parallel gives me 100k increase but it was said to cause crashes with some cards keccak-unroll usually only gives around 50k increase for me blake-compact gives about 50k as well with every thing combined my 290's get 5.26mh/s on x11 while my 290x's get 6.1mh/s you can try different settings on each to find what works best for you they should build different bin files for each combination
|
|
|
|
lsss
Newbie
Offline
Activity: 27
Merit: 0
|
|
August 09, 2014, 12:38:38 AM |
|
With all of them added, it has helped my 5870's with X11. 1.922mhs from 1.895
I'm running 3 5870's and 1 7950.
I run these cards at stock clocks of 850 with minimal V, same with my 7950.
|
|
|
|
badman74
|
|
August 09, 2014, 12:41:15 AM |
|
With all of them added, it has helped my 5870's with X11. 1.922mhs from 1.895
I'm running 3 5870's and 1 7950.
for those cards you might try hamsi-expand-big 4 on x13 and see if that helps
|
|
|
|
DragonSlayer
|
|
August 09, 2014, 03:23:46 AM |
|
Anyone ever get this version working with local P2Pool using scrypt-n?
|
|
|
|
badman74
|
|
August 09, 2014, 01:14:53 PM |
|
Anyone ever get this version working with local P2Pool using scrypt-n?
for p2pools put "no-extranonce" : true, in the pool config like this "pools" : [ { "name" : "X11P2P.com", "url" : " http://x11p2p.com:7903", "user" : "XvRs67Wnw1n1Kwtq4ihhTpv699DdJpxdnt+.02", "pass" : "x", "priority" : "0", "no-extranonce" : true, "profile": "x11" },
|
|
|
|
jzhoulon
|
|
August 10, 2014, 08:50:38 AM |
|
hi, I have tried several verion of sgminer ,but still have the problem, I can run successfully with sgminer 4.0.0 and other cgminer. but it can only mine with sript. so i want to use a higher verion ,which always met with this: "Error -11 Building Program <clBuildProgram>" extern/static/register not allowed for variables __constant static const sph_U64 BLAKE_IV512[8] = "./kernal/blake.cl", line 371:error:storage-cleass specifiers I don't kown how to past image,.so I typed my self..
|
|
|
|
badman74
|
|
August 10, 2014, 01:13:32 PM |
|
hi, I have tried several verion of sgminer ,but still have the problem, I can run successfully with sgminer 4.0.0 and other cgminer. but it can only mine with sript. so i want to use a higher verion ,which always met with this: "Error -11 Building Program <clBuildProgram>" extern/static/register not allowed for variables __constant static const sph_U64 BLAKE_IV512[8] = "./kernal/blake.cl", line 371:error:storage-cleass specifiers I don't kown how to past image,.so I typed my self.. most likely you have something set up wrong in your config make sure you are using --algorithm or "algorithm" : to set your algo and not -k or kernel that is the most common issue if this doesn't work post your configuration and we will try to help
|
|
|
|
lsss
Newbie
Offline
Activity: 27
Merit: 0
|
|
August 10, 2014, 03:32:44 PM |
|
badman...I am using "kernel" and it works fine on your latest mod miner from your sig.
Also, on an earlier version, also a v5 from your sig (4.2.2-254-gfdd4), I HAD to use "kernel". I tried and tried to get the miner to build bin's with the as expected "algorithm" and it would not. I could not figure it out. As a hail mary I tried "kernel" and it proceeded to build all bin's in a jiffy with no other changes.
On your latest miner badman, I just copy/pasted my conf over and no issue building bins with "kernel". I have not tried "algorithm" with this newest miner though.
On a side note, with this newest mod miner one of my three 5870's is going dead. Has never happened before and still doesn't with the last v5 miner I was using. Not sure why this new miner doesn't like it.
|
|
|
|
badman74
|
|
August 10, 2014, 03:50:14 PM |
|
badman...I am using "kernel" and it works fine on your latest mod miner from your sig.
Also, on an earlier version, also a v5 from your sig (4.2.2-254-gfdd4), I HAD to use "kernel". I tried and tried to get the miner to build bin's with the as expected "algorithm" and it would not. I could not figure it out. As a hail mary I tried "kernel" and it proceeded to build all bin's in a jiffy with no other changes.
On your latest miner badman, I just copy/pasted my conf over and no issue building bins with "kernel". I have not tried "algorithm" with this newest miner though.
On a side note, with this newest mod miner one of my three 5870's is going dead. Has never happened before and still doesn't with the last v5 miner I was using. Not sure why this new miner doesn't like it.
my version should be the same as the develop branch except for some changes to the *.cl files in the kernels folder as for your card going dead, none of mine have had this problem what algo are you having problems with
|
|
|
|
jch9678
|
|
August 10, 2014, 04:41:26 PM |
|
Hi Badman I've been trying to get my 6 290x working with your configs and your development miner but haven't had any luck. I keep getting "clSetKernelArg" errors as you can see in the image. Also notice the numbering of the devices when the error occurs. GPU 1,2,4,5,4,5 ? GPU 0 and 3 had the clSetKernelArg errors. Here are the configs I'm using: sgminer.conf { "pools" : [ { "name" : "NiceHash x15 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4339", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "x15" }, { "name" : "NiceHash x13 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4337", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "x13" }, { "name" : "NiceHash x11 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4336", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "x11" }, { "name" : "NiceHash nist5 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4340", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "nist5" }, { "name" : "NiceHash keccak Multi", "url" : "stratum+tcp://stratum.nicehash.com:4338", "user" : "x", "pass" : "d=1024;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "keccak" }, { "name" : "NiceHash nscrypt Multi", "url" : "stratum+tcp://stratum.nicehash.com:4335", "user" : "x", "pass" : "d=512;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "scrypt", "state" : "disabled" }, { "name" : "NiceHash scrypt Multi", "url" : "stratum+tcp://stratum.nicehash.com:4333", "user" : "x", "pass" : "d=2048;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "scrypt", "state" : "disabled" }, { "name" : "NiceHash x15 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3339", "user" : "x", "pass" : "x", "profile" : "x15" }, { "name" : "NiceHash x13 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3337", "user" : "19AdJ7ntDga744YSZAYuNZutWSDBcfGE36", "pass" : "x", "profile" : "x13" }, { "name" : "NiceHash x11 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3336", "user" : "x", "pass" : "x", "profile" : "x11" }, { "name" : "NiceHash Keccak Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3338", "user" : "x", "pass" : "x", "profile" : "keccak" }, { "name" : "NiceHash Nist5 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3340", "user" : "x", "pass" : "x", "profile" : "nist5" } ], "api-allow" : "W:127.0.0.1", "api-listen" : true, "gpu-threads" : "1", "gpu-platform" : "1", "gpu-reorder" : true, "temp-target" : "78", "temp-overheat" : "85", "temp-cutoff" : "95", "include" : "profiles.conf" } and profiles.conf { "profiles" : [ { "name" : "x11", "algorithm" : "darkcoin-mod", "xintensity" : "64", "gpu-threads" : "2", "worksize": "64" }, { "name" : "x13", "algorithm" : "marucoin-mod", "xintensity" : "51", "gpu-threads" : "2", "worksize": "64" }, { "name" : "x15", "algorithm" : "bitblock", "xintensity" : "51", "gpu-threads" : "2", "worksize": "64" }, { "name" : "nist5", "algorithm" : "talkcoin-mod", "intensity" : "16", "gpu-threads" : "2", "worksize": "64" } ], "default-profile": "x11", "hamsi-expand-big" : "7", "hamsi-short" : true, "blake-compact" : true, "keccak-unroll" : "8", "luffa-parallel" : true, "shaders" : "2816", "gpu-fan" : "50-100", "gpu-powertune" : "0", "gpu-engine" : "0", "gpu-memclock" : "0", "gpu-vddc" : "0", "auto-fan" : true, "failover-only" : true, "expiry" : "1", "gpu-dyninterval" : "7", "hotplug" : "5", "log" : "5", "queue" : "0", "scan-time" : "1", "temp-hysteresis" : "2", "shares" : "0", "no-submit-stale" : false, "no-restart" : true, "failover-switch-delay" : "30", "show-coindiff" : true, "remove-disabled" : true, "extranonce-subscription" : true } It's basically Bullus's configs with some minor changes like default clocks. On a whim I just changed algorithm to kernel like lsss did and the 6 cards started mining with no clSetKernelArg errors. Though the driver crashed pretty quickly, but that may be due to using Stilt's bios and not adjusting the voltage yet. Any ideas on what's going wrong?
|
BTC: 15GqpmqNNJ1REWrDWTfymh7moos1sEvz7A
|
|
|
badman74
|
|
August 10, 2014, 04:58:49 PM |
|
Hi Badman I've been trying to get my 6 290x working with your configs and your development miner but haven't had any luck. I keep getting "clSetKernelArg" errors as you can see in the image. Also notice the numbering of the devices when the error occurs. GPU 1,2,4,5,4,5 ? GPU 0 and 3 had the clSetKernelArg errors. Here are the configs I'm using: sgminer.conf { "pools" : [ { "name" : "NiceHash x15 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4339", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "x15" }, { "name" : "NiceHash x13 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4337", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "x13" }, { "name" : "NiceHash x11 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4336", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "x11" }, { "name" : "NiceHash nist5 Multi", "url" : "stratum+tcp://stratum.nicehash.com:4340", "user" : "x", "pass" : "d=0.16;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "nist5" }, { "name" : "NiceHash keccak Multi", "url" : "stratum+tcp://stratum.nicehash.com:4338", "user" : "x", "pass" : "d=1024;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "keccak" }, { "name" : "NiceHash nscrypt Multi", "url" : "stratum+tcp://stratum.nicehash.com:4335", "user" : "x", "pass" : "d=512;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "scrypt", "state" : "disabled" }, { "name" : "NiceHash scrypt Multi", "url" : "stratum+tcp://stratum.nicehash.com:4333", "user" : "x", "pass" : "d=2048;f0=5.88;f2=2.88;f3=32;f4=24;f5=2880;f6=21.6;f7=99.6", "profile" : "scrypt", "state" : "disabled" }, { "name" : "NiceHash x15 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3339", "user" : "x", "pass" : "x", "profile" : "x15" }, { "name" : "NiceHash x13 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3337", "user" : "19AdJ7ntDga744YSZAYuNZutWSDBcfGE36", "pass" : "x", "profile" : "x13" }, { "name" : "NiceHash x11 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3336", "user" : "x", "pass" : "x", "profile" : "x11" }, { "name" : "NiceHash Keccak Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3338", "user" : "x", "pass" : "x", "profile" : "keccak" }, { "name" : "NiceHash Nist5 Multi Failover", "url" : "stratum+tcp://stratum.nicehash.com:3340", "user" : "x", "pass" : "x", "profile" : "nist5" } ], "api-allow" : "W:127.0.0.1", "api-listen" : true, "gpu-threads" : "1", "gpu-platform" : "1", "gpu-reorder" : true, "temp-target" : "78", "temp-overheat" : "85", "temp-cutoff" : "95", "include" : "profiles.conf" } and profiles.conf { "profiles" : [ { "name" : "x11", "algorithm" : "darkcoin-mod", "xintensity" : "64", "gpu-threads" : "2", "worksize": "64" }, { "name" : "x13", "algorithm" : "marucoin-mod", "xintensity" : "51", "gpu-threads" : "2", "worksize": "64" }, { "name" : "x15", "algorithm" : "bitblock", "xintensity" : "51", "gpu-threads" : "2", "worksize": "64" }, { "name" : "nist5", "algorithm" : "talkcoin-mod", "intensity" : "16", "gpu-threads" : "2", "worksize": "64" } ], "default-profile": "x11", "hamsi-expand-big" : "7", "hamsi-short" : true, "blake-compact" : true, "keccak-unroll" : "8", "luffa-parallel" : true, "shaders" : "2816", "gpu-fan" : "50-100", "gpu-powertune" : "0", "gpu-engine" : "0", "gpu-memclock" : "0", "gpu-vddc" : "0", "auto-fan" : true, "failover-only" : true, "expiry" : "1", "gpu-dyninterval" : "7", "hotplug" : "5", "log" : "5", "queue" : "0", "scan-time" : "1", "temp-hysteresis" : "2", "shares" : "0", "no-submit-stale" : false, "no-restart" : true, "failover-switch-delay" : "30", "show-coindiff" : true, "remove-disabled" : true, "extranonce-subscription" : true } It's basically Bullus's configs with some minor changes like default clocks. On a whim I just changed algorithm to kernel like lsss did and the 6 cards started mining with no clSetKernelArg errors. Though the driver crashed pretty quickly, but that may be due to using Stilt's bios and not adjusting the voltage yet. Any ideas on what's going wrong? honestly i am not sure what is going on there, i have never been able to get more than 4 cards to work for me although you may try setting them all to I 16 and see if that helps i dont really see anything else wrong with your config
|
|
|
|
lsss
Newbie
Offline
Activity: 27
Merit: 0
|
|
August 10, 2014, 05:28:57 PM |
|
badman...I am using "kernel" and it works fine on your latest mod miner from your sig.
Also, on an earlier version, also a v5 from your sig (4.2.2-254-gfdd4), I HAD to use "kernel". I tried and tried to get the miner to build bin's with the as expected "algorithm" and it would not. I could not figure it out. As a hail mary I tried "kernel" and it proceeded to build all bin's in a jiffy with no other changes.
On your latest miner badman, I just copy/pasted my conf over and no issue building bins with "kernel". I have not tried "algorithm" with this newest miner though.
On a side note, with this newest mod miner one of my three 5870's is going dead. Has never happened before and still doesn't with the last v5 miner I was using. Not sure why this new miner doesn't like it.
my version should be the same as the develop branch except for some changes to the *.cl files in the kernels folder as for your card going dead, none of mine have had this problem what algo are you having problems with It's definately happening with X11, as I have been locked on that algo for most of the time lately. When I first started using the miner I am "pretty sure" it happened on some other algos too, probably X13, but can't really say for sure, at the time I was using the algo switching for X11, X13, X15, and Nsit5, the pool primarily switching between X11 and X13. At first I didn't pay much attention to it, thinking it was just a fluke, and just rebooted and carried on. But it's still happening while locked on X11 for sure. I'll keep playing with it and see if I can find out more, and let you know what happens. I can't really do much with it for the next few days though. Right now I am thinking I'll raise the GPU V a bit and see if that does it, but it would surprise me if that's it as I'm running the same V I have always used, including on the scrypt and scrypt-N algos, which as you know push the cards much harder.
|
|
|
|
|