Mining ZEL in Hashr8 OS – A tour with SavageMine!

Hi everyone,

Last night SavageMine did a live stream video mining ZEL using miniZ!

Sorry that we weren’t there at the time! Nevertheless, we would like to share some hints that may help you understand some of the issues that occurred during the video.

First of all, thanks a lot to SavageMine for the nice words about miniZ project!
Great that he managed to give it a try! It is also good to know that miniZ is running OK in Hashr8 OS.
You can check how miniZ performs for ZEL here, and do not miss the 2nd Table with our ECO settings for a test on efficiency!

Now let’s get into it:

  • Regarding --nonvml, it is annoying that it is set by default. We are considering adding an argument to override it. 😉 However, the best is to find a way to remove it from the command line when using the Hashr8 OS interface.
  • In the video, SavageMine tried to run miniZ from a console session. This is fine, but first it is good to check if the miner is already running from the Hashr8 OS interface. You can check it by running in the console the following: 
    ps xua|grep miniZ

    Note that the first time it ended up running two miner instances, hence the drop in hashrate for each instance. (It shouldn’t be necessary to reboot the rig.)

  • If you noticed, when miniZ was started in the console there was warning message indicating that the Telemetry port was already in use (miniZ was already running from Hashr8 OS), and a bit below you can read Telemetry [http://localhost:5502], so you would be able to find Telemetry for that instance in port 5502.
    When this message appears (valid for other OSs) it is good to check that the miner isn’t already running. You can still get to Telemetry but it moved to the next available port (add 1, 2… to port number).
  • One more thing, miniZ includes a command line argument for tunning performance when overclocking your GPUs. When you’re choosing your power limit and OCs, you can use --oc1 or --oc2 to adjust miniZ to your settings. Note that when you add --oc1 or --oc2 to your command line this is applied to all GPUs. You can also apply the setting to a specific GPU. In FAQ page you can find detailed information about usage and availability (see Table) of this option per GPU and algorithm.

Finally, you may want to take a closer look to other features in Telemetry, SavageMine didn’t get to the nice plots, both for the rig and per GPU. You need to click on device name to get to the GPU plots page (or Total). If you’re into playing with data and doing your own statistics you should definitely consider adding --csv [filename] to your command line. This will create a file with data separated by commas that you can easily import into R or into a spreadsheet.

Hope this helps! Feel free to leave a comment below if you need further information/help!

Cheers everyone and happy mining!

Follow us
On Twitter
Our thread on bitcointalk.org