Bitcoin Forum
July 12, 2020, 04:08:27 AM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 [95] 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 ... 419 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining  (Read 416832 times)
argonaute
Newbie
*
Offline Offline

Activity: 50
Merit: 0


View Profile
July 15, 2017, 04:53:27 PM
 #1881

Fullzero, IAmNotAJeep or Maxximus007,

Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.

The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.

I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.

60 x 12 = 720 mns Smiley

the description is wrong in the 1bash file
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1594526907
Hero Member
*
Offline Offline

Posts: 1594526907

View Profile Personal Message (Offline)

Ignore
1594526907
Reply with quote  #2

1594526907
Report to moderator
1594526907
Hero Member
*
Offline Offline

Posts: 1594526907

View Profile Personal Message (Offline)

Ignore
1594526907
Reply with quote  #2

1594526907
Report to moderator
1594526907
Hero Member
*
Offline Offline

Posts: 1594526907

View Profile Personal Message (Offline)

Ignore
1594526907
Reply with quote  #2

1594526907
Report to moderator
Nexillus
Full Member
***
Offline Offline

Activity: 169
Merit: 100


View Profile
July 15, 2017, 05:03:15 PM
 #1882

Fullzero, IAmNotAJeep or Maxximus007,

Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.

The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.

I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.

60 x 12 = 720 mns Smiley

the description is wrong in the 1bash file

I did catch that and changed it to 3600 minutes or 2.5 days Smiley

Thank you though!
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 05:34:48 PM
 #1883

Quick question that I'm sure many of you have solved various ways.  Any thoughts on the safest way to power the 7th GPU(1070)/riser with an EVGA 1300 G2?  Custom adapter cable? Molex to 6+2?  Two of the VGA cables have a split connection from the PSU, but I didn't want to connect two cards and two risers split twice from the same cable. 

Thanks for any quick thoughts.

There are dual molex to pcie 6+2 adapters; if you use both molex cables 2 different molex cables(from the psu each from a different molex port) into one adapter it should be able to handle 160 watts.  I would keep it below 135 if you use this method.


Thanks for the reply, fullzero.  I had to do something a little more taxing due to a bad riser.  One of my risers is molex and I'm currently feeding that directly from the PSU with no desire to use a SATA adapter. 

Is the following a terrible shorterm solution (until I can get another working 6 pin riser)?


                                       MOLEX Riser (Zotac 1070 powered from VGA on card)
                        MOLEX <   MOLEX to 6 PIN adapter
PSU (1300 G2) <                                                    > 6 PIN Y to dual 6+2 > 6 PIN Riser + Zotac 1070
                        MOLEX <   MOLEX to 6 PIN adapter


Two molex from the PSU.  One feeds a molex riser with a 1070 in that riser (powered from VGA on the card) as well as one half of the dual molex to 6 pin adapter.  The other half is fed clean from the PSU.  All cards are at 125 PL.  It's currently running but I'd like a second opinion.


I'm not sure how much power the the 1070s pull from the pcie slot; but with a 125 pl I think this setup should be ok.


fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 05:36:47 PM
 #1884

I have tried to compile the newest ccminer for gtx 1060 for ages now, I cannot get it to work. This happens every time I try to compile.

akefile:1728: recipe for target 'ccminer-bignum.o' failed
make[2]: *** [ccminer-bignum.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mv -f .deps/ccminer-api.Tpo .deps/ccminer-api.Po
mv -f .deps/ccminer-util.Tpo .deps/ccminer-util.Po
mv -f .deps/ccminer-ccminer.Tpo .deps/ccminer-ccminer.Po
make[2]: Leaving directory '/home/m1/ccminer'
Makefile:2028: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/m1/ccminer'
Makefile:629: recipe for target 'all' failed
make: *** [all] Error 2


It is probably too difficult for non CS to compile ccminer; the current devs of each fork should really make an updated guide / mitigate some of the problems encountered when compiling.

Give me a link to the version / fork of ccminer you want to use and I will compile it optimized for 1060s.

I sent you a pm earlier on the miner to compile but I have found a faster one for chc, https://github.com/alexis78/ccminer.git

I will have to check; but I am reasonably sure the version of alexis I have with nvOC is the newest linux branch (the linux branch is extremely far behind the windows) not sure what is going on there.

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 05:40:50 PM
 #1885

Guys, I've been playing with the Power Limit, and don't quite understand something: by default my cards draw 180W each, but I could enforce a 125W limit without affecting the hash rate, and stable (keeping the OC settings I use). How is that possible? I'm only mining ETH with Genoil at the moment; since it mostly use the memory, I guess a underutilized GPU processor could allow that. If that's the case, dual-mining would need a higher limit, right? What would be the symptoms of needing to raise the power limit?

Core uses at lot more power than memory; so memory intensive algos like Ethash use less power.

When Dualmining you will need to increase the powerlimit.

If you don't; or fail to increase it enough: your rig will have lots of soft and hard crashes.

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 06:14:46 PM
 #1886

All,

Was working great in 16 but having issues dual mining ETC and SC with Claymore in 18.  Got ETC working and working WELL (yay higher hashrate for my 1060) but whenever I try to connect to siamining.com I'm getting an error:

Code:

 SC: Stratum - connecting to 'us-east.siamining.com' <45.79.159.167> port 7777
 SC: Stratum - Connected (us-east.siamining.com:7777)
 SC: Authorization failed
: {"id":2,"error":null,"result":false}
Stratum - reading socket failed, disconnect
 SC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=65C fan=60%

Here's my 1bash config:

Code:
SC_WORKER="nv$IP_AS_WORKER"
SC_ADDRESS="c4fa3fa4acf1a317752204d730888c755367d8e81092a944f6727d06251f1fd1a752576afac6"
SC_POOL="us-east.siamining.com:7777"
SC_GW_POOL="us-east.siamining.com:9980"

I'm using port 7777 to reach siamining.com on a dual mining claymore config on Windows 10 with no problem.  It's not clear to me what I should be setting the SC_GW_POOL value to.  Any insight there?

Thanks!

this pool uses the syntax:

-dpool stratum+tcp://us-east.siamining.com:7777 -dwal YourSiacoinAddress.YourWorkerName -dcoin sc

on or near line 2764:
Code:
SCADDR="$SC_ADDRESS/$SC_WORKER"

need to be changed to

Code:
SCADDR="$SC_ADDRESS.$SC_WORKER"

for this pool.

for the next 1bash; I will make a YES/NO switch to make this easier to change in the future.

Let me know if this solves the problem.

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 06:17:16 PM
 #1887

just a quick one

Quote
ASUS PRIME Z270-A (7x gpu: 9x if you use 2x m2 adapters) Link

does not work with 9 GPUs even though it has 2x m2 slots

unless someone knows some magical trick?

Did you change the bios settings as directed by the OP?


If you are using an ASUS PRIME Z270-A;

ensure 'Above 4G Decoding' is enabled in the bios.
 

Also ensure PTP aware OS: is set to 'Not PTP Aware' in the bios. 

Finally, ensure you 'Clear Secure Boot Keys' in the bios.

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 06:26:56 PM
 #1888

I tried v0018 today but with no success: whenever I finished flashing my usb stick with etcher I can't unmount the device from windows anymore. When I plug it out without unmounting, it boots up but after a while my ssh session disconnects and it seems to hang.

v0017 worked fine, where can I redownload it?

Were you imaging an SSD or HDD with etcher when it didn't let you eject?  If so that is expected. 

Anytime you cannot properly eject an imaged drive; shutdown the build pc and remove it after shutdown is complete.

SALFTER_NICEHASH_PROFIT_SWITCHING

and

IAmNotAJeep_and_Maxximus007_WATCHDOG

will intermittently kill your screen in their normal operation.

If you set both to "NO" and:

Code:
LOCALorREMOTE="REMOTE"

you should be able to have an uninterrupted SSH screen connection similar to v0017

When using PROFIT_SWITCHING and or WATCHDOG if your screen was killed you can connect to the regenerated one with the cmd:

Code:
screen -r miner

Also I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.




idle_shell
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
July 15, 2017, 06:29:05 PM
 #1889

All,

Was working great in 16 but having issues dual mining ETC and SC with Claymore in 18.  Got ETC working and working WELL (yay higher hashrate for my 1060) but whenever I try to connect to siamining.com I'm getting an error:

Code:

 SC: Stratum - connecting to 'us-east.siamining.com' <45.79.159.167> port 7777
 SC: Stratum - Connected (us-east.siamining.com:7777)
 SC: Authorization failed
: {"id":2,"error":null,"result":false}
Stratum - reading socket failed, disconnect
 SC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=65C fan=60%

Here's my 1bash config:

Code:
SC_WORKER="nv$IP_AS_WORKER"
SC_ADDRESS="c4fa3fa4acf1a317752204d730888c755367d8e81092a944f6727d06251f1fd1a752576afac6"
SC_POOL="us-east.siamining.com:7777"
SC_GW_POOL="us-east.siamining.com:9980"

I'm using port 7777 to reach siamining.com on a dual mining claymore config on Windows 10 with no problem.  It's not clear to me what I should be setting the SC_GW_POOL value to.  Any insight there?

Thanks!

this pool uses the syntax:

-dpool stratum+tcp://us-east.siamining.com:7777 -dwal YourSiacoinAddress.YourWorkerName -dcoin sc

on or near line 2764:
Code:
SCADDR="$SC_ADDRESS/$SC_WORKER"

need to be changed to

Code:
SCADDR="$SC_ADDRESS.$SC_WORKER"

for this pool.

for the next 1bash; I will make a YES/NO switch to make this easier to change in the future.

Let me know if this solves the problem.

That did the job.  A switch would be awesome but even just a comment somewhere relevant in the config would be a good pointer.
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 06:30:47 PM
Last edit: July 15, 2017, 07:01:27 PM by fullzero
 #1890

Fullzero, IAmNotAJeep or Maxximus007,

Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.

The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.

I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.

60 x 12 = 720 mns Smiley

the description is wrong in the 1bash file

I did catch that and changed it to 3600 minutes or 2.5 days Smiley

Thank you though!

Code:
AUTO_REBOOT="NO"

REBOOT_TIMEOUT_IN_MINUTES=720   # every 24 hours

the

Code:
REBOOT_TIMEOUT_IN_MINUTES

only applies if
Code:
AUTO_REBOOT="YES"

and yes it is a typo:

I meant to say 'once' every 12 hours

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 06:36:21 PM
 #1891

Fullzero, IAmNotAJeep or Maxximus007,

Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.

The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.

I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.

I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.

It is also possible that the timeouts between checks in the WATCHDOG should be relaxed when mining Ethash COINs.  Or relaxed in general.


If the timing is right; PROFIT_SWITCHING will switch close to the WATCHDOG check and a low utilization will be detected. 

I will make a flag for both IN-SWITCHING and DAG-BUILDING to prevent this in the next 1bash.



What COIN selection are you using or are you using SALFTER_NICEHASH_PROFIT_SWITCHING?


fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 06:58:03 PM
 #1892

All once again good afternoon!

I added:
1. email alarms (sendemail),
2. webUI for monitoring (apache2 + go + gotty),  
# All needed apts will install in first boot if $GOTTY="YES" || $EMAIL="YES". in settings.sh
3. auto update pasteBin and restart miner if something changes.
# you need to run crontab -e and add "*/5 * * * * ~/update_wallets.sh" . To check update every 5 minutes.


Completed / redone:
1. Option to set all Target temps and PowerLimits in two strings while using autoFANS
2. add specific PL and CLOCK for some coins
3. output nvidia-smi to screen every 30 sec when check fans, even if the fans are in manual mode. (to see temps, RPMs, memory in gotty, or via SSH, or via local quake)
4. Manual setting WORKER_NAME to use with pools. In settings.sh . If don't set using nvXXX (last digs of ip)
5. WORKER_NAME is hostname of rig, for more useful network search.

I divided the code into several files (start, miner, overclock, e-mail, fans). Settings rendered in 3 separate files:
settings.sh - constant machine settings
gpus_settings.sh - constant settings of video cards
wallets - settings of wallets, miners, machine settings variables.
Unfortunately, I have not yet had a chance to check how it works on the v18, but on v17 all is good. I think I can check in the next couple of days.

All the files are added to the folders as in the archive. Your need to change autostart from "gnome-terminal" to "~/start" (sudo nano ~/.config/autostart/webmob.desktop )
Settings are given in three files in the mnt sub folder. settings, gpus_settings, wallets

I would be happy if someone at least a small part of my work is useful.

fullzero and other developers: I ask for applications for deleted comments and descriptions, maybe even in some places copyright. While working on the code - some parts were in the way.

Of course, I could forget or confuse something, but I seem to remember everything and wrote.

Please do not make alternate releases.

As I have already told you:

https://bitcointalk.org/index.php?topic=1854250.msg20058141#msg20058141

Quote
In general I would like to offer as many options to members as possible and encourage members to share their customizations.

With any contribution, so long as it is not a blatant copy of a prior contribution; I will integrate it and add acknowledgement and BTC donation address to the top of oneBash.

If you use or make an executable; you must provide me with the source code and I will examine and compile it myself.

Your contribution must be free and open source.

I would like to avoid solutions involving the installation of multiple programs or services; to so something that can be done via SSH, SFTP, or a socket.


also see:

https://bitcointalk.org/index.php?topic=1854250.msg20093039#msg20093039


Quote
You can make modules to do distinct operations: like overclocking, miner selection, watchdog, monero mining, etc to make easier to tune/restart some parts.  And I will integrate them with switches to be readinto / not used in oneBash.  In addition they could also be used independently, such as a OC bash could be run while already mining.  A benchmarking bash / py could be made to find and log the opt stable settings ect.  The goal is to provide members with as many options as possible while maintaining ease of use.

Once most of the requested features have been implemented; I will make a github and target oneBash optimization.


It makes no sense to have members downloading multiple versions of the OS when only a few files are changed.  

Also; in such cases: I cannot confirm that the system has not been altered or malware added ( I am not saying you have done this, but that it is always a possibility especially when done by new members).  


If you post the code for each additional file (or send me a pm with it); I will integrate your contributions into 1bash (or selectively in 2unix depending on how different they are) with a single or multiple switches: and add acknowledgement and your BTC donation address to the top of 1bash.



 


fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 07:02:48 PM
 #1893

All,

Was working great in 16 but having issues dual mining ETC and SC with Claymore in 18.  Got ETC working and working WELL (yay higher hashrate for my 1060) but whenever I try to connect to siamining.com I'm getting an error:

Code:

 SC: Stratum - connecting to 'us-east.siamining.com' <45.79.159.167> port 7777
 SC: Stratum - Connected (us-east.siamining.com:7777)
 SC: Authorization failed
: {"id":2,"error":null,"result":false}
Stratum - reading socket failed, disconnect
 SC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=65C fan=60%

Here's my 1bash config:

Code:
SC_WORKER="nv$IP_AS_WORKER"
SC_ADDRESS="c4fa3fa4acf1a317752204d730888c755367d8e81092a944f6727d06251f1fd1a752576afac6"
SC_POOL="us-east.siamining.com:7777"
SC_GW_POOL="us-east.siamining.com:9980"

I'm using port 7777 to reach siamining.com on a dual mining claymore config on Windows 10 with no problem.  It's not clear to me what I should be setting the SC_GW_POOL value to.  Any insight there?

Thanks!

this pool uses the syntax:

-dpool stratum+tcp://us-east.siamining.com:7777 -dwal YourSiacoinAddress.YourWorkerName -dcoin sc

on or near line 2764:
Code:
SCADDR="$SC_ADDRESS/$SC_WORKER"

need to be changed to

Code:
SCADDR="$SC_ADDRESS.$SC_WORKER"

for this pool.

for the next 1bash; I will make a YES/NO switch to make this easier to change in the future.

Let me know if this solves the problem.

That did the job.  A switch would be awesome but even just a comment somewhere relevant in the config would be a good pointer.

This is first time I have seen this syntax with SC; I will add comments as well.

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 07:13:57 PM
 #1894

How exactly do I utilize

The new watchdog function?

Auto reboot?

And can I remote in?

First I recommend watching the v0018 DEMO linked on the OP: I give an overview of how the WATCHDOG works.

To use the WATCHDOG; you only need to set:

Code:
IAmNotAJeep_and_Maxximus007_WATCHDOG="YES"


AUTO_REBOOT will stop all mining and reboot when its timeout expires.  You use it by setting:

Code:
AUTO_REBOOT="YES"

and then setting the timeout in minutes
Code:
REBOOT_TIMEOUT_IN_MINUTES=1440

is once a day

If you are planning on using a headless / SSH setup ensure:

Code:
LOCALorREMOTE="REMOTE"

then after SSHing into the rig:

enter

Code:
screen -r miner


SALFTER_NICEHASH_PROFIT_SWITCHING

and

IAmNotAJeep_and_Maxximus007_WATCHDOG

will intermittently kill your screen in their normal operation.


When using PROFIT_SWITCHING and or WATCHDOG if your screen was killed you can connect to the regenerated one with the same cmd:

Code:
screen -r miner


Also I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.

fk1
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
July 15, 2017, 07:19:06 PM
Last edit: July 15, 2017, 07:30:04 PM by fk1
 #1895

I tried v0018 today but with no success: whenever I finished flashing my usb stick with etcher I can't unmount the device from windows anymore. When I plug it out without unmounting, it boots up but after a while my ssh session disconnects and it seems to hang.

v0017 worked fine, where can I redownload it?

Were you imaging an SSD or HDD with etcher when it didn't let you eject?  If so that is expected.  

Anytime you cannot properly eject an imaged drive; shutdown the build pc and remove it after shutdown is complete.

SALFTER_NICEHASH_PROFIT_SWITCHING

and

IAmNotAJeep_and_Maxximus007_WATCHDOG

will intermittently kill your screen in their normal operation.

If you set both to "NO" and:

Code:
LOCALorREMOTE="REMOTE"

you should be able to have an uninterrupted SSH screen connection similar to v0017

When using PROFIT_SWITCHING and or WATCHDOG if your screen was killed you can connect to the regenerated one with the cmd:

Code:
screen -r miner

Also I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.





serious issues over here since 0018. I did reflash my stick, edited the 1bash and shut down computer. I SSHed into my rig like forever and when I take a look at nvidia-smi no cards are working (0%). nanoing the bash file over ssh doesn't work, nothing happens...

took a look: /media/m1 empty. I did not understand what you meant with

Quote
Were you imaging an SSD or HDD with etcher when it didn't let you eject?  If so that is expected.

I just downloaded the zip file you provided to my win system on ssd (checked the zip file successfully btw) unzipped the image and load it in etcher, choose my usb stick and flash+verify it. same procedure as 0017 but without the unmounting problem.

e: google says its etcher problem lets see... i also get info i have to format stick after flashing from win so i try to untick auto eject in etcher
Deki1904
Sr. Member
****
Offline Offline

Activity: 504
Merit: 250


View Profile
July 15, 2017, 07:29:52 PM
 #1896

Hi i added DeepOnion Mining in v17 without a Problem, but i cant get it working in v18

This is from v17:


ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="localhost:3633"


if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"

until $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
   do
   echo "FAILURE; reinit in 5" >&2
   sleep 5
done
fi


and this here v18 are not working

ONION_WORKER="nv$IP_AS_WORKER"
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"


if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"

screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION

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


also how could i Solo mining this coin by changing here the Parameters?
Just set localhost as Pool, but wehere to add the conf. for ccminer?

ccminer config for Onion?!
testnet=0
listen=1
maxconnections=30
server=1
rpcuser=username
rpcpassword=pass
rpcport=18580
rpcconnect=127.0.0.1

cheers
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 07:34:32 PM
 #1897

I tried v0018 today but with no success: whenever I finished flashing my usb stick with etcher I can't unmount the device from windows anymore. When I plug it out without unmounting, it boots up but after a while my ssh session disconnects and it seems to hang.

v0017 worked fine, where can I redownload it?

Were you imaging an SSD or HDD with etcher when it didn't let you eject?  If so that is expected. 

Anytime you cannot properly eject an imaged drive; shutdown the build pc and remove it after shutdown is complete.

SALFTER_NICEHASH_PROFIT_SWITCHING

and

IAmNotAJeep_and_Maxximus007_WATCHDOG

will intermittently kill your screen in their normal operation.

If you set both to "NO" and:

Code:
LOCALorREMOTE="REMOTE"

you should be able to have an uninterrupted SSH screen connection similar to v0017

When using PROFIT_SWITCHING and or WATCHDOG if your screen was killed you can connect to the regenerated one with the cmd:

Code:
screen -r miner

Also I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it.





serious issues over here since 0018. I did reflash my stick, edited the 1bash and shut down computer. I SSHed into my rig like forever and when I take a look at nvidia-smi no cards are working (0%). nanoing the bash file over ssh doesn't work, nothing happens...

took a look: /media/m1 empty. I did not understand what you meant with

Quote
Were you imaging an SSD or HDD with etcher when it didn't let you eject?  If so that is expected.

I just downloaded the zip file you provided to my win system on ssd (checked the zip file successfully btw) unzipped the image and load it in etcher, choose my usb stick and flash+verify it. same procedure as 0017 but without the unmounting problem.

in v0018 1bash is located at:

Code:
'/home/m1/1bash'

to open it with nano you would use:

Code:
nano '/home/m1/1bash'

Quote
Were you imaging an SSD or HDD with etcher when it didn't let you eject?  If so that is expected.

By this I mean: if you are imaging nvOC to an SSD or HDD most OS will not let you eject a system drive.  If you are using a USB key and this happened then there is something going wrong with etcher.

Quote
I just downloaded the zip file you provided to my win system on ssd (checked the zip file successfully btw) unzipped the image and load it in etcher, choose my usb stick and flash+verify it. same procedure as 0017 but without the unmounting problem.

Do you mean you used HDDRawCopy and it didn't have this problem?  If so then there may be an issue with etcher.

I will update the SSH guide now for v0018.


fk1
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
July 15, 2017, 07:39:57 PM
 #1898

Quote
Do you mean you used HDDRawCopy and it didn't have this problem?  If so then there may be an issue with etcher.

I never used HDDRawCopy. seems like etcher is the problem although I am doin nothing else since flashing 0017 wich flashed flawlessly
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 07:45:16 PM
 #1899

Hi i added DeepOnion Mining in v17 without a Problem, but i cant get it working in v18

This is from v17:


ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="localhost:3633"


if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"

until $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION
   do
   echo "FAILURE; reinit in 5" >&2
   sleep 5
done
fi

and this here v18 are not working

ONION_WORKER="nv$IP_AS_WORKER"
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"


if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"

screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION

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


also how could i Solo mining this coin by changing here the Parameters?
Just set localhost as Pool, but wehere to add the conf. for ccminer?

ccminer config for Onion?!
testnet=0
listen=1
maxconnections=30
server=1
rpcuser=username
rpcpassword=pass
rpcport=18580
rpcconnect=127.0.0.1

cheers


try:
Code:
ONION_ADDRESS="DijjrA5hMtFxuqt2U3BiF5gZ1sejxVQBFi"
ONION_POOL="stratum+tcp://kawaiipool.party:3633"


Code:
if [ $COIN == "ONION" ]
then
HCD='/home/m1/TPccminer/ccminer'
ADDR="$ONION_ADDRESS"

screen -dmS miner $HCD -a x13 -o $ONION_POOL -u $ADDR -p c=ONION

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

BITCOIN="theGROUND"

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

and let me know if it works


conf should be in the

'/home/m1/TPccminer'

directory

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
July 15, 2017, 07:47:57 PM
 #1900

Quote
Do you mean you used HDDRawCopy and it didn't have this problem?  If so then there may be an issue with etcher.

I never used HDDRawCopy. seems like etcher is the problem although I am doin nothing else since flashing 0017 wich flashed flawlessly

I changed the format of the windows partition for v0018 which possibly is causing problems with etcher.  I will try to replicate this problem with etcher; for now with windows I would try HDDRawCopy and see if it works as intended.

I also am not sure if there is a problem with the resulting image; regardless of if etcher cannot properly eject the image afterwards.



Pages: « 1 ... 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 [95] 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 ... 419 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!