Jump to content

[GUIDE] How to install macOS 14 Sonoma on Z390 Aorus Elite motherboard using OpenCore


miliuco
 Share

31 posts in this topic

Recommended Posts

Preface

 

Sonoma required fewer changes to OpenCore and kexts than were necessary to install older systems such as Big Sur, which was a big challenge for developers. This time, minor changes allowed Sonoma to be installed almost immediately after the first beta version was released.
Of course, there have been problems to work hard on, not all solved as of today. For now I will note the loss of Wi-Fi with Broadcom chipsets used in Mac models before 2017 and in Fenvi PCI-e cards, widely used in Hackintoshes. A fix has been provided by the OCLP team.

 

Hardware

  • Motherboard Gigabyte Z390 Aorus Elite
  • CPU Intel i9-9900K
  • GPUs: iGPU Intel UHD 630 / AMD Radeon RX 6600 XT
  • Audio Realtek ALC1220
  • Ethernet Intel I219V7
  • Wi-Fi + BT Fenvi FV-T919 (BCM94360CD).

BIOS settings (F10h version)

  • CFG Lock: Disabled
  • CSM: Disabled
  • VT-d: Disabled
  • Fast Boot: Disabled
  • OS Type: Windows 8/10 WHQL
  • Platform Power Management: Disabled
  • XHCI Hand-Off: Enabled
  • Network Stack: Disabled
  • Wake on LAN: Disabled
  • Secure Boot: Disabled
  • Integrated Graphics: Enabled
  • DVMT Pre-allocated: 256M o higher.

What works well?

  • dGPU AMD as main card
  • iGPU in headless mode
  • Shutdown, restart and sleep
  • Ethernet
  • Sound (also HDMI)
  • USB ports (USB port map for this board)
  • Bluetooth Fenvi T919.

What's not working well?

 

Fenvi T919 Wi-Fi: macOS Sonoma has dropped support for all Broadcom Wi-Fi present on Macs before 2017. Fenvi T919 and HB1200 have BCM4360 chipsets (not supported) so Wi-Fi does not work in Sonoma. Bluetooth works fine. This is a serious inconvenience because functions related to the Apple ecosystem (Airdrop, Continuity Camera, etc.) are also lost. A fix is proposed later.

 

Installing macOS Sonoma

 

I have updated macOS Ventura to Sonoma but creating USB boot media to install from scratch is another option for those who prefer to do it that way.

  • It is advisable to have macOS 13.4 Ventura or later
  • System Settings >> Software Update >> Beta Updates >> click on the info icon >> Disabled
  • Choose macOS Sonoma 14.0
  • Or get the app from App Store.

To create the USB installation media so you can install Sonoma from scratch:

  • Get the complete installation package from Apple's servers. I use the app Download Full Installer (original by scriptingosx), main window shows all versions available for download from Big Sur to Sonoma. 
    Spoiler

    DownloadFullInstaller.thumb.png.c441f563bdbce24adb7f9b66e7ae3c33.png

     

  • The package is downloaded as InstallAssistant-14.0-build.number.pkg, double click on the package to generate Install macOS Sonoma.app in the Applications folder
  • Format a USB stick of at least 16Gb with GUID partition scheme and Mac OS Plus (journaled) format, name it (e.g. USB)
  • Open Terminal and run this command
sudo /Applications/Install\ macOS\ Sonoma.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --no-interaction

At the end, you can reboot from the USB device and begin Sonoma installation.

 

OpenCore and EFI folder

 

Update OpenCore and extensions to Sonoma compatible versions. OpenCore, at least version 0.9.4. Settings used with macOS Ventura may work with macOS Sonoma. Updating OpenCore and kexts, there are no significant changes to the config.plist file, which may be the same for both systems.

 

For the update to be successful, 2 parameters in config.plist related to security must be adjusted:

  • SecureBootModel=Default or x86legacy (Apple Secure Boot as Default sets the same model as in SMBIOS and x86legacy is designed for SMBIOS that lack T2 chip and virtual machines)
  • SIP enabled (csr-active-config=00000000).

It is advisable to have Gatekeeper enabled (sudo spctl –master-enable in Terminal).

These security options can be changed after installation as they are not required out of updating macOS.

 

Note: in last versions of Ventura, sudo spctl –master-enable (or disable) has been replaced by sudo spctl –global-enable (or disable). For now, both commands work fine.

 

config.plist

 

I get best results with iMac19.1 SMBIOS and the iGPU enabled in BIOS.

These are the main details when configuring config.plist.

 

ACPI

  • ACPI: SSDT-EC-USBX.aml, SSDT-PLUG.aml and SSDT-PMC.aml. SSDT-AWAC.aml is not required on my system but, if in doubt, add it because it does not cause any harm if it is present without being needed
  • ACPI >> Quirks: all = False

Booter

  • Booter >> Quirks: AvoidRuntimeDefrag, DevirtualiseMmio, ProtectUefiServices, ProvideCustomSlide, RebuildAppleMemoryMap, SetupVirtualMap and SyncRuntimePermissions = True
  • Booter >> ResizeAppleGpuBars=-1

DeviceProperties >> Add

  • PciRoot(0x0)/Pci(0x2,0x0)
    AAPL,ig-platform-id | Data | 0300913E
    device-id | Data | 9B3E0000
    enable-metal | Data | 01000000
    rps-control | Data | 01000000
  • PciRoot(0x0)/Pci(0x1.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)
    unfairgva | Number | 6
  • PciRoot(0x0)/Pci(0x1F,0x3)
    layout-id | Data | 07000000
  • PciRoot(0x0)/Pci(0x14,0x0)
    acpi-wake-type | Data | 01
    acpi-wake-gpe | Data | 6D

Kernel

  • Kernel > Add: Sonoma compatible kexts, Lilu.kext in the first place, UTBMap.kext specific for this motherboard
  • Kernel >> Quirks: CustomSMBIOSGuid, DisableIoMapper, DisableIoMapperMapping, DisableLinkeditJettison, PanicNoKextDump and PowerTimeoutKernelPanic = True
  • Kernel >> Quirks: SetApfsTrimTimeout = 0

Misc

  • Misc >> Boot: HibernateMode=None, PickerAttributes=144, PickerVariant=Default, ShowPicker=True
  • Misc >> Debug: AppleDebug, ApplePanic and DisableWatchDog = True, Target=3
  • Misc >> Security: AllowSetDefault=True, BlacklistAppleUpdate=True, ExposeSensitiveData=6, SecureBootModel=x86legacy or Default

NVRAM

  • WriteFlash=True
  • Add >> 7C436110-AB2A-4BBB-A880-FE41995C9F82:
    boot-args >> agdpmod=pikera
    csr-active-config >> 00000000
    run-efi-updater >> No
  • Delete >> 7C436110-AB2A-4BBB-A880-FE41995C9F82:
    boot-args and csr-active-config

PlatformInfo

  • Generic >> iMac19.1
  • UpdateDataHub, UpdateNVRAM and UpdateSMBIOS = True
  • UpdateSMBIOSMode >> Custom

UEFI

  • UEFI >> Quirks: EnableVectorAcceleration and RequestBootVarRouting = True
  • UEFI >> Quirks >> ResizeGpuBars=-1.

Notes about software updates

 

There are 3 SMBIOS that I can use on my PC: iMac19,1 / iMacPro1,1 / MacPro7,1. My favorite is iMac19.1. Regarding the updates that are notified in Software Update and the size of the update (full or incremental package), there are some conditions to take into account.

 

About obtaining Update notification

  • iMac19.1 model (2019 iMac 27″) lacks a T2 security chip and, when using this SMBIOS model, you receive update notifications
  • iMacPro1,1 (iMac Pro 27″, late 2017) and MacPro7,1 (Mac Pro 2019) models do have a T2 chip and, when using these SMBIOS models, you do not receive update notifications
  • iMacPro1,1 and MacPro7,1 models receive update notifications if configured as vmm (virtual machine): revpatch=sbvmm in boot-args along with RestrictEvents.kext.

About the size of the update (full or incremental)

  • Systems where the OCLP root patch has not been applied or has been reverted:
    - iMac19,1 can get incremental updates
    - iMacPro1,1 and MacPro7,1 require revpatch=sbvmm in boot-args along with RestrictEvents.kext to get incremental updates, without this setting you get full update packages
  • All systems that have the OCLP root patch applied receive full-size updates.

In summary, using iMac19.1 you get update notifications but the updates are full size.

 

After the system is updated, RestrictEvents.kext and the boot argument can be disabled because they are not required for normal Sonoma operation.

 

Broadcom Wi-Fi stops working in Sonoma

 

 

EFI with OpenCore 0.9.5

  • iMac19,1 SMBIOS
  • iGPU enabled in BIOS
  • AMD as main card
  • config.plist as base config, try this by default
  • config-fenvi.plist if you have a Broadcom wifi card supported on Ventura but not on Sonoma (OCLP root patch also needed), it must be renamed to config.plist
  • Add your own serial numbers (they are empty).

 

EFI with OpenCore 0.9.6
 

EFI with OpenCore 0.9.7
 

EFI with OpenCore 0.9.8
 

EFI with OpenCore 0.9.9
 

EFI 0.9.5 Sonoma.zip

Edited by miliuco
Added links to EFIs
  • Like 9
  • Thanks 3
Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...

Hi Miliuco,

Thank you for this fantastic guide.

I was able to install SONOMA 14,2 on my hackintosh similar to your, following your guide.

It works quite everything, except wifi and bluetooth.

I tried to follow your guide DISABLING completely SIP, resetting NVRAM and trying to patch using OCLP , but unfortunately OCLP give me this error message (see picture attached) and don't allow me to patch....

Have you any suggestions ?.

Thank you 

Screenshot 2023-11-21 alle 00.17.52.png

  • Like 1
Link to comment
Share on other sites

1 hour ago, miliuco said:

@scipionems

SIP is wrong in your config.plist. 
Change SIP value to the recommended by OCLP. 
csr-active-config=03080000
 

Hi Miliuco,

thank you for the reply.

Using 03080000, I was able to use OCLP and to patch the root...

But unfortunately when I reboot the computer, my mackintosh go in loop.... starting and starting again... 

I have disabled from the EFI the AMFIPass.KEXT and the boot arg AMFIPASSBETA.... and I used only the boot arg AMFI=0X80 without the kext.... I was able to start again Sonoma , I tried to patch again with OCLP the root and rebooted my hack ... but wifi and bluetooth are still NOT working 😥

Probably for my kind of wifi I need some other kext.... 

Spoiler

 

 

Edited by scipionems
Link to comment
Share on other sites

2 hours ago, miliuco said:

@scipionems

Look for the chipset of the wifi, branch and model can help. To see if it’s included in the list of supported by OCLP. 
And show to me your config.plist. 


 

Hi Miliuco, thank you again.

My chipset is Broadcom BCM94352Z , model DW1560.... branch DELL (I suppose)....

I attach my EFI with config.plist 

EFI.zip

Edited by scipionems
Link to comment
Share on other sites

@scipionems

Config.plist looks fine, SIP value is ok.

 

Your BCM94352Z chipset may be supported but I'm not sure.
OCLP added more chipsets to the list:

  • device-id pci12e4,4357 >> BCM43225
  • device-id pci12e4,43B1 >> BCM4352
  • device-id pci12e4,43B2 >> BCM4352 (2.4 GHz).

I don't know if 4352 and 4352Z are the same chipset with slight differences. In any case, these chipsets also need AirportBrcmFixup, the kexts you currently have are not enough.


Try adding AirportBrcmFixup (Kexts folder and config.plist, after AirPortBrcmNIC.kext), reboot and comment on the result.

 

Important note on Readme.md

Please pay attention

In macOS 11+, class AirPortBrcm4360 has been completely removed. Using of injector kext with such class name and matched vendor-id:device-id blocks loading of original airport kext. To address this issue and keep compatibility with older systems injectors, AirPortBrcm4360 and AirPortBrcmNIC were removed from main Info.plist file. Instead, the two new kext injectors are deployed in PlugIns folder: AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext. You have to block (or remove) AirPortBrcm4360_Injector.kext in 11+. In OpenCore you can specify MaxKernel 19.9.9 for AirPortBrcm4360_Injector.kext.

 

According to this, You must block Sonoma from loading AirPortBrcm4360_Injector.kext and allow AirPortBrcmNIC_Injector.kext, e.g. (only wifi kexts):

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel</key>
	<dict>
		<key>Add</key>
		<array>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>IOSkywalkFamily.kext</string>
				<key>Comment</key>
				<string>IOSkywalkFamily</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/IOSkywalkFamily</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>23.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>IO80211FamilyLegacy.kext</string>
				<key>Comment</key>
				<string>IO80211FamilyLegacy</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/IO80211FamilyLegacy</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>23.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext</string>
				<key>Comment</key>
				<string>AirPortBrcmNIC</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/AirPortBrcmNIC</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>23.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AirportBrcmFixup.kext</string>
				<key>Comment</key>
				<string>Broadcom Wifi Patch</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/AirportBrcmFixup</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>12.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string></string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>20.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcm4360_Injector.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string></string>
				<key>MaxKernel</key>
				<string>19.9.9</string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
		</array>
	</dict>
</dict>
</plist>

 

 

  • Like 1
Link to comment
Share on other sites

Maybe you should try use compatible device properties in config.plist (exactly like print, not change for your device but extract from Hackintool and put parameters)

 

And add this boot args: -lilubetaall -brcmfxbeta 

 

 

device-properties-BRCM4360-Compatible.plist.zip

 

image.png.6d3237bc623b6b9adc6c64bb941f5c4c.png

 

I saw your EFI maybe you need try this kexts, ons by one and try fix Bluetooth 

 

Exclude those was no necessary 

 

image.png.421b9baed64059adbc18b8efed882242.png

 

Edited by Max.1974
  • Like 1
Link to comment
Share on other sites

1 hour ago, miliuco said:

@scipionems

Config.plist looks fine, SIP value is ok.

 

Your BCM94352Z chipset may be supported but I'm not sure.
OCLP added more chipsets to the list:

  • device-id pci12e4,4357 >> BCM43225
  • device-id pci12e4,43B1 >> BCM4352
  • device-id pci12e4,43B2 >> BCM4352 (2.4 GHz).

I don't know if 4352 and 4352Z are the same chipset with slight differences. In any case, these chipsets also need AirportBrcmFixup, the kexts you currently have are not enough.


Try adding AirportBrcmFixup (Kexts folder and config.plist, after AirPortBrcmNIC.kext), reboot and comment on the result.

 

Important note on Readme.md

Please pay attention

In macOS 11+, class AirPortBrcm4360 has been completely removed. Using of injector kext with such class name and matched vendor-id:device-id blocks loading of original airport kext. To address this issue and keep compatibility with older systems injectors, AirPortBrcm4360 and AirPortBrcmNIC were removed from main Info.plist file. Instead, the two new kext injectors are deployed in PlugIns folder: AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext. You have to block (or remove) AirPortBrcm4360_Injector.kext in 11+. In OpenCore you can specify MaxKernel 19.9.9 for AirPortBrcm4360_Injector.kext.

 

According to this, You must block Sonoma from loading AirPortBrcm4360_Injector.kext and allow AirPortBrcmNIC_Injector.kext, e.g. (only wifi kexts):

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel</key>
	<dict>
		<key>Add</key>
		<array>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>IOSkywalkFamily.kext</string>
				<key>Comment</key>
				<string>IOSkywalkFamily</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/IOSkywalkFamily</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>23.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>IO80211FamilyLegacy.kext</string>
				<key>Comment</key>
				<string>IO80211FamilyLegacy</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/IO80211FamilyLegacy</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>23.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext</string>
				<key>Comment</key>
				<string>AirPortBrcmNIC</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/AirPortBrcmNIC</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>23.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AirportBrcmFixup.kext</string>
				<key>Comment</key>
				<string>Broadcom Wifi Patch</string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/AirportBrcmFixup</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>12.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string></string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string>20.0.0</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>Arch</key>
				<string>x86_64</string>
				<key>BundlePath</key>
				<string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcm4360_Injector.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<false/>
				<key>ExecutablePath</key>
				<string></string>
				<key>MaxKernel</key>
				<string>19.9.9</string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
		</array>
	</dict>
</dict>
</plist>

 

 

Hi Miliuco, 

I added AirportBrcm4360Fixup in the kext folder, modified the config.plist, but unfortunately, after rebooting wifi and bluetooth are still NOT working 😥

Link to comment
Share on other sites

4 minutes ago, scipionems said:

Hi Miliuco, 

I added AirportBrcm4360Fixup in the kext folder, modified the config.plist, but unfortunately, after rebooting wifi and bluetooth are still NOT working 😥

 

How did you map your USB ports? Its necessary put Bluetooth Internal 

 

 

Link to comment
Share on other sites

10 minutes ago, Max.1974 said:

Maybe you should try use compatible device properties in config.plist (exactly like print, not change for your device but extract from Hackintool and put parameters)

 

And add this boot args: -lilubetaall -brcmfxbeta 

 

 

device-properties-BRCM4360-Compatible.plist.zip 623 B · 1 download

 

image.png.6d3237bc623b6b9adc6c64bb941f5c4c.png

 

I saw your EFI maybe you need try this kexts, ons by one and try fix Bluetooth 

 

Exclude those was no necessary 

 

image.png.421b9baed64059adbc18b8efed882242.png

 

Hi Max.1974,

I modified the config.plist device properties following your indication, but wifi and bluetooth still not working...

I tried to add the kexts , but I am not able to boot... kernel panic....black screen... 😥

  • Like 1
Link to comment
Share on other sites

Try EFI that im upload above, reset Nvram 

 

Try change your USBports for Usbinjectall + XHCIunsupported and after test remap 

 

Can you extract your DSDT.aml with Hackintool ?

 

 

Edited by Max.1974
Link to comment
Share on other sites

Unfortnely OCLP cause crash on your config.plist, and I suggest you look for old EFI without OCLP modifications and do block Skywalk kext manually 

 

Config again your BIOS from Load Optimal Defaults and another thinks necessary like XHCI enable, update BIOS if needed, disable secure boot, disable 4g Above, disable Legacy ports...check if your wireless card is connected and fine  with another OS, like Linux or Windows.  

Edited by Max.1974
Link to comment
Share on other sites

14 hours ago, makk said:

Seems like Sonoma installs well 

 

@Max.1974 how was the install on Raptor Lake?

 

I have Alder Lake 12600KF core i5 B660 board Gigabyte

 

 

Hi my friend, you can try use the same, im almost sure that my EFI is config to Alder Lake first 

 

I have same new Computer exactly your config, to my Son, but he not like use Hackintosh, so he has GTX 3060 Nvidia... 😆

 

If you want try my little "old" EFI (need update OC) is generic SMBIOS iMacPro1,1. 

 

:superman:

 

Or you can try my Update OC 0.9.7 Compiled 

 

Need exclude SSDT-RHUB if not works for you! 

 

 

 

 

 

OC 097 AORUS GIGABYTE Z790 ELITE AX.zip

Edited by Max.1974
  • Like 2
Link to comment
Share on other sites

20 hours ago, Max.1974 said:

 

 

Hi my friend, you can try use the same, im almost sure that my EFI is config to Alder Lake first 

 

I have same new Computer exactly your config, to my Son, but he not like use Hackintosh, so he has GTX 3060 Nvidia... 😆

 

If you want try my little "old" EFI (need update OC) is generic SMBIOS iMacPro1,1. 

 

:superman:

 

Or you can try my Update OC 0.9.7 Compiled 

 

Need exclude SSDT-RHUB if not works for you! 

 

 

 

 

 

OC 097 AORUS GIGABYTE Z790 ELITE AX.zip 35.76 MB · 0 downloads

 

Max.1974, thanks! 

 

Is that a OC Mod version you have ?

 

 

this board B660 is a new one for me. I got rid of the Z690 board didn't need all the xtras used a lot of power. 900watts

 

 

 

 

 

 

 

 

 

 

Edited by makk
  • Like 1
Link to comment
Share on other sites

@Max.1974 this works!

 

the sound now blasts thru the speakers of OC Menu.  haha. love it.

For the moment am running OC on desktop with just Windows 11 /10


I have the Nvidia Geforce RTX 3050.  And OC boots with it. to get past it, need drivers, however, this guy here was able to have QE/CL no GL working with Pascal. GTX 1050Ti.

the i5 12600KF > KF doesn't have the integrated GPU of Intel. So at the moment cannot install MacOS on here.

 

On the Desktop:

I have the intel bluetooth which is 0AA7 Rev 0001.  have no clue which model on the desktop. 

wifi is blocked by fans and water cooler.  pain to get to.

for wifi the Intel Dual Band AC-3168 the older wifi 5 on the desktop.

 

To keep with older MacOS using the older Intel Wifi/BT combos, don't know how to get the bluetooth to work right on Monterey on desktop.


I've looked at your kexts but I don't think I can use the Bluetooth one ?

 

My laptop is running Monterey with no bluetooth has the older Intel Wifi/BT combo on it. Wifi works fine. At one point the Bluetooth came on line but I could not connect to my iPhone.
Was able to connect to Windows Bluetooth and other bluethooth.

 

what kexts work for Intel Bluetooth on Monterey? 

 

  • Like 1
Link to comment
Share on other sites

@makk

 

"i5 12600KF > KF doesn't have the integrated GPU" >> Even if it have iGPU, iGPUs of this CPU generation aren't supported by macOS at all, a dedicated GPU is mandatory.

GTX 1050Ti works just up High Sierra, you can't have any newer macOS with this card.

 RTX 3050 unsupported, nothing to do on this side.

 

I do't know what your bluetooth is, if it's Intel take a look here:

https://github.com/OpenIntelWireless

 

Edited by miliuco
  • Thanks 1
Link to comment
Share on other sites

Em 29/11/2023 às 17:18, makk disse:

@Max.1974isso funciona!

 

o som agora explode através dos alto-falantes do OC Menu. haha. adorei.

No momento, estou executando o OC na área de trabalho com apenas o Windows 11 /10


Eu tenho o Nvidia Geforce RTX 3050. E OC boots com ele. para passar por isso, preciso de motoristas, no entanto, esse cara aqui conseguiu ter QE/CL sem GL trabalhando com Pascal. GTX 1050Ti.

o i5 12600KF > KF não tem a GPU integrada da Intel. Então, no momento, não é possível instalar o MacOS aqui.

 

Na área de trabalho:

Eu tenho o intel bluetooth que é 0AA7 Rev 0001. Não tenho ideia de qual modelo na área de trabalho.

o wifi está bloqueado por ventiladores e refrigerador de água. dor para chegar.

para wifi o Intel Dual Band AC-3168o wifi 5 mais antigo na área de trabalho.

 

Para manter o MacOS mais antigo usando os combos Intel Wifi/BT mais antigos, não sei como fazer o bluetooth funcionar diretamente no Monterey na área de trabalho.


Eu olhei para os seus kexts, mas acho que não posso usar o Bluetooth?

 

Meu laptop está rodando Monterey sem bluetooth, tem a combinação Intel Wifi/BT mais antiga. Wifi funciona bem. Em um ponto, o Bluetooth entrou em linha, mas eu não consegui me conectar ao meu iPhone.
Consegui me conectar ao Windows Bluetooth e outros bluethooth.

 

quais kexts funcionam para Intel Bluetooth em Monterey?

 

 

Hi my friend, so glad to help you!! Now you can use this kexts for specific macOs like Monterey, and you need change parameters on your config.plist and Opencore Cofigurator 

 

Check here the Kexts choose better for you system. 

 

https://github.com/OpenIntelWireless/itlwm/releases/tag/v2.2.0

 

 

But for Sonoma need use this Preview 5 

 

https://github.com/OpenIntelWireless/itlwm/releases/tag/v2.2.0 

 

If you have some difficulties send me PM. 

 

Sorry late its because my job 

 

 

 

 

Link to comment
Share on other sites

 Share

×
×
  • Create New...