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

whats the output of
are you mining with remote setting or local ?
are you using upPaste?

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

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 ?!

Got it working!

Only thing left is 12th gpu? Anybody any clue?
I checked at connections, all gpu are spinning

If u want to see watchdog running open a new terminal and type "screen -x wdog"

Hi, i just upgraded from 0018 to 0019 and my 1060 3g with same settings (cc100, mc800, pl75, Dual ETH_SC, dcri 40) shows 3-2 Mh less in 0019 then 0018. What is wrong, may be some additional settings?

Thanks! Shows it indeed.
However can t seem to open watchdog!

I just noticed ssh and remote on in my 1bash.

This is probably why it not showing on local screen?

Plus it only show 11 gpu in terminal? 0-10 . All my gpu fans are spinning though.

I have settings for pastebin update. Only ssh needed then and put remote to local?

https://imgur.com/oiS3RFK

how come my watt is so high i have max 80watt :^p

Tried this?

Go to Guake (you seem already have Guake opened from your screenshots)

Type this in a fresh tab


It should show you the mining process, it should've opened watch dog (given you set this flag to YES in 1bash)

You can run watchdog on its own independent from 1bash by typing 'bash I' then press tab and if it shows whole name of the script (gives you are in home/m1 directory), press enter, it would start watchdog.

Let me know if this has worked for you.

Hi, 'm no linux expert.. my rig seems to be mining but it doesn't open in terminal.

It's a clean install nvoss v19 .

Biostar TB250 BTC pro mobo with 12X GTX1070



http://imgur.com/a/oQBBc
https://i.imgur.com/CuJxZmH.jpg
https://i.imgur.com/WJRpKo7.jpg

I really need to see hashrate and watchdog etc

Setting target temp does not affect Maxximus

6_autotemplog :

1bash :

Edit 1 :
Only read from individual target temps even if it set to NO

Changing individual changes it :

1bash :

Edit 2 :
Acting strange, it reads all targets from  TARGET_TEMP_0=76
More tests :

1bash :


==> 6_autotemplog <==

Edit 3
Individual target temp works as it should
1bash:

==> 6_autotemplog <==

Can any one else test and clarify this please.

I finally got around to upgrading to v19 from v17.  I'd had some trouble with v18 and went back to v17, but v19's being much better behaved.  I put my config in (configured to use my MiningPoolHub switcher and Maxximus007's fan-control code) and let her rip.

There is one issue I ran across: no Cryptonight miner.  I noticed it when my mining rig's fans all slowed down.  To get things running again in a hurry, I copied the mining software from my v17 setup.  It's in this tarball:

https://alfter.us/wp/wp-content/uploads/2017/09/KTccminer-cryptonight.tar.xz

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.

Beyond that, the only other changes I made were to set the hostname equal to the worker name (changes in /etc/hostname and /etc/hosts), change the timezone from Eastern to Pacific, and to revise the speed and power figures in the mph_conf.json heredoc with my current configuration (up from 3 GPUs to 4).  As I write this, I'm imaging my v19 setup so I can copy it over to the (physically smaller) stick with v17.

To clear logs you dont want to keep enable the clear log file at reboot in 1bash
Then add your file address to "Clear_Logs" file

"Best" risers seller dont exist
Better to do is always buy more them you need in case u get one defunct !
I dont know all about this ebay seller, i buy mine on https://www.cryptomined.com/ a bit expensive people will say, but no one have fail actually.

Incidentally, what are the "best" risers out there - both from a type and seller standpoint? With so much that can go wrong in a 13 GPU setup, anything to minimize failure would be great.

try
> filename
Set bash file to clear log

oops VoskCoin, didn't see the nicehash equihash request sorry; please see this:

Add coin


Add coin details; make sure you have your BTC address and you can add us equihash pool as well; 'equihash.usa.nicehash.com:3357'


Add this in 3main at right place:


You are welcome, hope it works

I'll check the v0019 telegram daemon as soon as I manage to uncompress v0019 following your suggestion, wich I think was what I did to uncompress v0018. Thx

Try adding a "L" to the screen args like this:


That's what a I do. Then a file called "screenlog.0" will be created. Keep in main that this file grows constantly, so eventually you will have to do some thing about it.
To watch the output in real time: tail -f /path to screenlog.0

Thanks I just used Raw Copy to copy one of my other rigs with V0018 and gave up on V0019.

Making some more changes to my telegram
This is how it looks now :

Well, I was using etcher (Win7) for making v0019 image
and it works just fine