Topic: [OS] nvOC easy-to-use Linux Nvidia Mining - page 18. (Read 418313 times)
My 11x1070 is also mining without issues on BTG, no rejects at all. Check your settings or ask in ewnf miner thread.
ewbf 0.4 is the latest one for new equihash variants
read here: https://bitcointalksearch.org/topic/ewbfs-cuda-equihash-miner-06-4466962
We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".
If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.
read here: https://bitcointalksearch.org/topic/ewbfs-cuda-equihash-miner-06-4466962
We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".
If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.
Got it! Thanks for the info LuKePicci.
Quiet confusing...
My rigs work fine with equihash-MPH
but when I switch to BTG mining (EWBF v0.4) it was working with lots of rejects and eventually rig start to loosing cards/rebooting itself.
Last time before reboot 3 cards show 0 hash rate. This rig has 13 gtx1080
Also My BTG-MPH dashboard shows 0 kh/s all the time.
so I switched back to ZCL.
Now I'm trying to understand what I was doing wrong.
Can you help me?
What are your BTG settings?
These are working with no problems for me
Code:
# Bitcoin Gold (BTG)
BTG_ADDRESS="username"
BTG_EXTENSION_ARGUMENTS="--algo 144_5 --pers BgoldPoW"
BTG_POOL="europe.equihash-hub.miningpoolhub.com"
BTG_PORT="20595"
BTG_WORKER="$WORKERNAME"
ewbf 0.4 is the latest one for new equihash variants
read here: https://bitcointalksearch.org/topic/ewbfs-cuda-equihash-miner-06-4466962
We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".
If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.
read here: https://bitcointalksearch.org/topic/ewbfs-cuda-equihash-miner-06-4466962
We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".
If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.
Got it! Thanks for the info LuKePicci.
Quiet confusing...
My rigs work fine with equihash-MPH
but when I switch to BTG mining (EWBF v0.4) it was working with lots of rejects and eventually rig start to loosing cards/rebooting itself.
Last time before reboot 3 cards show 0 hash rate. This rig has 13 gtx1080
Also My BTG-MPH dashboard shows 0 kh/s all the time.
so I switched back to ZCL.
Now I'm trying to understand what I was doing wrong.
Can you help me?
ewbf 0.4 is the latest one for new equihash variants
read here: https://bitcointalksearch.org/topic/ewbfs-cuda-equihash-miner-06-4466962
We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".
If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.
read here: https://bitcointalksearch.org/topic/ewbfs-cuda-equihash-miner-06-4466962
We call those new variants in nvOC as "Zhash", as WTM does and we refer to this new ewbf miner for new variants as "z_ewbf".
The old ewbf 0.3.3 and 0.3.4 which we refer to as simply "ewbf" 3_3 and 3_4 are two miners you can use for the classic equihash variant, which we refer to as simply "equihash".
If you think ewbf author did a bad choice in naming the new miner (for us: z_ewbf) again as "EWBF Equihash Cuda miner" and versioning it the same way such that now officially exists both "ewbf 0.3.3" and "ewbf 0.3" where the second one is newer and a totally different miner for different algos (note: the new miner does not support the classic equihash algo) then I will support you if you would like to start a campaign to get the new miner renamed to anything different.
Thank you guys for nvOC v19.2.1
It works great! trying to mining BTG
The only issue I still can not upgrade EWBF to v3.0
I already run
cd ~/NVOC/mining
bash nvOC upgrade and miner upgrade
I upgraded NVidia driver to 390 version
but it always starts EWBF v0.4 with lots of rejects
Can you help me how to get EWBF v3.0 ruining?
also why do we need to set up BTG wallet address if we use MPH?
It works great! trying to mining BTG
The only issue I still can not upgrade EWBF to v3.0
I already run
cd ~/NVOC/mining
bash nvOC upgrade and miner upgrade
I upgraded NVidia driver to 390 version
but it always starts EWBF v0.4 with lots of rejects
Can you help me how to get EWBF v3.0 ruining?
also why do we need to set up BTG wallet address if we use MPH?
@fk2 I can't see any error from the miner output in any of logs you reported, try repeating the same thing using miner-log instead of master-log to focus only on miner output. Also report here the output you see in the gnome terminal including the "SCREEN …" command line used to launch the miner. Repeat all those tests with watchdog disabled otherwise it is hard to debug given it continuously try to recover
ewbf is closed source so you can't compile it, for the others may be you need a recompile but let's check if this is the actual issue.
@parentibule you still have nvCO installed as a service you have to uninstall or disable it by doing "sudo systemctl disable nvoc"
ewbf is closed source so you can't compile it, for the others may be you need a recompile but let's check if this is the actual issue.
@parentibule you still have nvCO installed as a service you have to uninstall or disable it by doing "sudo systemctl disable nvoc"
So, now I have the same problem:
Quote
m1@m1-desktop:~$/home/m1/NVOC/m1_2.1/nvOC restart
enabled
Stopping nvOC service..
Starting nvOC service..
● nvoc.service - nvOC Service
Loaded: loaded (/etc/systemd/system/nvoc.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Wed 2018-07-25 17:53:21 CEST; 733ms ago
Process: 5744 ExecStart=/usr/bin/screen -c /home/m1/NVOC/m1_2.1/screenrc-main -dmSL main /bin/bash /home/m1/NVOC/m1_2.
Main PID: 5746 (code=exited, status=1/FAILURE)
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Unit entered failed state.
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Failed with result 'exit-code'.
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Service hold-off time over, scheduling restart.
Jul 25 17:53:21 m1-desktop systemd[1]: Stopped nvOC Service.
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Start request repeated too quickly.
Jul 25 17:53:21 m1-desktop systemd[1]: Failed to start nvOC Service.
enabled
Stopping nvOC service..
Starting nvOC service..
● nvoc.service - nvOC Service
Loaded: loaded (/etc/systemd/system/nvoc.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Wed 2018-07-25 17:53:21 CEST; 733ms ago
Process: 5744 ExecStart=/usr/bin/screen -c /home/m1/NVOC/m1_2.1/screenrc-main -dmSL main /bin/bash /home/m1/NVOC/m1_2.
Main PID: 5746 (code=exited, status=1/FAILURE)
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Unit entered failed state.
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Failed with result 'exit-code'.
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Service hold-off time over, scheduling restart.
Jul 25 17:53:21 m1-desktop systemd[1]: Stopped nvOC Service.
Jul 25 17:53:21 m1-desktop systemd[1]: nvoc.service: Start request repeated too quickly.
Jul 25 17:53:21 m1-desktop systemd[1]: Failed to start nvOC Service.
Atfer some time mining ETH with 2.1 beta and enlargement pill I wanted to test further with mining VTC. But miner simply won't start again. I disabled OC GPUs to make sure no OC problem is the case but still no success. I did a nvOC upgrade but still no success:
edit: same with MONA
edit2: tried with vertminer instead of Tpccminer:
edit3: same problem with ZEN/EWBF
edit4: ZEN/DSTM works! should I upgrade or recompile miner software with bash nvOC??
Code:
Operating System info:
Kernel : 4.4.0-97-generic
OS : Ubuntu 16.04.3 LTS
System : (gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
nvidia driver : 387.34
nvOC info:
nvOC path : /home/m1/NVOC/testing
nvOC : nvOC_Ver=nvOC v0019-2.1 - Community Release" # Do not edit this
Report : 0012
1bash : v0019-2.1.0029
1bash.template: 0033
3main : 0024
5watchdog : 0020
6tempcontrol : 0006
wtm switch : 0022
wtm profit : 0004
pool switch : 0002
minerinfo : 0009
Hardware info:
Motherboard : ASUS STRIX Z270F GAMING Rev 1.xx
BIOS ver. : 1203 12/26/2017
CPU Model : Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores : 2 (Cores + Threads)
Mem Total : 3984516 kB
Mem Free : 2975756 kB
Swap Total : 0 kB
Swap Free : 0 kB
Ethernet : Intel I219-V
CUDA SDK version
nvcc path : /usr/local/cuda-8.0/bin/nvcc
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Tue_Jan_10_13:22:03_CST_2017
Cuda compilation tools, release 8.0, V8.0.61
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 51.9G ext4 part 0 0 /
└─sda3 4G swap part 0 0
VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1)
Local git branch and submodules status:
## 19-2.1...origin/19-2.1
+dadc77df1f6fbe67005260c18880f0985502405b miners (heads/19-2.1)
## HEAD (no branch)
-cd6fab68823e247bb84dd1fa0448d5f75ec4917d ANXccminer/src
-aafe2d19b6d9eb07d942d70ced3049e9aed1c241 ASccminer/src
-31865e0b846ad98e2ce99aeb9b28bb51d3be22db KTccminer-cryptonight/src
-c5ab73837c8024f1e6b8fe7ad46e6881fb8366e6 KTccminer/src
-7d41d49b92db27b9ab80270adaa92f6b06d1ef78 KXccminer/src
-78dad7dd659eae72a07d2448de62b1946c1f2b41 MSFTccminer/src
-8affcb9cd09edd917d33c1ed450f23400f571bdb NAccminer/src
-9e86bdd24ed7911b698f1d0ef61a4028fcbd13c5 SPccminer/src
-c800f1a803e1b2074ed2a7c15023c096d0772048 SUPRminer/src
-a81ab0f7a557a12a21d716dd03537bc8633fd176 TPccminer/src
-bfd1c002f98f2d63f2174618838afc28cf4ffffe cpuOPT/src
-48b170a5828256600ca71e66d4c114af4e114236 vertminer/src
-c0ab1734332d6472225d8ac7394f6fcba71aabc9 xmr-stak/src
1bash settings:
1bash version .............: v0019-2.1.0029
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 ............: 15
GPU Utilization Threshold .: 70
Alternate Pool ............: NO
Temp Control ..............: YES
MANUAL_FAN ................: NO
TARGET_TEMP ...............: 65
__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 ...........: GPU_SPECIFIC
GPU0 Power Limit ..........: 170
GPU1 Power Limit ..........: 160
GPU2 Power Limit ..........: 160
GPU3 Power Limit ..........: 120
OVERCLOCK MODE ............: NO
GLOBAL WORKERNAME .........: YES
AUTO WORKERNAME ...........: CUSTOM
WORKERNAME ................: LuisenMine02
plusCPU ...................: NO
AUTO_SWITCH ...............: NO
COIN ......................: VTC
ALGO ......................: LYRA2V2
MINER .....................: TPccminer
VTC WORKER ................: LuisenMine02
VTC ADDRESS ...............: LuisenMi...
VTC POOL ..................: hub.miningpoolhub.com
VTC PORT ..................: 20507
LYRA2V2 INTENSITY ..........: 0
Code:
m1@m1-desktop:~$nvOC master-log
==> /home/m1/NVOC/testing/nvoc_logs/screenlog.0 <==
==> /home/m1/NVOC/testing/nvoc_logs/tempcontrol-screenlog.0 <==
GLOBAL MINIMAL_FAN_SPEED (%): 50
GPU 0, Target temp: 65, Current: 29, Diff: 36, Fan: 50, Power: 12.15
GPU 1, Target temp: 65, Current: 31, Diff: 34, Fan: 50, Power: 10.78
GPU 2, Target temp: 65, Current: 28, Diff: 37, Fan: 50, Power: 11.13
GPU 3, Target temp: 65, Current: 32, Diff: 33, Fan: 50, Power: 8.56
Wed Jul 25 01:09:34 MST 2018 - All good, will check again in 18.0 seconds
==> /home/m1/NVOC/testing/nvoc_logs/watchdog-screenlog.0 <==
Wed Jul 25 01:08:06 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:08:41 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:09:15 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:09:33 MST 2018 - [INFO] - Watchdog is starting
Connection to google.com 443 port [tcp/https] succeeded!
Giving miner enough to stabilize
Wed Jul 25 01:09:50 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
tail: cannot open '/home/m1/NVOC/testing/nvoc_logs/8_wtmautoswitchlog' for reading: No such file or directory
edit: same with MONA
edit2: tried with vertminer instead of Tpccminer:
Code:
Wed Jul 25 01:23:28 MST 2018 - All good, will check again in 18.0 seconds
==> /home/m1/NVOC/testing/nvoc_logs/screenlog.0 <==
SCREEN -c /home/m1/NVOC/testing/screenrc-miner -dmSL miner /home/m1/NVOC/testing/miners/vertminer/ccminer -a lyra2v2 -o stratum+tcp://hub.miningpoolhub.com:20507 -u LuisenMine2.LuisenMine02 -p x -i 0
*** vertminer 1.0.2 for nVidia GPUs by turekaj ***
Built with the nVidia CUDA Toolkit 8.0
Originally based on tpruvot ccminer
VTC donation address: VdMVwYLairTcYhz3QnNZtDNrB2wpaHE21q (turekaj)
1 percent dev fee to turekaj for miner improvements
1 percent dev fee to Vertcoin Dev Team (vertcoin.org)
==> /home/m1/NVOC/testing/nvoc_logs/tempcontrol-screenlog.0 <==
Temp Control for nvOC nvOC v0019-2.1 - Community Release
Version: nvOC v0019-2.1 - Community Release.0006
2883 (process ID) old priority 0, new priority -15
LOG FILE: (Showing the last 10 recorded entries)
WARNING: Fri Jun 29 05:16:44 MST 2018 - Problem detected! GPU0 is not responding. Will give watchdog 60 seconds to react, if not we will reboot!
WARNING: Fri Jun 29 05:19:15 MST 2018 - Problem detected! GPU0 is not responding. Will give watchdog 45 seconds to react, if not we will reboot!
WARNING: Fri Jun 29 05:36:02 MST 2018 - Problem detected! GPU0 is not responding. Will give watchdog 60 seconds to react, if not we will reboot!
WARNING: Fri Jun 29 05:37:32 MST 2018 - Problem detected! GPU0 is not responding. Will give watchdog 45 seconds to react, if not we will reboot!
WARNING: Fri Jun 29 05:39:02 MST 2018 - Problem detected! GPU0 is not responding. Will give watchdog 30 seconds to react, if not we will reboot!
WARNING: Mon Jul 16 11:38:55 MST 2018 - Problem detected! GPU1 is not responding. Will give watchdog 60 seconds to react, if not we will reboot!
TEMP_CONTROL nvOC v0019-2.1 - Community Release.0006 by leenoox
Detected: 4 GPU's
GPU 0: POWER LIMIT: 170, TARGET TEMP: 65
GPU 1: POWER LIMIT: 160, TARGET TEMP: 65
GPU 2: POWER LIMIT: 160, TARGET TEMP: 65
GPU 3: POWER LIMIT: 120, TARGET TEMP: 65
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: 65, Current: 32, Diff: 33, Fan: 50, Power: 19.64
GPU 1, Target temp: 65, Current: 32, Diff: 33, Fan: 50, Power: 10.88
GPU 2, Target temp: 65, Current: 29, Diff: 36, Fan: 50, Power: 10.79
GPU 3, Target temp: 65, Current: 33, Diff: 32, Fan: 50, Power: 8.66
Wed Jul 25 01:23:42 MST 2018 - All good, will check again in 18.0 seconds
==> /home/m1/NVOC/testing/nvoc_logs/watchdog-screenlog.0 <==
Watchdog for nvOC nvOC v0019-2.1 - Community Release
Version: nvOC v0019-2.1 - Community Release.0020
LOG FILE: (Showing the last 10 recorded entries)
Wed Jul 25 01:16:14 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:16:48 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:17:23 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:17:57 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:18:32 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:20:04 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:20:39 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:21:13 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:22:49 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:23:23 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
Wed Jul 25 01:23:41 MST 2018 - [INFO] - Watchdog is starting
Connection to google.com 443 port [tcp/https] succeeded!
Giving miner enough to stabilize
Wed Jul 25 01:23:58 MST 2018 - [WARNING] - Miner not running, reinit nvOC from scratch
==> /home/m1/NVOC/testing/nvoc_logs/tempcontrol-screenlog.0 <==
GPU 0, Target temp: 65, Current: 31, Diff: 34, Fan: 50, Power: 11.46
GPU 1, Target temp: 65, Current: 32, Diff: 33, Fan: 50, Power: 10.88
GPU 2, Target temp: 65, Current: 29, Diff: 36, Fan: 50, Power: 11.13
GPU 3, Target temp: 65, Current: 33, Diff: 32, Fan: 50, Power: 8.31
Wed Jul 25 01:24:02 MST 2018 - All good, will check again in 18.0 seconds
edit3: same problem with ZEN/EWBF
edit4: ZEN/DSTM works! should I upgrade or recompile miner software with bash nvOC??
@parentibule you messed up something, I see you are running commands from an home directory of an user named 'm1_2.1'. Have you intentionally did this or you were just trying to put nvOC into a different folder? If you know how Windows users profile works, you know that there exist a folder for each user in C:\Users\ for example my user folder is C:\Users\LuKe. In Ubuntu that is the same thing but every user has a folder inside the /home directory, so in nvOC images the default user is 'm1', therefore exists a folder /home/m1 which is the place where all user files need to be. If you created a new user named 'm1_2.1' then it is correct that such /home/m1_2.1 folder exists, but in such a case you did a horrible choice in placing nvOC files inside his home folder because Ubuntu uses that folder to store all system files related to that user, that's why the default location for nvoc files in prebuilt images is '/home/m1/NVOC/something', /home/m1 is the home folder for m1 user, NVOC is just a folder like any other. If, instead, you choosed to place nvOC files inside an arbitrary folder name /home/m1_2.1 but you created no user named m1_2.1 then you did a mistake, reinstall nvOC into another folder. Remember that the default m1 user is a NOPASSWD sudoer, he can reboot doing 'sudo reboot' without being asked for credentials. Don't care the nvOC as a service mode, it is an alternative to gnome for who really needs it.
I don't know why I done this! It's clearly totally stupid :/ Thanks for your explanations. full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
I can see this message on MPH WebPage :
I think nvOC miners needs to be updated with Claymore v11.9 (For those are using this miner software)
https://bitcointalksearch.org/topic/claymores-dual-ethereum-amdnvidia-gpu-miner-v150-windowslinux-1433925
EDIT : Those who had update to nvOC 19.2.1 have Claymore v11.9. Sorry for this useless alert if you updated
Quote
"- Ethereum block height passed 6000000. If you are using old version of claymore your mining would be stopped due to epoch error. Please update to latest version. Claymore miner
I think nvOC miners needs to be updated with Claymore v11.9 (For those are using this miner software)
https://bitcointalksearch.org/topic/claymores-dual-ethereum-amdnvidia-gpu-miner-v150-windowslinux-1433925
EDIT : Those who had update to nvOC 19.2.1 have Claymore v11.9. Sorry for this useless alert if you updated
@parentibule you messed up something, I see you are running commands from an home directory of an user named 'm1_2.1'. Have you intentionally did this or you were just trying to put nvOC into a different folder? If you know how Windows users profile works, you know that there exist a folder for each user in C:\Users\ for example my user folder is C:\Users\LuKe. In Ubuntu that is the same thing but every user has a folder inside the /home directory, so in nvOC images the default user is 'm1', therefore exists a folder /home/m1 which is the place where all user files need to be. If you created a new user named 'm1_2.1' then it is correct that such /home/m1_2.1 folder exists, but in such a case you did a horrible choice in placing nvOC files inside his home folder because Ubuntu uses that folder to store all system files related to that user, that's why the default location for nvoc files in prebuilt images is '/home/m1/NVOC/something', /home/m1 is the home folder for m1 user, NVOC is just a folder like any other. If, instead, you choosed to place nvOC files inside an arbitrary folder name /home/m1_2.1 but you created no user named m1_2.1 then you did a mistake, reinstall nvOC into another folder. Remember that the default m1 user is a NOPASSWD sudoer, he can reboot doing 'sudo reboot' without being asked for credentials. Don't care the nvOC as a service mode, it is an alternative to gnome for who really needs it.
@Ventero I don't understand which kind of "settings" for claymore you are in search of. It is just a miner, the only things you need to set are the pool and the algorithm you intend to mine and it is done automatically by nvOC when you set COIN="ETH" and related ETH_* settings. You don't need nothing else in most cases. Try start mining and see the miner command line built up by nvOC in the miner log window, if you see there are some missing arguments come back here to ask why a certain argument is not set correctly, but I don't tkink this could happen to you with a well supported miner like claymore. Let me know.
The instructions you are referring to explain how to configure and customize the prebuilt image setup. Most people would be fine with defaults. firstboot.json file configures the very first boot of your rig during which nvOC is installed and then it is never ever used again in your rig lifespan. 1bash contains settings for nvOC. During the first boot the 1bash file you palce in the small fat partition is imported to the nvOC installation when it is ready.
The auto_expand option enables the Ubuntu disk partision to be enlarged (during firstboot) up to the entire disk sapce. The prebuilt image you download is small to fit various drive sizes. If you do not a lot of free space available on your rig ubuntu partition leave it to false.
Compiling a software means you take its source code (written in some programming language) and build again from sources the executable binary (think to .exe files in windows). nvOC comes with a set of already compiled miners, some of them are open source, we have the source code, some other are closed source, the source is secret and only the author has it. Therefore you can recompile only open source software or that one you authored. You don't need to recompile open source miners you find in nvOC unless the the compiled version is not compatible with your platform/runtime. Finally, claymore is a close source miner, nobody can recompile it. When someone install nvOC on a lagre number of rigs where he already knows in advance that a recompilation will be needed, he may find usefult to instruct the firstboot setup to do it before starting to try mining otherwise it will fail and he will need to manually recompile the miner on each rig. Compiling a miner require a lot of disk space to store sources and various files generated during the compilation, so it is usually needed to also enable auto_expand in such kinf of scenarios.
Long story short: you just need to write the image to drive, download a 1bash.template from github, customize it with mining-related settings (start by only setting coin and mining pool) and place this shiny 1bash file in the small fat partition. And boot the rig. That is why this thread title includes "easy-to-use"
@Ventero I don't understand which kind of "settings" for claymore you are in search of. It is just a miner, the only things you need to set are the pool and the algorithm you intend to mine and it is done automatically by nvOC when you set COIN="ETH" and related ETH_* settings. You don't need nothing else in most cases. Try start mining and see the miner command line built up by nvOC in the miner log window, if you see there are some missing arguments come back here to ask why a certain argument is not set correctly, but I don't tkink this could happen to you with a well supported miner like claymore. Let me know.
The instructions you are referring to explain how to configure and customize the prebuilt image setup. Most people would be fine with defaults. firstboot.json file configures the very first boot of your rig during which nvOC is installed and then it is never ever used again in your rig lifespan. 1bash contains settings for nvOC. During the first boot the 1bash file you palce in the small fat partition is imported to the nvOC installation when it is ready.
The auto_expand option enables the Ubuntu disk partision to be enlarged (during firstboot) up to the entire disk sapce. The prebuilt image you download is small to fit various drive sizes. If you do not a lot of free space available on your rig ubuntu partition leave it to false.
Compiling a software means you take its source code (written in some programming language) and build again from sources the executable binary (think to .exe files in windows). nvOC comes with a set of already compiled miners, some of them are open source, we have the source code, some other are closed source, the source is secret and only the author has it. Therefore you can recompile only open source software or that one you authored. You don't need to recompile open source miners you find in nvOC unless the the compiled version is not compatible with your platform/runtime. Finally, claymore is a close source miner, nobody can recompile it. When someone install nvOC on a lagre number of rigs where he already knows in advance that a recompilation will be needed, he may find usefult to instruct the firstboot setup to do it before starting to try mining otherwise it will fail and he will need to manually recompile the miner on each rig. Compiling a miner require a lot of disk space to store sources and various files generated during the compilation, so it is usually needed to also enable auto_expand in such kinf of scenarios.
Long story short: you just need to write the image to drive, download a 1bash.template from github, customize it with mining-related settings (start by only setting coin and mining pool) and place this shiny 1bash file in the small fat partition. And boot the rig. That is why this thread title includes "easy-to-use"
@Ventero the coin setup section looks fine, the miner specific options are usually fine with defaults so revert them back to defaults (you can always see defaults in the 1bash.template). Those settings defines how the params you put for eth or other coins are glued together and passed to the miner command line.
thanks for advice. I was trying to find defaults options for claymore but I did not found them in 1bash.template file (I was trying to find them with CTRL-f tool). Are you sure it is there?
I downloaded latest beta version and I don't understand two things in instructions
"Edit firstboot.json to enable/disable auto_expand. ("true" or "false")"
>>> What it does?
"recompile miners on first boot ("false" for no recompile, "A" for all, The letter/number associated to each recompilable miner depends on the latest nvOC_miner_update.sh script you find in the nvOC_miners repository on GitHub)" >>>
>>> I want to compile just claymore. I have to define letter/number asociated with claymore in 1bash file? I did not find it in bash file. I have to setup it "false" and then I will find letter/number associated with claymore after I boot into nvOS?
Thank you!
@parentibule have you intentionally enabled nvOC to run as a system service instead of as gnome profile launch script or you don't know what I'm talking about? In the first case, open an issue for that on github. In the second one, have you ever run the nvOC install-service command? You don't have to if you do not intend to switch to service mode, but if you have ever done this in the past, even accidentally, then check PR note here #149
edit:@parentibule I think there is a bug somewhere, we ill discuss it in github. For anyone else having problems with nvOC as a service the above general guideline is valid.
edit:@parentibule I think there is a bug somewhere, we ill discuss it in github. For anyone else having problems with nvOC as a service the above general guideline is valid.
I try nvOC install-service because I have a lbocking problem with reboot:
Quote
m1@m1-desktop:~$/home/m1_2.1/nvOC reboot
Warning: The host will reboot in 10 seconds, ctrl-c to cancel...
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
And I thought installing (and stopping) nvOC as service could resolve it.Warning: The host will reboot in 10 seconds, ctrl-c to cancel...
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
edit: note that I try all the known ways to (ssh) reboot linux and none works. I didn't even know it was possible!
Sure you can. zpool, nicehash and mph are some kind of special pools that require special configurations so they have their own sections in 1bash. If you are on ethermine (I'm on ethermine too), you just need to setup ETH coin with ethermine pool settings. There is a quite long list of coin settings, scroll down to ETH and set the pool address, your worker name, wallet address and port and you're done. If you see settings for mph in there,, they're just examples of what you should put in these configs for a generic pool.
thanks for reply!
I edited ETH coin like this
# Ethereum (ETH)
ETH_ADDRESS="0xDb4E411F930aC6aD73dF884f06FfA233bA1e830d"
ETH_EXTENSION_ARGUMENTS=""
ETH_POOL="eu1.ethermine.org"
ETH_PORT="4444"
ETH_WORKER="$Ruda_nvOS"
but I thought I still need to define miner somewhere, so I did it here, but I feel like I do something wrong because I specify pool and adress on two different places
ETHASH_MINER="CLAYMORE" # Choose "CLAYMORE" or "ETHMINER", "GENOIL" or "BMINER"
ETHASH_WALLET_FORMAT="-epool eu1.ethermine.org:4444 -ewal 0xDb4E411F930aC6aD73dF884f06FfA233bA1e830d.Ruda_nvOS"
CLAYMORE_VERSION="latest" # Choose: latest or any version you add its folder.
ETHMINER_OPTS="" # Ethminer optional arguments. add "--api-port -3333" if you want web info
CLAYMORE_OPTS="-wd 1 -r 1 -esm 0 -allpools 1 -asm 0 -mport -3333 -mode 1"
Is this correct or am I doing somthing wrong? Thank you, again!
ETHASH_WALLET_FORMAT is "." or "/" or whatever your pool requires, ethpool and ethermine wallet format are "."
from 1bash:
Code:
WALLET_ADDRESS_FORMAT="." # Choose between "." , "/" , "-" or any other separators your pool uses.
# Some pools require dot (address.worker), some require slash (address/worker) format.
# Depending on the pool you use, set this appropriately:
Guys, thank you both for the support, I greatly appreciate it.
There must be something basic I am missing.
When I run the command:
I get a usage list like this:
Any guidance you guys can provide?
Thanks again for all the help!
There must be something basic I am missing.
When I run the command:
Code:
cd ~/NVOC/mining
bash nvOC upgrade
I get a usage list like this:
Any guidance you guys can provide?
Thanks again for all the help!
Try this:
Code:
cd ~/NVOC/mining
wget -N https://raw.githubusercontent.com/papampi/nvOC_by_fullzero_Community_Release/19-2.1/nvOC
bash nvOC upgrade
@uga you have a very old nvOC script version which does not support the upgrade command. Either you do it manually if you are confident in managing git trees or you can simply grab a newer nvOC helper script from github, replace the old one, and there will be the upgrade command also.
@Ventero the coin setup section looks fine, the miner specific options are usually fine with defaults so revert them back to defaults (you can always see defaults in the 1bash.template). Those settings defines how the params you put for eth or other coins are glued together and passed to the miner command line.
@parentibule have you intentionally enabled nvOC to run as a system service instead of as gnome profile launch script or you don't know what I'm talking about? In the first case, open an issue for that on github. In the second one, have you ever run the nvOC install-service command? You don't have to if you do not intend to switch to service mode, but if you have ever done this in the past, even accidentally, then check PR note here #149
edit:@parentibule I think there is a bug somewhere, we ill discuss it in github. For anyone else having problems with nvOC as a service the above general guideline is valid.
@Ventero the coin setup section looks fine, the miner specific options are usually fine with defaults so revert them back to defaults (you can always see defaults in the 1bash.template). Those settings defines how the params you put for eth or other coins are glued together and passed to the miner command line.
@parentibule have you intentionally enabled nvOC to run as a system service instead of as gnome profile launch script or you don't know what I'm talking about? In the first case, open an issue for that on github. In the second one, have you ever run the nvOC install-service command? You don't have to if you do not intend to switch to service mode, but if you have ever done this in the past, even accidentally, then check PR note here #149
edit:@parentibule I think there is a bug somewhere, we ill discuss it in github. For anyone else having problems with nvOC as a service the above general guideline is valid.
Hi,
With git version, on nvOC restart (or nvOC start-service), I have:
With git version, on nvOC restart (or nvOC start-service), I have:
Quote
Jul 22 15:37:30 m1-desktop systemd[1]: Started nvOC Service.
Jul 22 15:37:30 m1-desktop systemd[1]: nvoc.service: Service hold-off time over, scheduling restart.
Jul 22 15:37:30 m1-desktop systemd[1]: Stopped nvOC Service.
Jul 22 15:37:30 m1-desktop systemd[1]: nvoc.service: Start request repeated too quickly.
Jul 22 15:37:30 m1-desktop systemd[1]: Failed to start nvOC Service.
And I don't find any log about this. Jul 22 15:37:30 m1-desktop systemd[1]: nvoc.service: Service hold-off time over, scheduling restart.
Jul 22 15:37:30 m1-desktop systemd[1]: Stopped nvOC Service.
Jul 22 15:37:30 m1-desktop systemd[1]: nvoc.service: Start request repeated too quickly.
Jul 22 15:37:30 m1-desktop systemd[1]: Failed to start nvOC Service.
Sure you can. zpool, nicehash and mph are some kind of special pools that require special configurations so they have their own sections in 1bash. If you are on ethermine (I'm on ethermine too), you just need to setup ETH coin with ethermine pool settings. There is a quite long list of coin settings, scroll down to ETH and set the pool address, your worker name, wallet address and port and you're done. If you see settings for mph in there,, they're just examples of what you should put in these configs for a generic pool.
thanks for reply!
I edited ETH coin like this
# Ethereum (ETH)
ETH_ADDRESS="0xDb4E411F930aC6aD73dF884f06FfA233bA1e830d"
ETH_EXTENSION_ARGUMENTS=""
ETH_POOL="eu1.ethermine.org"
ETH_PORT="4444"
ETH_WORKER="$Ruda_nvOS"
but I thought I still need to define miner somewhere, so I did it here, but I feel like I do something wrong because I specify pool and adress on two different places
ETHASH_MINER="CLAYMORE" # Choose "CLAYMORE" or "ETHMINER", "GENOIL" or "BMINER"
ETHASH_WALLET_FORMAT="-epool eu1.ethermine.org:4444 -ewal 0xDb4E411F930aC6aD73dF884f06FfA233bA1e830d.Ruda_nvOS"
CLAYMORE_VERSION="latest" # Choose: latest or any version you add its folder.
ETHMINER_OPTS="" # Ethminer optional arguments. add "--api-port -3333" if you want web info
CLAYMORE_OPTS="-wd 1 -r 1 -esm 0 -allpools 1 -asm 0 -mport -3333 -mode 1"
Is this correct or am I doing somthing wrong? Thank you, again!
Thank you so much for your help - greatly appreciated!
I have run the script:
Code:
cd ~/NVOC/mining
git pull
And it looks like it has run the update.
I had to rename 1bash, 3main and another file in the www directory for the update to generate the 1bash.template and run smoothly.
However, I am still unable to run the miner, I get the following error message:
Code:
/home/m1/NVOC/mining/2unix: line 48: 3572 Terminated
/home/m1/NVOC/mining/2unix: line 31: /home/m1/NVOC/mining/1bash.template: No such file or directory
I then copied 1bash and renamed it 1bash.template, so that I have both a 1bash and 1bash.template, but I still get the issue:
Code:
/home/m1/NVOC/mining/2unix: line 48: 3572 Terminated
Not sure if it matters, but the number before Terminated (above 3572) changes and goes in an increasing pattern.
It actually seems to be an issue I face with the beta version even before I run the script to upgrade to the latest.
I have tried a couple coins, but it has no impact.
Any insight into how to address this?
I am in way above my head here
Thanks guys!
P.S: Also wondering about something: when I look into the miner folder, for some reason I cannot locate a EWBF folder - Not sure if this is normal? I had a look to see if it was perhaps burried into another subfolded in the miner folder but no luck.
Avoid running 'git pull' manually, always use nvOC upgrade command which automatically handle removing conflicts like those you had in some files.
So you have to do:
Code:
cd ~/NVOC/mining
bash nvOC upgrade
You can do it by running (from the same directory):
Code:
bash nvOC miners-upgrade
This last command will also check again for further miners updates, it may pull additional miners updates released after the nvOC version you updated to with the first 'nvOC upgrade' command, and it will install all of them and eventually ask you if you intend to compile some of them. If you don't do it no miners update will be applied. Maybe in future revisions the nvOC upgrade command will ask you if you also intend to upgrade miners. At the moment you have to to both.
You can always install miners updates only without updating main nvOC files by just doing 'bash nvOC miners-upgrade' from your nvOC installation path.
Guys, thank you both for the support, I greatly appreciate it.
There must be something basic I am missing.
When I run the command:
Code:
cd ~/NVOC/mining
bash nvOC upgrade
I get a usage list like this:
https://image.ibb.co/mTqEzJ/error1.jpg
Any guidance you guys can provide?
Thanks again for all the help!
Thank you so much for your help - greatly appreciated!
I have run the script:
Code:
cd ~/NVOC/mining
git pull
And it looks like it has run the update.
I had to rename 1bash, 3main and another file in the www directory for the update to generate the 1bash.template and run smoothly.
However, I am still unable to run the miner, I get the following error message:
Code:
/home/m1/NVOC/mining/2unix: line 48: 3572 Terminated
/home/m1/NVOC/mining/2unix: line 31: /home/m1/NVOC/mining/1bash.template: No such file or directory
I then copied 1bash and renamed it 1bash.template, so that I have both a 1bash and 1bash.template, but I still get the issue:
Code:
/home/m1/NVOC/mining/2unix: line 48: 3572 Terminated
Not sure if it matters, but the number before Terminated (above 3572) changes and goes in an increasing pattern.
It actually seems to be an issue I face with the beta version even before I run the script to upgrade to the latest.
I have tried a couple coins, but it has no impact.
Any insight into how to address this?
I am in way above my head here
Thanks guys!
P.S: Also wondering about something: when I look into the miner folder, for some reason I cannot locate a EWBF folder - Not sure if this is normal? I had a look to see if it was perhaps burried into another subfolded in the miner folder but no luck.
Avoid running 'git pull' manually, always use nvOC upgrade command which automatically handle removing conflicts like those you had in some files.
So you have to do:
Code:
cd ~/NVOC/mining
bash nvOC upgrade
You can do it by running (from the same directory):
Code:
bash nvOC miners-upgrade
This last command will also check again for further miners updates, it may pull additional miners updates released after the nvOC version you updated to with the first 'nvOC upgrade' command, and it will install all of them and eventually ask you if you intend to compile some of them. If you don't do it no miners update will be applied. Maybe in future revisions the nvOC upgrade command will ask you if you also intend to upgrade miners. At the moment you have to to both.
You can always install miners updates only without updating main nvOC files by just doing 'bash nvOC miners-upgrade' from your nvOC installation path.
Jump to: