Bidnant
Newbie
Offline
Activity: 15
Merit: 0
|
|
February 25, 2017, 08:36:07 AM |
|
I see some of you guys getting 300+ H/s from RX 480's. What is being done doing to achieve that?
Modded memory timing.
|
|
|
|
|
|
If you want to be a moderator, report many posts with accuracy. You will be noticed.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
Lucky - Luciano
|
|
February 25, 2017, 01:19:45 PM |
|
I see some of you guys getting 300+ H/s from RX 480's. What is being done doing to achieve that?
Modded memory timing. That is not necessary. My downclock SAPPHIRE NITRO RX480 8 Gb OC+ ( stock BIOS) hashed 300 H/s (1200 MHz GPU, 2100 MHz GDDR5). Hashed be even more on the default clock (1342 MHz GPU).
|
|
|
|
mettalmag
Legendary
Offline
Activity: 1084
Merit: 1003
≡v≡
|
|
February 25, 2017, 01:34:49 PM |
|
I always wanted to ask has anyone tried to mine on win server? Any of them 2008, 2012? While the system is designed to run 24/7 I think there might be less chance for system failure after blackouts and less chance to freeze. Anyone?
|
|
|
|
silentrunner
Newbie
Offline
Activity: 52
Merit: 0
|
|
February 25, 2017, 04:12:43 PM |
|
I have two computers each with two cards (R270 now getting 172 H/s). One runs windows 10 the other ubuntu 14. These have been running fine on 11.1
After upgrading to 12.1 I saw about an 11% bump in h/s.
Windows runs fine but the linux box is restarting claymore every 3 to 20 minutes. It is using crimson 15.12 driver (fglrx-15.302). There appears to be some issue with OpenCL. I tried "-i 1" and "asm 0" but no change. Is there anything else I can try?
12:31:10:922 7a7a2780 GPU 6 temp = 63, old fan speed = 80%, new fan speed = 80% 12:31:10:930 7a7a2780 GPU0 t=69C fan=60%, GPU1 t=63C fan=80% 12:31:10:930 7a7a2780 em hbt: 1, fm hbt: 24, 12:31:10:930 7a7a2780 watchdog - thread 0, hb time 270 12:31:10:930 7a7a2780 watchdog - thread 1, hb time 402 12:31:10:930 7a7a2780 watchdog - thread 2, hb time 133 12:31:10:930 7a7a2780 watchdog - thread 3, hb time 5 12:31:10:930 7a7a2780 watchdog - thread 4, hb time 63268 12:31:10:930 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 5, hb time 62960 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 6, hb time 63134 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 7, hb time 63397 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 12:31:10:932 7a7a2780 OC v5, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
|
|
|
|
mettalmag
Legendary
Offline
Activity: 1084
Merit: 1003
≡v≡
|
|
February 25, 2017, 04:20:13 PM |
|
I have two computers each with two cards (R270 now getting 172 H/s). One runs windows 10 the other ubuntu 14. These have been running fine on 11.1
After upgrading to 12.1 I saw about an 11% bump in h/s.
Windows runs fine but the linux box is restarting claymore every 3 to 20 minutes. It is using crimson 15.12 driver (fglrx-15.302). There appears to be some issue with OpenCL. I tried "-i 1" and "asm 0" but no change. Is there anything else I can try?
12:31:10:922 7a7a2780 GPU 6 temp = 63, old fan speed = 80%, new fan speed = 80% 12:31:10:930 7a7a2780 GPU0 t=69C fan=60%, GPU1 t=63C fan=80% 12:31:10:930 7a7a2780 em hbt: 1, fm hbt: 24, 12:31:10:930 7a7a2780 watchdog - thread 0, hb time 270 12:31:10:930 7a7a2780 watchdog - thread 1, hb time 402 12:31:10:930 7a7a2780 watchdog - thread 2, hb time 133 12:31:10:930 7a7a2780 watchdog - thread 3, hb time 5 12:31:10:930 7a7a2780 watchdog - thread 4, hb time 63268 12:31:10:930 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 5, hb time 62960 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 6, hb time 63134 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 7, hb time 63397 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 12:31:10:932 7a7a2780 OC v5, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
try -ethi 8 and -wd 0
|
|
|
|
UnclWish
|
|
February 25, 2017, 05:33:06 PM |
|
mettalmag, -ethi option is for Ethereum miner, not for Zec. Maybe you mean -i option. But if enable maximum intensity without watchdog eneabled function miner just stops mining without restarting when hangs.
|
|
|
|
Corerj
Newbie
Offline
Activity: 23
Merit: 0
|
|
February 25, 2017, 06:25:07 PM |
|
-i 1 seems to solve the hang issue for me...
|
|
|
|
silentrunner
Newbie
Offline
Activity: 52
Merit: 0
|
|
February 25, 2017, 06:39:28 PM |
|
-i 1 seems to solve the hang issue for me...
It was already set to -i 1
|
|
|
|
UnclWish
|
|
February 25, 2017, 06:47:53 PM |
|
-i 1 seems to solve the hang issue for me...
For me -i 1 solves the problem too, but speed is less then -i 5 with v12.0. -i 2 gives the same speed as -i 5 in 12.0 but hangs often...
|
|
|
|
silentrunner
Newbie
Offline
Activity: 52
Merit: 0
|
|
February 25, 2017, 06:57:40 PM |
|
I have two computers each with two cards (R270 now getting 172 H/s). One runs windows 10 the other ubuntu 14. These have been running fine on 11.1
After upgrading to 12.1 I saw about an 11% bump in h/s.
Windows runs fine but the linux box is restarting claymore every 3 to 20 minutes. It is using crimson 15.12 driver (fglrx-15.302). There appears to be some issue with OpenCL. I tried "-i 1" and "asm 0" but no change. Is there anything else I can try?
12:31:10:922 7a7a2780 GPU 6 temp = 63, old fan speed = 80%, new fan speed = 80% 12:31:10:930 7a7a2780 GPU0 t=69C fan=60%, GPU1 t=63C fan=80% 12:31:10:930 7a7a2780 em hbt: 1, fm hbt: 24, 12:31:10:930 7a7a2780 watchdog - thread 0, hb time 270 12:31:10:930 7a7a2780 watchdog - thread 1, hb time 402 12:31:10:930 7a7a2780 watchdog - thread 2, hb time 133 12:31:10:930 7a7a2780 watchdog - thread 3, hb time 5 12:31:10:930 7a7a2780 watchdog - thread 4, hb time 63268 12:31:10:930 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 5, hb time 62960 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 6, hb time 63134 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 watchdog - thread 7, hb time 63397 12:31:10:931 7a7a2780 WATCHDOG: GPU 1 hangs in OpenCL call, exit 12:31:10:931 7a7a2780 OC v5, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 12:31:10:932 7a7a2780 OC v5, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
try -ethi 8 and -wd 0 turning off watchdog was not helpful. When the communication to the card stops, it just says to restart the miner. I could add -r 1 with a reboot.sh but I don't see a difference compared to just enabling the watchdog. ZEC - Total Speed: 172.517 H/s, Total Shares: 98, Rejected: 0, Time: 00:12 ZEC: GPU0 172.517 H/s, GPU1 0.000 H/s ZEC: 02/25/17-11:50:24 - SHARE FOUND - (GPU 0) ZEC: Share accepted (159 ms)! ZEC: 02/25/17-11:50:25 - SHARE FOUND - (GPU 0) ZEC: Share accepted (158 ms)! GPU0 t=74C fan=100%, GPU1 t=57C fan=80% ZEC: 02/25/17-11:50:41 - SHARE FOUND - (GPU 0) ZEC: Share accepted (158 ms)! ZEC: 02/25/17-11:50:43 - SHARE FOUND - (GPU 0) ZEC: Share accepted (159 ms)! ZEC: 02/25/17-11:50:46 - SHARE FOUND - (GPU 0) ZEC: Share accepted (159 ms)! ZEC: 02/25/17-11:50:58 - SHARE FOUND - (GPU 0) ZEC: Share accepted (159 ms)! GPU0 t=73C fan=100%, GPU1 t=51C fan=80% WATCHDOG: GPU 1 hangs in OpenCL call, you need to restart miner WATCHDOG: GPU 1 hangs in OpenCL call, you need to restart miner WATCHDOG: GPU 1 hangs in OpenCL call, you need to restart miner WATCHDOG: GPU 1 hangs in OpenCL call, you need to restart miner WATCHDOG: GPU error, you need to restart miner ZEC: 02/25/17-11:51:27 - SHARE FOUND - (GPU 0)
|
|
|
|
Corerj
Newbie
Offline
Activity: 23
Merit: 0
|
|
February 25, 2017, 07:51:32 PM |
|
-i 1 seems to solve the hang issue for me...
For me -i 1 solves the problem too, but speed is less then -i 5 with v12.0. -i 2 gives the same speed as -i 5 in 12.0 but hangs often... sadly after 3hours got a hang with -i 1 in 12.1....using 12.0 with -i 2 it is totally stable...i'm using agressive undervolting with my 7990s and 295...
|
|
|
|
mr.bRxXx
Newbie
Offline
Activity: 17
Merit: 0
|
|
February 25, 2017, 10:08:48 PM |
|
Using R9 280X with modded bios and some overclocked GPU. v12 works fine. Tested over 2-3 days working without issuies.
With v12.1 only 1st intensity is most stable. With any other intensity miner after about 10 min starts to show 0 hashrates and 0% GPU load. With 1st intensity miner works normal 20-30 min and then speed is 0 too. Miner restarts and so on.
Returning back to v12. It's stable for me.
Windows 10 Pro. Tryed 15.12 drivers, disable overclocking. Nothing helps. Any other miners works fine. PSU 60-70% load.
After some couple of days testing, i find 16.3.2 drivers performs better in terms of stability than 15.12, on all my 7970/280x/380/390 rigs... And it happens on v12.0 and v12.1 miner ... (got some strange instability with 280x rigs, and tried 16.3.2, everything works perfect so far). b.r. Alex
|
|
|
|
UnclWish
|
|
February 25, 2017, 10:43:02 PM |
|
Using R9 280X with modded bios and some overclocked GPU. v12 works fine. Tested over 2-3 days working without issuies.
With v12.1 only 1st intensity is most stable. With any other intensity miner after about 10 min starts to show 0 hashrates and 0% GPU load. With 1st intensity miner works normal 20-30 min and then speed is 0 too. Miner restarts and so on.
Returning back to v12. It's stable for me.
Windows 10 Pro. Tryed 15.12 drivers, disable overclocking. Nothing helps. Any other miners works fine. PSU 60-70% load.
After some couple of days testing, i find 16.3.2 drivers performs better in terms of stability than 15.12, on all my 7970/280x/380/390 rigs... And it happens on v12.0 and v12.1 miner ... (got some strange instability with 280x rigs, and tried 16.3.2, everything works perfect so far). b.r. Alex Thanks! I'll try 16.3.2. P.S. Are you tried other WHQL versions like 16.12.2, 16.9.2, 16.7.3?
|
|
|
|
Corerj
Newbie
Offline
Activity: 23
Merit: 0
|
|
February 25, 2017, 11:09:44 PM |
|
Using R9 280X with modded bios and some overclocked GPU. v12 works fine. Tested over 2-3 days working without issuies.
With v12.1 only 1st intensity is most stable. With any other intensity miner after about 10 min starts to show 0 hashrates and 0% GPU load. With 1st intensity miner works normal 20-30 min and then speed is 0 too. Miner restarts and so on.
Returning back to v12. It's stable for me.
Windows 10 Pro. Tryed 15.12 drivers, disable overclocking. Nothing helps. Any other miners works fine. PSU 60-70% load.
After some couple of days testing, i find 16.3.2 drivers performs better in terms of stability than 15.12, on all my 7970/280x/380/390 rigs... And it happens on v12.0 and v12.1 miner ... (got some strange instability with 280x rigs, and tried 16.3.2, everything works perfect so far). b.r. Alex Thanks! I'll try 16.3.2. P.S. Are you tried other WHQL versions like 16.12.2, 16.9.2, 16.7.3? im using 16.10.2, and its fine, tried 16.12.2 and no success....
|
|
|
|
UnclWish
|
|
February 25, 2017, 11:25:20 PM Last edit: February 26, 2017, 12:29:25 AM by UnclWish |
|
Using R9 280X with modded bios and some overclocked GPU. v12 works fine. Tested over 2-3 days working without issuies.
With v12.1 only 1st intensity is most stable. With any other intensity miner after about 10 min starts to show 0 hashrates and 0% GPU load. With 1st intensity miner works normal 20-30 min and then speed is 0 too. Miner restarts and so on.
Returning back to v12. It's stable for me.
Windows 10 Pro. Tryed 15.12 drivers, disable overclocking. Nothing helps. Any other miners works fine. PSU 60-70% load.
After some couple of days testing, i find 16.3.2 drivers performs better in terms of stability than 15.12, on all my 7970/280x/380/390 rigs... And it happens on v12.0 and v12.1 miner ... (got some strange instability with 280x rigs, and tried 16.3.2, everything works perfect so far). b.r. Alex Thanks! I'll try 16.3.2. P.S. Are you tried other WHQL versions like 16.12.2, 16.9.2, 16.7.3? im using 16.10.2, and its fine, tried 16.12.2 and no success.... Just installed 16.3.2 testing 12.1 in progress... On 16.10.2 7970/280x/380/390 rigs works without hangs? EDIT: After 13 minutes of mining on 16.3.2 + v12.1 with maximum intensity GPU0 hangs (280X). Try to lowing intesity by one step. Interesting that 270X works stable on any driver and max.intensity with 12.1... EDIT2: Intensity 4 couses hangs 280X so as 5... Trying 3... EDIT3: Intensity 3 also hangs 280X... Trying 2... I have feeling that low intensity hangs more quickly... 5 - 13 min. 4 and 3 - less than 5 min. Or it's random... EDIT4: Even Intensity 1 and 2 causes 280X to hang... I think it's no a driver problem...
|
|
|
|
cohnhead
|
|
February 25, 2017, 11:50:21 PM |
|
anyone have good settings for and msi twin frozer rx 470 8gb windows 7
|
|
|
|
UnclWish
|
|
February 26, 2017, 12:42:42 AM Last edit: February 26, 2017, 01:07:11 AM by UnclWish |
|
Finally I find it! A know the problem why GPU's hangs on 12.1! Maybe not all GPU's but on my 280X and 270X it so...
I just read the logs.. and...
GPU's hangs if used option -ttli and temperature of GPU achieves this value. After miner must to low intensity for cooldown GPU. And 12.1 on this hangs GPU at all. In logs appears string "Gpu # -ttli apply delta 1" and after that GPU hangs till restart.
To verify this I choose low -ttli for 270X and it hangs at chosen temperature!
Why my 280X hangs all time and 270X is not? Because 280X is hotter and more quickly achieves ttli temperature... And when I change intensity GPU allready was hot and therefore reach ttli temperature quickly... I'm scared to run miner without -ttli... Will set tstop at the moment...
Claymore, can you check this and correct?
|
|
|
|
Corerj
Newbie
Offline
Activity: 23
Merit: 0
|
|
February 26, 2017, 02:19:35 AM |
|
Finally I find it! A know the problem why GPU's hangs on 12.1! Maybe not all GPU's but on my 280X and 270X it so...
I just read the logs.. and...
GPU's hangs if used option -ttli and temperature of GPU achieves this value. After miner must to low intensity for cooldown GPU. And 12.1 on this hangs GPU at all. In logs appears string "Gpu # -ttli apply delta 1" and after that GPU hangs till restart.
To verify this I choose low -ttli for 270X and it hangs at chosen temperature!
Why my 280X hangs all time and 270X is not? Because 280X is hotter and more quickly achieves ttli temperature... And when I change intensity GPU allready was hot and therefore reach ttli temperature quickly... I'm scared to run miner without -ttli... Will set tstop at the moment...
Claymore, can you check this and correct?
i'll try here...indeed i use -ttli too
|
|
|
|
UnclWish
|
|
February 26, 2017, 02:27:10 AM |
|
Finally I find it! A know the problem why GPU's hangs on 12.1! Maybe not all GPU's but on my 280X and 270X it so...
I just read the logs.. and...
GPU's hangs if used option -ttli and temperature of GPU achieves this value. After miner must to low intensity for cooldown GPU. And 12.1 on this hangs GPU at all. In logs appears string "Gpu # -ttli apply delta 1" and after that GPU hangs till restart.
To verify this I choose low -ttli for 270X and it hangs at chosen temperature!
Why my 280X hangs all time and 270X is not? Because 280X is hotter and more quickly achieves ttli temperature... And when I change intensity GPU allready was hot and therefore reach ttli temperature quickly... I'm scared to run miner without -ttli... Will set tstop at the moment...
Claymore, can you check this and correct?
i'll try here...indeed i use -ttli too I am allready installed back latest 17.2.1 and miner 12.1 runs without any issues or GPU hangs all this time. I was right, I just removed ttli option and add tstop until Claymore fix this.
|
|
|
|
grizscom
|
|
February 26, 2017, 04:41:24 AM |
|
@ Claymore: Maybe I had a bug at v12.1 .
I noticed sometimes rigs go into disk operations and freezes. Used primarily ubuntu 14.04 .
|
|
|
|
|