Bootloop on Sonoma - Githubissues

ChefKissInc / NootedRed

The AMD Vega iGPU support patch kext. No commercial use.

https://ChefKissInc.github.io/nred

Other

1.55k stars 659 forks source link

Bootloop on Sonoma #214

Closed ethernetme closed 6 months ago

ethernetme commented 6 months ago

macOS Version

Sonoma

What is your CPU's model?

Ryzen 5 3500U

Please describe the behaviour in detail.

Sonoma crashes and reboots a few seconds after booting. Even with a clean install, the installation goes well but it starts crashing on the first boot screen. This issue only happens on Sonoma specifically and with the NootedRed kext enabled.

What should've happened instead?

The system should work fine without any crashes.

If applicable, attach the .gpuRestart, .panic, etc file related to this issue.

No response

Bug report submission terms

[X] I am using the latest version of NootedRed.
[X] I am on the latest minor and patch version of macOS (ex. 7 is the minor and 10 is the patch of macOS 11.7.10).
[X] The bug only happens with NootedRed enabled.
[X] I have ruled out any external factors that could interfere, including, but not limited to, using OCLP or WhateverGreen.

dinhhop11 commented 6 months ago

enable all AMD Vanilla kernel patch

ethernetme commented 6 months ago

enable all AMD Vanilla kernel patch

I've enabled all the patches but that didn't fix the issue. Still, I don't see how that'd fix anything since everything works fine without the NootedRed kext.

dinhhop11 commented 6 months ago

enable all AMD Vanilla kernel patch

I've enabled all the patches but that didn't fix the issue. Still, I don't see how that'd fix anything since everything works fine without the NootedRed kext.

because i have a same problem since ventura 13.4+,sonoma. I enable all kernel patch to fix it.

ethernetme commented 6 months ago

because i have a same problem since ventura 13.4+,sonoma. I enable all kernel patch to fix it.

Unfortunately, it's not the case for me. If you know any other way to fix it, please let me know.

tammo03 commented 6 months ago

I think it's related to your specific setup. It works for me in the latest Sonoma version. Without getting more input from you, it doesn't sound like it's a bug.

ethernetme commented 6 months ago

I think it's related to your specific setup. It works for me in the latest Sonoma version. Without getting more input from you, it doesn't sound like it's a bug.

I don't think that's the case since this only happens in Sonoma, and I'm not the only person with this issue. Besides, I don't see what could be wrong with my setup. I'll attach my config file here just in case it's helpful. config.zip

dinhhop11 commented 6 months ago

I think it's related to your specific setup. It works for me in the latest Sonoma version. Without getting more input from you, it doesn't sound like it's a bug.

I don't think that's the case since this only happens in Sonoma, and I'm not the only person with this issue. Besides, I don't see what could be wrong with my setup. I'll attach my config file here just in case it's helpful. config.zip

I don’t remember exactly the right way to fix this but i did delete old efi and build a new one with all OP,kext latest version... My old EFI works on macos 11,12 latest and 13.0 partition. But 13.4 and 14 are not.

VisualEhrmanntraut commented 6 months ago

Cannot reproduce. Join the Telegram for support.

ethernetme commented 6 months ago

Cannot reproduce. Join the Telegram for support.

Yes I'm already there but I don't know how to get support without getting ignored

VisualEhrmanntraut commented 6 months ago

You don't appear to actually be in our Telegram.