Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[grendel25]

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.

[zzzzzzzzzz]

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.

[nesic1]

how much 7950 give and what are the clocks? i get around 261H/s

on mine gigabyte at 1190/1497 +10% power doing around 308 h/s.

i'm at 261.5H@925/1201 @920mV

[grendel25]

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   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.

[xuanmichael]

  stock 6 Vga HIS 8G rx480 core 1288/mem 2000 ,setting undervolt 1000mV ; v12: 293H/s @wall 1050w but v12.1: 302H/s @wall 1200w

[lonelyworks]

Claymore, it seems that there's little bug in your program... When I mine with all my 7 rigs, sometime the miner just cannot connect. It says connected to the server and then timeout for 20 seconds. In the version 11 it wasn't doing this and its doing this on all my 7 rigs. After a little while its connecting and mining, but its just that sometime when my rigs reconnect it can take up to 30 minutes.

Please fix this

[zzzzzzzzzz]

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   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.

[xxDiggerxx]

W.10, 15,12 6x480(on stok)
as it turns out this performance on both 4, 5 and 6 of the GPU?
http://yadi.sk/i/IGF_RD5t3EKcgo

[envaluecrypto]

Stability issues with windows... Better on linux?

[Demarsac]

Stability issues with windows... Better on linux?

I am using linux since v.12 with modded bioses, RX 480's
Rock solid since then, i don't even remember when i did a restart last time

[Farstdury]

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   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.

[Dr_Victor]

With v.12.1 I have 'Memory can not be read' error. With 12 it is ok. 6*380x/win 8.1/15.12. Any suggestions, please?

[vapourminer]

With v.12.1 I have 'Memory can not be read' error. With 12 it is ok. 6*380x/win 8.1/15.12. Any suggestions, please?

is this message from the miner or windows? what intensity? how much system ram? swap file size? psu brand and wattage? any bios tweaks on the cards(s). what are the cards clocks (core/mem)?

[AzzAz]

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   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

[Jukagid]

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   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.

[d57heinz]

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

[ilievdh]

My videocards are rejected:

   
./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:

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

[laik2]

You won't get any working setup using Mesa-LLVM OpenCL implementation
Use amdgpu-pro opencl/libopencl

My videocards are rejected:

   
./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:

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

[jstefanop]

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.

[sorry2xs]

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.