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

mikespax

full member

Activity: 362

Merit: 102

switching to those settings took me from 13.54/12.98 to 13.8/13.2 on eth/lbry

thanks!

-100, 1500 crashed my computer btw

mikespax

full member

Activity: 362

Merit: 102

asus expedition oc edition 1050ti on your recommended 150, 1100 OC I believe. getting 3.7 Mh/s. dual eth/lbc gets 13 Mh/s on each coin which seems up to par for the card tho at least. I suspect the boat is quickly passing on this coin as somewhere I read difficulty went up like 10x in just the past few days and early miners are dumping coins

mikespax

full member

Activity: 362

Merit: 102

I found SIGT hashrates here: http://cryptoage.com/ru/857-signatum-sign-%D0%BA%D1%80%D0%B8%D0%BF%D1%82%D0%BE%D0%B2%D0%B0%D0%BB%D1%8E%D1%82%D0%B0-%D0%BD%D0%B0-%D0%BD%D0%BE%D0%B2%D0%BE%D0%BC-%D0%B0%D0%BB%D0%B3%D0%BE%D1%80%D0%B8%D1%82%D0%BC%D0%B5-skunkhash-raptor.html

looks like i'm underperforming or maybe have the wrong flavor of 1050ti

ivoldemar

newbie

Activity: 23

Merit: 0

Quote from: ?? on ??

Quote from: ivoldemar on July 26, 2017, 05:25:50 AM

Quote from: ?? on ??

Quote from: ivoldemar on July 25, 2017, 08:31:10 AM

Quote from: ?? on ??

Quote from: ivoldemar on July 24, 2017, 10:46:21 AM

Good afternoon!
===
I'll start with the configuration of my equipment:
GPU - 13 Colorful P106-100 Mining (without video outputs) Edition or 12 + 1 MSI 1060/6 (with video output)
Motherboard H110 Pro BTC
===
Downloaded and installed nvoc 18 version.
Starting with the first run, the system immediately began to issue an error and go into reboot. (Screenshot attached) http://prntscr.com/fzo8uv http://prntscr.com/fzobub

If you quickly close this window with an error and try to start the miner - the system starts and mining.

But, the system does not respond to overclocking. Increasing the memory, setting the speed of the coolers, powerlimit - nothing is applied and the system can only run in the stock.

It did not work out, I tried to connect via integrated video graphics, also through a card with a video output. I suspect this is because of the error that pops up at the very beginning, related to xorg.

One error message also appears on one MSI 1060/6 card.

I tried to run the data on the motherboard H81 Pro BTC + net install Ubuntu + version of the drivers Nvidia 384.47 and everything was fine.

Tell me how to solve this problem?
For earlier I express my gratitude!

I ask for prognosis for the possibly incorrect text, tk. I used an interpreter.

nvOC doesn't support integrated graphics. If you connect a monitor to the integrated graphics you will enter an infinite loop where the system xorg get corrupted then 1bash restores the xorg and reboots.

If you have connected a monitor to integrated graphics previously; after switching to using the primary GPU (the one connected to the 16x slot) you will need to allow the system to reboot once, then on the second boot after changing it should work.

WTF?

http://prntscr.com/g02inr
http://prntscr.com/g02iuz
http://prntscr.com/g02j15

UPDATE:

The system finally started. But, overclocking is applied only to the card in which the monitor is inserted. The remaining P106 cards do not overclock. Screenshots I enclose.
http://prntscr.com/g03joa
http://prntscr.com/g03jt8
http://prntscr.com/g03jyl
It's unclear what else, manual control of the cooler is turned on, set to 100%. But still the system adjusts them automatically.

If you want all the fans set to 100% ensure:

Code:

Maxximus007_AUTO_TEMPERATURE_CONTROL="NO"

Also I changed 1bash to hopefully better support the p106 GPUs in the bux fix version linked at the top of the OP. I don't have any of these, so these changes were based on what other members have reported.

Looking at your screenshots; it looks like there is a problem either with the image on the ssd or with the ssd itself. I would try reimaging and using the bug fix 1bash and files.

BTW this rig looks good; I want to make one of these myself.

Thank you!
Fix helped the system to run smoothly.
But the overclocking and any tuning of the action does not apply!

A couple of screenshots as always attached:
http://prntscr.com/g0ggi9
http://prntscr.com/g0gh50
http://prntscr.com/g0gh8s
http://prntscr.com/g0ghcz

I might have to make a custom xorg.conf for the P106-100. They appear to be using typical pcie addressing; but I am guessing the problem is related to their lack of outputs.

It is hard to know without having some of these P106-100 to test with.

I will add this to the list, and update 1bash to conditionally use that xorg.conf if a P106-100 is detected.

Quote from: darkfortedx on July 26, 2017, 09:52:36 AM

Quote from: ?? on ??

Quote from: darkfortedx on July 24, 2017, 10:58:53 PM

Quote from: ?? on ??

Quote from: darkfortedx on July 23, 2017, 09:48:06 PM

Quote from: Nexillus on July 23, 2017, 09:09:41 PM

Quote from: darkfortedx on July 23, 2017, 05:17:55 PM

my rigs keep restarting after few minutes. Some after 5 mins some after 30. Im not sure why this keeps happening.

im using all 1070's with core 100 / 1050 also i tried 150-200 / 1100-1600. No luck

what is your power limit on them? for 1070s I would push around 120-125 with a moderate/heavy OC. Anything less can cause stability problems.

my power limits are all at 125

in the home directory there is a file named:

Code:

4_restartlog

open it with gedit and tell me what is there

It says utilization is too low. Reviving did not work so restarting machine

Are you sure the client is connecting correctly to the pool? If you disable the watchdog:

Code:

IAmNotAJeep_and_Maxximus007_WATCHDOG="NO"

What happens when you try to mine?

Also what COIN are you mining?

Yea the pool is connecting, If i disable watchdog its still goes. Im trying to mine EXP and SC and switch around to ETH/ETC

Im not sure what you mean by: switch around to ETH/ETC.

Pools that support different Ethash coins usually have different pool connection urls and use different ports.

Quote from: salfter on July 26, 2017, 01:01:59 PM

Quote from: ?? on ??

Quote from: akokkon on July 25, 2017, 02:33:16 AM

I use nvoc for dual mining: DUAL_ETC_PASC

for ETC I can use only etc.nanopool.org or etc.ethermine.org servers, in all other ETC POOL servers I receive the message:

ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...

Please help me to find a solution.

Even i get this with various coins if i change my pool. I'm not sure why?

Different stratum implementations. The Genoil miner knows how to deal with these:

Code:

-SP, --stratum-protocol Choose which stratum protocol to use:
   0: official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)
   1: eth-proxy compatible: dwarfpool, f2pool, nanopool
   2: EthereumStratum/1.0.0: nicehash

The Claymore miner doesn't have this option...though you mention using it with Nanopool and Ethermine, and I've used it briefly with NiceHash, so that covers the types that Genoil knows about. Perhaps it adjusts automatically, but still runs into issues with some pools.

When using Genoil it is as salfter has explained.

Let me send you access to the rig. There are 13 cards, test how much it will fit in

UPDATE: Cool

Bug Fix you did to make P106 run fine, but here in Xorg to add at least coolbits forgot like .... and why then I have only 10 cards there, instead of 13. I tried to edit, all to register. But after the restart, nvoc restored its xorg.

http://Http://prntscr.com/g102c9

I hope that after reading, you will quickly send a fix version.

mikespax

full member

Activity: 362

Merit: 102

based on the instructions here and the new files you've posted, I was also able to get up and running on mining SIGT! sweet! but my single 1050ti is only doing like 3.7 MH/s which is around .17 USD per day which is less profitable than other coins, so perhaps I'm too late to the game already or I've got something setup incorrectly.

https://whattomine.com/coins/191-sigt-skunkhash?utf8=%E2%9C%93&hr=3.7&p=130.0&fee=1&cost=0.14&hcost=0.0&commit=Calculate

dual mining eth / lbc seems the most profitable for now, so I'll stick to that

WarwickNZ

newbie

Activity: 21

Merit: 0

Quote from: ?? on ??

Quote from: WarwickNZ on July 26, 2017, 06:03:17 PM

Quote from: ?? on ??

Quote from: WarwickNZ on July 26, 2017, 03:37:54 PM

Quote from: ?? on ??

Quote from: WarwickNZ on July 26, 2017, 11:01:23 AM

Quote from: ?? on ??

Quote from: car1999 on July 25, 2017, 02:26:08 AM

Hello fullzero,
After a bunch of research and try, I built ccminer 2.2 successfully on nvOC 0018.

The previous build break is due to the openssl version,

Code:

m1@m1-desktop:~$ openssl version
OpenSSL 1.1.1-dev xx XXX xxxx

You used a dev build of openssl in nvOC, ccminer doesn't support it. I download source code of openssl v1.0.2l from openssl.org, build the code, create a few soft links to replace the v1.1.1, it finally works. Not sure if this change breaks other things.

I also built alexis78 fork, https://github.com/alexis78/ccminer, it requires one more step, replace cuda-7.5 to cuda-8.0 in configure.sh.

I'm looking forward these miners in nvOC 0019.

Using linux requires some technical backgrounds, fortunately I was a windows developer Grin

Thanks car1999;

this was helpful.

the problem with tp2.2 on nvOC was a file in the openssl: bn.h. I swapped it with the version it was looking for and this resolved all the related errors.

Also the cuda version does need to be changed in configure.sh as you described, but also for 1000 series GPUs Makefile.am must be altered with the correct Arch flag, 61 for the 1000 series.

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

Hi,

I just tried these out following your instructions and just get "illegal instruction" from the miner, any thoughts?

Thanks

What coin are you mining, when this occurs?

Quote from: salfter on July 26, 2017, 12:39:39 PM

Quote from: ?? on ??

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

The alexis78 ~~miner appears to be OK (at least /home/m1/ASccminer/ccminer --help works), but the~~ and tpruvot miners exit on my rig with an illegal-instruction error. My rig runs on a Celeron G3920 (Skylake core).

(The help output worked for the alexis78 miner, but when it tried mining with it, it fell over.)

What coin are you mining?

Quote from: WarwickNZ on July 26, 2017, 12:54:48 PM

g4560 CPU for me, "illegal instruction" on ASccminer on --benchmark too Sad

I only tested these on a v0018 image (different from the one I compiled on) on the same computer I compiled them on. I didn't think compiling the miner was CPU specific.
I will test on some of my rigs that have similar CPUs to the ones you both have reported using; and recompile the clients if necessary.

Also what GPUs are you using on these rigs?

This is just when attempting to launch miner from terminal, unable to get either of them to mine or attempt to mine anything. I've since tried updating openssl and building myself but can't seem to get it to pick up the new version so still throws the build error...lacking the linux skills. Mining with Gigabyte 1070s on nvOC v18 G4560 (don't know if that's relevant)

I tested and had the same results; so I re-compiled both on a G1840. This should allow for all CPUs; please test the updated download link on the OP and let me know.

Thanks, OK so the new ones didn't work initially until I made the file have executable permissions and now it runs the benchmark but refuses to start stratum due to an "illegal instruction", i'm trying to mine Signatum with these switches:

./ccminer -a skunk -o stratum+tcp://sigt.suprnova.cc:7106 -u USERNAME -p PASSWORD -i 25

Would be awesome if we can get this going for everyones benefit by far most profitable mining coin out there right now

EDIT: So I just noticed that some of the skunk algo files are missing from the TPccminer folder, which were present in the gitclone of "https://github.com/tpruvot/ccminer/tree/linux" I did when trying to get it going. Would doing another build of the latest version sort the issue?

I think you may have the login and worker syntax incorrect, or you have not created the worker you are using before hand at suprnova.

add exe with the cmd:

Code:

chmod 755 '/home/m1/TP_2_2/ccminer'

then add the following to 1bash:

Code:

COIN="SIGT"

Code:

SIGT_WORKER="nvOC"
SIGT_ADDRESS="fullzero22"
SIGT_POOL="stratum+tcp://sigt.suprnova.cc:7106"

Code:

if [ $COIN == "SIGT" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$SIGT_ADDRESS.$SIGT_WORKER"

screen -dmS miner $HCD -a skunk -o $SIGT_POOL -u $ADDR -p x -i 25

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

BITCOIN="theGROUND"

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

or use the line:

Code:

'/home/m1/TP_2_2/ccminer' -a skunk -o stratum+tcp://sigt.suprnova.cc:7106 -u fullzero22.nvOC -p x -i 25

in guake terminal

Works for me:

https://s1.postimg.org/5veu8edmn/SIGT.png

Thanks for the reply, appreciate you looking into it. I think the issue must have been me overlooking that the CPU is actually different on my test rig...not ideal I know! I tried it again with the recompiled version and chmod on another rig with g4560 and it seems to have done the trick!

Have you got an address I can donate # / are mining Signatum yourself?

salfter

hero member

Activity: 651

Merit: 501

My PGP Key: 92C7689C

In the same vein as the NiceHash profit switcher I released a while back, I now have another switcher available that works with MiningPoolHub:

https://gitlab.com/salfter/mph_switch

Out of the box, it will mine all the algorithms supported by the miners bundled with nvOC. Instructions are included to add miners for Sia and CryptoNight. The contents of the config file are a bit different than for the NiceHash switcher, so there's no sharing the two. Integration with 1bash, if desired, would likely be similar at this point to integrating the NiceHash switcher in its current form.

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.

WarwickNZ

newbie

Activity: 21

Merit: 0

Quote from: ?? on ??

Quote from: WarwickNZ on July 26, 2017, 03:37:54 PM

Quote from: ?? on ??

Quote from: WarwickNZ on July 26, 2017, 11:01:23 AM

Quote from: ?? on ??

Quote from: car1999 on July 25, 2017, 02:26:08 AM

Hello fullzero,
After a bunch of research and try, I built ccminer 2.2 successfully on nvOC 0018.

The previous build break is due to the openssl version,

Code:

m1@m1-desktop:~$ openssl version
OpenSSL 1.1.1-dev xx XXX xxxx

You used a dev build of openssl in nvOC, ccminer doesn't support it. I download source code of openssl v1.0.2l from openssl.org, build the code, create a few soft links to replace the v1.1.1, it finally works. Not sure if this change breaks other things.

I also built alexis78 fork, https://github.com/alexis78/ccminer, it requires one more step, replace cuda-7.5 to cuda-8.0 in configure.sh.

I'm looking forward these miners in nvOC 0019.

Using linux requires some technical backgrounds, fortunately I was a windows developer Grin

Thanks car1999;

this was helpful.

the problem with tp2.2 on nvOC was a file in the openssl: bn.h. I swapped it with the version it was looking for and this resolved all the related errors.

Also the cuda version does need to be changed in configure.sh as you described, but also for 1000 series GPUs Makefile.am must be altered with the correct Arch flag, 61 for the 1000 series.

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

Hi,

I just tried these out following your instructions and just get "illegal instruction" from the miner, any thoughts?

Thanks

What coin are you mining, when this occurs?

Quote from: salfter on July 26, 2017, 12:39:39 PM

Quote from: ?? on ??

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

The alexis78 ~~miner appears to be OK (at least /home/m1/ASccminer/ccminer --help works), but the~~ and tpruvot miners exit on my rig with an illegal-instruction error. My rig runs on a Celeron G3920 (Skylake core).

(The help output worked for the alexis78 miner, but when it tried mining with it, it fell over.)

What coin are you mining?

Quote from: WarwickNZ on July 26, 2017, 12:54:48 PM

g4560 CPU for me, "illegal instruction" on ASccminer on --benchmark too Sad

I only tested these on a v0018 image (different from the one I compiled on) on the same computer I compiled them on. I didn't think compiling the miner was CPU specific.
I will test on some of my rigs that have similar CPUs to the ones you both have reported using; and recompile the clients if necessary.

Also what GPUs are you using on these rigs?

This is just when attempting to launch miner from terminal, unable to get either of them to mine or attempt to mine anything. I've since tried updating openssl and building myself but can't seem to get it to pick up the new version so still throws the build error...lacking the linux skills. Mining with Gigabyte 1070s on nvOC v18 G4560 (don't know if that's relevant)

I tested and had the same results; so I re-compiled both on a G1840. This should allow for all CPUs; please test the updated download link on the OP and let me know.

Thanks, OK so the new ones didn't work initially until I made the file have executable permissions and now it runs the benchmark but refuses to start stratum due to an "illegal instruction", i'm trying to mine Signatum with these switches:

./ccminer -a skunk -o stratum+tcp://sigt.suprnova.cc:7106 -u USERNAME -p PASSWORD -i 25

Would be awesome if we can get this going for everyones benefit by far most profitable mining coin out there right now

EDIT: So I just noticed that some of the skunk algo files are missing from the TPccminer folder, which were present in the gitclone of "https://github.com/tpruvot/ccminer/tree/linux" I did when trying to get it going. Would doing another build of the latest version sort the issue?

akokkon

newbie

Activity: 15

Merit: 0

Quote from: ?? on ??

Quote from: akokkon on July 26, 2017, 04:42:05 PM

I use nvoc for dual mining. My selection is DUAL_ETC_PASC, but ...

for ETC I can use only etc.nanopool.org or etc.ethermine.org mining pool servers, in all other ETC mining pool servers I receive the message:

ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...

Please help me to find a solution.

Tell me what pools you are using.

I am trying to use:
ETC_POOL="etc2.91pool.com:8009"
ETC_POOL="stratum-eu3.coin-miners.info:8008"
ETC_POOL="stratum-de.coin-miners.info:8008"
ETC_POOL="etc.pool.zet-tech.eu:8008"

akokkon

newbie

Activity: 15

Merit: 0

I use nvoc for dual mining. My selection is DUAL_ETC_PASC, but ...

for ETC I can use only etc.nanopool.org or etc.ethermine.org mining pool servers, in all other ETC mining pool servers I receive the message:

ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...

Please help me to find a solution.

WarwickNZ

newbie

Activity: 21

Merit: 0

Quote from: ?? on ??

Quote from: WarwickNZ on July 26, 2017, 11:01:23 AM

Quote from: ?? on ??

Quote from: car1999 on July 25, 2017, 02:26:08 AM

Hello fullzero,
After a bunch of research and try, I built ccminer 2.2 successfully on nvOC 0018.

The previous build break is due to the openssl version,

Code:

m1@m1-desktop:~$ openssl version
OpenSSL 1.1.1-dev xx XXX xxxx

You used a dev build of openssl in nvOC, ccminer doesn't support it. I download source code of openssl v1.0.2l from openssl.org, build the code, create a few soft links to replace the v1.1.1, it finally works. Not sure if this change breaks other things.

I also built alexis78 fork, https://github.com/alexis78/ccminer, it requires one more step, replace cuda-7.5 to cuda-8.0 in configure.sh.

I'm looking forward these miners in nvOC 0019.

Using linux requires some technical backgrounds, fortunately I was a windows developer Grin

Thanks car1999;

this was helpful.

the problem with tp2.2 on nvOC was a file in the openssl: bn.h. I swapped it with the version it was looking for and this resolved all the related errors.

Also the cuda version does need to be changed in configure.sh as you described, but also for 1000 series GPUs Makefile.am must be altered with the correct Arch flag, 61 for the 1000 series.

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

Hi,

I just tried these out following your instructions and just get "illegal instruction" from the miner, any thoughts?

Thanks

What coin are you mining, when this occurs?

Quote from: salfter on July 26, 2017, 12:39:39 PM

Quote from: ?? on ??

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

The alexis78 ~~miner appears to be OK (at least /home/m1/ASccminer/ccminer --help works), but the~~ and tpruvot miners exit on my rig with an illegal-instruction error. My rig runs on a Celeron G3920 (Skylake core).

(The help output worked for the alexis78 miner, but when it tried mining with it, it fell over.)

What coin are you mining?

Quote from: WarwickNZ on July 26, 2017, 12:54:48 PM

g4560 CPU for me, "illegal instruction" on ASccminer on --benchmark too Sad

I only tested these on a v0018 image (different from the one I compiled on) on the same computer I compiled them on. I didn't think compiling the miner was CPU specific.
I will test on some of my rigs that have similar CPUs to the ones you both have reported using; and recompile the clients if necessary.

Also what GPUs are you using on these rigs?

This is just when attempting to launch miner from terminal, unable to get either of them to mine or attempt to mine anything. I've since tried updating openssl and building myself but can't seem to get it to pick up the new version so still throws the build error...lacking the linux skills. Mining with Gigabyte 1070s on nvOC v18 G4560 (don't know if that's relevant)

mikespax

full member

Activity: 362

Merit: 102

ty fullzero! suprnova login help worked. I'm now one step closer to that 13x 1080ti mining rig I've always wanted

salfter

hero member

Activity: 651

Merit: 501

My PGP Key: 92C7689C

Quote from: ?? on ??

Quote from: akokkon on July 25, 2017, 02:33:16 AM

I use nvoc for dual mining: DUAL_ETC_PASC

for ETC I can use only etc.nanopool.org or etc.ethermine.org servers, in all other ETC POOL servers I receive the message:

ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...

Please help me to find a solution.

Even i get this with various coins if i change my pool. I'm not sure why?

Different stratum implementations. The Genoil miner knows how to deal with these:

Code:

-SP, --stratum-protocol Choose which stratum protocol to use:
0: official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)
1: eth-proxy compatible: dwarfpool, f2pool, nanopool
2: EthereumStratum/1.0.0: nicehash

The Claymore miner doesn't have this option...though you mention using it with Nanopool and Ethermine, and I've used it briefly with NiceHash, so that covers the types that Genoil knows about. Perhaps it adjusts automatically, but still runs into issues with some pools.

WarwickNZ

newbie

Activity: 21

Merit: 0

g4560 CPU for me, "illegal instruction" on ASccminer on --benchmark too Sad

salfter

hero member

Activity: 651

Merit: 501

My PGP Key: 92C7689C

Quote from: ?? on ??

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

The alexis78 ~~miner appears to be OK (at least /home/m1/ASccminer/ccminer --help works), but the~~ and tpruvot miners exit on my rig with an illegal-instruction error. My rig runs on a Celeron G3920 (Skylake core).

(The help output worked for the alexis78 miner, but when it tried mining with it, it fell over.)

WarwickNZ

newbie

Activity: 21

Merit: 0

Quote from: ?? on ??

Quote from: car1999 on July 25, 2017, 02:26:08 AM

Hello fullzero,
After a bunch of research and try, I built ccminer 2.2 successfully on nvOC 0018.

The previous build break is due to the openssl version,

Code:

m1@m1-desktop:~$ openssl version
OpenSSL 1.1.1-dev  xx XXX xxxx

You used a dev build of openssl in nvOC, ccminer doesn't support it. I download source code of openssl v1.0.2l from openssl.org, build the code, create a few soft links to replace the v1.1.1, it finally works. Not sure if this change breaks other things.

I also built alexis78 fork, https://github.com/alexis78/ccminer, it requires one more step, replace cuda-7.5 to cuda-8.0 in configure.sh.

I'm looking forward these miners in nvOC 0019.

Using linux requires some technical backgrounds, fortunately I was a windows developer Grin

Thanks car1999;

this was helpful.

the problem with tp2.2 on nvOC was a file in the openssl: bn.h. I swapped it with the version it was looking for and this resolved all the related errors.

Also the cuda version does need to be changed in configure.sh as you described, but also for 1000 series GPUs Makefile.am must be altered with the correct Arch flag, 61 for the 1000 series.

I compiled both alexis78 and Tpuvot 2.2 ccminer clients and added at download link to them on the OP. I will include them in v0019 of course.

Hi,

I just tried these out following your instructions and just get "illegal instruction" from the miner, any thoughts?

Thanks

darkfortedx

newbie

Activity: 9

Merit: 0

Quote from: ?? on ??

Quote from: darkfortedx on July 24, 2017, 10:58:53 PM

Quote from: ?? on ??

Quote from: darkfortedx on July 23, 2017, 09:48:06 PM

Quote from: Nexillus on July 23, 2017, 09:09:41 PM

Quote from: darkfortedx on July 23, 2017, 05:17:55 PM

my rigs keep restarting after few minutes. Some after 5 mins some after 30. Im not sure why this keeps happening.

im using all 1070's with core 100 / 1050 also i tried 150-200 / 1100-1600. No luck

what is your power limit on them? for 1070s I would push around 120-125 with a moderate/heavy OC. Anything less can cause stability problems.

my power limits are all at 125

in the home directory there is a file named:

Code:

4_restartlog

open it with gedit and tell me what is there

It says utilization is too low. Reviving did not work so restarting machine

Are you sure the client is connecting correctly to the pool? If you disable the watchdog:

Code:

IAmNotAJeep_and_Maxximus007_WATCHDOG="NO"

What happens when you try to mine?

Also what COIN are you mining?

Yea the pool is connecting, If i disable watchdog its still goes. Im trying to mine EXP and SC and switch around to ETH/ETC

Quote from: akokkon on July 25, 2017, 02:33:16 AM

I use nvoc for dual mining: DUAL_ETC_PASC

for ETC I can use only etc.nanopool.org or etc.ethermine.org servers, in all other ETC POOL servers I receive the message:

ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...

Please help me to find a solution.

Even i get this with various coins if i change my pool. I'm not sure why?

ivoldemar

newbie

Activity: 23

Merit: 0

Quote from: ?? on ??

Quote from: ivoldemar on July 25, 2017, 08:31:10 AM

Quote from: ?? on ??

Quote from: ivoldemar on July 24, 2017, 10:46:21 AM

Good afternoon!
===
I'll start with the configuration of my equipment:
GPU - 13 Colorful P106-100 Mining (without video outputs) Edition or 12 + 1 MSI 1060/6 (with video output)
Motherboard H110 Pro BTC
===
Downloaded and installed nvoc 18 version.
Starting with the first run, the system immediately began to issue an error and go into reboot. (Screenshot attached) http://prntscr.com/fzo8uv http://prntscr.com/fzobub

If you quickly close this window with an error and try to start the miner - the system starts and mining.

But, the system does not respond to overclocking. Increasing the memory, setting the speed of the coolers, powerlimit - nothing is applied and the system can only run in the stock.

It did not work out, I tried to connect via integrated video graphics, also through a card with a video output. I suspect this is because of the error that pops up at the very beginning, related to xorg.

One error message also appears on one MSI 1060/6 card.

I tried to run the data on the motherboard H81 Pro BTC + net install Ubuntu + version of the drivers Nvidia 384.47 and everything was fine.

Tell me how to solve this problem?
For earlier I express my gratitude!

I ask for prognosis for the possibly incorrect text, tk. I used an interpreter.

nvOC doesn't support integrated graphics. If you connect a monitor to the integrated graphics you will enter an infinite loop where the system xorg get corrupted then 1bash restores the xorg and reboots.

If you have connected a monitor to integrated graphics previously; after switching to using the primary GPU (the one connected to the 16x slot) you will need to allow the system to reboot once, then on the second boot after changing it should work.

WTF?

http://prntscr.com/g02inr
http://prntscr.com/g02iuz
http://prntscr.com/g02j15

UPDATE:

The system finally started. But, overclocking is applied only to the card in which the monitor is inserted. The remaining P106 cards do not overclock. Screenshots I enclose.
http://prntscr.com/g03joa
http://prntscr.com/g03jt8
http://prntscr.com/g03jyl
It's unclear what else, manual control of the cooler is turned on, set to 100%. But still the system adjusts them automatically.

If you want all the fans set to 100% ensure:

Code:

Maxximus007_AUTO_TEMPERATURE_CONTROL="NO"

Also I changed 1bash to hopefully better support the p106 GPUs in the bux fix version linked at the top of the OP. I don't have any of these, so these changes were based on what other members have reported.

Looking at your screenshots; it looks like there is a problem either with the image on the ssd or with the ssd itself. I would try reimaging and using the bug fix 1bash and files.

BTW this rig looks good; I want to make one of these myself.

Thank you!
Fix helped the system to run smoothly.
But the overclocking and any tuning of the action does not apply!

A couple of screenshots as always attached:
http://prntscr.com/g0ggi9
http://prntscr.com/g0gh50
http://prntscr.com/g0gh8s
http://prntscr.com/g0ghcz

argonaute

newbie

Activity: 50

Merit: 0

Quote from: Maxximus007 on July 26, 2017, 04:02:52 AM

Quote from: ?? on ??

Quote from: argonaute on July 25, 2017, 10:01:51 AM

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.

Yes, this was the exact same error message that prevented a restart. The new code block resolves this, and will restart rig upon receiving this message.

Cool

Thanks guys

Maxximus007

full member

Activity: 153

Merit: 100

Quote from: ?? on ??

Quote from: argonaute on July 25, 2017, 10:01:51 AM

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.

Yes, this was the exact same error message that prevented a restart. The new code block resolves this, and will restart rig upon receiving this message.

Topic: [ mining os ] nvoc - page 283. (Read 418549 times)