Problems with macOS 14.1 Update

[frontgear]

You made a fatal typo. It should've been revpatch=sbvmm.

That's what I have in the boot-args but will blame it on fast fingers

 

[elgipsy]

what do the restrictevents.kext and boot-args do by the way?

 

[elgipsy]

Anyone? And should I keep the kext and boot-args or just use them to install future updates and then remove it? Thanks

 

[craighazan]

Anyone? And should I keep the kext and boot-args or just use them to install future updates and then remove it? Thanks

You can remove the boot args after installation.

 

[elgipsy]

You can remove the boot args after installation.

Thanks, the kext too?

 

[craighazan]

Thanks, the kext too?

You can either disable it in your config or just delete it.

 

[dasboot5]

Is the boot arg only for legacy-patcher and Smbios versions that require the patcher? If you have a ImacPro1,1 Smbios and are on Ventura 13.6.1 will restrictevents allow the upgrade to Sonoma no boot arg, and no legacy patcher use? I am getting a failure to update to Sonoma both from Software Update which will not complete the download and from the Apple store which completes and then fails to update. BTW new version of patcher just released. I have not tried downloading Sonoma separte on anther machine then transferring with a flash over to the machine that is failing to update but my guess is it will still fail to complete the upgade.

 

[craighazan]

There’s also BlueToolFixup that needs to be disabled to a, show the update in System Settings, and b, complete the update. In regards to RestrictEvents, I am not entirely sure how that works with legacy patcher, I’ve just left RestrictEvents in my EFI, weather I need it or not I don’t know. But my understanding is if you have RestrictEvents then use the ‘revpatch=sbvmm’ boot argument. I have a Ryzen APU, so the boot arg I used is ‘revpatch=cpuname,pci,sbvmm’.

 

[dasboot5]

Thank you Craig,
Restrictevents purpose:
Lilu Kernel extension for blocking unwanted processes causing compatibility issues on different hardware and unlocking "the support for certain features restricted to other hardware." The list of blocks currently includes:

• /System/Library/CoreServices/ExpansionSlotNotification
• /System/Library/CoreServices/MemorySlotNotification

Explanation of boot arg for Intel based machined:

• sbvmm - forces VMM SB model, allowing OTA updates for unsupported models on macOS 11.3 or newer

Explanation of boot argument array: revpatch=cpuname,pci,sbvmm for AMD based machined to allow change of CPU name in About this Mac, prevent PCI warnings and add the newly wanted name in the argument:

• revcpuname=value custom CPU brand string (max 48 characters, 20 or less recommended, taken from CPUID otherwise)
• cpuname - custom CPU name in System Information
• pci - prevent PCI configuration warnings in System Settings on MacPro7,1 platforms

 

[frontgear]

Thank you Craig,
Restrictevents purpose:
Lilu Kernel extension for blocking unwanted processes causing compatibility issues on different hardware and unlocking "the support for certain features restricted to other hardware." The list of blocks currently includes:

• /System/Library/CoreServices/ExpansionSlotNotification
• /System/Library/CoreServices/MemorySlotNotification

Explanation of boot arg for Intel based machined:

• sbvmm - forces VMM SB model, allowing OTA updates for unsupported models on macOS 11.3 or newer

Explanation of boot argument array: revpatch=cpuname,pci,sbvmm for AMD based machined to allow change of CPU name in About this Mac, prevent PCI warnings and add the newly wanted name in the argument:

• revcpuname=value custom CPU brand string (max 48 characters, 20 or less recommended, taken from CPUID otherwise)
• cpuname - custom CPU name in System Information
• pci - prevent PCI configuration warnings in System Settings on MacPro7,1 platforms

I want to add something to your post regarding the cpuname boot-arg.

If you want to use the boot-arg -revpatch=cpuname, these settings must be specified:

config.plist → NVRAM → Add → 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 → revcpu = 1
config.plist → NVRAM → Add → 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 → cpuname = your custom CPU name

Or, you can also use these as standalone boot args, but either use this or the -revpatch above:

-revcpuname = your custom CPU name
-revcpu = 1