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

Temporel

full member

Activity: 224

Merit: 100

Quote from: Arek on October 24, 2017, 06:02:21 AM

I have the same issue. Both of my rigs running nvOC are down. It looks like some kind of update was done and drivers stopped working.

same here, that rig was up and running since August and it stopped an hour ago. I updated Nvidia drivers and its back online again.

That rig is still on v19 and is my last one on nvOC but after this event, Ill remove some cards and install Windows 10.

Heguli97

full member

Activity: 223

Merit: 101

Quote from: codereddew12 on October 24, 2017, 06:38:58 AM

So for those who are now reaching the login screen and cannot login even when you type in your password. SSH into your rig and run the following commands:

Code:

sudo apt-get purge nvidia*
sudo dpkg --configure -a 
sudo shutdown -r now

Now everything's working back to normal. Not sure why it did that for me. Also, I don't know if the first commmand is necessary, it's just what I typed in initially so I included it.

Too bad I don't have ssh configured/enabled.

codereddew12

newbie

Activity: 36

Merit: 0

So for those who are now reaching the login screen and cannot login even when you type in your password. SSH into your rig and run the following commands:

Code:

sudo apt-get purge nvidia*
sudo dpkg --configure -a 
sudo shutdown -r now

Now everything's working back to normal. Not sure why it did that for me. Also, I don't know if the first commmand is necessary, it's just what I typed in initially so I included it.

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: Heguli97 on October 24, 2017, 06:14:26 AM

I managed to grab an image:

This is happening on both my rigs

Thats not a problem
Ubuntu is checking drive, wait and it will boot

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Nvidia driver updated today on one of my rigs
A reboot fixed my problem
The other one already had latest 384-90

run update / upgrade again

Code:

sudo apt update && sudo apt upgrade && sudo reboot

Arek

newbie

Activity: 44

Merit: 0

Quote from: codereddew12 on October 24, 2017, 06:29:47 AM

I'm getting similar errors as those above me have mentioned this morning where I reach a llogin screen asking me for my password but cannot login. SSH shows this error
Failed to initialize NVML: Driver/library version mismatch -- what's going on here? It only happened on 1 rig for me...so far anyway
...

My stopped working few hours apart.

codereddew12

newbie

Activity: 36

Merit: 0

I'm getting similar errors as those above me have mentioned this morning where I reach a llogin screen asking me for my password but cannot login. SSH shows this error
Failed to initialize NVML: Driver/library version mismatch -- what's going on here? It only happened on 1 rig for me...so far anyway
...

Arek

newbie

Activity: 44

Merit: 0

Quote from: martyroz on October 24, 2017, 06:26:39 AM

Total noob question; Do I have to purchase a supported motherboard in the exact model number listed? Or will most motherboards just work?
I have a Gigabyte Z68XP-UD3R

Most mobos will work, my rigs are running on fm2 and fm2+ mobos.

martyroz

full member

Activity: 325

Merit: 110

Total noob question; Do I have to purchase a supported motherboard in the exact model number listed? Or will most motherboards just work?
I have a Gigabyte Z68XP-UD3R

Heguli97

full member

Activity: 223

Merit: 101

I managed to grab an image:

This is happening on both my rigs

Heguli97

full member

Activity: 223

Merit: 101

This is all of a sudden asking me a login password on both my rigs and when i input miner1 it does nothing.

Arek

newbie

Activity: 44

Merit: 0

I have the same issue. Both of my rigs running nvOC are down. It looks like some kind of update was done and drivers stopped working.

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: woodl1 on October 24, 2017, 05:36:11 AM

hi, all!

I'm using nvOC for a while and today got some rigs broken, tried to see what's wrong and got this error when launching nvidia-smi: "Failed to initialize NVML: Driver/library version mismatch". This happened to every nvidia rig that I tried to reboot. Never touched the drivers in nvOC distro, so I'm confused how this could happen... Does anyone have ideas? Is there any kind of autoupdater which could change something after reboot? How to disable it and make everything working again?

This exactly happened to me this morning!!

Don't know what has triggered this! haven't rebooted my for almost 2 weeks as it was running flawless!! I have restarted it, can connect through teamviewer but cannot see anything, just some blank screen!!

It took 3 hours to get my RIG back UP with version 19.13

My last telegram message ended up like this

Quote

System Boot Time: 2017-10-11 05:11:19
System Up Time: up 1 week, 6 days, 57 minutes
Miner Uptime: 16:13:22
GPU Count: 1

GPU_UTILIZATIONS: Failed to initialize NVML: Driver/library version mismatch

TEMPS: Failed to initialize NVML: Driver/library version mismatch

POWERDRAW: Failed to initialize NVML: Driver/library version mismatch

FAN SPEEDS: Failed to initialize NVML: Driver/library version mismatch

No idea why it happened, can't even access logs because of no access.

I had 3 wallets in there, I need to access it soon or rather than later! (haven't made any backup for them).

woodl1

newbie

Activity: 15

Merit: 0

hi, all!

I'm using nvOC for a while and today got some rigs broken, tried to see what's wrong and got this error when launching nvidia-smi: "Failed to initialize NVML: Driver/library version mismatch". This happened to every nvidia rig that I tried to reboot. Never touched the drivers in nvOC distro, so I'm confused how this could happen... Does anyone have ideas? Is there any kind of autoupdater which could change something after reboot? How to disable it and make everything working again?

pantalyra

newbie

Activity: 46

Merit: 0

weird bug with version 1.3 on my p106 headless rig.

Claymore only reads 11 cards but will mine. I can not get it to find the 12th even though linux sees the card. no error logs

Ethminer selected and the rig never gets past setting the OC before locking up
Genoil works the same as Ethminer. It never gets past setting the OC settings before system locks up.

Quite weird, since I am a newb I went back to the old version of nvOC19 that seemed more stable for now.

moofone

newbie

Activity: 65

Merit: 0

fullzero,

I'm sure you thought of this, and hopefully its already planned for a future version, but it would be really nice for the new "advanced 1bash" to split out individual clocks/power limits to per-algorithm (context of WTM switching)

I also like the idea of moving to json

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: Stubo on October 23, 2017, 03:14:51 PM

Quote from: papampi on October 23, 2017, 03:07:46 PM

Quote from: Stubo on October 23, 2017, 03:01:02 PM

Quote from: papampi on October 23, 2017, 02:30:38 PM

I cut the cable and my miner was keep mining for over 15 minutes without network
Was just getting some slow network warnings from zm

It is interesting that you say that because wdog would catch that (low GPU utilization) and restart which tells me that you probably aren't running it. Correct?

That's exactly the problem,
It was keep mining with all gpu Utilizations at 100%
It was only showing slow network warning without restarting or dropping gpu power
Would love others test zm 0.5.1 without network and see if they experience same or it was some thing else

So your theory is that somehow ZM was caching the sols? Beyond that, I don't know how it would know what work to do beyond a few seconds with no connection.

I was making some tests to improve the webinfo and telegram alerts so I remove the cable to see wdog alerts
when didnt come after a while I checked wdog log and there was no gpu under utilization ... my surprise ... checked miner log and there were lots of " Slow Network" ... ha?
checked miner screen and it was mining ...
I dont know where it got the sols, but it was mining for over 15 min then I get tired and attach network cable.

Will test it again soon.

z-axis

newbie

Activity: 15

Merit: 0

Please excuse my n00b questions:

- I'd like to read the OC script to understand it; can somebody give me the path to it?
- Is there a log of the OC process so I can see if they get applied (instead of just looking at nvidia-smi)?

Thanks!

msmde

member

Activity: 73

Merit: 10

Quote from: damNmad on October 23, 2017, 03:49:44 PM

problem solved, thank you!

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: msmde on October 23, 2017, 03:32:03 PM

Quote from: damNmad on October 23, 2017, 03:26:43 PM

Please delete the $ in the worker name, should be like this KMD_WORKER="MSMDE"

do the same with ZEN too, I remember fullzero replied to one of the similar issue.

Give it a try and let me know if it has worked for you.

if it still doesn't type 'ps aux | grep miner' when you see the 'screen terminated error' and paste the result here.

no go, here is what the terminal returns

Code:

There is no screen to be resumed matching miner.
/home/m1/2unix: line 30:  2280 Terminated              bash '/home/m1/3main'

here is quake return for ps aux | grep miner

Code:

m1        2838  0.0  0.0  14224   928 pts/16   S+   16:32   0:00 grep --color=auto miner

if [ $COIN == "KMD" ]
then

if [ $EWBF_VERSION == "3_3" ]
then
HCD='/home/m1/KMD/v3_3/miner'
fi

if [ $EWBF_VERSION == "3_4" ]
then
HCD='/home/m1/KMD/v3_4/miner'
fi

KMDADDR="$KMD_ADDRESS.$KMD_WORKER"

screen -dmS miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $KMD_POOL --user $KMDADDR --pass z --port $KMD_PORT;

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

BITCOIN="theGROUND"

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

Ok replace the above 3main KMD code with the below.

Code:

if [ $COIN == "KMD" ]
then

if [ $EWBF_VERSION == "3_3" ]
then
HCD='/home/m1/zec/v3_3/miner'
fi

if [ $EWBF_VERSION == "3_4" ]
then
HCD='/home/m1/zec/v3_4/miner'
fi

KMDADDR="$KMD_ADDRESS.$KMD_WORKER"

screen -dmS miner $HCD --eexit 3 --fee $EWBF_PERCENT --pec --server $KMD_POOL --user $KMDADDR --pass z --port $KMD_PORT;

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

BITCOIN="theGROUND"

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

Topic: [ mining os ] nvoc - page 171. (Read 418546 times)