|
|
grivad
Newbie
 Offline
Activity: 3
Merit: 0
|
 |
June 21, 2014, 09:22:07 PM |
|
ok but why did you change "pool-thread-concurrency" : "20481" when it was said you need to get rid of "pool-gpu-threads" and just set "gpu-threads" in the global section LOL, I had wondered this too. DUH, thanks  Totally misread the suggestion. I'll try this. That's too bad, though. Hopefully this gets fixed soon. x11 and x13 are much better with 2-4 threads, whereas Scrypt and Scrypt-N need 1, as everyone knows. Posted from Bitcointa.lk - #tISNwkrYDnnFhMya |
|
|
|
|
|
platinum4
|
|
June 21, 2014, 10:24:49 PM |
|
it appears that i can't build this from the current source...
don't know if it is a problem on my end or something in the code
Git pull didn't work for me even after a make clean; I had to delete the entire sgminer folder and re-clone the repo so I could compile. The multiple-profile config is awesome. Running quite well on my test rig. i am on win7 and fresh clone still wont compile for me... I had taken you first link and extracted it already into another folder that had sgminer_multi in it, so it probably already had an sgminer.exe in there too. I have no idea what version or flavor of this I am running but it's algo-flipping nicely with an old config file, I haven't tried to get fancy with profiles yet until we see a better set of binaries. |
|
|
|
|
|
DarkAGeS
|
|
June 22, 2014, 12:30:06 AM |
|
ups, yeah... what branch I should compile? |
|
|
|
|
|
badman74
|
|
June 22, 2014, 01:34:56 AM |
|
ups, yeah... what branch I should compile? v5_0 see link above |
|
|
|
|
|
|
|
DragonSlayer
|
|
June 22, 2014, 06:24:32 AM |
|
Thanks for all the great work on sgminer. I was wondering if there is a good guide on how to compile for x64 windows? I have played around with the documents at github, but I have not been successful.
Thanks
|
|
|
|
lewisc46
Newbie
Offline
Activity: 36
Merit: 0
|
|
June 22, 2014, 07:27:10 AM |
|
anyone having issues using this with TMB ?? really long interrupt times and waiting for work time, etc ??
|
|
|
|
|
|
oktay50000
|
|
June 22, 2014, 08:05:41 AM |
|
cant get old config working with this always using cholivas kernel |
BTC : bc1qqz9hvv806w2zs42mx4rn576whxmr202yxp00e9
feel free to buy me a bear
|
|
|
|
DarkAGeS
|
|
June 22, 2014, 08:45:37 AM |
|
ups, yeah... what branch I should compile? v5_0 see link above I confused... I used exactly this miner: git clone -b v5_0 git://github.com/sgminer-dev/sgminer.git |
|
|
|
|
|
bullus
|
|
June 22, 2014, 12:58:41 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner. using sgminer_v5_10062014 no problems |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
badman74
|
|
June 22, 2014, 01:00:44 PM
Last edit: June 22, 2014, 01:10:58 PM by badman74 |
|
|
|
|
|
|
|
badman74
|
|
June 22, 2014, 01:02:17 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner. using sgminer_v5_10062014 no problems i found that trying to use the new profile options caused the 60 sec quit problem |
|
|
|
|
|
bullus
|
|
June 22, 2014, 01:20:01 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner. using sgminer_v5_10062014 no problems i found that trying to use the new profile options caused the 60 sec quit problem I downloade the latest one, but stil the same. What do u mean by new profile options? Also tested with copie the ocl files from 14.6drivers and I get higher hashrates but getting hw-errors. |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
badman74
|
|
June 22, 2014, 01:31:35 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner. using sgminer_v5_10062014 no problems i found that trying to use the new profile options caused the 60 sec quit problem I downloade the latest one, but stil the same. What do u mean by new profile options? Also tested with copie the ocl files from 14.6drivers and I get higher hashrates but getting hw-errors. take a look at the example.conf also check doc/configuration.md |
|
|
|
|
|
bullus
|
|
June 22, 2014, 01:46:21 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner. using sgminer_v5_10062014 no problems i found that trying to use the new profile options caused the 60 sec quit problem I downloade the latest one, but stil the same. What do u mean by new profile options? Also tested with copie the ocl files from 14.6drivers and I get higher hashrates but getting hw-errors. take a look at the example.conf also check doc/configuration.md Ok, need to check that.. It is possible to use multi profiles like? "profile" : "x13,x13old,x13,x13" |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
platinum4
|
|
June 22, 2014, 01:59:59 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner.
using sgminer_v5_10062014 no problems
i found that trying to use the new profile options caused the 60 sec quit problem Are y'all trying to use pool-gpu-threads? This knowingly fucks up on Windows binaries. |
|
|
|
|
|
bullus
|
|
June 22, 2014, 02:04:50 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner.
using sgminer_v5_10062014 no problems
i found that trying to use the new profile options caused the 60 sec quit problem Are y'all trying to use pool-gpu-threads? This knowingly fucks up on Windows binaries. my config but got driver crashes and hw errors, not hashing yet {
"pools" : [
{
"name" : "am01 x11 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4010",
"user" : "xx",
"pass" : "xx",
"profile":"x11"
},
{
"name" : "am02 x13 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4011",
"user" : "xx",
"pass" : "xx",
"profile":"x13,x13old,x13,x13,x13"
}
],
"profiles": [
{
"name": "x11",
"algorithm": "darkcoin-mod",
"intensity": "18",
"device": "0,1,2,3,4",
"thread-concurrency": "8192,8000,8192,8192,8192",
"worksize": "256,64,256,256,256",
"gpu-threads": "2"
},
{
"name": "x13old",
"algorithm": "marucoin-modold",
"device": "1",
"intensity": "18",
"shaders" : "1536",
"thread-concurrency": "8000",
"worksize": "64",
"gpu-threads": "2"
},
{
"name": "x13",
"algorithm": "marucoin-mod",
"device": "0,2,3,4",
"intensity": "18",
"shaders" : "1792",
"thread-concurrency": "8192",
"worksize": "256",
"gpu-threads": "2"
}
],
"extranonce-subscribe" : true,
"remove-disabled" : true,
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "10",
"failover-only" : true,
"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",
"temp-target" : "75",
"temp-overheat" : "85",
"temp-cutoff" : "95",
"temp-hysteresis" : "3",
"vectors" : "1",
"lookup-gap" : "0",
"hamsi-expand-big" : "4",
"no-pool-disable" : true
}
7950-6970-7950-7950-7950 |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
platinum4
|
|
June 22, 2014, 02:17:16 PM |
|
Seems like it is not working, after 30sec. or so it just quits the miner.
using sgminer_v5_10062014 no problems
i found that trying to use the new profile options caused the 60 sec quit problem Are y'all trying to use pool-gpu-threads? This knowingly fucks up on Windows binaries. my config but got driver crashes and hw errors, not hashing yet {
"pools" : [
{
"name" : "am01 x11 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4010",
"user" : "xx",
"pass" : "xx",
"profile":"x11"
},
{
"name" : "am02 x13 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4011",
"user" : "xx",
"pass" : "xx",
"profile":"x13,x13old,x13,x13,x13"
}
],
"profiles": [
{
"name": "x11",
"algorithm": "darkcoin-mod",
"intensity": "18",
"device": "0,1,2,3,4",
"thread-concurrency": "8192,8000,8192,8192,8192",
"worksize": "256,64,256,256,256",
"gpu-threads": "2"
},
{
"name": "x13old",
"algorithm": "marucoin-modold",
"device": "1",
"intensity": "18",
"shaders" : "1536",
"thread-concurrency": "8000",
"worksize": "64",
"gpu-threads": "2"
},
{
"name": "x13",
"algorithm": "marucoin-mod",
"device": "0,2,3,4",
"intensity": "18",
"shaders" : "1792",
"thread-concurrency": "8192",
"worksize": "256",
"gpu-threads": "2"
}
],
"extranonce-subscribe" : true,
"remove-disabled" : true,
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "10",
"failover-only" : true,
"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",
"temp-target" : "75",
"temp-overheat" : "85",
"temp-cutoff" : "95",
"temp-hysteresis" : "3",
"vectors" : "1",
"lookup-gap" : "0",
"hamsi-expand-big" : "4",
"no-pool-disable" : true
}
7950-6970-7950-7950-7950 I have nothing good to offer; conceptually this feels as if it should parse ok; the only issue I see is the 8000 TC and worksize 64, I'm not sure if it will accept such settings (but unfamiliar with it, so don't take my word as gold) Is there a reason you are specifying gpu-threads in each profile, and is there a reason you are running 2 threads as opposed to 1? If you specify it globally at the bottom, then I would omit it elsewhere if you aren't changing it. |
|
|
|
|
|
bullus
|
|
June 22, 2014, 02:19:22 PM
Last edit: June 22, 2014, 02:33:10 PM by bullus |
|
Seems like it is not working, after 30sec. or so it just quits the miner.
using sgminer_v5_10062014 no problems
i found that trying to use the new profile options caused the 60 sec quit problem Are y'all trying to use pool-gpu-threads? This knowingly fucks up on Windows binaries. my config but got driver crashes and hw errors, not hashing yet {
"pools" : [
{
"name" : "am01 x11 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4010",
"user" : "xx",
"pass" : "xx",
"profile":"x11"
},
{
"name" : "am02 x13 multi",
"url" : "stratum+tcp://am02.eu.trademybit.com:4011",
"user" : "xx",
"pass" : "xx",
"profile":"x13,x13old,x13,x13,x13"
}
],
"profiles": [
{
"name": "x11",
"algorithm": "darkcoin-mod",
"intensity": "18",
"device": "0,1,2,3,4",
"thread-concurrency": "8192,8000,8192,8192,8192",
"worksize": "256,64,256,256,256",
"gpu-threads": "2"
},
{
"name": "x13old",
"algorithm": "marucoin-modold",
"device": "1",
"intensity": "18",
"shaders" : "1536",
"thread-concurrency": "8000",
"worksize": "64",
"gpu-threads": "2"
},
{
"name": "x13",
"algorithm": "marucoin-mod",
"device": "0,2,3,4",
"intensity": "18",
"shaders" : "1792",
"thread-concurrency": "8192",
"worksize": "256",
"gpu-threads": "2"
}
],
"extranonce-subscribe" : true,
"remove-disabled" : true,
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "10",
"failover-only" : true,
"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",
"temp-target" : "75",
"temp-overheat" : "85",
"temp-cutoff" : "95",
"temp-hysteresis" : "3",
"vectors" : "1",
"lookup-gap" : "0",
"hamsi-expand-big" : "4",
"no-pool-disable" : true
}
7950-6970-7950-7950-7950 I have nothing good to offer; conceptually this feels as if it should parse ok; the only issue I see is the 8000 TC and worksize 64, I'm not sure if it will accept such settings (but unfamiliar with it, so don't take my word as gold) Is there a reason you are specifying gpu-threads in each profile, and is there a reason you are running 2 threads as opposed to 1? If you specify it globally at the bottom, then I would omit it elsewhere if you aren't changing it. Running it for ages with TCC 8000 and -w 64 for my 6970  I can change that, but I notice it is not creating the darkcoin-mod or marucoin-mod bin files and it's using the ckolivas bin as default, that's why I have a lots of hw-errors and driver crash |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
