Quote from: mrplow on April 19, 2019, 04:27:58 AM

Hi, thank you very much for this great program. Last night I uninstalled amdgpu-pro then upgraded from Ubuntu 16.04 to 18.04. I then install amdgpu-pro 18.40-697810 with the --opencl=legacy command line option.

I'm now getting the 'Unknown OpenCL driver version' message while running phoenix in dual mode, eth and blake2s.

If I run it with -clKernel 0 I can mine eth but then no dual support.

Sorry if I'm missing something obvious but the search for this forum leaves much to be desired.

Code:

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

No CUDA driver found
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2686.5)
Available GPUs for mining:
GPU1: AMD Radeon (TM) R9 Fury Series (pcie 1), OpenCL 1.2, 4 GB VRAM, 64 CUs
Eth: Loading pools from epools.txt
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: eth-us-west1.nanopool.org:9999
Dual: Loading pools from dpools.txt
B2S: the pool list contains 1 pool (1 from command-line)
B2S: primary pool: blake2s.usa.nicehash.com:3361
Starting GPU mining
Eth: Connecting to ethash pool eth-us-west1.nanopool.org:9999 (proto: EthProxy)
B2S: Connecting to blake2s pool blake2s.usa.nicehash.com:3361 (proto: Stratum)
B2S: Connected to blake2s pool blake2s.usa.nicehash.com:3361 (172.65.194.244)
Eth: Connected to ethash pool eth-us-west1.nanopool.org:9999 (66.42.105.146)
B2S: Subscribed to blake2s pool
B2S: Worker [redacted] authorized
B2S: New job #[redacted] from blake2s.usa.nicehash.com:3361; diff: 137.4GH
Listening for CDM remote manager at port 3333 in read-only mode
GPU1: 30C 14%
Eth: New job #[redacted] from eth-us-west1.nanopool.org:9999; diff: 10000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #253
Light cache generated in 2.5 s (19.2 MB/s)
GPU1: Allocating DAG (2.99) GB; good for epoch up to #255
GPU1: Generating DAG for epoch #253
GPU1: DAG 17%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
B2S speed: 0.000 MH/s, shares: 0/0/0
GPU1: DAG 34%
GPU1: DAG 50%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
B2S speed: 0.000 MH/s, shares: 0/0/0
GPU1: DAG 67%
GPU1: DAG 84%
GPU1: DAG 100%
GPU1: DAG generated in 10.5 s (290.4 MB/s)
GPU1: Failed to prepare kernels: clCreateKernel (-46)
Thread(s) not responding. Restarting.

The current version of PhoenixMiner 4.2c supports AMD Linux drivers up to 18.40-676022 (your driver is the next one and is not supported by the released version). You need to uninstall amdgpu-pro and then download and install the 18.40-676022 drivers. We will add support for all newer drivers in the next release of PhoenixMiner but obviously nothing stops AMD from releasing newer drivers after that and therefore we recommend to avoid upgrading to drivers that are newer than the version of the PhoenixMiner you are using.

Quote from: allur on April 19, 2019, 08:17:50 AM

It is a fast miner, but has unpleasant issue: if during mining you loose internet connection - phoenix continues to mine! Shows "disconnected from pool", but gpus are loaded, and rig consumes power with no result. No good..
Tried ver.3.5 and new 4.2 - the same problem.
Claymore in same situation stops mining and release gpu load, so electricity not wasted.

Give it 3-4 minutes and it will stop mining. We don't immediately stop mining to avoid crashing if the connection is soon restored.

Quote from: tipo70 on April 19, 2019, 08:30:58 AM

Tonight, stopped mining on RX 550 2 gb.

Code:

2019.04.19:11:22:10.878: main Eth: Mining MOAC on >moac.2miners.com:5050 for 0:00
2019.04.19:11:22:10.878: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.04.19:11:22:10.878: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.04.19:11:22:10.878: main Eth: Average speed (5 min): 0.000 MH/s
2019.04.19:11:22:10.878: main
2019.04.19:11:22:21.724: main GPU1: 34C 39%, GPU2: 34C 39%, GPU3: 37C 39%, GPU4: 37C 39%, GPU5: 40C 39%, GPU6: 40C 24%, GPU7: 46C 33%, GPU8: 52C 35%, GPU9: 49C 34%, GPU10: 40C 24%, GPU11: 42C 16%, GPU12: 31C 30%
2019.04.19:11:22:26.811: unkn Eth: Connecting to ethash pool moac.2miners.com:5050 (proto: EthProxy)
2019.04.19:11:22:26.889: eths Eth: Connected to ethash pool moac.2miners.com:5050 (54.36.109.4)
2019.04.19:11:22:26.889: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":[""]}

2019.04.19:11:22:26.969: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2019.04.19:11:22:26.969: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.04.19:11:22:27.051: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":
2019.04.19:11:22:27.051: eths Eth: New job #e9614ac8 from moac.2miners.com:5050; diff: 8600MH
2019.04.19:11:22:27.051: eths GPU1: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU2: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU3: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU4: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU5: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU6: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU7: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU8: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU9: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU10: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU11: not enough VRAM for DAG epoch 77
2019.04.19:11:22:27.051: eths GPU12: not enough VRAM for DAG epoch 77

Add the following options: -rvram -1 -eres 0 This will stop the check for minimum free VRAM and will not allocate bigger DAG buffer than necessary for the future DAG epochs.

Quote from: dierickxalexandre@gmail.c on April 19, 2019, 05:07:33 PM

hello whats the arguments to add the flag nvidia to the GPU1 and amd to the rest?

It's not quite clear what you are trying to achieve. If you are referring to the -nvXXX and -clXXX flags, they are only applied to the respective types of GPUs. If you want the same value for all AMD GPUs, just use a single value like: -clkernel 2 which will set this for all AMD GPUs and won't affect the Nvidia GPUs at all. If want to achieve something else, please let us know to give more clear answer.