Bitcoin Forum
August 03, 2020, 09:16:07 PM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 [166] 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 ... 419 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining  (Read 416858 times)
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
September 05, 2017, 05:56:08 PM
 #3301


I just placed an order for some g4600's. I will see how that works - the rig that had been crashing every couple hours crashed after 24 hours after I turned off teamviewer - hopefully this puts me over the top.

As for power, both are built the same way. Each is running on 2 750w EVGA G3 power supplies. Each SATA/molex power connector is running no more than 2 GPU risers. The molex connectors (and single SATA) hooked to the board each share with the riser for a single GPU (this means 13 GPU's, 2 motherboard molex, and 1 motherboard SATA to connect. The PSU's each have 3 SATA and 1 Perif (molex) connector, hence my using two connections per cable). I did have a 550w PSU in the mix (as a third) to see if that would change things, but it did not.

The only other discernable different is that not all GPU's are the same brand/make (but all are 1060 6GB), and the risers are not all identical (though I have switched them out in troubleshooting).

Good, G4600 is 2 core, 4 threads CPU. That will definetely help, much better than Celerons you have.

As for the mixed GPU's, try to put as many of the same brand/model in the same rig. Then you will have to manualy set overclocking for each GPU. Don't use the global OC for all. Try with the lowest stable value for all (I believe it was about 600 memory for you), then increase +50 memory on one brand/model and see if it's stable, then try +50 on different model and see if it's stable, then repeat until you get max for all models. It will take a while to fine tune it, that's the downside of mixed cards. Good luck and keep us posted.

Yesterday I swapped both Celeron G3930's for G4600's.

Overnight, the stable rig remained stable, the unstable rig crashed again.

Short of replacing all my risers again (and I am still open to specifics on what version to get) or RMA'ing the motherboard, is there anything else I might be missing?

JudoFlash, have you tried my previous suggestion of manualy overclocking each card, not using the global settings since you have a mix of different cards?

If that doesn't work, disconnect one card completely, then run the rig, see if it's stable. If it still crashes, connect the disconnected card back and disconnect another card completely... repeat until you pinpoint the card that misbehave. Once you pinpointed the troublemaker, troubleshoot further: replace the riser, replace the adapter cable to the riser (depends on your risers, PCIe to SATA or Molex to SATA cable), plug the riser power to another connector of the SATA cable coming from the power supply, lastly, significantly lower the overclock values for that card. If previous steps didn't help, you have a bad GPU, replace it.

I've had problems with, bad riser, bad power adapter cable, bad SATA connector and bad GPU before. It's not easy to troubleshoot when the problem is intermittent but atleast with the above suggestion (disconnecting one card at a time completely) you can narrow the problematic section then troubleshoot further.

BTW, I am using version 006-c risers with PCIe to SATA power adapter cables.

Thank you. Yes I have tried the manual tuning. Right now I have everything running at stock as sort of a "last ditch" effort on making this configuration work (or at least narrowing it down). As you said, the challenge is that it does not crash right away (sometimes it takes 24 hours or so), so with so many variables, it takes a long time to pinpoint. I ordered some new risers (I would need them anyway as I plan to set up another rig or two), so I will do some further testing with those once I have them.

I appreciate everyone's input. Yes, I know I could just stand up another board and not have so much riding on this one, but I feel longer term, finding the issue will help my overall success. Plus, folks on this forum seem to be making things work with this board and similar setups.

Also, I'm stubborn.

I have been making / transitioning a lot of rigs lately.  On some of them I used risers a friend had bought from a seller on amazon; out of 39 risers 4 were bad.  This is a higher failure rate than I am used to with the v006+ 6pin power risers. 

Near the white latch lock on the back of the riser there is usually a word; which I believe denotes the factory where the riser was made.  Some of these are better than others, some risers also have no word at all.  It would be helpful if resellers provided this information when making listings / selling risers.

1596489367
Hero Member
*
Offline Offline

Posts: 1596489367

View Profile Personal Message (Offline)

Ignore
1596489367
Reply with quote  #2

1596489367
Report to moderator
1596489367
Hero Member
*
Offline Offline

Posts: 1596489367

View Profile Personal Message (Offline)

Ignore
1596489367
Reply with quote  #2

1596489367
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1596489367
Hero Member
*
Offline Offline

Posts: 1596489367

View Profile Personal Message (Offline)

Ignore
1596489367
Reply with quote  #2

1596489367
Report to moderator
1596489367
Hero Member
*
Offline Offline

Posts: 1596489367

View Profile Personal Message (Offline)

Ignore
1596489367
Reply with quote  #2

1596489367
Report to moderator
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
September 05, 2017, 05:57:54 PM
 #3302

Setting target temp does not affect Maxximus

6_autotemplog :
Code:
GPU 0, Target temp: 70, Current: 69, Diff: 1, Fan: 100, Power: 131.56
GPU 1, Target temp: 70, Current: 69, Diff: 1, Fan: 75, Power: 128.21
GPU 2, Target temp: 70, Current: 67, Diff: 3, Fan: 65, Power: 128.31
GPU 3, Target temp: 70, Current: 70, Diff: 0, Fan: 75, Power: 129.51
GPU 4, Target temp: 70, Current: 69, Diff: 1, Fan: 85, Power: 130.39
GPU 5, Target temp: 70, Current: 70, Diff: 0, Fan: 65, Power: 130.88

1bash :
Code:
TARGET_TEMP=75
 
__FAN_ADJUST=5      # Adjustment size in percent
 
POWER_ADJUST=5      # Adjustment size in watts
 
# Difference in actual temperature allowed before action:  Works only if current is BELOW target temp
 
ALLOWED_TEMP_DIFF=3
 
# Restore original power limit if fan speed is lower than this percentage
 
RESTORE_POWER_LIMIT=90
 
# lowest fan speed that will be used
 
MINIMAL_FAN_SPEED=65

Edit 1 :
Only read from individual target temps even if it set to NO

Changing individual changes it :
Code:
GPU 0, Target temp: 75, Current: 74, Diff: 1, Fan: 80, Power: 133.05
GPU 1, Target temp: 75, Current: 73, Diff: 2, Fan: 65, Power: 129.05
GPU 2, Target temp: 75, Current: 68, Diff: 7, Fan: 65, Power: 129.48
GPU 3, Target temp: 75, Current: 73, Diff: 2, Fan: 65, Power: 131.14
GPU 4, Target temp: 75, Current: 75, Diff: 0, Fan: 70, Power: 132.09
GPU 5, Target temp: 75, Current: 71, Diff: 4, Fan: 65, Power: 130.52

1bash :
Code:
INDIVIDUAL_TARGET_TEMPS="NO"    # YES NO
 
# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=75
TARGET_TEMP_1=75
TARGET_TEMP_2=75
TARGET_TEMP_3=75
TARGET_TEMP_4=75
TARGET_TEMP_5=75
TARGET_TEMP_6=75

Edit 2 :
Acting strange, it reads all targets from  TARGET_TEMP_0=76
More tests :

1bash :
Code:
TARGET_TEMP=74
 
__FAN_ADJUST=5      # Adjustment size in percent
 
POWER_ADJUST=5      # Adjustment size in watts
 
# Difference in actual temperature allowed before action:  Works only if current is BELOW target temp
 
ALLOWED_TEMP_DIFF=3
 
# Restore original power limit if fan speed is lower than this percentage
 
RESTORE_POWER_LIMIT=90
 
# lowest fan speed that will be used
 
MINIMAL_FAN_SPEED=65

Code:
INDIVIDUAL_TARGET_TEMPS="NO"    # YES NO
 
# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=76
TARGET_TEMP_1=70
TARGET_TEMP_2=70
TARGET_TEMP_3=70
TARGET_TEMP_4=75
TARGET_TEMP_5=70

==> 6_autotemplog <==
Code:
GPU 0, Target temp: 76, Current: 72, Diff: 4, Fan: 65, Power: 130.84
GPU 1, Target temp: 76, Current: 67, Diff: 9, Fan: 65, Power: 126.78
GPU 2, Target temp: 76, Current: 63, Diff: 13, Fan: 65, Power: 133.73
GPU 3, Target temp: 76, Current: 67, Diff: 9, Fan: 65, Power: 118.40
GPU 4, Target temp: 76, Current: 70, Diff: 6, Fan: 65, Power: 130.45
GPU 5, Target temp: 76, Current: 65, Diff: 11, Fan: 65, Power: 129.71

Edit 3
Individual target temp works as it should
1bash:
Code:
INDIVIDUAL_TARGET_TEMPS="YES"       # YES NO
 
# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=76
TARGET_TEMP_1=70
TARGET_TEMP_2=70
TARGET_TEMP_3=70
TARGET_TEMP_4=75
TARGET_TEMP_5=70

==> 6_autotemplog <==
Code:
GPU 0, Target temp: 76, Current: 66, Diff: 10, Fan: 70, Power: 111.09
GPU 1, Target temp: 70, Current: 65, Diff: 5, Fan: 65, Power: 121.22
GPU 2, Target temp: 70, Current: 60, Diff: 10, Fan: 65, Power: 119.53
GPU 3, Target temp: 70, Current: 66, Diff: 4, Fan: 65, Power: 118.83
GPU 4, Target temp: 75, Current: 67, Diff: 8, Fan: 65, Power: 118.53
GPU 5, Target temp: 70, Current: 62, Diff: 8, Fan: 65, Power: 118.99

Can any one else test and clarify this please.

Just loaded up the new v0019 onto my rig and works AWESOME!

Only bug I could find was that the maximum script didn't seem to work unless I selected "YES" on setting individual card temps.
But no biggie! Love it! Thanks fullzero

I will look into this; it is probably an error I made when modifying Maxximus007_AUTO_TEMPERATURE_CONTROL to work with lost_post's method for v0019.

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
September 05, 2017, 06:08:42 PM
 #3303

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 :

Quote
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.


salfter
Hero Member
*****
Offline Offline

Activity: 650
Merit: 500


My PGP Key: 92C7689C


View Profile WWW
September 05, 2017, 07:45:11 PM
 #3304

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.

Tipjars: BTC 1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2 LTC LTipsVC7XaFy9M6Zaf1aGGe8w8xVUeWFvR | My Bitcoin Note Generator | Pool Auto-Switchers: zpool MiningPoolHub NiceHash
Bitgem Resources: Pool Explorer Paper Wallet
woodl1
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
September 05, 2017, 07:49:59 PM
 #3305

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
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
September 05, 2017, 08:08:24 PM
 #3306

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
Sr. Member
****
Offline Offline

Activity: 467
Merit: 250


Resident Retard


View Profile
September 05, 2017, 08:22:00 PM
 #3307





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
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
September 05, 2017, 08:36:02 PM
 #3308





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
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
September 06, 2017, 12:40:03 AM
 #3309

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
Member
**
Offline Offline

Activity: 117
Merit: 10


View Profile
September 06, 2017, 01:31:26 AM
Last edit: September 06, 2017, 01:51:12 AM by kk003
 #3310

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



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
Member
**
Offline Offline

Activity: 154
Merit: 12


View Profile WWW
September 06, 2017, 01:37:13 AM
 #3311

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  Smiley
What does this option stands for?

★ ★ ★ ★ ★   DeepOnion  ✔  Anonymous and Untraceable Cryptocurrency  ✔  TOR INTEGRATED & SECURED   ★ ★ ★ ★ ★
› › › › ›  JOIN THE NEW AIRDROP ✈️    ★    ✔ VERIFIED WITH DEEPVAULT  ‹ ‹ ‹ ‹ ‹
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬   ANN  WHITEPAPER  FACEBOOK  TWITTER  YOUTUBE  FORUM   ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
bdog1234
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
September 06, 2017, 02:25:19 AM
 #3312

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



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
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
September 06, 2017, 05:21:04 AM
 #3313

SALFTER_NICEHASH_PROFIT_SWITCHING vs SALFTER_MPH_PROFIT_SWITCHING

what the difference?
FailSaf3
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
September 06, 2017, 05:34:38 AM
 #3314

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
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
September 06, 2017, 06:21:54 AM
 #3315

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? Smiley thanks in advance!
xxcsu
Hero Member
*****
Offline Offline

Activity: 1190
Merit: 580


View Profile WWW
September 06, 2017, 06:35:44 AM
 #3316

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

Learn about Merit & new rank requirements , Learn how to use MERIT , make this community better
If you like the answer you got for your question from any member ,
If you find any post useful , informative use the +Merit button.
jotun
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
September 06, 2017, 06:39:31 AM
 #3317

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

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
Full Member
***
Offline Offline

Activity: 616
Merit: 136


Linux FOREVER! Resistance is futile!!!


View Profile
September 06, 2017, 06:43:08 AM
 #3318

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
Full Member
***
Offline Offline

Activity: 378
Merit: 104


nvOC forever


View Profile
September 06, 2017, 06:50:06 AM
 #3319

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.


DeepOnion    ▬▬  Anonymous and Untraceable  ▬▬    ENJOY YOUR PRIVACY  •  JOIN DEEPONION
▐▐▐▐▐▐▐▐   ANN  Whitepaper  Facebook  Twitter  Telegram  Discord    ▌▌▌▌▌▌▌▌
Get $ONION  (✔Cryptopia  ✔KuCoin)  |  VoteCentral  Register NOW!  |  Download DeepOnion
bdog1234
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
September 06, 2017, 06:50:24 AM
 #3320

That worked. Thanks.

Pages: « 1 ... 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 [166] 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 ... 419 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!