At this point I'm pretty sure that there's a nasty bug with Polaris cards at least that shows itself on Linux Kernel 5.11 and later.

5.11 was when the fans suddenly got the zero rpm mode, so I'm sure there were some relevant changes made to the kernel.

Anyway, problem is that while the miner says that config clocks have been applied to all cards, even if I drop the mclock significantly in the config, all but GPU1 still hashes at the same rate and same power.

I noticed this because one of the cards started crashing which wasn't happening before. So I investigated and saw that power usage showed by the miner was significantly higher on kernel 5.11 and later.

I tried to drop the power usage by some means as an experiment and I just couldn't manage, no matter what.

So it's pretty clear to me that at very least, the miner thinks it applied the clocks from config successfully but it's not true for all cards.

Does anyone run this on linux with newer kernel than 5.10?

It works perfectly fine on 5.10 but as soon as I try booting with 5.11, it starts working just fine but then in about few minutes it starts slowing down the whole OS to basically 0.5 FPS until I kill the process.

I tried running it with minimum additional parameters and it's still the same.

Starting from 5.5c none of the versions have got along with linux kernel 5.11, including this one. On 5.5c only first GPU was hashing, on this version it seems like everything starts up properly but then within 15-20 seconds, hashrates start going crazy, fluctuating from 8 to 31 (all polaris GPUs) and the whole OS gets slowed down to 0.2 FPS.

Is there maybe something that needs adjusting on my side or is compatibility still in the works?

I'm asking because kernel 5.12 is right around a corner and it seems like at this pace the gap is only going to grow.

Same with 20.50 drivers on linux.

Has anyone tried mining with Polaris cards on new 5.11 kernel?

There are clearly some major fixes in that one because ZeroRPM fan finally works right out of the box, I WAS SHOCKED.

As for the mining though, all of the threads except for GPU0 are unresponsive. Is there something I should alter in the config or should I just wait for the new release?

I have a little problem with XMR stak.

I have two mostly similar rigs mining Monero, one running Windows 10, another SMOS. Each has 8 x RX580 Strix.

Some time ago I managed to find a spot on config for the Windows rig. It was two workers per GPU and managed to squeeze about 500 H/s per worker.

For a while I couldn't figure out how to modify AMD.txt in SMOS to get the same result, but today I managed to do that. I pushed the same thread config files in persistent memory and pointed the miner to them. The config files do their job but hashrate is about 100 H/s lower per worker, so about 200 H/s lower per GPU.

That's a significant difference and I can't figure out what could the reason be. Anyone with the same problem?

P.S. I had the "mmap failed" messages, followed the FAQ and fixed it. Didn't make a difference in hashrate.

P.P.S. Windows rig has 12 gigs of memory and runs from large fast SSD. SMOS rig has 4 gigs of memory and runs from the USB 2.0 flash drive.

P.P.P.S. I have several GPUs from the SMOS rig underclocked compared to others for stability reasons. That usually results in those GPUs showing less hashrate, but now all GPUs show hashrate within 1 H/s from each other. Which makes me suspect that there's a "bottleneck" somewhere capping all GPUs at about 80% of their full potential.

Praise to the crypto gods (and SM staff) for the new XMR Stak being added.

I have a question though. Is there any way to access XMR Stak thread configuration files? Because that way I can squeeze about 25% more juice out of the rig and it's kind of a big deal.

Can I somehow edit/access the thread configuration file for the XMR stak?

I found a great config on my windows rig and can't figure out how to apply it in SMOS.

For the love of any kind of theoretical omnipotent entity, please add the later release of XMR Stak. It's been out for months.

Also a question: How do I access XMR Stak thread config?