You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: details/thunderbolt-3-fix-part-3.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ After splicing the NUC's TI firmware into the iMac's update file and flashing it
40
40
41
41

42
42
43
-
The next step is to create a live-patcher so we do not have to depend on Intel's firmware updater on Windows or Linux to update. Instead of reversing Intel's update protocol, we instead just implement TI's update protocol, which is [well documented](http://www.ti.com/lit/pdf/slva783). The two share a single SPI chip so we can use TI's I2C interface to write to the shared SPI memory. An additional advantage of this is that even if we brick the Ridge, we can always recover though the TI controller \(as long as we make sure never to touch TI's firmware\). The patcher utility can be [found here](https://github.com/osy/ThunderboltPatcher). It requires some [secret](https://github.com/osy/HaC-Mini/blob/e3c95882e72f4e93585017909fc3824d04260188/OC/config.plist#L231-L240) [sauce](https://github.com/osy/HaC-Mini/blob/e3c95882e72f4e93585017909fc3824d04260188/ACPI/SSDT-Hpm.asl) to get the OSX drivers to recognize the TI controller. In the end, we only needed to patch [9 locations](https://github.com/osy/ThunderboltPatcher/blob/master/Patches/NUC_Hades_Canyon_Apple_Mode.plist).
43
+
The next step is to create a live-patcher so we do not have to depend on Intel's firmware updater on Windows or Linux to update. Instead of reversing Intel's update protocol, we instead just implement TI's update protocol, which is [well documented](http://www.ti.com/lit/pdf/slva783). The two share a single SPI chip so we can use TI's I2C interface to write to the shared SPI memory. An additional advantage of this is that even if we brick the Ridge, we can always recover though the TI controller \(as long as we make sure never to touch TI's firmware\). The patcher utility can be [found here](https://github.com/osy86/ThunderboltPatcher). It requires some [secret](https://github.com/osy86/HaC-Mini/blob/e3c95882e72f4e93585017909fc3824d04260188/OC/config.plist#L231-L240) [sauce](https://github.com/osy86/HaC-Mini/blob/e3c95882e72f4e93585017909fc3824d04260188/ACPI/SSDT-Hpm.asl) to get the OSX drivers to recognize the TI controller. In the end, we only needed to patch [9 locations](https://github.com/osy86/ThunderboltPatcher/blob/master/Patches/NUC_Hades_Canyon_Apple_Mode.plist).
Copy file name to clipboardExpand all lines: installation-guide/boot-camp.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ You should also disable Fast Boot from Windows settings as well as the NUC BIOS
39
39
40
40
### Drivers
41
41
42
-
Apple drivers \(including Apple keyboards\) should be installed as part of the Boot Camp installer. If you used an [Apple Wifi replacement](../post-installation/wifi.md), then you need to get the Broadcom drivers [here](https://github.com/osy/HaC-Mini/releases/download/v2.1/BCM94360CS2.zip). Finally, you should download the NUC drivers [from Intel](https://downloadcenter.intel.com/product/126143/Intel-NUC-Kit-NUC8i7HVK).
42
+
Apple drivers \(including Apple keyboards\) should be installed as part of the Boot Camp installer. If you used an [Apple Wifi replacement](../post-installation/wifi.md), then you need to get the Broadcom drivers [here](https://github.com/osy86/HaC-Mini/releases/download/v2.1/BCM94360CS2.zip). Finally, you should download the NUC drivers [from Intel](https://downloadcenter.intel.com/product/126143/Intel-NUC-Kit-NUC8i7HVK).
@@ -77,7 +77,7 @@ Your NUC is now a Mac. It is recommended you follow the update steps below to in
77
77
78
78
## Update Existing Install
79
79
80
-
When a macOS update is released, you should install it through normal means. Major macOS updates may not work 100% on day one and may have known issues, you should check the [issues page](https://github.com/osy/HaC-Mini/issues) before a major upgrade. When a [new release](https://github.com/osy/HaC-Mini/releases/latest) of HaC Mini comes out, you can follow the steps below to update the drivers and patches.
80
+
When a macOS update is released, you should install it through normal means. Major macOS updates may not work 100% on day one and may have known issues, you should check the [issues page](https://github.com/osy86/HaC-Mini/issues) before a major upgrade. When a [new release](https://github.com/osy86/HaC-Mini/releases/latest) of HaC Mini comes out, you can follow the steps below to update the drivers and patches.
81
81
82
82
{% hint style="danger" %}
83
83
You should never use MultiBeast or similar OSX "distributions" \(ever. on any system.\) as they include broken and outdated patches and are not customized for your specific system. If you use a distribution, it is recommended that you back up your system then follow the "clean install" instructions above and then restore your files.
*[Polaris22Fixup](https://github.com/osy86/Polaris22Fixup): fix graphics issues for Vega M
24
24
*[Lilu](https://github.com/acidanthera/Lilu): kernel patching framework used by AppleALC
25
25
* OldX4000HWLibs: macOS 10.14.5 broke Vega M support, so we load a patched version from 10.14.5 beta 1 instead
26
26
27
-
All of the above are pre-built as part of the [HaC Mini release](https://github.com/osy/HaC-Mini/releases)\(use version v1.x for legacy Clover\).
27
+
All of the above are pre-built as part of the [HaC Mini release](https://github.com/osy86/HaC-Mini/releases)\(use version v1.x for legacy Clover\).
28
28
29
29
{% hint style="warning" %}
30
30
We will be doing a clean installation. That means the SSD will be wiped and **any existing data will be lost**. If you plan to boot Windows and/or Linux, it is advised that you install those systems after OSX.
6. Once the installation completes, you should see a new drive named **EFI** get mounted.
33
-
7. Download the [HaC Mini release package](https://github.com/osy/HaC-Mini/releases) and merge the `EFI` directory into the one on the EFI drive. Replace any existing file \(which should just be _config.plist_\).
33
+
7. Download the [HaC Mini release package](https://github.com/osy86/HaC-Mini/releases) and merge the `EFI` directory into the one on the EFI drive. Replace any existing file \(which should just be _config.plist_\).
Copy file name to clipboardExpand all lines: post-installation/dw1820a-wifi.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# DW1820A Wifi
2
2
3
-
Although using a Wifi card from a real Mac is [recommended](wifi.md) due to native support, the community has developed an [alternative](https://github.com/osy/HaC-Mini/issues/91)[solution](https://github.com/osy/HaC-Mini/issues/113) to working Wifi and Bluetooth using the Dell DW1820A card. Note there are a few variants of this card and users have reported the most success with the "CN-08PKF4" model.
3
+
Although using a Wifi card from a real Mac is [recommended](wifi.md) due to native support, the community has developed an [alternative](https://github.com/osy86/HaC-Mini/issues/91)[solution](https://github.com/osy86/HaC-Mini/issues/113) to working Wifi and Bluetooth using the Dell DW1820A card. Note there are a few variants of this card and users have reported the most success with the "CN-08PKF4" model.
4
4
5
5

Copy file name to clipboardExpand all lines: post-installation/support.md
+12-4
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
# Support
2
2
3
-
Support is provided in the [Github issue tracker](https://github.com/osy/HaC-Mini/issues). **Please search before posting.** If there is no existing ticket, it is important that you follow the instructions in the template for a new ticket and provide all the requested information! Issues without the requested information may be rejected.
3
+
Support is provided in the [Github issue tracker](https://github.com/osy86/HaC-Mini/issues). **Please search before posting.** If there is no existing ticket, it is important that you follow the instructions in the template for a new ticket and provide all the requested information! Issues without the requested information may be rejected.
4
4
5
5
Do **not** ask for help in tonymacx86 \(better yet, stop going to tonymacx86!\). They do not permit discussion of anything except for their own "approved" installation methods--which are all pretty problematic. We tried to provide help there in the past but was banned for linking to a non-tonymac approved guide.
6
6
7
7
## Known Issues
8
8
9
-
Outstanding issues are tracked and worked on in the [Github issues](https://github.com/osy/HaC-Mini/issues). Some of the most common unresolved issues are documented here along with possible workarounds.
9
+
Outstanding issues are tracked and worked on in the [Github issues](https://github.com/osy86/HaC-Mini/issues). Some of the most common unresolved issues are documented here along with possible workarounds.
10
10
11
-
### [USB disconnected on sleep wakeup](https://github.com/osy/HaC-Mini/issues/8)
11
+
### [USB disconnected on sleep wakeup](https://github.com/osy86/HaC-Mini/issues/8)
12
12
13
13
This is a hardware issue and cannot be worked around without Intel support or extensive kernel patching. If you require a USB device to not be disconnected \(an external HDD for example\), you can use the blue USB 3.0 Type A port on the front of the NUC. This port is connected to the CPU directly \(does not go through the buggy PCH\) and does not exhibit the same wakeup issue. However, it does experience a separate issue where if you have the device connected before powering on, then it will get disconnected after the first sleep. You should either plug in the device after OSX boots or suffer a single disconnect before the issue goes away.
14
14
@@ -40,6 +40,14 @@ If you get this message while installing, make sure your BIOS clock is set to th
40
40
41
41
If that did not solve the issue, follow the [install instructions](../installation-guide/installation.md) again starting from the top, but this time do not select "Patch OSX Installer" after running the package. Finally, after installation, you have to follow the [upgrade instructions](../installation-guide/installation.md#update-existing-install).
42
42
43
+
### Cannot boot when "secure boot" is enabled
44
+
45
+
If you enable secure boot from the installer, you may not be able to boot into an existing macOS installation or the installer for a new installation. The reason for this is because macOS will be personalized with a random value generated by the installer. This means that you can no longer boot with OpenCore installed to a USB drive as the random value will be different. If you did not install macOS with secure boot enabled, you can either re-install macOS or boot into recoveryOS and run the following command
Replace "Machintosh HD" with the name of the partition containing the macOS install that will not boot. If you run into an error, make sure you do not have two SSDs installed \(temporarily disable one from BIOS\), then run First Aid from Disk Utility, and also make sure you are connected to the internet and can ping apple.com \(from recoveryOS\).
50
+
43
51
### Reset NVRAM
44
52
45
53
Sometimes incorrect settings and boot-args will cause issues. You need to [get into boot picker](support.md#getting-into-boot-picker-menu) and then select the NVRAM reset option.
@@ -50,7 +58,7 @@ Make sure you are on the [latest BIOS version](https://downloadcenter.intel.com/
50
58
51
59
### Remove Wifi Card
52
60
53
-
There are known compatibility issues with the [DW1820A](dw1820a-wifi.md). If you cannot boot, remove the card and try again.
61
+
There are known compatibility issues with the [DW1820A](dw1820a-wifi.md) and the Intel wireless card. If you cannot boot, remove the card and try again.
Copy file name to clipboardExpand all lines: post-installation/wifi.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ A problem shared by most Hackintosh builds is that OSX's Wifi/BT drivers are lim
4
4
5
5
With the Wifi card replaced, you can get continuity/handoff features \(and Apple Watch unlocking\) without any unstable software hacks.
6
6
7
-
For an easier \(but less perfect\) solution that will not block the second M.2 NVMe slot, check out the [DW1820A](dw1820a-wifi.md). There is also [another adapter](https://github.com/osy/HaC-Mini/issues/191) for Apple BCM943602CS that will allow you to retain the second M.2 NVMe slot but will require re-wiring the antennas.
7
+
For an easier \(but less perfect\) solution that will not block the second M.2 NVMe slot, check out the [DW1820A](dw1820a-wifi.md). There is also [another adapter](https://github.com/osy86/HaC-Mini/issues/191) for Apple BCM943602CS that will allow you to retain the second M.2 NVMe slot but will require re-wiring the antennas. Finally, some users have reported success with [BCM94352Z](https://github.com/osy/HaC-Mini/issues/541) and [BCM94360NG](https://github.com/osy/HaC-Mini/issues/197), M.2 cards that are compatible with Apple drivers and do not block the second M.2 NVMe slot. These alternative options may not have 100% compatibility with handoff or Apple Watch unlock features, so YMMV. The rest of this page will cover the recommended option with the adapter card.
0 commit comments