[OS] nvOC easy-to-use Linux Nvidia Mining

[fullzero]

So I make some changes for a new telegram alert system
The 30 min telegram notification is good but it gets annoying over time and I had to mute it.
I created a new telegram-alert to pass me alerts from IAmNotAJeep_and_Maxximus007_WATCHDOG
First create a new bot as explained on OP call it Mining Alerts (or whatever you like)
Make new telegram-alert file in m1 home and put these inside :

telegram-alert:

Code:

#!/bin/bash
# Telegram Info Script
# By BaliMiner et al...
# for nvOC by fullzero
# ref: http://bernaerts.dyndns.org/linux/75-debian/351-debian-send-telegram-notification
#

source ~/1bash

CHATID=$TELEGRAM_CHATID
APIKEY=$TELEGRAM_ALERT_APIKEY

SYSTEM_BOOT_TIME=$(uptime -s)
GPU_COUNT=$(nvidia-smi -L | tail -n 1| cut -c 5 |awk '{ SUM += $1+1}  ; { print SUM }')
STARTING_MINER=$(tail -n50 /home/m1/5_restartlog | grep Starting | tail -n 1)
LOST_GPU=$(tail -n50 /home/m1/5_restartlog | grep Lost| tail -n 1)
REBOOT_ALERT=$(tail -n50 /home/m1/5_restartlog | grep 'reboot in' |tail -n 1)
UTILIZATION_LOW_REBOOTING=$(tail -n50 /home/m1/5_restartlog | grep 'low: reviving' |tail -n 1)
UTILIZATION_LOW_RESTART_3MAIN=$(tail -n50 /home/m1/5_restartlog | grep 'low: restart' |tail -n 1)
LOW_UTILIZATION=$(tail -n50 /home/m1/5_restartlog | grep 'Low Utilization' |tail -n 1)
FAILURES_REINIT=$(tail -n50 /home/m1/5_restartlog | grep 'Before reinit')



SYSTEM_UP_TIME=$(uptime -p)
REBOOT_REQUIRED=$(/home/m1/reboot-required)
GPU_UTILIZATIONS=$(tail -n 30 5_restartlog | grep 'GPU UTILIZATION' | awk '{gsub(/GPU UTILIZATION:  /,"")}1' | tail -n 1)


TEMP=$(/usr/bin/nvidia-smi --query-gpu=temperature.gpu --format=csv,noheader)
PD=$(/usr/bin/nvidia-smi --query-gpu=power.draw --format=csv,noheader)
FAN=$(/usr/bin/nvidia-smi --query-gpu=fan.speed --format=csv,noheader)
TEMP_FAN_POWER=$(tail  -n 30 6_autotemplog  | grep GPU | awk '{gsub(/:/,": ")}1' |tail -n $GPU_COUNT)


LF=$'\n'


MSG=" Worker: $WORKERNAME
Boot Time: $SYSTEM_BOOT_TIME
GPU Count: $GPU_COUNT
GPU Utilization: 
$GPU_UTILIZATIONS
$STARTING_MINER
$LOW_UTILIZATION
$FAILURES_REINIT
$UTILIZATION_LOW_RESTART_3MAIN
$LOST_GPU
$REBOOT_ALERT
$UTILIZATION_LOW_REBOOTING
"

/usr/bin/curl -m 5 -s -X POST --output /dev/null https://api.telegram.org/bot${APIKEY}/sendMessage -d "text=${MSG}" -d chat_id=${CHATID}

In your 1bash add a line bellow APIKEY=$TELEGRAM_APIKEY and add your new alert api key

Code:

    TELEGRAM_ALERT_APIKEY="aaaaaaaaaaaaaaaaaaa:bbbbbbbbbbbb-cccccccccccccccccccccccc"

And here is my modified  IAmNotAJeep_and_Maxximus007_WATCHDOG for telegram alerts:

Code:

#!/bin/bash

# Miner restart script V002
# By Maxximus007 && IAmNotAJeep
# for nvOC by fullzero
# Modified by papampi for telegram-alerts

export DISPLAY=:0

# Creating a log file to record restarts
LOG_FILE="/home/m1/5_restartlog"
if [ -e "$LOG_FILE" ] ; then
  #Limit the logfile, just keep the last 2K
  LASTLOG=$(tail -n 2K $LOG_FILE)
  echo $LASTLOG
  echo ""
fi

echo "$(date) - Starting miner restart script." | tee -a ${LOG_FILE}
echo "" | tee -a ${LOG_FILE}
bash '/home/m1/telegram-alert'
# Give oneBash time to start to prevent reboot
echo "$(date) - waiting 70 seconds before going 'on watch'" | tee -a ${LOG_FILE}
sleep 60

THRESHOLD=90
RESTART=0
GPU_COUNT=$(nvidia-smi --query-gpu=count --format=csv,noheader,nounits | tail -1)
COUNT=$((6 * $GPU_COUNT))

while true
do
sleep 10  # sleep 60
#IAmNotAJeep MOD from V002
  JEEP=0
#IAmNotAJeep MOD from V002
  GPU=0
  REBOOTRESET=$(($REBOOTRESET + 1))

#IAmNotAJeep MOD from V002
  echo ""
  echo "      GPU_COUNT: " $GPU_COUNT | tee -a ${LOG_FILE}

#IAmNotAJeep MOD from V002

  UTILIZATIONS=$(nvidia-smi --query-gpu=utilization.gpu --format=csv,noheader,nounits)
  echo ""
  echo "GPU UTILIZATION: " $UTILIZATIONS | tee -a ${LOG_FILE}
  echo "" | tee -a ${LOG_FILE}




numtest='^[0-9]+$'
  
  for UTIL in $UTILIZATIONS
  do
    if ! [[ $UTIL =~ $numtest ]]
    then
        # Not numeric so: Help we've lost a GPU, so reboot
        echo "$(date) - Lost GPU so restarting system. Found GPU's:" | tee -a ${LOG_FILE}
        echo "" | tee -a ${LOG_FILE}
bash '/home/m1/telegram-alert'
        #Hope PCI BUS info will help find the faulty GPU
        nvidia-smi --query-gpu=gpu_bus_id --format=csv | tee -a ${LOG_FILE}
        echo "reboot in 10 seconds" | tee -a ${LOG_FILE}
        echo ""| tee -a ${LOG_FILE}
	bash '/home/m1/telegram-alert'
        sleep 10
        sudo reboot
    fi

    # If utilization is lower than threshold count them:
    if [ $UTIL -lt $THRESHOLD ]
    then
      echo "$(date) - GPU under threshold found" | tee -a ${LOG_FILE}
      echo "" | tee -a ${LOG_FILE}
bash '/home/m1/telegram-alert'
      COUNT=$(($COUNT - 1))
      #IAmNotAJeep MOD from V002
      JEEP=$(($JEEP + 1))
      #IAmNotAJeep MOD from V002
    fi
    GPU=$(($GPU + 1))
  done

#IAmNotAJeep MOD from V002
if [ $JEEP -gt 0 ]
 then

  if [ $COUNT -le 0 ]
  then
    INTERNET_IS_GO=0
    if nc -vzw1 google.com 443;
    #if nc -vzw1 $POOL 80;
    then
    INTERNET_IS_GO=1
    fi
    echo ""
    if [[ $RESTART -gt 4 && $INTERNET_IS_GO == 1 ]]
    then
      echo "$(date) - Utilization is too low: reviving did not work so restarting system in 10 seconds" | tee -a ${LOG_FILE}
      echo "" | tee -a ${LOG_FILE}
 bash '/home/m1/telegram-alert'
      sleep 10
      sudo reboot
    fi
    echo "$(date) - Utilization is too low: restart 3main" | tee -a ${LOG_FILE}
    # If miner runs in screen 'miner' kill the screen to be sure it's gone
    pkill -e miner
bash '/home/m1/telegram-alert'
    # Best to restart oneBash - settings might be adjusted already
    target=$(ps -ef | awk '$NF~"3main" {print $2}')
    kill $target | tee -a ${LOG_FILE}
    echo "" | tee -a ${LOG_FILE}
    RESTART=$(($RESTART + 1))
    REBOOTRESET=0
    COUNT=$GPU_COUNT
    # Give oneBash time to restart to prevent reboot
    sleep 60
  #fi
  else
  echo "$(date) - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures" | tee -a ${LOG_FILE}
  echo ""
  echo "                  "$COUNT "Failures Before reinit"  | tee -a ${LOG_FILE}
bash '/home/m1/telegram-alert'
#IAmNotAJeep MOD from V002
  fi

else
#IAmNotAJeep MOD from V002
  COUNT=$((6 * $GPU_COUNT))
  echo "$(date) - 5 by 5: REMEMBER TO THANK IAmNotAJeep and Maxximus007"
#IAmNotAJeep MOD from V002
fi

  # No need for a reboot after a while
  if [ $REBOOTRESET -gt 5 ]
  then
    RESTART=0
    REBOOTRESET=0
  fi
done

This is how it looks like when there is a gpu under threshold :

Worker: nv102
Boot Time: 2017-09-04 12:17:17
Miner Uptime:    02:45:07
GPU Count: 7
GPU Utilization:
99 83 99 99 98 99 99



Mon Sep  4 15:03:53 IRDT 2017 - GPU under threshold found


Mon Sep  4 15:03:56 IRDT 2017 - Low Utilization Detected: 3main will reinit if there are 6 consecutive failures
                  41 Failures Before reinit

Hopefull we get more/better integration for alerts from fullzero, Maxximus and IAmNotAJeep.
Thanks all.

I also only care to have alerts when there is a problem.  With the default v0019 if you set:

Code:

BaliMiner_TELEGRAM_ALERTS="NO" 

but still add your:

Code:

	TELEGRAM_CHATID="replace_here"

	TELEGRAM_APIKEY="replace_here"

You will only get telegrams when watchdog reboots.

Excessive logging greatly reduces stability (when using a USB key, it is usually ok with SSDs) this is why I want users to be able to choose how much logging they want / disable or not have it at all if desired.

I do like your telegram format and will had your versions.

Please provide me with your BTC address.  I am going to add you and damNmad as contributors.

[1713850235]

1713850235

[salfter]

how do you scroll up in the guake terminal?

Assuming that you're viewing a screen session in that window, Ctrl-A [ lets you begin scrolling back with the arrow keys.  Pressing Enter a couple of times will drop out of scrollback.

If you're not using screen, I don't know...is there a scrollbar?  I've always run my rigs headless over ssh and I don't use Ubuntu elsewhere, so I'm not too familiar with its desktop.

[woodl1]

Anone managed to start NVOC version 19 with built-in  VGA? I heared this version finally have a fix, for using on rigs built on GP106-100 GPUs

As I can see on the first page, it is still advised to start without monitor attached if you have only p106 in your rig.

I have tried to start full headless, with pure p106 mode enabled, but all I get are errors in logs, mining process doesn't start. Does anyone know why this could happen?

(I have asus z270-p with 8 p106-100, screen was attached only to modify bios settings as described for z270-a, usb stick was never attached with monitor at the same time)

Code:

Sep  5 15:13:51 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:51 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:51 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:51 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:51 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:51 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:52 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:52 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:52 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:52 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:54 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:54 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:55 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:55 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:55 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: /etc/modprobe.d is not a file
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:56 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:56 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:57 m1-desktop systemd[1]: Started Light Display Manager.

[elsystem]

genoil does not report current hashrate to pool. i'm mining etc on nanopool.

is there a way to make it report the hashrate as it would make checking on the rig much easier. with varying hashrates it's difficult to tell whether all gpus are running.

[jyakulis]

A Sempron might have difficulty with additional GPUs and some ALGOs; I previously used all Sempron's with BTC / LTC gpu rigs:  they were solid for BTC, but had some issues with LTC with more than 4x GPUs.  I haven't used one in a long time, so I have no idea how they fair with current algos.

Hmm interesting you brought that up. I use the same board on my personal computer. But I upgraded it for gaming to a 6 core processor and doubled my ram. Anyway, I run 3 gpu no problems on Windows 10. But with the board with the Sempron I could never get it to install past 3 gpu on Windows. And I am also having some freezing problems in Ubuntu during mining. Thinking maybe I should upgrade...

[dstm]

A Sempron might have difficulty with additional GPUs and some ALGOs; I previously used all Sempron's with BTC / LTC gpu rigs:  they were solid for BTC, but had some issues with LTC with more than 4x GPUs.  I haven't used one in a long time, so I have no idea how they fair with current algos.

Hmm interesting you brought that up. I use the same board on my personal computer. But I upgraded it for gaming to a 6 core processor and doubled my ram. Anyway, I run 3 gpu no problems on Windows 10. But with the board with the Sempron I could never get it to install past 3 gpu on Windows. And I am also having some freezing problems in Ubuntu during mining. Thinking maybe I should upgrade...

As far as I know K10 Amds use AGP-Gart for their IOMMU. You might get problems on these system because you're running out of DMA-Space, try using 'iommu=memapper=4' (maybe 5) as your boot-parameter, you can look up more details in the kernel documentation.

[bdog1234]

I am mining ZEC on Nanopool. I would like to add my email address as they outline here so that I can increase my minimum payout limit so as to not get so many small transactions.

Code:

 Make sure config.txt file looks like this(replace eu1 with nearest server):

-zpool ssl://zec-eu1.nanopool.org:6633
-zwal YOUR_WALLET.YOUR_WORKER_NAME/EMAIL
-zpsw z
-ftime 1
Where:

YOUR_ETH/ETC_ADDRESS - your valid ZCash address
YOUR_WORKER - simple short worker name (like worker01). Optional.
YOUR_EMAIL - your email address for notifications. Optional.
Don`t forget to set wallet, worker and email address to correct values.

In 1bash I see this:

Code:

ZEC_WORKER="$WORKERNAME"
ZEC_ADDRESS="t1JzsnP1qRWqt1Tpiai7uZQ1r461yRreNdy"
ZEC_POOL="zec-us-east1.nanopool.org"
ZEC_PORT="6666"
EWBF_VERSION="3_4"  # choose 3_3  or  3_4

Should I just change the ZEC_WORKER to?

Code:

ZEC_WORKER="machine1/bdog1234@blahblah.com"

[kk003]

Is there any OC list for 1060 and 1070 gpus? Seems to me that the recommendations are deleted  

My 13 1060 gpu rig has:
10 gpus mc=1700, cc=-100
 3 gpus mc=1500, cc=-100

hashrate around 315Mh/s (23-24Mhs/gpu)
mining etc
hope is helpfull

[octomob]

Please, explain me what does

P106_100_FULL_HEADLESS_MODE="YES/NO"

mean?

explain please also when should I use YES and when NO

Thank you in advance,
respectfully,
Sergey

Headless means no desktop

You only need to worry about that option if you are using P106-100 GPU's

If you are not using them then set it to 'NO'

Thank you, got that

And i use P106-100 on my rigs 
What does this option stands for?

[bdog1234]

Is there any OC list for 1060 and 1070 gpus? Seems to me that the recommendations are deleted 

I have 12 1070's running stable for four days now using
100 core
1000 memory
100 power limit
60 fan

Getting 30-31 MH/sec ETH & 400-410 Sol/sec ZEC

Temps running 50-60 deg

[EvgeniX]

SALFTER_NICEHASH_PROFIT_SWITCHING vs SALFTER_MPH_PROFIT_SWITCHING

what the difference?

[FailSaf3]

I actually signed up on this forum just to say thank you for your hard work,  this OS works amazing!

Can we get Claymore's dual miner v10 added in the next release.  The nvidia sorting method update would be very nice while setting up different GPUs.

[woodl1]

Anone managed to start NVOC version 19 with built-in  VGA? I heared this version finally have a fix, for using on rigs built on GP106-100 GPUs

As I can see on the first page, it is still advised to start without monitor attached if you have only p106 in your rig.

I have tried to start full headless, with pure p106 mode enabled, but all I get are errors in logs, mining process doesn't start. Does anyone know why this could happen?

(I have asus z270-p with 8 p106-100, screen was attached only to modify bios settings as described for z270-a, usb stick was never attached with monitor at the same time)

Code:

Sep  5 15:13:51 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:51 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:51 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:51 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:51 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:51 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:52 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:52 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:52 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:52 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:54 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:54 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:55 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:55 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:55 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: /etc/modprobe.d is not a file
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:56 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:56 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:57 m1-desktop systemd[1]: Started Light Display Manager.

i also have following errors in syslog, in clean nvos019 install. I suppose it's kinda tails from previous usage of "SanDisk_Cruzer_Blade", because I've never used such device.

Code:

Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Sep  6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Sep  6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Sep  6 02:13:06 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Sep  6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Sep  6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Sep  6 02:13:06 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Sep  6 02:13:06 m1-desktop systemd[1]: Startup finished in 7.010s (kernel) + 1min 30.221s (userspace) = 1min 37.231s.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.

Can anybody guess what to do to make this thing work? thanks in advance!

[xxcsu]

can not get this to work on one of my rig... in not a linux guru 

[jotun]

can not get this to work on one of my rig... in not a linux guru 

you don't need to be a linux guru to make nvOC work, you need to be a usb stick plug in and switch the power on guru though

also, we need more details in order to help...

[papampi]

I am mining ZEC on Nanopool. I would like to add my email address as they outline here so that I can increase my minimum payout limit so as to not get so many small transactions.

Code:

 Make sure config.txt file looks like this(replace eu1 with nearest server):

-zpool ssl://zec-eu1.nanopool.org:6633
-zwal YOUR_WALLET.YOUR_WORKER_NAME/EMAIL
-zpsw z
-ftime 1
Where:

YOUR_ETH/ETC_ADDRESS - your valid ZCash address
YOUR_WORKER - simple short worker name (like worker01). Optional.
YOUR_EMAIL - your email address for notifications. Optional.
Don`t forget to set wallet, worker and email address to correct values.

In 1bash I see this:

Code:

ZEC_WORKER="$WORKERNAME"
ZEC_ADDRESS="t1JzsnP1qRWqt1Tpiai7uZQ1r461yRreNdy"
ZEC_POOL="zec-us-east1.nanopool.org"
ZEC_PORT="6666"
EWBF_VERSION="3_4"  # choose 3_3  or  3_4

Should I just change the ZEC_WORKER to?

Code:

ZEC_WORKER="machine1/bdog1234@blahblah.com"

I add email to worker like this and works ok.

Code:

ZEC_WORKER="$WORKERNAME/email@gmail.com"
ZEC_ADDRESS="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

[damNmad]

SALFTER_NICEHASH_PROFIT_SWITCHING vs SALFTER_MPH_PROFIT_SWITCHING

what the difference?

SALFTER_NICEHASH_PROFIT_SWITCHING - This one mines the profitable algorithm according to nicehash stats and converts straight into BTC. You must have an account with nicehash and copy that address over to 1bash.

SALFTER_MPH_PROFIT_SWITCHING - This one mines the profitable coin according to miningpoolhub stats and keeps the coins under you account. You must have an account with miningpoolhub and add that to MPH_USER.

[bdog1234]

That worked. Thanks.

[papampi]

ZPOOL_NEOSCRYPT Algo mining :


coin:

Code:

COIN="ZPOOL_NEOSCRYPT"

1bash

Code:

# ZPOOL uses your BTC_ADDRESS
ZPOOL_NEOSCRYPT_POOL="stratum+tcp://neoscrypt.mine.zpool.ca:4233"

3main:

Code:

if [ $COIN == "ZPOOL_NEOSCRYPT" ]
then
HCD='/home/m1/SPccminer/ccminer'

ZPOOLPASS="$WORKERNAME,c=btc"

screen -dmS miner $HCD -a neoscrypt -o $ZPOOL_NEOSCRYPT_POOL -u $BTC_ADDRESS -p $ZPOOLPASS

if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi

BITCOIN="theGROUND"

while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi

[damNmad]

I actually signed up on this forum just to say thank you for your hard work,  this OS works amazing!

Can we get Claymore's dual miner v10 added in the next release.  The nvidia sorting method update would be very nice while setting up different GPUs.

Mate, that is a very simple DIY stuff, for which you don't need to wait until next release.

Just follow this guide and try v10, you can simply switch back by renaming folder names.

Download the Linux version on rig from this link :

https://drive.google.com/drive/folders/0B69wv2iqszefdFZUV2toUG5HdlU

extract it (right click extract here)

Go to /home/m1/eth (can do it using GUI)

rename the 9_8 to 9_8_xx

copy the latest claymore folder from downloads and paste it in the above eth folder and rename it to 9_8.

It should work normally (this is the easiest work around, you don't need to edit any 1bash or 3main).

I've seen a little increase in dual mining lbc hashrates.

Hope it helps