Hiveon. №1 OS for mining

[TiasJ]

phoenixminer exited..  waiting to cooldown a bit

any ideas where to look at ? i cant run hiveos properly this time.

using latest update

thanks

Check miner log for exact error.

how do i pullup miner log of phoenixminer on hiveos?

thanks

A few ways to go about this;

The easiest way is from your worker overview dashboard, top left corner you should see your username and numerous icons.
One of those icons is a pickaxe, you can click on it and bring up logs, config, stop and restart the miner from there.
Do note that there is a slight delay in what the miner log picks up from there and what is actually seen in the miner window (ssh'ing in, miner)

You can enable miner specific logs with the following extra parameters and pull it from the miner directory (little more complicated if you don't know your way around linux)

Code:

-log <n> Selects the log file mode:
     0: disabled - no log file will be written
     1: write log file but don't show debug messages on screen (default)
     2: write log file and show debug messages on screen
-logfile <name> Set the name of the logfile. If you place an asterisk (*) in the logfile name, it will be
      replaced by the current date/time to create a unique name every time PhoenixMiner is started. If there
      is no asterisk in the logfile name, the new log entries will be added to end of the same file. If you
      want to use the same logfile but the contents to be overwritten every time when you start the miner,
      put a dollar sign ($) character in the logfile name (e.g. -logfile my_log.txt$).
-logdir <path> Set a path where the logfile(s) will be created
-logsmaxsize <n> Maximum size of the logfiles in MB. The default is 200 MB (use 0 to turn off the limitation).
      On startup, if the logfiles are larger than the specified limit, the oldest are deleted. If you use a
      single logfile (by using -logfile), then it is truncated if it is bigger than the limit and a new one
      is created.

[jdash]

^ thanks! ill check it, and post it if i find it hard to understand 

[dimafern]

0.6-43@190521
*   hive-replace: fixed md5 checksum check
*   fixed time synchronization
*   minor changes in AMD OC
*   WildRig-Multi v0.16.5 (better stability for wildkeccak using --scratchpad-safe-update on some systems, small improvements x16-like algo and honeycomb)
*   Nanominer v1.3.1 (fixed cn-r runtime compilation issue on some AMD devices)
*   cpuminer-opt v3.9.0 (added lyra2rev3/yespower/yespowerr16/phi2)
*   T-Rex v0.11.0 (added x25x algo, bug fixes with built-in watchdog)
*   Gminer v1.43 (added support for mining mining V-Dimension, added support AE for NiceHash)
*   NEW teominer v0.16.3 (ethminer fork)

0.6-43@190521-2
*   Nanominer v1.3.2 (fixed hanging while enumerating AMD devices on some systems)

[Johny101010]

0.6-43@190521
*   hive-replace: fixed md5 checksum check
*   fixed time synchronization
*   minor changes in AMD OC
*   WildRig-Multi v0.16.5 (better stability for wildkeccak using --scratchpad-safe-update on some systems, small improvements x16-like algo and honeycomb)
*   Nanominer v1.3.1 (fixed cn-r runtime compilation issue on some AMD devices)
*   cpuminer-opt v3.9.0 (added lyra2rev3/yespower/yespowerr16/phi2)
*   T-Rex v0.11.0 (added x25x algo, bug fixes with built-in watchdog)
*   Gminer v1.43 (added support for mining mining V-Dimension, added support AE for NiceHash)
*   NEW teominer v0.16.3 (ethminer fork)

0.6-43@190521-2
*   Nanominer v1.3.2 (fixed hanging while enumerating AMD devices on some systems)

SMos says that they have a tool to bump mining on RX cards by 1-5 %. Is that something that can be added to hive os also? Always with tytanic or devs permission

[dimafern]

0.6-44@190522
*   updated `amdmemtweak` v0.1.8.1
*   fixed teominer for AMD platform

[ThePunisher49X]

Are you guys going to update the claymore 11.9 your OS is using to 14.5 so we can use the rxboost command instead of doing the amd memory tweak?
Can it be done on the fly or do we need to redownload the image with the updated release to have claymore updated?

[TiasJ]

Are you guys going to update the claymore 11.9 your OS is using to 14.5 so we can use the rxboost command instead of doing the amd memory tweak?
Can it be done on the fly or do we need to redownload the image with the updated release to have claymore updated?

The Claymore version available on hive is 12.0, which is the latest version on Linux.
Claymore 14.5 is Windows only.

[Volodka_007]

Hi, i have probleme whis some rigs, Errors “*ERROR* UVD not responding, trying to reset the VCPU!!!”
@
[drm:vce_v4_2_set powergating_state [amdgpu]] ERROR VCE not responding, trying to reset the ECPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
 ERROR UVD not responding, trying to reset the VCPU!!!
[drm:vce_v4_2_set powergating_state [amdgpu]] ERROR VCE not responding, giving up!!!


Kernel panic - not syncing: Timeout Not all CPUs entered broadcast exception handler
Shutting down cpus with NMI
Rebooting in 30 seconds
@

rigs whis r9 390 in windows they works perfect,
If you turn off and on the rig 5-7 times, everything starts without errors and works until it is rebooted or shut down.

[jdash]

phoenixminer exited, waiting to cooldown a bit

Phoenix Miner 4.2c Linux/gcc - Release build
--------------------------------------------

CUDA version: 9.0, CUDA runtime: 8.0
OpenCL driver version: 17.50-511655
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2527.3)
Available GPUs for mining:
GPU1: P106-100 (pcie 1), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU2: P106-100 (pcie 3), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU3: P106-100 (pcie 4), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
/hive/miners/phoenixminer/h-run.sh: line 23: 17457 Segmentation fault      ./PhoenixMiner

phoenixminer exited, waiting to cooldown a bit



is this the correct miner log? can't seem to find more details on it. how do i correct it?

thanks

[dimafern]

0.6-45@190525
*   added support of RXboost feature (fine tuning memory timings for AMD Polaris cards)
*   Gminer v1.44 (improved GPU utilization for high-end GPUs on VOLLAR)
*   WildRig-Multi v0.17.0 (added x25x, re-tuned auto-parameters to maximize hashrate)
*   GrinPro v2.2 (fixed AMD compatibility)

[dimafern]

WEB INTERFACE UPDATE 25 May 2019
- Added support of RX boost feature
- New ASIC options for startup
- Detailed activity log for “config applied” event
- Improved pagination support on workers page

Detailed information about the changes, see here. Video about RX boost feature implementation see here.

[dimafern]

0.6-46@190527
*   Claymore's Dual ETH v14.6 (first v14.x series Linux build, options -rxboost and -strap not working in Linux build)
*   CryptoDredge v0.20.0 (improved MTP algo, improved argon2d algo, new argon2d-nim algo)
*   WildRig-Multi v0.17.2 (fixed support x22i and x25x algos, re-tuned auto parameters for Baffin)
*   ccminer-enemy v2.0 (known as z-enemy miner)
*   NEW ccminer-rfv2 v1.0.2 (ccminer fork for Rainforest v2)

[TiasJ]

phoenixminer exited, waiting to cooldown a bit

Phoenix Miner 4.2c Linux/gcc - Release build
--------------------------------------------

CUDA version: 9.0, CUDA runtime: 8.0
OpenCL driver version: 17.50-511655
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2527.3)
Available GPUs for mining:
GPU1: P106-100 (pcie 1), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU2: P106-100 (pcie 3), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU3: P106-100 (pcie 4), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
/hive/miners/phoenixminer/h-run.sh: line 23: 17457 Segmentation fault      ./PhoenixMiner

phoenixminer exited, waiting to cooldown a bit



is this the correct miner log? can't seem to find more details on it. how do i correct it?

thanks

What driver version are you currently running?

[dimafern]

0.6-46@190528
*   Claymore's Dual ETH v14.6.1 (fixed hashrate drops on Nvidia cards vs v12.0)

[jdash]

phoenixminer exited, waiting to cooldown a bit

Phoenix Miner 4.2c Linux/gcc - Release build
--------------------------------------------

CUDA version: 9.0, CUDA runtime: 8.0
OpenCL driver version: 17.50-511655
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2527.3)
Available GPUs for mining:
GPU1: P106-100 (pcie 1), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU2: P106-100 (pcie 3), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU3: P106-100 (pcie 4), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
/hive/miners/phoenixminer/h-run.sh: line 23: 17457 Segmentation fault      ./PhoenixMiner

phoenixminer exited, waiting to cooldown a bit



is this the correct miner log? can't seem to find more details on it. how do i correct it?

thanks

What driver version are you currently running?

4.13.16-hiveosKernel Version
N390.48
P106-100 × 3

is it correct driver for p106?

[TiasJ]

phoenixminer exited, waiting to cooldown a bit

Phoenix Miner 4.2c Linux/gcc - Release build
--------------------------------------------

CUDA version: 9.0, CUDA runtime: 8.0
OpenCL driver version: 17.50-511655
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2527.3)
Available GPUs for mining:
GPU1: P106-100 (pcie 1), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU2: P106-100 (pcie 3), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
GPU3: P106-100 (pcie 4), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
/hive/miners/phoenixminer/h-run.sh: line 23: 17457 Segmentation fault      ./PhoenixMiner

phoenixminer exited, waiting to cooldown a bit



is this the correct miner log? can't seem to find more details on it. how do i correct it?

thanks

What driver version are you currently running?

4.13.16-hiveosKernel Version
N390.48
P106-100 × 3

is it correct driver for p106?

Cuda 9.2 and up are now the default on most miners.
You'll need at least 396.54, which is recommended on 0.6-01 (and above).

Start a Hive Shell session
Run the following commands;

Code:

disk-expand
logs-on
reboot

Note that logs should be turned back off after this procedure if you're running hive off a USB stick

Once you reboot start a Hive Shell session again.
Run the following;

Code:

systemctl stop hivex
miner stop
apt update
nvidia-driver-update

The installation could take up to around 10 minutes on SSD (depending on your internet connection speed) and takes longer on USB stick.
Reboot the machine again once done.

On some systems, OC and FAN settings may fail after a driver upgrade. This can easily be fixed.

Start a Hive Shell session
Run the following;

Code:

systemctl stop hivex
miner stop
apt-get install --reinstall -y nvidia-settings
reboot

All should be working again.

Let me know how it goes!

[dimafern]

Check out our new article

"Wallets Balances"

The article focuses on the following:

• Setting the display of public blockchain balances
• Setting the display of balance on pools
• Setting the display of the balance on exchanges
• Setting the balance display NiceHash

We invite you to discuss the expansion in functionality and suggest your favorite pools and exchanges!

[2h4u]

Cuda 9.2 and up are now the default on most miners.
You'll need at least 396.54, which is recommended on 0.6-01 (and above).

Start a Hive Shell session
Run the following commands;

Code:

disk-expand
logs-on
reboot

Note that logs should be turned back off after this procedure if you're running hive off a USB stick

Once you reboot start a Hive Shell session again.
Run the following;

Code:

systemctl stop hivex
miner stop
apt update
nvidia-driver-update

The installation could take up to around 10 minutes on SSD (depending on your internet connection speed) and takes longer on USB stick.
Reboot the machine again once done.

On some systems, OC and FAN settings may fail after a driver upgrade. This can easily be fixed.

Start a Hive Shell session
Run the following;

Code:

systemctl stop hivex
miner stop
apt-get install --reinstall -y nvidia-settings
reboot

All should be working again.

Let me know how it goes!

Actually, just one command

Code:

nvidia-driver-update

is pretty sufficient. Goes brilliant on recent Hives like 06-4x.

[TiasJ]

Cuda 9.2 and up are now the default on most miners.
You'll need at least 396.54, which is recommended on 0.6-01 (and above).

Start a Hive Shell session
Run the following commands;

Code:

disk-expand
logs-on
reboot

Note that logs should be turned back off after this procedure if you're running hive off a USB stick

Once you reboot start a Hive Shell session again.
Run the following;

Code:

systemctl stop hivex
miner stop
apt update
nvidia-driver-update

The installation could take up to around 10 minutes on SSD (depending on your internet connection speed) and takes longer on USB stick.
Reboot the machine again once done.

On some systems, OC and FAN settings may fail after a driver upgrade. This can easily be fixed.

Start a Hive Shell session
Run the following;

Code:

systemctl stop hivex
miner stop
apt-get install --reinstall -y nvidia-settings
reboot

All should be working again.

Let me know how it goes!

Actually, just one command

Code:

nvidia-driver-update

is pretty sufficient. Goes brilliant on recent Hives like 06-4x.

Yes, in most cases just running the

Code:

nvidia-driver-update

is enough, but the above steps ensure chances of things going wrong are kept to an absolute minimum. Especially in cases where individuals come from older builds.

[crazydane]

If I use Awesome Miner as my primary controller and install the Remote Agent on my Hive OS rigs, do I still need to "register" the rigs in the "Hive cloud", or can I get by with just entering a rig name and password in the init.conf file and never bother managing the rig(s) from the Hive web based service?

I realize that going this route, I won't be able to update the Hive OS version on each rig as new releases come out, but since Awesome Miner takes care of keeping the mining software updated, this is less of an issue I would think.  So whenever a new Hive OS image comes out, that would be when I would update the rigs and of course I can run the nvidia-driver-update command as explained in the previous post to keep the video drivers current.

Thoughts?