Please post the kernel panic that you are getting when waking from sleep. I suspect that it's the same one that I was experiencing. I was getting a panic related to HDMI audio. I disabled WhateverGreen and haven't see a panic since.
There's no reason why Clover doesn't respect your default drive setting. Double check your config.plist and try clearing NVRAM (press F11 at the Clover boot menu).
9900K and Radeon VII are not problems. I've been using the same for a pretty long time with no issues.
After a while, I am here with the problem again. A few days have passed without the crash occurring after sleep then suddenly and without any modification to the PC, it came back and instead of a few times, now it happens all the times the computer goes to sleep, both on request and due to inactivity (when I searched for it I couldn't get it one way or the other).
I noticed that every time it has happened since the restart of the processor the number indicated at the beginning is always different and compared to what happened before, Boot args indicated is a strange alphanumeric (before it was Dart = 0 as in plist); I don't seem to have found any more differences, but before I didn't look at him very carefully. I have attached the report.
Another thing that happens every time, now, is the madness of the AMPlibraryAgent process that gets 100% fixed and only with a restart it returns to normal.
If you find analogies with what happened to you, I await information, also on how to do to possibly try to disable whatevergreen and see what happens, but of course I await advice even if you find, reading the panic report, some other possible cause.
On Clover that at boot does not find the disk indicated in plist alone, I tried several times to reset the NVRAM but without any effect and also to move to the last clover (5109), but nothing has changed, it is possible that it is really due to any bugs on the versions after 5107, (as I read from
@Stork)?
As always, thanks for the passion and the work that you experts put on all the "creations"
Edit:
With some time that I let go to read the panic report and write this post, AMPLibraryAgent went back to normal by itself, so maybe it was just me who didn't give him time to finish what he had to do. After the panic, that 100% never noticed before and for a time longer than a few minutes, it seemed to me an oddity that required rebooting, the first time and then, seeing that it returned to normal on reboot, I thought it was really like that, instead now he denied me ... better this way, one less problem.