Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

6
How to fine-tune Xmr-Stak on HiveOS
Post Body

In this article I would like to give some tips and maybe help ones who are struggling with linux-like systems, and will use most popular - HiveOS as an example.

Most actions are done using console, so an unexperienced in terminal (console) systems users might be confused on how to do anything there.

If you have experience and know basic linux commands, then most likely you will know everything written here.

So lets use few scenarios from easier to more hard ones, about checking and tuning something with our cards in xmr-stak and some info about OC

To use console in Hiveos - press "hive shell start" button and then press popped up arrow button next to this command on frontend.

1. We need to learn what clocks our gpu runs at

Sometimes you need to learn actual core clocks and mem clocks that your gpu is running. This is helpful to understand if you're hitting tdp limit and clocks are not growing or in other cases

- Log into Hive-console

- type nvidia-info for nvidia cards or amd-info for amd cards and press enter

if you want to clear this info and run again - use clear command and press enter

2. We need to disable some card from mining (temporarily turn it off in miner)

e.g we have a system with 2 nvidia cards and we want to disable first card in it.

- First we need to run xmr-stak on all cards and open console in Hive and go to xmr-stak miner directory to see contents of generated nvidia.txt file (just like we would do on windows). Run command:

cd / & cd /hive/miners/xmr-stak/fireice-uk/2.10.8/***(if your version varies - type in the end of command your version)***

- type nano nvidia.txt this will open config file for nvidia and screenshot and write down threads and intensity and blocksize config params for cards you wish to keep on (or screenshot it) and then close console.

- Navigate to your flight sheet, press 3-dot button to edit it and then press in the right part next to xmr-stak miner name "Setup Miner Config".

- In the opened page you will see several fields. One of them is "Nvidia config override" and "Amd config override" and press on i button next to nvidia-config-override field and in opened popup press on gpu_threads text block to paste sample in the field.

https://preview.redd.it/hkv6ppbdw1091.jpg?width=855&format=pjpg&auto=webp&s=4f34e886907172266a3835ed16d80f859b354cda

- remove section with 0 index (0 is the first gpu, 1 is the second in rig etc) and write intensity, blocks and threads for the remaining you want to run from your saved data.

"gpu_threads_conf" : [

{ "index" : 0, "threads" : 4, "blocks" : 48,

"bfactor" : 2, "bsleep" : 0, "affine_to_cpu" : false, "sync_mode" : 3, "mem_mode" : 1, },

{ "index" : 1, "threads" : 4, "blocks" : 48,

"bfactor" : 2, "bsleep" : 0, "affine_to_cpu" : false, "sync_mode" : 3, "mem_mode" : 1, },

],

should turn into:

"gpu_threads_conf" : [

{ "index" : 1, "threads" : 8, "blocks" : 132,

"bfactor" : 2, "bsleep" : 0, "affine_to_cpu" : false, "sync_mode" : 3, "mem_mode" : 1, },

],

- press "apply changes"

- press "update" and confirm restarting miners ("all workers") on farm that uses this flight sheet.

p.s What intensities and threads to use? Check this doc to see some references

Have more questions about xmr-stak tuning in HiveOS? Join our telegram and request help or write here in comments

Author
Account Strength
90%
Account Age
6 years
Verified Email
Yes
Verified Flair
No
Total Karma
2,798
Link Karma
2,560
Comment Karma
n/a
Profile updated: 1 week ago
Posts updated: 10 months ago
Xmr-Stak Support

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
2 years ago