[EB|#LOG:EXITBS:START] on Ryzen 5 2600

1van4o123

New member
AMD OS X Member
Joined
Jan 8, 2024
Messages
4
I'm stuck with an error when trying to boot from a USB drive: [EB|#LOG:EXITBS:START]. I've created my own EFI twice following the Opencore guide and tried different EFIs, but no luck.
My computes specifications:

CPU: Ryzen 5 2600
GPU: Asus RX 6600 8GB
Motherboard: X370M-HDV
RAM: Kingston FURY Beast 32 GB (2 x 16 GB) DDR4-3200MHz
Storage : Kingston A1000 240 GB M.2-2280
 

Attachments

  • EFI.zip
    4.1 MB · Views: 4
  • IMG_3100.jpg
    IMG_3100.jpg
    718.3 KB · Views: 7
  • opencore-2024-01-09-162751.txt
    256 KB · Views: 2

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,513
Issues in your config.plist:

Kernel > Add section:
Lilu.kext should be loaded before VirtualSMC.kext. Your config has then in the wrong order with VirtualSMC.kext first in the list of kexts.

Screenshot 2024-01-09 at 19.55.34.png Current Kext order

Screenshot 2024-01-09 at 19.55.51.png Correct Kext oder.

Kernel > Emulate section:

You have set MaxKernel and MinKernel in the Emulate section of your config, this is not correct. These two entries should be blank/empty.

Screenshot 2024-01-09 at 19.56.49.png Populated MaxKernel & MinKernel entries - incorrect option

Screenshot 2024-01-09 at 19.58.24.png Empty/Blank MaxKernel & MinKernel entries - correct option.

Kernel > Quirks section:

You have Kernel > Quirks > XhciPortLimit entry set as true/enabled. This is incorrect when you have a custom USB configuration, such as the UTBMap.kext you have in your setup.

Screenshot 2024-01-09 at 20.01.56.png Incorrect XhciPortLimit setting in your current config.plist

Screenshot 2024-01-09 at 20.02.10.png Correct XhciPortLimit setting when using USBPorts.kext/USBMap.kext or UTBMap.kext

I have attached a revised config.plist for you to try.

It contains the items mentioned above, plus I have cleaned up and removed a number of unnecessary entries, to make your config easier to navigate and read.

See if this helps.
 

Attachments

  • config.plist.zip
    5.9 KB · Views: 2

1van4o123

New member
AMD OS X Member
Joined
Jan 8, 2024
Messages
4
Unfortunately, it didn't work. Here are the logs from it.
 

Attachments

  • opencore-2024-01-09-224007.txt
    256 KB · Views: 3

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,513
I don't see anything in the OC log that indicates where the system kernel panic'd.

Questions:
  1. What did the Verbose text show?
  2. Did the system end up on a black screen? or
  3. Did it automatically reboot?
  4. How many drives do you have installed in the system?
  5. Have you tried booting the macOS Installer with just the drive you plan to install macOS on connected?
 

Shaneee

The AMD Guy
Staff member
Administrator
Joined
Mar 13, 2020
Messages
2,213
Unsure if it would halt it there or in the kernel but it's not gonna help,

Code:
130:908 00:057 OCAK: Failed to pk find com.apple.driver.AppleIntelCPUPowerManagement - Not Found
130:945 00:036 OCAK: [OK] Skipping dummy AppleIntelCPUPowerManagement patch on 220500
 

1van4o123

New member
AMD OS X Member
Joined
Jan 8, 2024
Messages
4
I don't see anything in the OC log that indicates where the system kernel panic'd.

Questions:
  1. What did the Verbose text show?
  2. Did the system end up on a black screen? or
  3. Did it automatically reboot?
  4. How many drives do you have installed in the system?
  5. Have you tried booting the macOS Installer with just the drive you plan to install macOS on connected?
Attached an image, unsure if it includes verbose text, but sharing just in case.
The system neither ended up on blackscreen nor automatically rebooted. It just got to the error message and didn't do anything more.
I have only the SSD mentioned above (Kingston A1000 240 GB M.2-2280).
I haven't tried booting it only on my SSD since I haven't heard this method.
 

Attachments

  • IMG_3111.jpg
    3.6 MB · Views: 6

1van4o123

New member
AMD OS X Member
Joined
Jan 8, 2024
Messages
4
I don't see anything in the OC log that indicates where the system kernel panic'd.

Questions:
  1. What did the Verbose text show?
  2. Did the system end up on a black screen? or
  3. Did it automatically reboot?
  4. How many drives do you have installed in the system?
  5. Have you tried booting the macOS Installer with just the drive you plan to install macOS on connected?
Any ideas?
 
Back
Top Bottom
  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.