- Joined
- Jun 2, 2020
- Messages
- 105
Hi there. Sonoma 14.3 update is live. Is it safe to update or do we need to make any chages to the kernel patches or config.plist...?
I am on latest OC 0.97.
Thanks!
I am on latest OC 0.97.
Thanks!
it works for me. thank you, with my EFI OC 097 untouched, no boot arg added.Just download the installer from the App Store and run that. It will download from the Software Update prefs pane, and give an error when it tries to update, so just exit and run the installer app from the Applications folder. No mods or patches or boot args necessary.
Just download the installer from the App Store and run that. It will download from the Software Update prefs pane, and give an error when it tries to update, so just exit and run the installer app from the Applications folder. No mods or patches or boot args necessary.
Thank you so much. I amended my config plist according to your instructions and now the cpu name is shown correctly in the "about Mac".Installing/adding RestricEvents.kext is sometimes not enough. In that there are options available to make sure you have the correct CPU, Memory & PCI elements set in your config.plist. These can either be by using boot arguments or Nvram entries.
For example the NVRAM section of my Ryzen 7 5700G/Asus TUF Gaming B550M/RX 5700 XT system looks like this.
View attachment 13205
You will note that both the ADD and DELETE 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 sections are populated with additional entries. These are options available when using RestrictEvents.kext that will help the system use the correct CPU name, MEM and PCI attributes if using the MacPro7,1 SMBIOS and allow OTA updates. I have also added a custom CPU name, using the revcpuname option. This CPU name carries through to the About this Mac and System Settings tabs, as shown below.
Thanks! I've missed that. I will delete the -lilubetaall entry.That looks Ok as far as the RestrictEvent entries in the NVRAM section.
You don't need -lilubetall boot argument, as you are not using a beta release of the OS. Doesn't help you have mis-spelt the boot argument (-lilubetaall) either, as the entry you are using is missing the second letter 'a'.