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

[dittie]

TPccminer is failing.

[2017-07-28 14:56:44] Starting on stratum+tcp://sigt.suprnova.cc:7106
[2017-07-28 14:56:44] NVML GPU monitoring enabled.
[2017-07-28 14:56:44] 5 miner threads started, using 'skunk' algorithm.
Illegal instruction


I followed all instructions.
I copied over new files you provided.
Do I need to compile again?

Now I got all AMD rigs on SGminer and SIGT I am stuck on what I thought was the easy one! The Nvidia rig! jeez

I did following and it worked for me:

1) I downloaded "v2 Alexis78 and Tpuvot 2.2 ccminer clients" from page 1 link and extracted as instructions (dirname) says.
2) I followed instructions in this post https://bitcointalk.org/index.php?topic=1854250.msg20411710#msg20411710 and run chmod and added "COIN="SIGT" and rest of the code to end of the 1bash file... "

It worked perfectly, no compile needed.

Yes that works, but there is a more optimized version now giving +30%-40% extra hashrate for SIGT on 1050/60/70/80 cards. It was compiled for ubuntu by Palgin, however its not running in nvOC : https://bitcointalk.org/index.php?topic=2030529.msg20437974#msg20437974

[1714199181]

1714199181

[1714199181]

1714199181

[1714199181]

1714199181

[1714199181]

1714199181

[OverEasy]

Didn't work for me at all. Hardly matters now. Too many miners and sellers and no buyers. SIGT is circling the drain and about to be flushed...Moving on to another coin

[gig410]

question for fullzero: Is there a reason why you do not failover mining pool addresses in 1bash? I was watching my rig (for a completely separate issue which I might require help later) it lost connection to the mining pool I use (nanopool west) then the mining process tried restarted twice, then the whole rig just shut down. I tested my internet connection while the rig was restarting and trying to connect to the pool and my connection was ok. Wouldn't it be better to connect to a failover pool address and if it connects to the failover, try to re-establish with the original pool an hour later? or something along that line, perhaps incorporated into the watchdog? It's cool that it shut itself down and not waste power, but I would prefer that the rig try to connect to another pool if it can.

[fullzero]

On the road; I will respond to everyone fully when I get back to a desktop, and reliable internet in a few days.

[car1999]

TPccminer is failing.

[2017-07-28 14:56:44] Starting on stratum+tcp://sigt.suprnova.cc:7106
[2017-07-28 14:56:44] NVML GPU monitoring enabled.
[2017-07-28 14:56:44] 5 miner threads started, using 'skunk' algorithm.
Illegal instruction


I followed all instructions.
I copied over new files you provided.
Do I need to compile again?

Now I got all AMD rigs on SGminer and SIGT I am stuck on what I thought was the easy one! The Nvidia rig! jeez

I did following and it worked for me:

1) I downloaded "v2 Alexis78 and Tpuvot 2.2 ccminer clients" from page 1 link and extracted as instructions (dirname) says.
2) I followed instructions in this post https://bitcointalk.org/index.php?topic=1854250.msg20411710#msg20411710 and run chmod and added "COIN="SIGT" and rest of the code to end of the 1bash file... "

It worked perfectly, no compile needed.

Yes that works, but there is a more optimized version now giving +30%-40% extra hashrate for SIGT on 1050/60/70/80 cards. It was compiled for ubuntu by Palgin, however its not running in nvOC : https://bitcointalk.org/index.php?topic=2030529.msg20437974#msg20437974

yes, it doesn't work  on nvOC, I tried both G3900 and G4560 CPU,. so  i switch a rig to Windows to mine SIGT.)

[Zeix]

question for fullzero: Is there a reason why you do not failover mining pool addresses in 1bash? I was watching my rig (for a completely separate issue which I might require help later) it lost connection to the mining pool I use (nanopool west) then the mining process tried restarted twice, then the whole rig just shut down. I tested my internet connection while the rig was restarting and trying to connect to the pool and my connection was ok. Wouldn't it be better to connect to a failover pool address and if it connects to the failover, try to re-establish with the original pool an hour later? or something along that line, perhaps incorporated into the watchdog? It's cool that it shut itself down and not waste power, but I would prefer that the rig try to connect to another pool if it can.

I haven't tested it, but for Claymore, can't you just put all the failover addresses into /home/m1/eth/9_7/epools.txt like you do on Windows?

[damNmad]

Hello guys,

Any of you mining Pascal Lite? If so can you please share your PASL coin code part from oneBash (would prefer DUAL though), would like to create an account with PASL.

Tried with accounts.pascallite.com, but don't have any PASL on Cryptopia to buy (it just costs 0.05 PASL though), so want to try pasl.fairpool.xyz as they said they will give an account if I mine with my public wallet key for 12.25 PASL.

I've tried to edit and add on my oneBash, it does nothing but crashing/hanging my RIG.

Thanks in advance.

&&

Would also like to share my stable OC settings with ASUS DUAL 1060 6GB.

cc : -100; mc:  1100; pl  :  90W

giving me 170MH for ETHASH and 200MH for LBC (dcri-40)

Hope it help some new users trying for stable OC, also happy to get some advice if I can increase the yield.

Thanks and good luck with our mining.

Hail fullZero for creating and expanding this OS with amazing support.

Long live CRYPTO & fullZero...

I have tried adding the following code to my one bash as per the instructions on replies, but still my rig is crashing when I tried to mine PASL. Though I want DUAL_ETC_PASL, I've tried just PASL using this code.

Code:

COIN="PASL"

Code:

PASL_WORKER="$IP_AS_WORKER"
PASL_ADDRESS="xxxxxxxxxxxxxx"
PASL_POOL="stratum+tcp://mine.pasl.fairpool.xyz:4009"

Code:

if [ $COIN == "PASL" ]
then
HCD='/home/m1/pasc/sgminer'
ADDR="$PASL_ADDRESS..$PASL_WORKER"

screen -dmS miner $HCD -k pascal -o $PASL_POOL -u $ADDR -p x -p x -I 21 -w 64 -g2

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

BITCOIN="theGROUND"

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

SGMINER starts but RIG hangs, can some one please help me with this...

[mikespax]

As for NiceHash vs. MiningPoolHub, that's something I'm figuring out for myself right now. MPH takes 0.9% on all coins mined and imposes a BTC0.0003 miner fee on withdrawals, so by raising the auto-withdraw threshold to BTC0.03 (NiceHash is fixed at BTC0.01), the miner fee ends up being only 1% of the total.  As for which is more productive (read: produces more BTC per week), that's something I hope to get a handle on over the next couple or so weeks.

I eagerly await your findings here. Always want to make sure I'm on top of the most profitable way to use my rig.

[Nexillus]

As for NiceHash vs. MiningPoolHub, that's something I'm figuring out for myself right now. MPH takes 0.9% on all coins mined and imposes a BTC0.0003 miner fee on withdrawals, so by raising the auto-withdraw threshold to BTC0.03 (NiceHash is fixed at BTC0.01), the miner fee ends up being only 1% of the total.  As for which is more productive (read: produces more BTC per week), that's something I hope to get a handle on over the next couple or so weeks.

I eagerly await your findings here. Always want to make sure I'm on top of the most profitable way to use my rig.

Same here, be some very good information

[darkomega69]

Hi Fullzero

I want to share with you a GPU failed that the watchdog is not able to detect

wdog screen:

GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:09:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Tue Jul 25 16:57:01 CEST 2017 - All good! Will check again in 60 seconds


GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:09:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Tue Jul 25 16:58:01 CEST 2017 - All good! Will check again in 60 seconds


the miner show/detect only 6 GPU over 7

nvidia-smi doesn't work
$ nvidia-smi
Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost.  Reboot the system to recover this GPU

temp screen:
Provided power limit 75.00 W is not a valid power limit which should be between 115.00 W and 291.00 W for GPU 00000000:0A:00.0
Terminating early due to previous errors.
Tue Jul 25 17:01:07 CEST 2017 - All good, will check again soon

GPU 0, Target temp: 61, Current: 60, Diff: 1, Fan: 75, Power: 123.46

GPU 1, Target temp: 61, Current: 60, Diff: 1, Fan: 63, Power: 124.62

GPU 2, Target temp: 61, Current: 59, Diff: 2, Fan: 77, Power: 119.23

GPU 3, Target temp: 61, Current: 60, Diff: 1, Fan: 68, Power: 120.72

GPU 4, Target temp: 61, Current: 59, Diff: 2, Fan: 57, Power: 124.26

GPU 5, Target temp: 61, Current: Unable, Diff: 61, Fan: to, Power: determine

/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 125: [: Unable: integer expression expected
/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 158: [: the: integer expression expected
/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 171: [: to: integer expression expected
GPU 6, Target temp: 61, Current: 55, Diff: 6, Fan: 50, Power: 126.76

Tue Jul 25 17:01:37 CEST 2017 - Restoring Power limit for gpu:6. Old limit: 125 New limit: 75 Fan speed: 50

Provided power limit 75.00 W is not a valid power limit which should be between 115.00 W and 291.00 W for GPU 00000000:0A:00.0
Terminating early due to previous errors.
Tue Jul 25 17:01:37 CEST 2017 - All good, will check again soon

I believe this is the exact problem that Maxximus007 recently made a new code block to resolve.

Fullzero,

I'm getting this error as well, and looks like watchdog is not rebooting the system.
I believe I have the latest bash files.
are Maxximus007's changes to resolve this issue in the current bash files?
Thank you.



GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:01:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:01:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Sat Jul 29 21:07:09 PDT 2017 - All good! Will check again in 60 seconds

[dbolivar]

@salfter :

I'd like to suggest an idea to your switcher: when the most profitable algorithm is Ethash, give the option to dual-mine automatically with the second most profitable algorithm if it's able to do so.

A rough draft:

* Give the user the choice to dual-mine or not in conf.json

* List the safe algorithms to dual-mine with Ethash (Decred, Lbry, Sia, Pascal, ...?)

* List NiceHash's most profitable algorithms after Ethash, if it's the first one; for each one, check if it's in the safe list, and select the first match (most profitable AND in the safe list)

* Profit

Of course I'm oversimplifying, as the switching itself will have to consider a higher power limit, more complex profit calculation and perform a "switch inside a switch" (Ethash fixed + switching second algo). But I think we can get a few more bucks this way, at least from my short mining experience it's usually profitable to dual-mine when Ethash is the most profitable.

What do you think?

[damNmad]

Hello guys,

Any of you mining Pascal Lite? If so can you please share your PASL coin code part from oneBash (would prefer DUAL though), would like to create an account with PASL.

Tried with accounts.pascallite.com, but don't have any PASL on Cryptopia to buy (it just costs 0.05 PASL though), so want to try pasl.fairpool.xyz as they said they will give an account if I mine with my public wallet key for 12.25 PASL.

I've tried to edit and add on my oneBash, it does nothing but crashing/hanging my RIG.

Thanks in advance.

&&

Would also like to share my stable OC settings with ASUS DUAL 1060 6GB.

cc : -100; mc:  1100; pl  :  90W

giving me 170MH for ETHASH and 200MH for LBC (dcri-40)

Hope it help some new users trying for stable OC, also happy to get some advice if I can increase the yield.

Thanks and good luck with our mining.

Hail fullZero for creating and expanding this OS with amazing support.

Long live CRYPTO & fullZero...

I have tried adding the following code to my one bash as per the instructions on replies, but still my rig is crashing when I tried to mine PASL. Though I want DUAL_ETC_PASL, I've tried just PASL using this code.

Code:

COIN="PASL"

Code:

PASL_WORKER="$IP_AS_WORKER"
PASL_ADDRESS="xxxxxxxxxxxxxx"
PASL_POOL="stratum+tcp://mine.pasl.fairpool.xyz:4009"

Code:

if [ $COIN == "PASL" ]
then
HCD='/home/m1/pasc/sgminer'
ADDR="$PASL_ADDRESS..$PASL_WORKER"

screen -dmS miner $HCD -k pascal -o $PASL_POOL -u $ADDR -p x -p x -I 21 -w 64 -g2

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

BITCOIN="theGROUND"

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

SGMINER starts but RIG hangs, can some one please help me with this...

I have figured it out, don't need to add additional code, just use the current PASC code as is, change the details of pool and account of PASC to PASL details.

[darklow]

TPccminer is failing.

[2017-07-28 14:56:44] Starting on stratum+tcp://sigt.suprnova.cc:7106
[2017-07-28 14:56:44] NVML GPU monitoring enabled.
[2017-07-28 14:56:44] 5 miner threads started, using 'skunk' algorithm.
Illegal instruction


I followed all instructions.
I copied over new files you provided.
Do I need to compile again?

Now I got all AMD rigs on SGminer and SIGT I am stuck on what I thought was the easy one! The Nvidia rig! jeez

I did following and it worked for me:

1) I downloaded "v2 Alexis78 and Tpuvot 2.2 ccminer clients" from page 1 link and extracted as instructions (dirname) says.
2) I followed instructions in this post https://bitcointalk.org/index.php?topic=1854250.msg20411710#msg20411710 and run chmod and added "COIN="SIGT" and rest of the code to end of the 1bash file... "

It worked perfectly, no compile needed.

Yes that works, but there is a more optimized version now giving +30%-40% extra hashrate for SIGT on 1050/60/70/80 cards. It was compiled for ubuntu by Palgin, however its not running in nvOC : https://bitcointalk.org/index.php?topic=2030529.msg20437974#msg20437974

yes, it doesn't work  on nvOC, I tried both G3900 and G4560 CPU,. so  i switch a rig to Windows to mine SIGT.)

I contacted @palgin - the author and the problem was that previous binary was compiled for 32-bit only. He just fixed the problem and great news - it finally works now! Increase is very very good, for me from 19 MH/s to 26 MH/s per 1070 card!
Download link is here: https://bitcointalk.org/index.php?topic=2030529.msg20489060#msg20489060

[Alquemista]

Hi Fullzero

I want to share with you a GPU failed that the watchdog is not able to detect

wdog screen:

GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:09:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Tue Jul 25 16:57:01 CEST 2017 - All good! Will check again in 60 seconds


GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:09:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Tue Jul 25 16:58:01 CEST 2017 - All good! Will check again in 60 seconds


the miner show/detect only 6 GPU over 7

nvidia-smi doesn't work
$ nvidia-smi
Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost.  Reboot the system to recover this GPU

temp screen:
Provided power limit 75.00 W is not a valid power limit which should be between 115.00 W and 291.00 W for GPU 00000000:0A:00.0
Terminating early due to previous errors.
Tue Jul 25 17:01:07 CEST 2017 - All good, will check again soon

GPU 0, Target temp: 61, Current: 60, Diff: 1, Fan: 75, Power: 123.46

GPU 1, Target temp: 61, Current: 60, Diff: 1, Fan: 63, Power: 124.62

GPU 2, Target temp: 61, Current: 59, Diff: 2, Fan: 77, Power: 119.23

GPU 3, Target temp: 61, Current: 60, Diff: 1, Fan: 68, Power: 120.72

GPU 4, Target temp: 61, Current: 59, Diff: 2, Fan: 57, Power: 124.26

GPU 5, Target temp: 61, Current: Unable, Diff: 61, Fan: to, Power: determine

/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 125: [: Unable: integer expression expected
/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 158: [: the: integer expression expected
/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 171: [: to: integer expression expected
GPU 6, Target temp: 61, Current: 55, Diff: 6, Fan: 50, Power: 126.76

Tue Jul 25 17:01:37 CEST 2017 - Restoring Power limit for gpu:6. Old limit: 125 New limit: 75 Fan speed: 50

Provided power limit 75.00 W is not a valid power limit which should be between 115.00 W and 291.00 W for GPU 00000000:0A:00.0
Terminating early due to previous errors.
Tue Jul 25 17:01:37 CEST 2017 - All good, will check again soon

I believe this is the exact problem that Maxximus007 recently made a new code block to resolve.

Fullzero,

I'm getting this error as well, and looks like watchdog is not rebooting the system.
I believe I have the latest bash files.
are Maxximus007's changes to resolve this issue in the current bash files?
Thank you.



GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:01:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:01:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Sat Jul 29 21:07:09 PDT 2017 - All good! Will check again in 60 seconds

I'm experiencing same issues sometimes, that's how I fixed, I made a python script to check for GPUs failure and reboots if it's not mining with all the GPUs,

nano deepredchecker.py
Paste the following:

#!/bin/python

import os

card_status = os.popen("nvidia-smi").read()

if "reboot" in card_status:
    os.popen("sudo shutdown -r now")
else:
    exit()


Type: chmod a+x deepredchecker.py
Type: crontab -e
Paste: */5 * * * * python /home/m1/deepredchecker.py > /dev/null
 At the bottom and save crontab.

Now, every 5 minutes (you can adjust it) it will check if all of your cards are up and running, in case of problems it will reboot your rig, so far this is making my life easier. Hope it helps you

[uat88]

Any of you all getting the error when downloading from Google drive for v0018?

The error I got is 'We're sorry. You can't access this item because it is in violation of our Terms of Service'

[Nexillus]

@salfter :

I'd like to suggest an idea to your switcher: when the most profitable algorithm is Ethash, give the option to dual-mine automatically with the second most profitable algorithm if it's able to do so.

A rough draft:

* Give the user the choice to dual-mine or not in conf.json

* List the safe algorithms to dual-mine with Ethash (Decred, Lbry, Sia, Pascal, ...?)

* List NiceHash's most profitable algorithms after Ethash, if it's the first one; for each one, check if it's in the safe list, and select the first match (most profitable AND in the safe list)

* Profit

Of course I'm oversimplifying, as the switching itself will have to consider a higher power limit, more complex profit calculation and perform a "switch inside a switch" (Ethash fixed + switching second algo). But I think we can get a few more bucks this way, at least from my short mining experience it's usually profitable to dual-mine when Ethash is the most profitable.

What do you think?

Biggest issue I see with this is power. To dual mine the rigs need considerably more power then solo mining. Example is 1070 rig with solo mine can do same OC with PL around 110-115, while on dual mining needs 120-125. Some people may have stability problems with this type of switch if they are not aware of the power needed to support it.

[osnwt]

Sorry if this was already fixed or is a duplicate report. Didn't read the thread for a long time.

I found that my nvOC system boots too long (around 2 minutes). The cause of that is a swap partition in /etc/fstab that does not exist on USB drive (was /dev/sda5 at install time). After commenting it out a 120 seconds swap disk mount wait time has gone.

[argonaute]

Hi Fullzero

I want to share with you a GPU failed that the watchdog is not able to detect

wdog screen:

GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:09:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Tue Jul 25 16:57:01 CEST 2017 - All good! Will check again in 60 seconds


GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:09:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Tue Jul 25 16:58:01 CEST 2017 - All good! Will check again in 60 seconds


the miner show/detect only 6 GPU over 7

nvidia-smi doesn't work
$ nvidia-smi
Unable to determine the device handle for GPU 0000:09:00.0: GPU is lost.  Reboot the system to recover this GPU

temp screen:
Provided power limit 75.00 W is not a valid power limit which should be between 115.00 W and 291.00 W for GPU 00000000:0A:00.0
Terminating early due to previous errors.
Tue Jul 25 17:01:07 CEST 2017 - All good, will check again soon

GPU 0, Target temp: 61, Current: 60, Diff: 1, Fan: 75, Power: 123.46

GPU 1, Target temp: 61, Current: 60, Diff: 1, Fan: 63, Power: 124.62

GPU 2, Target temp: 61, Current: 59, Diff: 2, Fan: 77, Power: 119.23

GPU 3, Target temp: 61, Current: 60, Diff: 1, Fan: 68, Power: 120.72

GPU 4, Target temp: 61, Current: 59, Diff: 2, Fan: 57, Power: 124.26

GPU 5, Target temp: 61, Current: Unable, Diff: 61, Fan: to, Power: determine

/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 125: [: Unable: integer expression expected
/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 158: [: the: integer expression expected
/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL: line 171: [: to: integer expression expected
GPU 6, Target temp: 61, Current: 55, Diff: 6, Fan: 50, Power: 126.76

Tue Jul 25 17:01:37 CEST 2017 - Restoring Power limit for gpu:6. Old limit: 125 New limit: 75 Fan speed: 50

Provided power limit 75.00 W is not a valid power limit which should be between 115.00 W and 291.00 W for GPU 00000000:0A:00.0
Terminating early due to previous errors.
Tue Jul 25 17:01:37 CEST 2017 - All good, will check again soon

I believe this is the exact problem that Maxximus007 recently made a new code block to resolve.

Fullzero,

I'm getting this error as well, and looks like watchdog is not rebooting the system.
I believe I have the latest bash files.
are Maxximus007's changes to resolve this issue in the current bash files?
Thank you.



GPU UTILIZATION:  Unable to determine the device handle for GPU 0000:01:00.0: GPU is lost. Reboot the system to recover this GPU

/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Unable: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: determine: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: device: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: handle: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: for: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: 0000:01:00.0:: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: is: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: lost.: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: Reboot: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: the: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: system: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: to: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: recover: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: this: integer expression expected
/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG: line 44: [: GPU: integer expression expected
Sat Jul 29 21:07:09 PDT 2017 - All good! Will check again in 60 seconds

I'm experiencing same issues sometimes, that's how I fixed, I made a python script to check for GPUs failure and reboots if it's not mining with all the GPUs,

nano deepredchecker.py
Paste the following:

#!/bin/python

import os

card_status = os.popen("nvidia-smi").read()

if "reboot" in card_status:
    os.popen("sudo shutdown -r now")
else:
    exit()


Type: chmod a+x deepredchecker.py
Type: crontab -e
Paste: */5 * * * * python /home/m1/deepredchecker.py > /dev/null
 At the bottom and save crontab.

Now, every 5 minutes (you can adjust it) it will check if all of your cards are up and running, in case of problems it will reboot your rig, so far this is making my life easier. Hope it helps you

I like that !!

thanks for the share

[Avarets]

New driver has been released.
https://devtalk.nvidia.com/default/topic/1019588/unix-graphics-announcements-and-news/linux-solaris-and-freebsd-driver-384-59-long-lived-branch-release-/

[Chili.Dog]

@ fullzero, would like to download v0018, but very difficult Google says violation of TOS.
Mega downloads 5 gigs every 6hrs. or 5.00 euros.

Chili