Bitcoin Forum
May 06, 2024, 10:47:17 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 [4] 5 6 7 8 9 10 11 »  All
  Print  
Author Topic: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining  (Read 4095 times)
papampi (OP)
Full Member
***
Offline Offline

Activity: 686
Merit: 140


Linux FOREVER! Resistance is futile!!!


View Profile WWW
May 18, 2019, 05:20:40 AM
 #61


I have no experience with xmr-stak
Maybe @LuKePicci or @CryptAtomeTrader44 can help with it

1714992437
Hero Member
*
Offline Offline

Posts: 1714992437

View Profile Personal Message (Offline)

Ignore
1714992437
Reply with quote  #2

1714992437
Report to moderator
1714992437
Hero Member
*
Offline Offline

Posts: 1714992437

View Profile Personal Message (Offline)

Ignore
1714992437
Reply with quote  #2

1714992437
Report to moderator
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714992437
Hero Member
*
Offline Offline

Posts: 1714992437

View Profile Personal Message (Offline)

Ignore
1714992437
Reply with quote  #2

1714992437
Report to moderator
1714992437
Hero Member
*
Offline Offline

Posts: 1714992437

View Profile Personal Message (Offline)

Ignore
1714992437
Reply with quote  #2

1714992437
Report to moderator
1714992437
Hero Member
*
Offline Offline

Posts: 1714992437

View Profile Personal Message (Offline)

Ignore
1714992437
Reply with quote  #2

1714992437
Report to moderator
LuKePicci
Jr. Member
*
Offline Offline

Activity: 128
Merit: 1


View Profile
May 19, 2019, 05:15:11 PM
 #62

@damnMad hardcoded monero currency can be removed from manifest if you include such a setting in 1bash.template where needed by default (ie for each coin where xmr-stak is selected as miner by default add <coin>_XMR_Stak_OPTS="--currency xxx"). Open the two needed PRs for these changes (against 3.2 branch).

Give me some more detail on the compilation failure, maybe better if you open an issue for that on https://github.com/papampi/nvOC_miners
damNmad
Full Member
***
Offline Offline

Activity: 378
Merit: 104


nvOC forever


View Profile
May 19, 2019, 08:18:48 PM
 #63

@damnMad hardcoded monero currency can be removed from manifest if you include such a setting in 1bash.template where needed by default (ie for each coin where xmr-stak is selected as miner by default add <coin>_XMR_Stak_OPTS="--currency xxx"). Open the two needed PRs for these changes (against 3.2 branch).

Give me some more detail on the compilation failure, maybe better if you open an issue for that on https://github.com/papampi/nvOC_miners

Thanks @LuKePicci, appreciate it.

Yes, you are right, we can add a note in 1bash and ask people to add _XMR_Stak_OPTS="--currency xxx".

I don't think we have any other better miner available for cryptonight coins other than XMR-STAK.

I'll try to apply those two changes in a PR.

Regarding compilation error, this is the error I'm getting!

Code:
m1@m1-desktop:~/NVOC/mining/miners/XMR_Stak/xmr-stak/build$ make install
Scanning dependencies of target xmr-stak-asm
[  2%] Building ASM object CMakeFiles/xmr-stak-asm.dir/xmrstak/backend/cpu/crypto/asm/cryptonight_v8_main_loop.S.o
[  4%] Building ASM object CMakeFiles/xmr-stak-asm.dir/xmrstak/backend/cpu/crypto/asm/cnR/CryptonightR_template.S.o
[  6%] Linking C static library bin/libxmr-stak-asm.a
[  6%] Built target xmr-stak-asm
Scanning dependencies of target xmr-stak-c
[  9%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_skein.c.o
[ 11%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_groestl.c.o
[ 13%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_jh.c.o
[ 15%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_blake256.c.o
[ 18%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_keccak.c.o
[ 20%] Linking C static library bin/libxmr-stak-c.a
[ 20%] Built target xmr-stak-c
Scanning dependencies of target xmr-stak-backend
[ 22%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/version.cpp.o
[ 25%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/jconf.cpp.o
[ 27%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/cpuType.cpp.o
[ 29%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/minethd.cpp.o
[ 31%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/jconf.cpp.o
[ 34%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/hwlocMemory.cpp.o
[ 36%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/backendConnector.cpp.o
[ 38%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/globalStates.cpp.o
[ 40%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/cryptonight_common.cpp.o
[ 43%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/cn_gpu_avx.cpp.o
[ 45%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/CryptonightR_gen.cpp.o
[ 47%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/cn_gpu_ssse3.cpp.o
[ 50%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/http/httpd.cpp.o
[ 52%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/http/webdesign.cpp.o
[ 54%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/utility.cpp.o
[ 56%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/executor.cpp.o
[ 59%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/uac.cpp.o
[ 61%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/telemetry.cpp.o
[ 63%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/console.cpp.o
[ 65%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/net/socket.cpp.o
[ 68%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/net/jpsock.cpp.o
[ 70%] Linking CXX static library bin/libxmr-stak-backend.a
[ 70%] Built target xmr-stak-backend
[ 72%] Building NVCC (Device) object CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/xmrstak_cuda_backend_generated_cuda_extra.cu.o
/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9220): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9231): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9244): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9255): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9268): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9279): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9292): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9303): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9316): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9327): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9340): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9352): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9365): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9376): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9389): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9401): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9410): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9419): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9428): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9437): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9445): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9454): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9463): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9472): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9481): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9490): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9499): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9508): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9517): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9526): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9535): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9544): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(55): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(63): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(73): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(81): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(91): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(100): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(109): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(117): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(127): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(136): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(145): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(153): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10799): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10811): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10823): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10835): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10847): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10859): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10871): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10883): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10895): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10907): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10919): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10931): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10943): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10955): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10967): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10979): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10989): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11000): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11009): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11020): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11029): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11040): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11049): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11060): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11069): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11080): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11089): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11100): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11109): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11120): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11129): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11140): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11149): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11160): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11169): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11180): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11189): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11200): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11209): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11220): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11229): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11240): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11249): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11260): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11269): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11280): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11289): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11300): error: argument of type "void *" is incompatible with parameter of type "long long *"

92 errors detected in the compilation of "/tmp/tmpxft_000033a8_00000000-14_cuda_extra.compute_70.cpp1.ii".
CMake Error at xmrstak_cuda_backend_generated_cuda_extra.cu.o.cmake:266 (message):
  Error generating file
  /home/m1/NVOC/mining/miners/XMR_Stak/xmr-stak/build/CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/./xmrstak_cuda_backend_generated_cuda_extra.cu.o


CMakeFiles/xmrstak_cuda_backend.dir/build.make:70: recipe for target 'CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/xmrstak_cuda_backend_generated_cuda_extra.cu.o' failed
make[2]: *** [CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/xmrstak_cuda_backend_generated_cuda_extra.cu.o] Error 1
CMakeFiles/Makefile2:143: recipe for target 'CMakeFiles/xmrstak_cuda_backend.dir/all' failed
make[1]: *** [CMakeFiles/xmrstak_cuda_backend.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
m1@m1-desktop:~/NVOC/mining/miners/XMR_Stak/xmr-stak/build$

I can raise an issue if you think this is not specific for my rig.

Thanks Smiley

DeepOnion    ▬▬  Anonymous and Untraceable  ▬▬    ENJOY YOUR PRIVACY  •  JOIN DEEPONION
▐▐▐▐▐▐▐▐   ANN  Whitepaper  Facebook  Twitter  Telegram  Discord    ▌▌▌▌▌▌▌▌
Get $ONION  (✔Cryptopia  ✔KuCoin)  |  VoteCentral  Register NOW!  |  Download DeepOnion
LuKePicci
Jr. Member
*
Offline Offline

Activity: 128
Merit: 1


View Profile
May 19, 2019, 11:46:55 PM
 #64

Did you try already to run the compiler script via miners upgrade script? Probably this won't make any difference but…
damNmad
Full Member
***
Offline Offline

Activity: 378
Merit: 104


nvOC forever


View Profile
May 20, 2019, 08:18:56 AM
 #65

Did you try already to run the compiler script via miners upgrade script? Probably this won't make any difference but…

Yes, I have, I tried through it first and then tried independently myself.

DeepOnion    ▬▬  Anonymous and Untraceable  ▬▬    ENJOY YOUR PRIVACY  •  JOIN DEEPONION
▐▐▐▐▐▐▐▐   ANN  Whitepaper  Facebook  Twitter  Telegram  Discord    ▌▌▌▌▌▌▌▌
Get $ONION  (✔Cryptopia  ✔KuCoin)  |  VoteCentral  Register NOW!  |  Download DeepOnion
LuKePicci
Jr. Member
*
Offline Offline

Activity: 128
Merit: 1


View Profile
May 27, 2019, 04:54:23 PM
 #66

It seems like an issue with gcc 5.5 https://stackoverflow.com/questions/50815093/avx512-intrinsics-header-produces-many-errors-after-distro-upgrades-gcc-to-5-5-0

Nothing we could really address guaranteeing then nothing else breaks. Probably it's compiling fine on ubuntu 18.04 based images. Try upgrading gcc on your 16.04 and see what happens to other miners as well.
fk2
Jr. Member
*
Offline Offline

Activity: 67
Merit: 2


View Profile
May 27, 2019, 08:40:02 PM
Last edit: September 18, 2019, 11:36:47 PM by mprep
 #67

Hi, I was running a 1080 rig with nvOC 0019-3.0 all the time with NICE_X16R. Now I wanted to switch to NICE_ETHASH but unfortunetly with nvOC "never touch a running system" is again the truth: nothing works anymore Sad I thought I might need another update and ran bash nvOC upgrade but it didn't update to 3.2 so I thought I do a git clone and 'git submodule update --init --remote miners' but after that I have no nvOC_miner_update.sh script found. therefore nothing happens when I do a nvOC start with 3.2.

tried to go back to X16R but nothing happens. rig is now on idle Sad here is report of 3.2

Code:

Operating System info:
Kernel        :  4.15.0-33-generic
OS            :  Ubuntu 18.04.1 LTS
System        :  (gcc 7.3.0 7.3.0-16ubuntu3)) #36-Ubuntu
nvidia driver :  396.54

nvOC info:
nvOC path     :  /home/m1/NVOC/3.2
nvOC          :  0019-3.2
Report        :  0012
1bash         :  0058
1bash.template:
3main         :  0028
5watchdog     :  0024
6tempcontrol  :  0012
wtm switch    :  0023
wtm profit    :  0004
pool switch   :  0002
minerinfo     :  0013

Hardware info:
Motherboard   :  ASUS PRIME Z270-A  Rev 1.xx
BIOS ver.     :  1203 12/25/2017
CPU Model     :  Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores     :  2 (Cores + Threads)
Mem Total     :         3978180 kB
Mem Free      :         2729752 kB
Swap Total    :               0 kB
Swap Free     :               0 kB
Ethernet      :  Intel I219-V

CUDA SDK version
nvcc path     : /usr/local/cuda/bin/nvcc
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Tue_Jun_12_23:07:04_CDT_2018
Cuda compilation tools, release 9.2, V9.2.148

nvOC is not installed as a service

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN   VENDOR   MODEL             REV MOUNTPOINT
sda    55.9G        disk    0       0 sata   ATA      Patriot Flare    21.1
├─sda1    9M vfat   part    0       0
└─sda2 55.9G ext4   part    0       0                                       /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)

Local git branch and submodules status:
## 3.2-stable...origin/3.2-stable
 M 1bash.template
+64a28c034abccc936045c793ab5567cf2c477f1d miners (remotes/origin/3.2-miners)
## HEAD (no branch)
A  .gitmodules
 M XMR_Stak/2.10.0/xmr-stak.nvoc.sh
 M XMR_Stak/2.10.1/xmr-stak.nvoc.sh
 M XMR_Stak/2.4.4/xmr-stak.nvoc.sh
 M XMR_Stak/2.9.0/xmr-stak.nvoc.sh
+4c529a80c09231893432f55ed4675b52f4df3d62 ETHMINER/0.17.0/src (v0.17.1-rc.0)
+a8a603ea3370f35af78c642adf3db52991e77f86 ETHMINER/0.17.1/src (v0.17.1)
+370684f7435d1256cbabef4410a57ed5bc705fdc TPccminer/src (2.3-tpruvot)
+61e997c3474734590e3f3788de9e8c125eebdeeb XMR_Stak/src (2.9.0)

1bash settings:
1bash version .............: 0058
LOCAL or REMOTE ...........: REMOTE
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO

Watchdog ..................: YES
SYSRQ Reboot ..............: NO
Watchdog Cycle ............: 20
GPU Utilization Threshold .: 70
Alternate Pool ............: NO

Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 50
MAXIMAL_FAN_SPEED .........: 95

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: NO
TELEGRAM_ALERTS ...: NO

HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: YES

POWERLIMIT MODE ...........: GLOBAL
Power Limit WATTS .........: 160
OVERCLOCK MODE ............: GLOBAL
Memory Overclock ..........: 1200
Core Overclock ............: 120

GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: Icemine01
plusCPU ...................: NO

AUTO_SWITCH ...............: NO
COIN ......................: NICE_ETHASH
ALGO ......................: ETHASH
MINER .....................: ETHMINER
NICE_ETHASH WORKER ................: Icemine01
NICE_ETHASH ADDRESS ...............: 39qjQtzn...
NICE_ETHASH POOL ..................: daggerhashimoto.usa.nicehash.com
NICE_ETHASH PORT ..................: 3353



output of master log when starting 3.2:
Code:
m1@m1-desktop:~$nvOC start
nvOC already running, use ./nvOC restart
m1@m1-desktop:~/NVOC/3.2$ bash nvOC master-log
m1@m1-desktop:~$nvOC master-log
tail: cannot open '/home/m1/NVOC/3.2/nvoc_logs/screenlog.0' for reading: No such file or directory
tail: cannot open '/home/m1/NVOC/3.2/nvoc_logs/tempcontrol-screenlog.0' for reading: No such file or directory
tail: cannot open '/home/m1/NVOC/3.2/nvoc_logs/watchdog-screenlog.0' for reading: No such file or directory
tail: cannot open '/home/m1/NVOC/3.2/nvoc_logs/8_wtmautoswitchlog' for reading: No such file or directory
tail: no files remaining
m1@m1-desktop:~/NVOC/3.2$

what to do?

edit: ok found the update script but that is basically the same as doing bash nvOC miners-upgrade which I did including a recomplie all


now from the updated mining folder:
Code:

Operating System info:
Kernel        :  4.15.0-33-generic
OS            :  Ubuntu 18.04.1 LTS
System        :  (gcc 7.3.0 7.3.0-16ubuntu3)) #36-Ubuntu
nvidia driver :  396.54

nvOC info:
nvOC path     :  /home/m1/NVOC/mining
nvOC          :  0019-3.2
Report        :  0012
1bash         :  0058
1bash.template:
3main         :  0028
5watchdog     :  0024
6tempcontrol  :  0012
wtm switch    :  0023
wtm profit    :  0004
pool switch   :  0002
minerinfo     :  0013

Hardware info:
Motherboard   :  ASUS PRIME Z270-A  Rev 1.xx
BIOS ver.     :  1203 12/25/2017
CPU Model     :  Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores     :  2 (Cores + Threads)
Mem Total     :         3978180 kB
Mem Free      :         2684156 kB
Swap Total    :               0 kB
Swap Free     :               0 kB
Ethernet      :  Intel I219-V

CUDA SDK version
nvcc path     : /usr/local/cuda/bin/nvcc
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Tue_Jun_12_23:07:04_CDT_2018
Cuda compilation tools, release 9.2, V9.2.148

nvOC is not installed as a service

HDD and Partion info:
NAME    SIZE FSTYPE TYPE ROTA HOTPLUG TRAN   VENDOR   MODEL             REV MOUNTPOINT
sda    55.9G        disk    0       0 sata   ATA      Patriot Flare    21.1
├─sda1    9M vfat   part    0       0
└─sda2 55.9G ext4   part    0       0                                       /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)

Local git branch and submodules status:
## release...origin/release [ahead 16, behind 220]
M  .gitmodules
M  0cpuminer
UU 0miner
UU 1bash.template
D  1bash.template.lite
M  2unix
M  3main
M  5watchdog
M  6tempcontrol
A  7load_check
M  7miner_restart
A  7miner_schedule
M  7reboot
M  7telegram
M  8wtm_auto_switch
M  8wtm_profit_check
M  9poolswitch
A  LICENSE
UU README.md
A  foreman/miner-watch
A  foreman/package.sh
A  helpers/disabled_gpu.sh
A  helpers/generic_helper.sh
UU miners
M  nvOC
M  www/cgi-bin/minerinfo
U0000000000000000000000000000000000000000 miners
## HEAD (no branch)
-cd6fab68823e247bb84dd1fa0448d5f75ec4917d ANXccminer/src
-baf6c9e4e36c9cc1b67698ee2977d445f598c573 ASccminer/src
-24c65cf166bbb3332d60e2baef859ceb604e5d49 ETHMINER/src
-c5ab73837c8024f1e6b8fe7ad46e6881fb8366e6 KTccminer/src
-bedaf007d4619fc4157aeafb59b44850f08d93f1 KTccminer_cryptonight/src
-7d41d49b92db27b9ab80270adaa92f6b06d1ef78 KXccminer/src
-78dad7dd659eae72a07d2448de62b1946c1f2b41 MSFTccminer/src
-8affcb9cd09edd917d33c1ed450f23400f571bdb NAccminer/src
-9e86bdd24ed7911b698f1d0ef61a4028fcbd13c5 SPccminer/src
-c800f1a803e1b2074ed2a7c15023c096d0772048 SUPRminer/src
-a81ab0f7a557a12a21d716dd03537bc8633fd176 TPccminer/src
-48b170a5828256600ca71e66d4c114af4e114236 VERTMINER/src
-c0ab1734332d6472225d8ac7394f6fcba71aabc9 XMR_Stak/src
-bfd1c002f98f2d63f2174618838afc28cf4ffffe cpuOPT/src

1bash settings:
1bash version .............: 0058
LOCAL or REMOTE ...........: REMOTE
TEAMVIEWER started ........: NO
SSH daemon started ........: YES
SLOW_USB_KEY_MODE .........: NO
SRR .......................: NO

Watchdog ..................: YES
SYSRQ Reboot ..............: NO
Watchdog Cycle ............: 20
GPU Utilization Threshold .: 70
Alternate Pool ............: NO

Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 70
__FAN_ADJUST ..............: 5
POWER_ADJUST ..............: 5
ALLOWED_TEMP_DIFF .........: 2
RESTORE_POWER_LIMIT .......: 85
MINIMAL_FAN_SPEED .........: 50
MAXIMAL_FAN_SPEED .........: 95

CLEAR_LOGS_ON_BOOT ........: NO
AUTO_REBOOT ...............: NO
_Parallax_MODE (upPaste)...: NO

TELEGRAM_MESSAGES .: NO
TELEGRAM_ALERTS ...: NO

HEADLESS MODE:.............: NO
GPUPowerMizerMode_Adjust...: NO
ETH Pill ..................: YES

POWERLIMIT MODE ...........: GLOBAL
Power Limit WATTS .........: 160
OVERCLOCK MODE ............: GLOBAL
Memory Overclock ..........: 1200
Core Overclock ............: 120

GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: Icemine01
plusCPU ...................: NO

AUTO_SWITCH ...............: NO
COIN ......................: NICE_X16R
ALGO ......................: X16R
MINER .....................: BMINER
NICE_X16R WORKER ................: Icemine01
NICE_X16R ADDRESS ...............: 39qjQtzn...
NICE_X16R POOL ..................: x16r.eu.nicehash.com
NICE_X16R PORT ..................: 3366
X16R INTENSITY ..........: 0


at least something happens after bash nvOC start:

Code:
m1@m1-desktop:~$nvOC start
Restarting nvOC tasks....

m1@m1-desktop:~/NVOC/mining$ bash nvOC master-log
m1@m1-desktop:~$nvOC master-log
==> /home/m1/NVOC/mining/nvoc_logs/screenlog.0 <==









==> /home/m1/NVOC/mining/nvoc_logs/tempcontrol-screenlog.0 <==


GPU 0, Target temp: 70, Current: 29, Diff: -41, Fan: 50, Power: 8.75
GPU 1, Target temp: 70, Current: 21, Diff: -49, Fan: 50, Power: 11.84
GPU 2, Target temp: 70, Current: 24, Diff: -46, Fan: 50, Power: 10.55
GPU 3, Target temp: 70, Current: 21, Diff: -49, Fan: 50, Power: 9.22
Mon May 27 16:59:55 EDT 2019 - All good, will check again in 18.0 seconds




==> /home/m1/NVOC/mining/nvoc_logs/watchdog-screenlog.0 <==
 <pid> [...]            send signal to every <pid> listed
 -<signal>, -s, --signal <signal>
                        specify the <signal> to be sent
 -l, --list=[<signal>]  list all signal names, or convert one to a name
 -L, --table            list all signal names in a nice table

 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more details see kill(1).
tail: cannot open '/home/m1/NVOC/mining/nvoc_logs/8_wtmautoswitchlog' for reading: No such file or directory

==> /home/m1/NVOC/mining/nvoc_logs/screenlog.0 <==


==> /home/m1/NVOC/mining/nvoc_logs/tempcontrol-screenlog.0 <==
DISABLED_GPUS not set
Temp Control for nvOC v0019-3.2
Version: v0019-3.2.0012

5264 (process ID) old priority 0, new priority -15
LOG FILE: (Showing the last 10 recorded entries)
WARNING: Sat Nov  3 00:36:32 EDT 2018 - Problem detected! GPU1 is not responding. Will give watchdog 60 seconds to react, if not we will reboot!
WARNING: Sat Nov  3 00:36:47 EDT 2018 - Problem detected! GPU1 is not responding. Will give watchdog 45 seconds to react, if not we will reboot!
WARNING: Mon May 27 10:57:26 EDT 2019 - tempcontrol@[GPU2] Problem detected: nvidia-smi failed to query current status. Watchdog has 60 seconds to react, otherwise we will reboot!
========= SMI Query output with errors @[GPU2]:
57, 85, 160.00, 15.72, GeForce GTX 1080 38, 70, 160.00, 18.00, GeForce GTX 1080 Ti 55, [Unknown Error], 160.00, [Unknown Error], GeForce GTX 1080 Ti 40, 70, 160.00, 18.40, GeForce GTX 1080 Ti
========= End of SMI query output
WARNING: Mon May 27 10:57:47 EDT 2019 - tempcontrol@[GPU2] Problem detected: nvidia-smi failed to query current status. Watchdog has 60 seconds to react, otherwise we will reboot!
========= SMI Query output with errors @[GPU2]:
50, 85, 160.00, 10.26, GeForce GTX 1080 33, 70, 160.00, 14.08, GeForce GTX 1080 Ti 52, [Unknown Error], 160.00, [Unknown Error], GeForce GTX 1080 Ti 35, 70, 160.00, 11.94, GeForce GTX 1080 Ti
========= End of SMI query output



      TEMP_CONTROL v0019-3.2.0012 - nvOC v0019-3.2 - Community Release

Detected: 4 GPU's

GPU 0:  POWER LIMIT: 160,  TARGET TEMP: 70
GPU 1:  POWER LIMIT: 160,  TARGET TEMP: 70
GPU 2:  POWER LIMIT: 160,  TARGET TEMP: 70
GPU 3:  POWER LIMIT: 160,  TARGET TEMP: 70

GLOBAL  FAN_ADJUST (%):  5
GLOBAL  POWER_ADJUST (W):  5
GLOBAL  ALLOWED_TEMP_DIFF (C):  2
GLOBAL  RESTORE_POWER_LIMIT (%):  85
GLOBAL  MINIMAL_FAN_SPEED (%):  50

GPU 0, Target temp: 70, Current: 29, Diff: -41, Fan: 50, Power: 8.26
GPU 1, Target temp: 70, Current: 21, Diff: -49, Fan: 50, Power: 11.25
GPU 2, Target temp: 70, Current: 24, Diff: -46, Fan: 50, Power: 10.65
GPU 3, Target temp: 70, Current: 21, Diff: -49, Fan: 50, Power: 9.02
Mon May 27 17:00:21 EDT 2019 - All good, will check again in 18.0 seconds



but unfortunately no mining, no matter if I choose ETHASH/CLAYMORE/ETHMINER or X16R/ZENEMY/BMINER:

Code:
m1@m1-desktop:~$nvOC miner-log











there was one log back in the days where at least I could saw what command was used to fire up the mining tool but now I dont even see this





FYI: I can do bash nvOC start and then do a screen-dmS miner manually and with
Code:
ethdcrminer64 -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal 39qjQtznWGrsQAcbgQCa4VjQyMonzDNSUK -epsw x -esm 3 -allpools 1 -estale 0 

the rig is running fine. Seriously: Why do I always have problems with nvOC after every single update/change process? Why are there dozens of logs if none of them help me in any way? What is the best way to check for problems in nvOC anyways?

Once I chose this OS because of the great features like profitswitching etc but nowadays I am just happy if it mines?!



I deleted all nvoc folders and cloned git again and things are working. besides ethminer&nicehash, wont start. claymore works
papampi (OP)
Full Member
***
Offline Offline

Activity: 686
Merit: 140


Linux FOREVER! Resistance is futile!!!


View Profile WWW
May 30, 2019, 04:38:17 AM
 #68

I deleted all nvoc folders and cloned git again and things are working. besides ethminer&nicehash, wont start. claymore works

Glad its working ...

Ethminer has some changes in latest versions 
Read 1bash additional info on ethminer
Code:
ETHASH_WALLET_FORMAT="$WALLET_ADDRESS_FORMAT"       # Some pools require to use "%2e" instead of "." More examples available :https://github.com/ethereum-mining/ethminer/blob/master/docs/POOL_EXAMPLES_ETH.md

LuKePicci
Jr. Member
*
Offline Offline

Activity: 128
Merit: 1


View Profile
May 31, 2019, 07:05:07 PM
 #69

FYI: I can do bash nvOC start and then do a screen-dmS miner manually and with
Code:
ethdcrminer64 -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal 39qjQtznWGrsQAcbgQCa4VjQyMonzDNSUK -epsw x -esm 3 -allpools 1 -estale 0 

the rig is running fine. Seriously: Why do I always have problems with nvOC after every single update/change process? Why are there dozens of logs if none of them help me in any way? What is the best way to check for problems in nvOC anyways?

Once I chose this OS because of the great features like profitswitching etc but nowadays I am just happy if it mines?!

We completely reworked a few very important things from 3.0 to 3.2, this means you are basically required to update your config from a fresh new 1bash template (you should have seen a warning about that during the upgrade if you used our managed script). Another aspect not to underestimate is that if you upgrade not so often it is very likely that also the miners you are currently used to implement something new to take care, and with lot of new things it's very difficult to troubleshoot the issues.

About the logs, those errors about no logs available are just the consequence of nvOC didn't start correctly, so there were still no logs to look at. The only log you should look at if nvOC fails to start its components is the master log, which is not available via nvOC cmdlet if you run nvOC into gnome-terminal - which is both your and default default. Your only option in such case is to access your rig via TeamViewer/vnc to see the gnome terminal window. Of course both ssh and TeamViewer gets automatically enable in such failure situations to prevent you get locked out.

I'm not sure what was the root cause of your issues where you said "I thought I might need another update and ran bash nvOC upgrade but it didn't update to 3.2". Did you save some outputs of the upgrade command? Then, what you attempted afterwards was likely not correct because the point upgrade is not so easy to handle manually via git commands - that's why the upgrade cmdlet exists. From your reports, I see you explicitly cloned 3.2-stable branch. This means your upgrade path won't jump to future point releases. I guess you were on 3.0-stable before. This is fine if you want to take control over the upgrade path and not getting major updates, but if you expected to get the new 3.2 release doing nvOC upgrade you should consider switching to "release" branch instead - which is the default one in firstboot settings.
Bmoop
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
June 02, 2019, 11:48:58 AM
 #70

Hi all,

after i did big update for NVOC - I cant open the screen (screen -x miner) to miner-machine.
If I want open the screen then I get follow message
"There is no screen to be attached matching miner"

If I open over browser then I get follow message
"Gpu Count: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."
and
"GPU Utilization: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."

Cards are 8 * GTX1060


Please, can me anyone say, how I can install the lastest NVIDIA driver? And will this fix this problem/message?

Many thx for you help!
papampi (OP)
Full Member
***
Offline Offline

Activity: 686
Merit: 140


Linux FOREVER! Resistance is futile!!!


View Profile WWW
June 02, 2019, 01:21:24 PM
 #71

Hi all,

after i did big update for NVOC - I cant open the screen (screen -x miner) to miner-machine.
If I want open the screen then I get follow message
"There is no screen to be attached matching miner"

If I open over browser then I get follow message
"Gpu Count: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."
and
"GPU Utilization: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."

Cards are 8 * GTX1060


Please, can me anyone say, how I can install the lastest NVIDIA driver? And will this fix this problem/message?

Many thx for you help!


Check my earlier post on this problem
let us know if it solves your problem or not
https://bitcointalk.org/index.php?topic=5129295.msg50597130#msg50597130
 

Bmoop
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
June 02, 2019, 05:15:06 PM
 #72

I did try your older post

sudo apt install --reinstall nvidia-410

and

sudo apt install nvidia-418

I get for both actions the message "Unable to locate package....."

I think I need a fool-proof description  Huh
LuKePicci
Jr. Member
*
Offline Offline

Activity: 128
Merit: 1


View Profile
June 02, 2019, 10:44:56 PM
 #73

Run
Code:
sudo apt-get update
then retry. Which nvOC os image are you using?
Bmoop
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
June 03, 2019, 04:44:25 AM
 #74

The Update was a lot of Auto-Updates.

I did try also to download current OS but the download has always errors on unzipp.
papampi (OP)
Full Member
***
Offline Offline

Activity: 686
Merit: 140


Linux FOREVER! Resistance is futile!!!


View Profile WWW
June 03, 2019, 10:20:23 AM
 #75

Auto update is disabled by default, so you get the no package found

You should enable updates in "Software & Updates" in "Updates" tab.

Or you can use the latest image with nvidia-418 pre installed.

Download-pre-built-OS-images

Bmoop
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
June 03, 2019, 02:59:03 PM
 #76

Can I install the newest Image and set in/use with the old "1bash-file" ?  Or were there any changes to the new image?

Many  thx for your help!

BR
LuKePicci
Jr. Member
*
Offline Offline

Activity: 128
Merit: 1


View Profile
June 05, 2019, 12:03:32 AM
 #77

Safe answer: no, you cannot.

Actually it depends on the version of nvOC you're running on your current image.
WaveFront
Member
**
Offline Offline

Activity: 126
Merit: 10


View Profile
June 05, 2019, 07:36:56 PM
 #78

Hello,
I just tried to install nvOC 19-3.2, Ubuntu 16.04, Cuda 9.2, Nvidia 418, 2019-05-02

After the first boot, after resizing the partition, I get an error message:

error : unknown filesystem
Entering rescue mode...
grub rescue>

Is there anything I can do. What might be wrong?

cheers
Luca
LuKePicci
Jr. Member
*
Offline Offline

Activity: 128
Merit: 1


View Profile
June 06, 2019, 08:55:11 AM
 #79

Something went damn wrong during partition auto-expand, retry with partition expansion enabled, and see what happens. If it still doesn't work, reinstall with disabled auto-expand and do it manually from Gparted once you get in normally. Let me know.

Some logs for this kind of issue during firstboot should be found into the small fat partition if you manage to read it somehow.
WaveFront
Member
**
Offline Offline

Activity: 126
Merit: 10


View Profile
June 06, 2019, 03:25:18 PM
Last edit: September 18, 2019, 11:40:24 PM by mprep
 #80

Hey Luke,

Thanks for your answer.
The partition auto-expand is starting automatically after first boot.
Is there a way to stop partition auto-expand?
I cannot find any option related to partitioning on 1bash

Cheers
Luca



Hello Luke,

Didn't notice that I just have to edit the firstboot.json

Will try this.

Cheers
Luca
Pages: « 1 2 3 [4] 5 6 7 8 9 10 11 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!