-
-
Notifications
You must be signed in to change notification settings - Fork 130
Navi 21 rendering glitches, macOS Sequoia #95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@larini Which macOS 15 version to be precise, 15.1? |
@VisualEhrmanntraut Yes, version 15.1. I already tried a fresh install, but same results. |
Uh well I told some people with Navi 22 to test and they don't have any issues. So I'm not sure what I broke with Navi 21. I'll have to take a look at a later point. |
Thanks for the test. Maybe his card is just fried then? |
I think he have to try other method, spoofing, etc and see. If his card is fried he would noticed it in Windows, right? |
This comment was marked as off-topic.
This comment was marked as off-topic.
Should I open new issue? |
No, I am not the developer of these drivers therefore it's not my responsibility. Same for bugs in AMD's firmware. |
Ok, got it. Seems to me it's related to NootRX.kext. I rebooted with spoofed OC config again after and results was back to high as it was. So I thought it's related... |
No, it's not a bug with the kext. The kext uses the existing drivers just as WhateverGreen does, with the exception of firmware and setting updates extracted from the Windows drivers. If performance regressions are introduced by these changes, it's AMD's fault. |
Also, I do have a firmware update pending, but none of the internal quality control testers have tested it yet. |
That's nice, will wait for updated kext then . Or I can test it for you if it's compiled. |
Sure, here's a build. |
Great! Will report in a half an hour. |
Ok, Geekbench result didn't changed :( Same, twice lower. Also got kernel panic "WindowServer" with testing kext on first boot. Second boot went fine. I'm getting same kernel panic occasionally without nootrx.kext anyway. But if you interested to look at it I'm attaching it. Also forgot to mention. GPU is for 10 degrees hotter with kext compared to spoofed entry. |
That panic is usually either memory corruption or attempt to free memory that can't be freed. |
@shrisha108 Could you also try this? |
Oh, thank you. So my whitelisting of MMIO is not proper probably? |
sure |
Can't say for sure, it could also be one of the kexts being written bad. |
You sure it's another one? Size is fully identical with the one you gave me half an hour ago |
Good catch, I guess I forgot to recompile. |
May be change the release number for something like 1.0.1 |
I'm 100% sure it's a fresh build. It might just be cached info. |
Ok, sure. |
Yes, that's definitely latest build. I've got hard hang, even reset button didn't work, Have to fully switched off power supply. |
"NootRX: @ Failed to find a compatible GPU" How would that be possible? I only changed one line to enable the SMC firmware injection for Navi 21 |
Got it, so will wait then until #69 will be resolved. Thank you. |
@larini @shrisha108 try the build of the latest commit |
The new NootRX gives a better performance for my RX 6600. Around 33% increase of performance. |
hi, the newest NootRX got very slow and hang after wake from sleep if play video, anyone had same issue? |
You haven't even specified which GPU and which CPU. |
hi, sorry my bad, |
hi, your super fast reply, |
When did you try it? I made an update 2 days ago |
(And you can't use it along with CpuTscSync) |
I'm just trying to make sure it works properly, don't worry. |
your best creator ever, |
16 is 0x10 |
the field takes in decimal, you basically gave it an invalid policy and it fell back to default |
Not work here at all.. |
Well, you can't be the only one with the rendering glitches. Besides, this GPU is natively supported, NootRX is really just injecting some personalities and updated firmware, which are taken from Windows. |
Sorry @VisualEhrmanntraut , I don't know what's happen. Sonoma works like a charm... Thanks |
The issue could be fixed but the shaders be cached and showing corruption still |
A strange behavior is that the system becomes slow, broken, sometimes it works and after a while it crashes, then it comes back... |
@larini Maybe running these will help find $(getconf DARWIN_USER_CACHE_DIR) -exec sudo rm -rf {} \;
find $(getconf DARWIN_USER_TEMP_DIR) -exec sudo rm -rf {} \; |
@larini Now restart |
@VisualEhrmanntraut, I appreciate your attention, but nothing works. |
macOS Version
Sequoia
What is your CPU's model?
Ryzen 3700X
What is your GPU's model?
RX 6950 XT
Please describe the behaviour in detail.
My GPU is a XFX RX 6950 XT Merc 319.
Works perfect with Sonoma, but after upgrade to Sequoia, the machine is very slow, and full of strange artifacts on screen.
This is a bug of this model or Sequoia breaking change?
What should've happened instead?
Works like Sonoma.
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
No response
The text was updated successfully, but these errors were encountered: