Topic: [ mining os ] nvoc - page 70. (Read 418557 times)

But I'm willing to work with everyone interested in creating a full headless image.

So many users use desktop also use teamviewer, cant do that without making so many angry users

I think the only thing left to reduce size and improve stability (maybe?) is abandon Desktop

bbswitch: No suitable _DSM call found.

anyone know why I would be getting this error message on repeat after boot?

root partition wont allow to go lower, So I think its the smallest we can get.
But will try to cleanup the OS again, see if I can reduse more.

So, i see you reduce the image weight by 2 GB ! It's a very good news !
Is it possible to reduce weight again ?

it's a big step for nvOC, and a big step for profit switching :-)

https://github.com/papampi

I use MiningRigRentals as a free hosted proxy server.

What kind of issues was the 1bash copy having before this fix was applied?

Thanks again for all the great work.  

If I have already run the update script before today to get to v0019-2.0 and want to run it again to get the latest updates,
will that overwrite all my 1bash settings again?

WARNING: Sat Jan 20 22:05:46 MST 2018 - Problem found: See diagnostics below:
Percent of GPUs bellow threshold: 100 %
name, pstate, temperature.gpu, fan.speed [%], utilization.gpu [%], power.draw [W], power.limit [W]
GeForce GTX 1080 Ti, P8, 48, 65 %, 0 %, 21.60 W, 280.00 W
GeForce GTX 1070, P5, 52, 65 %, 0 %, 12.28 W, 180.00 W
GeForce GTX 1070, P5, 56, 65 %, 0 %, 8.67 W, 160.00 W
GeForce GTX 1070, P5, 44, 65 %, 0 %, 10.36 W, 180.00 W
GeForce GTX 1070, P5, 41, 65 %, 0 %, 12.45 W, 180.00 W
GeForce GTX 1070, P5, 52, 65 %, 0 %, 13.91 W, 180.00 W
[2018-01-20 22:05:30] GPU #4: waiting for data
[2018-01-20 22:05:30] GPU #3: waiting for data
[2018-01-20 22:05:30] GPU #1: waiting for data
[2018-01-20 22:05:33] GPU #5: waiting for data
[2018-01-20 22:05:33] GPU #0: waiting for data
[2018-01-20 22:05:33] GPU #2: waiting for data
[2018-01-20 22:05:33] GPU #4: waiting for data
[2018-01-20 22:05:33] GPU #3: waiting for data
[2018-01-20 22:05:33] GPU #1: waiting for data
[2018-01-20 22:05:36] GPU #5: waiting for data
[2018-01-20 22:05:36] GPU #0: waiting for data
[2018-01-20 22:05:36] GPU #2: waiting for data
[2018-01-20 22:05:36] GPU #4: waiting for data
[2018-01-20 22:05:36] GPU #3: waiting for data
[2018-01-20 22:05:36] GPU #1: waiting for data
CRITICAL: Sat Jan 20 22:05:46 MST 2018 - GPU Utilization is too low: restarting 3main...

   All I got from Mega.NZ was that I have to install some piece of S/W before I can d/l it.
Just what I need is more unknown stuff running.

Will wait for the  FR site and try it.

My drive is almost full, Sorry.
Problem with Mega was when size is over 5 GB and it triggers the wait, bellow 5 GB should be no problem.

nvOC v0019-2.0 Community Release new shrinked image Mega.nz
Download Link

Beta testing...
Please test and let me know.

Change Log:

Download and replace for nvOC v0019-2.0:


Or run the update script to get all latest miners and changes:


Change Log:

Where all the development is going for nvOC ? Is there a github page ?

Also I want to know is there support for Claymore's miner failover implementation in nvOC ?

Forgive me if this was mentioned in the thread already (I couldn't find it) - but I put together a quick checklist for upgrading Claymore revisions for the latest nvOC_19:

Claymore Updates:
[ ]Download linux version of claymore update and unzip tar
[ ]Rename claymore folder to just version number as follows: 10.5 is 10_5
[ ]Upload to appropriate path using sftp client like filezilla (for nvOC_19 it's ~\eth\10_5)
[ ]Copy epools.txt and dpools.txt from pre-existing claymore folder into new path
[ ]Edit 1bash by replacing old version number with new (10_0 to 10_5): sudo nano ~/1bash
[ ]Grant permissions to new claymore dir: chmod -R 777 ~/eth/10_5
[ ]Restart OS: sudo shutdown -r now
[ ]Grep for new total speed - curl http://0.0.0.0:3333 | grep "ETH - Total Speed:"


And a script that I partially stole and modified for tweaking GPU on the fly:

export DISPLAY=:0
for i in {0..5} # Replace range with number of cards you have
do
for x in {3..3}
    do
    nvidia-settings  -a [gpu:${i}]/GPUGraphicsClockOffset[${x}]=10 # CORE_OVERCLOCK (MAXIMUM tested 175 with 1070)
    nvidia-settings  -a [gpu:${i}]/GPUMemoryTransferRateOffset[${x}]=1200 # MEMORY_OVERCLOCK(MAXIMUM tested 1500 with 1070)
done
done
sudo nvidia-smi -pl 100 #POWERLIMIT