Administrators Hervé Posted November 21, 2018 Administrators Share Posted November 21, 2018 'took the old girl out of retirement! Specifications: Modded/unlocked BIOS 1.0.16 (from www.bios-mods.com) with HDD set to AHCI mode (standard BIOS 1.0.16 with HDD set to RAID mode should be Ok too) G33M02 motherboard (dual-core CPUs only; G33M03 mobo required for quad-core CPUs) Intel G33 chipset (ICH9R, PCIe 1.1, PCI 2.3, SATA-II and USB 2.0) CPU: Intel Wolfdale Core2Duo E8600 @3.33GHz Intel Wolfdale-DP Xeon X5270 @3.5GHz (with LGA771-to-LGA775 mod) Integrated Intel GMA 3100 graphics (unsupported in Mac OS X/OS X/macOS and disabled in BIOS) Graphics card: Asus PCIe x16@x8 GeForce GT730 (Kepler) 2GB-DDR5 (10de:1287) single-slot low-profile, 1 x VGA + 1 x DVI + 1 x HDMI output + HDMI audio (10de:0e0f) Gigabyte PCIe x16@x4 GeForce GT1030 (Pascal) 2GB-DDR5 (10de:1d01) single-slot low-profile, 1 x DVI + 1 x HDMI output + HDMI audio (10de:0fb8) Yeston PCIe x16@x8 Radeon RX560 (Polaris 21/Baffin) 4GB-DDR5 (1002:67ef) single-slot low-profile, 1 x VGA + 1 x DVI + DVI, 1 x HDMI output + HDMI audio (1002:aae0) AMD PCIe x16@8 Radeon Pro WX4100 (Polaris 21/Baffin) 4GB-DDR5 (1002:67e3) single-slot low-profile, 4 x mini-DP outputs + HDMI audio (1002:aae0) 6Go 8GB DDR2-800 RAM Intel 82562V-2 10/100Mb FastEthernet (8086:10c0) ALC888 7:1 High Definition Audio (10ec:0888) TEAC CA-200 internal-USB 19-in-1 card reader (0644:0200) SATA CD/DVD RW drive Dell wireless keyboard and mouse (Bluetooth devices with dedicated USB dongle in HID proxy mode) 6 x USB 2.0 ports 2 x front jack ports (microphone + headset) 6 x rear jack ports (various audio I/O) Wireless/Bluetooth: any compatible PCI/PCIe card or USB dongle compatible with target macOS version With GT730: vostro200:lspci admin$ lspci -nn pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:00:1b.0 64-bit device address ignored. pcilib: 0000:00:1f.3 64-bit device address ignored. 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) 00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02) 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GK208 HDMI/DP Audio Controller [10de:0e0f] (rev a1) With GT1030 (High Sierra only): vostro200:~ admin$ lspci -nn pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:00:1b.0 64-bit device address ignored. pcilib: 0000:00:1f.3 64-bit device address ignored. 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) 00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02) 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GP108 High Definition Audio Controller [10de:0fb8] (rev a1) For recommended BIOS settings, see here. These guides are for Vostro200 desktop computers fitted with a Wolfdale Core2Duo CPU (or Wolfdale-DP dual core Xeon CPU) that includes SSE4.1 instructions set. Conroe CPUs do not include these and are therefore unsuitable for macOS, they can only run OS X up to El Capitan. From Mojave to Big Sur, macOS natively supports nVidia Kepler cards only. As such, High Sierra 10.13 is the end of the road for Pascal cards such as the GT1030, knowing that these (like Maxwell cards) are only supported with the nVidia Web Driver due to lack of native drivers. From Monterey, macOS drops all native support for nVidia cards, marking the official end for Kepler cards. Support can however be recovered/provided by applying patches with tools such as OCLP. The only alternative is to use supported AMD cards (HD7000/HD8000 series minimum, Polaris minimum being favoured), hence why I opted for a Polaris21/Baffin RX560. AMD Radeon Pro WX4100 (LP card) is suitable too (tested 100% successfully). Both those AMD cards are natively fully supported. NB: Wolfdale-DP CPUs may require adjusting CPU clock rate parameter to highest multiplier in BIOS for proper CPU SpeedStep to work. Running on a Wolfdale-DP Xeon dual core CPU may also require the use of additional boot arg npci=0x2000 or npci=0x3000 to avoid boot freeze and system hard reset. It certainly did on my Vostro200 (but then again my X5270 was an ES model...). Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 21, 2018 Author Administrators Share Posted November 21, 2018 Last update: 20 Jan 2019 Target macOS release: High Sierra 10.13.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration GT730: with macOS native/default drivers (or with nVidia Web Driver) GT1030: with nVidia Web Driver only multi-display, including VGA (with Lilu + WEG) GT730: DVI + HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 GT1030: DVI + HDMI OOB audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19-in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) CPU power management (works better with MacPro3,1 SMBIOS than iMac10,1) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) AppleALC supports the following layouts for ALC888: Audio found to work with all such layouts which individually support various inputs and outputs as shown below: Spoiler Layout 1 Layout 7 Layout 2 Layout 3 Layout29 Layout 4 Layout 5 Layout 28 Layout 11 Layout 27 I went with layout #1: VoodooHDA lists I/O that are more PC oriented Not working: N/A Not tested: N/A GeekBench v2.4.3 (32bit) gives a 4500+/4700+ rating: 1) 10.13 USB installer creation Using a USB key of 8GB minimum, create a High Sierra USB installer through the following Terminal command: sudo <path>/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of High Sierra installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following customised settings: Install Clover in the ESP Boot Sectors -> Install boot0af in MBR Clover for BIOS (legacy) booting -> Clover EFI 64-bits SATA BIOS Drivers, 64 bit -> FSInject-64 / ApfsDriverLoader-64 / AppleImageLoader-64 BIOS Drivers, 64 bit -> GrubEXFAT-64 / GrubNTFS-64 (both optional only) Themes (optional only) Install Clover PrefPane (optional only) you may use version r4689 attached below or any subsequent version available at Dids' Github repo Clover_v2.4k_r4689.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the Vostro200 High Sierra Clover pack below to the EFI/Clover folder of the EFI partition Vostro200_10.13_Clover_Pack.zip 2) 10.13 installation boot the High Sierra USB installer and wait until you get to the language menu; it'll get there. at the Clover main menu, select the "Install macOS High Sierra" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target High Sierra installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target High Sierra partition>" repeat this until this partition is no longer offered and only the target High Sierra partition is left to boot 3) Post-Installation tuning Once the target High Sierra partition has booted, complete the 1st boot configuration finalisation Once at the desktop, install Clover bootloader on the High Sierra partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the High Sierra partition/disk Open this EFI partition and transfer the files & folders from the above Vostro200 High Sierra Clover pack to the EFI/Clover folder of the EFI partition You may then reboot and verify that High Sierra boots off your disk through Clover After that reboot, finalise post-installation tuning actions such as disabling hibernation, allowing all apps download from anywhere, changing all serial numbers, etc. Edit #1: 20 Jan 2019 New pack with updated DSDT re-patched for proper Sleep & Wake Link to comment Share on other sites More sharing options...
Administrators Hervé Posted December 5, 2018 Author Administrators Share Posted December 5, 2018 Last update: 18 Aug 2019 Target macOS release: Mojave 10.14.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration on GT730 OOB with macOS native driver multi-display (with Lilu +WEG): DVI & HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19-in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) CPU power management (works better with MacPro3,1 SMBIOS than iMac10,1) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) Not working: N/A Not tested: N/A GeekBench v2.4.3 (32bit) gives a 4500+ rating: 1) 10.14 USB installer creation Using a USB key of 8GB minimum, create a Mojave USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Mojave installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following customised settings: Install Clover in the ESP Boot Sectors -> Install boot0af in MBR Clover for BIOS (legacy) booting -> Clover EFI 64-bits SATA BIOS Drivers, 64 bit -> FSInject-64 / ApfsDriverLoader-64 / AppleImageLoader-64 BIOS Drivers, 64 bit -> GrubEXFAT-64 / GrubNTFS-64 (both optional only) Themes (optional only) Install Clover Pref Pane (optional only) you may use version r4689 r4911 attached below or any subsequent version available at Dids' Github repo: Clover_v2.4k_r4689.pkg.zip Clover_v2.4k_r4911.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover_Configurator.zip open this EFI partition and transfer the files & folders from the Vostro200 Mojave Clover pack below to the EFI/Clover folder Clover_pack_Vostro200_Mojave Clover_pack_Vostro200_Mojave_#2.zip copy High Sierra 10.13.6's telemetry plugin below to the root of your USB installer com.apple.telemetry.plugin.zip 2) 10.14 installation boot the Mojave USB installer at the Clover main menu, select the "Install macOS Mojave" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target Mojave installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Mojave partition>" repeat this until this partition is no longer offered and only the target Mojave partition is left to boot at this stage, Mojave installation is complete but requires one final piece of tuning to avoid KP and boot loop reboot the USB installer as it if were the 1st time or reboot in single-user mode and, at main screen, open up Terminal from Tools menu copy 10.13.6's telemetry plugin to Mojave's target partition to avoid SSE4.2-related KP/reset on Core2Duo/Quad at boot time (this telemetry plugin process is required after each update ) cp -Rf /com.apple.telemetry.plugin /Volumes/<target Mojave partition>/System/Library/UserEventPlugins/ Exit Terminal and restart your computer. Reboot the target Mojave partition via your USB installer 3) Post-installation tuning Once the target Mojave partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Mojave partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the Mojave partition/disk Open this EFI partition and transfer the files & folders from the above Vostro200 Mojave Clover pack to the EFI/Clover folder You may then reboot and verify that Mojave boots off your disk through Clover Edit #1: 19 Jan 2019 New pack with updated DSDT re-patched for proper Sleep & Wake Edit #2: 18 Aug 2019 Update Clover version to r4911 (minimum version) in order to recover RTC fix for Mojave 10.14.4 and later Link to comment Share on other sites More sharing options...
Administrators Hervé Posted October 8, 2019 Author Administrators Share Posted October 8, 2019 Target macOS release: Catalina 10.15.x This is a Clover-based installation using the well-known/well documented vanilla method detailed below: Working: full graphics acceleration on GT730 OOB with macOS native driver multi-display (with Lilu + WEG): DVI & HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19-in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) CPU power management (works better with MacPro3,1 SMBIOS than iMac10,1) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) Not working: N/A Not tested: N/A GeekBench v4.4.4 (64bit) gives a 3500/3900+ multicore rating: 1) 10.15 USB installer creation Using a USB key of 8GB minimum, create a Catalina USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Catalina installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: install Clover bootloader on the USB installer with the following customised settings: Install Clover in the ESP Boot Sectors -> Install boot0af in MBR Clover for BIOS (legacy) booting -> Clover EFI 64-bits SATA BIOS Drivers, 64 bit -> ApfsDriverLoader / FSInject / HFSPlus / SMCHelper BIOS Drivers, 64 bit -> GrubEXFAT / GrubNTFS (both optional only) Themes (optional only) Install Clover PrefPane (optional only) you may use version r5093 attached below or any subsequent version available at Dids' Github repo: Clover_v2.5k_r5093.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the Vostro200 Catalina Clover pack below to the EFI/Clover folder Vostro200_Catalina_Clover_Pack.zip copy High Sierra 10.13.6's telemetry plugin below to the root of your USB installer com.apple.telemetry.plugin.zip 2) 10.15 installation boot the Catalina USB installer at the Clover main menu, select the "Install macOS Catalina" partition (but don't press [ENTER]) press [SPACE], select -v verbose option in the menu, then choose to boot with the selected options proceed with installation, creating & formatting the target Catalina installation through Disk Utility as/if required on 1st reboot, boot off the USB installer and select the freshly created "macOS install from <target Catalina partition>" repeat this until this partition is no longer offered and only the target Catalina partition is left to boot at this stage, Catalina installation is complete but requires one final pice of tuning to avoid KP and boot loop reboot the USB installer as it if were the 1st time or reboot in single-user mode and, at main screen, open up Terminal from Tools menu copy 10.13.6's telemetry plugin to Catalina's target partition to avoid SSE4.2-related KP/reset on Core2Duo at boot time reboot normally (this telemetry plugin process is required after each update ) cp -Rf /com.apple.telemetry.plugin /Volumes/<target Catalina partition>/System/Library/UserEventPlugins/ Exit Terminal and restart your computer. Reboot the target Catalina partition via your USB installer 3) Post-installation tuning Once the target Catalina partition has booted, complete the 1st boot configuration tuning Once at the desktop, install Clover bootloader on the Catalina partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the Catalina partition/disk Open this EFI partition and transfer the files & folders from the above Vostro200 Catalina Clover pack to the EFI/Clover folder You may then reboot and verify that Catalina boots off your disk through Clover Link to comment Share on other sites More sharing options...
Administrators Hervé Posted January 29, 2021 Author Administrators Share Posted January 29, 2021 Target macOS release: Big Sur 11.x This is an OpenCore-based installation, completed as an upgrade of an existing Catalina installation as detailed below. Working: full graphics acceleration on GT730 OOB with macOS native driver multi-display (with Lilu + WEG): DVI & HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) partial CPU power management with OpenCore, legacy Core2Duo platform oblige (LFM + HFM only since OpenCore does not generate C States/P States) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) USB or Wireless keyboard and mouse (with IOHIDFamily's isSingleUser function OpenCore patch) Not working: N/A Not tested: N/A GeekBench v4.4.4 (64bit) gives a 3900+ rating: This old desktop PC only operates in legacy BIOS mode, not UEFI. This is a problem for installing Big Sur from scratch with a USB installer because, in legacy BIOS mode, OpenCore does not appear capable to dynamically obtain the volume UUID of the temporary MacOS installer partition/volume (created during the installation process) and properly define an essential parameter called msu-product-url. This causes the installation process to fail proper execution and, instead, triggers computer reset + continuous boot loop of the temporary volume, the installation therefore never reaching completion. A workaround to this problem is to install Big Sur as an upgrade of an existing Catalina installation. When installing Big Sur as an upgrade of Catalina, the temp installation will be created on the existing Catalina Data volume whose UUID can be readily obtained and passed through NVRAM parameter msu-product-url to the installation process. This was described in this thread by pac-man at InsanelyMac, credits to him. Basically, the UUID of the Catalina Data volume is obtained through the diskutil line command and the resulting value is used to create a fully-defined path for the temp installation volume that is stored in NVRAM parameter msu-product-url. This NVRAM parameter is essential to complete the installation process. Please note that installing Big Sur on this old desktop PC takes a substantial amount time to complete (even on a SATA SSD) so set aside a few hours... 1) Preparation OpenCore needs to be setup in legacy mode to boot the Vostro 200 computer, lack of UEFI BIOS mode oblige. This is well documented on the Dortania OpenCore GitHub repo which I invite everyone to refer to. the following OC 0.6.5 EFI folder may be used on the existing disk's EFI partition or on a USB key as bootloader to reboot the system during the Big Sur installation phases, then boot Big Sur once it has been fully installed: OC_0-6-5_EFI_Vostro200_BigSur.zip key elements to note in that config are: the IOHIDFamily kext patch applied to the _isSingleUser function; it's required to obtain working USB keyboard & mouse, they don't work without the patch. This is detailed in the Dortania's documentation. additional msu-product-url parameter added under NVRAM->7C436110-AB2A-4BBB-A880-FE41995C9F82 UUID UUID as per pac-man's thread at InsanelyMac. 2) 11.x installation from an existing Catalina installation (can be a Clover-based one), download a copy of Big Sur installation package. ensure you have emulated NVRAM working and define msu-product-url parameter as follows through Terminal: sudo nvram msu-product-url="msu-product-url://$(diskutil info /System/Volumes/Data | grep "Volume UUID" | awk '{print $3}')/macOS%2520Install%2520Data" run the Big Sur installation package and proceed with installation on your Catalina disk/volume/partition as offered by the installer app. the Big Sur files will be copied over and this may take a lot of time (could be anything from 40mins to 1hr). on 1st and all subsequent reboots, make sure to use OpenCore and the EFI folder/config setup offered above. the whole installation process will normally require 3 or 4 reboots to complete and this make take anything like 1hr. 3) Post-installation tuning once the Big Sur installation has completed and Big Sur first boots, complete the initial configuration tuning. Here too, this may take an unusual and very long time; just hang in there. once at the Big Sur desktop, mount your disk's EFI partition and copy the OpenCore EFI folder as necessary/appropriate in order to boot Big Sur via OpenCore. proceed with usual macOS fine-tuning (wireless setup, hibernation disabling, refresh of serial numbers, etc.). NB: Contrary to pac-man's suggestion to remove the msu-product-url from NVRAM after installation, I strongly recommended to retain it because it'll be required for each Big Sur update. Edit #1: ------- For a fresh installation of Big Sur, proceed as follows to obtain the UUID value to inject in NVRAM as msu-product-url: Boot your Big Sur installer and initiate installation or launch the Big Sur installation package from an existing macOS build. At 1st reboot, boot the Big Sur installer again and type the following in Terminal: diskutil info /Volumes/<target disk or partition name"> | grep "Volume UUID" | awk '{print $3}' Make a note of the returned UUID Edit your OC config and add the following parameter in NVRAM section against UUID 7C436110-AB2A-4BBB-A880-FE41995C9F82: msu-product-url <obtained UUID>/macOS%2520Install%2520Data String Reboot and Reset NVRAM before booting your temp Macintosh HD partition For instance, if installing Big Sur on a disk or partition called "macOS_BigSur_11": In Terminal, type: diskutil info /Volumes/macOS_BigSur_11 | grep "Volume UUOD" | awk '{print $3}' say it returns UUID value 4B9B8623-B1B4-3DC8-841A-D57C824B0067. set key msu-product-url with value 4B9B8623-B1B4-3DC8-841A-D57C824B0067/macOS%2520Install%2520Data and type String in the OC config. reboot, reset NVRAM and boot your temp installation partition to complete the installation. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 21, 2021 Author Administrators Share Posted November 21, 2021 Revised DSDT following replacement of DW1510 wireless card by an Apple BCM94360CS2 causing built-in Bluetooth to break sleep. All Ok once the UHC ports were patched so that their individual _PWR statements was adjusted from: Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0nn, // where nn=03/04/0C/0E/05/20 for UHC1/UHC2/UHC3/UHC4/UHC5/UHC6 respectively 0x03 }) to: Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0D, 0x03 }) as per USB2.0 EH0x devices. DSDT.aml.zip Link to comment Share on other sites More sharing options...
Administrators Hervé Posted July 25, 2022 Author Administrators Share Posted July 25, 2022 Target macOS release: Monterey 12.x Finally got round to do it! This is an OpenCore-based installation using the vanilla method detailed below: Working: full graphics acceleration on GT730 -> with Kepler patch since there are no drivers natively provided in Monterey, Apple having dropped all nVidia dGPUs on RX560 -> OOB multi-display (with Lilu + WEG): on GT730 -> DVI + HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 on RX560 -> DVI + HDMI + VGA OOB audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19-in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) partial CPU power management with OpenCore, legacy Core2Duo platform oblige (LFM + HFM only since OpenCore does not generate C States/P States) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) USB or Wireless keyboard and mouse (with IOHIDFamily's isSingleUser function OpenCore patch) Not working: N/A Not tested: N/A GeekBench v4.4.4 (64bit) gives a 3900+ rating with MacPro3,1 SMBIOS: This old desktop PC only operates in legacy BIOS mode, not UEFI. This is a problem for installing Monterey from scratch with a USB installer because, in legacy BIOS mode, OpenCore does not appear capable to dynamically obtain the volume UUID of the temporary macOS installer partition/volume (created during the installation process) and properly define an essential parameter called msu-product-url. This causes the installation process to fail proper execution and, instead, triggers computer reset + continuous boot loop of the temporary volume, the installation therefore never reaching completion. The workaround to this problem is detailed below. When installing Monterey, the temp installation will be created on the target disk/partition volume whose UUID can be readily obtained and passed through NVRAM parameter msu-product-url to the installation process. This was described in this thread by pac-man at InsanelyMac, credits to him. Basically, the UUID of the target Monterey volume is obtained through the diskutil line command and the resulting value is used to create a fully-defined path for the temp installation volume that is stored in NVRAM parameter msu-product-url. This NVRAM parameter is essential to complete the installation process. Please note that installing Monterey on this old desktop PC takes some time to complete (even on a SATA SSD) so set aside an hour or two... 1) Preparation OpenCore needs to be setup in legacy mode to boot the Vostro 200 computer, lack of UEFI BIOS mode oblige. This is well documented on the Dortania OpenCore GitHub repo which I invite everyone to refer to. the OC 0.8.2 pack provided below may be used on a USB key or the existing disk's EFI partition as bootpack to reboot the system during the Monterey installation phases, then boot Monterey once it has been fully installed. key elements to note in that config are: the IOHIDFamily kext patch applied to the _isSingleUser function; it's required to obtain working USB keyboard & mouse, they don't work without the patch. This is detailed in the Dortania's documentation. additional msu-product-url parameter to be added under NVRAM->7C436110-AB2A-4BBB-A880-FE41995C9F82 UUID UUID as per pac-man's thread at InsanelyMac. 2) 12.x USB installer creation Using a USB key of 16GB minimum, create a Monterey USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Catalina installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: mount the USB installer's EFI partition. If it does not exist, create it (size 200MB, format FAT32). unzip the following OpenCore bootpack and copy the resulting EFI folder + boot file to the root of the mounted EFI partition: Vostro200_Monterey_OC_0.8.2_Pack.zip 3) 12.x installation boot the Monterey USB installer. at the OpenCore picker, select the "Install macOS Monterey" entry. proceed with installation, creating & formatting the target Monterey installation through Disk Utility as/if required. on 1st reboot, do not boot the newly created Macintosh HD or macOS installer partition but boot the Monterey USB installer again. Open up Terminal and collect the volume UUID of the target partition in order to store additional NVRAM parameter msg-product-url into your OC config. Note down the value returned by the command: diskutil info /Volumes/<name of target Monterey disk/partition> | grep "Volume UUID" | awk '{print $3}' Open up your OC config file and, under NVRAM->7C436110-AB2A-4BBB-A880-FE41995C9F82, add msu-product-url <obtained UUID value>/macOS%2520Install%2520Data STRING Save your OC config and reboot At the OC picker, select the Macintosh HD or macOS installer partition. The Monterey installation will now resume. The process normally requires to boot this temp partition twice only; however, should it hang or freeze, reboot that partition as many times as required until the OC Picker offers you the final Monterey partition with the name you initially created it with. Reboot this final partition until you reach Monterey 1st boot. 4) Post-installation tuning once the Monterey installation has completed and Monterey first boots, complete the initial configuration tuning. Here too, this may take an unusual and very long time, especially with a natively unsupported graphics card like a Kepler one; just hang in there. once at the Monterey desktop, mount your disk's EFI partition and copy the OpenCore EFI folder as necessary/appropriate in order to boot Monterey via OpenCore. proceed with usual macOS fine-tuning (wireless setup, hibernation disabling, refresh of serial numbers, etc.). If running Monterey on an unsupported graphics card (eg: nVidia Tesla/Kepler card), install the necessary drivers to obtain graphics acceleration. This can be done manually (only for the expert), with OCLP (recommended) or other existing tool. I apply OCLP root patches for my Kepler card. Reboot into your finalised Monterey installation. Link to comment Share on other sites More sharing options...
Recommended Posts