Welcome to osx86.net

If you need help with your Hackintosh we have all the drivers, kexts and bootloaders and other stuff that you hadn't figured out you needed yet. Register now to get access to all of the files and forums.


Spas

Members
  • Content count

    8
  • Joined

  • Last visited

  1. Finally. all my troubles were because of the source I've been using to install OS X. I found a source which installed automatically and smoothly and Clover Boot Loader on the installation USB drive booted the OS. There is one more possibility to boot the OS - from board's Internal EFI Shell. For this to work the HDD's EFI partition needs to be made bootable, for example by installing Clover in it, and then to put the EFI folder from the installing USB drive in it. (In case Clover has been installed for the purpose of making HDD's EFI partition bootable, its EFI folder is to be replaced.) Then, board's Internal EFI Shel needs the boot path HDD:\EFI\BOOT\BOOTX64.efi from which it invokes Clover Boot Loader. It boots the OS.
  2. I've got a working installation of OS X 10.11.6 El Capitan on Intel Server Board S5520HC. Not sure I'll tune it to match the board, though. Never the less, with a bootable HDD's EFI partition (after installing Clover in it for example) and the EFI folder from the installation USB drive in it and with a boot path for the board's Internal EFI Shell drive:\EFI\BOOT\BOOTX64.efi the board can invoke Clover Boot Loader which load the OS.
  3. Thank you for answering me. I've thought I need to find a better solution for the boot OS X process I've implemented but situation has changed and I'm almost at the beginning. The long story short seams like this: I've made a Clover boot installer, it installed OS X 10.11.6 on a target HDD, I've made the proposed changes to the EFI partition of target disk so as to make the OS X bootable and using the installer's USB I can boot the installed OS X El Capitan. But, ... an error on the installer's USB flash prevents me from new OS installation. I tried to generate a new Clover boot installer but still without success. The problem I see is: panic(cpu ...): Kernel trap at [], type 13=general protection Debugger called: <panic> Kernel Extensions in backtrace: com.apple.driver.AppleIntelCPUPowerManagement (218.0) Darwin Kernel ver 15.6.0 The situation is the same even when no AppleIntelCPUPowerManagement.kext is present in the Clover/kext/10.11 folder and NullCPUPowerManagement.kext is present there and in the root of USB drive, where I put it because even I put this extension in the Clover Cofigurator's Kernel and Kext Patches/ForceKextsToLoad nothing has happened, along with FakeSMC.kext and EFI folder. So, right know, I don't know what to do. When I've succeed making the bootloader I just followed the publication Install OS X 10.11 El Capitan on Hackintosh (Vanilla) knowing nothing. Now, I'm in a better form having some experience but, obviously, not enough knowledge. So, someone help me please.
  4. Let me finish this topic although I'm not finished yet. I've found this: I did that and using the installer to run its BOOTX64.efi Clover offered an option to boot the OS from the HDD and finally macOS 10.11 started on my machine. Not understanding this boot process, I'm not satisfied. The chain is: Clover boots from the boot installer, which boots from the HDD where the installed OS resides. (This OS is bootable by VNware also.) The HDD EFI partition contains a BOOT directory where there is a BOOTX64.efi and two more directories: Clover and BOOT. The last BOOT directory contains BOOTX64.efi also.
  5. I've copied /Volumes/SSD_Ext/System/Library/CoreServices/boot.efi to my macOS installation EFI folder. BIOS displayed the mac Lego and ... "Boot failed" I could't mount boot.efi while working on VMware.
  6. Thank you for answering me. I saw the answer after I've made some progress not having reached the final goal, though. What I have now is a working El Capitan - macOS 10.11.6 generated using a Clover installer. It is working because I can boot the system in VMware Workstation environment. My host cannot boot it and, I think, it cannot because neither I nor AMD BIOS can see a boot.efi file in the EFI partition. I've checked the EFI partition of the already booted system and saw: gEFI FAT32 non system disk Press any key to reboot. So, I think if I knew the boot.efi file for the installed system, maybe Clover should now it, and I save it in the EFI partition I can tell BIOS the path to it. That should be enough, although there could be problems with the BIOS but I have to handle them. So, I've seen the answer and tried this method but not a success - some errors I couldn't understand. Then tried another approach I've seen on youtube: diskutil mount /dev/disk0s1 I got a message saying something about redirection requested operation to the host system which could explain my previous unsuccessful attempt. Nevertheless, I think, this is not the way I need to follow. First, mount, as long as I remember, is establishing a link which is to be interpreted by the executing software. In the case of maxOS this should be OK, but my board BIOS understand a direct path of the form EFI\BOOT\BOOTX64.EFI or maybe shorter. This BIOS loads the OS (for example Microsoft Windows) from its EFI Shell. Here is what Intel say in their publication GUID Partition Table (GPT) How to install an Operating System (OS) using the GUID Disk Partition Table (GPT) on an Intel® Hardware RAID (HWR) Array under uEFI environment. So, I've been looking for something like macOS 10.11 boot.efi and found publications mentioning and replacing the boot.efi. But these all work with macOS. I've even found boot.efi developed in a project whose author says: So, I think I need the 64-bit file boot.efi, maybe from the System/Library/CoreServices, to copy it to the EFI partition and to set path to it in my board BIOS. I'm not a Macintosh user, I've forgotten UNIX shells long time ago, so help me please. If I cannot get the original boot.efi, which knows were the boot code is, I have to recompile the published boot32.efi to 64-bit and try it. So, really, help me, please.
  7. Something more: The Disk 1 below has been formatted by Mac Disk Utility during the process of installing OS X conducting by Clover. The 200 MB EFI partition is FAT32 and I can see in Explorer it is empty. Is this my problem at the moment?
  8. Hi, I'm doing my first attempts to install OS X 10.11.6 on an Intel S5520HC (Dual Xeon) machine. To get some results I need the path to the OS X boot loader. For example: The Windows 10 Installer boot loader path is X:\efi\boot\bootx64.efi So, if I knew the Clover installed OS X boot loader path I could invoke it. Can someone help with this? Thanks, Respectfully