KiloWatts
Member
Offline
Activity: 119
Merit: 10
|
|
June 11, 2014, 04:59:33 PM |
|
By george, that was it!
I wonder why CGWatcher is causing that ruckus with it? Thank you, I'll keep tinkering with it to try to make it work with CG Watcher, I do like some of it's features.
This was my issue also with the intensity not registering. Unfortunately, I still can't get NScrypt to hash more than 50% of what it's supposed to... I'm getting a paltry 250kh with my r9 290x. Here's my setup: { "pools" : [ { "name" : "NiceHash_Scrypt-N", "url" : "stratum +tcp://stratum.nicehash.com:4335", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "11", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1400" }, { "name" : "NiceHash_Scrypt", "url" : "stratum +tcp://stratum.nicehash.com:4333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "10", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" }, { "name" : "NiceHash_X11", "url" : "stratum +tcp://stratum.nicehash.com:4336", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "darkcoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_X13", "url" : "stratum +tcp://stratum.nicehash.com:4337", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt_Regular_Backup", "url" : "stratum +tcp://stratum.nicehash.com:3333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" } ], "vectors" : "1", "worksize" : "128", "kernel" : "zuikkis", "lookup-gap" : "2", "shaders" : "2560", "gpu-powertune" : "0", "temp-target" : "69", "gpu-threads" : "1", "auto-fan" : true, "log" : "5", "log-dateformat" : "1", "failover-only" : true, "failover-switch-delay" : "30", "no-pool-disable" : true, "scrypt" : true, "queue" : "1", "scan-time" : "7", "expiry" : "28", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4001", "api-allow" : "W:127.0.0.1" }
|
|
|
|
platinum4
|
|
June 11, 2014, 05:13:25 PM |
|
By george, that was it!
I wonder why CGWatcher is causing that ruckus with it? Thank you, I'll keep tinkering with it to try to make it work with CG Watcher, I do like some of it's features.
This was my issue also with the intensity not registering. Unfortunately, I still can't get NScrypt to hash more than 50% of what it's supposed to... I'm getting a paltry 250kh with my r9 290x. Here's my setup: { "pools" : [ { "name" : "NiceHash_Scrypt-N", "url" : "stratum +tcp://stratum.nicehash.com:4335", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "11", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1400" }, { "name" : "NiceHash_Scrypt", "url" : "stratum +tcp://stratum.nicehash.com:4333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "10", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" }, { "name" : "NiceHash_X11", "url" : "stratum +tcp://stratum.nicehash.com:4336", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "darkcoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_X13", "url" : "stratum +tcp://stratum.nicehash.com:4337", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt_Regular_Backup", "url" : "stratum +tcp://stratum.nicehash.com:3333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" } ], "vectors" : "1", "worksize" : "128", "kernel" : "zuikkis", "lookup-gap" : "2", "shaders" : "2560", "gpu-powertune" : "0", "temp-target" : "69", "gpu-threads" : "1", "auto-fan" : true, "log" : "5", "log-dateformat" : "1", "failover-only" : true, "failover-switch-delay" : "30", "no-pool-disable" : true, "scrypt" : true, "queue" : "1", "scan-time" : "7", "expiry" : "28", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4001", "api-allow" : "W:127.0.0.1" } If you have a 290X your shaders value should be 2816; and try ckolivas as the algorithm, keep your TC and drop I to 19. Report back if you get comparable results to vert/exeminer.
|
|
|
|
mannyg
|
|
June 11, 2014, 05:15:15 PM |
|
By george, that was it!
I wonder why CGWatcher is causing that ruckus with it? Thank you, I'll keep tinkering with it to try to make it work with CG Watcher, I do like some of it's features.
This was my issue also with the intensity not registering. Unfortunately, I still can't get NScrypt to hash more than 50% of what it's supposed to... I'm getting a paltry 250kh with my r9 290x. Here's my setup: { "pools" : [ { "name" : "NiceHash_Scrypt-N", "url" : "stratum +tcp://stratum.nicehash.com:4335", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "11", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1400" }, { "name" : "NiceHash_Scrypt", "url" : "stratum +tcp://stratum.nicehash.com:4333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "10", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" }, { "name" : "NiceHash_X11", "url" : "stratum +tcp://stratum.nicehash.com:4336", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "darkcoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_X13", "url" : "stratum +tcp://stratum.nicehash.com:4337", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt_Regular_Backup", "url" : "stratum +tcp://stratum.nicehash.com:3333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" } ], "vectors" : "1", "worksize" : "128", "kernel" : "zuikkis", "lookup-gap" : "2", "shaders" : "2560", "gpu-powertune" : "0", "temp-target" : "69", "gpu-threads" : "1", "auto-fan" : true, "log" : "5", "log-dateformat" : "1", "failover-only" : true, "failover-switch-delay" : "30", "no-pool-disable" : true, "scrypt" : true, "queue" : "1", "scan-time" : "7", "expiry" : "28", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4001", "api-allow" : "W:127.0.0.1" } If you have a 290x, your shaders are wrong. 290x has 2816 shaders. You might also want to try 256 or 512 worksize, and changing the powertune to 10 or 20. Try with gpu-engine 1000, and gpu-memclock of 1250 first, then 1500. one or the other should work. Your TC is ok, but you might see something i noticed with my 290's with that TC and thats higher rejects of ~2%
|
|
|
|
KiloWatts
Member
Offline
Activity: 119
Merit: 10
|
|
June 11, 2014, 05:25:37 PM |
|
Okay, I made the changes, but unfortunately it's about the same... { "pools" : [ { "name" : "NiceHash_Scrypt-N", "url" : "stratum +tcp://stratum.nicehash.com:4335", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "ckolivas", "pool-intensity" : "19", "pool-nfactor" : "11", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1000", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt", "url" : "stratum +tcp://stratum.nicehash.com:4333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "10", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" }, { "name" : "NiceHash_X11", "url" : "stratum +tcp://stratum.nicehash.com:4336", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "darkcoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_X13", "url" : "stratum +tcp://stratum.nicehash.com:4337", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt_Regular_Backup", "url" : "stratum +tcp://stratum.nicehash.com:3333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" } ], "vectors" : "1", "worksize" : "512", "kernel" : "zuikkis", "lookup-gap" : "2", "shaders" : "2816", "gpu-powertune" : "0", "temp-target" : "69", "gpu-threads" : "1", "auto-fan" : true, "log" : "5", "log-dateformat" : "1", "failover-only" : true, "failover-switch-delay" : "30", "no-pool-disable" : true, "scrypt" : true, "queue" : "1", "scan-time" : "7", "expiry" : "28", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4001", "api-allow" : "W:127.0.0.1" }
|
|
|
|
platinum4
|
|
June 11, 2014, 05:32:32 PM |
|
Okay, I made the changes, but unfortunately it's about the same... { "pools" : [ { "name" : "NiceHash_Scrypt-N", "url" : "stratum +tcp://stratum.nicehash.com:4335", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "ckolivas", "pool-intensity" : "19", "pool-nfactor" : "11", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1000", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt", "url" : "stratum +tcp://stratum.nicehash.com:4333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-xintensity" : "400", "pool-nfactor" : "10", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" }, { "name" : "NiceHash_X11", "url" : "stratum +tcp://stratum.nicehash.com:4336", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "darkcoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_X13", "url" : "stratum +tcp://stratum.nicehash.com:4337", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt_Regular_Backup", "url" : "stratum +tcp://stratum.nicehash.com:3333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "zuikkis", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" } ], "vectors" : "1", "worksize" : "512", "kernel" : "zuikkis", "lookup-gap" : "2", "shaders" : "2816", "gpu-powertune" : "0", "temp-target" : "69", "gpu-threads" : "1", "auto-fan" : true, "log" : "5", "log-dateformat" : "1", "failover-only" : true, "failover-switch-delay" : "30", "no-pool-disable" : true, "scrypt" : true, "queue" : "1", "scan-time" : "7", "expiry" : "28", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4001", "api-allow" : "W:127.0.0.1" } Be sure to delete all previous bin files in your newest build's directory. remove/change "zuikkis" in main .conf to "ckolivas" add in "vectors" : "1" and "gpu-platform" : "0", bump memclock to 1500 is OK for a 290X. Report back please. You should at least be in the 300's.
|
|
|
|
Ajeto
Member
Offline
Activity: 97
Merit: 10
|
|
June 11, 2014, 05:39:53 PM |
|
I can't even get this to start on windows7 x64. Starts..then closes no errors..no nothing. And trust me I have run A LOT of different cg/sgminer variations with countless kernels at this point without any problem.
Are you by any chance running it with cgwatcher? If yes start first time with batch file, than you can use cgwatcher.. don't know why
|
|
|
|
KiloWatts
Member
Offline
Activity: 119
Merit: 10
|
|
June 11, 2014, 05:45:28 PM |
|
Okay, all bins deleted. gpu-platform added algorithm changed to ckolivas main conf kernel changed to ckolivas shaders corrected vectors added worksize changed engine/memclock are what i use with vert Each card is still about about 300kh short of where they should be: { "pools" : [ { "name" : "NiceHash_Scrypt-N", "url" : "stratum +tcp://stratum.nicehash.com:4335", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "ckolivas", "pool-intensity" : "20", "pool-nfactor" : "11", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" }, { "name" : "NiceHash_Scrypt", "url" : "stratum +tcp://stratum.nicehash.com:4333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "ckolivas", "pool-xintensity" : "400", "pool-nfactor" : "10", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" }, { "name" : "NiceHash_X11", "url" : "stratum +tcp://stratum.nicehash.com:4336", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "darkcoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_X13", "url" : "stratum +tcp://stratum.nicehash.com:4337", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1050", "pool-gpu-memclock" : "1250" }, { "name" : "NiceHash_Scrypt_Regular_Backup", "url" : "stratum +tcp://stratum.nicehash.com:3333", "user" : "19tg4DmbwEiwebVHoHvCZ5MPTjaPKZhsLY", "pass" : "x", "pool-algorithm" : "ckolivas", "pool-nfactor" : "10", "pool-xintensity" : "400", "pool-thread-concurrency" : "24550", "pool-gpu-engine" : "1040", "pool-gpu-memclock" : "1500" } ], "vectors" : "1", "worksize" : "512", "kernel" : "ckolivas", "lookup-gap" : "2", "shaders" : "2816", "gpu-powertune" : "20", "gpu-platform" : "0", "temp-target" : "80", "temp-overheat" : "85", "temp-cutoff" : "99", "gpu-threads" : "1", "auto-fan" : true, "log" : "5", "log-dateformat" : "1", "failover-only" : true, "failover-switch-delay" : "30", "no-pool-disable" : true, "no-submit-stale" : true, "scrypt" : true, "queue" : "1", "scan-time" : "7", "expiry" : "28", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4001", "api-allow" : "W:127.0.0.1" }
|
|
|
|
guzzzi
Newbie
Offline
Activity: 53
Merit: 0
|
|
June 11, 2014, 05:49:17 PM |
|
Got Asus 290x OC Cards and getting 400+ in NScrypt. But still have Problems when switching the Algos back to NScrypt all Cards go Off. But when starting in Nscrypt it works. { "name" : "NiceHash_Scrypt-N_multi", "url" : "stratum+tcp://stratum.nicehash.com:4335", "user" : "***", "pass" : "***", "pool-nfactor" : "11", "pool-algorithm" : "ckolivas", "pool-intensity" : "19", "pool-gpu-engine" : "950", "pool-gpu-memclock" : "1500", "pool-thread-concurrency" : "25440" },
|
|
|
|
|
KiloWatts
Member
Offline
Activity: 119
Merit: 10
|
|
June 11, 2014, 06:02:36 PM |
|
PS: I tried my exact same conf on the 06/06 release, and I get the same results. In case it matters, I'm on 14.1 drivers.
|
|
|
|
KiloWatts
Member
Offline
Activity: 119
Merit: 10
|
|
June 11, 2014, 06:30:18 PM |
|
Okay, I may have isolated the problem to the driver. I recently upgraded to 14.1, and I can't get _any_ nscrypt miner to hash at the correct speed now. So it's probably the driver.
I'll report back when I've rolled back to 13.11.
|
|
|
|
phzi
|
|
June 11, 2014, 07:01:17 PM |
|
The extranonce-subscribe feature is causing so many issues with other pools... this absolutely stupid client-initiated design needs to be scrapped and replaced with a server initiated system.
I set "no-extranonce-subscribe" : true, on all pools, and so many Dead pool and auth problems stopped immediately.
|
|
|
|
KiloWatts
Member
Offline
Activity: 119
Merit: 10
|
|
June 11, 2014, 07:37:09 PM |
|
Yep, this version doesn't work right with NScrypt and 14.1 drivers. Here's the same config with 13.12 drivers. Still not ideal, but better.
|
|
|
|
comeonalready
|
|
June 11, 2014, 07:53:31 PM |
|
Reconnects are needed, because the stratum protocol does not implement a way to change special extranonce parameters except for on first connection. Switching between other pool's relays requires changing these parameters. You can use the patches or patched compiled cgminer that nicehashdev has posted and are available on git. This implements a new command in the stratum protocol so that the reconnects are not necessary.
True, you can simply download pacthed cgminer and sgminer binaries here: https://www.nicehash.com/software and you'll get rid of these issues and better performance on NiceHash (and the same performance on other pools as if you would be using other non-nicehash cgminer/sgminer builds). BTW: Some pools ignores connection from our extended cgminer and sgminer. We added an option to disable these "advanced features" for pools not supporting this features. One of these pools is CoinFu. Just add "no-extranonce-subscribe" : true to the pool config for pools, that doesn't support extranonce-subscribe Example: { "name" : "NiceHash Scrypt", "url" : "stratum+tcp://stratum.nicehash.com:3333", "user" : "btc_address", "pass" : "x", "algorithm" : "scrypt", "nfactor" : "10" }, { "name" : "CoinFu", "url" : "stratum+tcp://pool.coinfu.io:3333", "no-extranonce-subscribe" : true, "user" : "myrig_btc_address", "pass" : "myemail", "algorithm" : "scrypt", "nfactor" : "10" } Keep in mind: this only applies it you're using our cgminer and sgminer builds from https://www.nicehash.com/software !You guys really mucked up the implementation of the extranonce subscription extension. Of all the ways you could have done it, you chose the only option with the potential to create enabled mining clients that are incompatible with other pools by default. You had full control of your stratum server implementation, and full access to nearly all client miner implementations, but little or no access to oftentimes proprietary stratum implementations at other pools, so the fact that you decided to initiate extranonce subscription messages from the mining client side, demonstrates either your incompetence or ignorance as to how to extend an already well established protocol without introducing negative consequences elsewhere, or callous disregard for the effects upon miners and the other pool operators who are affected by your protocol extension. Given the circumstances, you should be initiating the extranonce subscription from the stratum server side, at which point an enabled mining client can respond in the appropriate fashion, and an earlier version ignore the message as you can easily verify that most mining clients do. But as it stands now, you have created a situation where extranonce subscription enabled mining clients are sending unexpected messages to stratum servers at other pools potentially causing unknown consequences there. Or was sabotaging your competitors part of the original plan?
|
|
|
|
Adz
Newbie
Offline
Activity: 24
Merit: 0
|
|
June 11, 2014, 08:09:08 PM |
|
I can't even get this to start on windows7 x64. Starts..then closes no errors..no nothing. And trust me I have run A LOT of different cg/sgminer variations with countless kernels at this point without any problem.
Are you by any chance running it with cgwatcher? If yes start first time with batch file, than you can use cgwatcher.. don't know why this was listed in the thread earlier remove this code from your pool entries: Code: "pool-gpu-threads": "2"
|
|
|
|
mrbrdo
|
|
June 11, 2014, 08:12:31 PM |
|
Adz does that setting always crash on Windows? Or just in some special circumstances?
|
|
|
|
mrbrdo
|
|
June 11, 2014, 08:16:42 PM |
|
You guys really mucked up the implementation of the extranonce subscription extension. Of all the ways you could have done it, you chose the only option with the potential to create enabled mining clients that are incompatible with other pools by default. You had full control of your stratum server implementation, and full access to nearly all client miner implementations, but little or no access to oftentimes proprietary stratum implementations at other pools, so the fact that you decided to initiate extranonce subscription messages from the mining client side, demonstrates either your incompetence or ignorance as to how to extend an already well established protocol without introducing negative consequences elsewhere, or callous disregard for the effects upon miners and the other pool operators who are affected by your protocol extension.
Given the circumstances, you should be initiating the extranonce subscription from the stratum server side, at which point an enabled mining client can respond in the appropriate fashion, and an earlier version ignore the message as you can easily verify that most mining clients do. But as it stands now, you have created a situation where extranonce subscription enabled mining clients are sending unexpected messages to stratum servers at other pools potentially causing unknown consequences there. Or was sabotaging your competitors part of the original plan?
I have to agree with this (except the last sentance, which is kinda stupid).. I wonder if it is already too late to change this (also, this is just a feature nicehash added, or is it some standard?). I did not go into what this is actually useful for, if it's only for these rental/multipools, then we could simply turn this option off by default (opt-in instead of opt-out). Please do open github issues. I think most of the developers (including me), are not on forums that much, compared to github where we will see the issue very fast and can respond much faster. I guarantee you, things will be fixed faster if you open an issue for it, and especially do that if multiple people are having the same problem. For anyone who doesn't know, issues can be reported here: https://github.com/sgminer-dev/sgminer/issues (please mention if you are using the v5_0 version)
|
|
|
|
platinum4
|
|
June 11, 2014, 08:45:46 PM |
|
PS: I tried my exact same conf on the 06/06 release, and I get the same results. In case it matters, I'm on 14.1 drivers.
THAT's your problem you will only get your good results with 13.12 or older.
|
|
|
|
mannyg
|
|
June 11, 2014, 09:33:50 PM |
|
Yep, this version doesn't work right with NScrypt and 14.1 drivers. Here's the same config with 13.12 drivers. Still not ideal, but better. Yeah I'm on 13.12 drivers and I refuse to upgrade. You might need to start looking at different TC's to tweak the speed. I've seen a number of 290 configs using TC 32765 I used to have 24550 on my 290's, but the 2% rejects started to bother me regardless of how great the hashrate was. I changed it to 25600 and now my reject % is below .5%.
|
|
|
|
Adz
Newbie
Offline
Activity: 24
Merit: 0
|
|
June 11, 2014, 10:35:12 PM |
|
Adz does that setting always crash on Windows? Or just in some special circumstances?
I have found that "pool-gpu-threads": "2" under Windows Will always cause sgminer to exit after 60sec
|
|
|
|
|