|
unlock.mk
|
 |
July 06, 2014, 11:34:52 PM |
|
I can't get it to work at all on X11 and X13:
AMD 14.6
HD5XXX
Older miner works fine on both algos mentioned above.
|
|
|
|
|
|
badman74
|
|
July 07, 2014, 12:06:24 AM |
|
I can't get it to work at all on X11 and X13:
AMD 14.6
HD5XXX
Older miner works fine on both algos mentioned above.
the newest build only seems to work for me if there is only 1 algo, and no profiles in the config i believe it is being looked into the version in my sig should work, it is the last build i did before it started messing up on me |
|
|
|
|
|
platinum4
|
|
July 07, 2014, 01:10:14 AM |
|
I'm testing that 7-6-2014 build and going to let my pools flip the algos normally as if I wasn't monitoring it. I'll report back. So far, algo flips between x11 and x13 ok. [7/6/2014 6:53:24 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4337 to stratum+tcp://stratum.nicehash.com:4336
[7/6/2014 6:55:04 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4336 to stratum+tcp://stratum.nicehash.com:4337
[7/6/2014 7:40:36 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4337 to stratum+tcp://stratum.nicehash.com:4336
[7/6/2014 7:43:47 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4336 to stratum+tcp://stratum.nicehash.com:4337
[7/6/2014 7:54:20 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4337 to stratum+tcp://stratum.nicehash.com:4336
[7/6/2014 7:56:10 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4336 to stratum+tcp://stratum.nicehash.com:4337
[7/6/2014 8:06:23 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4337 to stratum+tcp://stratum.nicehash.com:4336
[7/6/2014 8:08:33 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4336 to stratum+tcp://stratum.nicehash.com:4337
[7/6/2014 6:41:56 PM] Total hashrate is below X13 minimum threshold 25% (2.398 Mh/s); but am inside the miner's startup grace period (Elapsed:16 sec;GracePeriod:3 min) so did not attempt to restart yet, but I will if the condition exists after the grace period expires.
[7/6/2014 6:53:00 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4337 to stratum+tcp://stratum.nicehash.com:4336
[7/6/2014 6:56:31 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4336 to stratum+tcp://stratum.nicehash.com:4337
[7/6/2014 8:06:09 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4337 to stratum+tcp://stratum.nicehash.com:4336
[7/6/2014 8:07:39 PM] Pool changed from stratum+tcp://stratum.nicehash.com:4336 to stratum+tcp://stratum.nicehash.com:4337
|
|
|
|
|
dark8011
Newbie
 Offline
Activity: 44
Merit: 0
|
|
July 07, 2014, 01:17:37 AM |
|
hi,badman74,thanks for your work.
on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,it says not enough graphic memorys.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in new version sgminer no longer?
Is there any other new sgminer builds that can let that parameter "--thread-concurrency" works again to decrease the memory occupancy in order to let my 512m cards run the x15 algo？
|
|
|
|
|
|
mrbrdo
|
|
July 07, 2014, 02:58:50 AM |
|
dark8011: lookup-gap is only used with Scrypt. I think thread-concurrency also is only used with Scrypt, but in any case it is not used to calculate buffer size for non-Scrypt. I think your cards unfortunately just do not have enough VRAM for these algorithms. The only thing you can try is set gpu-threads to 1 if you don't already have that. Other than that I don't think there's much you can do.
For developers: Perhaps X11/X13... buffer size can be lowered? I remember that some miners had a formula to calculate it, while we use hardcoded values in sgminer 5.0.
|
|
|
|
|
badman74
|
|
July 07, 2014, 03:15:54 AM
Last edit: July 07, 2014, 03:27:42 AM by badman74 |
|
hi,badman74,thanks for your work.
on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,it says not enough graphic memorys.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in new version sgminer no longer?
Is there any other new sgminer builds that can let that parameter "--thread-concurrency" works again to decrease the memory occupancy in order to let my 512m cards run the x15 algo？
don't know about that but i leave the TC out completely and let the kernel build with what is available also try lowering work size |
|
|
|
|
dark8011
Newbie
Offline
Activity: 44
Merit: 0
|
|
July 07, 2014, 03:37:43 AM |
|
hi,badman74,thanks for your work.
on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,it says not enough graphic memorys.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in new version sgminer no longer?
Is there any other new sgminer builds that can let that parameter "--thread-concurrency" works again to decrease the memory occupancy in order to let my 512m cards run the x15 algo？
don't know about that but i leave the TC out completly and let the kernel build with what is available In the practical, place the parameter "--thread-concurrency" into the BAT files , the sgminer can still run,but the "--thread-concurrency" parameter can't take effect actually according to the filename of the *.bin fies built by the new sgminer, I just find the gpu model、worksize and the hamsi_big number but TC information, not like the previous version.. so ,I guess . could it have the new version sgminer cancelled the TC manual operation surpport? |
|
|
|
|
|
platinum4
|
|
July 07, 2014, 09:39:52 AM
Last edit: July 07, 2014, 11:00:20 AM by platinum4 |
|
I'm showing that some of the newer builds don't pay respect to pool priority when it comes to rentals.
If you have your rental pool specified as pool priority 0, even if work is served to it, the miner won't flip back up to it. I didn't have this problem using the build from 07-02-2014 (unversioned, it was ystarnaud's personal wrap)
|
|
|
|
|
|
badman74
|
|
July 07, 2014, 11:14:49 AM |
|
hi,badman74,thanks for your work.
on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,it says not enough graphic memorys.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in new version sgminer no longer?
Is there any other new sgminer builds that can let that parameter "--thread-concurrency" works again to decrease the memory occupancy in order to let my 512m cards run the x15 algo？
don't know about that but i leave the TC out completly and let the kernel build with what is available In the practical, place the parameter "--thread-concurrency" into the BAT files , the sgminer can still run,but the "--thread-concurrency" parameter can't take effect actually according to the filename of the *.bin fies built by the new sgminer, I just find the gpu model、worksize and the hamsi_big number but TC information, not like the previous version.. so ,I guess . could it have the new version sgminer cancelled the TC manual operation surpport? TC only ever affected scrypt and nscrypt and it still works for them |
|
|
|
|
|
platinum4
|
|
July 07, 2014, 12:33:20 PM |
|
@badman74, can you compile an x64 build of the latest commits to sgminer5 repo, the one that adds in log-file capabilities in the .conf files?
|
|
|
|
|
|
mannyg
|
|
July 07, 2014, 03:20:17 PM |
|
Should I upgrade my AMD drivers from 13.12 to 14.6? I'm seeing so many people say they get better hash rate out of the driver upgrade, but also have read about people seeing HW errors, etc.
Is there something I would need to do after upgrading, ie. copying files or something, that would make it work better?
|
|
|
|
|
|
|
|
mannyg
|
|
July 07, 2014, 07:00:51 PM
Last edit: July 07, 2014, 07:33:44 PM by mannyg |
|
OH MY GOD, THANK YOU! FWIW, I didn't even need to upgrade from 13.12 drivers. I kept the same drivers, and just copied those files from the 14.6 drivers into my sgminers folder. This is because since we do profit switching, I dont want to lose the speed I have with Scrypt-N which still comes up profitable sometimes. Upgrading to 14.4 and 14.6, your Scrypt/-N hash speed will decrease. Mining before and after on X13 right now: 280x was 2.5MH/s --- now 3.25MH/s 290 was 2.9MH/s --- now 3.65MH/s X11 also improved: 280x was 3.25MH/s --- now 4.3MH/s 290 was 3.75MH/s --- now 4.85MH/s That link you posted is solid gold. |
|
|
|
|
datosti
Newbie
Offline
Activity: 3
Merit: 0
|
|
July 07, 2014, 07:56:55 PM |
|
I've been trying to get this to run stable for days now, without success. It's hashing and switching fine, but after a couple of hours my GPU goes DEAD. It has never run more than about 5-6 hours straight. I never had a DEAD card before and if I use another miner it runs stable for days, so there's nothing wrong with my card (I rechecked). I don't know what else to try, so hopefully someone else can help me! Here's the config (Asus 280x DC2T): {
"pools" : [
{
"name" : "NH x13 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "BTC adres",
"pass" : "d=.01;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x13"
},
{
"name" : "NH x11 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "BTC adres",
"pass" : "d=.04;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x11"
},
{
"name" : "NH x15 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "BTC adres",
"pass" : "d=.01;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x15"
},
{
"name" : "TMB",
"url" : "stratum+tcp://am01.eu.trademybit.com:3458",
"user" : "user",
"pass" : "x",
"profile": "x11"
}
],
"profiles" : [
{
"name" : "x11",
"algorithm" : "darkcoin-mod",
"intensity" : "17",
"gpu-threads" : "2",
"worksize": "256"
},
{
"name" : "x13",
"algorithm" : "marucoin-mod",
"intensity" : "18",
"gpu-threads" : "2",
"worksize": "128"
},
{
"name" : "x15",
"algorithm" : "bitblock",
"intensity" : "16",
"gpu-threads" : "2",
"worksize": "64"
}
],
"hamsi-expand-big" : "1",
"hamsi-short" : true,
"gpu-engine" : "1070",
"gpu-memclock" : "1500",
"gpu-fan" : "20-60",
"failover-only" : true,
"temp-cutoff" : "75",
"temp-overheat" : "72",
"temp-target" : "68",
"auto-fan" : true,
"auto-gpu" : true,
"expiry" : "1",
"gpu-dyninterval" : "7",
"log" : "5",
"queue" : "0",
"scan-time" : "1",
"no-submit-stale" : false,
"no-restart" : false,
"failover-switch-delay" : "30"
}
try setting intensity on x15 to 16, if that doesn't work it is probably your clocks on one of the algo's is too high Intensity on 16 for X15 fixed it I think. Its running stable for over 10 hours now, thanks alot! Here are the speeds with the config in the quote for an Asus 280x DC2T: X11 - 4.15 MH/s X13 - 3.17 MH/s X15 - 2.62 MH/s I was too early with my conclusion, it's giving me a DEAD gpu again. I even tried without X15 in the config, mining only X11 and X13, but that also did not fix it. The settings for X11 and X13 are the same as I had with other miners and cannot be the problem imo. I use stock engine and mem speeds. Any suggestions? |
|
|
|
|
|
mannyg
|
|
July 07, 2014, 08:02:59 PM |
|
I've been trying to get this to run stable for days now, without success. It's hashing and switching fine, but after a couple of hours my GPU goes DEAD. It has never run more than about 5-6 hours straight. I never had a DEAD card before and if I use another miner it runs stable for days, so there's nothing wrong with my card (I rechecked). I don't know what else to try, so hopefully someone else can help me! Here's the config (Asus 280x DC2T): {
"pools" : [
{
"name" : "NH x13 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "BTC adres",
"pass" : "d=.01;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x13"
},
{
"name" : "NH x11 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "BTC adres",
"pass" : "d=.04;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x11"
},
{
"name" : "NH x15 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "BTC adres",
"pass" : "d=.01;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x15"
},
{
"name" : "TMB",
"url" : "stratum+tcp://am01.eu.trademybit.com:3458",
"user" : "user",
"pass" : "x",
"profile": "x11"
}
],
"profiles" : [
{
"name" : "x11",
"algorithm" : "darkcoin-mod",
"intensity" : "17",
"gpu-threads" : "2",
"worksize": "256"
},
{
"name" : "x13",
"algorithm" : "marucoin-mod",
"intensity" : "18",
"gpu-threads" : "2",
"worksize": "128"
},
{
"name" : "x15",
"algorithm" : "bitblock",
"intensity" : "16",
"gpu-threads" : "2",
"worksize": "64"
}
],
"hamsi-expand-big" : "1",
"hamsi-short" : true,
"gpu-engine" : "1070",
"gpu-memclock" : "1500",
"gpu-fan" : "20-60",
"failover-only" : true,
"temp-cutoff" : "75",
"temp-overheat" : "72",
"temp-target" : "68",
"auto-fan" : true,
"auto-gpu" : true,
"expiry" : "1",
"gpu-dyninterval" : "7",
"log" : "5",
"queue" : "0",
"scan-time" : "1",
"no-submit-stale" : false,
"no-restart" : false,
"failover-switch-delay" : "30"
}
try setting intensity on x15 to 16, if that doesn't work it is probably your clocks on one of the algo's is too high Intensity on 16 for X15 fixed it I think. Its running stable for over 10 hours now, thanks alot! Here are the speeds with the config in the quote for an Asus 280x DC2T: X11 - 4.15 MH/s X13 - 3.17 MH/s X15 - 2.62 MH/s I was too early with my conclusion, it's giving me a DEAD gpu again. I even tried without X15 in the config, mining only X11 and X13, but that also did not fix it. The settings for X11 and X13 are the same as I had with other miners and cannot be the problem imo. I use stock engine and mem speeds. Any suggestions? I've had to decrease gpu-engine clocks by 10Mhz to get rid of the DEAD GPU issue. I would suggest bringing it down just a bit, maybe to 1040 or 1050, and see then. |
|
|
|
|
|
bullus
|
|
July 07, 2014, 08:44:22 PM |
|
OH MY GOD, THANK YOU! FWIW, I didn't even need to upgrade from 13.12 drivers. I kept the same drivers, and just copied those files from the 14.6 drivers into my sgminers folder. This is because since we do profit switching, I dont want to lose the speed I have with Scrypt-N which still comes up profitable sometimes. Upgrading to 14.4 and 14.6, your Scrypt/-N hash speed will decrease. Mining before and after on X13 right now: 280x was 2.5MH/s --- now 3.25MH/s 290 was 2.9MH/s --- now 3.65MH/s X11 also improved: 280x was 3.25MH/s --- now 4.3MH/s 290 was 3.75MH/s --- now 4.85MH/s That link you posted is solid gold. no problem , glad I could help. It was also mention before in this thread I think about those files. I notice with 14.4 that scrypt hashrate was very low yes..will try 13.12 again. |
btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
|
|
|
|
unlock.mk
|
|
July 07, 2014, 09:47:19 PM |
|
With HD5970 HD5850 HD5870 getting lower hashrate by 10%
Copied those files in sgminer folder and hashrate lowered.
|
|
|
|
|
|
mannyg
|
|
July 07, 2014, 10:58:30 PM |
|
With HD5970 HD5850 HD5870 getting lower hashrate by 10%
Copied those files in sgminer folder and hashrate lowered.
Delete the files you copied, and delete the .bin files again, and you will be back to normal. Did you delete the .bin files after copying the driver files and before launching sgminer? I wouldnt expect them to boost older cards. As far as I can tell, it really only boosts performance of the R7/R9 GPUs |
|
|
|
|
|
badman74
|
|
July 08, 2014, 02:50:13 AM |
|
@badman74, can you compile an x64 build of the latest commits to sgminer5 repo, the one that adds in log-file capabilities in the .conf files?
unfortunately i have broken my mingw so until i can fix that i cant build anything |
|
|
|
|
|
platinum4
|
|
July 08, 2014, 03:20:15 AM |
|
@badman74, can you compile an x64 build of the latest commits to sgminer5 repo, the one that adds in log-file capabilities in the .conf files?
unfortunately i have broken my mingw so until i can fix that i cant build anything Gah, in the same boat as me now huh!  |
|
|
|
|
|
