[ mining os ] nvoc - page 12. | Bitcointalksearch.org

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: CryptAtomeTrader44 on September 16, 2018, 01:07:22 PM

Note 5: I observed that WTM_Switching no longer sorts the values retrieved from the WTM website in decreasing order. In addition, the displayed values do not indicate profitability but income since the values are positive whereas they should be negative as on the WTM website.

Check your WTM URL
That usually happens when you sort not by current revenue and difficulty

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

fk2

jr. member

Activity: 67

Merit: 2

I'm still having the problem that my first rig with 1060s is rebooting due to lost gpu, even though I can see they are mining properly and are not lost:

Code:

Mon Sep 17 04:42:08 MST 2018 - [CRITICAL] - reboot in 10 seconds
Mon Sep 17 04:59:16 MST 2018 - [CRITICAL] - Lost GPU6 so restarting system. Found GPU's:
Unable to determine the device handle for GPU 0000:08:00.0: GPU is lost. Reboot the system to recover this GPU

Im trired of restarting on my own since even this is failing into a state where I just can remotely power off and on again. Somebody has an idea?

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 : 390.77

nvOC info:
nvOC path : /home/m1/NVOC/testing
nvOC : 0019-2.1
Report : 0012
1bash : 0038
1bash.template:
3main : 0026
5watchdog : 0022
6tempcontrol : 0008
wtm switch : 0023
wtm profit : 0004
pool switch : 0002
minerinfo : 0010

Hardware info:
Motherboard : ASUS PRIME Z270-A Rev 1.xx
BIOS ver. : 1009 07/23/2017
CPU Model : Celeron(R) CPU G3900 @ 2.80GHz
CPU Cores : 2 (Cores + Threads)
Mem Total : 3984604 kB
Mem Free : 2847916 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 74.5G disk 1 0 sata ATA TOSHIBA MK8052GS 0A
├─sda1 9M vfat part 1 0
└─sda2 74.5G ext4 part 1 0 /

VGA info:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)

Local git branch and submodules status:
## 19-2.1...origin/19-2.1 [behind 1065]
M 0miner
D 1bash.template
M telegram
+f7c8bc2e3f604fe15b5dbb5fe75fa566d3ae5587 miners (remotes/origin/19-2.1)
## HEAD (no branch)
cd6fab68823e247bb84dd1fa0448d5f75ec4917d ANXccminer/src (heads/master)
+aafe2d19b6d9eb07d942d70ced3049e9aed1c241 ASccminer/src (1.5.3-tpruvot-81-gaafe2d1)
-24c65cf166bbb3332d60e2baef859ceb604e5d49 ETHMINER/src
c5ab73837c8024f1e6b8fe7ad46e6881fb8366e6 KTccminer/src (1.4.6-tpruvot-1293-gc5ab738)
-bedaf007d4619fc4157aeafb59b44850f08d93f1 KTccminer_cryptonight/src
7d41d49b92db27b9ab80270adaa92f6b06d1ef78 KXccminer/src (0.1)
78dad7dd659eae72a07d2448de62b1946c1f2b41 MSFTccminer/src (2.2.5-rvn)
8affcb9cd09edd917d33c1ed450f23400f571bdb NAccminer/src (v2.2-mod-r2)
9e86bdd24ed7911b698f1d0ef61a4028fcbd13c5 SPccminer/src (1.5.81)
c800f1a803e1b2074ed2a7c15023c096d0772048 SUPRminer/src (1.5)
a81ab0f7a557a12a21d716dd03537bc8633fd176 TPccminer/src (2.2.5-tpruvot)
-48b170a5828256600ca71e66d4c114af4e114236 VERTMINER/src
-c0ab1734332d6472225d8ac7394f6fcba71aabc9 XMR_Stak/src
bfd1c002f98f2d63f2174618838afc28cf4ffffe cpuOPT/src (v3.8.8.1)

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

Watchdog ..................: NO
SYSRQ Reboot ..............: YES
Watchdog Cycle ............: 15
GPU Utilization Threshold .: 50
Alternate Pool ............: NO

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

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

TELEGRAM_MESSAGES .: YES
TELEGRAM_ALERTS ...: NO
TELEGRAM_TYPE .............: fk1
TELEGRAM_TIMEOUT_IN_MINUTES: 360
TELEGRAM_CHATID ...........: CHATID_NOT_SHOWN
TELEGRAM_APIKEY ...........: APIKEY_NOT_SHOWN

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

POWERLIMIT MODE ...........: GLOBAL
Power Limit WATTS .........: 76
OVERCLOCK MODE ............: GLOBAL
Memory Overclock ..........: 1200
Core Overclock ............: 110

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

AUTO_SWITCH ...............: NO
COIN ......................: NICE_ETHASH
ALGO ......................: ETHASH
MINER .....................: ETHMINER
NICE_ETHASH WORKER ................: AnyMine01
NICE_ETHASH ADDRESS ...............: ...
NICE_ETHASH POOL ..................: daggerhashimoto.eu.nicehash.com
NICE_ETHASH PORT ..................: 3353

wi$em@n

newbie

Activity: 46

Merit: 0

Quote from: CryptAtomeTrader44 on September 16, 2018, 01:07:22 PM

Note: I installed RealVNC for a local remote control in place of Teamviwer that I can not use anymore, but I saw by looking in the menus of the new version of ubuntu that other software have been added, notably SSHVNC (i don't know if this software is user friendly).

There is no any "SSHVNC" there, there is Sharing in the settings, which is disabled by default, and I have a big request to devs, guys please can you make it activated, with disabled "require-encryption" and the default password (miner1 for example) in the next image of nvOC? Cause it's not simple to do that on each rig by SSH, if you do not have a possibility to attach a monitor to it.

Brainfruit_Me

newbie

Activity: 23

Merit: 0

I am having a repeating problem, but only with one rig, when ubuntu login screen asks for password after i enter the correct password it goes to a green screen but is totally frozen and will not progress to the desktop. This happens every reboot with only this one rig. Have reflashed the USB multiple times.

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: papampi_2 on September 06, 2018, 12:57:08 AM

nvOC_19-2.1 beta Ubuntu 18.04 Dual-Cuda Nvidia 396 2018-09-07

- Ubuntu 18.04.1 with latest updates and patches
- Dual Cuda support with Cuda 9.2 and 8 pre installed
- Disabled ubuntu splash screen to show kernel message
- All the latest miners
- bminer dual mining support
- CryptoDredge miner
- New Hot temp shutdown
- Fix bugs in WTM Switcher
- New Coins and Algos
- Bug fixes
- So many new additions and improvements.

- With so many changes, its recommended to use new 1bash.
- Recompile miners may have some problems due to changes in ubuntu 18.04.
- Telegram not working due to Ubuntu 18.04 moved to libcurl4, but many miners depend on libcurl3

As always extract the compressed file, flash your SSD/USB with the extracted img file
Open small fat partition and read the README
Download latest 1bash.template
Edit 1bash.template and save it as 1bash

Notice: Do NOT remove 1bash.template from /NVOC/mining, copy and rename new one if needed

Edit firstboot.json to enable/disable auto_expand. ("true" or "false")
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)
Auto recompile may take long time to download and recompile all miners.

On first boot, firstboot gnome-terminal profile will expand partition to full size, after reboot it will add latest nvOC and miners from GitHub repo.
firstboot gnome-terminal will stop and open mining gnome-terminal profile.
May reboot again if xorg.conf needs update.

Mega download link

Gdrive download link

Image size: 12.5 Gb
Zip size: 3.5 Gb
(Due to bigger image size we used 7z with ultra compression to keep download size at 3.5 Gb)

sha256:

Code:

nvOC_19-2.1_U18.04_Dual-Cuda_N396_2018-09-07.img:
27090E4CF4C4928619AFE456995870F9FAC0996F7876B7791898BD18F2B21D00

nvOC_19-2.1_U18.04_Dual-Cuda_N396_2018-09-05.7z
2384B639142123F13D9E8BAE834F248A293F4F7142B05D5CBF55FBE2DBCB6903

This new version (DUAL CUDA) works for me except for MONERO (XMR) with xmr-stak.

I have this error when I want to mine XMR:

Quote

/home/m1/NVOC/mining/0miner: line 159: xmr-stak_VERSION: bad substitution
/home/m1/NVOC/mining/0miner: line 179: xmr-stak_VERSION: bad substitution

Note: I installed RealVNC for a local remote control in place of Teamviwer that I can not use anymore, but I saw by looking in the menus of the new version of ubuntu that other software have been added, notably SSHVNC (i don't know if this software is user friendly).

Note 2: I stopped the miner for about 2 weeks because we are in the negative profitability. By testing this new papampi's version proposed, I just wanted to prepare to restart as soon as the profitability becomes acceptable. If this profitability does not return in the positive, then I will rekindle the miner this winter when it will be cold to heat my apartment to the place of my radiating electric convectors. This will not be long since the night temperatures begin to fall below 10 degrees Celsius for a few days.

Note 3: I had to redo my 1bash file from zero because I tried to use kdiff3 to easily get the values of my old 1bash file and the control of this file by the scripts told me that my 1bash file was wrong .
Have you considered using a PHP or HTML script that would easily generate this 1bash file faster via a web browser?

Note 4: I also reinstated my minerinfo file that I had tinkered in older versions. Everything works well with him.

Note 5: I observed that WTM_Switching no longer sorts the values retrieved from the WTM website in decreasing order. In addition, the displayed values do not indicate profitability but income since the values are positive whereas they should be negative as on the WTM website.

Translated from French with Google translation

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: hallzero on September 14, 2018, 04:51:31 PM

Any ideas?

1) Try restoring your xorg.conf with that one provided for nvOC 2.0.
2) update to nvOC 2.1, the most recent image based on ubuntu 16 is mature enough

Quote from: WaveFront on September 15, 2018, 11:25:30 AM

Hello,
I am considering upgrading from the 19-2.0 to the 19-2.1.
How mature do you think the 19-2.1 is? Is it at an advanced beta stage or is it better to stay on the non beta 19-2.0 release?

2.0 is damn old and difficult to support, 2.1 was waiting for ubuntu 18 but some events occurred in the middle like the btg hard fork, and the release of some new miners based on the newer cuda sdk, so we had to take care of them, otherwise @papampi would likely have managed to finalize the 2.1 dev branch and release it. I would say that, in the unlikely event that you encounter any kind of problems there would probably be on the first run with your settings, in terms of stability it is fine.

WaveFront

member

Activity: 126

Merit: 10

Hello,
I am considering upgrading from the 19-2.0 to the 19-2.1.
How mature do you think the 19-2.1 is? Is it at an advanced beta stage or is it better to stay on the non beta 19-2.0 release?

hallzero

newbie

Activity: 12

Merit: 0

Hi there,

i have a strange problem. Updated a long running nvOC 19 2.0 community release rig consisting of 4 1050ti`s with one more 1050ti so it contains 5 now but it is only showing 4 GPU`s i can´t get nvOC to use the 5th gpu.

In order for you to spare a few hints i did the following.
On the hardware side i checked all risers and cables, also i swapped all cards within the rig, didn´t change anything it continues to mine with only 4 gpu`s. Then i swapped all cards into a different rig to see whether a card was faulty, it was not.

So, as far as hardware goes:
1. All risers and all cables check good
2. All gpu´s work (just not within this nvOC rig)

So i went on with the software side of things:

First i stopped everything with

Code:

./nvOC stop

then i checked the Nvidia X-Server it only shows gpu 0-3 so the 5th is missing

then i updated the nvOC installation with

Code:

sudo -- sh -c 'apt-get update; apt-get upgrade -y; apt-get dist-upgrade -y; apt-get autoremove -y; apt-get autoclean -y'

and rebooted.

No change it works and is mining with 4 gpu´s it does not recognize the 5th and i can´t get it to do so.

Using

Code:

./nvOC gpumap

only finds 4 gpu´s

Any ideas?

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: fk2 on September 13, 2018, 07:23:39 AM

Even though the error was more like "lost" I will try that but what I was concerned about is that I am not able to start the system with bash nvOC start because the mining process won't start. Only when auto start option is active and that doesnt stop watchdog rebooting in fail case even when watchdog disabled.

In other words: a seperate option to start mining process once with script is requested. I can fire the whole command manually by myself but maybe not everyone is able to

If there is a problem with a GPU temp control will do the rebooting too, as it catches the error when trying to get the temp.
So just disabling watchdog will not prevent rig with a faulty GPU from rebooting

fk2

jr. member

Activity: 67

Merit: 2

Even though the error was more like "lost" I will try that but what I was concerned about is that I am not able to start the system with bash nvOC start because the mining process won't start. Only when auto start option is active and that doesnt stop watchdog rebooting in fail case even when watchdog disabled.

In other words: a seperate option to start mining process once with script is requested. I can fire the whole command manually by myself but maybe not everyone is able to

LuKePicci

jr. member

Activity: 128

Merit: 1

Try reducing the utilization threshold, the default one is quite hight for miners like z_ewbf and is likely to get the watchdogs rebooting for no valid reason. I set mine to 55% if I remember correctly to avoid such behavior.

fk2

jr. member

Activity: 67

Merit: 2

my rig no 1 is currently constantly rebooting because watchdog loses gpu0-7 after a couple of minutes even though they are mining fine. I wanted to disable the watchdog/auto reboot but this is the opton "auto start miner = yes" which prevents the mining starting at all if set to no...

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: Brainfruit_Me on September 11, 2018, 12:34:09 PM

It still gets the error but it doesn't stop the miner from starting now, thankfully.

I'm not sure which error are you mentioning but if my guess is correct then you should be safe to ignore it. Just check if hashrates are what you expect.

Brainfruit_Me

newbie

Activity: 23

Merit: 0

Quote from: papampi_2 on September 10, 2018, 01:01:29 PM

Quote from: LuKePicci on September 10, 2018, 09:19:40 AM

Quote from: Brainfruit_Me on September 09, 2018, 03:25:37 PM

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

Post some logs of the error and a full report, just in case.

I noticed it on some of my rigs too, no idea why
And the error changes from GPU to GPU after each reboot
Same SSD works with no problems on a rig and shows that error on another almost identical rig.

I finally just had to reflash the USB until it took. It still gets the error but it doesn't stop the miner from starting now, thankfully. Overall it was a bigger pain to initial boot compared to 19 - 2.0 but with the new cuda enhancements I can run a much more efficient miner. ~50% more hash rate and efficiency per watt!
Thanks for your continued work and support for nvoc!

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: LuKePicci on September 10, 2018, 09:19:40 AM

Quote from: Brainfruit_Me on September 09, 2018, 03:25:37 PM

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

Post some logs of the error and a full report, just in case.

I noticed it on some of my rigs too, no idea why
And the error changes from GPU to GPU after each reboot
Same SSD works with no problems on a rig and shows that error on another almost identical rig.

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: LuKePicci on September 09, 2018, 08:55:02 AM

Quote from: fk2 on September 07, 2018, 03:02:01 PM

any chance for current 2.1 beta rigs to update to the latest 18.04 release with dual cuda support by remote/without imaging?

Nope, if you really need dual_cuda support and you can't reimage right now, you could try installing the other cuda-9-2 runtime manually (use cuda distribution specific packages, never cuda runfiles), but you have to be very careful because it could mess with nvidia drivers and get you unable to boot or recover remotely.

Due to Ubuntu 18.04 libcurl3/4 limitations I will make a dual cuda 16.04 image when I find some free time

papampi_2

jr. member

Activity: 112

Merit: 3

Linux Forever... Resistance is futile!!!

Quote from: Hardforkman on September 10, 2018, 07:21:55 AM

Hi! Any one can help me with login, user m1 pass miner1 not working, going to the same login windows

That could be xorg problem, try to ssh and restore xorg with

Code:

bash ~/NVOC/mining/nvOC restore-xorg

Is the onboard GPU disabled in bios?

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: Hardforkman on September 10, 2018, 07:21:55 AM

Hi! Any one can help me with login, user m1 pass miner1 not working, going to the same login windows

May not be a wrong password problem.

LuKePicci

jr. member

Activity: 128

Merit: 1

Quote from: Brainfruit_Me on September 09, 2018, 03:25:37 PM

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

Post some logs of the error and a full report, just in case.

Topic: [ mining os ] nvoc - page 12. (Read 418523 times)