Quote from: vapourminer on August 28, 2021, 04:12:16 PM

so whats up with cl error -11 and -41.

this only started when i installed a 6600XT, the 6700xt in the same rig was fine.

rig is an onda D8P (G4400, 8 gigs ram, 120 gig ssd, 2x g3 evga 850s) with 1080ti, 1070ti, 1070, 6700xt - ran fine on all that for months

using phoenix 5.7b

then added the 6600xt no joy it fails and exits the program. pcie plugs is connected. i changed slots no joy there either.

installed latest win update 21/h1 (i think have to check but its what win update just installed), amd driver is dated 8/25/2021 so its the latest. swap is 64 gigs.

i know people are mining on the 6600xt, so what am i doing wrong?

edit mining eth

EDIT switched to nbminer.. works fine with NO other changes. dropped it in and it just ran... so much for phoenixminer

I have a 6700xt that gives the cl error -11 and -41, I believe that this may be because the opencl version was updated to 2.1, and Phoenixminer is expecting 2.0, but that is just a guess based on the researching the error very quickly.. Regardless, the only way i can get it to run, even with 5.7b, is to use the -clKernel 0 setting that 5.7b was supposed to no longer require. I don't know if I'm missing any performance, and my rig is simple. Just a 5900x, 16gb of RAM, and a single 6700xt. The CPU and RAM aren't even overclocked (yet).

These are all the switches I have tried after the wallet address, and only the last two work:
-proto 3
-proto 3 -dagrestart 1 -rvram -1 -eres 0 -altinit
-proto 3 -dagrestart 1 -rvram -1 -eres 0
-proto 3 -dagrestart 1 -rvram -1 -eres 8
-proto 3 -dagrestart 1 -rvram -1 -eres 0 -clKernel 0
-proto 3 -dagrestart 1 -rvram -1 -eres 8 -clKernel 0

I'd love to know if I'm doing something wrong, what performance I'm losing, if any, and what I should try to fix/debug this.

And before someone says "compute mode," there is no separate compute mode on big navi cards. It isn't an option. Also, I have tried at full standards feeds and speeds, no over or underclocks, the errors are always the same without -clKernel 0. If I've tried anything else, i can't think of it at the moment