...
 
Commits (5)
    https://gitcode.net/btwise/opencorepkg_mod/-/commit/0989cb201501bc6ff2fcb3b1399d4c959d747e70 Update MaxKernel for AirportBrcmFixup and NVMeFix 2023-10-01T00:43:55+03:00 Andrey1970AppleLife ua6lpo@rambler.ru https://gitcode.net/btwise/opencorepkg_mod/-/commit/ebb438b94ed354c1c8210c333e0be95deb27edd3 Merge branch 'master' of https://github.com/acidanthera/OpenCorePkg 2023-10-07T14:46:31+08:00 btwise tyq@qq.com https://gitcode.net/btwise/opencorepkg_mod/-/commit/16f83e58d5de7d206fd3e2f610646c2c1af9daae Docs: Clarify relevance of KernelArch=Auto to handling of 10.6 SnowLeopard 32... 2023-10-09T15:33:22+01:00 Mike Beaton mjsbeaton@gmail.com Thx @dakanji https://gitcode.net/btwise/opencorepkg_mod/-/commit/1b493be4efc6e87a81f19cf7b6cd7563e4031e5e Merge branch 'master' of https://github.com/acidanthera/OpenCorePkg 2023-10-12T10:07:21+08:00 btwise tyq@qq.com https://gitcode.net/btwise/opencorepkg_mod/-/commit/a2e155105ff27f5e8e65d4dadcee89493cf5544a Merge branch 'master' of https://gitee.com/btwise/OpenCorePkg 2023-10-12T10:08:06+08:00 btwise tyq@qq.com
5c460454adb816f53426dd7682c1800f df3af82157ce89c1990dff6eb26cb6d0
...@@ -3012,15 +3012,17 @@ to install and troubleshoot such macOS installations. ...@@ -3012,15 +3012,17 @@ to install and troubleshoot such macOS installations.
\texttt{x86\_64}, \texttt{i386}, \texttt{i386-user32}. \texttt{x86\_64}, \texttt{i386}, \texttt{i386-user32}.
\end{enumerate} \end{enumerate}
Unlike macOS~10.7 (where certain board identifiers are treated as the \texttt{i386} Unlike macOS~10.7 (where certain board identifiers are treated as \texttt{i386}
only machines), and macOS~10.5 or earlier (where \texttt{x86\_64} is not supported only machines), and macOS~10.5 or earlier (where \texttt{x86\_64} is not supported
by the macOS kernel), macOS~10.6 is very special. The architecture choice on macOS~10.6 by the macOS kernel), macOS~10.6 is very special. The architecture choice on macOS~10.6
depends on many factors including not only the board identifier, but also the macOS depends on many factors including not only the board identifier, but also the macOS
product type (client vs server), macOS point release, and amount of RAM. The detection product type (client vs server), macOS point release, and amount of RAM. The detection
of all these is complicated and impractical, as several point releases had implementation of all these is complicated and impractical, as several point releases had implementation
flaws resulting in a failure to properly execute the server detection in the first place. flaws resulting in a failure to properly execute the server detection in the first place.
For this reason, OpenCore on macOS~10.6 falls back on the \texttt{x86\_64} For this reason when \texttt{Auto} is set, OpenCore on macOS~10.6 falls back
architecture whenever it is supported by the board, as it is on macOS~10.7. to the \texttt{x86\_64} architecture when it is supported by the board, as
on macOS~10.7. The 32-bit \texttt{KernelArch} options can still be configured
explicitly however.
A 64-bit Mac model compatibility matrix corresponding to actual A 64-bit Mac model compatibility matrix corresponding to actual
EfiBoot behaviour on macOS 10.6.8 and 10.7.5 is outlined below. EfiBoot behaviour on macOS 10.6.8 and 10.7.5 is outlined below.
......
\documentclass[]{article} \documentclass[]{article}
%DIF LATEXDIFF DIFFERENCE FILE %DIF LATEXDIFF DIFFERENCE FILE
%DIF DEL PreviousConfiguration.tex Wed Sep 27 10:25:48 2023 %DIF DEL PreviousConfiguration.tex Mon Oct 9 15:13:53 2023
%DIF ADD ../Configuration.tex Wed Sep 27 10:25:48 2023 %DIF ADD ../Configuration.tex Mon Oct 9 15:31:36 2023
\usepackage{lmodern} \usepackage{lmodern}
\usepackage{amssymb,amsmath} \usepackage{amssymb,amsmath}
...@@ -3072,15 +3072,18 @@ to install and troubleshoot such macOS installations. ...@@ -3072,15 +3072,18 @@ to install and troubleshoot such macOS installations.
\texttt{x86\_64}, \texttt{i386}, \texttt{i386-user32}. \texttt{x86\_64}, \texttt{i386}, \texttt{i386-user32}.
\end{enumerate} \end{enumerate}
Unlike macOS~10.7 (where certain board identifiers are treated as the \texttt{i386} Unlike macOS~10.7 (where certain board identifiers are treated as \DIFdelbegin \DIFdel{the }\DIFdelend \texttt{i386}
only machines), and macOS~10.5 or earlier (where \texttt{x86\_64} is not supported only machines), and macOS~10.5 or earlier (where \texttt{x86\_64} is not supported
by the macOS kernel), macOS~10.6 is very special. The architecture choice on macOS~10.6 by the macOS kernel), macOS~10.6 is very special. The architecture choice on macOS~10.6
depends on many factors including not only the board identifier, but also the macOS depends on many factors including not only the board identifier, but also the macOS
product type (client vs server), macOS point release, and amount of RAM. The detection product type (client vs server), macOS point release, and amount of RAM. The detection
of all these is complicated and impractical, as several point releases had implementation of all these is complicated and impractical, as several point releases had implementation
flaws resulting in a failure to properly execute the server detection in the first place. flaws resulting in a failure to properly execute the server detection in the first place.
For this reason, OpenCore on macOS~10.6 falls back on the \texttt{x86\_64} For this reason \DIFaddbegin \DIFadd{when }\texttt{\DIFadd{Auto}} \DIFadd{is set}\DIFaddend , OpenCore on macOS~10.6 falls back
architecture whenever it is supported by the board, as it is on macOS~10.7. \DIFdelbegin \DIFdel{on }\DIFdelend \DIFaddbegin \DIFadd{to }\DIFaddend the \texttt{x86\_64} architecture \DIFdelbegin \DIFdel{whenever }\DIFdelend \DIFaddbegin \DIFadd{when }\DIFaddend it is supported by the board, as
\DIFdelbegin \DIFdel{it is }\DIFdelend on macOS~10.7. \DIFaddbegin \DIFadd{The 32-bit }\texttt{\DIFadd{KernelArch}} \DIFadd{options can still be configured
explicitly however.
}\DIFaddend
A 64-bit Mac model compatibility matrix corresponding to actual A 64-bit Mac model compatibility matrix corresponding to actual
EfiBoot behaviour on macOS 10.6.8 and 10.7.5 is outlined below. EfiBoot behaviour on macOS 10.6.8 and 10.7.5 is outlined below.
......
...@@ -17,7 +17,7 @@ Kexts ...@@ -17,7 +17,7 @@ Kexts
| Wi-Fi and bluetooth | MinKernel (Min macOS) | MaxKernel (Max macOS) | Note | | Wi-Fi and bluetooth | MinKernel (Min macOS) | MaxKernel (Max macOS) | Note |
|---------------------|-----------------------|-----------------------|------| |---------------------|-----------------------|-----------------------|------|
| [AirPortAtheros40.kext](https://i.applelife.ru/2018/12/442854_AirPortAtheros40.kext.zip) | 18.0.0 (10.14) | — | From 10.13 | | [AirPortAtheros40.kext](https://i.applelife.ru/2018/12/442854_AirPortAtheros40.kext.zip) | 18.0.0 (10.14) | — | From 10.13 |
| [AirportBrcmFixup.kext](https://github.com/acidanthera/AirportBrcmFixup) | 12.0.0 (10.8) | 22.9.9 (13) | — | | [AirportBrcmFixup.kext](https://github.com/acidanthera/AirportBrcmFixup) | 12.0.0 (10.8) | 23.9.9 (14) | — |
| [ATH9KFixup.kext](https://github.com/chunnann/ATH9KFixup) | — | — | — | | [ATH9KFixup.kext](https://github.com/chunnann/ATH9KFixup) | — | — | — |
| [BrcmPatchRAM](https://github.com/acidanthera/BrcmPatchRAM) | 14.0.0 (10.10) | 23.9.9 (14) | — | | [BrcmPatchRAM](https://github.com/acidanthera/BrcmPatchRAM) | 14.0.0 (10.10) | 23.9.9 (14) | — |
| [IntelBluetoothFirmware](https://github.com/zxystd/IntelBluetoothFirmware) | — | — | — | | [IntelBluetoothFirmware](https://github.com/zxystd/IntelBluetoothFirmware) | — | — | — |
......
...@@ -594,7 +594,7 @@ ...@@ -594,7 +594,7 @@
<key>ExecutablePath</key> <key>ExecutablePath</key>
<string>Contents/MacOS/AirportBrcmFixup</string> <string>Contents/MacOS/AirportBrcmFixup</string>
<key>MaxKernel</key> <key>MaxKernel</key>
<string>22.9.9</string> <string></string>
<key>MinKernel</key> <key>MinKernel</key>
<string>12.0.0</string> <string>12.0.0</string>
<key>PlistPath</key> <key>PlistPath</key>
...@@ -630,7 +630,7 @@ ...@@ -630,7 +630,7 @@
<key>ExecutablePath</key> <key>ExecutablePath</key>
<string></string> <string></string>
<key>MaxKernel</key> <key>MaxKernel</key>
<string>22.9.9</string> <string></string>
<key>MinKernel</key> <key>MinKernel</key>
<string>17.0.0</string> <string>17.0.0</string>
<key>PlistPath</key> <key>PlistPath</key>
...@@ -648,7 +648,7 @@ ...@@ -648,7 +648,7 @@
<key>ExecutablePath</key> <key>ExecutablePath</key>
<string>Contents/MacOS/NVMeFix</string> <string>Contents/MacOS/NVMeFix</string>
<key>MaxKernel</key> <key>MaxKernel</key>
<string>22.9.9</string> <string></string>
<key>MinKernel</key> <key>MinKernel</key>
<string>18.0.0</string> <string>18.0.0</string>
<key>PlistPath</key> <key>PlistPath</key>
......
...@@ -594,7 +594,7 @@ ...@@ -594,7 +594,7 @@
<key>ExecutablePath</key> <key>ExecutablePath</key>
<string>Contents/MacOS/AirportBrcmFixup</string> <string>Contents/MacOS/AirportBrcmFixup</string>
<key>MaxKernel</key> <key>MaxKernel</key>
<string>22.9.9</string> <string></string>
<key>MinKernel</key> <key>MinKernel</key>
<string>12.0.0</string> <string>12.0.0</string>
<key>PlistPath</key> <key>PlistPath</key>
...@@ -630,7 +630,7 @@ ...@@ -630,7 +630,7 @@
<key>ExecutablePath</key> <key>ExecutablePath</key>
<string></string> <string></string>
<key>MaxKernel</key> <key>MaxKernel</key>
<string>22.9.9</string> <string></string>
<key>MinKernel</key> <key>MinKernel</key>
<string>17.0.0</string> <string>17.0.0</string>
<key>PlistPath</key> <key>PlistPath</key>
...@@ -648,7 +648,7 @@ ...@@ -648,7 +648,7 @@
<key>ExecutablePath</key> <key>ExecutablePath</key>
<string>Contents/MacOS/NVMeFix</string> <string>Contents/MacOS/NVMeFix</string>
<key>MaxKernel</key> <key>MaxKernel</key>
<string>22.9.9</string> <string></string>
<key>MinKernel</key> <key>MinKernel</key>
<string>18.0.0</string> <string>18.0.0</string>
<key>PlistPath</key> <key>PlistPath</key>
......