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

[Moordact]

Send: resources temporary unavailable?

New zcash miner New beta get it on multiple miners??

[1714277157]

1714277157

[1714277157]

1714277157

[dstm]

Send: resources temporary unavailable?

New zcash miner New beta get it on multiple miners??

I'm pretty verbose on networking currently. It's verbose to make sure everything is working as expected.
This is nothing to worry about if it doesn't happen often.
It means that kernel's tx-buffer is full.

Does it happen often?
It happens usually on a (temporary) bad network connection.

[Moordact]

I just noticed on the fresh installs.

I have 5 x 12gpu 1070 rigs running nvoc zcash.

It should be a pretty solid network connection also.

[kk003]

0019-1.1 is not able to pick up an IP address on a consistent basis.  It only picks it up on every other reboot or thereabouts.

If I run this from the console

Code:

m1@skylake:~$ IPW=$(ifconfig | sed -En 's/127.0.0.1//;s/.*inet (addr:)?(([0-9]*\.){3}[0-9]*).*/\2/p')
m1@skylake:~$ echo “My IP is” $IPW

It returns nothing about 50% of the time.

0019-1 did not have this issue.

I'm seeing this behavior on rigs with the following mobos:

ASRock Fatal1ty Z170 Gaming K6 (using on-board NIC)
Asus Maximus VIII Extreme (using Intel X520 10G NIC)

My main rigs use these mobos, but I have not dared upgrade any of those yet:

Asus PRIME Z270-A
MSI Z270A PRO

Is this a known issue?

I'll check load average at the time that problem occurs:

Code:

uptime

If you use static ip may be could help disable network-manager.service.
Check the status like this:

Code:

systemctl status network-manager.service

May be the network is down so the ifconfig can't get the ip?

This script may help you to test that:

Code:

#!/bin/bash
LOG="test_network.log"
uptime &>> $LOG
# ping 3 packets every 2 seconds, wait 3 seconds maximum
/bin/echo "$(date +%F\ %T) &>> $LOG
/bin/echo "Pining 8.8.8.8 with 3 paquets of data every 2 segs, wait 3 segs max" &>> $LOG
PING=$(ping -n -c 3 -i 2 -W 3 8.8.8.8 2>&1)

if [[ $? != 0 ]]; then          # If not response from host
        if [[ $PING =~ "loss" ]]; then
               # no reply
                ERROR=$(echo "$PING" | grep 'loss')
         else
               # destination unreachable
                ERROR=$PING
         fi

        echo "ERROR ----> $(date +%F\ %T) - Failed check - $ERROR" &>> $LOG
        echo &>> $LOG
exit
fi
/bin/echo "8.8.8.8 ----> OK" &>> $LOG
/bin/echo "------------------------------------" &>> $LOG
/bin/echo &>> $LOG
exit

In order to get it working first do:

Code:

nano /home/m1/net_uptime.sh

Copy the script. Then CTRL+O, say yes to save the file.
then:

Code:

chmod 700 /home/m1/net_uptime.sh

run it from cron:

Code:

crontab -e 

add this line to run it every minute:

Code:

*/1 * * * * /home/m1/net_uptime.sh > /dev/null 2>&1

if your system open the crontab file with "vi" then: ":wq" to write the modification on crontab and exit.
if your system open the crontab file with "nano" then: "CTRL+O", say yes to write the modification on crontab and exit.

you should get to the log file here /home/m1/test_network.log

Hope it helps.

[dstm]

I just noticed on the fresh installs.

I have 5 x 12gpu 1070 rigs running nvoc zcash.

It should be a pretty solid network connection also.

It might happen if some host/applications is using all network-bandwidth temporary.                                           
Could you please provide some logs?

[fullzero]

Updated my telegram and it will be pushed in v0019-1.2
Here it is if you want to get it sooner :
https://pastebin.com/w3T4BcKm

replace it with existing one
This is what you get if you set the timer :

Code:

Worker: nv102
Boot Time: 2017-09-24 06:11:41
System Up Time: up 7 hours, 1 minute
Miner Uptime:    06:59:02
GPU Count: 7
GPU Utilization: 
99 100 97 97 100 97 99

 Temp, Fan, Power:
GPU 0, Target temp:  75, Current:  70, Diff:  5, Fan:  65, Power:  135.25
GPU 1, Target temp:  75, Current:  68, Diff:  7, Fan:  65, Power:  137.36
GPU 2, Target temp:  75, Current:  70, Diff:  5, Fan:  65, Power:  136.05
GPU 3, Target temp:  75, Current:  72, Diff:  3, Fan:  65, Power:  133.92
GPU 4, Target temp:  75, Current:  57, Diff:  18, Fan:  65, Power:  136.58
GPU 5, Target temp:  75, Current:  67, Diff:  8, Fan:  65, Power:  137.50
GPU 6, Target temp:  75, Current:  67, Diff:  8, Fan:  65, Power:  132.73

And these are IAmNotAJeep watch dog alerts in case any thing goes wrong:

Code:

date-time - Starting miner restart script.

Code:

date-time - Lost GPU so restarting system.
reboot in 10 seconds

Code:

date-time - Utilization is too low: restart 3main

Code:

date-time - Utilization is too low: reviving did not work so restarting system in 10 seconds

If you have slow/small usb it will clear temp and wdog logs after every message is sent

Looks good; I will made these changes to -1.2.

[fullzero]

Some questions and / or Suggestions :

Would it be possible to output all the variables from the 1bash file to use a CSV file where we could list the currencies, our respective wallets for each currency, the associated tradding pools and platforms as well as their ports and usernames? and finally if we want to undermine it or not according to its profitability at the moment t + 3 min (in terms of its difficulty and its profitability).

I ask this because it has to undermine a little of everything and everywhere, this file would allow you to manage which miner mine what, when, on which pools that send themselves on which platforms of tradding...

Without keeping an Excel file up to date with wallets, addresses, and other pools, there is something to lose.

Column headers proposed for CSV file :

COIN   ALGO   ALGO_PL   ALGO_CORE_OVCLOCK   ALGO_MEM_OVCLOCK   GLOBAL_TARGET_TEMP   MINER_SOFTWARE   EXTENSION_ARGUMENTS (DUAL MINER)   SOFT_VERSION_MINER   WORKER (NAME)   WALLET_ ADDRESS   WALLET_PROVIDER_NAME   POOL_NAME   POOL_DNS   POOL_PORT   DUAL_WALLET ADDRESS   DUAL_WALLET_PROVIDER_NAME   DUAL_POOL_NAME   DUAL_POOL_DNS   DUAL_POOL_PORT   BTC_ADDRESS   BTC_ADDRESS_PROVIDER   COMMENT

Later it will be possible to add more columns in the file.
For example, if papami or damNmad (i don't remmeber who work on this) produces us a profit script, it would be possible to add a SWITCH_PROFIT column whose value could be as YES or NO. Thus, the profit script would compare only selected coins with each other and mine for the best profit while choosing oneself each coin we chose (not the coins proposals of the pools).

I do not know if I formulated my idea correctly, but to summarize, it was to make a database file in CSV format that we could thus insert more easily into excel or calc.

this would also greatly reduce the 1bash file but would not remove any utility

This is a useful feature I will add it to the list.

[fullzero]

I update the versión to 0019 now It doesnt start mining. It doesnt hangs, but It repetively tries to start mining but It reaches until Launching: Mining process.

I can manually start claymore and It works

Update to 0019-1.1 instructions were posted few pages back. You will need to re-edit your 1bash file again after the update.

I updated from 0018 to 0019. No to 0019-1.1

I think there are lots of changes from v18 to v19, you need to update the 1bash with your coin details again! Can't use your old 1bash because 1bash has been split into two parts in v19 in 1bash and 3main. So, you need to update 1bash (which only holds coin details). Hope it make sense, try update 1bash and let us know if you still see any issues.

Note : in v19 it won't copy the 1bash from the spare drive, you need to copy it from there manually.

I am using the default 1bash, I only want to see that it can work with all the video cards connected and stable. Is there a mandatory change over default 1bash that I need to do in order to it starts working?

I am using the default 1bash

you mean the one from the v19 right?

I only want to see that it can work with all the video cards connected and stable

You might need to double check all the options before you start mining.

Is there a mandatory change over default 1bash that I need to do in order to it starts working

Can't completely recall because there are two more beta releases I've tested, but you definitely need to edit the one under /home/m1/ folder to let the mining start.

Yes, the default that comes in v0019.
I didn't let it completely default, I changed the currency to DUAL_ETH_DCR and the eth pool and worker to automatic.
I will try another time this afternoon.

@Edit: I've found the problem, I never changed the miner from ETHMINER to CLAYMORE, and the coin was set to DUAL_ETH_DCR

This 'DUAL_ETH_DCR' coin selection should've worked because the in 3main no matter whether you've selected ETHMINER or CLAYMORE it is configured to pick CLAYMORE if you select any DUAL_XXX_XXX coin.

If you haven't resolved this yet: when using v0019 it defaults to using REMOTE which launches the screen containing the mining process in the background; If you updated to -1.1 I changed the default back to LOCAL as this was causing too much confusion.  After updating to -1.1 you will need to configure the 1bash in the /home/m1 directory (click the file cabinet icon on the left) with your addresses / COIN selection / other desired settings.

[fullzero]

Hi guys,

I have recently built a new rig with 13 P106-100 ASUS cards on nv0019 running -200cc 1550mc and PL90. I have a weird problem that after some time the hashrate on all cards drop by 50% or more and doesn't go back up, the miner doesn't restart and it just keeps running with lower hashrate.  This time it did this after 7 hours , with 7 cards running it was up for over 12hours and no problems. Has anyone experienced this before and maybe you know where the problem is?

I am obviously running headless and using SSH to monitor the rig and adjust the settings.

PS. The miner or the OS doesn't restart the miner or reboot the system, just the hashrate drops pretty badly from 328 to 140 MH/s.

Thanks in advance to everyone who can help and also thanks to fullzero for the new version!

I've had similar issue, when one or two cards would semi-freeze, bringing the whole rig to work extremely slow. I added whole bunch of debug options in the watchdog to figure out what was going on... it turns out watcdog enters into a loop for counting down errors before trying to restart the mining process and it takes about 5-10 min to change the count by -1 and it won't catch the low utilization to restart the rig until few hours later.

The mining doesn't stop but continues at reduced hash speed, some cards drop from 25 to 13 MH/s, some down to 0.

To make it worst, during this semi-hang the driver changes p-state due to low/high utilization so it ends up with some cards at p2, some at p8 and some at p0 which screws the OC and makes more cards to hang.

I have some ideas to modify or even rewrite the watchdog to address these issues and will post it once finished. I am quite busy atm to work on it but I can post logs from the added debug so that devs can look into it.

Anyway, it turns out all of this was caused by two cards (same brand/model/memory) that couldn't handle the overclocking as the rest of the cards. By reducing the memory overclock on these two from 1820 to 1700 it stabilized the rig, no more hangups.

For now, reduce your overclock and give it a try, see if it fixes the problem. Please post back with results.

Have you managed to improve your watchdog as you said in this previous post?

Hey CryptAtomeTrader44,
I had some code that I was testing, however after updating to 19-1, the update has overwritten the watchdog file with all the changes I had in it and I had no backup of the modified wd
I have to start over now, hopefully I will have working beta version by the end of the week. I will post once I am done.

I warned about this in the update post; Please always backup any custom modifications / your 1bash before updating. 

[fullzero]

please disregard my earlier comments about not having temperature controls after updating to beta. Just had to slowly put my rig back together and it seems to be running stable on 13 cards.

Does anyone know how to mix amd and nvidia on linux?

I have done this before; IMO you are better off making 2 rigs one AMD and one Nvidia.

[fullzero]

oh, i added in 1bash, sudo nano 1bash
and my version is v0019

Code:

UBQ_WORKER="$WORKERNAME"
UBQ_ADDRESS="my ubq wallet"
UBQ_POOL="stratum+tcp://us.ubiqpool.io:8008"

Code:

DOT_POOL_FORMAT_or_FORWARD_SLASH_POOL_FORMAT="DOT"

These lines already exist in 1bash; please check (you can see it after EXP coin details). You need to delete the newly added lines and edit the existing ones.

If you are using claymore the above settings should work.

If you still facing issue, when you see this error

Code:

ETH AUTHORIZATION FAILED.. stratum reading socket failed

please run this command:

Code:

ps aux | grep miner

& paste the result here; I can help you from that.

I don't see anything after EXP... that is why i added them manually..

That's odd!!!

If it wasn't there, then how come you were getting Authorization failure error??!!!

OK then please start mining UBQ (though you getting error) and paste the result of 'ps aux | grep miner' command here.

just send you a message

Did you get this working?

[fullzero]

Tried to use the "auto update" to get to 0019-1.1 and my machine failed to load, was stuck on black screen forever.
had to re-image back to 0019

to update to -1.1 from v0019 follow the directions on: https://bitcointalk.org/index.php?topic=1854250.msg22109824#msg22109824

Did you follow this process?

[fullzero]

0019-1.1 is not able to pick up an IP address on a consistent basis.  It only picks it up on every other reboot or thereabouts.

If I run this from the console

Code:

m1@skylake:~$ IPW=$(ifconfig | sed -En 's/127.0.0.1//;s/.*inet (addr:)?(([0-9]*\.){3}[0-9]*).*/\2/p')
m1@skylake:~$ echo “My IP is” $IPW

It returns nothing about 50% of the time.

0019-1 did not have this issue.

I'm seeing this behavior on rigs with the following mobos:

ASRock Fatal1ty Z170 Gaming K6 (using on-board NIC)
Asus Maximus VIII Extreme (using Intel X520 10G NIC)

My main rigs use these mobos, but I have not dared upgrade any of those yet:

Asus PRIME Z270-A
MSI Z270A PRO

Is this a known issue?

I'll check load average at the time that problem occurs:

Code:

uptime

If you use static ip may be could help disable network-manager.service.
Check the status like this:

Code:

systemctl status network-manager.service

May be the network is down so the ifconfig can't get the ip?

This script may help you to test that:

Code:

#!/bin/bash
LOG="test_network.log"
uptime &>> $LOG
# ping 3 packets every 2 seconds, wait 3 seconds maximum
/bin/echo "$(date +%F\ %T) &>> $LOG
/bin/echo "Pining 8.8.8.8 with 3 paquets of data every 2 segs, wait 3 segs max" &>> $LOG
PING=$(ping -n -c 3 -i 2 -W 3 8.8.8.8 2>&1)

if [[ $? != 0 ]]; then          # If not response from host
        if [[ $PING =~ "loss" ]]; then
               # no reply
                ERROR=$(echo "$PING" | grep 'loss')
         else
               # destination unreachable
                ERROR=$PING
         fi

        echo "ERROR ----> $(date +%F\ %T) - Failed check - $ERROR" &>> $LOG
        echo &>> $LOG
exit
fi
/bin/echo "8.8.8.8 ----> OK" &>> $LOG
/bin/echo "------------------------------------" &>> $LOG
/bin/echo &>> $LOG
exit

In order to get it working first do:

Code:

nano /home/m1/net_uptime.sh

Copy the script. Then CTRL+O, say yes to save the file.
then:

Code:

chmod 700 /home/m1/net_uptime.sh

run it from cron:

Code:

crontab -e 

add this line to run it every minute:

Code:

*/1 * * * * /home/m1/net_uptime.sh > /dev/null 2>&1

if your system open the crontab file with "vi" then: ":wq" to write the modification on crontab and exit.
if your system open the crontab file with "nano" then: "CTRL+O", say yes to write the modification on crontab and exit.

you should get to the log file here /home/m1/test_network.log

Hope it helps.

My guess is this is due to a system update which changed the priority of networking services or created a conflict.

I will add a conditional to verify the IP is properly detected in an update; what is the IP set to when it is not properly set?

[CryptAtomeTrader44]

Hey CryptAtomeTrader44,
I had some code that I was testing, however after updating to 19-1, the update has overwritten the watchdog file with all the changes I had in it and I had no backup of the modified wd
I have to start over now, hopefully I will have working beta version by the end of the week. I will post once I am done.

Arf, the shoemaker's syndrome always badly shod! The computer technician (engineer?) Who does not back up his script before updating! hi hi ha ha oh oh! I know that too! I do not stop tinkering the Salfter files to have a little more details at my convenience on the MPH-Switch, but I do not know where the original files at all. But anyway, my changes are very minimal because I do not understand much about Python. Even some Bash script goes beyond me then ... For example I can not reproduce this manual command of nvidia-settings that would allow me to reduce a little fan speed when they make too much noise annoy me.

Post us your script with an explanatory comment on the changes made. At least it will be here and therefore saved in some sorts.

yup... lesson learned...

i will post once i have something modded, right now i am at square one.

here's the command to change fan speed on a single GPU:

Code:

nvidia-settings -a [gpu:5]/GPUFanControlState=1 -a [fan:5]/GPUTargetFanSpeed=70

This will set fan on GPU5 to 70%. Change as you see fit, however note that if you have Maxximus007_auto_temp control enabled, it will readjust it back on its regular cycle.

That's the response that i recieve :

Code:

sudo nvidia-settings -a [gpu:0]/GPUFanControlState=1 -a [fan:0]/GPUTargetFanSpeed=30
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

[CryptAtomeTrader44]

if your system open the crontab file with "vi" then: ":wq" to write the modification on crontab and exit.
if your system open the crontab file with "nano" then: "CTRL+O", say yes to write the modification on crontab and exit.

you should get to the log file here /home/m1/test_network.log

Hope it helps.

VI, the best of the best full text editor and massive substitutor by "the power of G"

I think, we coulf make some script likes profit switching 's salfter's script with, Vi, cat, Grep, egrep, pgrep sed, awk, and others basics systems integrated commands, méta and spécials characters.

only I do not feel able to do it

[dstm]

if your system open the crontab file with "vi" then: ":wq" to write the modification on crontab and exit.
if your system open the crontab file with "nano" then: "CTRL+O", say yes to write the modification on crontab and exit.

you should get to the log file here /home/m1/test_network.log

Hope it helps.

VI, the best of the best full text editor and massive substitutor by "the power of G"

Sry for spamming this thread, couldn't resist.
I prefer emacs

[crazydane]

0019-1.1 is not able to pick up an IP address on a consistent basis.  It only picks it up on every other reboot or thereabouts.

If I run this from the console

Code:

m1@skylake:~$ IPW=$(ifconfig | sed -En 's/127.0.0.1//;s/.*inet (addr:)?(([0-9]*\.){3}[0-9]*).*/\2/p')
m1@skylake:~$ echo “My IP is” $IPW

It returns nothing about 50% of the time.

0019-1 did not have this issue.

I'm seeing this behavior on rigs with the following mobos:

ASRock Fatal1ty Z170 Gaming K6 (using on-board NIC)
Asus Maximus VIII Extreme (using Intel X520 10G NIC)

My main rigs use these mobos, but I have not dared upgrade any of those yet:

Asus PRIME Z270-A
MSI Z270A PRO

Is this a known issue?

I'll check load average at the time that problem occurs:

Code:

uptime

If you use static ip may be could help disable network-manager.service.
Check the status like this:

Code:

systemctl status network-manager.service

May be the network is down so the ifconfig can't get the ip?

This script may help you to test that:

Code:

#!/bin/bash
LOG="test_network.log"
uptime &>> $LOG
# ping 3 packets every 2 seconds, wait 3 seconds maximum
/bin/echo "$(date +%F\ %T) &>> $LOG
/bin/echo "Pining 8.8.8.8 with 3 paquets of data every 2 segs, wait 3 segs max" &>> $LOG
PING=$(ping -n -c 3 -i 2 -W 3 8.8.8.8 2>&1)

if [[ $? != 0 ]]; then          # If not response from host
        if [[ $PING =~ "loss" ]]; then
               # no reply
                ERROR=$(echo "$PING" | grep 'loss')
         else
               # destination unreachable
                ERROR=$PING
         fi

        echo "ERROR ----> $(date +%F\ %T) - Failed check - $ERROR" &>> $LOG
        echo &>> $LOG
exit
fi
/bin/echo "8.8.8.8 ----> OK" &>> $LOG
/bin/echo "------------------------------------" &>> $LOG
/bin/echo &>> $LOG
exit

In order to get it working first do:

Code:

nano /home/m1/net_uptime.sh

Copy the script. Then CTRL+O, say yes to save the file.
then:

Code:

chmod 700 /home/m1/net_uptime.sh

run it from cron:

Code:

crontab -e 

add this line to run it every minute:

Code:

*/1 * * * * /home/m1/net_uptime.sh > /dev/null 2>&1

if your system open the crontab file with "vi" then: ":wq" to write the modification on crontab and exit.
if your system open the crontab file with "nano" then: "CTRL+O", say yes to write the modification on crontab and exit.

you should get to the log file here /home/m1/test_network.log

Hope it helps.

My guess is this is due to a system update which changed the priority of networking services or created a conflict.

I will add a conditional to verify the IP is properly detected in an update; what is the IP set to when it is not properly set?

In my case, no IP is assigned.  So a reboot from the local console is the only way to get back in.  All devices on my LAN (about 60) have static mappings managed by my router/gateway.  Never had issues with them not being assigned IPs on reboots or when their leases renew.  This behavior is definitely associated with 19-1.1  I agree is sounds related to networking services or a conflict.

[Temporel]

if your system open the crontab file with "vi" then: ":wq" to write the modification on crontab and exit.
if your system open the crontab file with "nano" then: "CTRL+O", say yes to write the modification on crontab and exit.

you should get to the log file here /home/m1/test_network.log

Hope it helps.

VI, the best of the best full text editor and massive substitutor by "the power of G"

Sry for spamming this thread, couldn't resist.
I prefer emacs

learned vi when I was younger, discovered pico, dropped vi and now I use nano. I dont do much, thats probably why Im fine with it

[fullzero]

0019-1.1 is not able to pick up an IP address on a consistent basis.  It only picks it up on every other reboot or thereabouts.

If I run this from the console

Code:

m1@skylake:~$ IPW=$(ifconfig | sed -En 's/127.0.0.1//;s/.*inet (addr:)?(([0-9]*\.){3}[0-9]*).*/\2/p')
m1@skylake:~$ echo “My IP is” $IPW

It returns nothing about 50% of the time.

0019-1 did not have this issue.

I'm seeing this behavior on rigs with the following mobos:

ASRock Fatal1ty Z170 Gaming K6 (using on-board NIC)
Asus Maximus VIII Extreme (using Intel X520 10G NIC)

My main rigs use these mobos, but I have not dared upgrade any of those yet:

Asus PRIME Z270-A
MSI Z270A PRO

Is this a known issue?

I'll check load average at the time that problem occurs:

Code:

uptime

If you use static ip may be could help disable network-manager.service.
Check the status like this:

Code:

systemctl status network-manager.service

May be the network is down so the ifconfig can't get the ip?

This script may help you to test that:

Code:

#!/bin/bash
LOG="test_network.log"
uptime &>> $LOG
# ping 3 packets every 2 seconds, wait 3 seconds maximum
/bin/echo "$(date +%F\ %T) &>> $LOG
/bin/echo "Pining 8.8.8.8 with 3 paquets of data every 2 segs, wait 3 segs max" &>> $LOG
PING=$(ping -n -c 3 -i 2 -W 3 8.8.8.8 2>&1)

if [[ $? != 0 ]]; then          # If not response from host
        if [[ $PING =~ "loss" ]]; then
               # no reply
                ERROR=$(echo "$PING" | grep 'loss')
         else
               # destination unreachable
                ERROR=$PING
         fi

        echo "ERROR ----> $(date +%F\ %T) - Failed check - $ERROR" &>> $LOG
        echo &>> $LOG
exit
fi
/bin/echo "8.8.8.8 ----> OK" &>> $LOG
/bin/echo "------------------------------------" &>> $LOG
/bin/echo &>> $LOG
exit

In order to get it working first do:

Code:

nano /home/m1/net_uptime.sh

Copy the script. Then CTRL+O, say yes to save the file.
then:

Code:

chmod 700 /home/m1/net_uptime.sh

run it from cron:

Code:

crontab -e 

add this line to run it every minute:

Code:

*/1 * * * * /home/m1/net_uptime.sh > /dev/null 2>&1

if your system open the crontab file with "vi" then: ":wq" to write the modification on crontab and exit.
if your system open the crontab file with "nano" then: "CTRL+O", say yes to write the modification on crontab and exit.

you should get to the log file here /home/m1/test_network.log

Hope it helps.

My guess is this is due to a system update which changed the priority of networking services or created a conflict.

I will add a conditional to verify the IP is properly detected in an update; what is the IP set to when it is not properly set?

In my case, no IP is assigned.  So a reboot from the local console is the only way to get back in.  All devices on my LAN (about 60) have static mappings managed by my router/gateway.  Never had issues with them not being assigned IPs on reboots or when their leases renew.  This behavior is definitely associated with 19-1.1  I agree is sounds related to networking services or a conflict.

Let me know if -1.2 resolves this problem.

[crazydane]

I set auto update to yes in 1bash and rebooted.  It started mining, then killed the miner and started the update process (which includes a newer nVidia driver).  Anyway, when it was done, it rebooted to this:



I type it the miner1 password, and it just keep looping back to the same prompt.  Rebooted and got the same thing.

I SCP'ed over my 0019-1.1 1bash and 3main files and rebooted again.  Got to the same screen as above.  So I guess my only option now is to go back to the 0019 image and start fresh?