Quote from: BeefyBitcoinBoy on July 20, 2020, 08:55:28 AM

Quote from: PhoenixMiner on July 20, 2020, 06:28:34 AM

Quote from: BeefyBitcoinBoy on July 19, 2020, 10:23:54 PM

Just reporting an issue I ran into on v5.1b with mixed-gen ETH mining on one XFX RX 5700 8GB + one XFX RX 480 8GB + one MSI RX 480 8GB on Ubuntu 20.04 (via both minerstatOS v1.5 and v1.6). When I upgraded from PhoenixMiner v5.0e to v5.1b, I saw my RX 5700 hashrate drop to about 58% of normal, and the two RX 480s dropped to about 67% of normal hashrate. Whether related to the miner or the OS, I cannot say, but I also saw the GPU memory clocks intermittently bouncing back to stock settings for 20 seconds at a time instead of locking in at my normal overclocks, and I would hear the fans adjust their throttles each time the clocks adjusted.

Rolling back to v5.0e followed by a reboot seems to have resolved these issues. I have happily used a few versions of the PhoenixMiner for about four months on this mixed-gen rig without issue, so this was a bit of a surprise. Unfortunately, my normal log file didn't have any suspicious messages or errors to report.

This could be related to the OS and driver versions. We haven't tested on Ubuntu 20.04 yet (our Linux test rigs use Ubuntu 16.x and Ubuntu 18.x) and it is possible that the new AMD pro drivers for 20.04 are different that these for 18.04 (this is certainly true for 20.20-1098277, which is released only for 20.04 and is not supported by PhoenixMiner yet). We are going to build some rigs with 20.04 soon but this will only be reflected in the next release of PhoenixMiner.

Wow, thanks very much for the reply, @PhoenixMiner. For clarification, this also occurred under Ubuntu 18.04.3 LTS (bionic). The 18.04.3 build is on amdgpu-pro 19.50-967956 drivers. For both builds (Ubuntu 18.04.3 and Ubuntu 20.04), rolling back to PhoenixMiner v5.0e resolved the issue. Thanks very much for the heads-up that Ubuntu 20.04 is not supported, yet! I'll keep investigating and let you know if I find anything else that might be useful.

Hey, there, PhoenixMiner - just wanted to report that I am still seeing this behavior for 5.1c, as well (on Ubuntu 18.04.3 / amdgpu-pro 19.50-967956). Rolling back to v5.0e still fixes the issue.