Unable to install Sonoma

hasrt1206

New member
AMD OS X Member
Aug 17, 2020
24
1
3
CPU:
Ryzen 5 3600
Hi!
I am currently trying to install Sonoma on the following hardware:
CPU: Ryzen 5 3600
MOBO: Asus b550-f
GPU: 5700xt
RAM: corsair vengeance lpx 4 x 8gb.

I am getting stuck on: [EB|#LOG:EXITBS:START].
I have done all the steps on the dortania guide in reference to this kernel error and cannot get past it.
I have attached my EFI folder and latest OC debug log.


Thank you for your help!
 

Attachments

Straight away you've not applied the kernel patches, https://github.com/AMD-OSX/AMD_Vanilla

Your ACPI -> Add is mad. Revisit the guide and go over your config again. You also don't need all those Bcrm kexts.
 
Straight away you've not applied the kernel patches, https://github.com/AMD-OSX/AMD_Vanilla

Your ACPI -> Add is mad. Revisit the guide and go over your config again. You also don't need all those Bcrm kexts.
I went back and revisited the guide, added the AMD patches, clean my ACPI folder accordingly and lastly removed the berm kexts as you suggested. Unfortunately I am still locked in the same kernel error. I have attached my latest debug file and EFI folder.

Once again, thank you.
 

Attachments

Try this revised EFI.

See if this gets you any further along the installation process.
 

Attachments

Try this revised EFI.

See if this gets you any further along the installation process.
Thank you for your reply.

I have tried your efi but now I get this screen : IMG_4127.jpg
 
Give this a whirl. On first boot press the spacebar to show OC Tools and clear NVRAM. Reboot and try booting.
 

Attachments

Give this a whirl. On first boot press the spacebar to show OC Tools and clear NVRAM. Reboot and try booting.
I was able to get into the installer and install Sonoma but now I keep getting a bootloop right after it restarts from the installer. You can see it here.
 
I was able to get into the installer and install Sonoma but now I keep getting a bootloop right after it restarts from the installer. You can see it here.
In the config.plist change Misc/ Security from "Default" to "Disabled", clear NVRAM and try again
 
In the config.plist change Misc/ Security from "Default" to "Disabled", clear NVRAM and try again
I did that but I might have done it on the wrong line. I am now getting this error as soon as I boot the pc up:

IMG_4132.jpg
The setting I change is Misc/Security/SecurebootModel default to disable.
 
Undo the change(s) you made to the EFI or config.plist, after installing Sonoma.
 
I did that but I might have done it on the wrong line. I am now getting this error as soon as I boot the pc up:

The setting I change is Misc/Security/SecurebootModel default to disable.

It's Disabled not Disable.
 
  • Like
Reactions: leesurone
It's Disabled not Disable.

My bad...😅. I have installed Sonoma, Now I just need to add my kexts and edit my config.plist to match my system.

Thank you all for your help.
 
  • Like
Reactions: Shaneee
I have been reading that the Intel I225V network card works natively in Sonoma. Is that true? I don't have ethernet working. AMD-V or SVD has been enabled but ethernet is still not working. Is the AppleIGC.kext still needed or could it be a work around for me?
 
I have been reading that the Intel I225V network card works natively in Sonoma. Is that true? I don't have ethernet working. AMD-V or SVD has been enabled but ethernet is still not working. Is the AppleIGC.kext still needed or could it be a work around for me?
I believe I225V Network cards can be natively supported on intel platforms, I don't believe that's the case with our AMD systems. I'm sure Shaneee has more insight. I use AppleIntelI210Ethernet.kext in my AMD system
 

Attachments

Last edited:
I believe I225V Network cards can be natively supported on intel platforms, I don't believe that's the case with our AMD systems. I'm sure Shaneee has more insight. I use AppleIntelI210Ethernet.kext in my AMD system
I am using that kext and it worked, so far no problems. Another problem I've seen is that when the computer goes to sleep it does not come back up. Is that a bug with AMD CPU's? Is there a fix?

Edit: The computer went to Lock Screen and the Ethernet stopped working. I rebooted the computer and ethernet it’s not working. Is there a way to troubleshoot if the kext is loading properly?

Thank you @leesurone @Shaneee @Edhawk !
 
Last edited:
I am using that kext and it worked, so far no problems. Another problem I've seen is that when the computer goes to sleep it does not come back up. Is that a bug with AMD CPU's? Is there a fix?

Edit: The computer went to Lock Screen and the Ethernet stopped working. I rebooted the computer and ethernet it’s not working. Is there a way to troubleshoot if the kext is loading properly?

Thank you @leesurone @Shaneee @Edhawk !
Have you attempted to map your USB Ports? It's not like windows, or a real Mac, that correctly identifies all your ports automatically. Once you have macOS installed and your devices working then the final step is mapping your USB Ports. Without that step your system will fail to sleep and or wake properly often causing a system crash or other anomalies.
That's basically what happened to you, the system failed to wake properly from sleep. To get ethernet working again you will probably have to clear the NVRAM as long as your EFI is set up correctly.
 
Have you attempted to map your USB Ports? It's not like windows, or a real Mac, that correctly identifies all your ports automatically. Once you have macOS installed and your devices working then the final step is mapping your USB Ports. Without that step your system will fail to sleep and or wake properly often causing a system crash or other anomalies.
That's basically what happened to you, the system failed to wake properly from sleep. To get ethernet working again you will probably have to clear the NVRAM as long as your EFI is set up correctly.
I had mapped my usb ports but forgot to add my kexts. I am dual booting windows and macOS and I saw the my time in macOS it’s weird, I tried the editing the windows registry to RTC but did not fix it. Weirdly enough that also broke the Ethernet. I have clear the nvram several times but no fix.
Is there a way to fix the time?
 
I had mapped my usb ports but forgot to add my kexts. I am dual booting windows and macOS and I saw the my time in macOS it’s weird, I tried the editing the windows registry to RTC but did not fix it. Weirdly enough that also broke the Ethernet. I have clear the nvram several times but no fix.
Is there a way to fix the time?
If you mean adding the RealTimeIsUniversal setting to the control set in the windows registry that works, you probably made a mistake
 
If you mean adding the RealTimeIsUniversal setting to the control set in the windows registry that works, you probably made a mistake
Yes, I used the RealTimeIsUniversal setting in the regedit. I checked and it's made for 64 bit os using Q WORD not D WORD. and adding the 1 as a value. Restarted windows to see if it was correct and it was. But on Sonoma it does not change and says my location/timezone is Cupertino, CA. After a while I just changed the city and it changed to my current timezone. Going back to my ethernet problem, I lost ethernet connection after computer wakes from sleep mode, although I had map my usb ports and I can safely go into sleep mode.
 
Yes, I used the RealTimeIsUniversal setting in the regedit. I checked and it's made for 64 bit os using Q WORD not D WORD. and adding the 1 as a value. Restarted windows to see if it was correct and it was. But on Sonoma it does not change and says my location/timezone is Cupertino, CA. After a while I just changed the city and it changed to my current timezone. Going back to my ethernet problem, I lost ethernet connection after computer wakes from sleep mode, although I had map my usb ports and I can safely go into sleep mode.
Its supposed to be a DWord value, I always use 32 bit but 64 bit might work. Definitely do not use Q Word.

There are too many reasons you lose internet after sleep that I don't know I can help unless you zip and upload your current EFI.
 
Last edited:
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.