Author

Topic: Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux) - page 146. (Read 3839201 times)

legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
anyone notice that 390x show 500 hs for the first 30 sec then it steadily drops.  12.1.  Is that potential or just that the rounds havent avg out.  Most of time it started way short and worked its way up not other way around.. Just wondering


Edit for what its worth it does it on all cards.  even 290x shows 450 h/s

Code:
ZEC - Total Speed: 2793.691 H/s, Total Shares: 1, Rejected: 0, Time: 00:00
08:46:22:493 1894 ZEC: GPU0 465.998 H/s, GPU1 477.434 H/s, GPU2 488.427 H/s, GPU3 398.163 H/s, GPU4 428.854 H/s, GPU5 511.049 H/s
GPU #0: Hawaii
08:46:22:306 1894 GPU #1: Hawaii
08:46:22:337 1894 GPU #2: Hawaii
08:46:22:399 1894 GPU #3: Hawaii
08:46:22:415 1894 GPU #4: Hawaii
08:46:22:431 1894 GPU #5: Hawaii

BR

Actually Claymore specifically states that it takes 3000 rounds (his words) to get an accurate hash rate. I believe the miner states that in the log, when the miner first starts.

Yes 3000 rounds. But usually it would start a bit short then work it's way up. Never in all the versions have I seen it start high and work down. Just thought maybe we had some decent upside left. Thanks FFI2013 for the confirmation.

BR
newbie
Activity: 12
Merit: 0
Can someone give me link to 15.12 drivers, cant find them online. AMD page is super not user friendly when searching for old drivers. thx

Also what drivers give best results for R9 390s?
sudo apt install -t jessie-backports fglrx-driver=1:15.12-2~bpo8+3

E: The value 'jessie-backports' is invalid for APT::Default-Release as such a release is not available in the sources
??
newbie
Activity: 68
Merit: 0
Now that we have a faster CM version, Zcash is going down the drain Huh

Oh man, i hope it stops at 0.20 at least. Anything below, and it will make it unprofitable, and it's really pitty cause it has the potential to be a key player.
newbie
Activity: 46
Merit: 0
Can someone give me link to 15.12 drivers, cant find them online. AMD page is super not user friendly when searching for old drivers. thx

Also what drivers give best results for R9 390s?

http://www.guru3d.com/files-details/amd-radeon-software-crimson-15-12-driver-download.html
hero member
Activity: 630
Merit: 502
Can someone give me link to 15.12 drivers, cant find them online. AMD page is super not user friendly when searching for old drivers. thx

Also what drivers give best results for R9 390s?
sudo apt install -t jessie-backports fglrx-driver=1:15.12-2~bpo8+3
newbie
Activity: 24
Merit: 0
Can someone give me link to 15.12 drivers, cant find them online. AMD page is super not user friendly when searching for old drivers. thx

Also what drivers give best results for R9 390s?
newbie
Activity: 54
Merit: 0
Sadly v12 and v12.1 are too unstable here (already tried to low intensity)...rig with 3x 7990 and 1x R9 295x2, under win10 with cat 15.12...other versions and optiminer run fine...
Can I mine dash with claymore? how ? I have 7990 and 280x some help will be appreciate!!!

No Dash. That is minable with ASIC.
full member
Activity: 150
Merit: 100
anyone notice that 390x show 500 hs for the first 30 sec then it steadily drops.  12.1.  Is that potential or just that the rounds havent avg out.  Most of time it started way short and worked its way up not other way around.. Just wondering


Edit for what its worth it does it on all cards.  even 290x shows 450 h/s

Code:
ZEC - Total Speed: 2793.691 H/s, Total Shares: 1, Rejected: 0, Time: 00:00
08:46:22:493 1894 ZEC: GPU0 465.998 H/s, GPU1 477.434 H/s, GPU2 488.427 H/s, GPU3 398.163 H/s, GPU4 428.854 H/s, GPU5 511.049 H/s
GPU #0: Hawaii
08:46:22:306 1894 GPU #1: Hawaii
08:46:22:337 1894 GPU #2: Hawaii
08:46:22:399 1894 GPU #3: Hawaii
08:46:22:415 1894 GPU #4: Hawaii
08:46:22:431 1894 GPU #5: Hawaii

BR

Actually Claymore specifically states that it takes 3000 rounds (his words) to get an accurate hash rate. I believe the miner states that in the log, when the miner first starts.
hero member
Activity: 906
Merit: 507
anyone notice that 390x show 500 hs for the first 30 sec then it steadily drops.  12.1.  Is that potential or just that the rounds havent avg out.  Most of time it started way short and worked its way up not other way around.. Just wondering


Edit for what its worth it does it on all cards.  even 290x shows 450 h/s

Code:
ZEC - Total Speed: 2793.691 H/s, Total Shares: 1, Rejected: 0, Time: 00:00
08:46:22:493 1894 ZEC: GPU0 465.998 H/s, GPU1 477.434 H/s, GPU2 488.427 H/s, GPU3 398.163 H/s, GPU4 428.854 H/s, GPU5 511.049 H/s
GPU #0: Hawaii
08:46:22:306 1894 GPU #1: Hawaii
08:46:22:337 1894 GPU #2: Hawaii
08:46:22:399 1894 GPU #3: Hawaii
08:46:22:415 1894 GPU #4: Hawaii
08:46:22:431 1894 GPU #5: Hawaii

BR
yes it does it to my 390 and 290 more on the 390 it starts out higher than drop down
full member
Activity: 150
Merit: 100
Since V12 it seems to run for 3+ hours and then the computer starts rebooting in 5-15 cycles... and then it ran for 45 minutes and then for over an hour again... weirdness  

Further down this road and the "stability" seemed to get worse.  However, in the end I can't say that it was mainly attributed to v12+ or something else.  I ended up getting several blue screens and then finally doing a reset.  I'm back to an apparent "stable" condition but it has only been an hour.  

Also... I'm running a 3-year old 850 Watt power supply and measuring up to 815 watts with my kill-a-watt at the wall.  That's with 4x 7950's in the rig.  I measure around 100 Watts before the miner turns on so I guess that would average around 175 watts per card.  This is without any undervolting.  I tried undervolting along with this whole stability troubleshooting process and I wasn't successful at all.  I may try again since the reset of Windows 10 OS seems to have made things more stable.

So what does the 850 watt power supply mean anyway?  Should I be able to pull up to 850 at the wall and be fine?  I read elsewhere in this thread (I think) that you could pull upwards of what your power supply is rated for and this gets into the realm of efficiency.  Regardless... I'm jonesing for a new PSU so that I'm not so near the apparent threshold.



The PSU rating is for the DC side (inside the system), not the AC side (wall). So, if the PSU is 90% efficient, it should max out at (100/90) * 850 = 944 watts at the wall.



I'm back to the random restarts Sad  I'm kind of thinking it's the power supply but if I still have over 100 watts overhead I'd think it would be okay.  But that's still a lot of work on a 3-4 year old power supply.

If you have the option, you could move a card off that rig and see if stability returns. Just a thought.

I removed a card from the system today and it crashed with 12.1.  I'm going all the way back to 9.2 now to see how it does.  I'm still thinking this is a power supply issue.

9.2 was the last version I was on before I went up to 12.1.  I was also running 3 video cards for the majority of the time on 9.2 but I did run 4 cards with no issues for nearly a week before I started having reboot issues which is when I started looking to see if there were newer versions of the miner that might 'help'.  Foolish of me... this is looking more and more like a power supply problem.  Now I'm seeing people say they try to stay around 70% of what' their power supply is rated.  With 3 cards on 12.1 I was seeing around 560 Watts at the wall which is close to that 70% range some others were saying they spec for.  Hoping I can get a 1200 Watt gold PSU in a few months and then be back up to full speed.  ugh patience is not my strength ><

Edit:  crossing my fingers this will solve some problems:   I just ordered this thing:  http://www.parallelminer.com/product/gpu-mining-power-supply-kit-hp-1200-watt-80-gold/   

Perhaps you've already done this, but you could try optiminer v1.6.2, which has been a rock, for me, just to eliminate the miner as the possible problem.
sr. member
Activity: 273
Merit: 250
Anyone else notice that v12/12.1 is reporting about a 5% higher hashrate than pool(flypool) for polaris based cards?

For example a 470 is reporting 280H/s miner side, and 260H/s poolside average. With 2% fee should be reporting ~275H/s.

Can anyone else on flypool with polaris cards confirm...want to see if its just me or a pool related issue.
Put the miner on local proxy and see what it shows about shares/speed.

what local proxy?
legendary
Activity: 2296
Merit: 1031
Since V12 it seems to run for 3+ hours and then the computer starts rebooting in 5-15 cycles... and then it ran for 45 minutes and then for over an hour again... weirdness  

Further down this road and the "stability" seemed to get worse.  However, in the end I can't say that it was mainly attributed to v12+ or something else.  I ended up getting several blue screens and then finally doing a reset.  I'm back to an apparent "stable" condition but it has only been an hour.  

Also... I'm running a 3-year old 850 Watt power supply and measuring up to 815 watts with my kill-a-watt at the wall.  That's with 4x 7950's in the rig.  I measure around 100 Watts before the miner turns on so I guess that would average around 175 watts per card.  This is without any undervolting.  I tried undervolting along with this whole stability troubleshooting process and I wasn't successful at all.  I may try again since the reset of Windows 10 OS seems to have made things more stable.

So what does the 850 watt power supply mean anyway?  Should I be able to pull up to 850 at the wall and be fine?  I read elsewhere in this thread (I think) that you could pull upwards of what your power supply is rated for and this gets into the realm of efficiency.  Regardless... I'm jonesing for a new PSU so that I'm not so near the apparent threshold.



The PSU rating is for the DC side (inside the system), not the AC side (wall). So, if the PSU is 90% efficient, it should max out at (100/90) * 850 = 944 watts at the wall.



I'm back to the random restarts Sad  I'm kind of thinking it's the power supply but if I still have over 100 watts overhead I'd think it would be okay.  But that's still a lot of work on a 3-4 year old power supply.

If you have the option, you could move a card off that rig and see if stability returns. Just a thought.

I removed a card from the system today and it crashed with 12.1.  I'm going all the way back to 9.2 now to see how it does.  I'm still thinking this is a power supply issue.

9.2 was the last version I was on before I went up to 12.1.  I was also running 3 video cards for the majority of the time on 9.2 but I did run 4 cards with no issues for nearly a week before I started having reboot issues which is when I started looking to see if there were newer versions of the miner that might 'help'.  Foolish of me... this is looking more and more like a power supply problem.  Now I'm seeing people say they try to stay around 70% of what' their power supply is rated.  With 3 cards on 12.1 I was seeing around 560 Watts at the wall which is close to that 70% range some others were saying they spec for.  Hoping I can get a 1200 Watt gold PSU in a few months and then be back up to full speed.  ugh patience is not my strength ><

Edit:  crossing my fingers this will solve some problems:   I just ordered this thing:  http://www.parallelminer.com/product/gpu-mining-power-supply-kit-hp-1200-watt-80-gold/   
sr. member
Activity: 652
Merit: 266
Anyone else notice that v12/12.1 is reporting about a 5% higher hashrate than pool(flypool) for polaris based cards?

For example a 470 is reporting 280H/s miner side, and 260H/s poolside average. With 2% fee should be reporting ~275H/s.

Can anyone else on flypool with polaris cards confirm...want to see if its just me or a pool related issue.
Put the miner on local proxy and see what it shows about shares/speed.
newbie
Activity: 23
Merit: 0
Sadly v12 and v12.1 are too unstable here (already tried to low intensity)...rig with 3x 7990 and 1x R9 295x2, under win10 with cat 15.12...other versions and optiminer run fine...
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
Anyone else notice that v12/12.1 is reporting about a 5% higher hashrate than pool(flypool) for polaris based cards?

For example a 470 is reporting 280H/s miner side, and 260H/s poolside average. With 2% fee should be reporting ~275H/s.

Can anyone else on flypool with polaris cards confirm...want to see if its just me or a pool related issue.
[/quote1.8 kH/s   1.6 kH/s 480s ref.
legendary
Activity: 2174
Merit: 1401
Anyone else notice that v12/12.1 is reporting about a 5% higher hashrate than pool(flypool) for polaris based cards?

For example a 470 is reporting 280H/s miner side, and 260H/s poolside average. With 2% fee should be reporting ~275H/s.

Can anyone else on flypool with polaris cards confirm...want to see if its just me or a pool related issue.
sr. member
Activity: 652
Merit: 266
newbie
Activity: 3
Merit: 0
My videocards are rejected:

Quote
   
./zecminer64: /usr/local/lib/libOpenCL.so.1: no version information available (required by ./zecminer64)
./zecminer64: /lib64/libcrypto.so.1.0.0: no version information available (required by ./zecminer64)
./zecminer64: /lib64/libssl.so.1.0.0: no version information available (required by ./zecminer64)

ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º           Claymore's ZCash AMD GPU Miner v11.1 Beta            º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ

ZEC: 1 pool is specified
Main ZCash pool is zec.suprnova.cc:2242
AMD OpenCL platform not found
No AMD OPENCLGPUs found, exit
I am using the open source drivers with 2 7950 cards and I have Opencl Support. Please, make the miner so, that  Platform Name: Clover and Platform Vendor: Mesa are accepted by your miner too. Here is the full output of clinfo:
Quote
clinfo: /usr/local/lib/libOpenCL.so.1: no version information available (required by clinfo)
clinfo: /usr/local/lib/libOpenCL.so.1: no version information available (required by clinfo)
Number of platforms:                             1
  Platform Profile:                              FULL_PROFILE
  Platform Version:                              OpenCL 1.1 Mesa 17.1.0-devel (git-0514b0b)
  Platform Name:                                 Clover
  Platform Vendor:                               Mesa
  Platform Extensions:                           cl_khr_icd


  Platform Name:                                 Clover
Number of devices:                               2
  Device Type:                                   CL_DEVICE_TYPE_GPU
  Vendor ID:                                     1002h
  Max compute units:                             28
  Max work items dimensions:                     3
    Max work items[0]:                           256
    Max work items[1]:                           256
    Max work items[2]:                           256
  Max work group size:                           256
  Preferred vector width char:                   16
  Preferred vector width short:                  8
  Preferred vector width int:                    4
  Preferred vector width long:                   2
  Preferred vector width float:                  4
  Preferred vector width double:                 2
  Native vector width char:                      16
  Native vector width short:                     8
  Native vector width int:                       4
  Native vector width long:                      2
  Native vector width float:                     4
  Native vector width double:                    2
  Max clock frequency:                           925Mhz
  Address bits:                                  64
  Max memory allocation:                         2254857830
  Image support:                                 No
  Max size of kernel argument:                   1024
  Alignment (bits) of base address:              1024
  Minimum alignment (bytes) for any datatype:    128
  Single precision floating point capability
    Denorms:                                     No
    Quiet NaNs:                                  Yes
    Round to nearest even:                       Yes
    Round to zero:                               No
    Round to +ve and infinity:                   No
    IEEE754-2008 fused multiply-add:             No
  Cache type:                                    None
  Cache line size:                               0
  Cache size:                                    0
  Global memory size:                            3221225472
  Constant buffer size:                          2147483647
  Max number of constant args:                   16
  Local memory type:                             Scratchpad
  Local memory size:                             32768
  Kernel Preferred work group size multiple:     64
  Error correction support:                      0
  Unified memory for Host and Device:            1
  Profiling timer resolution:                    0
  Device endianess:                              Little
  Available:                                     Yes
  Compiler available:                            Yes
  Execution capabilities:                               
    Execute OpenCL kernels:                      Yes
    Execute native function:                     No
  Queue on Host properties:                             
    Out-of-Order:                                No
    Profiling :                                  Yes
  Platform ID:                                   0x7f0ede9a1a00
  Name:                                          AMD TAHITI (DRM 2.43.0 / 4.4.38, LLVM 3.9.1)
  Vendor:                                        AMD
  Device OpenCL C version:                       OpenCL C 1.1
  Driver version:                                17.1.0-devel
  Profile:                                       FULL_PROFILE
  Version:                                       OpenCL 1.1 Mesa 17.1.0-devel (git-0514b0b)
  Extensions:                                    cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_fp64


  Device Type:                                   CL_DEVICE_TYPE_GPU
  Vendor ID:                                     1002h
  Max compute units:                             28
  Max work items dimensions:                     3
    Max work items[0]:                           256
    Max work items[1]:                           256
    Max work items[2]:                           256
  Max work group size:                           256
  Preferred vector width char:                   16
  Preferred vector width short:                  8
  Preferred vector width int:                    4
  Preferred vector width long:                   2
  Preferred vector width float:                  4
  Preferred vector width double:                 2
  Native vector width char:                      16
  Native vector width short:                     8
  Native vector width int:                       4
  Native vector width long:                      2
  Native vector width float:                     4
  Native vector width double:                    2
  Max clock frequency:                           925Mhz
  Address bits:                                  64
  Max memory allocation:                         2254857830
  Image support:                                 No
  Max size of kernel argument:                   1024
  Alignment (bits) of base address:              1024
  Minimum alignment (bytes) for any datatype:    128
  Single precision floating point capability
    Denorms:                                     No
    Quiet NaNs:                                  Yes
    Round to nearest even:                       Yes
    Round to zero:                               No
    Round to +ve and infinity:                   No
    IEEE754-2008 fused multiply-add:             No
  Cache type:                                    None
  Cache line size:                               0
  Cache size:                                    0
  Global memory size:                            3221225472
  Constant buffer size:                          2147483647
  Max number of constant args:                   16
  Local memory type:                             Scratchpad
  Local memory size:                             32768
  Kernel Preferred work group size multiple:     64
  Error correction support:                      0
  Unified memory for Host and Device:            1
  Profiling timer resolution:                    0
  Device endianess:                              Little
  Available:                                     Yes
  Compiler available:                            Yes
  Execution capabilities:                               
    Execute OpenCL kernels:                      Yes
    Execute native function:                     No
  Queue on Host properties:                             
    Out-of-Order:                                No
    Profiling :                                  Yes
  Platform ID:                                   0x7f0ede9a1a00
  Name:                                          AMD TAHITI (DRM 2.43.0 / 4.4.38, LLVM 3.9.1)
  Vendor:                                        AMD
  Device OpenCL C version:                       OpenCL C 1.1
  Driver version:                                17.1.0-devel
  Profile:                                       FULL_PROFILE
  Version:                                       OpenCL 1.1 Mesa 17.1.0-devel (git-0514b0b)
  Extensions:                                    cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_fp64

legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
anyone notice that 390x show 500 hs for the first 30 sec then it steadily drops.  12.1.  Is that potential or just that the rounds havent avg out.  Most of time it started way short and worked its way up not other way around.. Just wondering


Edit for what its worth it does it on all cards.  even 290x shows 450 h/s

Code:
ZEC - Total Speed: 2793.691 H/s, Total Shares: 1, Rejected: 0, Time: 00:00
08:46:22:493 1894 ZEC: GPU0 465.998 H/s, GPU1 477.434 H/s, GPU2 488.427 H/s, GPU3 398.163 H/s, GPU4 428.854 H/s, GPU5 511.049 H/s
GPU #0: Hawaii
08:46:22:306 1894 GPU #1: Hawaii
08:46:22:337 1894 GPU #2: Hawaii
08:46:22:399 1894 GPU #3: Hawaii
08:46:22:415 1894 GPU #4: Hawaii
08:46:22:431 1894 GPU #5: Hawaii

BR
newbie
Activity: 64
Merit: 0
Since V12 it seems to run for 3+ hours and then the computer starts rebooting in 5-15 cycles... and then it ran for 45 minutes and then for over an hour again... weirdness 

Further down this road and the "stability" seemed to get worse.  However, in the end I can't say that it was mainly attributed to v12+ or something else.  I ended up getting several blue screens and then finally doing a reset.  I'm back to an apparent "stable" condition but it has only been an hour. 

Also... I'm running a 3-year old 850 Watt power supply and measuring up to 815 watts with my kill-a-watt at the wall.  That's with 4x 7950's in the rig.  I measure around 100 Watts before the miner turns on so I guess that would average around 175 watts per card.  This is without any undervolting.  I tried undervolting along with this whole stability troubleshooting process and I wasn't successful at all.  I may try again since the reset of Windows 10 OS seems to have made things more stable.

So what does the 850 watt power supply mean anyway?  Should I be able to pull up to 850 at the wall and be fine?  I read elsewhere in this thread (I think) that you could pull upwards of what your power supply is rated for and this gets into the realm of efficiency.  Regardless... I'm jonesing for a new PSU so that I'm not so near the apparent threshold.



The PSU rating is for the DC side (inside the system), not the AC side (wall). So, if the PSU is 90% efficient, it should max out at (100/90) * 850 = 944 watts at the wall.



I'm back to the random restarts Sad  I'm kind of thinking it's the power supply but if I still have over 100 watts overhead I'd think it would be okay.  But that's still a lot of work on a 3-4 year old power supply.

You need to reduce the frequency. The peak power is quite high. There are spikes.
Best is to mine @60-70 % of PSU power. There is max eff. Also ZEC mining demands stable PSU, there are power spikes demanding large 12V output electrolyths

I run at about 70% of the power limit.
Jump to: