papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 13, 2019, 03:32:13 PM Last edit: September 18, 2019, 09:52:03 PM by mprep |
|
NBMiner updated to 22.1v22.1(2019-04-12) Change Log: - Add support for mining Swap (XWP).
- Improve Grin29 & AEperformance.
- Improve Windows compatibility on Grin & AE, significant boost on performance.
GMiner updated to 1.38v1.38 Change Log: - Added 4GB solver for grin29 and swap (will works under linux and windows 7 on 4GB cards)
To get latest updates, Run: bash ~/NVOC/mining/nvOC upgrade
Heads up to those whom enabled updates in their system. (By default its disabled) I just updated a rig to test and check for a new image and got into a problem. It updated the kernel to 4.4.0-145 but after reboot rig failed to start mining I got this message when ran nvidia-smi: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver To solve the issue you should do either of these steps: a- reinstall nvidia-410 with sudo apt install --reinstall nvidia-410 b- install latest nvidia-418 with: sudo apt install nvidia-418
Reminder: Never update nvidia driver or system while miner is running or you get into login screen cant login and get back to login screen. Stop nvoc with bash ~/NVOC/mining/nvOC stop Then update your system or driver BMiner updated to 15.5.015.5.0 Change Log: - Improve the performance of the Cuckatoo algorithm.
- Support dual-mining ETH and VBK.
- Add the parameter -version to output the version and exit.
To get latest updates, Run: bash ~/NVOC/mining/nvOC upgrade
|
|
|
|
|
|
|
|
Remember that Bitcoin is still beta software. Don't put all of your money into BTC!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
dhan000
|
|
April 18, 2019, 01:28:24 PM Last edit: April 18, 2019, 01:45:23 PM by dhan000 |
|
Hello I'm sending this message with google translate. When the ubuntu is switched on, I can operate the terminal automatically. but when sudo is given the command prompts me for the password. How can I prevent the password from prompting? I want the sudo command to run without asking for the password. As is the NVOC. how can I do that.
Ubuntu 18.04
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 18, 2019, 02:16:11 PM |
|
Hello I'm sending this message with google translate. When the ubuntu is switched on, I can operate the terminal automatically. but when sudo is given the command prompts me for the password. How can I prevent the password from prompting? I want the sudo command to run without asking for the password. As is the NVOC. how can I do that.
Ubuntu 18.04
This should do the trick Append the following to run ALL command without a password for user named john: john ALL=(ALL) NOPASSWD:ALL
|
|
|
|
dhan000
|
|
April 18, 2019, 03:00:00 PM |
|
I'm sending this message with google translate. it does not happen that you have written. There is no such thing as NVOC. used a different method. NVOC visudo # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"
# Host alias specification
# User alias specification
# Cmnd alias specification
# User privilege specification root ALL=(ALL:ALL) ALL
# Members of the admin group may gain root privileges %admin ALL=(ALL) ALL
# Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL
# See sudoers(5) for more information on "#include" directives:
#includedir /etc/sudoers.d
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 20, 2019, 06:12:15 AM |
|
I'm sending this message with google translate. it does not happen that you have written. There is no such thing as NVOC. used a different method. NVOC visudo # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"
# Host alias specification
# User alias specification
# Cmnd alias specification
# User privilege specification root ALL=(ALL:ALL) ALL
# Members of the admin group may gain root privileges %admin ALL=(ALL) ALL
# Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL
# See sudoers(5) for more information on "#include" directives:
#includedir /etc/sudoers.d
Did you restart your session after appending the line ? nvOC image is created by fullzero, I have no idea how he done it. Will check and see if I can find how its done in nvOC.
|
|
|
|
LuKePicci
Jr. Member
Offline
Activity: 128
Merit: 1
|
|
April 21, 2019, 03:27:13 PM |
|
Append the following to run ALL command without a password for user named john: john ALL=(ALL) NOPASSWD:ALL Yes, we have something like that for m1 user.
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 21, 2019, 04:59:59 PM |
|
Append the following to run ALL command without a password for user named john: john ALL=(ALL) NOPASSWD:ALL Yes, we have something like that for m1 user. Thanks for clarify Yup, its in "/etc/sudoers.d/90-m1" m1@m1-desktop:~$ sudo cat /etc/sudoers.d/90-m1 m1 ALL=(ALL) NOPASSWD:ALL
|
|
|
|
Brainfruit_Me
Newbie
Offline
Activity: 23
Merit: 0
|
|
April 22, 2019, 02:43:46 AM Last edit: September 18, 2019, 09:53:59 PM by mprep |
|
I'm having a problem on new flashed images where the miner temp control bugs out and causes Nvidia driver errors? Tried flashing multiple versions of nvOC. Any thoughts?
I cross posted this to the discord bug reports with images. Can't post photos here yet as my account is newb
So I reverted to loading from disk image 19-2.1 and it is working fine now. I had previously been loading from image 19-3.X
There were no issues until recently.
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 22, 2019, 07:07:18 AM Last edit: April 22, 2019, 01:48:14 PM by papampi |
|
I'm having a problem on new flashed images where the miner temp control bugs out and causes Nvidia driver errors? Tried flashing multiple versions of nvOC. Any thoughts?
I cross posted this to the discord bug reports with images. Can't post photos here yet as my account is newb
It looks like an Nvidia driver update before rebooting error, have you tried rebooting the rig and see if it still gives that error?
|
|
|
|
sikke1
Jr. Member
Offline
Activity: 44
Merit: 18
|
|
April 23, 2019, 09:46:19 AM |
|
If anyone wonders. nvOC supports up to 19 GPUs with ASUS B250 Mining Expert. nvOC supports Nvidia P106 and P104 mining cards.
|
|
|
|
Tigel
Newbie
Offline
Activity: 66
Merit: 0
|
|
April 24, 2019, 03:53:19 AM |
|
Tried to upgrade T-Rex to cuda 10 version. extracted 9.2 to fresh directory and made symblic link: m1@miner-075:~/NVOC/mining/miners/T_Rex$ ls -la recommended lrwxrwxrwx 1 m1 m1 47 Apr 24 06:30 recommended -> /home/m1/NVOC/mining/miners/T_Rex/0.9.2-cuda10/ m1@miner-075:~/NVOC/mining/miners/T_Rex$ ls -la recommended/ total 18328 drwxrwxr-x 2 m1 m1 4096 Apr 24 06:26 . drwxrwxr-x 5 m1 m1 4096 Apr 24 06:30 .. -rw-rw-r-- 1 m1 m1 3876 Feb 3 12:57 config_example -rwx------ 1 m1 m1 9980164 Feb 3 13:03 t-rex -rw-rw-r-- 1 m1 m1 8757091 Feb 3 13:13 t-rex-0.9.2-linux-cuda10.0.tar.gz -rw-rw-r-- 1 m1 m1 15758 Feb 3 12:57 t-rex-help.txt m1@miner-075:~/NVOC/mining/miners/T_Rex$
I get error stating /home/m1/NVOC/mining/miners/T_Rex/recommended not found, check your settings. What I might be missing ?
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 24, 2019, 12:26:35 PM |
|
Tried to upgrade T-Rex to cuda 10 version. extracted 9.2 to fresh directory and made symblic link: m1@miner-075:~/NVOC/mining/miners/T_Rex$ ls -la recommended lrwxrwxrwx 1 m1 m1 47 Apr 24 06:30 recommended -> /home/m1/NVOC/mining/miners/T_Rex/0.9.2-cuda10/ m1@miner-075:~/NVOC/mining/miners/T_Rex$ ls -la recommended/ total 18328 drwxrwxr-x 2 m1 m1 4096 Apr 24 06:26 . drwxrwxr-x 5 m1 m1 4096 Apr 24 06:30 .. -rw-rw-r-- 1 m1 m1 3876 Feb 3 12:57 config_example -rwx------ 1 m1 m1 9980164 Feb 3 13:03 t-rex -rw-rw-r-- 1 m1 m1 8757091 Feb 3 13:13 t-rex-0.9.2-linux-cuda10.0.tar.gz -rw-rw-r-- 1 m1 m1 15758 Feb 3 12:57 t-rex-help.txt m1@miner-075:~/NVOC/mining/miners/T_Rex$
I get error stating /home/m1/NVOC/mining/miners/T_Rex/recommended not found, check your settings. What I might be missing ? nvOC images dont have cuda-10 pre installed you should install cuda 10
|
|
|
|
Tigel
Newbie
Offline
Activity: 66
Merit: 0
|
|
April 24, 2019, 04:44:24 PM |
|
nvOC images dont have cuda-10 pre installed you should install cuda 10
Did that, thanks!! Also it seems I had forgot to copy nvoc-miner.json over from t-rex 0.9.2 cuda directory. -- Tigel
|
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
April 28, 2019, 03:56:16 PM |
|
Hello all, I must be blind as a bat, but I cannot find the download image link of the latest stable version. Can you help me? Cheers
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 28, 2019, 04:31:27 PM |
|
Hello all, I must be blind as a bat, but I cannot find the download image link of the latest stable version. Can you help me? Cheers
Have a look at nvOC GitHub Wiki Download-pre-built-OS-images
|
|
|
|
akokkon
Newbie
Offline
Activity: 15
Merit: 0
|
|
April 29, 2019, 07:17:36 AM Last edit: April 29, 2019, 10:40:16 AM by akokkon |
|
Why the algo_specific_oc is not working ?
the hashrate is the same as OC core=0 and mem=0
My system is based on nvOC_19-3.x_U16.04_Cuda_8-9.2_N410_2018-10-27.7z and on the automated upgrades (NVOC V0019-3.2)
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 29, 2019, 07:39:34 AM |
|
Why the algo_specific_oc seems not working ?
the hashrate is the same as OC core=0 and mem=0
My system is based on nvOC_19-3.x_U16.04_Cuda_8-9.2_N410_2018-10-27.7z and on the automated upgrades (nvidia 410 1bash 3.2)
Run this command to check the core and mem values with and without oc : bash ~/NVOC/mining/nvOC gpuinfo
|
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
April 29, 2019, 10:38:32 AM |
|
Hello all, I must be blind as a bat, but I cannot find the download image link of the latest stable version. Can you help me? Cheers
Have a look at nvOC GitHub Wiki Download-pre-built-OS-imagesThank you so much Papampi
|
|
|
|
akokkon
Newbie
Offline
Activity: 15
Merit: 0
|
|
April 29, 2019, 11:36:50 AM |
|
as i wrote before the gpuinfo prints the same results before and after algo_specific _oc
|
|
|
|
papampi (OP)
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
April 29, 2019, 12:03:12 PM |
|
as i wrote before the gpuinfo prints the same results before and after algo_specific _oc
Does it show nvidia-settings applying OC values after miner restart on gnome-terminal? Please set OVERCLOCK_MODE to " NO", "GLOBAL" and "ALGO_SPECIFIC" with different values. Restart NVOC after editing 1bash with: bash ~/NVOC/mining/nvOC restart
Check if gnome-terminal shows nvidia-settings applying OC values or not Run report command after every nvOC restart and post results. bash ~/NVOC/mining/nvOC report
|
|
|
|
|