[ mining os ] nvoc

[damNmad]

I have a problem with the 19-1.3 beta update process.

I followed these instructions: https://bitcointalk.org/index.php?topic=1854250.msg22109824#msg22109824

Once the the machine reboots, my teamviewer stopped to work. So I used putty/ssh and checked the home folder. There was no "your_old_1bash" file and when I opened the 1bash to check version number it still says v19 (not 19-1.3, it's my old v19 bash file).

Now when I try to run the update again, it just downloads some pastebin files and claims "no change".

What to do besides burning new stick?

In your 1bash, do you have this:

   AUTO_UPDATE="BETA"         # STABLE  or  BETA

It needs be set to BETA not STABLE to get to 19.1-3 by running 4update.

Hope this helps.

Thanks @Stubo

I really like it when newbies answering the questions, it will easy of the dev, so that he can concentrate on actual development and fix the issues.

Good going guys keep it up

[mraug]

I have a problem with the 19-1.3 beta update process.

I followed these instructions: https://bitcointalk.org/index.php?topic=1854250.msg22109824#msg22109824

Once the the machine reboots, my teamviewer stopped to work. So I used putty/ssh and checked the home folder. There was no "your_old_1bash" file and when I opened the 1bash to check version number it still says v19 (not 19-1.3, it's my old v19 bash file).

Now when I try to run the update again, it just downloads some pastebin files and claims "no change".

What to do besides burning new stick?

In your 1bash, do you have this:

   AUTO_UPDATE="BETA"         # STABLE  or  BETA

It needs be set to BETA not STABLE to get to 19.1-3 by running 4update.

Hope this helps.

I did that, I followed these instructions: https://bitcointalk.org/index.php?topic=1854250.msg22109824#msg22109824

Anyway, I managed to find a workaround, I run the 2unix bash manualy with

 bash '/home/m1/2unix'

This started the v0019-1.3 update process and after reboot it was running OK.

[Havesovgosh]

Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.

I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.

In first RIG In temp Screen I have following errors for all GPUs:

ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------

IN Second in temp Screen the following:

ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------


Please help, What I'm doing wrong or what is missing in my config.

are you using:

Code:

P106_100_FULL_HEADLESS_MODE="YES"

?

My configuration was set to "NO".

I changed on one rig to "YES" and getting this error in the "temp" screen:

----------------
Mon Oct 23 01:24:05 EDT 2017 - Adjusting Fan for gpu:8. Old: 50 New: 45 Temp: 46
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.

Mon Oct 23 01:24:05 EDT 2017 - All good, will check again soon
----------

Also there was an error related to "persistence mode". I have enabled it manually for all GPUs.

Please Help!

Hi fullzero, Guys,

I have digged and try lot of things.
Unfortunately, without good results.
Now, I'm sure that very small thing I have missed and that's killing me.
What is I'm doing wrong?? Please support.

[leenoox]

Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.

I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.

In first RIG In temp Screen I have following errors for all GPUs:

ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------

IN Second in temp Screen the following:

ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------


Please help, What I'm doing wrong or what is missing in my config.

are you using:

Code:

P106_100_FULL_HEADLESS_MODE="YES"

?

My configuration was set to "NO".

I changed on one rig to "YES" and getting this error in the "temp" screen:

----------------
Mon Oct 23 01:24:05 EDT 2017 - Adjusting Fan for gpu:8. Old: 50 New: 45 Temp: 46
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.

Mon Oct 23 01:24:05 EDT 2017 - All good, will check again soon
----------

Also there was an error related to "persistence mode". I have enabled it manually for all GPUs.

Please Help!

Hi fullzero, Guys,

I have digged and try lot of things.
Unfortunately, without good results.
Now, I'm sure that very small thing I have missed and that's killing me.
What is I'm doing wrong?? Please support.

Don't worry about persistence mode, it's not fatal, just ignore that message.

Not many of us have those P106 cards to help troubleshoot. Hopefuly someone that has them and have a working setup can help you.

Your problem might be related to your motherboard. Apperantly there is known problem where motherboard doesn't work well with more than 12 or was it 13 GPU's. Asus is aware of the problem and they intend to fix it with new bios update. Check if they released new bios.

[Havesovgosh]

Hi,
I need some support.
I have installed nvoc 0019 in my two rigs:
motherboard: ASUS B250 MIning
Videos: ASUS 106-100 mining edition.

I have disabled IAmNotAJeep_and_Maxximus007_WATCHDOG="NO", because miner is restarting periodically.

In first RIG In temp Screen I have following errors for all GPUs:

ERROR: The GPU has fallen off the bus or has otherwise become inaccessible
ERROR: Error assigning value 57 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:13]) as specified in assignment '[fan:13]/GPUTargetFanSpeed=57' (Unknown Error).
------------------------

IN Second in temp Screen the following:

ERROR: Error assigning value 52 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:7]) as specified in assignment '[fan:7]/GPUTargetFanSpeed=52' (Unknown Error).
GPU 8, Target temp: 70, Current: 46, Diff: 24, Fan: 51, Power: 99.41
Sun Oct 22 00:35:58 EDT 2017 - Adjusting Fan for gpu:8. Old: 51 New: 46 Temp: 46
------------------------------


Please help, What I'm doing wrong or what is missing in my config.

are you using:

Code:

P106_100_FULL_HEADLESS_MODE="YES"

?

My configuration was set to "NO".

I changed on one rig to "YES" and getting this error in the "temp" screen:

----------------
Mon Oct 23 01:24:05 EDT 2017 - Adjusting Fan for gpu:8. Old: 50 New: 45 Temp: 46
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.

Mon Oct 23 01:24:05 EDT 2017 - All good, will check again soon
----------

Also there was an error related to "persistence mode". I have enabled it manually for all GPUs.

Please Help!

Hi fullzero, Guys,

I have digged and try lot of things.
Unfortunately, without good results.
Now, I'm sure that very small thing I have missed and that's killing me.
What is I'm doing wrong?? Please support.

Don't worry about persistence mode, it's not fatal, just ignore that message.

Not many of us have those P106 cards to help troubleshoot. Hopefuly someone that has them and have a working setup can help you.

Your problem might be related to your motherboard. Apperantly there is known problem where motherboard doesn't work well with more than 12 or was it 13 GPU's. Asus is aware of the problem and they intend to fix it with new bios update. Check if they released new bios.

Thx for your soon feedback. I'll check the bios update.

Hope someone can help!!

[wesleypolling]

Hello fellow miners,

Currently I'm running 3 rigs with 6x 1070 GPU.
Setup NVOC Nvidea miner on Zcash ZEC on Flypool.

I have some problems since yesterday, where the miners work fine and suddenly stop working all 3 together.

Mail alert :
•   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Last seen 51 minutes 59 seconds ago
•   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Last seen 58 minutes 38 seconds ago
•   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Last seen 51 minutes 51 seconds ago

Then I reboot and everything seems to be working fine.

I checked my internet connection but everything seems fine, rebooted central modem several times but seems fine.
I don't think it is hardware, since everything is stable for over a month and works perfect when I reboot.

If the cause is a power surge or internet malfunction, it is weird that they don't stop working all together.

If anyone has similar problems or has some tips to try feel free to share !
Thanks.

https://ibb.co/fMjxfm
https://ibb.co/kd0aY6

Kind regards,
Wesley Polling

[papampi]

Hello fellow miners,

Currently I'm running 3 rigs with 6x 1070 GPU.
Setup NVOC Nvidea miner on Zcash ZEC on Flypool.

I have some problems since yesterday, where the miners work fine and suddenly stop working all 3 together.

Mail alert :
•   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Last seen 51 minutes 59 seconds ago
•   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Last seen 58 minutes 38 seconds ago
•   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Last seen 51 minutes 51 seconds ago

Then I reboot and everything seems to be working fine.

I checked my internet connection but everything seems fine, rebooted central modem several times but seems fine.
I don't think it is hardware, since everything is stable for over a month and works perfect when I reboot.

If the cause is a power surge or internet malfunction, it is weird that they don't stop working all together.

If anyone has similar problems or has some tips to try feel free to share !
Thanks.




Kind regards,
Wesley Polling

Do you use dstm zm miner or ewbf?
I noticed zm don't disconnect when network is not present
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

[mikespax]

Joined the discord! - https://discord.gg/8YDFEvY

Just thought I would add that after upgrading my CPU, claymore is still the only miner that doesn't crash immediately on the 19 GPU rig. Still on 4GB of ram though, so I suppose I should wait for that upgrade to arrive. If it helps, claymore does specifically list that his miner supports like 30+ GPUs so I'm thinking that's the reason why it's the only one that works.

[Stubo]

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?

[prodigz]

I an running into an issue mining VTC.  I am running my own pool and for some reason it is not accepting any shares if there is a worker name present.  If it is just the wallet address it works fine.
I cant seem to get nvOC to use no worker name, I have tried to use the wallet as the name and to hash it out completely and it still inputs "." as the name.  Has anyone else ran into this?  
Can you disable worker names somehow?

Thanks

[papampi]

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

[Stubo]

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.

[msmde]

i'm working on getting KMD going but rig doesn't seem to be picking it up. some coins are working while others are not, so it is probably a small detail that i'm overlooking.

I followed the instructions in this post https://bitcointalk.org/index.php?topic=1854250.msg21422521#msg21422521

here's my 1bash file

KMD_WORKER="$MSMDE"
KMD_ADDRESS="myaddresshere"
KMD_POOL="luckpool.org"
KMD_PORT="3857"

as per the above instructions, i also added to the 3main file. maybe i put it in the wrong spot? I put it right before hush and after zen and I placed the KMD information for the 1bash file in the same spot.

the zen 1bash file info looks just like the kmd info but zen runs fine

ZEN_WORKER="$MSMDE"
ZEN_ADDRESS="myaddresshere"
ZEN_POOL=" luckpool.org"
ZEN_PORT="3057"



terminal returns

Code:

[screen is terminating]

[damNmad]

i'm working on getting KMD going but rig doesn't seem to be picking it up. some coins are working while others are not, so it is probably a small detail that i'm overlooking.

I followed the instructions in this post https://bitcointalk.org/index.php?topic=1854250.msg21422521#msg21422521

here's my 1bash file

KMD_WORKER="$MSMDE"
KMD_ADDRESS="myaddresshere"
KMD_POOL="luckpool.org"
KMD_PORT="3857"

as per the above instructions, i also added to the 3main file. maybe i put it in the wrong spot? I put it right before hush and after zen and I placed the KMD information for the 1bash file in the same spot.

the zen 1bash file info looks just like the kmd info but zen runs fine

ZEN_WORKER="$MSMDE"
ZEN_ADDRESS="myaddresshere"
ZEN_POOL=" luckpool.org"
ZEN_PORT="3057"



terminal returns

Code:

[screen is terminating]

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.

[msmde]

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

[damNmad]

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

[msmde]

problem solved, thank you!

[z-axis]

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!

[papampi]

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.

[moofone]

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