Author

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

newbie
Activity: 46
Merit: 0
September 03, 2017, 12:46:30 PM
There is one issue I ran across: no Cryptonight miner.  

And what about xmr-stak-nvidia? It's for XMR only?

Unpack to ~m1. It'll unpack to a Git repo into which you can pull updates (I last updated it just a few days ago) that has already been configured and built.  I might've built it for Pascal (GeForce 10-series) GPUs only; I don't recall for sure if I did, so if you're using older GPUs and it doesn't work for you, you might need to rebuild it.

There was also an upstream change in this miner that requires a change in 3main.  The "-a cryptonight" option is no longer accepted, so load 3main into the editor of your choice, search for "KTccminer-cryptonight" (it's near the beginning of the heredoc that gets written to mph_conf.json), and delete "-a cryptonight" from that line.

In 3main we have now:

if [ $COIN == "XMR" ]
then
HCD='/home/m1/xmr/stakGPU/bin/xmr-stak-nvidia'

How to change 1bash and 3main in order to have a choice between ktccminer and xmr-stak-nvidia when mining XMR?
newbie
Activity: 28
Merit: 0
September 03, 2017, 12:13:36 PM
I edited this on my previous reply while you were replying, not sure if you noticed:

Oh, one more thing... On the Asrock 13 gpu board, the PCIe slots on the board are so close, the small riser boards that plug to the motherboard might be touching each other and create short circuits. What I did is: I cut the excessive lenght of the soldered pins of the USB connector on the back side of that small board; used heat-shrink tube (1.5 inch wide) and wrapped the small boards where they could touch eachother, making sure the pins that plug to the PCIe slots are not covered. I would suggest that everyone usung the Asrock 13 GPU board do this to prevent problems... the heat-shrink tube is about 5-6 bucks and it's quete long, I don't remember exactly but it was at least 4 feet long. I got it from Sayal in Toronto but I am sure you can find one in electronic shops or even Home Depot.

I had put heat resistant electrical tape on the back side of each of the small riser parts that plug into those slots (not initially, but as I have gone through this process). Would that have a similar impact to what you describe?
full member
Activity: 200
Merit: 101
September 03, 2017, 11:55:07 AM
I edited this on my previous reply while you were replying, not sure if you noticed:

Oh, one more thing... On the Asrock 13 gpu board, the PCIe slots on the board are so close, the small riser boards that plug to the motherboard might be touching each other and create short circuits. What I did is: I cut the excessive lenght of the soldered pins of the USB connector on the back side of that small board; used heat-shrink tube (1.5 inch wide) and wrapped the small boards where they could touch eachother, making sure the pins that plug to the PCIe slots are not covered. I would suggest that everyone usung the Asrock 13 GPU board do this to prevent problems... the heat-shrink tube is about 5-6 bucks and it's quete long, I don't remember exactly but it was at least 4 feet long. I got it from Sayal in Toronto but I am sure you can find one in electronic shops or even Home Depot.
newbie
Activity: 28
Merit: 0
September 03, 2017, 11:48:05 AM

I just placed an order for some g4600's. I will see how that works - the rig that had been crashing every couple hours crashed after 24 hours after I turned off teamviewer - hopefully this puts me over the top.

As for power, both are built the same way. Each is running on 2 750w EVGA G3 power supplies. Each SATA/molex power connector is running no more than 2 GPU risers. The molex connectors (and single SATA) hooked to the board each share with the riser for a single GPU (this means 13 GPU's, 2 motherboard molex, and 1 motherboard SATA to connect. The PSU's each have 3 SATA and 1 Perif (molex) connector, hence my using two connections per cable). I did have a 550w PSU in the mix (as a third) to see if that would change things, but it did not.

The only other discernable different is that not all GPU's are the same brand/make (but all are 1060 6GB), and the risers are not all identical (though I have switched them out in troubleshooting).

Good, G4600 is 2 core, 4 threads CPU. That will definetely help, much better than Celerons you have.

As for the mixed GPU's, try to put as many of the same brand/model in the same rig. Then you will have to manualy set overclocking for each GPU. Don't use the global OC for all. Try with the lowest stable value for all (I believe it was about 600 memory for you), then increase +50 memory on one brand/model and see if it's stable, then try +50 on different model and see if it's stable, then repeat until you get max for all models. It will take a while to fine tune it, that's the downside of mixed cards. Good luck and keep us posted.

Yesterday I swapped both Celeron G3930's for G4600's.

Overnight, the stable rig remained stable, the unstable rig crashed again.

Short of replacing all my risers again (and I am still open to specifics on what version to get) or RMA'ing the motherboard, is there anything else I might be missing?

JudoFlash, have you tried my previous suggestion of manualy overclocking each card, not using the global settings since you have a mix of different cards?

If that doesn't work, disconnect one card completely, then run the rig, see if it's stable. If it still crashes, connect the disconnected card back and disconnect another card completely... repeat until you pinpoint the card that misbehave. Once you pinpointed the troublemaker, troubleshoot further: replace the riser, replace the adapter cable to the riser (depends on your risers, PCIe to SATA or Molex to SATA cable), plug the riser power to another connector of the SATA cable coming from the power supply, lastly, significantly lower the overclock values for that card. If previous steps didn't help, you have a bad GPU, replace it.

I've had problems with, bad riser, bad power adapter cable, bad SATA connector and bad GPU before. It's not easy to troubleshoot when the problem is intermittent but atleast with the above suggestion (disconnecting one card at a time completely) you can narrow the problematic section then troubleshoot further.

BTW, I am using version 006-c risers with PCIe to SATA power adapter cables.

Thank you. Yes I have tried the manual tuning. Right now I have everything running at stock as sort of a "last ditch" effort on making this configuration work (or at least narrowing it down). As you said, the challenge is that it does not crash right away (sometimes it takes 24 hours or so), so with so many variables, it takes a long time to pinpoint. I ordered some new risers (I would need them anyway as I plan to set up another rig or two), so I will do some further testing with those once I have them.

I appreciate everyone's input. Yes, I know I could just stand up another board and not have so much riding on this one, but I feel longer term, finding the issue will help my overall success. Plus, folks on this forum seem to be making things work with this board and similar setups.

Also, I'm stubborn.
full member
Activity: 200
Merit: 101
September 03, 2017, 11:22:48 AM

I just placed an order for some g4600's. I will see how that works - the rig that had been crashing every couple hours crashed after 24 hours after I turned off teamviewer - hopefully this puts me over the top.

As for power, both are built the same way. Each is running on 2 750w EVGA G3 power supplies. Each SATA/molex power connector is running no more than 2 GPU risers. The molex connectors (and single SATA) hooked to the board each share with the riser for a single GPU (this means 13 GPU's, 2 motherboard molex, and 1 motherboard SATA to connect. The PSU's each have 3 SATA and 1 Perif (molex) connector, hence my using two connections per cable). I did have a 550w PSU in the mix (as a third) to see if that would change things, but it did not.

The only other discernable different is that not all GPU's are the same brand/make (but all are 1060 6GB), and the risers are not all identical (though I have switched them out in troubleshooting).

Good, G4600 is 2 core, 4 threads CPU. That will definetely help, much better than Celerons you have.

As for the mixed GPU's, try to put as many of the same brand/model in the same rig. Then you will have to manualy set overclocking for each GPU. Don't use the global OC for all. Try with the lowest stable value for all (I believe it was about 600 memory for you), then increase +50 memory on one brand/model and see if it's stable, then try +50 on different model and see if it's stable, then repeat until you get max for all models. It will take a while to fine tune it, that's the downside of mixed cards. Good luck and keep us posted.

Yesterday I swapped both Celeron G3930's for G4600's.

Overnight, the stable rig remained stable, the unstable rig crashed again.

Short of replacing all my risers again (and I am still open to specifics on what version to get) or RMA'ing the motherboard, is there anything else I might be missing?

JudoFlash, have you tried my previous suggestion of manualy overclocking each card, not using the global settings since you have a mix of different cards?

If that doesn't work, disconnect one card completely, then run the rig, see if it's stable. If it still crashes, connect the disconnected card back and disconnect another card completely... repeat until you pinpoint the card that misbehave. Once you pinpointed the troublemaker, troubleshoot further: replace the riser, replace the adapter cable to the riser (depends on your risers, PCIe to SATA or Molex to SATA cable), plug the riser power to another connector of the SATA cable coming from the power supply, lastly, significantly lower the overclock values for that card. If previous steps didn't help, you have a bad GPU, replace it.

I've had problems with, bad riser, bad power adapter cable, bad SATA connector and bad GPU before. It's not easy to troubleshoot when the problem is intermittent but atleast with the above suggestion (disconnecting one card at a time completely) you can narrow the problematic section then troubleshoot further.

BTW, I am using version 006-c risers with PCIe to SATA power adapter cables.

Oh, one more thing... On the Asrock 13 gpu board, the PCIe slots on the board are so close, the small riser boards that plug to the motherboard might be touching each other and create short circuits. What I did is: I cut the excessive lenght of the soldered pins of the USB connector on the back side of that small board; used heat-shrink tube (1.5 inch wide) and wrapped the small boards where they could touch eachother, making sure the pins that plug to the PCIe slots are not covered. I would suggest that everyone usung the Asrock 13 GPU board do this to prevent problems... the heat-shrink tube is about 5-6 bucks and it's quete long, I don't remember exactly but it was at least 4 feet long. I got it from Sayal in Toronto but I am sure you can find one in electronic shops or even Home Depot.
full member
Activity: 200
Merit: 101
September 03, 2017, 11:00:05 AM
Hi guys,

I've a problem with booting nvOS - never booted. I tried several USB sticks (16G and 32G), always successfully created (with Etcher, I've Mac). I tried on two computers.

Testing PC has ASUS ROG motherboard with 2x 1060.
RIG has ASRock H110 PRO BTC+ with 7x 1080Ti.

I tried connect DVI cable on primary GPU. On rig, I had a no signal, so I tried all GPUs - without signal. If I used motherboard DVI, so I got signal, but after choosing Ubuntu in boot menu, so it's freezy. After 30 minutes nothing happens.

Similar situation on second computer, I got monitor signal on both GPUs and motherboard, but always Ubuntu freezy and cursor blinking over 1 hour...

Can you help me, please? Thanks for any advice.


Disable on-board video (motherboard video) in the Bios. Connect monitor to GPU that is in the first x16 PCIe slot (the first long slot closest to the CPU).

Something is very wrong if boot takes longer than 3 minutes.

Did you verify the sha256 sum of the zip file?

to leenoox: thanks, now it works :-)

to fullzero: yes, verified.

BTW, I try use USB 2.0 sticks, so I bought USB 3.0 (Patriot Supersonic Rage XT 32GB) and repeat steps again. Now nvOS boot up in 30 seconds...

Thanks both :-)

I'm glad it worked. Anyone else having similar issues, make sure on-board video is disabled in the bios... it creates problems with the X-server
full member
Activity: 378
Merit: 104
nvOC forever
September 03, 2017, 10:56:40 AM
Please show me where in the settings of the miner specify the name of the miner and the password for the suprnova pool for the coin zen? I do not see the password field in the 1bash file

There is no need of worker password as suprnova doesn't care about password, (but better set your worker password as 'x' on suprnova pool), it is only asking for worker password not user account.

Add Worker Name : This is the name you add on suprnova portal (under worker; password must be 'x')
Code:
XXXX_WORKER="miner"

This is your suprnova login name :
Code:
XXXX_ADDRESS="loginName"

suprnova pool address :
Code:
XXXX_POOL="XXXX.suprnova.cc:0000"

Hope it helps...
newbie
Activity: 31
Merit: 0
September 03, 2017, 10:10:15 AM
Please show me where in the settings of the miner specify the name of the miner and the password for the suprnova pool for the coin zen? I do not see the password field in the 1bash file
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
September 03, 2017, 09:47:27 AM

I just placed an order for some g4600's. I will see how that works - the rig that had been crashing every couple hours crashed after 24 hours after I turned off teamviewer - hopefully this puts me over the top.

As for power, both are built the same way. Each is running on 2 750w EVGA G3 power supplies. Each SATA/molex power connector is running no more than 2 GPU risers. The molex connectors (and single SATA) hooked to the board each share with the riser for a single GPU (this means 13 GPU's, 2 motherboard molex, and 1 motherboard SATA to connect. The PSU's each have 3 SATA and 1 Perif (molex) connector, hence my using two connections per cable). I did have a 550w PSU in the mix (as a third) to see if that would change things, but it did not.

The only other discernable different is that not all GPU's are the same brand/make (but all are 1060 6GB), and the risers are not all identical (though I have switched them out in troubleshooting).

Good, G4600 is 2 core, 4 threads CPU. That will definetely help, much better than Celerons you have.

As for the mixed GPU's, try to put as many of the same brand/model in the same rig. Then you will have to manualy set overclocking for each GPU. Don't use the global OC for all. Try with the lowest stable value for all (I believe it was about 600 memory for you), then increase +50 memory on one brand/model and see if it's stable, then try +50 on different model and see if it's stable, then repeat until you get max for all models. It will take a while to fine tune it, that's the downside of mixed cards. Good luck and keep us posted.

Yesterday I swapped both Celeron G3930's for G4600's.

Overnight, the stable rig remained stable, the unstable rig crashed again.

Short of replacing all my risers again (and I am still open to specifics on what version to get) or RMA'ing the motherboard, is there anything else I might be missing?

So if I said you are being stupid cheap would you be insulted?

How about penny wise pound foolish?

Buy a third mobo that will use some cards from the rig that crashes.

Run a 13 card a 8 card and a 5 card.  Problem should be solved.

Or don't buy a new mobo take the troubled mobo and use say 7 identical cards on it with gentle clocks and lower tdp say 70.

If the bad mobo works add 1 card if it works add 1 card.

Frankly more mobos makes more sense in your case.
newbie
Activity: 28
Merit: 0
September 03, 2017, 09:36:00 AM

I just placed an order for some g4600's. I will see how that works - the rig that had been crashing every couple hours crashed after 24 hours after I turned off teamviewer - hopefully this puts me over the top.

As for power, both are built the same way. Each is running on 2 750w EVGA G3 power supplies. Each SATA/molex power connector is running no more than 2 GPU risers. The molex connectors (and single SATA) hooked to the board each share with the riser for a single GPU (this means 13 GPU's, 2 motherboard molex, and 1 motherboard SATA to connect. The PSU's each have 3 SATA and 1 Perif (molex) connector, hence my using two connections per cable). I did have a 550w PSU in the mix (as a third) to see if that would change things, but it did not.

The only other discernable different is that not all GPU's are the same brand/make (but all are 1060 6GB), and the risers are not all identical (though I have switched them out in troubleshooting).

Good, G4600 is 2 core, 4 threads CPU. That will definetely help, much better than Celerons you have.

As for the mixed GPU's, try to put as many of the same brand/model in the same rig. Then you will have to manualy set overclocking for each GPU. Don't use the global OC for all. Try with the lowest stable value for all (I believe it was about 600 memory for you), then increase +50 memory on one brand/model and see if it's stable, then try +50 on different model and see if it's stable, then repeat until you get max for all models. It will take a while to fine tune it, that's the downside of mixed cards. Good luck and keep us posted.

Yesterday I swapped both Celeron G3930's for G4600's.

Overnight, the stable rig remained stable, the unstable rig crashed again.

Short of replacing all my risers again (and I am still open to specifics on what version to get) or RMA'ing the motherboard, is there anything else I might be missing?
newbie
Activity: 46
Merit: 0
September 03, 2017, 09:12:38 AM
Hi guys,

I've a problem with booting nvOS - never booted. I tried several USB sticks (16G and 32G), always successfully created (with Etcher, I've Mac). I tried on two computers.

Testing PC has ASUS ROG motherboard with 2x 1060.
RIG has ASRock H110 PRO BTC+ with 7x 1080Ti.

I tried connect DVI cable on primary GPU. On rig, I had a no signal, so I tried all GPUs - without signal. If I used motherboard DVI, so I got signal, but after choosing Ubuntu in boot menu, so it's freezy. After 30 minutes nothing happens.

Similar situation on second computer, I got monitor signal on both GPUs and motherboard, but always Ubuntu freezy and cursor blinking over 1 hour...

Can you help me, please? Thanks for any advice.


Disable on-board video (motherboard video) in the Bios. Connect monitor to GPU that is in the first x16 PCIe slot (the first long slot closest to the CPU).

Something is very wrong if boot takes longer than 3 minutes.

Did you verify the sha256 sum of the zip file?

to leenoox: thanks, now it works :-)

to fullzero: yes, verified.

BTW, I try use USB 2.0 sticks, so I bought USB 3.0 (Patriot Supersonic Rage XT 32GB) and repeat steps again. Now nvOS boot up in 30 seconds...

Thanks both :-)
member
Activity: 117
Merit: 10
September 03, 2017, 08:54:04 AM
This is the scheme of my setup. Is a box 44cm wide x 32cm high and gpus are setup on two levels one on top of other. (1060 3Gb gpu)
There is a raspberry pi wich allows me to reset/poweroff-on and control the inside temps using 5 sensors DS18B20.
12 fans push fresh air inside the box. They feed on an external psu. Temps with power limite 92W are 57-68ºC.
By the way I had a big cpu load (5-14) when I had power limit to 72W. Once set to 92W got down to 1.5-2.2 (yes I know no good yet, but much better).
I use a celeron g3900, looking forward to upgrade to I3.
I post this hoping the schematic helps others like me who have their rig in remote locations.
Here the code bits for temps, poweron/off and reset.

Code:
#!/bin/bash
# Script name: poweron-poweroff.sh
# El script apaga o enciende el equipo al que esta conectado
# usando el canal 1 del rele
GPIO_POWER=24
gpio -g mode $GPIO_POWER out
sleep 2
# Enciende o apaga el equipo segun su estado previo
gpio -g write $GPIO_POWER 1
sleep 1 # Lo mantengo activado 1 segundo
gpio -g write $GPIO_POWER 0
exit
Code:
#!/bin/bash
# Nombre script: reset_remoto.sh
# El script resetea el equipo al que esta conectado
# usando el canal 2 del rele
GPIO_RESET=23
gpio -g mode $GPIO_RESET out
sleep 2
# Resetea el equipo
gpio -g write $GPIO_RESET 1
sleep 1 # Lo mantengo pulsado 1 segundo
gpio -g write $GPIO_RESET 0
exit
Code:
#!/bin/bash
Nombre script: show_temp_sensores.sh
# El script lee la temperatura de los sensores
NOMBRES_DIR=/root/nombres
/bin/ls /sys/bus/w1/devices/ | grep 28* > $NOMBRES_DIR
N=$(/bin/cat $NOMBRES_DIR | wc -l)
echo "Numero de sensores : " $N
for ((LINEAS=1; LINEAS <= $N ; LINEAS=LINEAS+1))
do
NOMBRE_FILE=`/bin/sed -n -e "${LINEAS}p" $NOMBRES_DIR`
TEMP=$(/bin/cat /sys/bus/w1/devices/$NOMBRE_FILE/w1_slave | grep t= | awk -F= '{ printf "%.2f C\n", $2/1000}')
echo -n "Sensor$LINEAS :" $NOMBRE_FILE
echo " - Temp " $TEMP
done

newbie
Activity: 28
Merit: 0
September 03, 2017, 08:39:48 AM
Just loaded up the new v0019 onto my rig and works AWESOME!

Only bug I could find was that the maximum script didn't seem to work unless I selected "YES" on setting individual card temps.
But no biggie! Love it! Thanks fullzero
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
September 03, 2017, 08:35:01 AM
How to setup telegram for nvoc0019

First of all install Telegram, you can have it on almost all operating systems: Windows, Mac, Linux, Android, iOS, ...
Open your telegram and send /newbot to @BotFather
To send message to @botfather, click the search (magnifying glass) and search for @botfather, when found click start and send message /newbot
It will ask for name, send your desired bot name EX.  Mining Rigs Info
Then it ask for a username for your bot , send your desired unique username EX. papampi_mining_nvoc0019
it will give you an HTTP API token EX.     HTTP API: 408504581:AAHen-E4peZrlVhJx-GlnADyiVDgGiR4O8g
Put it in your 1bash  like this :
Code:
TELEGRAM_APIKEY="408504581:AAHen-E4peZrlVhJx-GlnADyiVDgGiR4O8g"
this part is ok
but
Quote
Now send /getid to @myidbot same search process for @botfather
It will give you a 8 digit number put it in 1bash :
Code:
 TELEGRAM_CHATID="97994065"
when I send /getid - it gives nothing, just silence
Could you please give more details on /getid ?
thank you

Have you searched for @myidbot ?
click start,
then click /getid


http://i65.tinypic.com/im16bc.jpg
newbie
Activity: 32
Merit: 0
September 03, 2017, 07:49:16 AM
How to setup telegram for nvoc0019

First of all install Telegram, you can have it on almost all operating systems: Windows, Mac, Linux, Android, iOS, ...
Open your telegram and send /newbot to @BotFather
To send message to @botfather, click the search (magnifying glass) and search for @botfather, when found click start and send message /newbot
It will ask for name, send your desired bot name EX.  Mining Rigs Info
Then it ask for a username for your bot , send your desired unique username EX. papampi_mining_nvoc0019
it will give you an HTTP API token EX.     HTTP API: 408504581:AAHen-E4peZrlVhJx-GlnADyiVDgGiR4O8g
Put it in your 1bash  like this :
Code:
TELEGRAM_APIKEY="408504581:AAHen-E4peZrlVhJx-GlnADyiVDgGiR4O8g"
this part is ok
but
Quote
Now send /getid to @myidbot same search process for @botfather
It will give you a 8 digit number put it in 1bash :
Code:
 TELEGRAM_CHATID="97994065"
when I send /getid - it gives nothing, just silence
Could you please give more details on /getid ?
thank you
full member
Activity: 378
Merit: 104
nvOC forever
September 03, 2017, 07:33:56 AM
Possible to mine nicehash equihash only?

When will KMD be integrated?

Guide to add  KMD

Code:
COIN="KMD"

Add coin details

Code:
KMD_WORKER="xxxx"
KMD_ADDRESS="xxxxxx"
KMD_POOL="kmd.suprnova.cc"
KMD_PORT="6250"


Add this to 3main file in right place:

Code:
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


@fullzero I'm getting prepared all the coins (stuck with cryptonight algo coins ATM), will share once its ready.

I have a question, what coins can we mine with ethminer (all 3 versions 11, 12dev, genoil) ?

Can we mine any ethash coin using ethminer?? My point is when we mine any ethash like EXP, UBQ, MUSIC, SOIL its better mine then with 0 fee uing ethminer?

I've tried to mine SOIL, but no success so far with ethminer, if someone succeeded using ethminer for any ethash, can you please share your 1bash and 3main, would like to integrate it with my version.

Thanks.


Thanks for adding more COIN selections.  Grin

With genoil and ethminer some coins need the -SP 2 or -SP 1 argument to work correctly. 

I haven't done comparative testing of Claymore vs ethminer vs genoil for EXP, UBQ, MUSIC, SOIL ect so I am unsure which has the best performance.

With SOIL; maybe adding the: -SP 2 or -SP 1 argument is needed.


Thanks fullzero, I've figured it out on how to use genoil/ethminer (any version) for mining any ethash, will add it to the list, do you have any coin requests pending? will also add them if there are any??
full member
Activity: 378
Merit: 104
nvOC forever
September 03, 2017, 07:24:26 AM
Please, explain me what does

P106_100_FULL_HEADLESS_MODE="YES/NO"

mean?

explain please also when should I use YES and when NO

Thank you in advance,
respectfully,
Sergey
Headless means no desktop

You only need to worry about that option if you are using P106-100 GPU's

If you are not using them then set it to 'NO'
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
September 03, 2017, 07:20:16 AM
Please, explain me what does

P106_100_FULL_HEADLESS_MODE="YES/NO"

mean?

explain please also when should I use YES and when NO

Thank you in advance,
respectfully,
Sergey
Headless means no desktop
newbie
Activity: 32
Merit: 0
September 03, 2017, 07:06:19 AM
Please, explain me what does

P106_100_FULL_HEADLESS_MODE="YES/NO"

mean?

explain please also when should I use YES and when NO

Thank you in advance,
respectfully,
Sergey
newbie
Activity: 8
Merit: 0
September 03, 2017, 06:31:42 AM
Back at version v0018, I had problem with mining not working when system started and launcher mining.
Claymore couldt connect, socket error.
If i started claymore manualy, then it worked..
That error was fixed later when i downloaded fixed scripts.

But now i installed fresh v0019 and same thing happening Cheesy

Im mining ETH with claymore 9.7-9.8 (genoil and ethminer have same problems)

Also i did update using 1update bash and rebooted.

Help ?! Cheesy
whats the output of
Code:
ps aux | grep miner
are you mining with remote setting or local ?
are you using upPaste?

Im using remote (at v0018 it didt matter if it was local or remote it still didt want to connect when mining)
not using parallax mode

after it didt work i tryed executing bash 4update and rebooting.
my upPaste hmm?! pasteBASH="uZNXXJuE"

m1        2376  0.0  0.0  27188  2884 ?        Ss   13:39   0:00 SCREEN -dmS miner /home/m1/eth/9_8/ethdcrminer64 -epool eu1.ethermine.org:4444 -ewal (my add i removed)/nvQ -epsw x -mode 1 -dbg -1
m1        2378  4.3  7.1 128451952 582152 pts/22 Ssl+ 13:39   0:01 /home/m1/eth/9_8/ethdcrminer64 -epool eu1.ethermine.org:4444 -ewal  (my add i removed)/nvQ -epsw x -mode 1 -dbg -1

Should it be address.name of miner not /

Yes i forgot to change to DOT Cheesy didt even see that Cheesy

Well thanks for help Cheesy
Jump to: