PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[UserU]

I thought newbies with zero merit and less than 10 posts couldn't post links?

They are still able to embed links in texts using the URL BB code

For instance:

Code:

[url=https://google.com]This is a Google link[/url]

This is a Google link

[1715437702]

1715437702

[1715437702]

1715437702

[1715437702]

1715437702

[1715437702]

1715437702

[1715437702]

1715437702

[deedeeranged]

Wow as Im reading about all these hacks I see a post about 6.0 beta. Reported that ish. DO NOT DOWNLOAD ANY VERSIONS OF ANYTHING FROM "NEW MEMBERS"

Now that you mention about "other" downloads, what about phoenixminer.ORG? It differ's from phoenixminer.INFO?

Yes they are completely different the phoenixminer.INFO is the only one, all others I wouldn't touch with a bargepole or in other words avoid them like the plague.

[Tiggz]

Hey All, I've been using phoenix since v5.5 I just updated to 5.9 from this site and I received a security warning I've never seen. Says it has a trojan called AndroidOS/Multiverze in the miner. I have seen all the !pua and coinminer warnings for all miners, but never anything like this. I have confirmed multiple times this is in the zip. Any idea what this is or if it's concerning? Thanks!

[Lafu]

Hey All, I've been using phoenix since v5.5 I just updated to 5.9 from this site and I received a security warning I've never seen. Says it has a trojan called AndroidOS/Multiverze in the miner. I have seen all the !pua and coinminer warnings for all miners, but never anything like this. I have confirmed multiple times this is in the zip. Any idea what this is or if it's concerning? Thanks!

Do you have downloaded the files from Real download link for PhoenixMiner : https://phoenixminer.info/downloads/  ?
Or what kind of links you have used ? If you have used some download links posted from random Users lately you should change your password everywhere and scan your system.
Because if you downloaded the files from random posted Users it was Malware , if you got the files from the Original download then you should be good.

[Real-Duke]

Download only content from the first post of this thread!!
Avoid any other Post from new Members wich contain:

"Glad to see you new crypto software LHR-pill"




This Posts contain malware so please be carefull!

[Tiggz]

Hey All, I've been using phoenix since v5.5 I just updated to 5.9 from this site and I received a security warning I've never seen. Says it has a trojan called AndroidOS/Multiverze in the miner. I have seen all the !pua and coinminer warnings for all miners, but never anything like this. I have confirmed multiple times this is in the zip. Any idea what this is or if it's concerning? Thanks!

Do you have downloaded the files from Real download link for PhoenixMiner : https://phoenixminer.info/downloads/  ?
Or what kind of links you have used ? If you have used some download links posted from random Users lately you should change your password everywhere and scan your system.
Because if you downloaded the files from random posted Users it was Malware , if you got the files from the Original download then you should be good.

I got it from the first page of this forum like always. its the .info directory.

[deedeeranged]

Hey All, I've been using phoenix since v5.5 I just updated to 5.9 from this site and I received a security warning I've never seen. Says it has a trojan called AndroidOS/Multiverze in the miner. I have seen all the !pua and coinminer warnings for all miners, but never anything like this. I have confirmed multiple times this is in the zip. Any idea what this is or if it's concerning? Thanks!

Do you have downloaded the files from Real download link for PhoenixMiner : https://phoenixminer.info/downloads/  ?
Or what kind of links you have used ? If you have used some download links posted from random Users lately you should change your password everywhere and scan your system.
Because if you downloaded the files from random posted Users it was Malware , if you got the files from the Original download then you should be good.

I got it from the first page of this forum like always. its the .info directory.

Then you are good. A lot of miners are getting these warnings and I think it maybe has also something to do with LHR code being used.

[AlexanderM2]

Still not LHR Unlock??

[mrbillishere]

Hey all, got what amounts to a head's up for folks. (Not sure there's a solution...)

I have a rig running Win10 with two nVidia GPUs, one being a 3060 so I have the drivers v470.05 installed to unlock full hashrate for that GPU which is also installed in a 16-bit slot and cabled up to HDMI. The other nVidia card is a 3060 Ti (non-LHR) and this system also has a pair of AMD RX580-8GB in it. PM is in charge of all hardware control for all four cards.

Things were completely stable until yesterday and the rig was still running PM v5.7b (just due to laziness on my part - no incentive to update PM's bits, as nothing was having an issue.)

As I said, all was well - the rig was up over 600 hours non-stop until I un-paused updates and allowed the monthly cumulative updates for Windows to be installed yesterday. (I do this manually, every month.)

Now, for these two nVidia cards on that driver version, PM has lost its ability to set clock speeds for GPU and Memory. Instead, I get messages with error - 137, like this:

GPU1: Unable to reset memory clock delta - error -137
GPU3: Unable to reset memory clock delta - error -137
GPU1: Unable to set GPU clock delta to -400 MHz - error -137
GPU1: Unable to set memory clock delta to 1200 MHz - error -137
GPU3: Unable to set GPU clock delta to -200 MHz - error -137
GPU3: Unable to set memory clock delta to 1370 MHz - error -137

I can only assume that something in this month's Win10 patches is messing with stuff and it could be/probably is specific to this particular nVidia driver. One thing I did note was that for the first 20 minutes after the reboot, after patching, everything was still normal as far as mining was concerned. But 22 minutes into it, I saw this appear in the log:

2021.12.17:19:03:55.165: gps3 CUDA error in CudaProgram.cu:256 : unknown error (999)
2021.12.17:19:03:55.165: GPU3 CUDA error in CudaProgram.cu:474 : unknown error (999)
2021.12.17:19:03:55.165: GPU3 GPU3 search error: unknown error
2021.12.17:19:03:55.165: gps3 CUDA error in CudaProgram.cu:256 : unknown error (999)
2021.12.17:19:03:55.165: wdog Fatal error detected. Restarting.
2021.12.17:19:03:55.165: eths Eth: New job #7a9544e3 from ssl://us1.ethermine.org:5555; diff: 4295MH
2021.12.17:19:03:55.219: GPU1 CUDA error in CudaProgram.cu:474 : unknown error (999)
2021.12.17:19:03:55.219: GPU1 GPU1 search error: unknown error

(GPU3 is the 3060, GPU1 is the 3060Ti)


FWIW, there is no difference if I run PM v5.9d with my same config file, I get exactly the same error when PM is starting up as above, the 'unable to set/reset clocks' errors. My next action will be to look in recently-installed updates to see if there is something like a driver that was downloaded after the reboot which I might be able to uninstall.

What's truly insidious about this is the fact that if I test by using PM in benchmark mode and I employ MSI Afterburner to set core clocks/frequencies/undervolts (instead of PM) - that all still works just fine. And Afterburner is not a recent version, it's one that's a few versions behind because I prefer the one with the older UI - which shows that evidently it is still possible (for apps other than PM) to set clock deltas, post this-month's Win10 updates, and with the same version of the nVidia driver, and without said app requiring some sort of update.

OK, there you have it. Sorry about the long post. Just sharing with the class. I've been using PM for a long time and love how stable my particular (four) rigs are - or, were - up till now. BTW, none of the other rigs I have require that funky driver, in fact they're using older nVidia drivers than 470.05, and none of them are any worse for the wear after yesterday's patching. Just this funky one. Cheers.

[miner29]

Current is 497.09 for windows.  This is most likely the issue.

[mrbillishere]

Current is 497.09 for windows.  This is most likely the issue.

@miner29 - if your reply was directed towards my post, just above yours, then first off thank you for weighing in... I should add that per the nVidia control panel we're still using driver package 470.05, and per device-manager's info the timestamp on the driver file is still 2021-02-26, so I believe I've ruled out Microsoft being helpful with a GPU driver update. (Also, I looked at update history and aside from the monthly cumulative update, nothing else was applied yesterday. bummer.)

That said, I'm not averse to cleaning up the existing nVidia drivers package using DDU followed by a reinstallation of the same to see if anything changes.

In the meantime I did get t-rex going to see what it thinks. Both cards are hashing and t-rex was able to set the memory and clock speed deltas, and the clock power delta. Of course nothing's perfect - it is claiming it can't see the temps of the graphics memory so I can't specify a fanspeed range based on mem-temps. IDK if that ever worked because I've never used t-rex for ethash before and heck, I'm not sure I want to switch because t-rex doesn't support AMD GPUs like PM does, which means I'd have to run PM for AMD and t-rex for nVidia on this mixed GPU rig. Yaay.

[igotek]

RX 6600 not mining with phoenixminer.
gminer works. please update your code.

[deedeeranged]

RX 6600 not mining with phoenixminer.
gminer works. please update your code.

Please state OS used we cannot guess.

I have a rx 6600 xt and it works fine with PhoenixMiner on Linux.

*** 19:31 *** 12/21 13:18 **************************************
Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 19:31
Available GPUs for mining:
GPU1: ASRock Navi 23 [Radeon RX 6600/6600 XT/6600M] (pcie 45), OpenCL 2.0, 8 GB VRAM, 32 CUs
GPU1: 56C 22% 66W
GPU1: cclock 1190 MHz, cvddc 743 mV, mclock 1169 MHz, Tj 61C, Tmem 76C, 509 kH/J
GPUs power: 66.0 W; cost: 0.48 USD/day; 509 kH/J
Current -gt 15
Eth: Accepted shares 547 (1 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.18%
Eth: Maximum difficulty of found share: 849.2 GH (!)
Eth: Average speed (5 min): 33.601 MH/s
Eth: Effective speed: 33.41 MH/s; at pool: 33.41 MH/s

[Digital_Seytan]

I have been using phoenixminer for several years, a while ago I used Gminer for a few months, what strikes me is that gminer gets much more THashrate and phoenixminer only gets smaller Mhashrate or Ghashrate, so that in the end the yield at Gminer in Ethereum or ETC is much more per day or per month, does this also occur to others I have tried software such as phoenixminer or Gminer on K1pool and this is the result with me, hopefully the developer of PM will also watch and do something about it, but as always this one sleeps farther think me, and by the way with the lowest percentage devfee phoenixminer is no longer correct, BZminer and Teamblacminer use 0.5 % devfee  and this one nsfminer (no stinkin' fees) 0% devfee


 

[makipsee]

has anyone run into the issue of the miner taking forever (>2mins) to detect the gpus? (happens with any miner but i mainly use phoenix). nvidia driver 471.11, amd driver 21.4.1, windows 10, PM 5.6d

[soda37]

Time to reduce devfee to 0,5 at least, Phoenix Team!!!

Vote!

[ironmanred]

RX 6600 not mining with phoenixminer.
gminer works. please update your code.

It does. I am using Windows 10/PM 5.8c and RX6000 is running well.

[mrbillishere]

Current is 497.09 for windows.  This is most likely the issue.

@miner29 - if your reply was directed towards my post, just above yours, then first off thank you for weighing in... I should add that per the nVidia control panel we're still using driver package 470.05, and per device-manager's info the timestamp on the driver file is still 2021-02-26, so I believe I've ruled out Microsoft being helpful with a GPU driver update. (Also, I looked at update history and aside from the monthly cumulative update, nothing else was applied yesterday. bummer.)

That said, I'm not averse to cleaning up the existing nVidia drivers package using DDU followed by a reinstallation of the same to see if anything changes.

In the meantime I did get t-rex going to see what it thinks. Both cards are hashing and t-rex was able to set the memory and clock speed deltas, and the clock power delta. Of course nothing's perfect - it is claiming it can't see the temps of the graphics memory so I can't specify a fanspeed range based on mem-temps. IDK if that ever worked because I've never used t-rex for ethash before and heck, I'm not sure I want to switch because t-rex doesn't support AMD GPUs like PM does, which means I'd have to run PM for AMD and t-rex for nVidia on this mixed GPU rig. Yaay.

Here's a quick update re: a workaround I discovered that remediates the bizarre errors I was getting from PM...

So to recap, for the past five days the rig was running PM v5.9d for the AMD RX580 GPUs and t-rex for the nVidia GPUs because PM glitched on me after this month's Win10 patches. That was alright, but let's just say I am not a fan of the t-rex console, nor of its higher dev-fees, and I missed some of PM's features like being able to hit C while mining when you want the app to re-read its config settings and update them on the fly, so I didn't leave well enough alone.

This evening, I went into the UEFI of the motherboard (it's an ASUS brand with an AMD x570 chipset) and fiddled with the settings for the PCIe version assigned to each PCIe slot. Previously, all four were set to Auto and the newer nVidia RTX 3000-series GPUs were being set to PCIe 4 automatically while the RTX 580s were being set to PCIe 3. Pretty normal stuff. Don't ask me why but I decided to set all four expansion slots to PCIe 3 to see what would happen. Lo and behold, PhoenixMiner is back to normal! You could even go so far as to say that it's risen from the ashes. (cue rimshot)

So, take this fwiw. Maybe it'll help someone else too. Cheers.

[relax69]

RX 6600 not mining with phoenixminer.
gminer works. please update your code.

It does. I am using Windows 10/PM 5.8c and RX6000 is running well.

I would say it works somehow, but there are still a lot of bugs needed fixing.

My problems with PM started back in May or June when I try to run RX 6700 XT in HiveOS. First, I had to run an older version of PM to make it works. Then, I found -clKernel 0 is fixing this issue, but the GPUs which are running with it, are producing a lot of invalid shares, and the hashrate is unstable. Since then, I added some RX6600's to that rig, and PM had a few updates, but I never got my RX 6x00 cards working with -clKernel 1. Anyway I believe, this issue is on the HiveOS side (I try to contact them, but no answer from them yet) because PM requires current new drivers, but Hive sticks with old ones. I think PM devs need to work with Hive to resolve it.

Now back to my Windows rigs.
When I run any of my RX 6x00 GPUs on my testing PC as a single card with current PM, I do not have any issues. Frequencies and voltages changes as expected  -clKernel 1 works fine, and cards are singing.
All my problems are starting after moving the cards to a mixed rig. Unfortunately, I don't have enough GPUs and free space to combine only cards of the same type.
After swapping GPUs around my rigs, the current situation is:
Running Windows 10 Pro 21H2 with AMD driver 21.8.2 minimal required for RX 6600 XT. Driver 21.8.1 is more unstable, and higher versions do not make any better.
The RX 6600 XT now is running as expected, but in the past, on a different rig with driver  21.10.2 I had to run it with -clKernel 0 together with some other BigNavi cards.
The problem now is an RX 5500 XT which must be run with -clKernel 0 and it does not accept the commands -cclock and -cvddc from the miner unless I do not change OC settings in the AMD software before I start the miner. This makes the card jump power usage from 50-52 Wats to over 80 Wats with no changes on the hashrate.
Another issue shows up on this rig after I added the RX 6600 all Polaris cards, or randomly some of them are unable to init straps and set straps. For more details, please see parts of my log file posted below.

Code:

2021.12.22:21:33:48.619: main Phoenix Miner 5.9d Windows/msvc - Release build
2021.12.22:21:33:48.619: main Cmd line: 
2021.12.22:21:33:48.619: main config.txt: -pool ssl://us2.ethermine.org:5555 -wal 0xdxxxxxxxxxxxxxxxx8a.RPM59d -acm -gbase 0 -mode 1 -cdm 0 -eres 5 -wdog 1 -rmode 2 -clgreen 1 -logfile Log*.log -logdir Logs -tt 67 -fcm 2 -fanmin 50 -tstop 86 -tstart 68 -hstats 2 -hwm 1 -fanstop 0 -gt 0 -pidle 100 -prate 0.11 -clKernel 1,0,1,1,1,1,1 -amd -ttj 72 -ttmem 78 -mt 1,1,1,0,0,2,0 -vmr 25,25,20,0,25,70,10 -straps 1,1,0,0,1,3,1 -cclock 1000,1000,1100,1100,1100,1100,1100 -cvddc 670,750,850,850,850,850,850 -mclock 2100,1900,2075,1995,2150,2150,2030 -mvddc 0,0,800,800,800,750,750 
2021.12.22:21:37:21.624: main OpenCL driver version: 21.6-8.x
2021.12.22:21:37:35.331: main Available GPUs for mining:
2021.12.22:21:37:35.331: main GPU0: Gigabyte AMD Radeon RX 6600 XT (pcie 8), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.12.22:21:37:35.331: main GPU1: XFX Radeon RX 5500 XT (pcie 11), OpenCL 2.0, 8 GB VRAM, 22 CUs
2021.12.22:21:37:35.331: main GPU2: PowerColor Radeon RX 580 Series (pcie 12), OpenCL 2.0, 8 GB VRAM, 36 CUs
2021.12.22:21:37:35.331: main GPU3: XFX Radeon RX 570 Series (pcie 13), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.12.22:21:37:35.331: main GPU4: Sapphire Radeon RX 570 Series (pcie 14), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.12.22:21:37:35.331: main GPU5: MSI Radeon RX 570 Series (pcie 15), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.12.22:21:37:35.331: main GPU6: XFX Radeon RX 570 Series (pcie 16), OpenCL 2.0, 8 GB VRAM, 32 CUs
2021.12.22:21:37:35.332: main ADL library initialized
2021.12.22:21:37:36.951: main Eth: Loading pools from epools.txt
2021.12.22:21:37:36.952: main Eth: the pool list contains 7 pools (1 from command-line)
2021.12.22:21:37:36.952: main Eth: primary pool: ssl://us2.ethermine.org:5555
2021.12.22:21:37:36.952: main Starting GPU mining
2021.12.22:21:37:36.952: main Matched GPU0 to ADL adapter index 41 (method 1)
2021.12.22:21:37:50.473: main GPU0: AMD driver 21.8.2
2021.12.22:21:37:50.473: main GPU0: Created ADL monitor for adapter 41; overdrive version: 8 (8)
2021.12.22:21:37:50.473: main GPU0: using AMD driver ver 21.8.2
2021.12.22:21:37:50.473: main Matched GPU1 to ADL adapter index 35 (method 1)
2021.12.22:21:38:05.019: main GPU1: AMD driver 21.8.2
2021.12.22:21:38:05.019: main GPU1: Created ADL monitor for adapter 35; overdrive version: 8 (8)
2021.12.22:21:38:05.019: main GPU1: using AMD driver ver 21.8.2
2021.12.22:21:38:05.019: main Matched GPU2 to ADL adapter index 0 (method 1)
2021.12.22:21:38:18.386: main GPU2: AMD driver 21.8.2
2021.12.22:21:38:18.386: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7 (7)
2021.12.22:21:38:18.386: main GPU2: using AMD driver ver 21.8.2
2021.12.22:21:38:18.386: main Matched GPU3 to ADL adapter index 21 (method 1)
2021.12.22:21:38:33.095: main GPU3: AMD driver 21.8.2
2021.12.22:21:38:33.095: main GPU3: Created ADL monitor for adapter 21; overdrive version: 7 (7)
2021.12.22:21:38:33.095: main GPU3: using AMD driver ver 21.8.2
2021.12.22:21:38:33.095: main Matched GPU4 to ADL adapter index 28 (method 1)
2021.12.22:21:38:46.961: main GPU4: AMD driver 21.8.2
2021.12.22:21:38:46.961: main GPU4: Created ADL monitor for adapter 28; overdrive version: 7 (7)
2021.12.22:21:38:46.961: main GPU4: using AMD driver ver 21.8.2
2021.12.22:21:38:46.962: main Matched GPU5 to ADL adapter index 7 (method 1)
2021.12.22:21:39:03.221: main GPU5: AMD driver 21.8.2
2021.12.22:21:39:03.221: main GPU5: Created ADL monitor for adapter 7; overdrive version: 7 (7)
2021.12.22:21:39:03.222: main GPU5: using AMD driver ver 21.8.2
2021.12.22:21:39:03.222: main Matched GPU6 to ADL adapter index 14 (method 1)
2021.12.22:21:39:15.536: main GPU6: AMD driver 21.8.2
2021.12.22:21:39:15.536: main GPU6: Created ADL monitor for adapter 14; overdrive version: 7 (7)
2021.12.22:21:39:15.536: main GPU6: using AMD driver ver 21.8.2
2021.12.22:21:39:18.550: wdog Starting watchdog thread
2021.12.22:21:39:19.059: hwmc GPU0: set VMEM timing level to 1
2021.12.22:21:39:19.168: hwmc GPU0: unable to set straps - unsupported GPU
2021.12.22:21:39:19.168: hwmc GPU0: unable to set straps 
2021.12.22:21:39:19.181: hwmc GPU2: set VMEM timing level to 1
2021.12.22:21:39:19.370: main Eth: Connecting to ethash pool ssl://us2.ethermine.org:5555 (proto: EthProxy)
2021.12.22:21:39:19.371: main GPU0: 34C 0% 6W, GPU1: 31C 55% 3W, GPU2: 32C 34% 6W, GPU3: 32C 0% 16W, GPU4: 34C 37% 8W, GPU5: 31C 30% 11W, GPU6: 29C 74% 23W
GPU0: cclock 167 MHz, cvddc 637 mV, mclock 128 MHz, Tj 34C
GPU1: mclock 10 MHz, mvddc 650 mV, Tj 32C
GPU2: cclock 301 MHz, cvddc 750 mV, mclock 300 MHz
GPU3: cclock 300 MHz, cvddc 750 mV, mclock 300 MHz
GPU4: cclock 300 MHz, cvddc 750 mV, mclock 400 MHz
GPU5: cclock 1010 MHz, cvddc 750 mV, mclock 300 MHz
GPU6: cclock 939 MHz, cvddc 856 mV, mclock 300 MHz
GPUs power: 72.3 W; total power: 172.3 W; cost: 0.45 USD/day
2021.12.22:21:39:19.371: main GPU0 Gigabyte AMD Radeon RX 6600 XT (pcie 8): AMD Compute mode is not needed by this GPU/driver
2021.12.22:21:39:19.371: main GPU1 XFX Radeon RX 5500 XT (pcie 11): AMD Compute mode is not needed by this GPU/driver
------------------------------------------------------------
2021.12.22:21:41:37.483: main GPU0: 45C 72% 61W, GPU1: 46C 60% 50W, GPU2: 48C 49% 80W, GPU3: 56C 49% 68W, GPU4: 55C 49% 83W, GPU5: 52C 49% 64W, GPU6: 60C 50% 67W
GPU0: cclock 980 MHz, cvddc 662 mV, mclock 2088 MHz, Tj 50C, 530 kH/J
GPU1: cclock 988 MHz, cvddc 743 mV, mclock 1838 MHz, mvddc 850 mV, Tj 47C, 530 kH/J
GPU2: cclock 1100 MHz, cvddc 850 mV, mclock 2075 MHz, 349 kH/J
GPU3: cclock 1100 MHz, cvddc 850 mV, mclock 1995 MHz, 420 kH/J
GPU4: cclock 1100 MHz, cvddc 850 mV, mclock 2150 MHz, 326 kH/J
GPU5: cclock 1100 MHz, cvddc 850 mV, mclock 2150 MHz, 428 kH/J
GPU6: cclock 1100 MHz, cvddc 850 mV, mclock 2030 MHz, 438 kH/J
GPUs power: 472.5 W; total power: 572.5 W; cost: 1.51 USD/day; 348 kH/J
2021.12.22:21:41:38.316: main Eth speed: 199.562 MH/s, shares: 6/0/0, time: 0:04
2021.12.22:21:41:38.316: main GPUs: 0: 32.303 MH/s (0) 1: 26.992 MH/s (0) 2: 27.908 MH/s (1) 3: 28.689 MH/s (3) 4: 26.964 MH/s (0) 5: 27.306 MH/s (1) 6: 29.401 MH/s (1)
--------------------------------
2021.12.22:21:41:26.102: hwmc GPU4: unable to init straps
2021.12.22:21:41:26.102: hwmc GPU4: unable to set straps 
2021.12.22:21:41:26.104: hwmc GPU5: unable to init straps
2021.12.22:21:41:26.104: hwmc GPU5: unable to set straps 
2021.12.22:21:41:26.105: hwmc GPU6: unable to init straps
2021.12.22:21:41:26.105: hwmc GPU6: unable to set straps 
2021.12.22:21:41:26.163: hwmc GPU1: set GPU clocks to 1000 MHz (Vddc 750 mV)

P.S. Also on this rig, I currently have a couple of 4G Nvidia cards, mining RVN.

[ironmanred]

RX 6600 not mining with phoenixminer.
gminer works. please update your code.

It does. I am using Windows 10/PM 5.8c and RX6000 is running well.

I would say it works somehow, but there are still a lot of bugs needed fixing.

My problems with PM started back in May or June when I try to run RX 6700 XT in HiveOS. First, I had to run an older version of PM to make it works. Then, I found -clKernel 0 is fixing this issue, but the GPUs which are running with it, are producing a lot of invalid shares, and the hashrate is unstable. Since then, I added some RX6600's to that rig, and PM had a few updates, but I never got my RX 6x00 cards working with -clKernel 1. Anyway I believe, this issue is on the HiveOS side (I try to contact them, but no answer from them yet) because PM requires current new drivers, but Hive sticks with old ones. I think PM devs need to work with Hive to resolve it.

Now back to my Windows rigs.
When I run any of my RX 6x00 GPUs on my testing PC as a single card with current PM, I do not have any issues. Frequencies and voltages changes as expected  -clKernel 1 works fine, and cards are singing.
All my problems are starting after moving the cards to a mixed rig. Unfortunately, I don't have enough GPUs and free space to combine only cards of the same type.
After swapping GPUs around my rigs, the current situation is:
Running Windows 10 Pro 21H2 with AMD driver 21.8.2 minimal required for RX 6600 XT. Driver 21.8.1 is more unstable, and higher versions do not make any better.
The RX 6600 XT now is running as expected, but in the past, on a different rig with driver  21.10.2 I had to run it with -clKernel 0 together with some other BigNavi cards.
The problem now is an RX 5500 XT which must be run with -clKernel 0 and it does not accept the commands -cclock and -cvddc from the miner unless I do not change OC settings in the AMD software before I start the miner. This makes the card jump power usage from 50-52 Wats to over 80 Wats with no changes on the hashrate.
Another issue shows up on this rig after I added the RX 6600 all Polaris cards, or randomly some of them are unable to init straps and set straps. For more details, please see parts of my log file posted below.

P.S. Also on this rig, I currently have a couple of 4G Nvidia cards, mining RVN.

I use RX6000 (non-XT) with WIndows10 21H2, AMD driver 21.10.2, PM 5.8C in a rig with five RX5700(XT) and one RX6600 without a single issue.