Still unknown CPU with OC 1.0.3

[Danish297]

Hi Everyone,

I’ve updated my OC to version 1.0.3, but my CPU is still showing as "unknown."
What settings do I need to adjust in 1.0.3 to ensure my Intel Raptor Lake CPU is correctly detected?

 

[Edhawk]

Updating the version OpenCore you are using doesn't fix the 'Unkown' CPU error.

You need to add the latest release of RestrictEvents.kext to your /EFI/OC/Kexts folder with a corresponding entry for the kext in your config.plist.
Then you need to use the NVRAM > Add and Delete option to set your system CPU with the correct name.

GitHub - acidanthera/RestrictEvents

Contribute to acidanthera/RestrictEvents development by creating an account on GitHub.

github.com

Here is an example of the RestrictEvents.kext NVRAM entries for my AMD CPU.

RestrictEvent Entries in Add & Delete NVRAM sections highlighted.

Obviously you would need to change the CPU name to match your CPU.

 

[Danish297]

Updating the version OpenCore you are using doesn't fix the 'Unkown' CPU error.

You need to add the latest release of RestrictEvents.kext to your /EFI/OC/Kexts folder with a corresponding entry for the kext in your config.plist.
Then you need to use the NVRAM > Add and Delete option to set your system CPU with the correct name.

GitHub - acidanthera/RestrictEvents

Contribute to acidanthera/RestrictEvents development by creating an account on GitHub.

github.com

Here is an example of the RestrictEvents.kext NVRAM entries for my AMD CPU.

View attachment 15816 RestrictEvent Entries in Add & Delete NVRAM sections highlighted.

Obviously you would need to change the CPU name to match your CPU.

@Edhawk I tried this but no luck.

As of the OC 1.0.3 release, should it automatically detect my CPU (Intel i9 14900K)? Please correct me if I'm mistaken.


I've attached my config file as well. Could you take a look and let me know if I missed anything?

 

[Edhawk]

Yes it should, but it obviously doesn’t. So something else needs to change for the correct CPU name to show.

Have you enabled the ProvideCurrentCpuInfo quirk in your config.plist?

 

[Danish297]

Yes it should, but it obviously doesn’t. So something else needs to change for the correct CPU name to show.

Have you enabled the ProvideCurrentCpuInfo quirk in your config.plist?

Yes it's enabled.

 

[Edhawk]

Post a copy of your whole EFI, as the config on its own isn't sufficient for troubleshooting issues.

 

[Danish297]

Post a copy of your whole EFI, as the config on its own isn't sufficient for troubleshooting issues.

here is my whole EFI folder.

 

[Edhawk]

I see a couple of issues that need attention.

1. You have a Boot Argument and NVRAM entry for 'revpatch', which should never be the case. The Boot argument will take precedence over the NVRAM entry, so only one of the two NVRAM RestrictEvents fixes will be implemented in your config.
   1. Current NVRAM section in your config.
   2. Revised NVRAM section - 3 x Boot arguments removed as not required.
2. You have 3 x USB ports set with the Connector Type 8 in your USBPorts.kext. This is wrong, unless you computer has suddenly become a Phone. As the only time the Connector Type 8 is required would be with a Type-C USB2 port on a phone.
   1. Current USBPorts.kext/Contents/Info.plist, with 3 x ports highlighted.
   2. These 3 x ports in the SSxx section of the kext should either be USB3 or Type-C + Switch (9) to Type-C (10) no switch.
   3. Revised USBPorts.kext/Contents/Info.plist, with 3 x ports highlighted and set as USB3 with connector type 3 not 8.
   4. If they are Type-C ports then you need to confirm which Type-C port type needs to be used.
   5. USB Port connector types
   6. Along with having a custom USBPorts.kext for your system you also have the Kernel > Quirks > XhciPortLimit entry enabled. This shouldn't be enabled when a custom USB kext is present.
      1. XhciPortLimit Quirk is currently 'Enabled'
      2. XhciPortLimit quirk is now 'Disabled'

Revised USBPorts.kext and config.plist are present in the EFI attached below.

Give it a try and see if this helps.

 

[miZhiDr63]

Are you sure RestrictEvents.kext is loaded?

 

[Edhawk]

Are you sure RestrictEvents.kext is loaded?

Your question is out of context with the progress of this thread.

1. Who were you asking if the kext was loaded?
2. Are you using the latest version of ResetEvents.kext v1.1.5?
   1. https://github.com/acidanthera/RestrictEvents/releases/tag/1.1.5
3. If you are finding that the kext isn't loading or more likely that the NVRAM entries are not being implemented, try using the ResetNvram option from the OC boot screen to see if that helps.