Best to add your full system specs, at minimum include what motherboard. I'd also include the type of SSDs you are using as some are incompatible. To get verbose boot the easiest way to is to add -v to your boot argument but you have other issues. You have no Booter/ MmioWhitelist entries in your config.plist, see the beginning of this post for a quick overview of how to get those. Its possible you may also need ACPI patches depending on the type of motherboard you have and bios version.Couldn't figure out why my installer boot only on apple logo with progress bar stuck at 0% progression and reboots. no verbose or error description.
Machine Spec:
Ryzen 5 5600x
GPU RX 6800
View attachment 18566
Here is my full pc specs:Best to add your full system specs, at minimum include what motherboard. I'd also include the type of SSDs you are using as some are incompatible. To get verbose boot the easiest way to is to add -v to your boot argument but you have other issues. You have no Booter/ MmioWhitelist entries in your config.plist, see the beginning of this post for a quick overview of how to get those. Its possible you may also need ACPI patches depending on the type of motherboard you have and bios version.
Thanks for the reply, I've added the -v keepsyms=1 debug=0x100 and now it got stuck on the log text screen, here's attached log file.As the OP is using a Ryzen 5 5600X CPU they will be using an AM4 motherboard, most likely from the 400 or 500 series. So they shouldn't need MmioWhitelist entries or ACPI patches (like an AM5 board) for running macOS.
Adding -v keepsyms=1 debug=0x100 to the NVRAM > Add > boot args section of your config.plist will enable the system to show the verbose text, plus they should prevent if from rebooting, so you can take a photo of the text on the screen. Which you can then post here, so we can hopefully see what is causing your system to kernel panic.
As soon as I saw his motherboard information I knewI had given him wrong information, somehow I thought his CPU was AM5.As the OP is using a Ryzen 5 5600X CPU they will be using an AM4 motherboard, most likely from the 400 or 500 series. So they shouldn't need MmioWhitelist entries or ACPI patches (like an AM5 board) for running macOS.
Adding -v keepsyms=1 debug=0x100 to the NVRAM > Add > boot args section of your config.plist will enable the system to show the verbose text, plus they should prevent if from rebooting, so you can take a photo of the text on the screen. Which you can then post here, so we can hopefully see what is causing your system to kernel panic.
Apologies for the bad advice. Knowing now you have a B550 chipset board I would advance you are missing SSDT-CPUR.aml. There could be other issues as well but that by itself stands out and probably why your system stops loading OpenCore so early.Thanks for the reply, I've added the -v keepsyms=1 debug=0x100 and now it got stuck on the log text screen, here's attached log file.
