EB|LOG:EXITBS:START no matter what I've tried

[Havakak]

Hi. I was using my computer with Sonoma 14.6 without any issues. Today I've just wanted to clean install sonoma so I have created an installer USB via createinstallmedia command. Anyways while erasing the disk I've accidentally erased the whole disk with all its partitions so my EFI is gone. Stupid me, I have no backup of the EFI.

So I've created a new EFI to install Sonoma. With the EFI I've attached, I can boot the installer and pass the first phase of installation. After the first reboot and see the internal "macos installer" my computer reboots. When I see the log file I see EB|LOG:EXITBS:START. I have tried everything in the EB|LOG:EXITBS:START section of the Dortania's guide. Nothing had worked.

I have my old SSDT Usb Mapping file (aml). I have created the other three AML files via SSDTTime from live linux.

Can anyone check my EFI please? Thank you.

Asrock B450 Fatality ITX Board (latest 2024 bios) and all my Bios settings are correct because it was still running with OC 1.0.2 until today's disaster.
Intel wi-fi and ethernet
RX470 GPU

 

[Edhawk]

Are you still using the 6-core Ryzen 5 3600X CPU in this system?

You might want to try the following:

• Setting SetupVirtualMap Quirk to 'False' if you are using a new bios. As this can sometimes cause a kernel panic on B450 boards.
• Setting SecureBooModel Quirk to 'Disabled', as this may help get past any early kernel panics.
• Setting both MinDate and MinVersion to '0'.

The ReservedMemory sub-section in the UEFI section of your config.plist has been dragged and dropped to a different location. It should be the second last section in the config, just before 'Unload' sub-section.

bottom section of your config

bottom section of revised config.

I have made the changes listed above to the attached config.plist.
I have also cleaned up the config, removing any unnecessary elements.

Give it a try and see if this helps.

 

[Havakak]

Are you still using the 6-core Ryzen 5 3600X CPU in this system?

You might want to try the following:

• Setting SetupVirtualMap Quirk to 'False' if you are using a new bios. As this can sometimes cause a kernel panic on B450 boards.
• Setting SecureBooModel Quirk to 'Disabled', as this may help get past any early kernel panics.
• Setting both MinDate and MinVersion to '0'.

The ReservedMemory sub-section in the UEFI section of your config.plist has been dragged and dropped to a different location. It should be the second last section in the config, just before 'Unload' sub-section.

View attachment 15870 bottom section of your config

View attachment 15871 bottom section of revised config.

I have made the changes listed above to the attached config.plist.
I have also cleaned up the config, removing any unnecessary elements.

Give it a try and see if this helps.

Thanks for the quick reply. I’ll try your suggestions tomorrow after work and inform you. Hope it helps.

 

[Havakak]

Yes I still use 6 Core Ryzen5. Tried your config still the same. I've just created the efi from scratch again. Still no change. I can start the installation and it resets in the second phase of the installation. I've attached my rebuilt EFI.

When I change the SecureBootModel to 0 I have "OC: Failed to find SB Model 0" error.

I have tried to apply the "EnableWriteUnprotector" section of the Dortania's guide but still the same.

 

[Edhawk]

Misc > Security > SecureBootModel should be set to Disabled, not 0.

The UEFI > APFS > MinDate & MinVersion entries should be set to 0, when running any version of macOS newer than Catalina.

The Dortania OC Ryzen guide says the EnableWriteUnprotector entry should be set to False, setting it to True is likely to add an unnecessary complication.

 

[Havakak]

I set SecureBootModel to Disabled(case sensitive) and this time I have kernel panic while getting into the installer. Computer does not restart this time.

I have MinDate and MinVersion set to 0 and EnableWriteUnprotector False.

 

[Havakak]

Now I tried to change the APFS property to Catalina. Still the same. The interesting thing is computer is just resetting itself so I cannot see the verbose. If I use debug version of OC can I log the whole verbose?

 

[Havakak]

I've disabled all the network and bluetooth related kexts except for the Lilu, whatevergreen, virtualsmc, mcereporterdisabler etc. still the same. system just reboots not freezing so I cannot see what is on the last line of verbose. But the last line of the log is

02:720 00:016 AAPL: #[EB|LOG:EXITBS:START] 2024-12-19T04:40:04

and after this line there is bunch of random character. I am pasting here some of them.

02:720 00:016 AAPL: #[EB|LOG:EXITBS:START] 2024-12-19T04:40:04
bvxS€ª:û[ùÓjå5ÒܵQˆ÷πÛ¬4yZpBIæE¨°l˜‡‹Pd∂Â~U}Áéìe1 Âñá≤$DÕ
vcBÜKºpN˚ˆûGºç¯1¿?¬∞ÏU=Œ81¿Bc`*D
ƒOù∫◊«⁄à<    3è0‰l◊´&†ßçw|J
ùCJô:ÛãΩ≥∂T¶B»XV2Oí£j®œN1û‹øÿQ&¨K Ã∑á≥
‹{§TÔ√
0≤vÕâuΩæ7Å<CPHŸÆI$MΩY√e™á¸Ùvϯºãkˆcı@üõw<ü.m$ANr    ¶;Ù*«‡cüXP⁄˘Î@óòéP0yK.aŸò\ÉÛ;óNáÔ†Ω"wÓ‡fA–”uxfiC%O$Å9∆®¯"ÛÅ˙:¯W_hö„¥–§;ê0ÊÂZc]fio∂7Ôç$˘)Æ”x¬»—§Ib•ù˚ϯ∞7÷sœ≈È…   
z`–Æ€
ùˇ€c
x≈∑≤Œ≤∫ã↴&=¸Òd—º7L‘ògIı=èÄnÚ‚†Bn8    Ô?ÀoXl(H+ÉÓ<∫Z1$N¡ç±ÕG≤bâ§%†ˇü¥cwΩ†àpË»fi=Uµ∫πÖ»U“©Æ«<®n~◊VªÑY˜€Q¥ï=“sı~»‚ÄÉG‡nô¡¯Ø®J
ß1…Ì«QAm÷eÁ;}º°¶…∫πÂ∞¶Ë7Û®]ÂcqaÀ7A∑´ÅtõªZäÄ fl≠Fh~ËE◊ÆÂiX”£Ó`»+ÇHÏ”ß<‘`ÑPÎѱ跉¿Ëùfl¸Ùl?k»ı“åÅ:&°$°\˚    †mw`ßx»5àfiÀ
µ‚Í÷߬$´I7ƒXI£O≈z’{ÚH /Ïäu+D.ö¶™˛d    …kâ%‚¬Ùºs∏?…˜*IŒ:êªe¨öóˆÓC0’ÑΩ„l‚÷+òº\zrOM∑Œâ·√∏≥·,l∂[tˆyw3˚r“Ç4.†g£JRrN5IÖ≈¨_∑ds˘„ÖÁ∏B]Iï5x§DH˙jfië±*gÏ~oTmQ∑ÌTƒNòöúè·Ç≤Gœˇ¢_x≈Å©8K*ºiQ•?E‰&k„ÙàG_ôz8Á'övTIø.Å

 

[Edhawk]

Try the EFI attached below.

I have made the following changes:

1. Deleted the ASRock USB SSDT, as you have the XhciPortLimit quirk enabled and the SSDT doesn't look correct for your system.
2. Cleaned up the config.plist.
3. Added the MinDate and MinVersion entries for Catalina to the config.
4. Added a couple of boot arguments and made a few other edits.

See if this EFI will boot your system.

 

[Havakak]

Try the EFI attached below.

I have made the following changes:

1. Deleted the ASRock USB SSDT, as you have the XhciPortLimit quirk enabled and the SSDT doesn't look correct for your system.
2. Cleaned up the config.plist.
3. Added the MinDate and MinVersion entries for Catalina to the config.
4. Added a couple of boot arguments and made a few other edits.

See if this EFI will boot your system.

Thank you for your efforts but still the same. I've attached the logfile itself.

Does it help if I would use the debug version of Opencore?

 

[Edhawk]

OK, I'm not sure why this keeps kernel panicking as the same EFI worked on another (MSI) B450 system.

I have rebuilt the attached EFI from Fresh (OC 1.0.3) for your ASRock B450, R5 3600X & RX 570 system.

Try this EFI and see if this helps.

Just make sure you use the ResetNvramEntry from the OC boot screen (GUI) before booting in to macOS.

• To unhide the drivers in your OC setup press the spacebar while on the OC boot screen and select the ResetNvram icon.
• This will clear any unnecessary NVRAM entries before you boot with the new EFI.

I am assuming you have the Bios set to run macOS, that you haven't cleared the CMOS/Bios between failed attempts.

If you have reset the Bios, then you need to check that the Bios features listed in the link below are set correctly for your AMD system.

Ryzen and Threadripper(17h and 19h) | OpenCore Install Guide

 

[Havakak]

Thank you very much. I'll try it immediately.

Just make sure you use the ResetNvramEntry from the OC boot screen (GUI) before booting in to macOS.

I am resetting the NVRAM via Opencore menu before every boot attempt.

I am assuming you have the Bios set to run macOS, that you haven't cleared the CMOS/Bios between failed attempts.

I have my BIOS settings correct as Dortania's guide mentioned. (secureboot, above4g, fastboot etc.)

 

[Havakak]

Computer freezes in this line. IO PCI Configurator. Could it be about MCEReporter kext?

 

[Edhawk]

No. AppleMCEReporterDisabler.kext is essential for your AMD system to boot macOS. Without it your system will never run macOS.

If you have Above 4G Decoding ENABLED in your Bios, then the npci=0x3000 boot argument needs to be removed from the config.plist, as the two should not be used together.

Revised EFI attached with npci=0x3000 boot argument removed.

 

[Havakak]

Still the same. The funny thing is this computer was running smoothly until I have accidentally deleted my EFI.
By the way I was seeing the boot list like "UEFI: Toshiba Transmemory" etc.
Now I see the boot list as the attached image. This weekend I'll try to build an EFI with the debug version and log everything. Maybe it will help to see what is wrong.

 

[Havakak]

Could it be anything with the PlatformInfo->Generic section. Like SystemUUID or something? Maybe I have inserted something wrong there? I have changed the serial and other stuff because.

 

[Edhawk]

The iMacPro1,1 SMBIOS data in the config.plist looks fine.

Adding the OpenCore boot option to your bios was one of the edits I made to the config.plist, it has nothing to do with the issues that you are experiencing. It simply replaces the UEFI partition option for your macOS or USB Installation drive, with the word OpenCore.

 

[Havakak]

I've rebuilt the EFI with the debug version of OC and set the logging to maximum. After resetting NVRAM it kernel panicked. I've attached the log and the EFI folder.

I can see kexts and SSDT's and patches are loading correctly. I don't know about those meaningless characters. Are they related to kernel panic?

 

[laurent]

there is an error in the kernel patch 0 section
you forgot to set to 06 if you have a ryzen 5 3600x

on the left your patch
on the right what you need to change

 

[Havakak]

Thank you. Still the same. Installation's first phase is OK. After first reboot and seeing "Macos installer" on the local disk and continue to installation(seeing apple logo and progress bar) it resets again. And the same EXITBS:START.

I was using the 2024 beta bios. I reverted to 2022 release which is not beta. same.
I reverted to OC 1.0.2 which I was using before the accident. same.

Last night I just ordered a Mac Mini M4 Pro.

Dear fellow members of AMD-OSX Community, thank you for all your efforts to this day. I am out of this journey.