platinum4
|
|
June 09, 2014, 03:38:23 AM |
|
Do you have a pimped hamsi x13 mod cl? Do those 2 settings provide any better hashrate?
|
|
|
|
bullus
|
|
June 09, 2014, 11:16:48 AM Last edit: June 09, 2014, 11:40:47 AM by bullus |
|
I can't make it work. If I use pool-algorithm than no bin file is created, without pool it is fine but only the first pool. If I manually switch to x11 pool no bin file is created, so I have to manually set the x11 pool in my config to the top. Another problem is that it seems it only use the first pool. After creating the bin-files and manually swith to another pool 3 is just says "detected new block", detected new block". No hashrates and no accepting shares. 4x7950 { "pools" : [ { "poolname" : "am02 x13 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4011", "user" : "x", "pass" : "1111", "algorithm" : "marucoin-mod", "gpu-threads" : "2" }, { "poolname" : "am01 x11 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4010", "user" : "x", "pass" : "1111", "pool-algorithm" : "darkcoin-mod", "gpu-threads" : "2" }, { "poolname" : "am02 x13 ", "url" : "stratum+tcp://am02.eu.trademybit.com:5550", "user" : "bullus.3", "pass" : "1111", "pool-algorithm" : "marucoin-mod", "gpu-threads" : "2" }, { "poolname" : "am02 x11", "url" : "stratum+tcp://am02.eu.trademybit.com:4440", "user" : "bullus.3", "pass" : "1111", "algorithm" : "darkcoin-mod", "gpu-threads" : "2" }, { "poolname" : "am01 x13", "url" : "stratum+tcp://am01.eu.trademybit.com:5550", "user" : "x", "pass" : "1111", "pool-algorithm" : "marucoin-mod", "pool-gpu-threads" : "2" }, { "poolname" : "am01 x11", "url" : "stratum+tcp://am01.eu.trademybit.com:4440", "user" : "x", "pass" : "1111", "pool-algorithm" : "darkcoin-mod", "pool-gpu-threads" : "2" }
], "api-allow" : "W:127.0.0.1", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4028", "expiry" : "10", "failover-only" : true, "kernel-path" : "/usr/local/bin", "log" : "5", "queue" : "1", "scan-time" : "7", "shares" : "0", "failover-switch-delay" : "10", "gpu-threads" : "2,2,2,2,2", "gpu-dyninterval" : "7", "gpu-engine" : "0", "gpu-fan" : "65", "gpu-platform" : "0", "gpu-memclock" : "0", "gpu-memdiff" : "0", "gpu-powertune" : "8", "gpu-vddc" : "0", "intensity" : "18", "temp-target" : "75", "temp-overheat" : "85", "temp-cutoff" : "95", "temp-hysteresis" : "3", "vectors" : "1", "worksize" : "256,64,256,256,256", "lookup-gap" : "0", "shaders" : "1792,1536,1792,1792,1792", "thread-concurrency" : "8192,8000,8192,8192,8192", "no-pool-disable" : true, "hamsi-expand-big" : "4", "device" : "0,2,3,4" } Also hamsi to 1 gave me instantly driver failes
|
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
Ninetoe
Newbie
Offline
Activity: 45
Merit: 0
|
|
June 09, 2014, 11:18:50 AM |
|
anyone got a workaround to get new miner to work with cgwatcher ?
|
|
|
|
Dehumanizer
Member
Offline
Activity: 77
Merit: 10
|
|
June 09, 2014, 11:39:14 AM |
|
I was just trying to use the auto-switching but it doesn't seem to work for me. When I set pool ports to 33xx, everything works perfectly, I can manually switch pools and all pools work, however when I switch it over to 43xx and start the sgminer, it says that all pools are dead after a while. Any suggestions?
|
|
|
|
platinum4
|
|
June 09, 2014, 11:39:32 AM |
|
I can't make it work. If I use pool-algorithm than no bin file is created, without pool it is fine but only the first pool. If I manually switch to x11 pool no bin file is created, so I have to manually set the x11 pool in my config to the top. Another problem is that it seems it only use the first pool. After creating the bin-files and manually swith to another pool 3 is just says "detected new block", detected new block". No hashrates and no accepting shares. 4x7950 { "pools" : [ { "poolname" : "am02 x13 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4011", "user" : "x", "pass" : "1111", "algorithm" : "marucoin-mod", "gpu-threads" : "2" }, { "poolname" : "am01 x11 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4010", "user" : "x", "pass" : "1111", "pool-algorithm" : "darkcoin-mod", "gpu-threads" : "2" }, { "poolname" : "am02 x13 ", "url" : "stratum+tcp://am02.eu.trademybit.com:5550", "user" : "bullus.3", "pass" : "1111", "pool-algorithm" : "marucoin-mod", "gpu-threads" : "2" }, { "poolname" : "am02 x11", "url" : "stratum+tcp://am02.eu.trademybit.com:4440", "user" : "bullus.3", "pass" : "1111", "algorithm" : "darkcoin-mod", "gpu-threads" : "2" }, { "poolname" : "am01 x13", "url" : "stratum+tcp://am01.eu.trademybit.com:5550", "user" : "x", "pass" : "1111", "pool-algorithm" : "marucoin-mod", "pool-gpu-threads" : "2" }, { "poolname" : "am01 x11", "url" : "stratum+tcp://am01.eu.trademybit.com:4440", "user" : "x", "pass" : "1111", "pool-algorithm" : "darkcoin-mod", "pool-gpu-threads" : "2" }, { "poolname" : "beta rigs x13", "url" : "stratum+tcp://r6303.g40.rigs.eu.betarigs.com:9136", "user" : "bullus-6303", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-gpu-threads" : "2" }
], "api-allow" : "W:127.0.0.1", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4028", "expiry" : "10", "failover-only" : true, "kernel-path" : "/usr/local/bin", "log" : "5", "queue" : "1", "scan-time" : "7", "shares" : "0", "failover-switch-delay" : "10", "gpu-threads" : "2,2,2,2,2", "gpu-dyninterval" : "7", "gpu-engine" : "0", "gpu-fan" : "65", "gpu-platform" : "0", "gpu-memclock" : "0", "gpu-memdiff" : "0", "gpu-powertune" : "8", "gpu-vddc" : "0", "intensity" : "18", "temp-target" : "75", "temp-overheat" : "85", "temp-cutoff" : "95", "temp-hysteresis" : "3", "vectors" : "1", "worksize" : "256,64,256,256,256", "lookup-gap" : "0", "shaders" : "1792,1536,1792,1792,1792", "thread-concurrency" : "8192,8000,8192,8192,8192", "no-pool-disable" : true, "hamsi-expand-big" : "4", "device" : "0,2,3,4" } Also hamsi to 1 gave me instantly driver failes I would drop all instances of gpu-threads and only put one setting for it in the bottom portion of .conf file. pool-gpu-threads is known to crash this right now.
|
|
|
|
platinum4
|
|
June 09, 2014, 11:41:09 AM |
|
I was just trying to use the auto-switching but it doesn't seem to work for me. When I set pool ports to 33xx, everything works perfectly, I can manually switch pools and all pools work, however when I switch it over to 43xx and start the sgminer, it says that all pools are dead after a while. Any suggestions?
Perfectly normal; in order to 'switch' only one algorithm can be 'selected' at a time. All of NH ports that start with 43xx are multi-algo ports, which will shut, so when 1 is selected, the other 4 algos go dead. If you have no failovers, it is possible you may get no work served if there are not enough orders up for that algo.
|
|
|
|
Dehumanizer
Member
Offline
Activity: 77
Merit: 10
|
|
June 09, 2014, 11:43:36 AM |
|
I was just trying to use the auto-switching but it doesn't seem to work for me. When I set pool ports to 33xx, everything works perfectly, I can manually switch pools and all pools work, however when I switch it over to 43xx and start the sgminer, it says that all pools are dead after a while. Any suggestions?
Perfectly normal; in order to 'switch' only one algorithm can be 'selected' at a time. All of NH ports that start with 43xx are multi-algo ports, which will shut, so when 1 is selected, the other 4 algos go dead. If you have no failovers, it is possible you may get no work served if there are not enough orders up for that algo. I understand that, but there surely IS some work at least for scrypt, since when I go manual, it works. So it's unlikely that there's no work for any algo...
|
|
|
|
nahallacman
Newbie
Offline
Activity: 33
Merit: 0
|
|
June 09, 2014, 11:52:32 AM |
|
I was just trying to use the auto-switching but it doesn't seem to work for me. When I set pool ports to 33xx, everything works perfectly, I can manually switch pools and all pools work, however when I switch it over to 43xx and start the sgminer, it says that all pools are dead after a while. Any suggestions?
Perfectly normal; in order to 'switch' only one algorithm can be 'selected' at a time. All of NH ports that start with 43xx are multi-algo ports, which will shut, so when 1 is selected, the other 4 algos go dead. If you have no failovers, it is possible you may get no work served if there are not enough orders up for that algo. I understand that, but there surely IS some work at least for scrypt, since when I go manual, it works. So it's unlikely that there's no work for any algo... If you only use 4xxx ports there could be a situation where you cant get work, or if it switches to a known buggy algorithm like keccak where I ignore the pool setting, so you have to set the backup pool with a 3xxx port or else the backup pool is pointless. You can set the backup to any one of the profit switching pools main ports on 3xxx, I put things by default on x13 for AMD cards since I have some nvidia cards running x11 that can't be auto switched yet.
|
|
|
|
lbr
|
|
June 09, 2014, 11:57:45 AM |
|
I was just trying to use the auto-switching but it doesn't seem to work for me. When I set pool ports to 33xx, everything works perfectly, I can manually switch pools and all pools work, however when I switch it over to 43xx and start the sgminer, it says that all pools are dead after a while. Any suggestions?
Perfectly normal; in order to 'switch' only one algorithm can be 'selected' at a time. All of NH ports that start with 43xx are multi-algo ports, which will shut, so when 1 is selected, the other 4 algos go dead. If you have no failovers, it is possible you may get no work served if there are not enough orders up for that algo. I understand that, but there surely IS some work at least for scrypt, since when I go manual, it works. So it's unlikely that there's no work for any algo... There is no 'at least'. And there are no multi-algo pools. There are pools with different algos which go offline/dead if they are not profitable. So you must configure all 4xxx pools for nicehash in order to get this to work. Tho, check nicehash thread, apparently they ban by IP for 'hacking'..
|
|
|
|
Dehumanizer
Member
Offline
Activity: 77
Merit: 10
|
|
June 09, 2014, 12:05:44 PM |
|
There is no 'at least'. And there are no multi-algo pools. There are pools with different algos which go offline if they are not profitable.
So you must configure all 4xxx pools for nicehash in order to get this to work. Tho, check nicehash thread, apparently they ban by IP for 'hacking'..
Yes, of course I mean all nicehash pools for different algos. I have set stratum+tcp://stratum.nicehash.com:4333, stratum+tcp://stratum.nicehash.com:4335, stratum+tcp://stratum.nicehash.com:4336, stratum+tcp://stratum.nicehash.com:4337 and stratum+tcp://stratum.nicehash.com:4338 as pools, with no backup because I just wanted to check if it works but it looks like there's no work on neither one of these pools. However when I use same pools with 33xx instead of 43xx, they work. So is it possible that for example stratum+tcp://stratum.nicehash.com:3333 which is a port for scrypt algo works, but 4333 does not work?
|
|
|
|
ekoice
|
|
June 09, 2014, 12:06:47 PM |
|
anybody got a working conf file for 280x cards ? thanks
|
|
|
|
lbr
|
|
June 09, 2014, 12:08:53 PM |
|
So is it possible that for example stratum+tcp://stratum.nicehash.com:3333 which is a port for scrypt algo works, but 4333 does not work?
Yes of course, 3xxx pools are always online. But 4xxx pools are only online when they are most profitable, so multi-algo configuration must include(ideally) all 4xxx pools.
|
|
|
|
bullus
|
|
June 09, 2014, 12:12:37 PM |
|
I can't make it work. If I use pool-algorithm than no bin file is created, without pool it is fine but only the first pool. If I manually switch to x11 pool no bin file is created, so I have to manually set the x11 pool in my config to the top. Another problem is that it seems it only use the first pool. After creating the bin-files and manually swith to another pool 3 is just says "detected new block", detected new block". No hashrates and no accepting shares. 4x7950 { "pools" : [ { "poolname" : "am02 x13 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4011", "user" : "x", "pass" : "1111", "algorithm" : "marucoin-mod", "gpu-threads" : "2" }, { "poolname" : "am01 x11 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4010", "user" : "x", "pass" : "1111", "pool-algorithm" : "darkcoin-mod", "gpu-threads" : "2" }, { "poolname" : "am02 x13 ", "url" : "stratum+tcp://am02.eu.trademybit.com:5550", "user" : "bullus.3", "pass" : "1111", "pool-algorithm" : "marucoin-mod", "gpu-threads" : "2" }, { "poolname" : "am02 x11", "url" : "stratum+tcp://am02.eu.trademybit.com:4440", "user" : "bullus.3", "pass" : "1111", "algorithm" : "darkcoin-mod", "gpu-threads" : "2" }, { "poolname" : "am01 x13", "url" : "stratum+tcp://am01.eu.trademybit.com:5550", "user" : "x", "pass" : "1111", "pool-algorithm" : "marucoin-mod", "pool-gpu-threads" : "2" }, { "poolname" : "am01 x11", "url" : "stratum+tcp://am01.eu.trademybit.com:4440", "user" : "x", "pass" : "1111", "pool-algorithm" : "darkcoin-mod", "pool-gpu-threads" : "2" }, { "poolname" : "beta rigs x13", "url" : "stratum+tcp://r6303.g40.rigs.eu.betarigs.com:9136", "user" : "bullus-6303", "pass" : "x", "pool-algorithm" : "marucoin-mod", "pool-gpu-threads" : "2" }
], "api-allow" : "W:127.0.0.1", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4028", "expiry" : "10", "failover-only" : true, "kernel-path" : "/usr/local/bin", "log" : "5", "queue" : "1", "scan-time" : "7", "shares" : "0", "failover-switch-delay" : "10", "gpu-threads" : "2,2,2,2,2", "gpu-dyninterval" : "7", "gpu-engine" : "0", "gpu-fan" : "65", "gpu-platform" : "0", "gpu-memclock" : "0", "gpu-memdiff" : "0", "gpu-powertune" : "8", "gpu-vddc" : "0", "intensity" : "18", "temp-target" : "75", "temp-overheat" : "85", "temp-cutoff" : "95", "temp-hysteresis" : "3", "vectors" : "1", "worksize" : "256,64,256,256,256", "lookup-gap" : "0", "shaders" : "1792,1536,1792,1792,1792", "thread-concurrency" : "8192,8000,8192,8192,8192", "no-pool-disable" : true, "hamsi-expand-big" : "4", "device" : "0,2,3,4" } Also hamsi to 1 gave me instantly driver failes I would drop all instances of gpu-threads and only put one setting for it in the bottom portion of .conf file. pool-gpu-threads is known to crash this right now. I use this config now, but still doesn't work { "pools" : [ { "poolname" : "am01 x11 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4010", "user" : "x", "pass" : "1111", "algorithm" : "darkcoin-mod" }, { "poolname" : "am02 x13 multi", "url" : "stratum+tcp://am02.eu.trademybit.com:4011", "user" : "x", "pass" : "1111", "algorithm" : "marucoin-mod" }, { "poolname" : "am02 x13 ", "url" : "stratum+tcp://am02.eu.trademybit.com:5550", "user" : "x", "pass" : "1111", "algorithm" : "marucoin-mod" }, { "poolname" : "am02 x11", "url" : "stratum+tcp://am02.eu.trademybit.com:4440", "user" : "x", "pass" : "1111", "algorithm" : "darkcoin-mod" }, { "poolname" : "am01 x13", "url" : "stratum+tcp://am01.eu.trademybit.com:5550", "user" : "x", "pass" : "1111", "algorithm" : "marucoin-mod" }, { "poolname" : "am01 x11", "url" : "stratum+tcp://am01.eu.trademybit.com:4440", "user" : "x", "pass" : "1111", "algorithm" : "darkcoin-mod" } ], "api-allow" : "W:127.0.0.1", "api-listen" : true, "api-mcast-port" : "4028", "api-port" : "4028", "expiry" : "10", "failover-only" : true, "kernel-path" : "/usr/local/bin", "log" : "5", "queue" : "1", "scan-time" : "7", "shares" : "0", "failover-switch-delay" : "10", "gpu-threads" : "2", "gpu-dyninterval" : "7", "gpu-engine" : "0", "gpu-fan" : "65", "gpu-platform" : "0", "gpu-memclock" : "0", "gpu-memdiff" : "0", "gpu-powertune" : "8", "gpu-vddc" : "0", "intensity" : "18", "temp-target" : "75", "temp-overheat" : "85", "temp-cutoff" : "95", "temp-hysteresis" : "3", "vectors" : "1", "worksize" : "256", "lookup-gap" : "0", "shaders" : "1792", "thread-concurrency" : "8192", "no-pool-disable" : true, "hamsi-expand-big" : "4", "device" : "0,2,3,4" } x11 multi is dead ,so it switch to x13 multi but no hashrates, they are just 0. If I set the x13 multi on top of the config it's working, so somehow it doesn't use the second pool "pool-algorithm" doesn't work, it uses the ckolivas kernel. All bin files are created. edit: also "device" : "0-4" doesn't work
|
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
Dehumanizer
Member
Offline
Activity: 77
Merit: 10
|
|
June 09, 2014, 12:13:57 PM |
|
So is it possible that for example stratum+tcp://stratum.nicehash.com:3333 which is a port for scrypt algo works, but 4333 does not work?
Yes of course, 3xxx pools are always online. But 4xxx pools are only online when they are most profitable, so multi-algo configuration must include(ideally) all 4xxx pools. hmm. there might be some different problem here right now... I have now switched back from 4xxx pools to 3xxxx and I see X11 and X13 pools are dead (scrypt, scrypt n-factor and keccak are alive). and from what I see, X11 is now the most profitable and that might be the reason why I'm getting all pools dead with autoswitch. Do X11 and X13 nicehash pools work for anyone right now?
|
|
|
|
lbr
|
|
June 09, 2014, 12:14:39 PM |
|
I have set stratum+tcp://stratum.nicehash.com:4333, stratum+tcp://stratum.nicehash.com:4335, stratum+tcp://stratum.nicehash.com:4336, stratum+tcp://stratum.nicehash.com:4337 and stratum+tcp://stratum.nicehash.com:4338 as pools, with no backup because I just wanted to check if it works but it looks like there's no work on neither one of these pools. But this is strange. Are all of them DEAD? Right now.. my rigs switched to x11 from x13.. ~10 mins ago.
|
|
|
|
Dehumanizer
Member
Offline
Activity: 77
Merit: 10
|
|
June 09, 2014, 12:16:46 PM |
|
I have set stratum+tcp://stratum.nicehash.com:4333, stratum+tcp://stratum.nicehash.com:4335, stratum+tcp://stratum.nicehash.com:4336, stratum+tcp://stratum.nicehash.com:4337 and stratum+tcp://stratum.nicehash.com:4338 as pools, with no backup because I just wanted to check if it works but it looks like there's no work on neither one of these pools. But this is strange. Are all of them DEAD? Right now.. my rigs switched to x11 from x13.. ~10 mins ago. yes, now even manual ports 3336 and 3337 are dead for me... very strange. they were alive about one hour ago or so (before I started playing with autoswitch)
|
|
|
|
lbr
|
|
June 09, 2014, 12:18:32 PM |
|
3336 is ALIVE for me right now..
|
|
|
|
Dehumanizer
Member
Offline
Activity: 77
Merit: 10
|
|
June 09, 2014, 12:22:16 PM |
|
3336 is ALIVE for me right now..
well, then I have absolutely no idea what's going on here... I have also tried to remove the pool and re-add it but it didn't help
|
|
|
|
lbr
|
|
June 09, 2014, 12:31:29 PM |
|
3336 is ALIVE for me right now..
well, then I have absolutely no idea what's going on here... I have also tried to remove the pool and re-add it but it didn't help If it's alive for me and dead for you, either nicehash banned all and whitelisted me or it banned you or you have connection issues to nicehash. In either way nothing to be done.. maybe ask nicehash? Ah, maybe you specified incorrect BTC address? It does go DEAD if it is not valid.
|
|
|
|
Dehumanizer
Member
Offline
Activity: 77
Merit: 10
|
|
June 09, 2014, 12:35:47 PM |
|
3336 is ALIVE for me right now..
well, then I have absolutely no idea what's going on here... I have also tried to remove the pool and re-add it but it didn't help If it's alive for me and dead for you, either nicehash banned all and whitelisted me or it banned you or you have connection issues to nicehash. In either way nothing to be done.. maybe ask nicehash? Ah, maybe you specified incorrect BTC address? It does go DEAD if it is not valid. I'll ask them, however it would be strange if only X11 and X13 ports were banned for my IP and also just a few seconds ago I saw X11 to be alive and then dead again as I switched to it, which would imply connection problems, but if I had connection problems to the X11 and X13 ports, I would have the same problems for all other ports as well, since it's the same IP address...
|
|
|
|
|