<<  >> (p.337)
    Author Topic: [ mining os ] nvoc  (Read 418569 times)

    • Muhammadaffandi10
    Member
    **
    Offline Offline

    Activity: 126
    Merit: 10


    View Profile
    August 05, 2018, 02:40:06 PM
     #6721
    Quote from: newmz on April 15, 2017, 11:21:27 AM
    This is all very interesting to me because I currently use Windows 8.1 for my Nvidia Rig but in the past I have mined with my AMD rigs using EthOS and found it much more stable and reliable, and using much lower resources, etc - so a Linux solution for an Nvidia rig sounds great. I was considering trying the PiMP Nvidia version but when I tried that for my AMD rigs it confused the hell out of me.

    Anyway, I have one big question because it doesn't seem clear to me from the small amount of info in this thread whether it will suit my rig. Reason being, my rig is currently 2 x  Gigabyte  gtx1070 G1 Gaming cards and 2 x Galax gtx 1060 6GB cards.

    It seems from what I read above that when you set cc & mc overclock and powerlimit - this is one setting to apply to all cards on the rig. This is obviously suitable for the typical situation where people commonly use  multiple instances of 1 type of card on a rig, which I understand - people choose a GPU, buy however many of them and populate the rig with them.

    What about a situation like mine though, where I have 2 of one GPU and 2 of another, so I need to be able to specify different OC and powerlimits for the different cards.

    Currently in Windows 8.1 I just use MSI afterburner and set each card individually, so for example I mine ZEC and the 1070s are powerlimited to around 68%, core OC to +70 and mem OC to +700, while the 1060s are powerlimited to about 75%, core OC to +50 and me OC to +500. Using EWBF this is giving me approximately 1400sol/s using 500W at the wall.

    Since the powerlimit in Linux seems to be set in watts rather than percent, one setting in a percentage (70% would probably work) but I would need to be able to set the 1070s to around 125W and the 160s to around 85W. The CC could all conceivably be set to +60 and MC to +500 or +600 but is there a way to set powerlimits individually for each card?
    yes but convincing the bitcoinner that using windowns depends

  • papampi_2
    Jr. Member
    *
    Offline Offline

    Activity: 112
    Merit: 3

    Linux Forever... Resistance is futile!!!


    View Profile WWW
    August 05, 2018, 04:47:52 PM
     #6722
    Quote from: Muhammadaffandi10 on August 05, 2018, 02:40:06 PM
    Quote from: newmz on April 15, 2017, 11:21:27 AM
    This is all very interesting to me because I currently use Windows 8.1 for my Nvidia Rig but in the past I have mined with my AMD rigs using EthOS and found it much more stable and reliable, and using much lower resources, etc - so a Linux solution for an Nvidia rig sounds great. I was considering trying the PiMP Nvidia version but when I tried that for my AMD rigs it confused the hell out of me.

    Anyway, I have one big question because it doesn't seem clear to me from the small amount of info in this thread whether it will suit my rig. Reason being, my rig is currently 2 x  Gigabyte  gtx1070 G1 Gaming cards and 2 x Galax gtx 1060 6GB cards.

    It seems from what I read above that when you set cc & mc overclock and powerlimit - this is one setting to apply to all cards on the rig. This is obviously suitable for the typical situation where people commonly use  multiple instances of 1 type of card on a rig, which I understand - people choose a GPU, buy however many of them and populate the rig with them.

    What about a situation like mine though, where I have 2 of one GPU and 2 of another, so I need to be able to specify different OC and powerlimits for the different cards.

    Currently in Windows 8.1 I just use MSI afterburner and set each card individually, so for example I mine ZEC and the 1070s are powerlimited to around 68%, core OC to +70 and mem OC to +700, while the 1060s are powerlimited to about 75%, core OC to +50 and me OC to +500. Using EWBF this is giving me approximately 1400sol/s using 500W at the wall.

    Since the powerlimit in Linux seems to be set in watts rather than percent, one setting in a percentage (70% would probably work) but I would need to be able to set the 1070s to around 125W and the 160s to around 85W. The CC could all conceivably be set to +60 and MC to +500 or +600 but is there a way to set powerlimits individually for each card?
    yes but convincing the bitcoinner that using windowns depends

    you are replying to thread from april 2017 ?
    https://github.com/papampi/nvOC_by_fullzero_Community_Release

  • gs777
    Member
    **
    Offline Offline

    Activity: 118
    Merit: 10


    View Profile
    August 05, 2018, 06:42:29 PM
     #6723
    Looks like somebody hacked his account and using random text generator

  • fk2
    Jr. Member
    *
    Offline Offline

    Activity: 67
    Merit: 2


    View Profile
    August 06, 2018, 11:12:57 AM
    Last edit: August 06, 2018, 01:48:28 PM by fk2
     #6724
    @papampi: tyvm for quick support on watchdog! already pulled latest version but stucked on cuda update.

    I did an update following this guide: https://wagonhelm.github.io/articles/2018-02/Installing-Cuda-9.0-Toolkit-Ubuntu-16.04
    I installed 9.2 and skipped cudNN. I did the last two steps udating bash file and terminal.

    Code:
    m1@m1-desktop:~$ cdusr/local/cuda
    m1@m1-desktop:/usr/local/cuda$ cat version.txt
    CUDA Version 9.2.88

    I recompiled KTccminer plus KTccminer-cryptonight, unfortunately not everything was saved properly, the first KTccminer lines are missing but it looked good:
    Code:
    ptxas info    : Used 157 registers, 256 bytes smem, 344 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa2_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 132 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa1_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 90 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha2_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 132 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha1_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 91 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z24neoscrypt_gpu_hash_startijj' for 'sm_37'
    ptxas info    : Function properties for _Z24neoscrypt_gpu_hash_startijj
        320 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 236 registers, 256 bytes smem, 332 bytes cmem[0]
    ptxas info    : 88 bytes gmem, 1088 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z21get_cuda_arch_neo_gpuPi' for 'sm_70'
    ptxas info    : Function properties for _Z21get_cuda_arch_neo_gpuPi
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 6 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z25neoscrypt_gpu_hash_endingijjPj' for 'sm_70'
    ptxas info    : Function properties for _Z25neoscrypt_gpu_hash_endingijjPj
        64 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 128 registers, 256 bytes smem, 376 bytes cmem[0], 8 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa2_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 136 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa1_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 92 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha2_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 136 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha1_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 92 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z24neoscrypt_gpu_hash_startijj' for 'sm_70'
    ptxas info    : Function properties for _Z24neoscrypt_gpu_hash_startijj
        320 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 95 registers, 256 bytes smem, 364 bytes cmem[0], 8 bytes cmem[2]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_52'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        16 bytes stack frame, 24 bytes spill stores, 28 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 76 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_52'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        40 bytes stack frame, 48 bytes spill stores, 52 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 84 bytes cmem[2]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_50'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        16 bytes stack frame, 24 bytes spill stores, 28 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 76 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_50'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        40 bytes stack frame, 48 bytes spill stores, 52 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 84 bytes cmem[2]
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_37'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 126 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_37'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 126 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_35'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_35'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas warning : Too big maxrregcount value specified 128, will be ignored
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_30'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 63 registers, 4096 bytes smem, 336 bytes cmem[0], 4 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_30'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 63 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_70'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        48 bytes stack frame, 76 bytes spill stores, 96 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 368 bytes cmem[0], 8 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_70'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        56 bytes stack frame, 92 bytes spill stores, 104 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 368 bytes cmem[0], 8 bytes cmem[2]
    g++  -O3 -march=native -std=c++11 -pthread -fno-strict-aliasing -pthread -L/usr/local/cuda/lib64 -ldl  -o ccminer ccminer-crc32.o ccminer-hefty1.o ccminer-ccminer.o ccminer-util.o ccminer-api.o ccminer-hashlog.o ccminer-stats.o ccminer-sysinfos.o ccminer-cuda.o ccminer-nvml.o ccminer-nvsettings.o sph/ccminer-neoscrypt.o sph/ccminer-sha256_Y.o sph/ccminer-sph_sha2.o ccminer-fuguecoin.o Algo256/cuda_fugue256.o sph/ccminer-fugue.o ccminer-groestlcoin.o cuda_groestlcoin.o ccminer-myriadgroestl.o cuda_myriadgroestl.o lyra2/ccminer-Lyra2.o lyra2/ccminer-Sponge.o lyra2/lyra2REv2.o lyra2/cuda_lyra2v2.o Algo256/cuda_blake256.o Algo256/cuda_groestl256.o Algo256/cuda_keccak256.o Algo256/cuda_skein256.o Algo256/cuda_bmw256.o Algo256/cuda_cubehash256.o Algo256/blake256.o Algo256/keccak256.o JHA/jackpotcoin.o JHA/cuda_jha_keccak512.o JHA/cuda_jha_compactionTest.o cuda_checkhash.o quark/cuda_jh512.o quark/cuda_quark_blake512.o quark/cuda_quark_groestl512.o quark/cuda_skein512.o quark/cuda_bmw512.o quark/cuda_quark_keccak512.o quark/cuda_jh512keccak512.o quark/quarkcoin.o quark/cuda_quark_compactionTest.o cuda_nist5.o pentablake.o skein.o Sia/sia.o Sia/cuda_sia.o sph/ccminer-bmw.o sph/ccminer-blake.o sph/ccminer-groestl.o sph/ccminer-jh.o sph/ccminer-keccak.o sph/ccminer-skein.o sph/ccminer-cubehash.o sph/ccminer-echo.o sph/ccminer-luffa.o sph/ccminer-sha2.o sph/ccminer-shavite.o sph/ccminer-simd.o sph/ccminer-hamsi.o sph/ccminer-hamsi_helper.o sph/ccminer-shabal.o sph/ccminer-whirlpool.o sph/ccminer-sha2big.o sph/ccminer-haval.o qubit/qubit.o qubit/qubit_luffa512.o qubit/deep.o qubit/doom.o x11/x11.o x11/fresh.o x11/cuda_x11_luffa512.o x11/cuda_x11_cubehash512.o x11/cuda_x11_shavite512.o x11/cuda_x11_simd512.o x11/cuda_x11_echo.o x11/cuda_x11_luffa512_Cubehash.o x13/x13.o x13/cuda_x13_hamsi512.o x13/cuda_x13_fugue512.o x15/x14.o x15/x15.o x15/cuda_x14_shabal512.o x15/cuda_x15_whirlpool.o x15/whirlpool.o x17/x17.o x17/cuda_x17_haval512.o x17/cuda_x17_sha512.o x11/s3.o x11/c11.o bitcoin.o cuda_bitcoin.o x15/cuda_whirlpoolx.o x15/whirlpoolx.o neoscrypt/neoscrypt.o neoscrypt/cuda_neoscrypt.o neoscrypt/cuda_neoscrypt_tpruvot.o -L/usr/lib/x86_64-linux-gnu -lcurl -ljansson -lpthread  -lcudart -fopenmp -lcrypto -lssl  -ldl -lcrypto -lssl
    make[2]: Leaving directory '/home/m1/NVOC/testing/miners/KTccminer/src'
    make[1]: Leaving directory '/home/m1/NVOC/testing/miners/KTccminer/src'

    Finished compiling KlausT ccminer
    ~/NVOC/testing
    m1@m1-desktop:~/NVOC/testing$ sudo bash nvOC miners-upgrade
    root@m1-desktop:~$nvOC miners-upgrade
    Checking for nvOC miners updates...
    Submodule path 'miners': checked out 'cdc0910c7257d245d045fd43643cad68ee8037cb'
    Running updates installer
    ~/NVOC/testing ~/NVOC/testing
    Updating miners for nvOC V0019-2.1
    Will check and restart miner if needed

    Checking EWBF Equihash miner
    EWBF Equihash miner is already up-to-date

    Checking EWBF ZHASH miner
    EWBF ZHASH miner is already up-to-date

    Checking Equihash DSTM zm miner 0.6.1
    DSTM zm miner is already up-to-date

    Checking Z-Enemy 1.10
    z-enemy is already up-to-date

    Checking xmr-stak 2.4.4
    xmr-stak is already up-to-date

    Checking Silent Miner 1.1.0
    Silent Miner is already up-to-date

    Checking Claymore v11.9
    Claymore is already up-to-date

    Checking SP Mod ccminer-1.8.2
    SPccminer is already up-to-date

    Checking alexis ccminer
    ASccminer is already up-to-date

    Checking Krnlx ccminer
    KXccminer is already up-to-date

    Checking Tpruvot ccminer-2.2.5
    Tpruvot ccminer is already up-to-date

    Checking KlausT ccminer 8.20
    KlausT ccminer is already up-to-date

    Checking Vertminer v1.0-stable.2 Release
    Vertminer is already up-to-date

    Checking nanashi-ccminer-2.2-mod-r2
    nanashi-ccminer is already up-to-date

    Checking Ethminer 0.14.0
    ethminer is already up-to-date

    Checking KTccminer-cryptonight v2.06
    KTccminer-cryptonight is already up-to-date

    Checking Equihash Bminer 9.1.0
    Extracting Bminer

    Checking ANXccminer (git@cd6fab68823e247bb84dd1fa0448d5f75ec4917d)
    ANXccminer is already at up-to-date

    Checking MSFT Tpruvot ccminer-2.2.5 (RVN)
    MSFTccminer is already up-to-date

    Checking SUPRminer 1.5
    SUPRminer is already up-to-date

    Checking cpuminer-opt
    cpuminer is already up-to-date


    Extracting and checking new miners for nvOC-v0019-2.x finished


    Do you want to re-compile your miners (y/N)?  y

    Checking if bn.h bignum error is fixed for compiling miners or not
    bn.h openssl already fixed for compiling miners

    Select miners to compile (multiple comma separated values: 1,6,7)
    1 - ASccminer
    2 - KTccminer
    3 - KTccminer-cryptonight
    4 - KXccminer
    5 - NAccminer
    6 - SPccminer
    7 - TPccminer
    8 - vertminer
    9 - ANXccminer
    C - cpuminer
    R - MSFTccminer (RVN)
    U - SUPRminer
    X - xmr-stak

    Do your Choice: [A]LL [1] [2] [3] [4] [5] [6] [7] [8] [9] [C] [R] [U] [X] [E]xit: 3
    3

    Compiling KlausT ccminer cryptonight
     This could take a while ...
    Submodule path 'src': checked out '31865e0b846ad98e2ce99aeb9b28bb51d3be22db'
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking target system type... x86_64-unknown-linux-gnu
    checking for a BSD-compatible install...usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p...bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking whether gcc understands -c and -o together... yes
    checking dependency style of gcc... gcc3
    checking for gcc option to accept ISO C99... none needed
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e...bin/grep
    checking for egrep...bin/grep -E
    checking whether gcc needs -traditional... no
    checking dependency style of gcc... gcc3
    checking for ranlib... ranlib
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    checking for gcc option to support OpenMP... -fopenmp
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking sys/endian.h usability... no
    checking sys/endian.h presence... no
    checking for sys/endian.h... no
    checking sys/param.h usability... yes
    checking sys/param.h presence... yes
    checking for sys/param.h... yes
    checking syslog.h usability... yes
    checking syslog.h presence... yes
    checking for syslog.h... yes
    checking for sys/sysctl.h... yes
    checking whether be32dec is declared... no
    checking whether le32dec is declared... no
    checking whether be32enc is declared... no
    checking whether le32enc is declared... no
    checking for size_t... yes
    checking for working alloca.h... yes
    checking for alloca... yes
    checking for getopt_long... yes
    checking whether we can compile AVX code... yes
    checking whether we can compile XOP code... yes
    checking whether we can compile AVX2 code... yes
    checking for json_loads in -ljansson... yes
    checking for pthread_create in -lpthread... yes
    checking for SSL_library_init in -lssl... yes
    checking for EVP_DigestFinal_ex in -lcrypto... yes
    checking for gawk... (cached) gawk
    checking for curl-config...usr/bin/curl-config
    checking for the version of libcurl... 7.47.0
    checking for libcurl >= version 7.15.2... yes
    checking whether libcurl is usable... yes
    checking for curl_free... yes
    checking that generated files are newer than configure... done
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating compat/Makefile
    config.status: creating compat/jansson/Makefile
    config.status: creating cpuminer-config.h
    config.status: executing depfiles commands
    bash:home/m1/NVOC/testing/miners/KTccminer-cryptonight/src/build.sh: No such file or directory
    cp: cannot stat '/home/m1/NVOC/testing/miners/KTccminer-cryptonight/src/ccminer': No such file or directory

    Finished compiling KlausT ccminer cryptonight
    ~/NVOC/testing
    m1@m1-desktop:~/NVOC/testing$ sudo reboot -f

    Now starting NICE-CRYPTONIGHT:

    Code:
    m1@m1-desktop:~$nvOC miner-log
    /home/m1/NVOC/testing/miners/KTccminer-cryptonight/ccminer: error while loading shared libraries: libcudart.so.8.0: cannot open shared object file: No such file or directory

    rig rebooting after some time so I guess the patched watchdog is working

    edit: I tried some more NICE_ETHASH meanwhile. Can't get ethminer running, I tried Claymore 11.9 again. I always end up with the very first problem, no matter what argument I add to NICE_ETHASH:
    Code:
    ����������������������������������������������������������������ͻ
    �                Claymore's Dual GPU Miner - v11.9               �
    �              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             �
    ����������������������������������������������������������������ͼ

    ETH: 1 pool is specified
    Main Ethereum pool is daggerhashimoto.usa.nicehash.com:3353
    AMD OpenCL platform not found
    Be careful with overclocking, use default clocks for first tests
    Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU
    CUDA initializing...

    NVIDIA Cards available: 5
    CUDA Driver Version/Runtime Version: 9.2/8.0
    GPU #0: GeForce GTX 1080 Ti, 11177 MB available, 28 compute units, capability: 6.1  (pci bus 1:0:0)
    GPU #1: GeForce GTX 1080 Ti, 11178 MB available, 28 compute units, capability: 6.1  (pci bus 2:0:0)
    GPU #2: GeForce GTX 1080 Ti, 11178 MB available, 28 compute units, capability: 6.1  (pci bus 4:0:0)
    GPU #3: GeForce GTX 1080, 8119 MB available, 20 compute units, capability: 6.1  (pci bus 5:0:0)
    GPU #4: GeForce GTX 1080, 8119 MB available, 20 compute units, capability: 6.1  (pci bus 7:0:0)
    Total cards: 5

    You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

    ETH: Stratum - connecting to 'daggerhashimoto.usa.nicehash.com' <172.65.194.252> port 3353 (unsecure)
    ETH: Stratum - Connected (daggerhashimoto.usa.nicehash.com:3353) (unsecure)
    ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
    ETH: miner-proxy stratum mode
    "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
    Watchdog enabled
    Remote management (READ-ONLY MODE) is enabled on port 3333

    ETH: Authorized
    cannot convert blob3 data
    cannot convert blob3 data
    cannot convert blob3 data
    cannot convert blob3 data
    ETH: Job timeout, disconnect, retry in 20 sec...
    I tried following arguments:
    NICE_ETHASH_EXTENSION_ARGUMENTS="-esm 3 -allpools 1 -estale 0"
    NICE_ETHASH_EXTENSION_ARGUMENTS="-esm 2 -allpools 1 -estale 0"
    NICE_ETHASH_EXTENSION_ARGUMENTS="-esm 2 -allpools 1"
    NICE_ETHASH_EXTENSION_ARGUMENTS="-allpools 1" 

    error remains the same. Is anybody using any NICEHASH with nvOC 2.1 successfully?

  • papampi_2
    Jr. Member
    *
    Offline Offline

    Activity: 112
    Merit: 3

    Linux Forever... Resistance is futile!!!


    View Profile WWW
    August 06, 2018, 04:37:19 PM
     #6725
    Quote from: fk2 on August 06, 2018, 11:12:57 AM
    @papampi: tyvm for quick support on watchdog! already pulled latest version but stucked on cuda update.

    I did an update following this guide: https://wagonhelm.github.io/articles/2018-02/Installing-Cuda-9.0-Toolkit-Ubuntu-16.04
    I installed 9.2 and skipped cudNN. I did the last two steps udating bash file and terminal.

    Code:
    m1@m1-desktop:~$ cdusr/local/cuda
    m1@m1-desktop:/usr/local/cuda$ cat version.txt
    CUDA Version 9.2.88

    I recompiled KTccminer plus KTccminer-cryptonight, unfortunately not everything was saved properly, the first KTccminer lines are missing but it looked good:
    Code:
    ptxas info    : Used 157 registers, 256 bytes smem, 344 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa2_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 132 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa1_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 90 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha2_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 132 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha1_stream1jj' for 'sm_37'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 91 registers, 328 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z24neoscrypt_gpu_hash_startijj' for 'sm_37'
    ptxas info    : Function properties for _Z24neoscrypt_gpu_hash_startijj
        320 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 236 registers, 256 bytes smem, 332 bytes cmem[0]
    ptxas info    : 88 bytes gmem, 1088 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z21get_cuda_arch_neo_gpuPi' for 'sm_70'
    ptxas info    : Function properties for _Z21get_cuda_arch_neo_gpuPi
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 6 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z25neoscrypt_gpu_hash_endingijjPj' for 'sm_70'
    ptxas info    : Function properties for _Z25neoscrypt_gpu_hash_endingijjPj
        64 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 128 registers, 256 bytes smem, 376 bytes cmem[0], 8 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa2_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 136 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z33neoscrypt_gpu_hash_salsa1_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z33neoscrypt_gpu_hash_salsa1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 92 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha2_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha2_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 136 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z34neoscrypt_gpu_hash_chacha1_stream1jj' for 'sm_70'
    ptxas info    : Function properties for _Z34neoscrypt_gpu_hash_chacha1_stream1jj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 92 registers, 360 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z24neoscrypt_gpu_hash_startijj' for 'sm_70'
    ptxas info    : Function properties for _Z24neoscrypt_gpu_hash_startijj
        320 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 95 registers, 256 bytes smem, 364 bytes cmem[0], 8 bytes cmem[2]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_52'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        16 bytes stack frame, 24 bytes spill stores, 28 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 76 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_52'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        40 bytes stack frame, 48 bytes spill stores, 52 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 84 bytes cmem[2]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_50'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        16 bytes stack frame, 24 bytes spill stores, 28 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 76 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_50'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        40 bytes stack frame, 48 bytes spill stores, 52 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0], 84 bytes cmem[2]
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_37'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 126 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_37'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 126 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_35'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_35'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas warning : Too big maxrregcount value specified 128, will be ignored
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_30'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 63 registers, 4096 bytes smem, 336 bytes cmem[0], 4 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_30'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
    ptxas info    : Used 63 registers, 4096 bytes smem, 336 bytes cmem[0]
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : Overriding global maxrregcount 128 with entry-specific value 64 computed using thread count
    ptxas info    : 0 bytes gmem, 4224 bytes cmem[3]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_80jjPv' for 'sm_70'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_80jjPv
        48 bytes stack frame, 76 bytes spill stores, 96 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 368 bytes cmem[0], 8 bytes cmem[2]
    ptxas info    : Compiling entry function '_Z26x11_shavite512_gpu_hash_64jPj' for 'sm_70'
    ptxas info    : Function properties for _Z26x11_shavite512_gpu_hash_64jPj
        56 bytes stack frame, 92 bytes spill stores, 104 bytes spill loads
    ptxas info    : Used 64 registers, 4096 bytes smem, 368 bytes cmem[0], 8 bytes cmem[2]
    g++  -O3 -march=native -std=c++11 -pthread -fno-strict-aliasing -pthread -L/usr/local/cuda/lib64 -ldl  -o ccminer ccminer-crc32.o ccminer-hefty1.o ccminer-ccminer.o ccminer-util.o ccminer-api.o ccminer-hashlog.o ccminer-stats.o ccminer-sysinfos.o ccminer-cuda.o ccminer-nvml.o ccminer-nvsettings.o sph/ccminer-neoscrypt.o sph/ccminer-sha256_Y.o sph/ccminer-sph_sha2.o ccminer-fuguecoin.o Algo256/cuda_fugue256.o sph/ccminer-fugue.o ccminer-groestlcoin.o cuda_groestlcoin.o ccminer-myriadgroestl.o cuda_myriadgroestl.o lyra2/ccminer-Lyra2.o lyra2/ccminer-Sponge.o lyra2/lyra2REv2.o lyra2/cuda_lyra2v2.o Algo256/cuda_blake256.o Algo256/cuda_groestl256.o Algo256/cuda_keccak256.o Algo256/cuda_skein256.o Algo256/cuda_bmw256.o Algo256/cuda_cubehash256.o Algo256/blake256.o Algo256/keccak256.o JHA/jackpotcoin.o JHA/cuda_jha_keccak512.o JHA/cuda_jha_compactionTest.o cuda_checkhash.o quark/cuda_jh512.o quark/cuda_quark_blake512.o quark/cuda_quark_groestl512.o quark/cuda_skein512.o quark/cuda_bmw512.o quark/cuda_quark_keccak512.o quark/cuda_jh512keccak512.o quark/quarkcoin.o quark/cuda_quark_compactionTest.o cuda_nist5.o pentablake.o skein.o Sia/sia.o Sia/cuda_sia.o sph/ccminer-bmw.o sph/ccminer-blake.o sph/ccminer-groestl.o sph/ccminer-jh.o sph/ccminer-keccak.o sph/ccminer-skein.o sph/ccminer-cubehash.o sph/ccminer-echo.o sph/ccminer-luffa.o sph/ccminer-sha2.o sph/ccminer-shavite.o sph/ccminer-simd.o sph/ccminer-hamsi.o sph/ccminer-hamsi_helper.o sph/ccminer-shabal.o sph/ccminer-whirlpool.o sph/ccminer-sha2big.o sph/ccminer-haval.o qubit/qubit.o qubit/qubit_luffa512.o qubit/deep.o qubit/doom.o x11/x11.o x11/fresh.o x11/cuda_x11_luffa512.o x11/cuda_x11_cubehash512.o x11/cuda_x11_shavite512.o x11/cuda_x11_simd512.o x11/cuda_x11_echo.o x11/cuda_x11_luffa512_Cubehash.o x13/x13.o x13/cuda_x13_hamsi512.o x13/cuda_x13_fugue512.o x15/x14.o x15/x15.o x15/cuda_x14_shabal512.o x15/cuda_x15_whirlpool.o x15/whirlpool.o x17/x17.o x17/cuda_x17_haval512.o x17/cuda_x17_sha512.o x11/s3.o x11/c11.o bitcoin.o cuda_bitcoin.o x15/cuda_whirlpoolx.o x15/whirlpoolx.o neoscrypt/neoscrypt.o neoscrypt/cuda_neoscrypt.o neoscrypt/cuda_neoscrypt_tpruvot.o -L/usr/lib/x86_64-linux-gnu -lcurl -ljansson -lpthread  -lcudart -fopenmp -lcrypto -lssl  -ldl -lcrypto -lssl
    make[2]: Leaving directory '/home/m1/NVOC/testing/miners/KTccminer/src'
    make[1]: Leaving directory '/home/m1/NVOC/testing/miners/KTccminer/src'

    Finished compiling KlausT ccminer
    ~/NVOC/testing
    m1@m1-desktop:~/NVOC/testing$ sudo bash nvOC miners-upgrade
    root@m1-desktop:~$nvOC miners-upgrade
    Checking for nvOC miners updates...
    Submodule path 'miners': checked out 'cdc0910c7257d245d045fd43643cad68ee8037cb'
    Running updates installer
    ~/NVOC/testing ~/NVOC/testing
    Updating miners for nvOC V0019-2.1
    Will check and restart miner if needed

    Checking EWBF Equihash miner
    EWBF Equihash miner is already up-to-date

    Checking EWBF ZHASH miner
    EWBF ZHASH miner is already up-to-date

    Checking Equihash DSTM zm miner 0.6.1
    DSTM zm miner is already up-to-date

    Checking Z-Enemy 1.10
    z-enemy is already up-to-date

    Checking xmr-stak 2.4.4
    xmr-stak is already up-to-date

    Checking Silent Miner 1.1.0
    Silent Miner is already up-to-date

    Checking Claymore v11.9
    Claymore is already up-to-date

    Checking SP Mod ccminer-1.8.2
    SPccminer is already up-to-date

    Checking alexis ccminer
    ASccminer is already up-to-date

    Checking Krnlx ccminer
    KXccminer is already up-to-date

    Checking Tpruvot ccminer-2.2.5
    Tpruvot ccminer is already up-to-date

    Checking KlausT ccminer 8.20
    KlausT ccminer is already up-to-date

    Checking Vertminer v1.0-stable.2 Release
    Vertminer is already up-to-date

    Checking nanashi-ccminer-2.2-mod-r2
    nanashi-ccminer is already up-to-date

    Checking Ethminer 0.14.0
    ethminer is already up-to-date

    Checking KTccminer-cryptonight v2.06
    KTccminer-cryptonight is already up-to-date

    Checking Equihash Bminer 9.1.0
    Extracting Bminer

    Checking ANXccminer (git@cd6fab68823e247bb84dd1fa0448d5f75ec4917d)
    ANXccminer is already at up-to-date

    Checking MSFT Tpruvot ccminer-2.2.5 (RVN)
    MSFTccminer is already up-to-date

    Checking SUPRminer 1.5
    SUPRminer is already up-to-date

    Checking cpuminer-opt
    cpuminer is already up-to-date


    Extracting and checking new miners for nvOC-v0019-2.x finished


    Do you want to re-compile your miners (y/N)?  y

    Checking if bn.h bignum error is fixed for compiling miners or not
    bn.h openssl already fixed for compiling miners

    Select miners to compile (multiple comma separated values: 1,6,7)
    1 - ASccminer
    2 - KTccminer
    3 - KTccminer-cryptonight
    4 - KXccminer
    5 - NAccminer
    6 - SPccminer
    7 - TPccminer
    8 - vertminer
    9 - ANXccminer
    C - cpuminer
    R - MSFTccminer (RVN)
    U - SUPRminer
    X - xmr-stak

    Do your Choice: [A]LL [1] [2] [3] [4] [5] [6] [7] [8] [9] [C] [R] [U] [X] [E]xit: 3
    3

    Compiling KlausT ccminer cryptonight
     This could take a while ...
    Submodule path 'src': checked out '31865e0b846ad98e2ce99aeb9b28bb51d3be22db'
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking target system type... x86_64-unknown-linux-gnu
    checking for a BSD-compatible install...usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p...bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking whether gcc understands -c and -o together... yes
    checking dependency style of gcc... gcc3
    checking for gcc option to accept ISO C99... none needed
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e...bin/grep
    checking for egrep...bin/grep -E
    checking whether gcc needs -traditional... no
    checking dependency style of gcc... gcc3
    checking for ranlib... ranlib
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    checking for gcc option to support OpenMP... -fopenmp
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking sys/endian.h usability... no
    checking sys/endian.h presence... no
    checking for sys/endian.h... no
    checking sys/param.h usability... yes
    checking sys/param.h presence... yes
    checking for sys/param.h... yes
    checking syslog.h usability... yes
    checking syslog.h presence... yes
    checking for syslog.h... yes
    checking for sys/sysctl.h... yes
    checking whether be32dec is declared... no
    checking whether le32dec is declared... no
    checking whether be32enc is declared... no
    checking whether le32enc is declared... no
    checking for size_t... yes
    checking for working alloca.h... yes
    checking for alloca... yes
    checking for getopt_long... yes
    checking whether we can compile AVX code... yes
    checking whether we can compile XOP code... yes
    checking whether we can compile AVX2 code... yes
    checking for json_loads in -ljansson... yes
    checking for pthread_create in -lpthread... yes
    checking for SSL_library_init in -lssl... yes
    checking for EVP_DigestFinal_ex in -lcrypto... yes
    checking for gawk... (cached) gawk
    checking for curl-config...usr/bin/curl-config
    checking for the version of libcurl... 7.47.0
    checking for libcurl >= version 7.15.2... yes
    checking whether libcurl is usable... yes
    checking for curl_free... yes
    checking that generated files are newer than configure... done
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating compat/Makefile
    config.status: creating compat/jansson/Makefile
    config.status: creating cpuminer-config.h
    config.status: executing depfiles commands
    bash:home/m1/NVOC/testing/miners/KTccminer-cryptonight/src/build.sh: No such file or directory
    cp: cannot stat '/home/m1/NVOC/testing/miners/KTccminer-cryptonight/src/ccminer': No such file or directory

    Finished compiling KlausT ccminer cryptonight
    ~/NVOC/testing
    m1@m1-desktop:~/NVOC/testing$ sudo reboot -f

    Now starting NICE-CRYPTONIGHT:

    Code:
    m1@m1-desktop:~$nvOC miner-log
    /home/m1/NVOC/testing/miners/KTccminer-cryptonight/ccminer: error while loading shared libraries: libcudart.so.8.0: cannot open shared object file: No such file or directory

    rig rebooting after some time so I guess the patched watchdog is working

    edit: I tried some more NICE_ETHASH meanwhile. Can't get ethminer running, I tried Claymore 11.9 again. I always end up with the very first problem, no matter what argument I add to NICE_ETHASH:
    Code:
    ����������������������������������������������������������������ͻ
    �                Claymore's Dual GPU Miner - v11.9               �
    �              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             �
    ����������������������������������������������������������������ͼ

    ETH: 1 pool is specified
    Main Ethereum pool is daggerhashimoto.usa.nicehash.com:3353
    AMD OpenCL platform not found
    Be careful with overclocking, use default clocks for first tests
    Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU
    CUDA initializing...

    NVIDIA Cards available: 5
    CUDA Driver Version/Runtime Version: 9.2/8.0
    GPU #0: GeForce GTX 1080 Ti, 11177 MB available, 28 compute units, capability: 6.1  (pci bus 1:0:0)
    GPU #1: GeForce GTX 1080 Ti, 11178 MB available, 28 compute units, capability: 6.1  (pci bus 2:0:0)
    GPU #2: GeForce GTX 1080 Ti, 11178 MB available, 28 compute units, capability: 6.1  (pci bus 4:0:0)
    GPU #3: GeForce GTX 1080, 8119 MB available, 20 compute units, capability: 6.1  (pci bus 5:0:0)
    GPU #4: GeForce GTX 1080, 8119 MB available, 20 compute units, capability: 6.1  (pci bus 7:0:0)
    Total cards: 5

    You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

    ETH: Stratum - connecting to 'daggerhashimoto.usa.nicehash.com' <172.65.194.252> port 3353 (unsecure)
    ETH: Stratum - Connected (daggerhashimoto.usa.nicehash.com:3353) (unsecure)
    ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
    ETH: miner-proxy stratum mode
    "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
    Watchdog enabled
    Remote management (READ-ONLY MODE) is enabled on port 3333

    ETH: Authorized
    cannot convert blob3 data
    cannot convert blob3 data
    cannot convert blob3 data
    cannot convert blob3 data
    ETH: Job timeout, disconnect, retry in 20 sec...
    I tried following arguments:
    NICE_ETHASH_EXTENSION_ARGUMENTS="-esm 3 -allpools 1 -estale 0"
    NICE_ETHASH_EXTENSION_ARGUMENTS="-esm 2 -allpools 1 -estale 0"
    NICE_ETHASH_EXTENSION_ARGUMENTS="-esm 2 -allpools 1"
    NICE_ETHASH_EXTENSION_ARGUMENTS="-allpools 1" 

    error remains the same. Is anybody using any NICEHASH with nvOC 2.1 successfully?

    We are working on a cuda-9.2 Image with latest cuda-9.2 miners
    If you compile miners using nvOC miner-upgrade now, you wont get latest miners which has cuda-9.2 support.
    You should manually download source and compile them until the image is ready and we update Git repo to support both cuda 8 and 9
    https://github.com/papampi/nvOC_by_fullzero_Community_Release

  • Bibi187
    Full Member
    ***
    Offline Offline

    Activity: 420
    Merit: 106


    https://steemit.com/@bibi187


    View Profile WWW
    August 07, 2018, 02:33:30 PM
     #6726
    Hey Wink

    It seems i have a weird issue ...

    When using 3main to ETH it seems that launching autotemp control ...

    When i choice another based on ETHASH everything is working fine ...

    As example my 3main file working for ATH but not for ETH, 3main don't even launch the miner.

    3main sample :

    if [ $COIN == "ATH" ]
    then
    HCD='/home/m1/eth/ethminer_12dev2/ethminer'
    ATHADDR="$ATH_ADDRESS.$ATH_WORKER"

    fi

    screen -dmSL miner $HCD --farm-recheck 200 -U -S $ATH_POOL -SP 1 -O $ATHADDR

    if [ $LOCALorREMOTE == "LOCAL" ]
    then
    screen -r miner
    fi

    if [ $LOCALorREMOTE == "LOCAL" ]
    then
    screen -r miner
    fi

    BITCOIN="theGROUND"

    while [ $BITCOIN == "theGROUND" ]
    do
    sleep 60
    done
    fi

    if [ $COIN == "ETH" ]
    then

    HCD='/home/m1/eth/ethminer_12dev2/ethminer'
    ETHADDR="$ETH_ADDRESS/$ETH_WORKER"

    fi

    screen -dmSL miner $HCD -S $ETH_POOL -O $ETHADDR:x -U

    if [ $LOCALorREMOTE == "LOCAL" ]
    then
    screen -r miner
    fi

    BITCOIN="theGROUND"

    while [ $BITCOIN == "theGROUND" ]
    do
    sleep 60
    done
    fi




    Here is my 1bash extract :

    ETH_WORKER="$WORKERNAME"
    ETH_ADDRESS="MyAddress"   
    ETH_POOL="eth-eu1.nanopool.org:9999"

    ATH_WORKER="$WORKERNAME"
    ATH_ADDRESS="MyAddress"   
    ATH_POOL="geo.pool.atheios.eu:8001"


    So really weird when i select ATH everything is working fine miner launch etc ... When i select ETH instant of miner launch on screen -x miner, i get another temp control session ...

    I think i finally have to go on the new version Cheesy
    DeepOnion    ▬▬  Anonymous and Untraceable  ▬▬    ENJOY YOUR PRIVACY  •  JOIN DEEPONION
    ▐▐▐▐▐▐▐▐   ANN  Whitepaper  Facebook  Twitter  Telegram  Discord    ▌▌▌▌▌▌▌▌
    Get $ONION  (✔Cryptopia  ✔KuCoin)  |  VoteCentral  Register NOW!  |  Download DeepOnion

  • VoskCoin
    Sr. Member
    ****
    Offline Offline

    Activity: 1414
    Merit: 487


    YouTube.com/VoskCoin


    View Profile WWW
    August 07, 2018, 03:26:25 PM
     #6727
    Quote from: gs777 on August 01, 2018, 08:48:58 PM
    Is anyone tried EWBF v0.5?
    Is it worth to upgrade v0.4
     Huh

    .5 is worth it to upgrade over .4 -- you do actually receive the claimed 2% increase
    Check out my Crypto YouTube channel
    https://www.youtube.com/VoskCoin
    If you enjoy my content click Subscribe

  • blackline
    Newbie
    *
    Offline Offline

    Activity: 21
    Merit: 0


    View Profile
    August 07, 2018, 08:01:04 PM
     #6728
    How to compline nvOC miner-upgrade now

  • gs777
    Member
    **
    Offline Offline

    Activity: 118
    Merit: 10


    View Profile
    August 08, 2018, 03:58:17 PM
     #6729
    Quote from: VoskCoin on August 07, 2018, 03:26:25 PM
    Quote from: gs777 on August 01, 2018, 08:48:58 PM
    Is anyone tried EWBF v0.5?
    Is it worth to upgrade v0.4
     Huh

    .5 is worth it to upgrade over .4 -- you do actually receive the claimed 2% increase

    Thanks for reply VoskCoin!
    I already upgraded my EWBF to v0.5. It's hashing aprox 15% batter then v0.4.
    Really like it
     Grin

  • papampi_2
    Jr. Member
    *
    Offline Offline

    Activity: 112
    Merit: 3

    Linux Forever... Resistance is futile!!!


    View Profile WWW
    August 09, 2018, 07:32:13 AM
     #6730
    Quote from: blackline on August 07, 2018, 08:01:04 PM
    How to compline nvOC miner-upgrade now
    Better to update nvoc first

    Code:
    cd ~/NVOC/mining
    bash nvOC upgrade

    If it didnt ask you to update miners, run it again
    It will ask to update miners then ask for compile
    https://github.com/papampi/nvOC_by_fullzero_Community_Release

  • Joykiller
    Newbie
    *
    Offline Offline

    Activity: 35
    Merit: 0


    View Profile
    August 10, 2018, 07:23:37 AM
     #6731
    Anyone come across random nvidia GPU Fallen off the bus messages before?

    I've been logging them over the past few days to see if i can break down as to what is making it fail.

    Code:
    Aug  8 03:42:57 m1-desktop kernel: [105074.572611] NVRM: GPU Board Serial Number:
    Aug  8 03:42:57 m1-desktop kernel: [105074.572620] NVRM: Xid (PCI:0000:05:00): 79, GPU has fallen off the bus.
    Aug  8 03:42:57 m1-desktop kernel: [105074.572626] NVRM: GPU at 0000:05:00.0 has fallen off the bus.

    Second Time

    Code:
    Aug  9 22:18:43 m1-desktop kernel: [122030.262423] NVRM: GPU Board Serial Number:
    Aug  9 22:18:43 m1-desktop kernel: [122030.262433] NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus.
    Aug  9 22:18:43 m1-desktop kernel: [122030.262439] NVRM: GPU at 0000:01:00.0 has fallen off the bus.

    So its not the same GPU's each time its a new Bus, and GPU, Anyone got any Ideas? I was thinking maybe the 1070s not playing nice with the newest drivers or maybe the riser or its components failing? Thoughts?

  • gs777
    Member
    **
    Offline Offline

    Activity: 118
    Merit: 10


    View Profile
    August 10, 2018, 08:41:14 AM
     #6732
    No. My 1070 rig works fine, no problem.
    I had problem with other rig
    and when I switch gpu0 and gpu12 usb3 connection it stopped crushing.
    Don't know is it the case for your rig, but its working for me
     Roll Eyes

  • LuKePicci
    Jr. Member
    *
    Offline Offline

    Activity: 128
    Merit: 1


    View Profile
    August 10, 2018, 08:53:21 AM
     #6733
    @joykiller check that your connectors in motherboard pcie sockets do not touch each other.

  • Joykiller
    Newbie
    *
    Offline Offline

    Activity: 35
    Merit: 0


    View Profile
    August 10, 2018, 03:50:22 PM
     #6734
    Quote from: LuKePicci on August 10, 2018, 08:53:21 AM
    @joykiller check that your connectors in motherboard pcie sockets do not touch each other.


    You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

  • Joykiller
    Newbie
    *
    Offline Offline

    Activity: 35
    Merit: 0


    View Profile
    August 10, 2018, 03:52:16 PM
     #6735
    Quote from: gs777 on August 10, 2018, 08:41:14 AM
    No. My 1070 rig works fine, no problem.
    I had problem with other rig
    and when I switch gpu0 and gpu12 usb3 connection it stopped crushing.
    Don't know is it the case for your rig, but its working for me
     Roll Eyes

    Thanks, Yeah I was thinking maybe it was something to do with either USB/x1 Connector/ the riser its self or Drivers. I got spares to replace them, Just continuing to test to see if more than just these two are causing the bus failure to see how many Risers i may have to replace.

  • LuKePicci
    Jr. Member
    *
    Offline Offline

    Activity: 128
    Merit: 1


    View Profile
    August 11, 2018, 11:08:47 AM
     #6736
    Quote from: Joykiller on August 10, 2018, 03:50:22 PM
    Quote from: LuKePicci on August 10, 2018, 08:53:21 AM
    @joykiller check that your connectors in motherboard pcie sockets do not touch each other.


    You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

    Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

  • Joykiller
    Newbie
    *
    Offline Offline

    Activity: 35
    Merit: 0


    View Profile
    August 11, 2018, 07:08:48 PM
     #6737
    Quote from: LuKePicci on August 11, 2018, 11:08:47 AM
    Quote from: Joykiller on August 10, 2018, 03:50:22 PM
    Quote from: LuKePicci on August 10, 2018, 08:53:21 AM
    @joykiller check that your connectors in motherboard pcie sockets do not touch each other.


    You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

    Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

    You mean wrap the USB Cable in aluminium foil tape? Or you talking about the x1 Slot wouldnt that cause issues with conductivity on the board? Got a picture for reference please?

    I've seem'ed to get it working so far, its been going for over 24h so far as it has in the past year, but if the foil tape helps increase hashrate due to frequency noise maybe might be worth it. I got some tape laying around.

  • WaveFront
    Member
    **
    Offline Offline

    Activity: 126
    Merit: 10


    View Profile
    August 12, 2018, 04:28:57 AM
     #6738
    Quote from: Joykiller on August 11, 2018, 07:08:48 PM
    Quote from: LuKePicci on August 11, 2018, 11:08:47 AM
    Quote from: Joykiller on August 10, 2018, 03:50:22 PM
    Quote from: LuKePicci on August 10, 2018, 08:53:21 AM
    @joykiller check that your connectors in motherboard pcie sockets do not touch each other.


    You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

    Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

    You mean wrap the USB Cable in aluminium foil tape? Or you talking about the x1 Slot wouldnt that cause issues with conductivity on the board? Got a picture for reference please?

    I've seem'ed to get it working so far, its been going for over 24h so far as it has in the past year, but if the foil tape helps increase hashrate due to frequency noise maybe might be worth it. I got some tape laying around.
    No. What LukePicci was meaning is that in boards where the pcie connectors are close to each other, the side of the x1 connector, might touch the flat part of usb female connector of next x1 connector. This might disable the slot at best, or create short circuits.
    in order to prevent this you should place isolating tape on the side of the x1 connector. You should cover with tape the parts highlited in red in the picture.


    If you exclude too aggressive overclocking, 90% of the instability problems on a rig are coming from poor power distribution. Two pieces of advice:

    1) the pcie cable to SATA provided with the risers is generally of crappy quality. In any case the SATA connector cannot take more than 50-55W, so you should connect the pcie riser to a 6pin PCI cable directly to the power supply or through a pcie splitter.


    2) If you have a dual power supply configuration, you should power the motherboard and all PCI risers with the same power supply. You will use the second power supply to power the top connectors of the GPUs only. This will prevent ground loops and many headaches.

  • Joykiller
    Newbie
    *
    Offline Offline

    Activity: 35
    Merit: 0


    View Profile
    August 12, 2018, 06:18:34 AM
     #6739
    Quote from: WaveFront on August 12, 2018, 04:28:57 AM
    Quote from: Joykiller on August 11, 2018, 07:08:48 PM
    Quote from: LuKePicci on August 11, 2018, 11:08:47 AM
    Quote from: Joykiller on August 10, 2018, 03:50:22 PM
    Quote from: LuKePicci on August 10, 2018, 08:53:21 AM
    @joykiller check that your connectors in motherboard pcie sockets do not touch each other.


    You mean the x1 connectors? Those are not touching, the USB wires are, but its been like this now for over a year and had no issues.

    Yes, make sure the usb female connector of each x1 adapter is well spaced from the back contacts of the adjacent x1 connector board. It is a known issue for motherboards where each pcie socket is too close to the other one, like in the Asrock H110 Pro BTC+. I stopped having random gpus falling off the bus as soon as I covered each connector with isolating tape.

    You mean wrap the USB Cable in aluminium foil tape? Or you talking about the x1 Slot wouldnt that cause issues with conductivity on the board? Got a picture for reference please?

    I've seem'ed to get it working so far, its been going for over 24h so far as it has in the past year, but if the foil tape helps increase hashrate due to frequency noise maybe might be worth it. I got some tape laying around.
    No. What LukePicci was meaning is that in boards where the pcie connectors are close to each other, the side of the x1 connector, might touch the flat part of usb female connector of next x1 connector. This might disable the slot at best, or create short circuits.
    in order to prevent this you should place isolating tape on the side of the x1 connector. You should cover with tape the parts highlited in red in the picture.
    https://cdn.pbrd.co/images/HyM9NAj.jpg

    If you exclude too aggressive overclocking, 90% of the instability problems on a rig are coming from poor power distribution. Two pieces of advice:

    1) the pcie cable to SATA provided with the risers is generally of crappy quality. In any case the SATA connector cannot take more than 50-55W, so you should connect the pcie riser to a 6pin PCI cable directly to the power supply or through a pcie splitter.
    https://cdn.pbrd.co/images/HyMadEJ.jpghttps://cdn.pbrd.co/images/HyMcXqw.jpg

    2) If you have a dual power supply configuration, you should power the motherboard and all PCI risers with the same power supply. You will use the second power supply to power the top connectors of the GPUs only. This will prevent ground loops and many headaches.


    ah right, well I already know about the connectors, been running a few GPU rigs for over a year already no problems. Problem seems to be be fixed it was more or less a power issue i believe as its going now for 48h no interuptions. (Undervolted)

    Interesting about the USB I dont seem to have that issue tho.

  • gs777
    Member
    **
    Offline Offline

    Activity: 118
    Merit: 10


    View Profile
    August 13, 2018, 04:15:33 PM
     #6740
    Trying to run new Bminer but It doesn't start
    I have this message all the time

    Code:
    SCREEN -chome/m1/NVOC/mining/screenrc-miner -dmSL minerhome/m1/NVOC/mining/miners/bminer/latest/bminer -uri stratum+tcp://MyAddress.001:x@us-east.equihash-hub.miningpoolhub.com:20575
    invalid value "stratum+tcp://MyAddress.001:x@us-east.equihash-hub.miningpoolhub.com:20575" for flag -uri: Unsupported scheme
    Bminer: When Crypto-mining Made Fast (v9.1.0-9f41d5c)

    Can anyone help me, what I did wrong?
    Pages: « 1 ... 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 [337] 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 »
      Print  
Page 336
Viewing Page: 337

IRLBTC™ © 2025 IRLBTC.com