Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 172. (Read 835838 times)

1. Move config.txt and nvidia.txt files to persistent storage (e.g. /home/miner) from /var/tmp/miner/xmr-stak-xxxxxxx/
2. Change verbose level from 3 to 4 in config.txt - " "verbose_level" : 4, "
3. Edit your group in smos web interface - add "--config /home/miner/config.txt --nvidia /home/miner/nvidia.txt" to miner parameters
4. Reboot rig

When you are SSH into the miner and use screen -x miner
you can type c,  h, or r to get connection report, hashrate and results.

No idea if there are command line options to make the hashrate be reported continuously so you can see it in the SMOS console.

This is for 2.4.1 sorry

rejected aswell here, on nanopool no problem.

Does anyone have a idea how to display hashrate on xmr-stak-v2.4.1-cuda8?

Hi

I have  a strange problem with my Asus rx470 mining gpus. They get very unstable with modded bios (only one click timing patch applied), otherwise with stock bios they work just fine 24mhs 
I used to run EthOS before SMOS...the same problem appeared there too!

I have also other rx570 gpus (Asus and MSI)...modded them in the same way with memory and core clock changes and they perform just perfect.

Also i get this kind of error in claymore console and its appearing very often, even though mining process continues without hash loss or incorrect shares

 GPU fault detected: 147 0x09a00802
[ 5789.300803] amdgpu 0000:02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00201534
[ 5789.303516] amdgpu 0000:02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x08008002
[ 5789.304585] amdgpu 0000:02:00.0: VM fault (0x02, vmid 4) at page 2102580, read from 'TC0' (0x54433000) (
[ 5789.305681] amdgpu 0000:02:00.0: GPU fault detected: 147 0x0dd84402
[ 5789.306758] amdgpu 0000:02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001F5912
[ 5789.307814] amdgpu 0000:02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x08088002
[ 5789.308860] amdgpu 0000:02:00.0: VM fault (0x02, vmid 4) at page 2054418, read from 'TC6' (0x54433600) (136)
[ 5789.309883] amdgpu 0000:02:00.0: GPU fault detected: 147 0x04f80402
[ 5789.310900] amdgpu 0000:02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001AE74C
[ 5789.311896] amdgpu 0000:02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
[ 5789.312866] amdgpu 0000:02:00.0: VM fault (0x0c, vmid 4) at page 1763148, read from 'TC4' (0x54433400) (72)
[ 5789.313846] amdgpu 0000:02:00.0: GPU fault detected: 147 0x05e88802

This line works fine for me, have you tried without the stratus tcp stuff (don't remember if it was due to SMOS or pool if that should be there or not).

--currency monero7 -o europe.cryptonight-hub.miningpoolhub.com:17024 -u bullshituser.$rigName -p x

using, xmr-stak-v2.4.1-cuda8 and string below, I am getting

--noCPU --noAMD --currency monero7 -o stratum+tcp://cryptonightv7.USA.nicehash.com:3363 -u .$rigName -p x

[2018-04-08 20:20:52] : Pool stratum+tcp://cryptonightv7.USA.nicehash.com:3363 c
onnected. Logging in...
[2018-04-08 20:20:52] : Difficulty changed. Now: 100001.
[2018-04-08 20:20:52] : Pool logged in.
[2018-04-08 20:21:14] : Result rejected by the pool.
[2018-04-08 20:21:38] : New block detected.
[2018-04-08 20:21:44] : New block detected.
[2018-04-08 20:21:53] : New block detected.
[2018-04-08 20:22:00] : New block detected.
[2018-04-08 20:22:05] : Result rejected by the pool.
[2018-04-08 20:22:21] : New block detected.
[2018-04-08 20:22:23] : Result rejected by the pool.
[2018-04-08 20:22:29] : New block detected.
[2018-04-08 20:22:38] : New block detected.
[2018-04-08 20:22:51] : New block detected.
[2018-04-08 20:23:01] : New block detected.
[2018-04-08 20:23:32] : New block detected.

I got the same error but could remoe that by following the FAQ
https://github.com/fireice-uk/xmr-stak/blob/master/doc/FAQ.md
SSH to the rig,
sudo su
mc -c
edit the files
reboot
-->no error

But in my case the error did not make a difference, it was mining the same before and after (9x GTX 1060 3GB).

/mnt/user/config.txt

How can I export config file via ssh?

I am actually having the same problem as well.

ccminer-tpruvot-v2.2.5-cuda8.0   OR ccminer-tpruvot-v2.2.5-x16s-cuda8.0

-a neoscrypt -o stratum+tcp://neoscrypt.hk.nicehash.com:3341 -u .$rigName -p x

Neoscrypt miner for NVIDIA ?
Did you hide it somewhere ?

yes

getting this failure too: [2018-04-08 19:40:39] : MEMORY ALLOC FAILED: mmap failed

Hello, could you add this SRBMiner Cryptonight AMD GPU Miner (Cryptonight, Cryptonight Lite and Cryptonight Heavy miner)??

https://bitcointalksearch.org/topic/srbminer-cryptonight-amd-gpu-miner-v193-native-algo-switching-3167363

Anyone tried xmr-stak-v2.4.1-cuda8 with VEGAs or in multi GPU rig (AMD and NVIDIA) ?

Do you use this options?
"--noCPU --noAMD --currency monero7"

I'm pushing 67 GPU's across 8 rigs and the things that I personally think would be most helpful (in order of importance) would be:

1. Way to recall overclock settings per rig per algo.
2. Error log access via gui so if your rig does crash you can start to pinpoint the issue.
3. Adding new versions of existing miners. I know these take time to test and implement but we pay for SMOS for the ease of use and being able to update and try different miners to maximize our earnings.
4. An automated removal option of non-used miner software so that we don't have dead code sitting on our rigs. 
5. A list of best run pools to use for each coin with their respective stratum code built in. Although this may come down to personal preference it would make sense to point newbs in the right direction making it even easier for them to mine.


Just a few of my ramblings!

Hi. My suggestion would be to implement the voting system to people with x amount of rigs running. Also if it’s possiple to see what miners are people using the most and update the top 5 always. Thanks Great progress.

I suggest you change pool and not mine on nicehash and see if that works.  if it does, then something is wrong with your config or something is wrong with nicehash.

Trying to point some 1080ti and 1070 cards that way, but getting the same result here ... tried all sorts of tweaks, but no dice ...

Anyone with problems mining cryptonightv7 with nvidia? xmr-stak

Everything seems to be fine:

[2018-04-07 19:38:25] : Fast-connecting to cryptonightv7.eu.nicehash.com:3363 pool ...
[2018-04-07 19:38:25] : Pool cryptonightv7.eu.nicehash.com:3363 connected. Logging in...
[2018-04-07 19:38:25] : Difficulty changed. Now: 100001.
[2018-04-07 19:38:25] : Pool logged in.

but than:

[2018-04-07 19:38:25] : Pool logged in.
[2018-04-07 19:38:59] : Result rejected by the pool.
[2018-04-07 19:39:21] : Result rejected by the pool.
[2018-04-07 19:40:59] : New block detected.
[2018-04-07 19:41:48] : Result rejected by the pool.