Bitcoin Forum
November 18, 2024, 07:49:28 AM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 146 147 148 ... 416 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining  (Read 418244 times)
hatch789
Member
**
Offline Offline

Activity: 66
Merit: 10


View Profile WWW
July 17, 2017, 09:38:06 PM
 #1941

Hey Full,

Is there any way you could make the image a tiny bit smaller? I (and I'm sure others) have 16G USB sticks that are already USB 3.0. Unfortunately your image is just a few hundred MB too large to fit onto a 16G stick.

I see there is free space at the end of the image. Any chance you could trim off just 500MB? -If you are able to do that then we can truly use our 16G USB Sticks without hassle.

Also running into an issue with RDP. It won't let me connect. I have tried searching the forum; I know you said it's fully indexed by google... but HOW does one search just this thread in google for something like RDP as an example? If you have an example of that type of search string it would be great.




Thanks,
-Hatch -= http://UbuMiner.com =-
Deki1904
Sr. Member
****
Offline Offline

Activity: 490
Merit: 250


View Profile
July 17, 2017, 09:44:20 PM
 #1942

Gparted would be cool. Because I tried to install few things it didn't work for me. Not enough space. I couldn't install Gparted... Would be nice for the next image. Also if you could add solo mining options would be great. That you could connect to one instance server what ever. Maybe for few coins not all at the time. Think it's a lot of work.

Cheers
hatch789
Member
**
Offline Offline

Activity: 66
Merit: 10


View Profile WWW
July 17, 2017, 09:56:22 PM
 #1943

Gparted would be cool. Because I tried to install few things it didn't work for me. Not enough space. I couldn't install Gparted... Would be nice for the next image. Also if you could add solo mining options would be great. That you could connect to one instance server what ever. Maybe for few coins not all at the time. Think it's a lot of work.

Cheers

GParted Partition Editor is already included in the build mate! Use the top left button to search and start typing GPAR ...it's there. Trust me. nv0018 build has it at least.

Thanks,
-Hatch -= http://UbuMiner.com =-
i0n
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
July 18, 2017, 12:37:17 AM
 #1944

Where is the changelog for v18?
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 01:47:21 AM
 #1945

I tried to Change TPccminer to ASccminer for Skein Algo Mining DGB, nothing happend, Mining will not start.

With TPccminer is working well... but AS is faster 20-30%...

Any idea why istn working?

cheers

The linux branch of AS is very far behind the Windows branch; I'm not sure if the linux branch even supports DGB. 



I will look into the link kw1k sent me:

https://github.com/alexis78/ccminer/tree/master

and see if this is different from the version I complied for nvOC.




I compiled the alexis78 git under ubuntu 16.04 VM, this version does support c11. Not sure about DGB algos as I have not tested.

K good to know.

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 01:58:40 AM
 #1946

I am getting errors on V.18
I am SSH ONLY. No monitor. No Guake. No Gnome.

First error is after 1bash tries to stop TeamViewer -


Mon Jul 17 14:26:28 EDT 2017
Action: Removing ...
systemctl stop teamviewerd.service
Failed to stop teamviewerd.service: Unit teamviewerd.service not loaded.
fail

kill '/opt/teamviewer/tv_bin/script/teamviewer' - root (/home/m1/.local/share/teamviewer12 / /home/m1/.local/share/teamviewer12)



Failed to execute operation: No such file or directory
try again, full path...
Failed to execute operation: Invalid argument

Second error is when Maxximus007_AUTO_TEMPERATURE_CONTROL launches -

LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL

process in Guake Tab

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

I have to assume Temp Control has failed and is not working.
Can you consider launching temp control and watchdog NOT in Guake if "REMOTE" is chosen but in screens instead? I will try to change bash myself to make this happen.

Thanks


I will make a conditional execution for the teamviewer block and add the appropriate export cmd in the auto temp block to resolve those errors.

To get auto temp working ( almost positive this is the problem ) add this line:
Code:
EXPORT DISPLAY=:0

I can make each open in a screen when remote is selected.

If you replace the:

Code:
if [ $Maxximus007_AUTO_TEMPERATURE_CONTROL == "YES" ]

block with:


Code:
if [ $Maxximus007_AUTO_TEMPERATURE_CONTROL == "YES" ]
then

cd /home/m1

rm /home/m1/p0
rm /home/m1/p1
rm /home/m1/p2
rm /home/m1/p3
rm /home/m1/p4
rm /home/m1/p5
rm /home/m1/p6
rm /home/m1/p7
rm /home/m1/p8
rm /home/m1/p9
rm /home/m1/p10
rm /home/m1/p11
rm /home/m1/p12
rm /home/m1/p13
rm /home/m1/t0
rm /home/m1/t1
rm /home/m1/t2
rm /home/m1/t3
rm /home/m1/t4
rm /home/m1/t5
rm /home/m1/t6
rm /home/m1/t7
rm /home/m1/t8
rm /home/m1/t9
rm /home/m1/t10
rm /home/m1/t11
rm /home/m1/t12
rm /home/m1/t13
rm /home/m1/fa
rm /home/m1/pa
rm /home/m1/td
rm /home/m1/rpl

sleep 2

echo $INDIVIDUAL_POWERLIMIT_0 > '/home/m1/p0'
echo $INDIVIDUAL_POWERLIMIT_1 > '/home/m1/p1'
echo $INDIVIDUAL_POWERLIMIT_2 > '/home/m1/p2'
echo $INDIVIDUAL_POWERLIMIT_3 > '/home/m1/p3'
echo $INDIVIDUAL_POWERLIMIT_4 > '/home/m1/p4'
echo $INDIVIDUAL_POWERLIMIT_5 > '/home/m1/p5'
echo $INDIVIDUAL_POWERLIMIT_6 > '/home/m1/p6'
echo $INDIVIDUAL_POWERLIMIT_7 > '/home/m1/p7'
echo $INDIVIDUAL_POWERLIMIT_8 > '/home/m1/p8'
echo $INDIVIDUAL_POWERLIMIT_9 > '/home/m1/p9'
echo $INDIVIDUAL_POWERLIMIT_10 > '/home/m1/p10'
echo $INDIVIDUAL_POWERLIMIT_11 > '/home/m1/p11'
echo $INDIVIDUAL_POWERLIMIT_12 > '/home/m1/p12'
echo $INDIVIDUAL_POWERLIMIT_13 > '/home/m1/p13'

echo $TARGET_TEMP_0 > '/home/m1/t0'
echo $TARGET_TEMP_1 > '/home/m1/t1'
echo $TARGET_TEMP_2 > '/home/m1/t2'
echo $TARGET_TEMP_3 > '/home/m1/t3'
echo $TARGET_TEMP_4 > '/home/m1/t4'
echo $TARGET_TEMP_5 > '/home/m1/t5'
echo $TARGET_TEMP_6 > '/home/m1/t6'
echo $TARGET_TEMP_7 > '/home/m1/t7'
echo $TARGET_TEMP_8 > '/home/m1/t8'
echo $TARGET_TEMP_9 > '/home/m1/t9'
echo $TARGET_TEMP_10 > '/home/m1/t10'
echo $TARGET_TEMP_11 > '/home/m1/t11'
echo $TARGET_TEMP_12 > '/home/m1/t12'
echo $TARGET_TEMP_13 > '/home/m1/t13'

echo $__FAN_ADJUST > '/home/m1/fa'
echo $POWER_ADJUST > '/home/m1/pa'
echo $ALLOWED_TEMP_DIFF > '/home/m1/td'
echo $RESTORE_POWER_LIMIT > '/home/m1/rpl'
echo ""
echo "LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL "

HCD='/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL'
running=$(ps -ef | awk '$NF~"Maxximus007_AUTO_TEMPERATURE_CONTROL" {print $2}')
if [ "$running" == "" ]
then
EXPORT DISPLAY=:0

if [ $LOCALorREMOTE == "LOCAL" ]
then
guake -n $HCD -r Maxximus007_AUTO_TEMPERATURE_CONTROL -e "bash /home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL"
  echo ""
  echo "process in guake terminal (f12)"
  echo ""
fi

if [ $LOCALorREMOTE == "REMOTE" ]
then
screen -dmS autotemp $HCD
  echo ""
  echo "process in screen autotemp; attach with: screen -r autotemp"
  echo ""
fi

running=""
fi
fi

it should implement this change (but I haven't tested it)

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 02:01:21 AM
 #1947

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?



I am not currently using SALFTER_NICEHASH_PROFIT_SWITCHING since Ethash is so close with the profit switching right now.

Not sure what it is but I am rolling back to VER17 on this rig, as it just restarted again and then hard locked up after initial start-up showing a black screen then the flash drive was corrupted and refused to boot.

Just found out it may have been the flash drive the last 48 hours as it just died. LOL write errors all over it. I am testing now with a new flash drive.

What program are you using to image you USB key?

If your using a Windows build computer; I would use hddrawcopy for v0018.

Let me know if this is working with your new USB key.

I am using hddrawcopy on windows 10. It seems to be the flash drive, been over 20 hours now no issues with a new flash drive.

Love new flash drive dies within a week, time to contact newegg!
I am using hddrawcopy  on windows 10, it was the flash drive.

Glad it was a hardware issue; an not a major software problem.  The v0018 watchdog reboots a little too aggressively; but with reasonable OC it should still work effectively.

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 02:09:48 AM
 #1948

So if I want my rigs to be completely headless is there a way to access Teamviewer and enable all those check marks for auto running, and log in through ssh? or is there a better alternative? as it is now, I have a fully closed rig, and I have to rip it apart everytime, I want to update to a new version or if there is an issue with my TV or USB. Thanks!

The simplest solution for now is probably:

https://www.amazon.com/dp/B00B2HOKKQ


I don't use teamviewer; so another member can probably answer if it has cmd line interface or not: if it does I can add automation for setup. 

I've been attempting to finish a: monitor / push / update / dashboard app for a while now.  Keep getting sidetracked keeping up with new coins and integrations + there is an rxOC stack now as well.  Although I do think the contributions so far are extremely helpful and have deserved to be bumped to the front of my improvement stack.

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 02:15:28 AM
 #1949

Hey Full,

Is there any way you could make the image a tiny bit smaller? I (and I'm sure others) have 16G USB sticks that are already USB 3.0. Unfortunately your image is just a few hundred MB too large to fit onto a 16G stick.

I see there is free space at the end of the image. Any chance you could trim off just 500MB? -If you are able to do that then we can truly use our 16G USB Sticks without hassle.

Also running into an issue with RDP. It won't let me connect. I have tried searching the forum; I know you said it's fully indexed by google... but HOW does one search just this thread in google for something like RDP as an example? If you have an example of that type of search string it would be great.


I will add using a 15.5gb image to the list.

first enable / configure with the Desktop Sharing GUI on the left on the rig you want to connect to.

then with another ubuntu computer

Try using the Remmina client to RDP.

see:

https://github.com/FreeRDP/Remmina/wiki/Remmina-User%27s-guide

for more info.

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 02:17:37 AM
 #1950

Gparted would be cool. Because I tried to install few things it didn't work for me. Not enough space. I couldn't install Gparted... Would be nice for the next image. Also if you could add solo mining options would be great. That you could connect to one instance server what ever. Maybe for few coins not all at the time. Think it's a lot of work.

Cheers

GParted Partition Editor is already included in the build mate! Use the top left button to search and start typing GPAR ...it's there. Trust me. nv0018 build has it at least.

hatch789 is right; gparted has been installed since ~ v0015.

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 02:18:27 AM
 #1951

Where is the changelog for v18?

its on the OP ( Original Post or post # 1 )

v0018
  re - added SSD / HDD support
  updated driver to: 384.47
  added CLAYMORE 9.7
  added plus integrated SRR support: Thanks xleejohnx  Grin
  added plus integrated IAmNotAJeep_and_Maxximus007_WATCHDOG: Thanks IAmNotAJeep  and  Maxximus007  Grin
  added plus integrated Maxximus007_AUTO_TEMPERATURE_CONTROL: Thanks Maxximus007  Grin
  added plus integrated SALFTER_NICEHASH_PROFIT_SWITCHING: Thanks salfter  Grin
  added AUTO_REBOOT selector
  added GPUPowerMizerMode_Adjust and selector
  added LOCALorREMOTE selector
  added lspci and nvidia-smi output to the top of mining process
  prepended 'nv' to auto workernames
    Zpool_Blake_2S COIN selection
    Zpool_Lyra2v2 COIN selection
    GRS COIN selection
    DMD COIN selection

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 02:28:05 AM
 #1952

Hey guys I am running v0013 and it was running smoothly for 5 weeks.  Now every few days the terminal locks up with this error :

Error message : NVML: cannot get current temperature, error 15

Has anyone here seen the issue before or found a way to resolve?

My rig uses 9x 1070s OC settings are cc100 / mem900 which was stable for 3 weeks.  Recently I power limited to 140 ( I dual mine ) but I seem to get the error whether power limit is on or off.

Since the system freezes I cant remote in to reset it.   I might buy a wifi power point so I can reaet it today but would rather a cure Wink

I scoured the forums and some people reckon turning off WD worked in windows but cant seem to replicate the fix in Linux.

Here was one solution :
"Problem solved : -write "-wd 0" in claymore start.bat -in windows power management high, pci off"

If you only started having this problem after increasing your powerlimit: your risers might not be quite able to handle the higher powerlimit.

What kind of risers are you using, and how are you powering them?


If you look in the system log after a crash:

top left type system, click System Log

it should tell you what likely caused the trash.


If you are using claymore:  I highly recommend updating to v0018 as it has the 9.7 version of claymore which has significantly higher hashrates.

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
July 18, 2017, 02:49:43 AM
Last edit: July 18, 2017, 06:38:37 PM by fullzero
 #1953

I got a BIOSTAR TB250-BTC PRO (12x gpu) today Link

I made a 12x 1060 rig with it.

ensure Mining Mode is enabled in the bios LINK  

ensure Max TOLUD is set to 3.5 GB in the bios LINK

NOTE: you must first only connect 6x GPUs, boot, make Bios changes, save and reboot, shutdown, add the other 6x GPUs, attach the USB or SSD and boot





I like the 13x out the box + m2 ssd ready ASRock more; but this is also a good mobo.  

Biostar sadly still can't handle; making mining settings the default.

mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of:  2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days.  How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ).  This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis.  If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
dbolivar
Member
**
Offline Offline

Activity: 119
Merit: 10


View Profile
July 18, 2017, 05:24:09 AM
 #1954

I'm planning to experiment with Salfter's NiceHash switcher, but by reading the relevant code in 1bash and switch, it seems that the individual OC settings (per card) defined in 1bash won't be used at all - only the ones set per coin, applied to all the cards. Since I have a mix of different cards, each one must take different core and mem OC values. I have an initial idea of the code changes needed, but before doing that, I'd like to check if there's another way to do that already implemented (which I missed), or something already being developed in that sense.

Thanks!
Deki1904
Sr. Member
****
Offline Offline

Activity: 490
Merit: 250


View Profile
July 18, 2017, 06:38:30 AM
 #1955

Oh Sorry, didn't realize that they are integreated. Anyhow i like your work Keep going Smiley
When i have Mined enough Coins i will send you a Little Tip. Actually im Mining DeepOnion Coins...

Cheers

Gparted would be cool. Because I tried to install few things it didn't work for me. Not enough space. I couldn't install Gparted... Would be nice for the next image. Also if you could add solo mining options would be great. That you could connect to one instance server what ever. Maybe for few coins not all at the time. Think it's a lot of work.

Cheers

GParted Partition Editor is already included in the build mate! Use the top left button to search and start typing GPAR ...it's there. Trust me. nv0018 build has it at least.

hatch789 is right; gparted has been installed since ~ v0015.
damNmad
Full Member
***
Offline Offline

Activity: 378
Merit: 104


nvOC forever


View Profile
July 18, 2017, 07:44:05 AM
 #1956

Where is the changelog for v18?

Go to the first page of this post and you can find change log for every release.

You are welcome.

DeepOnion    ▬▬  Anonymous and Untraceable  ▬▬    ENJOY YOUR PRIVACY  •  JOIN DEEPONION
▐▐▐▐▐▐▐▐   ANN  Whitepaper  Facebook  Twitter  Telegram  Discord    ▌▌▌▌▌▌▌▌
Get $ONION  (✔Cryptopia  ✔KuCoin)  |  VoteCentral  Register NOW!  |  Download DeepOnion
BaliMiner
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
July 18, 2017, 07:49:07 AM
 #1957

Hi All,
i made a telegram script to report hash rates and other stats using telegram bot, the stats consists of power draw, temperature and fan speed on my little mining rig.

the code below, i got the command from older posts, currently the hash rates obtained from claymore or other miner that supports web-api, this script only works for claymore, can be modified if you are using ewbf, other stats is miner agnostic obtained from nvidia-smi
 
Code:
#!/bin/bash
# Telegram Info Script
# By BaliMiner et al...
# for nvOC by fullzero
# ref: http://bernaerts.dyndns.org/linux/75-debian/351-debian-send-telegram-notification
#
CHATID=<your-chat-id>
APIKEY=<your-bot-token-api-key>
CURRENTHASH=`/usr/bin/curl -s http://localhost:3333 | sed '/Total/!d; /Speed/!d;' | awk '{print $6}' | awk 'NR == 3'`
TEMP=$(/usr/bin/nvidia-smi --query-gpu=temperature.gpu --format=csv)
PD=$(/usr/bin/nvidia-smi --query-gpu=power.draw --format=csv)
FAN=$(/usr/bin/nvidia-smi --query-gpu=fan.speed --format=csv)
LF=$'\n'
PROFIT=$(cat /home/m1/current-profit)
MSG="Current Hashrate = "$CURRENTHASH" "$TEMP$LF$PD

/usr/bin/curl -s -X POST --output /dev/null https://api.telegram.org/bot${APIKEY}/sendMessage -d "text=${MSG}" -d chat_id=${CHATID}

put the script on crontab and specify how often you wanted the report ex: 5 mins, then put this on your crontab
Code:
*/5 * * * * /home/m1/telegram-info
dont forget to chmod 700 on the script to make it executable

Hope this script helps...
any suggestion is appreciated Smiley
citronick
Legendary
*
Offline Offline

Activity: 1834
Merit: 1080


---- winter*juvia -----


View Profile
July 18, 2017, 10:48:30 AM
 #1958

fullzero -- did you managed to get ccminer_alexei78 into this new v18 build?

If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
lost_post
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
July 18, 2017, 12:15:09 PM
 #1959

I divided the settings into several files, so that it would be possible to set up purses and choose a currency, could be shared across several farms. And the map and system settings were locally configured.

Here is code to send email:
Quote
EMAIL_TEXT=$1 # take argument and put it to $EMAIL_TEXT
sudo apt-get install libio-socket-ssl-perl libnet-ssleay-perl sendemail -y
# to send email use command ( ./mail.sh X) where X is N of text message.

case $EMAIL_TEXT in
     0)
     SUBJECT="Starting $WORKER_NAME"
     TEXT="System was started just now!"
          ;;
     1)
     SUBJECT="Starting $WORKER_NAME"
     TEXT="GPU Miner was started just now!"
          ;;
     2)
     SUBJECT="Starting $WORKER_NAME"
     TEXT="CPU Miner was started just now!"
          ;;
     3)
     SUBJECT="Restaring $WORKER_NAME"
     TEXT="GPU miner was crushed and restarting now"
          ;;
     4)
     SUBJECT="Settings update $WORKER_NAME"
     TEXT="New setiings arrived. Restart now"
          ;;
     5)
     SUBJECT="Rebooting $WORKER_NAME"
     TEXT="Lost GPU so restarting system."
          ;;
     6)
     SUBJECT="Rebooting $WORKER_NAME"
     TEXT="Utilization is too low: reviving did not work so restarting system in 10 seconds"
          ;;
     7)
     SUBJECT="Starting $WORKER_NAME"
     TEXT="NICEHASH was started just now!"
          ;;
     Cool
     SUBJECT="Starting $WORKER_NAME"
     TEXT="Gotty was started just now"
          ;;
     *)
     SUBJECT="Error $WORKER_NAME"
     TEXT="Error with subject!"
          ;;
esac

sendemail -f $RIG_EMAIL -t $ADMIN_EMAIL -u $SUBJECT -m "$TEXT" -s $RIG_SMTP -o tls=yes -xu $RIG_EMAIL -xp $RIG_EMAIL_PASS &
It will try to install sendemail every time, but it is not problem. Or you can add apt-get in firstBOOT section of 1bash. All arguments must be loaded from 1bash using files. But I don't have time to do it, for now. I am using another way - I add "source ~/wallets # from this file we take $ADMAIL_EMAIL
source ~/settings.sh # from this file we take $RIG_EMAIL, $WORKER_NAME, $RIG_EMAIL_PASS, $RIG_SMTP
".
OverEasy
Sr. Member
****
Offline Offline

Activity: 301
Merit: 251


View Profile
July 18, 2017, 12:39:04 PM
Last edit: July 18, 2017, 02:20:33 PM by OverEasy
 #1960

I am getting errors on V.18
I am SSH ONLY. No monitor. No Guake. No Gnome.

First error is after 1bash tries to stop TeamViewer -


Mon Jul 17 14:26:28 EDT 2017
Action: Removing ...
systemctl stop teamviewerd.service
Failed to stop teamviewerd.service: Unit teamviewerd.service not loaded.
fail

kill '/opt/teamviewer/tv_bin/script/teamviewer' - root (/home/m1/.local/share/teamviewer12 / /home/m1/.local/share/teamviewer12)



Failed to execute operation: No such file or directory
try again, full path...
Failed to execute operation: Invalid argument

Second error is when Maxximus007_AUTO_TEMPERATURE_CONTROL launches -

LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL

process in Guake Tab

Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.

I have to assume Temp Control has failed and is not working.
Can you consider launching temp control and watchdog NOT in Guake if "REMOTE" is chosen but in screens instead? I will try to change bash myself to make this happen.

Thanks


I will make a conditional execution for the teamviewer block and add the appropriate export cmd in the auto temp block to resolve those errors.

To get auto temp working ( almost positive this is the problem ) add this line:
Code:
EXPORT DISPLAY=:0

I can make each open in a screen when remote is selected.

If you replace the:

Code:
if [ $Maxximus007_AUTO_TEMPERATURE_CONTROL == "YES" ]

block with:


Code:
if [ $Maxximus007_AUTO_TEMPERATURE_CONTROL == "YES" ]
then

cd /home/m1

rm /home/m1/p0
rm /home/m1/p1
rm /home/m1/p2
rm /home/m1/p3
rm /home/m1/p4
rm /home/m1/p5
rm /home/m1/p6
rm /home/m1/p7
rm /home/m1/p8
rm /home/m1/p9
rm /home/m1/p10
rm /home/m1/p11
rm /home/m1/p12
rm /home/m1/p13
rm /home/m1/t0
rm /home/m1/t1
rm /home/m1/t2
rm /home/m1/t3
rm /home/m1/t4
rm /home/m1/t5
rm /home/m1/t6
rm /home/m1/t7
rm /home/m1/t8
rm /home/m1/t9
rm /home/m1/t10
rm /home/m1/t11
rm /home/m1/t12
rm /home/m1/t13
rm /home/m1/fa
rm /home/m1/pa
rm /home/m1/td
rm /home/m1/rpl

sleep 2

echo $INDIVIDUAL_POWERLIMIT_0 > '/home/m1/p0'
echo $INDIVIDUAL_POWERLIMIT_1 > '/home/m1/p1'
echo $INDIVIDUAL_POWERLIMIT_2 > '/home/m1/p2'
echo $INDIVIDUAL_POWERLIMIT_3 > '/home/m1/p3'
echo $INDIVIDUAL_POWERLIMIT_4 > '/home/m1/p4'
echo $INDIVIDUAL_POWERLIMIT_5 > '/home/m1/p5'
echo $INDIVIDUAL_POWERLIMIT_6 > '/home/m1/p6'
echo $INDIVIDUAL_POWERLIMIT_7 > '/home/m1/p7'
echo $INDIVIDUAL_POWERLIMIT_8 > '/home/m1/p8'
echo $INDIVIDUAL_POWERLIMIT_9 > '/home/m1/p9'
echo $INDIVIDUAL_POWERLIMIT_10 > '/home/m1/p10'
echo $INDIVIDUAL_POWERLIMIT_11 > '/home/m1/p11'
echo $INDIVIDUAL_POWERLIMIT_12 > '/home/m1/p12'
echo $INDIVIDUAL_POWERLIMIT_13 > '/home/m1/p13'

echo $TARGET_TEMP_0 > '/home/m1/t0'
echo $TARGET_TEMP_1 > '/home/m1/t1'
echo $TARGET_TEMP_2 > '/home/m1/t2'
echo $TARGET_TEMP_3 > '/home/m1/t3'
echo $TARGET_TEMP_4 > '/home/m1/t4'
echo $TARGET_TEMP_5 > '/home/m1/t5'
echo $TARGET_TEMP_6 > '/home/m1/t6'
echo $TARGET_TEMP_7 > '/home/m1/t7'
echo $TARGET_TEMP_8 > '/home/m1/t8'
echo $TARGET_TEMP_9 > '/home/m1/t9'
echo $TARGET_TEMP_10 > '/home/m1/t10'
echo $TARGET_TEMP_11 > '/home/m1/t11'
echo $TARGET_TEMP_12 > '/home/m1/t12'
echo $TARGET_TEMP_13 > '/home/m1/t13'

echo $__FAN_ADJUST > '/home/m1/fa'
echo $POWER_ADJUST > '/home/m1/pa'
echo $ALLOWED_TEMP_DIFF > '/home/m1/td'
echo $RESTORE_POWER_LIMIT > '/home/m1/rpl'
echo ""
echo "LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL "

HCD='/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL'
running=$(ps -ef | awk '$NF~"Maxximus007_AUTO_TEMPERATURE_CONTROL" {print $2}')
if [ "$running" == "" ]
then
EXPORT DISPLAY=:0

if [ $LOCALorREMOTE == "LOCAL" ]
then
guake -n $HCD -r Maxximus007_AUTO_TEMPERATURE_CONTROL -e "bash /home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL"
  echo ""
  echo "process in guake terminal (f12)"
  echo ""
fi

if [ $LOCALorREMOTE == "REMOTE" ]
then
screen -dmS autotemp $HCD
  echo ""
  echo "process in screen autotemp; attach with: screen -r autotemp"
  echo ""
fi

running=""
fi
fi

it should implement this change (but I haven't tested it)

Ok I added export DISPLAY=:0 to fist line of bash and now the script goes further.
But still I am getting the error I have posted below and no additional screens are starting.
Also I just discovered that the switch IAmNotAJeep_and_Maxximus007_WATCHDOG="YES" doesn't do anything! There is no code to go with the switch.
I will try to edit bash and stick it in there. I must be the only person using SSH lol. Why am I the only one finding all these issues?

Also we need discuss the new way to launch the miner using SSH and 2unix and 1bash. The way it's set up now is you use Putty or whatever and SSH to server. Then WITHOUT using a screen you execute " bash '/home/m1/2unix' ". Then what happens is the terminal displays some stuff and just stops when the bash launches the miner. So now you are left with a terminal screen that is just stopped and a miner screen you can't get to. The only way to get to it is terminate the terminal, re-log in and screen -r OR CTRL-c the current terminal screen and then screen -r. I am a Linux noob but seems to me there should be a better way. version 17 was simpler IMO. Open terminal, create a screen and execute bash. I think your doing it this way to automate a screen and miner in the case of a power up or reboot.

So in summary -

A: Watchdog not launching as code is missing
B: Errors on launch trying to execute something it can't find (BTW miner still launches and works in spite of error)
C: No idea if temp control working because I still can't get it to execute it's own screen
D: Funky startup procedure for SSH users

I love your work and really appreciate it. These are not criticisms, just notes to try to help...

dos2unix: converting file /home/m1/1bash to Unix format ...


workername: nv136


rig IP: 10.0.0.136


03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
22:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
23:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)


Tue Jul 18 09:47:50 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.47                 Driver Version: 384.47                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:03:00.0  On |                  N/A |
| 79%   58C    P8    12W / 125W |     94MiB /  3012MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    Off  | 00000000:04:00.0 Off |                  N/A |
| 54%   61C    P8    10W / 125W |     10MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:22:00.0 Off |                  N/A |
| 56%   57C    P8    13W / 125W |      2MiB /  3013MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:23:00.0 Off |                  N/A |
| 57%   59C    P8    14W / 125W |      2MiB /  3013MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1293    G   /usr/lib/xorg/Xorg                              69MiB |
|    0      1925    G   compiz                                          21MiB |
|    1      1293    G   /usr/lib/xorg/Xorg                               7MiB |
+-----------------------------------------------------------------------------+


ENVIRONMENTAL VARIBLES SET


Tue Jul 18 09:47:50 EDT 2017
Action: Removing ...
systemctl stop teamviewerd.service
Failed to stop teamviewerd.service: Unit teamviewerd.service not loaded.
fail

kill '/opt/teamviewer/tv_bin/script/teamviewer' - root (/home/m1/.local/share/teamviewer12 / /home/m1/.local/share/teamviewer12)



Failed to execute operation: No such file or directory
try again, full path...
Failed to execute operation: Invalid argument


LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL

  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value
  1000.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:1]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:1]) assigned value
  1000.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:0]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:1]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:2]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:3]) assigned value 2.


Pages: « 1 ... 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 146 147 148 ... 416 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!