Jump to content
10 posts in this topic

Recommended Posts

OpenCore 0.8.8 is out now, you can get it from Acidanthera.

Although there are no news in the config.plist file, there are many changes to other OpenCore components. Just take note that almost 40 compilations have been released. They are important changes in code files even if they do not require changes in the configuration file. To get a better and more mature OpenCore.


Main changes

  • Updated AppleKeyboardLayouts.txt from macOS 13.1.
  • Updated builtin firmware versions for SMBIOS.
  • Updated ocvalidate to allow duplicate tool if FullNvramAccess is different.
  • Added .contentVisibility to hide boot entries: exclude entries if there is a .contentVisibility file near the bootloader or inside the boot directory with Disabled contents (ASCII). The entry will become auxiliary if its .contentVisibility file contains Auxiliary.
  • Fixed build on Apple Silicon.
  • Added SD card support for boot device selection.

config.plist

  • Nothing to do.

Kexts

  • AppleALC 1.7.8: added new layouts.
  • FeatureUnlock 1.1.2: unlocked AirPlay to Mac on systems with 'kern.hv_vmm_present' set to as 1 (Ventura and newer).
  • Lilu 1.6.3: added Raptor Lake CPU definitions.
  • VoodooInput 1.1.3: fixes and improvements.
  • VoodooPS2Controller 2.3.3: fixes.
  • WhateverGreen 1.6.3: added GPU identifiers from different Macs.

Note about .contentVisibility (OpenCore now can hide or make auxiliary boot entries)
 
We know that OpenCore hides its own EFI, it means that the EFI of the booting macOS system isn't shown in the picker. But other EFI partitions of not booting macOS systems are always shown in the picker, despite of many users don't like this behaviour and prefer to hide all EFI partitions.
 
OpenCore 0.8.8 has added .contentVisibility to hide boot entries: exclude entries if there is a .contentVisibility file near the bootloader or inside the boot directory with Disabled content (ASCII). The entry will become auxiliary if its .contentVisibility file contains Auxiliary.

Spoiler

contentVisibility.thumb.jpg.66472225150788b06cd9524b6b527d99.jpg

 

By default the .contentVisibility file containing the text Disabled is already placed next to the BOOTx64.efi file. So, you don't have to do anything extra if you want to hide the macOS EFI partitions.

Spoiler

hidden-efi.jpg.8aa3eb0b9fc09c07300dd6e2b88b5c7b.jpg


Thank you again, OpenCore team!!!

Edited by miliuco
  • Like 6
  • Thanks 4

Thanks. I was able to hide Mac OS entries individually and treat them as auxiliary entries in OC Boot Picker by placing .contentVisibility file in

 

APFS -> Preboot -> System -> Library -> CoreServices

HFS -> /System/Library/CoreServices

EFI -> EFI -> BOOT

 

image.thumb.png.40c80af1243100189cbbf8fecaad7c2e.png

 

The hidden entries will only appear by pressing space.

 

 

Edited by AppleBreak
  • Like 3
  • Thanks 1

@AppleBreak

Yes, that's the purpose of this new contentVisibility feature. I have commented in my post on the possibility of hiding or making auxiliary the entries of EFI partitions but, as you have seen, it can be used for any boot entry. I think it's a good feature.

  • Like 4
On 1/3/2023 at 1:57 AM, miliuco said:

FeatureUnlock 1.1.2: unlocked AirPlay to Mac on systems with 'kern.hv_vmm_present' set to as 1 (Ventura and newer).

Anyone can explain this? Pls

i understand Ventura and up has “kern.hv_vmm_present” set 1 default, is it correct? How to check it?

@oldman20

Good question. 

 

All hacks working on Ventura have kern.hv_vmm_present set 1? Or only those with unsupported hardware?

 

In OCLP guide:

 

Reroute kern.hv_vmm_present Patch

  • Reason: Allows macOS to be installed and updated on unsupported hardware
  • Logic: Forces userspace to see system as Virtual Machine
  • Models: Any model using VMM spoofing.
Edited by miliuco
  • Like 1

@oldman20 @miliuco 

I believe the 'kern.hv_vmm_present' here simply refers to its corresponding variable (original value=1) also found to be present in Control Center.app's executable binary file, which was patched (original vmm value replaced with one from Acidanthera) to remove the additional check placed on the blacklisting of said feature (AirPlay To Mac) in macOS Ventura.

Edited by aben
  • Like 1
1 hour ago, aben said:

@oldman20 @miliuco 

I believe the 'kern.hv_vmm_present' here simply refers to its corresponding variable (original value=1) also found to be present in Control Center.app's executable binary file, which was patched (original vmm value replaced with one from Acidanthera) to remove the additional check placed on the blacklisting of said feature (AirPlay To Mac) in macOS Ventura.

So no way to check kern.hv_vmm_present value?

I cant use AirPlay with Intel 3160, is it reason?

1 minute ago, oldman20 said:

So no way to check kern.hv_vmm_present value?

I cant use AirPlay with Intel 3160, is it reason?


Kindly note that 'kern.hv.vmm.present' is not a variable meant for end-users to be able to manipulate/modify; in this particular case the author of the patch simply chose to detail how the patch was implemented for those inclined.

For Continuity features in macOS (AirDrop, HandOff, Universal Control/Clipboard, AirPlay etc), you will require a native Broadcom Wifi+BT combo chipset, more specifically the BCM94360 series: Fenvi T919 for desktops, BCM94360NG for laptops with NGFF/M.2 slot.

  • Like 4
On 1/4/2023 at 9:44 PM, aben said:


Kindly note that 'kern.hv.vmm.present' is not a variable meant for end-users to be able to manipulate/modify; in this particular case the author of the patch simply chose to detail how the patch was implemented for those inclined.

For Continuity features in macOS (AirDrop, HandOff, Universal Control/Clipboard, AirPlay etc), you will require a native Broadcom Wifi+BT combo chipset, more specifically the BCM94360 series: Fenvi T919 for desktops, BCM94360NG for laptops with NGFF/M.2 slot.

I using intel3160 some feature work: universal clipboard (not stable much), handoff ok, airdrop no (of course), only airplay didnt! 

×
×
  • Create New...