Contribute
Register

Monterey desktop installation stuck at [EB|LOG:EXITBS:START]

Thanks for your reply.

I am still confused as to how to make these changes.

When comparing my .plist to sample.plist:

I checked every "quirks" folder in the .plist file but I am not able to find CustomPciSerialDevice nor am I able to find how or where to add it.
you open your config.plist (use PlistEditPro) and then the sample.plist side by side, search for example CustomPciSerialDevice in the sample.plist, if it is there, then add it in to your config.plist, if it is not, then remove from yours

repeat until you get no errors
 
you open your config.plist (use PlistEditPro) and then the sample.plist side by side, search for example CustomPciSerialDevice in the sample.plist, if it is there, then add it in to your config.plist, if it is not, then remove from yours

repeat until you get no errors
Ok thank you for clarifying!!
 
When I edited the .plist file for the first error and then re-ran ocvalidate, the error is still there:

OCS: Missing key CustomPciSerialDevice, context <Quirks>!


*and* now there is an additional error:


OCS: No schema for CustomPciSerialDevice at 20 index, context <Quirks>!

Is this a normal result?


(in the attached image: my plist on the left and the sample plist on the right)
 

Attachments

  • Screen Shot 2022-09-25 at 11.23.27 AM.png
    Screen Shot 2022-09-25 at 11.23.27 AM.png
    547.1 KB · Views: 32
Thanks for your reply.

I am still confused as to how to make these changes.

When comparing my .plist to sample.plist:

I checked every "quirks" folder in the .plist file but I am not able to find CustomPciSerialDevice nor am I able to find how or where to add it.

What @Feartech says is correct though.

These errors are still caused by differences between OpenCore versions.

So, when you think about it, you are missing the CustomPciSerialDevice key.

It is definitely there in OC 0.8.4 in the Kernel section. I have just checked for you. :thumbup:
 
When I edited the .plist file for the first error and then re-ran ocvalidate, the error is still there:

OCS: Missing key CustomPciSerialDevice, context <Quirks>!


*and* now there is an additional error:


OCS: No schema for CustomPciSerialDevice at 20 index, context <Quirks>!

Is this a normal result?


(in the attached image: my plist on the left and the sample plist on the right)
make sure you are using the correct version of ocvalidate for your opencore version

make sure when/if you upgraded opencore that you copied all the needed files

maybe zip and upload your EFI
 
What @Feartech says is correct though.

These errors are still caused by differences between OpenCore versions.

So, when you think about it, you are missing the CustomPciSerialDevice key.

It is definitely there in OC 0.8.4 in the Kernel section. I have just checked for you. :thumbup:
Ok I do see it in the Kernel section in the sample.plist file, but when I added the "child" that's when I received an additional error while also maintaining that same error.

I will follow up on Feartech's recent comment and see if that works.
 
make sure you are using the correct version of ocvalidate for your opencore version

make sure when/if you upgraded opencore that you copied all the needed files

maybe zip and upload your EFI
ocvalidate and opencore definitely match - 0.8.4 debug for both.

The original .plist file that I am working from was uploaded by another member here who had the same build as me. I had hoped that this would save time by working from their existing edits, given that they also mapped usb and created a custom kext for usb.

This user was definitely working from an older version of opencore, 0.7.x - and it seems that this might be the issue.

I performed a search just now but I am not showing any instructions on how to "merge" the older .plist file that I have with the updated sample.plist file that has been provided in the newest OC 0.8.4 release.
Is this even a good idea to merge the two?
Or should I go through line by line and add edits from my current .plist to the OC 0.8.4 .plist and rebuild it with the edits?

Lastly, I have zipped and included my efi below as requested.
 

Attachments

  • EFI.zip
    4 MB · Views: 43
ocvalidate and opencore definitely match - 0.8.4 debug for both.

The original .plist file that I am working from was uploaded by another member here who had the same build as me. I had hoped that this would save time by working from their existing edits, given that they also mapped usb and created a custom kext for usb.

This user was definitely working from an older version of opencore, 0.7.x - and it seems that this might be the issue.

I performed a search just now but I am not showing any instructions on how to "merge" the older .plist file that I have with the updated sample.plist file that has been provided in the newest OC 0.8.4 release.
Is this even a good idea to merge the two?
Or should I go through line by line and add edits from my current .plist to the OC 0.8.4 .plist and rebuild it with the edits?

Lastly, I have zipped and included my efi below as requested.
you don't merge the files, you edit/copy and paste the information over

and it is a better idea to create your own USBPorts.kext as you may have a different setup
 
ocvalidate and opencore definitely match - 0.8.4 debug for both.

The original .plist file that I am working from was uploaded by another member here who had the same build as me. I had hoped that this would save time by working from their existing edits, given that they also mapped usb and created a custom kext for usb.

This user was definitely working from an older version of opencore, 0.7.x - and it seems that this might be the issue.

I performed a search just now but I am not showing any instructions on how to "merge" the older .plist file that I have with the updated sample.plist file that has been provided in the newest OC 0.8.4 release.
Is this even a good idea to merge the two?
Or should I go through line by line and add edits from my current .plist to the OC 0.8.4 .plist and rebuild it with the edits?

Lastly, I have zipped and included my efi below as requested.
also you have placed CustomPciSerialDevice in the wrong place....
 
also you have placed CustomPciSerialDevice in the wrong place....
Ok I have started all over again, with OC 0.8.3 debug

ocvalidate now shows no errors

I am encountering this error in my log now when I try to boot:

39:210 00:051 AAPL: #[EB.RH.LRH|P!] Err(0xE) <- EB.LD.LF
39:261 00:050 AAPL: #[EB.BST.FBS|!] Err(0xE) <- EB.RH.LRH
39:312 00:051 OCSMC: SmcReadValue Key 4D535463 Size 1
39:363 00:050 OCSMC: SmcReadValue Key 4D534163 Size 2
39:415 00:051 AAPL: #[EB|LOG:DT] 2022-10-02T07:39:53
39:466 00:051 AAPL: #[EB|LOG:EXITBS:START] 2022-10-02T07:39:53


+ newest .plist file attached

+ image of the verbose error where I am getting stuck.

Thank you!!
 

Attachments

  • config.plist
    44.2 KB · Views: 21
  • ss1.jpeg
    ss1.jpeg
    254 KB · Views: 36
Last edited:
Back
Top