Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0018
by
Bibi187
on 10/08/2017, 16:16:56 UTC
sure mate here it is http://www.linuxfromscratch.org/blfs/view/7.4/postlfs/openssl.html

Hello mate,

do you mind sharing which website you have downloaded  and copied that file (bn.h) in detail (if possible with steps, may help other users too).

Thanks Smiley

One Page back...I sorted the issue by downloading openssl 1.0.1 from their website and copying the "bn.h" after install to \usr\local\include\openssl

It then builds without issue. Hope it helps Smiley


hi guys i try to build.sh this https://github.com/krnlx/ccminer-skunk-krnlx  on terminal but i cant manage to make this ccminer work
can u help me how to use this in nvoc thanks

God Bless us All



Thanks both of you, I've managed to build it too, if any one interested happy to share step by step detail Smiley

How much do u get with this new release on nvOC ?
1070 -i 25 / OC : 120 / MC : -500 / PL : 150 : / TL : 70 ( Autotemp ON, watchdog OFF ) 30.5mh/s

I actually mining on https://pool.mn/sigt/ ( 0.99% fee ) more detailled stats vs no sense stats on suprnova pool ...

On my 8x GPU rig, one of my card us lower them all the other one by 2mh/s, any idea where that come from ?

Last question, i setup OC: 120 / MC: -500 on all GPU, but i dont get same stats for the nvclock ... Why ?

 Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:0]): nvclock=2025, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1
  Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:1]): nvclock=2025, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1
  Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:2]): nvclock=1885, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1
  Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:3]): nvclock=1885, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1
  Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:4]): nvclock=1999, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1
  Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:5]): nvclock=1911, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1
  Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:6]): nvclock=2037, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1
  Attribute 'GPUCurrentClockFreqsString' (m1-desktop:0[gpu:7]): nvclock=1936, nvclockmin=215, nvclockmax=2100, nvclockeditable=1, memclock=3553, memclockmin=3552,
  memclockmax=3552, memclockeditable=1, memTransferRate=7106, memTransferRatemin=7104, memTransferRatemax=7104, memTransferRateeditable=1

As u can see, that only happen on nvclock the memclock is strictly ident

TBH, I'm not sure about 1070.

You can follow this post to get more accurate info.

https://bitcointalk.org/index.php?topic=2070862.180

but I can clearly see that there is 2-3 MH increase per card (reports from other users too) with recent update.

you can increase your cc a little (i pushed it till 150-170 on my 1060) and reduce mc even bit more, PL I will always test till 70% or with my 1060 even less depending on card.

Well, it varies card to card, because not every card is same (even you bought same model), also memory may differ between cards (from my analysis Samsung > Hynix > Micron).

Hope it helps...


Nvclock is the freq rate from GPU not memory Wink so we dont care about memory builder i decrease the usage of them Wink
The variance from nvclock, i assume is from the power variation