Recently Browsing 0 members
No registered users viewing this page.
Clover r4542 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
Tested with unlocked Workstation 14 running OSX 10.9 -->10.14 guest in Windows X64 host.
1. Download and unzip "EFI_Clover_r4542 for VMware.zip". Mount Clover-v2.4k-4542-X64.iso by double clicking on it.
2. Mount your VM's EFI System Partition eg in terminal
sudo diskutil mount disk0s1 3. Copy EFI folder from step 1 into the EFI partition
4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
Sorry for the vague subject line, but I think I have a hardware issue and I'm having trouble diagnosing it. This is a LONG post because I'm trying to explain what I tried and to give you all the info that I do have.
History: This has been a successful Hackintosh for 2 years 2 months. I have not changed the OS (still running 10.11.4) just to avoid any problems. I have not changed the hardware other than GPU about a year ago, hard drives over time, and RAM about two weeks ago. (Keep that RAM in mind.)
Motherboard: ASRock Z170 OC Formula CPU: Intel i7-6700K RAM: G.SKILL Ripjaws V Series 32GB DDR4 @2400, replaced with Corsair 64GB DDR4 @2133 (but lower CAS latency) GPU: MSI GeForce GTX 970 PSU: CORSAIR AX760 760W 80+ Platinum CPU Heatsink: CORSAIR Hydro Series H105
Problem, Tuesday Night: Catastrophic death. Just shut down, couldn't get it up. I spent over two hours midnight–2am, then another hour after I got up in the AM, determining that the heatsink pump had died. To make a three hour story short, the errors on the motherboard were all related to RAM, but it had been running fine with the new RAM for 10 days. I put in the old RAM and got the computer to boot, and then I heard that the fans were going full-tilt and saw the CPU temperature at just under boiling. And it shut down. I determined it was the pump and not motherboard because the pump did not turn on when I moved it to a header on the motherboard that had just been powering a fan that was fine. So I ordered a new CPU cooler and installed it yesterday.
Problem, Sunday Night: It was running fine for a day, after installing the new CPU heat sink. We had a brown-out in the morning which apparently did NOT trip any UPS in the house, and the computer restarted. Seemed fine, then tonight (11 hrs after the brownout), I went to make dinner, came back and all the fans were going and the computer wasn't on. The light on the Corsair pump was flickering.
Trying to Diagnose: So, with the light flickering, I thought maybe it was the motherboard after all, and the CPU fan 1 was just dead (or dying). No problem, moved it to CPU fan 2 and moved the fans for the heatsink to chassis 2 and tweaked the fan speeds in the BIOS (I was able to boot to it) and ... couldn't boot. I can get to the BIOS. I can start getting to the Mac OS, but I can't actually boot fully. The motherboard is cycling between error codes 00 and 19, which from what I can find means CPU (00) or RAM (19). I have tried powering the whole system down (on the PSU) for awhile, going back to the old RAM (works but then same error code on reboot), and even going to a passive heatsink I had in storage.
Why this May Be a Hackintosh Question: I have a pattern now to diagnose. After hitting the restart a few times, I can get into the BIOS, no longer getting the 00/19 error on the motherboard. I can get to the Clover boot menu, at which point the diagnostic LED on the motherboard turns off. I can start the Mac OS, it spits out a bunch of diagnostic stuff, and then freezes, and the lights on the motherboard turn back on and flash between the 00 and 19 errors and the display shuts off. I get to the same spot in the Mac OS startup, and that's when it shuts down. To me, from the zero that I know about this, it looks like it's saying there's a CPU error. Meaning I may have fried the CPU (or motherboard? or both?) during that initial CPU cooler failure five days ago. I have attached a screenshot from the video I took of the screen while starting up the last time.
CMOS Reset: I tried doing this as an addendum, after taking pictures of every screen in the BIOS so I could restore. The reset definitely reset the BIOS, I got it to boot to the BIOS again, but I'm stuck at the same death point as in the screenshot. The ONLY difference is that now instead of just stopping there, it goes black for a few seconds and returns to the BIOS option screen (F2 for BIOS, F11 for Boot, etc.), and then tries to boot the Mac OS again. Fails at the same point again, the only difference each time is that in that "Backtrace (CPU #) ..." line, the # changes, and the com.apple.lokit.IOBluetoothHostController... hex stuff is different.
Help!? Do I need a new motherboard and CPU? Fortunately, everything is backed up hourly, and on my laptop, and the HDDs should still be fine.
First... If you need DSDT edits for SkyLake, KabyLake or CoffeeLake... -Post your full Clover folder with original tables in Origin folder(Extract with F4 in Clover boot screen) -Run it, post files generated in your desktop RunMe.app Installation --Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/ --Create a bootable copy of macOS HighSierra Check out the link http://diskmakerx.com/ --Install Clover in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/ --Replace with my Clover folder CLOVER.zip --Install Sierra/High Sierra and boot into system! Post Installation --Install Clover in HDD/SSD and replace with my folder CLOVER.zip --Reboot and activate video! -Nvidia WebDriver Sierra http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-07212017/ -Nvidia WebDriver High Sierra http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-10162017/ -Cuda http://www.insanelymac.com/forum/topic/302795-cuda-90214-is-out-update-10162017/ --DSDT My DSDT with patches for Skylake DSDT.MaLd0n ASUS Z170M PLUS.zip Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -DMAC -DARWIN -LPC -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -IMEI -PNLF -HDMI --FakeSMC
http://www.hwsensors.com/releases --Audio https://github.com/vit9696/AppleALC --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN https://github.com/Mieze/IntelMausiEthernet -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders! Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others! We're all here to have fun and learn from each other! ENJOY!
EDITED - 9 JUNE 2018 - as all other issues resolved but am now stuck with QEMU Error: "PFLASH: Possible BUG - Write Block Confirm" details on testing lower in thread (to follow).
I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.
After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
I have now managed to get OVMF/Clover boot and install of MacOS Sierra.
I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.
So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager
As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of:
GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)
This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).
Using bare minimal Clover config.plist:
And following Clover UEFI drivers:
I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.
Here is my virtlib.xml dump for the virtual machine:
Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.