[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[BOTMT]

The backup procedure for Big Sur is the same as for Catalina. There is one weird thing to note about Big Sur, however:

• The first backup of Big Sur uses Apple's "APFS Replication" tool to duplicate both the System and User volumes.
• The second and all subsequent backups will only clone the User volume.
• So if the first backup was done with Big Sur 11.3, for example, and you make another backup after installing Big Sur 11.4, the System volume on the backup disk will still be 11.3.
  • If you would like to backup 11.4 to the same backup disk, it will be necessary to erase the backup disk in Disk Utility and then run CCC again.

Update: Modified the Carbon Copy Cloner guide:

View attachment 517771

I just purchased CCC 5 at CaseySJ's recommendation, and just made my first Clone with it. In reading some of the documentation, what they advise is to boot off of the clone, and then you can run the Apple updates on it. They also suggest that you can wait until you have a need to restore from the clone, and at that time install all the updates before migrating it back.

Doing this they say will avoid the scenario where you would have to erase, and thereby lose your backup.

 

[BOTMT]

@CaseySJ

I wanted to back-up my EFI drive with CCC (is this not a good approach?). I used HackinDROM App to mount the EFI, but when I select it in CCC, I get an error, and I don't now how to resolve the issue.

Have you run into this or know how to resolve? There is a process in CCC for changing the UUID, but my "EFI-GIG-236" mounted drive does not even show up in the left hand pain of CCC. It DOES show up when I try to select it as my source, but when I select it, that's when I receive the error.

Thank you!

 

[joostiphone]

@CaseySJ I'm not sure if it's asked before, but can we have a micro-guide on the OpenIntelWireless using either Itlwm or AirportItlwm in combination with Heliport? I'm not sure how to configure the config.plist for this.

https://openintelwireless.github.io

https://github.com/OpenIntelWireless

I think the current micro-guide on the start-post is outdated since the driver evolved:

 

[CaseySJ]

@CaseySJ

I wanted to back-up my EFI drive with CCC (is this not a good approach?). I used HackinDROM App to mount the EFI, but when I select it in CCC, I get an error, and I don't now how to resolve the issue.

Have you run into this or know how to resolve? There is a process in CCC for changing the UUID, but my "EFI-GIG-236" mounted drive does not even show up in the left hand pain of CCC. It DOES show up when I try to select it as my source, but when I select it, that's when I receive the error.

Thank you!

Please see the CCC backup mini-guide found in the Quick Reference spoiler. As explained there, we need to add EFIClone.sh as a post-backup task.

 

[archalys]

I have used those RAID cards (I still have a few). Have you checked to make sure the firmware and drivers are the very latest?

Yes, it was actually resolved by Highpoint support. I posted their updated driver shortly after that post. I issue appears to be resolved in current versions

 

[CaseySJ]

** Mini Guide for Configuring OpenIntelWireless Drivers in OpenCore **
Please do not quote this guide in its entirety. Post a link or excerpt instead.​

Background:
Although a Broadcom-based WiFi/Bluetooth module is still highly recommended because it enables all Handoff / Continuity features of macOS, an open source set of Intel WiFi/Bluetooth drivers is available in beta and alpha forms. The drivers are developed and maintained in the OpenIntelWireless repository on GitHub.

Caveats:
These drivers are still in development and do not support all features of macOS. Always refer to the release notes on GitHub for up date information. Any Bluetooth device connectivity problem or WiFi network connectivity problem or signal stability problem should be reported to the developers on GitHub according to their problem-reporting guidelines. No technical support is provided here other than for configuring the drivers into an OpenCore EFI.

Prerequisites:
First ensure that the system contains only one Intel WiFi/Bluetooth module and no Broadcom modules. Physically remove any Fenvi, YOUBO, ABWB or other Broadcom device.

Then check the Compatibility page to determine whether your Intel module is supported. The Intel modules on the following boards are supported:

• Gigabyte Z390 Designare
• Gigabyte Z490 Vision D

In addition, any PCIe add-in-card with an Intel AX-200 module is supported, such as Fenvi FV-AX3000. Many more modules are also supported, but Intel AX-210 is not yet on the list.

General Installation:

• Bluetooth operates over a USB port so we must ensure that the correct port is defined in the USB port map. On Gigabyte Z390 Designare and Gigabyte Z490 Vision D, the internal Intel Bluetooth module is connected to USB port HS14.
• The Intel WiFi module must not be hidden from macOS or disabled in BIOS. On the Gigabyte Z390 Designare the Intel WiFi module is hidden from macOS by SSDT-SSDT-DESIGNARE-Z390-NO-CNVW.aml. This SSDT must be disabled so that macOS can detect the Intel WiFi module. On the Gigabyte Z490 Vision D the Intel WiFi module is always visible to macOS and no such SSDT exists.
• The OpenCore parameter SecureBootModel must be set to Default (Mojave, Catalina) but can be set to either Default or Disabled in Big Sur. This parameter is located in Misc --> Security.

Bluetooth Driver Installation:

• The latest Bluetooth drivers are available from here by downloading the .zip file.
• Inside the ZIP are two files:
  • IntelBluetoothInjector.kext
  • IntelBluetoothFirmware.kext
• These files must be copied to EFI/OC/Kexts folder and references to them must be added to config.plist --> Kernel section in the order shown:

BundlePath	Comment	ExecutablePath	PlistPath	Enabled
IntelBluetoothInjector.kext	Intel BT	Contents/MacOS/IntelBluetoothInjector	Contents/Info.plist	true
IntelBluetoothFirmware.kext	Intel BT	Contents/MacOS/IntelBluetoothFirmware	Contents/Info.plist	true

WiFi Driver Installation:

• The latest WiFi drivers are available from here by downloading the file for the appropriate version of macOS.

• Because the name of the kext is the same (AirportItlwm.kext) for all supported versions of macOS, a good practice is to rename each file after downloading. For example:
  • After downloading the Big Sur version, rename it to AirportItlwm-Big-Sur.kext
  • After downloading the Catalina version, rename it to AirportItlwm-Catalina.kext
  • After downloading the Mojave version, rename it to AirportItlwm-Mojave.kext
• These renamed files must be copied to EFI/OC/Kexts folder and references to them must be added to config.plist --> Kernel section as shown:

BundlePath	Comment	ExecutablePath	PlistPath	MinKernel	MaxKernel	Enabled
AirportItlwm-Mojave	Intel WiFi	Contents/MacOS/AirportItlwm	Contents/Info.plist	18.0.0	18.99.99	true
AirportItlwm-Catalina	Intel WiFi	Contents/MacOS/AirportItlwm	Contents/Info.plist	19.0.0	19.99.99	true
AirportItlwm-Big-Sur	Intel WiFi	Contents/MacOS/AirportItlwm	Contents/Info.plist	20.0.0	20.99.99	true

• Notice in this example that all three Kexts are present and enabled at the same time. This is correct and valid because the MinKernel and MaxKernel columns will inject the correct version automatically. This is known as conditional injection.
  • Mojave kernel versions are 18.0.0 to 18.99.99
  • Catalina kernel versions are 19.0.0 to 19.99.99
  • Big Sur kernel versions are 20.0.0 to 20.99.99

Finishing Touches:
After making the changes, reboot and log back into macOS. Determine if the Bluetooth and WiFi drivers are running by checking System Information --> Bluetooth and System Information --> WiFi.

• For Bluetooth, check if Manufacturer is Intel and Connectable is Yes.
• For WiFi, check if Firmware Version begins with itlwm.

 

[CaseySJ]

@CaseySJ I'm not sure if it's asked before, but can we have a micro-guide on the OpenIntelWireless using either Itlwm or AirportItlwm in combination with Heliport? I'm not sure how to configure the config.plist for this.

https://openintelwireless.github.io

https://github.com/OpenIntelWireless

I think the current micro-guide on the start-post is outdated since the driver evolved:

Done.

 

[joostiphone]

Done.

Blazing-fast as always. Thanks!

 

[trs96]

So does this mean one of these ultra low cost Intel Cards will work in a Dell Optiplex 9010/9020 USFF ?
Everything except for Continuity and Handoff ?

Intel Wireless-AC 7260HMW Network Card Mini PCIE Wifi Adapter Bluetooth 4.0 Card | eBay

Dual Mode Bluetooth 4.0. Bluetooth Version: 4.0. Integrated Bluetooth: Yes. Wi-Fi CERTIFIED : 802.11ac. Bands: 2.4 GHz, 5 GHz. TX/RX Streams: 2x2. Networking Specifications. Windows 7, 32-bit , Windows 7, 64-bit , Linux .

www.ebay.com

 

[CaseySJ]

So does this mean one of these ultra low cost Intel Cards will work in a Dell Optiplex 9010/9020 USFF ?

Intel Wireless-AC 7260HMW Network Card Mini PCIE Wifi Adapter Bluetooth 4.0 Card | eBay

Dual Mode Bluetooth 4.0. Bluetooth Version: 4.0. Integrated Bluetooth: Yes. Wi-Fi CERTIFIED : 802.11ac. Bands: 2.4 GHz, 5 GHz. TX/RX Streams: 2x2. Networking Specifications. Windows 7, 32-bit , Windows 7, 64-bit , Linux .

www.ebay.com

From the Compatibility page:

Chances are good...