Jump to content

Search the Community: Showing results for tags 'El Capitan'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • OSx86 Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Complete Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 372 results

  1. ****************************************************************************************************************************** IF YOU WANT A RAW COPY (THAT INCLUDES ACTUAL FORMATTING) OF THIS UNFINISHED GUIDE, ASK ME THROUGH PRIVATE MESSAGE, THEN MODIFY IT AND SEND IT BACK TO ME THROUGH PRIVATE MESSAGE, IT'LL BE A PLEASURE TO UPDATE IT, BUT I'M NOT ACTIVE HERE ANYMORE -- ALSO, IF YOU KNOW HOW TO HAVE THIS THREAD'S OWNERSHIP CHANGED AND WANT TO OWN IT, LET ME KNOW HOW TO PROCEED AS I DO NOT WISH TO KEEP IT FOR ME, THANKS! ****************************************************************************************************************************** Hi, I'm starting this new topic in the hope to, progessively, create a guide for a vanilla (as much as possible) OS X Installation on Z400/Z600/Z800 Workstations. I invite you to participate in the comments so that this topic becomes an easy-to-follow guide. The idea of doing this emerged from information exchanged with other members (proteinshake, MacPeet, zhangtemplar, MacUser2525, nitelava & apav) in topic titled "Fix my HP! Just a few random DSDT-edits to improve your HacMac experience." originally created by proteinshake. Main goals of this guide Explain manual procedures; Avoid "magical" utilities, but don't ignore them (they can sometimes be time/life savers); Make you become independent & aware of the inner mechanics of creating a functional Hackintosh, so that you can repeat & adapt those procedures for future hackintosh projects. *** AS THIS IS A WORK IN PROGRESS TOPIC, I WILL NEED SOME HELP TO GATHER ACCURATE INFORMATION *** HELP NEEDED, PLEASE READ THIS SECTION, THANKS! As I only own a Z400 Workstation, I'd need you (those who own Z600 and Z800 Workstations) to send me your lspci output. To do so, you have 2 options: Boot with a Linux LiveCD (see the Tools/Utilities/kexts or other useful links section at the bottom of this post); If you already have an OSX version installed, you'll need to install lspci (see the Tools/Utilities/kexts or other useful links section at the bottom of this post). Type the following command : lspci -nnvv >~/Desktop/lspci-nnvv_output.txt If you are using Linux, please also type this command (before creating the following, make sure you updated your BIOS to v03.57) : sudo cat /sys/firmware/acpi/tables/DSDT >~/Desktop/DSDT.aml OR: sudo cat /proc/acpi/dsdt >~/Desktop/DSDT.aml (whichever works for you) Copy those files to a USB flash drive, send them to yourself by email or whatever other method you want. Then, reply to this topic mentionning which workstation you have, and attach the file(s) created above. ALSO, if you got Clover to boot your Z400 / Z600 / Z800 Worktation, PLEASE send us your config.plist so that we can have a starting point. I'm trying to switch from Chameleon to Clover, but I'm still unable to fix a Kernel Panic I have; I will report it with a screenshot soon in the comments, maybe some of you might know why I get it. Requirements Another Mac or Hackintosh machine; 8GB+ USB flash drive; BIOS updated to latest version (v03.57, 2013-09-20 release, found HERE); This is mandatory for 2 reasons : patched DSDT files included in this guide will not work (properly) if you use a different BIOS version; that latest BIOS version fixes possible erratic behaviours with Xeon 3600 & 5600 CPU series. Z400/Z600/Z800 specific files (see Z400/Z600/Z800 specific information sections further below). BIOS setup instructions (eventually, there will be screenshots) You must set your hard drive controller to AHCI+RAID mode, else you won't be able to use your SATA devices. ... Generic instructions (for all downloads/credits, see Tools/Utilities/kexts or other useful links & All attached files sections at the bottom of this post) Get a copy of Yosemite Installer from the AppStore; Create a Yosemite boot DVD or USB (USB recommended); Partition & format the USB Flash Drive : Put your USB Flash Drive in a USB port; Open Disk Utility; Select your USB Flash Drive disk in the left pane; Click on the "Partition" tab in the right pane; Change "Partition Scheme" to 1; Click on "Options" at the bottom; Make sur you select GUID (first one) and click on OK; Give it a name, let's say Yosemite-Installer for the sake of this guide; Change "Format" to "Extended Mac OS (journaled)" (AFTER THIS STEP, YOU'LL ERASE YOUR USB Flash Drive, so make a backup first if you have important data on it!); Click on "Apply"; Create a USB Flash Drive with Yosemite Installer on it; Open Terminal; Copy/Paste the following command (make sure to verify the path names as they might differ slightly on your setup) - it will ask for your user password to elevate the command at root permission level : sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/YosemiteInstaller --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction Wait until it's completed (takes about 20 minutes, depending on your setup and USB speed); Into your volume's /System/Library/Extensions folder, copy the following kernel extensions (kext) : AHCIPortInjector_v1.0.0_Micky1979.kext.zip & IOAHCIBlockStorageInjector_v1.0.0_Micky1979.kext.zip - Those extensions make OS X detect your SATA controller. You'll get the "Waiting for root device..." message if you don't install those. (Couldn't yet find official page nor original thread for those, please let me know if you found it - credits seem to go to Micky1979); FakeSMC_v6.16.1372_netkas.kext.zip - emulates Apple's SMC chip found on Apple motherboards; NullCPUPowerManagement_v1.0.0d2_tgwbd.kext.zip - prevents kernel panic of genuine Apple Power Management; (optional for the install disk, this is to get sound working) VoodooHDA_v2.87.kext.zip (autumnrain, slice2009) - The file attached here is version 2.87 with a tweaked Info.plist to fix noise & volume issues for our workstations. According to my tests, HDADisabler kext is not needed (probably because original unpatched AppleHDA won't detect our Realtek ALC262 chipset). Now, let's rebuild that target volume's kernel cache with the following command : kextcache -f -update-volume /Volumes/YosemiteInstall Create the Extra folder on your Yosemite's install disk : mkdir -p /Volumes/YosemiteInstaller/Extra Install a bootloader Chameleon ... Clover ... ... Z400 specific information Instructions ... Files BIOS v03.57 - released on 2013-09-20 (latest realease known as of 20150711) dsdt-Z400-BIOS_v03.57-untouched.dsl.zip - Grabbed using Ubuntu LiveCD (this is NOT the patched DSDT); My latest patched DSDT files (USE AT YOUR OWN RISK!) dsdt-shdw_chatdeau-20150710-27-various_fixes.zip (includes both aml & commented dsl files); org.chameleon.Boot.plist.zip (not using SSDT with that version); For those who would know how to properly patch AppleHDA, here are the needed information files : AppleHDA_patch_request_ALC262.zip; lspci -nnvv output : Z400_lspci-nnvv.txt. Known problems Unable to find a working AppleHDA patch for Realtek ALC262 (sound is working using VoodooHDA with tweaked Info.plist, see Generic instructions section above); USB Mass Storage devices are ejected upon wake (PLEASE let us know if you know who to fix this!); Impossible to boot without -f flag in Chameleon, unless ALL kexts are in /System/Library/Extensions (which is not really a problem); ... Links ... Z600 specific information Instructions ... Files ... Known problems ... Links ... Z800 specific information Instructions ... Files ... Known problems ... Links ... Processor specific information Files Generated SSDT for Intel Xeon W3690 using Piker-Alpha's beta ssdtPRGen.sh script (USE THIS SSDT AT YOUR OWN RISK!) : ssdt-shdw_chatdeau-W3690.zip; Generated SSDT for Intel i7-930 (probably using Piker-Alpha's ssdtPRGen.sh script), found "somewhere" (UNTESTED - USE AT YOUR OWN RISK!) : ssdt_i7-930.dsl.zip. Links Intel® Core™ i7-930 Processor (8M Cache, 2.80 GHz, 4.80 GT/s Intel® QPI); Intel® Xeon® Processor W3690 (12M Cache, 3.46 GHz, 6.40 GT/s Intel® QPI); List of Macintosh models grouped by CPU type; Tools/Utilities/kexts or other useful links (not always OSx86 specific) Kernel Extensions (kexts) : AppleUSBXHCI.kext [patched] - "This is used for none-Intel chipset USB3.0 controllers. The AppleUSBXHCI.kext is based on Zenith432's patch."; GenericUSBXHCI (Zenith432) - "Open Source USB 3.0 xHC driver for OS X 10.7.5 - 10.10"; HWSensors [includes FakeSMC.kext] (blusseau, kozlek, slice2009) - "HWSensors is a software bundle that includes drivers and applications that allow you to access information from hardware sensors available on your Mac."; NullCPUPowerManagement.kext (tgwbd) - "[Plays] a couple of tricks with the IOKit service registration process to ensure it takes over the AppleIntelCPUPowerManagement match category on its IOResources provider nub"; VoodooHDA (autumnrain, slice2009) - "VoodooHDA is an open source audio driver for devices compliant with the Intel High Definition Audio specification. It is intended as a replacement for AppleHDA on Mac OS X with support for a wide range of audio controllers and codecs."; Kext tools : Kext Wizard (janek202) - Repairs kext permissions & rebuilds kernel caches; Bootloaders : Chameleon (ErmaC, Kabyl, Tamás Kosárszky, JrCs, etc.) - "Chameleon is a Darwin/XNU boot loader based on Apple's boot-132."; Chameleon Wizard (janek202) - "helps to install, update and download latests revs of this bootloader"; Clover Configurator (mackie100) - Helps you configure Clover Bootloader options; Clover EFI bootloader (apianti, blackosx, blusseau, dmazar, slice2009) - "EFI-based bootloader for BIOS-based computers created as a replacement to EDK2/Duet bootloader"; Clover third-party tools - Clover FixDsdtMask Calculator (cvad) & Clover builder (cvad); Clover Utilities (blusseau, kozlek, slice2009) - "Preference pane for Clover bootloader". Audio / HDA : Apple Hardware Dumps (tea blog) - Dumps of system information from original Apple computers (ioreg, acpi, lspci, audio codec dump, etc.); HDA Wizard for Mountain Lion (janek202) - Tool that helps you patch AppleHDA (apparently works with Yosemite); it was not yet possible to use this to successfully patch AppleHDA for Z400/Z600/Z800 Realtek ALC262 chipset (using VoodooHDA for now, see attachments in the Generic instructions section). Power Management : Intel Power Gadget (Jun De Vega @ Intel) - "Intel® Power Gadget is a software-based power usage monitoring tool enabled for 2nd Generation Intel® Core™ processors or later.". [Note : This won't work with Nehalem processors. I use (and prefer) HWSensors' HWMonitor]. DSDT / SSDT / binary patching : Apple Hardware Dumps (tea blog) - Dumps of system information from original Apple computers (ioreg, acpi, lspci, audio codec dump, etc.); ACPICA iASL & Intel ACPI Tools 20150619 / github repository (ACPICA) - "The ACPI Component Architecture (ACPICA) project provides an operating system (OS)-independent reference implementation of the Advanced Configuration and Power Interface Specification (ACPI)."; HexPatcher (EvOSX86) - Universal / generic hex patcher for any kind of Mac OS X binary; MaciASL (phpdev32) - "A native AML compiler and IDE for OS X, with syntax coloring, tree navigation, automated patching, online patch file repositories, and iASL binary updates."; ssdtPRGen.sh Beta (Piker-Alpha) - "Script to generate a SSDT for Power Management". Hardware / system information : DPCIManager (phpdev32) - "DPCIManager lists all of the PCI devices attached to your machine, along with their PCI IDs, vendor name, and device name. It will also retrieve the kext loaded for that device, important when troubleshooting."; lspci v1.1 (EvOSX86) - "lspci is a command on Unix-like operating systems that prints ("lists") detailed information about all PCI buses and devices in the system. It is based on a common portable library libpci which offers access to the PCI configuration space on a variety of operating systems". Misc : Ubuntu Desktop LiveCD; Yosemite in the AppStore; XtraFinder (Tran Ky Nam Software) - "[Adds] Tabs and features to Mac Finder". All attached files (oldest is first, newest is last) AppleHDA_patch_request_ALC262.zip AHCIPortInjector_v1.0.0_Micky1979.kext.zip IOAHCIBlockStorageInjector_v1.0.0_Micky1979.kext.zip NullCPUPowerManagement_v1.0.0d2_tgwbd.kext.zip VoodooHDA_v2.87.kext.zip FakeSMC_v6.16.1372_netkas.kext.zip dsdt-Z400-BIOS_v03.57-untouched.dsl.zip dsdt-shdw_chatdeau-20150710-27-various_fixes.zip ssdt-shdw_chatdeau-W3690.zip ssdt_i7-930.dsl.zip org.chameleon.Boot.plist.zip Z400_lspci-nnvv.txt ... more to come! - chatdeau
  2. hi people you can use this thread to link / talk about of the future Nvidia Web Driver updates for El Capitan 10.11.6 Nvidia Web Driver - 346.03.15f14 --> build 15G20015 (thanks to DMCrimson) New! Nvidia Web Driver - 346.03.15f13 --> build 15G20015 (thanks to Louvier) Nvidia Web Driver - 346.03.15f12 --> build 15G19009 (thanks to WeBeRiO) Nvidia Web Driver - 346.03.15f11 --> build 15G18013 (thanks to BreBo) Nvidia Web Driver - 346.03.15f10 --> build 15G17023 (thanks to Badruzeus) Nvidia Web Driver - 346.03.15f09 --> build 15G1611 (thanks to Badruzeus) Nvidia Web Driver - 346.03.15f08 --> build 15G1510 (thanks to Badruzeus) Nvidia Web Driver - 346.03.15f07 --> build 15G1421 (thanks to bb1045) Nvidia Web Driver - 346.03.15f06 --> build 15G1217 (thanks to bb1045) Nvidia Web Driver - 346.03.15f05 --> build 15G1212 (thanks to WeBeRiO) Nvidia Web Driver - 346.03.15f04 --> build 15G1108 (see this post) Nvidia Web Driver - 346.03.15f03 --> build 15G1004 (thanks to BreBo) Nvidia Web Driver - 346.03.15f02 --> build 15G31 (thanks to Moviemakergr) Nvidia Web Driver - 346.03.15f01 --> build 15G31 (thanks to WeBeRiO) [uPDATE_3]Nvidia Web Driver - 346.03.15b01 --> build 15G24b (thanks to DMCrimson) 10.11.5 Nvidia Web Driver - 346.03.10f02 --> build 15F34 (thanks to marcozardi) Nvidia Web Driver - 346.03.10f01 --> build 15F34 (thanks to WeBeRiO) [uPDATE_2] Nvidia Web Driver - 346.03.10b01 --> build 15F31a (see this post) 10.11.4 Nvidia Web Driver - 346.03.06f01 --> build 15E65 (see this post) Nvidia Web Driver - 346.03.06b01 --> build 15E (see this post) 10.11.3 Nvidia Web Driver - 346.03.05f02 --> second release for build 15D21 (thanks to Fljagd) Nvidia Web Driver - 346.03.05f01 --> build 15D21 (see this post) Nvidia Web Driver - 346.03.05b02 --> build 15D (see this post) 10.11.2 Nvidia Web Driver - 346.03.04f02 --> second public release (see this post) Nvidia Web Driver - 346.03.04f01 --> build 15C50 (see this post) Nvidia Web Driver - 346.03.04b02 --> build 15C48a (see this post) Nvidia Web Driver - 346.03.04b01 --> build 15C47a (see this post) 10.11.1 Nvidia Web Driver - 346.03.03f02 --> second public release (see this post) Nvidia Web Driver - 346.03.03f01 --> build 15B42 (thanks to jperkins909) 10.11.0 Nvidia Web Driver - 346.03.02f02 --> build 15A284 (thanks to MTWomg) Nvidia Web Driver - 346.03.02f01 --> build 15A284 (see this post) DP Nvidia Web Driver - 346.03.01b07 --> GM/DB/PB6/DB7/PB5 (thanks to BreBo) Nvidia Web Driver - 346.03.01b06 --> build 15A (thanks to MTWomg)
  3. Run Vanilla OS X El Capitan, Sierra, or High Sierra in VMware Workstation 12 on a Windows Host I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host. The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh. There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there…. I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program. Requirements Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack 1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder. 2. Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg 3. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes…. 4. Open OS X terminal, then run the following commands to execute the script: cd downloads chmod +x CECI.tool ./CECI.tool 5. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later. Update: @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362. Install and Patch VMware Workstation 12 on your PC 1. Download and install VMWare Workstation Player 12 or later 2. Download and extract Unlocker 2.0.7 or later to your USB stick… 3. Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt. Create an El Capitan Virtual Machine 1. Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”. Choose “I will install the operating system later” at the How will you install screen…. 2. Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version. By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder. 3. Under Specify Disk Capacity, you can leave the default 40GB or set a larger value. I personally store the virtual disk as a single file. Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12. 4. Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier. 5. To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file). The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad). 6. For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine. 7. Finally click “Play virtual machine” Installation of El Capitan Installation should be relatively straight forward, just following the prompts of the OS X installer: 1. Select language, agree to legal terms 2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan. 3. Quit DU and choose Macintosh HD to install El Capitan on. 4. After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot… 5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish… 6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple…. 7. Finally, you will arrive at the El Capitan Desktop. You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”. This will allow you to install VMware Tools…. 8. After rebooting, the VM can now be resized or run at full screen resolution. Audio and network/internet should also work OOB. SMBIOS Customization and iMessage Vars To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS - eg for an iMac 11,3 SMBIOS, you can enter the following lines.... smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation. The critical variables for iMessage/Facetime activation are MLB & ROM. By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk. If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0").... efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to "<=>?@A". Vanilla Mavericks and Yosemite The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware. With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie To create a Mavericks ISO on your desktop cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5... Enjoy Update for Sierra 10.12 The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13. Update for High Sierra 10.13 See post#30 & post#41 which describes how to build "Install macOS High Sierra.app" on the fly from installer files downloaded beforehand in /SharedSupport folder. CECI.zip CYI.tool.zip CMI.tool.zip
  4. Hi guys, I need testers who have netbook with Intel Atom or Celeron Processor I want to know, whether the kernel boots or not and If not, then upload an image with Details of what point the system gets stuck with information what bootloader do you use. thx 10.11.6-IPCA.zip
  5. crazybirdy

    El Capitan MBR Patch

    Version 10.11.6

    15,843 downloads

    Patched OSInstall.mpkg and OSInstaller.framework to allow OS X 10.11 installation on MBR partition. To use those patched files you must follow HowTo-10.11.x to create an USB installer. You can't just run the app downloaded from Mac App Store. The patch is made base on 落下爱@pcbeta 10.10.x patch method How to make 10.11 installer for MBR? Open /Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg/BaseSystem.dmg first. 1. Restore BaseSystem.dmg to HFS partition and rename the partition’s name as OSXMBR as /Volumes/OSXMBR/ 2. Copy InstallESD.dmg/BaseSystem.dmg to /Volumes/OSXMBR/ 3. Copy InstallESD.dmg/BaseSystem.chunklist to /Volumes/OSXMBR/ 4. Copy InstallESD.dmg/AppleDiagnostics.dmg to /Volumes/OSXMBR/ 5. Copy InstallESD.dmg/AppleDiagnostics.chunklist to /Volumes/OSXMBR/ 6. Remove /Volumes/OSXMBR/System/Installation/Packages 7. Copy InstallESD.dmg/Packages to /Volumes/OSXMBR/System/Installation/Packages 8. OSInstall.mpkg replace to /Volumes/OSXMBR/System/Installation/Packages/OSInstall.mpkg OSInstaller replace to /Volumes/OSXMBR/System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller 9. Copy InstallESD.dmg/Packages/Essentials.pkg/System/Library/Kernels/kernel to /Volumes/OSXMBR/System/Library/Kernels/kernel (use Pacifist v3.2.14 to access the contents of Essentials.pkg, and make directory /System/Library/Kernels first.) (Need kernel only if you use Chameleon with -f to boot the installer disk, needn't with Clover.) 10. Boot to /Volumes/OSXMBR/ to install Mac OS X. Work fine with Clover Work fine with Enoch and /Extra/kernel.plist with <key>KernelBooter_kexts</key> <string>Yes</string> 10.11.6.15G1011 10.11.6.15G31 10.11.5.15F34 10.11.4.15E65 10.11.3.15D21 10.11.2.15C50 10.11.1.15B42 10.11.0.15A284 If you want to patch MBR by yourself, here is the patch code, works on 10.11.0 ~ 10.11.6 perl -pi -e 's|\x48\x8B\x78\x28\x48\x85\xFF\x74\x5F\x48\x8B\x85|\x48\x8B\x78\x28\x48\x85\xFF\xEB\x5F\x48\x8B\x85|g' OSInstaller codesign -f -s - OSInstaller
  6. Hello, I will explain how i have installed Os X EL Capitan 10.11 on HP ElibteBook 820 G2. Before start this installation, or buy this computer, you have to know that it's hard to find a compatible wifi/BT module. This guide still not 100% perfect. This allow to install: - El Capitan Public Beta 1 (10.11.0) - El Capitan Public Beta 2 and above (10.11.0) Yosemite 10.10.x doesn't support Broadwell processor and so can't be installed. Working: - Wifi and Bluetooth doesn't work, you have to find a compatible wifi/bt card with NGFF M2 slot. this one is compatible: Dell DW1560 part code: 6xRYC - SD card reader. - Display port on the dock station Needed materials: - a mac or hackintosh - usb drive - external hard drive (if you do fusion on post-install) Other solution: You can use HP Probook Installer Clover Edition 6.4 or up to install El Capitan. It doesn't add anything more than working with my guide. It will define you mac as a MacBookAir7,2. 1/Create Bootable USB Installer 2/ Configurer le Bios 3/ Installer le système Mac sur le disque dur 4/ post installation 5/ DSDT 6/ SSDT. 7/ Fusion drive 8/ ENJOY !! 9/ Ressources and thanks All greatings to Rehabman
  7. Hi guys. Sometimes I am a complete noob, so I deleted two kexts from S/L/E and now my Asus Q200E laptop with OS X El Capitan boot hangs on kernel panic. I still can enter go through Clover to reach Recovery Mode and use Terminal, so I've put the two kexts on a USB pendrive and after some struggle I've managed to succefully copy them using Terminal, but the boot is still stuck on kernel panic. As I remember, these are the commands I've typed: mount -rw cp -a /Volumes/usb-stick/name.kext /Volumes/my-osx-drive/System/Library/Extensions Is there anything else I should do? Is anything wrong? Should I type some command else? For instance, should I type something to fix permissions and rebuild cache? Thanks a lot!
  8. fusion71au

    EFI_Clover for VMware

    Version r4385

    803 downloads

    Clover r4385 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation. Tested with unlocked Workstation 12.5 running OSX 10.9 -->10.13 guest in Windows X64 host. Installation 1. Download and unzip "EFI_Clover_r4385 for VMware.zip". Mount Clover-v2.4k-4385-X64.iso by double clicking on it. 2. Mount your VM's EFI System Partition eg in terminal 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.
  9. Version Driver:5.0.1.25 Utility:

    6,942 downloads

    This is a new updated kext and utility directly from MediaTek for the MT7610U and MT7612U network chipset. This utility was updated and released on January 20th 2016 on MediaTek website. I have the Netgear A6210 AC1200-WiFi USB 3.0 Adapter and it works perfectly under OSX 10.11.2 with USB 3.0 and 5GHz networks being recognized. It should work for any card with one of those two chips. UPDATE 10/1/2016 I have had some serious trouble updating my system to macOS 10.12 Sierra but I have finally seemed to have gotten it working. When I have done a clean install and installing this package afterwards, It didn't seem to work. However after updating a working copy of El Capitan to Sierra with this package already installed, it seems to work. So as of this post, this same package does work under macOS 10.12 Sierra but you might have some trouble like I have until mediatek performs their own official update. UPDATE 10/26/16 I have finally figured out what is going on with this installer package. When you run this package as is, it will not install the kext on macOS sierra. It will install the wireless utility and all associated files but not the actual kext. I have included the kext as a standalone as well. Install the Kext with kext utility then run the installer pkg. Reboot and you will have a perfectly working USB wireless stick. Confirmed working macOS 10.12.1
  10. Version v2.5

    32,849 downloads

    A Minimal and Super Fast Kext Installer and Repair Permissions for Mac OS This app is written in Swift Description : Drag one or several Kexts,Bundle,Plugin,PPP on the application (not a folder) Double Tap on "Drop your kext here" to select several Kexts,Bundle,Plugin,PPP on the application manually Change destination as desired (LE or SLE) Backup is created at Desktop Option to save log Choose auto-mode , when automode is not selected you have to press Install button after dragging files Use Drag-Drop or manually browse (click on drop section) files to select New option : Right click on kext , select open with EasyKextPro and rest will be automatically, you don't need to open app New option : Drag kext to EasykextPro icon and rest will be automatically , you don't need to open app Note : for Mac OS 10.12 and greatersudo spctl --master-disable for EL Capitan and Sierra disable SIP or use 0x03 For Yosemite use kext-dev-mode=1 Restart is required after installation
  11. Atasher

    Help! ASUS K501UX

    Hey guys, I am fairly new to the scene and recently successfuly installed El Capitan 10.11 on the Asus K501UX The specs are: Core i7-6500u, 8GB RAM, GTX 950M (DISABLED), HD520 Everything seems to be in good working order thanks to Ludwig Bartholomew for guiding me and helping me through the process. But, I keep recieving a Kernel Panic everytime I have the VoodooI2C kext installed for the trackpad to function. If I remove it everything works fine except for the trackpad which is the issue. Note: I also removed all of the LPSS kext files from the S/L/E to no avail. Any help would be greatly appreciated. Thanks in advance.
  12. Run Vanilla OS X El Capitan, Sierra or High Sierra in VirtualBox 5.0.34 on a Windows Host Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh. There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there…. I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg @colt2 HOW TO: Create a bootable El Capitan ISO for VMware @dsmccombs comment on faking Ivybridge Processor @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6 @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg. VirtualBox Forum: Status of OSX on OSX Requirements Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine Oracle VM VirtualBox v 5.0.34 Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack 1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder. 2. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes. Note: you will need approx 16GB of free space on your hard disk for the script to complete. 3. Open OS X terminal, then run the following commands to execute the script: cd downloads chmod +x CECI.tool ./CECI.tool 4. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later. Create an El Capitan Virtual Machine in VirtualBox 1. Open the VirtualBox program and click the "New" button to create a new VM. 2. Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version. I named my Virtual Machine "El_Capitan", then clicked next... 3. Leave the Memory size at the recommended 2048 MB, then click next. 4. Choose to "Create a virtual hard disk now", then click the create button. 5. For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare. Click next... 6. For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space). 7. On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger. When you click the create button, you will now see your new VM in the VirtualBox main GUI. 8. Click the settings button on the Main Menu to tweak a few settings.... a. On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?) b. On the System/Processor tab, you can increase the allocated CPU cores to 2 c. On the Display tab, you can increase the allocated Video Memory to 128MB d. On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". Navigate and select the El Capitan ISO we created earlier... e. Click the OK button to finalise the VM settings. Patch El Capitan vbox configuration file with DMI Settings from a Mac 1. From the start menu, type cmd and click run as administrator to open an administrative command prompt. 2. Choose a Mac Model similar to your host system, then type the following lines, followed by <enter> after each line. Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick... Eg iMac11,3 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3. Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors. You can try from one of the following if this happens: To spoof Lynnfield i5 750 CPU VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4. Close the command prompt window. Installation of El Capitan We are now ready to start the El_Capitan Virtual Machine.... Installation should be relatively straight forward, just following the prompts of the OS X installer: 1. Select language, agree to legal terms 2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan. 3. Quit DU and choose Macintosh HD to install El Capitan on. 4. After 20-30 min (depending on how fast your system is), the installation will complete. At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive. The VM is now ready to reboot into OS X from the virtual hard drive. 5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish… 6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple…. 7. Finally, you will arrive at the El Capitan Desktop. 8. Network/internet and audio should work OOB but on my system, the sounds were distorted. Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). Customization with VBoxManage 1. You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt: cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively. Update: For VirtualBox 5.2.x, the command for changing screen resolution has changed... VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution) eg VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2. Adding serials and other SMBIOS details for the System Information Screen VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html. Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware. With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie To create a Mavericks ISO on your desktop cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5... Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above). Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free . UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51. UPDATE macOS High Sierra 17A365: For macOS High Sierra, use CHSI.tool in post#73. Good luck and enjoy CECI.tool.zip CYI.tool.zip CMI.tool.zip
  13. Hey guys, This is a tutorial on how to fix (or at least try to fix) the second stage boot, when you're having these issues: missing logo and loading bar being displayed on the bottom left corner of the screen. Might or might not work for other issues. So proceed with caution. This is an issue that I experienced starting with early stages of development in Yosemite. Still continued in El Capitan. So this thread is primarily for these two versions of Mac OS X. Not sure it will work on earlier versions, cause I never tried it. So far it worked in Yosemite, El Capitan and Sierra. Please, note that I did not test this on all video cards. So it might or might not work, depending on that. Don't take this as a final solution for everything. Also, I'm pretty sure this won't work with iGPUs. So I would strongly suggest to look around for solutions if that's your case. This tutorial is not for multiple display setups! Please, don't use it for that! Especially not in iGPU + dedicated GPU combos. Known issue: if you're using the auto-login feature, try to disable it and use the regular login screen. Otherwise you won't get the second stage boot (confirmed as fixed in Sierra). This tutorial would have not been possible without the help and insight of: Pike R. Alpha cecekpawon Mirone Riley Freeman So all the credit goes to them. I just put this together based on my successes and failures. Succesfully tested with: NVidia cards: GeForce 210 GT 640 GTX 650 GTX 660 GTX 670 Superclocked+ 4GB - works partially (ok for 1080p, with CSM disabled, but no second stage in higher resolutions) GTX 750 Ti - works partially (ok for 1080p, but no Apple logo for second stage in higher resolutions) GTX 760 GTX 780 GTX 960 GTX 970 - works partially (ok for 1080p, and 1440p with CSM disabled, but no second stage in higher resolutions) ATI cards: Sapphire Toxic R9 270X Might work on other graphic cards, as well. But these are the ones that worked so far. Please, share if you got good results with another video card. Also, the same thing can be achieved by modding your DSDT. Unfortunately this thread does not make the object of that method, nor am I able to help you with that, since I really have no idea how to mod a DSDT, so far. Also, to be honest, this method seems a bit easier. Nonetheless, try this at your own risk! I'm not responsible for any damage that you might cause to your computer/components etc. Also, please, note that this tutorial is not perfect. I'm doing my best to make it as easy to understand as possible. Also, I'm opened to suggestions and I'm doing my best to improve this in the future. Still, it's not perfect. So keep that in mind. Suggestions are appreciated though. Please, note that, if you've got a video card with GOP UEFI Bios, you most likely don't need this tutorial in the first place. All you need is to disable CSM in BIOS (motherboard dependent). Note that, by doing this, only GPT drives will be loaded. So if you've got Windows installed on another drive, for example, you won't be able to select it anymore, if it's installed in "legacy" mode. With that being said, let's get to work. Prerequisites: Mandatory: a computer running Mac OS X Yosemite or newer Clover bootloader (changes are gonna be saved to the config.plist file) IORegistryExplorer v 2.1 (attached) gfxutil (attached) gfx_hex (attached) - script credit to cecekpawon Optional: Sublime Text Editor Clover Configurator a Windows PC for reading the graphic card's VBios version. So far, I couldn't find a way to do it from OS X. But if you know how to do it, please, share. I'll update this accordingly. An alternative (though not really the same thing) is this. an USB installer might come in handy, so keep one close by. Extra: If you want to try the modded Bootx64.efi (rev 3279), thanks to cecekpawon, featuring an option to easily enable/disable string injection in Clover (in case you're stuck outside your OS, and don't have a USB drive or something else to boot from), click here to get it. Please, note that this revision might not work with newer versions of OS X/macOS. You will need to replace the one in your EFI/EFI/CLOVER folder. If you want to revert to the previous one, you can either reinstall Clover, or make a backup of your current one before replacing it. I would recommend creating a single folder with all the necessary files and tools and putting it on your Desktop, just to have all the needed things in one place. Note: If you use a custom SSDT/DSDT, I would try first without it, and using Clover's patches instead, so that you minimize the risk for failure due to custom DSDTs. I don't use a custom DSDT, didn't test in collaboration with a custom DSDT, so I don't know if it will work. If you wanna try it this way, I would love to know your results. What to do: Step 1 (establishing the port): Open up your IOreg file (or just open IORegistryExplorer if you don't want to save it as a separate file), and search for "display". You should see something like this: Now, depending on your card, you might have more or less ports. The important thing is to note the one that has the AppleDisplay attached to it. In this example, the second port (B@1) is the one in use. So that's the one we need to set as default. Please, note that they start at 0, so first port is A@0, the second one is B@1 and so on so forth. Step 2 (extracting device-properties.hex): Open up a terminal window, navigate to the desktop folder you're using, and do this (make sure gfxutil is present into that folder): ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;' > "device-properties.hex" && ./gfxutil -s -n -i hex -o xml "device-properties.hex" "device-properties.xml" This will extract two new files into that folder: device-properties.hex and device-properties.xml Step 3 (modding the device-properties.xml): Open up the xml file using any text editor (I'm gonna use Sublime here) and ADD the number of ports you need for your card (the same number of ports, with the same name as in the IOreg) and the rest of the information, as described in the example below (use the attached xml as reference): Don't forget that the first port is port 0! In this example, we're using an MSi GTX 650 OC with 2GB of RAM, which has 3 ports, and we want to set as default port #2 (B@1). Attached you can find my device-properties.xml file, if you wanna use it as reference. The first section will set port B@1 as default. Change this according to your case. <!-- Primary display --> <key>@1,AAPL,boot-display</key> <string>0x00000001</string> Whereas on the bottom you can see regular values. Here we can set the amount of VRAM, the name of the card and the VBios version. <key>VRAM,totalMB</key> <string>0x00000800</string> // for 2048 MB or 2 GB of RAM <key>device_type</key> <string>NVDA,Parent</string> <key>model</key> <string>MSi GeForce GTX 650</string> // Name of your card <key>rom-revision</key> <string>80.07.35.00.04</string> //VBIOS version In my experience, these values are rather cosmetic than anything else. For an accurate version of your VBios, you can use either the Nvidia driver on Windows, or any hardware information software like GPU-Z, aida64 or nvflash. Here's a little table with hex values for different amounts of RAM. If you need other values than the ones specified in this table, please, ask. Also, if you spot a mistake, let me know so I can correct it. Amount of memory Hex value 128 MB 0x00000080 256 MB 0x00000100 512 MB 0x00000200 1024 MB (1 GB) 0x00000400 2048 MB (2 GB) 0x00000800 3072 MB (3 GB) 0x00000C00 4096 MB (4 GB) 0x00001000 5120 MB (5 GB) 0x00001400 6144 MB (6 GB) 0x00001800 7168 MB (7 GB) 0x00001C00 8192 MB (8 GB) 0x00002000 9216 MB (9 GB) 0x00002400 10240 MB (10 GB) 0x00002800 11264 MB (11 GB) 0x00002C00 12288 MB (12 GB) 0x00003000 13312 MB (13 GB) 0x00003400 14336 MB (14 GB) 0x00003800 15360 MB (15 GB) 0x00003C00 16384 MB (16 GB) 0x00004000 Once we're done modding, we're gonna save the changes and convert the xml file back into hex, using this command: ./gfxutil -i xml -o hex device-properties.xml device-properties.hex Step 4 (reading the modded hex): Unpack gfx_hex (attached) file into your working directory and double click to run it. It should output the content of your modded hex into a terminal window, and it should look something like this: Select and copy that code. After that, open up Clover Configurator and paste that hex code in Devices -> Properties section (see below) and check the box for Inject. You can also add this manually into the config.plist file, if that's more of your thing. Step 5 (setting up final arrangements): We're almost done. But, if your experience is the same as mine, at this point you only got the loading bar back centered. Which, of course is a step forward. But we're not quite there yet. So, to add the logo as well, we will check the boxes for Patch VBios and Inject EDID in Clover Configurator (Graphics section). You can inject your own EDID if you have one. Though, in my experience, Clover does a really good job in adding the correct one itself. So you don't really need to add a custom EDID. Just to use Clover's InjectEDID feature. Also, in my experience, you don't need CsmVideoDrv.efi for this to work. And I've got pretty similar results with and without it. So, if you have issues with it, you can try without it, and vice-versa. When it's all done, save the changes to your config. Now, I would highly recommend you to make a backup of your current config.plist from EFI/EFI/Clover/config.plist anywhere you want. You might need it later. When that's done too, replace the config.plist in your Clover folder with the one you just modded, and restart. Keep your fingers crossed (toes too). And hope for the best. If everything ok, you should have a pretty close to perfect second stage boot. If not, you might have nothing or an unbootable system. To fix this, boot from your USB installer, or use boot flag nv_disable=1 (for Nvidia cards), upon booting, and revert the changes. Or, if you already know where is the problem, fix that and restart. That's it. Please, let me know if it worked for you. gfx_hex.zip IORegistryExplorer.app.zip gfxutil.zip device-properties.xml
  14. Introduction With Whatevergreen.kext we already have a workaround for the AMD GPU wakeup issue which first arose with the release of El Capitan, but as a workaround is just a second class solution for a problem I decided to trace back the reason for the issue to it's origin and this post is the result of my research. As I used a R9 270X to do my research, which is the only AMD GPU I have, my patch has only been verified to work properly with this chip but according to the information sources I used, I have no reason to believe it won't work on other AMD GPU's too. In case there is still some uncertainty left in a particular point, I will mention this explicitly. Materials Used The Linux kernel sources of the Radeon driver in order to get a better understanding of the GPU's internals: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/radeon?h=next-20171013 A copy of the ACPI 6.0 specs in order to find out how to dump the chip's control register space. A disassembler, e.g. objdump in Terminal or the trial version of Hopper Disassembler. What I Did As it's been a well known fact that wakeup with AMD GPUs still works with El Capitan and Sierra provided you select the IGPU as primary GPU enabled CSM and use Legacy VBIOS of the AMD GPU in BIOS setup. I was wondering what is different with UEFI VBIOS and decided to I create dumps of the GPU's control register space while using Legacy VBIOS with CSM enabled and while using UEFI VBIOS with CSM disabled in order to find out. Comparing the register space contents it became obvious where the root of the problem lies and how it can be fixed with a DSDT patch. Technical Background Using Legacy VBIOS only the primary GPU is initialized by the VBIOS, i.e. only the IGPU is initialized while the AMD GPU is left untouched. When OS X boots up the framebuffer controller kext will find the AMD GPU in vanilla state, initialize it properly and wakeup will work as expected. That's also the reason why you have to blind boot in this configuration. Using UEFI VBIOS the AMD GPU will be initialized too, provided it has a display connected to one of it's ports. You'll see the BIOS splash screen and will be able to access the BIOS settings but unfortunately macOS's framebuffer controller kext will notice that the GPU has already been initialized and skips the basic setup so that the configuration made by the VBIOS will be used and this is the point where things start to go wrong because this configuration seems to be broken causing wakeup to fail. First of all you have to locate the AMD GPU in your DSDT. In my case it can be found at _SB.PCI0.PEG0.PEGP but it needs to be renamed to GFX0 for AppleGraphicsDevicePolicy.kext (AGDP) to work properly. This can be done manually or using a Clover patch (this is what I did) and I assume that this problem has been already solved before. The reason why I mention it explicitly here, is that you should be aware of it and don't get confused when your AMD GPU has a different name in the DSDT than in IORegistry. Second, we need to get access to the GPU's control register space. According to the Linux sources, PCI Base Address Register 2 (BAR2) is used to address the control register space on Radeon HD5000, HD6000 and HD7000 GPUs. It's a 64bit base address register but newer GPUs (BONAIRE and above, i.e. Radeon HD8000 and HD9xxx) are different as the use BAR5 instead of BAR2. Unlike BAR2, BAR5 is a 32bit base address register. On my R9 270X (PITCAIRN) BAR5 is zero so that I decided to use this as an indication to use BAR2 but I must confess that I haven't checked if it works for all supported GPUs too. In case my patch doesn't work for you, be aware that this might be a pitfall! The Radeon driver's source code tells us that the first display controller engine's registers can be found starting at offset 0x6800. It also tells us a lot about the meaning of the register contents. Using Legacy VBIOS my R9 270X's display controller engine's registers are still at their default values when macOS boots: 00006800 01 00 00 00 08 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | With UEFI VBIOS the display controller engine's registers look quite different. Using the Linux driver sources you can easily make sense out of these values and will discover that I've got a 4K display connected to my R9 270X which is configured to it's native resolution using 32 bits per pixel. 00006800 01 00 00 00 0a 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 0f 00 00 f4 00 00 00 |................| 00006820 f4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 0f 00 00 70 08 00 00 00 00 00 00 |........p.......| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | The rest was just a little bit of laborious work and trial and error, comparing register contents, understanding their meanings and see what happens when you reset these registers to their default values. If you try to play around with your GPU's control registers a little bit more, be prepared to get a garbled screen for a few seconds. After all I've managed to create a DSDT patch which fixes the wrong registers while preserving screen output during boot and, most important, solves the wakeup issue. The Patch Putting things together I created a DSDT patch to fix the incorrectly initialized registers. With this patch applied, I now have working wakeup with my R9 270X under Sierra (10.12.6) using UEFI VBIOS with CSM disabled in UEFI setup. No kext patches or additional kexts are needed anymore for sleep/wake to work properly with my R9 270X anymore. I can see the BIOS splash screen on my display and can access UEFI setup but the best of all is that there hasn't been a single wakeup issue since I applied this patch. Device (PEGP) { Name (_ADR, Zero) // _ADR: Address OperationRegion (PCIB, PCI_Config, Zero, 0x0100) Field (PCIB, AnyAcc, NoLock, Preserve) { Offset (0x10), BAR0, 32, BAR1, 32, BAR2, 64, BAR4, 32, BAR5, 32 } Method (_INI, 0, NotSerialized) // _INI: Initialize { If (LEqual (BAR5, Zero)) { Store (BAR2, Local0) } Else { Store (BAR5, Local0) } OperationRegion (GREG, SystemMemory, And (Local0, 0xFFFFFFFFFFFFFFF0), 0x8000) Field (GREG, AnyAcc, NoLock, Preserve) { Offset (0x6800), GENA, 32, GCTL, 32, LTBC, 32, Offset (0x6810), PSBL, 32, SSBL, 32, PTCH, 32, PSBH, 32, SSBH, 32, Offset (0x6848), FCTL, 32, Offset (0x6EF8), MUMD, 32 } Store (Zero, FCTL) Store (Zero, PSBH) Store (Zero, SSBH) Store (Zero, LTBC) Store (One, GENA) Store (Zero, MUMD) } } In case you have in-detail questions or need AML code for debugging (code to dump BARs or to dump the GPUs control register space) please let me know. I'm willing to share all my information in order support further research. Below you can find the register dumps I created attached to this post. FAQ Do I still have to select the IGPU as the primary display? No. Although I haven't tried this on my own, user chh1 confirmed that this is no longer required when using the patch (please see http://www.insanelymac.com/forum/topic/328549-tracing-back-the-amd-gpu-wakeup-issue-to-its-origin/?do=findComment&comment=2519884). Nevertheless I still recommend to select the IGPU as primary as there is absolutely no reason not to do so, in particular as the IGPU will be unusable for multimedia acceleration on Haswell based systems when it's not the primary one (IGPU's dev id is different when it's not the primary one). ​When I boot into macOS I always end up with a black screen. Does your patch solve this problem too? No, it doesn't. This patch solves the wakeup issue, nothin more and nothing less. The black screen after boot is either the result of a connector problem (please create a connector patch for your graphics card using the well-known methods) or the result of a problem with AGPM as certain system definitions (in particular recent iMacs) select special configurations for graphics power management. In order to achieve proper operation of AGPM it is crucial that your GPUs have correct names in the DSDT matching those listed in the AGPM configuration for the system definition (IGPU for the Intel GPU and GFX0 for the AMD GPU on iMac15,1, iMac17,1 and iMac18,x). You may patch your DSDT manually or use a Clover DSDT-patch to fix the device names. Credits vit9696 for developing Whatevergreen.kext and pointing me to the right direction. RehabMan for developing ACPIDebug.kext The Linux Radeon driver kernel developers for providing me with the background information I needed. Legacy.bin.zip UEFI.bin.zip
  15. Hi insanelymac, I'm using a Dell All in one Inspiron 5348. It has a Pentium dual core G3240 Haswell clocked at 3.07 ghz in Mac. I've successfully booted and installed Mac Os X el capitan on an external hdd using a fake cpuid (0x0306E0) its ivybride. But my problem is the drivers. The only thing I could remotely do is wifi. I've installed the kexts for my wifi card. What I need is to install intel hd graphics (desktop) kexts and audio drivers (alc668) I've tried doing every method. Except for Ddst because I don't understand it whatsoever.Also found this thing called xcpm and was wondering if I can just spoof the graphics ids or something like that. Hopefully you guys can help me and thanks!
  16. specs: Intel® Core™ i5-2450M CPU @ 2.50GHz Lenovo base board 4gbsingle channel ram intel hd 3000 Wi-Fi 802.11b/g/n Wi-Fi Model Atheros AR9285 Wireless Bluetooth Bluetooth 2.1+EDR Finally installed el captain successfully i tried many ways but was unable to install a working bootloader or any kexts Could someone help and tell me how to install a bootloader which is easy and good And how to install the basic kexts like audio wifi keyboard and trackpad
  17. This thread is a walkthrough on how to install El Capitan. These are fully detailed instructions to make it easier for newbs. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW. THANKS I wanna start off by thanking the following guys whose efforts inspired me to proceed in making this guide: stinga11 for his implementation of the FakeCPUID hack, rehabman for his kexts, ammulder for his Skylake Starter Guide, chris1111 and DwarfVador for their configuration setup ideas, Slice for Clover, toleda for his audio solution and vit9696 for his audio solution, and shout outs to Pike for the IOAPIC Fix and assisting me with applying his ssdtPRGen.sh script SSDT generation method. • MY SPECS: 1. Intel Pentium Processor G4500 2. ASUS Z170M-PLUS Micro ATX Motherboard 3. Mushkin Enhanced ECO2 512GB SSD 4. Corsair Vengeance LPX 16GB (2x8GB) DDR4 5. HGST Travelstar 7K1000 1TB 2.5" 7200RPM HDD 6. Seagate Barracuda 3TB 3.5" 7200RPM HDD ST3000DM001 7. LEPA AquaChanger 240 Liquid CPU Cooler 8. Corsair Carbide 88R Mid-Tower Case 9. LG Electronics 14x SATA Blu-ray Rewriter 10. PNY GTX 960 XLR8 4GB 11. EVGA SuperNOVA 750 G1 750W PSU • WHAT YOU WILL NEED: 1. Mac OS X 10.11 El Capitan [from Mac App Store] 2. A computer running an Intel Processor 3. Access to OS X on VMWare (for Windows), Mac, or Hackintosh 4. A supported graphics card 5. Clover v2.3k r3354 and up 6. A USB flash drive at least 8 GB 7. Update your system with the latest BIOS • STEP 1: BIOS SETTINGS 1. Start off by entering the BIOS and accessing Advanced Mode. Go to Exit to select 'Load Optimized Defaults'. 2. Go to Boot and disable 'Fast Boot' and go to CSM (Compatibility Support Module) to enable 'Launch CSM'. 3. Back out to Boot and scroll down to Secure Boot and access Key Management to disable 'Secure Boot State'. In order to do so you must clear any installed keys [delete each keys]. a. Access Secure Boot again and set OS Type to 'Other OS'. 4. Scroll down to Hard Drive BBS Priorities to set boot sequence of the available hard disks. 5. Go to Advanced → System Agent (SA) Configuration and disable 'VT-d'. 6. Scroll down to access Graphics Configuration and set 'Primary Display' to PCIE and disable 'iGPU Multi-Monitor'. 7. Back out to Advanced and scroll down to access APM Configuration → 'ErP Ready' and disable it [equates to "S3 only, Suspend to Ram"]; the rest of the options should be disabled by default. 8. Go to Advanced → CPU Configuration and disable 'Intel Virtualization Technology'. 9. Scroll down to CPU Power Management Configuration to disable 'CFG lock'. 10. Go to Advanced → Onboard Devices Configuration and turn off 'Serial Port Configuration' and 'Parallel Port Configuration'. 11. Go to Advanced → USB Configuration and enable 'XHCI Hand-off'. 12. [Optional] Go to Ai Tweaker → Scroll down to 'DRAM Frequency' and set it to the specified frequency of your memory. 13. [Optional] Go to Tool → ASUS Overclocking Profile to save your BIOS settings profile [to a USB stick]. 14. Go to Exit, 'Save Changes & Reset'. • STEP 2: CREATING A BOOTABLE USB TO INSTALL OF EL CAPITAN 10.11 1. Clover and the OS X installer are placed on separate partitions on the USB stick. This guide will use 'diskutil list' in Terminal instead of Disk Utility to format the USB with GPT partitioning for Clover UEFI support. 2. You must determine its disk identifier before you can partition the USB. Plug the USB stick into a Mac (or Hackintosh), run Terminal and type 'diskutil list'. The following screenshot will serve as a reference: As you can see the the USB stick’s identifier is /dev/disk2. 3. Type the following entry into Terminal to format the USB stick (two partitions, via GPT): diskutil partitionDisk /dev/disk2 1 GPT HFS+J "OS X" R During the process the following occurred: /dev/disk2 GPT partitioning initiated by default EFI was automatically created remainder "OS X", HFS+J is partitioned 4. It resulted in the following screenshot: Close Terminal 5. We need to download and install the latest version of Clover (here) on the USB stick. a. Run the pkg, "Change Install Location" by selecting "OS X" (partition name) as the target of the install. Use the following settings below: Make sure that it shows "Installation Complete." NOTE: When installing to HDD select "Install RC scripts on target volume" and/or "Install all RC scripts on all other boot volumes" and "Install Clover Preference Pane". 6. You must copy your kexts to the EFI/ Clover folder. You can use EFI Mounter v3 when necessary to mount the EFI partition, just use "diskutil list" first to ensure you chose the right one for the USB stick. a. Remove EFI/CLOVER/kexts/10.6, 10.7, 10.8, 10.9, 10.10, leaving just '10.11' and 'Other'. b. Copy the required kexts FakeSMC.kext, NullCPUPowerManagement 1.0.0d2, VoodooPS2Controller.kext, and your ethernet kext (Intel I219-V) IntelMausiEthernet-V2.1.0d5 or AppleIntelE1000e 3.3.1 to the following directory: /EFI/CLOVER/KEXTS/10.11. NOTE: If you are having trouble getting Ethernet to work you can also try copying IONetworkingFamily.kext from S/L/E to /EFI/CLOVER/KEXTS/10.11 with your networking kext. 7. We must apply the following mandatory patches: a. IOAPIC Fix. Without this fix most things such as USB, SATA, ethernet, many PCI devices, sound devices, etc will not work. ○ Use a text editor or a plist editor like PlistEdit Pro to modify your config.plist manually. Add this <dict> entry to EFI/CLOVER/config.plist in the KextsToPatch array: <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>Skylake APIC fix, discovered by Pike R. Alpha</string> <key>Find</key> <data> wegQD7bw </data> <key>Name</key> <string>AppleAPIC</string> <key>Replace</key> <data> vhcAAACQ </data> </dict> </array> b. FakeCPUID patch. Since the Pentium is not supported in 10.11, the following CPUID will convert it into an Ivy Bridge CPU. Add this <dict> entry to the config.plist: <key>KernelAndKextPatches</key> <dict> <key>FakeCPUID</key> <string>0x0306A0</string> <key>KextsToPatch</key> </dict> or [Lynnfield] <key>KernelAndKextPatches</key> <dict> <key>FakeCPUID</key> <string>0x0106E0</string> <key>KextsToPatch</key> </dict> c. USB patch. It is required to raise the port limit in order to boot the USB installer. Otherwise garbled text with the message "Still waiting for root device" and a circle with a slash in the middle will appear onscreen. This process involves installing USBInjectAll.kext as well. Add this <dict> entry to the config.plist: <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>change 15 port limit to 30 in AppleUSBXHCIPCI</string> <key>Find</key> <data> g72M/v//EA== </data> <key>Name</key> <string>AppleUSBXHCIPCI</string> <key>Replace</key> <data> g72M/v//Hw== </data> </dict> </array> Be sure to copy USBInjectAll.kext to /EFI/CLOVER/KEXTS/10.11. d. SMBIOS. With the config file still opened in your text/plist editor, scroll down to SMBIOS section to add the following SMBIOS system definition: <key>SMBIOS</key> <dict> <key>Manufacturer</key> <string>Apple Inc.</string> <key>ProductName</key> <string>MacPro3,1</string> <key>Trust</key> <false/> </dict> NOTE: Macmini6,2, iMac13,2 and iMac13,1 support speedstep. You can also do this using Clover Configurator: In the SMBIOS section, click the magic wand to select a SMBIOS relevant to your hardware (e.g. iMac14,2) – and close the screen and File/Save. e. GUI. Here you indicate the theme you want to use that you installed by entering the title in the string. I chose to use "random" as shown below: <key>GUI</key> <dict> <key>Mouse</key> <dict> <key>DoubleClick</key> <integer>500</integer> <key>Enabled</key> <true/> <key>Mirror</key> <false/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <true/> <key>Theme</key> <string>random</string> </dict> f. Boot Flag. NVIDIA graphics cards especially 'Maxwell' currently lack support natively in OS X. To correct this problem in order to boot the installer it requires "nv_disable=1". In addition to that, it is necessary to use "-v" to monitor if any problems arise. Add this <dict> entry to the config.plist: <key>Boot</key> <dict> <key>Arguments</key> <string>-v nv_disable=1</string> </dict> g. SIP. Apple has implemented 'rootless' security or System Integrity Protection (SIP) (reference sources 1, 2, & 3) in 10.11 which restricts users from modifying system folders/files, and as a result it locks down system folders and files against hacks and root attacks, making the system safer. However, SIP must be disabled in order to install anything (i.e., kexts) into protected system folders. Add this <dict> entry to the config.plist: <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x3</string> </dict> h. Audio Fix. This Skylake board comes with a Realtek ALC887 audio chip. Realtek onboard audio device has been changed in ACPI to 'HDAS'. In order to use toleda's CloverALC (discussed further in this guide), you must add the following patch in the config.plist: <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Patches</key> <array> <dict> <key>Comment</key> <string>Rename HDAS to HDEF</string> <key>Find</key> <data> SERBUw== </data> <key>Replace</key> <data> SERFRg== </data> </dict> </array> 8. Preparing OS X partition. Download OS X v10.11.0 (15A284) El Capitan [Mac App Store]; "Install OS X El Capitan" will be in /Applications. a. Right-click "Install OS X El Capitan" → Show Package Contents → Contents → ShareSupport → Double click to mount "InstallESD.dmg". b. Once "OS X Install ESD" appears, use ShowHiddenFiles to show hidden files. c. Now you will see an image called "BaseSystem.dmg" appear. Mount it by right-clicking and opening it with DiskImageMounter... d. Open Disk Utility. Select and highlight the volume "OS X Base System", click "Restore" at the top-right, drag the volume into "Source" field, and drag the USB [OS X] partition (you already created) to the "Destination" field where you will restore the image: click the "Restore" button then "Erase"... e. After the process is complete, you'll now have (2) "OS X Base System" present in Finder. Eject the image "BaseSystem.dmg" and close Disk Utility. f. On the remaining volume "OS X Base System" (USB stick), go to System/Installation and delete Packages symlink. g. Open "OS X Install ESD" in a new Finder window, and copy the Packages folder to System/Installation folder inside "OS X Base System". h. Copy BaseSystem.chunklist, BaseSystem.dmg, AppleDiagnostics.chunklist, and AppleDiagnostics.dmg from "OS X Install ESD" and copy it to the volume root. i. Create a new folder named "Kernels" in System/Library on the USB stick. Use Pacifist v.3.2.17+ to extract "kernel" from "OS X Install ESD/Packages/Essential.pkg [/system/Library/Kernels/kernel]" and place "kernel" into System/Library/Kernels/ location. Or download the vanilla version here. j. Delete following kexts from System/Library/Extensions/: AppleIntelCPUPowerManagement.kext and AppleIntelCPUPowerManagementClient.kext. k. Use ShowHiddenFiles to hide the hidden files, and quit the application. l. With the USB installer ready, remember before restarting system to change boot priority of USB stick to first to install El Capitan on the hard disk of choice. m. Once installer is finished, it will automatically restart the system. n. Now reboot from the USB installer and select the drive where you installed El Capitan at the boot menu screen and use boot flag nv_disable=1 to log in. • STEP 3: Mac OS X 10.11 Post-Installation 1. As the system is loading, you'll be prompted to the Mac OS X Welcome screen. a. Select your country then click "right arrow" to go to the next screen. b. Select "My computer does not connect to the Internet." c. Select "Don’t transfer any information now." d. Do not "Enable Location Services on this Mac" e. Agree to "Terms and Conditions." f. Enter your name, password, and hint and Continue. g. Confirm "Diagnostics & Usage" h. Wait a moment for the OS X desktop to load. i. When prompted to back up any disk with Time Machine, click on the "Don't Use" button. • STEP 4: Mac OS X 10.11 Post-Installation (Continued) 1. Mount the EFI partition of the USB stick with EFI Mounter v3 and copy the 'EFI' folder to the EFI partition of El Capitan boot disk. 2. Install Clover v2.3k on the El Capitan install HDD partition you plan to boot from. In addition to the settings configured earlier, select "Install RC scripts on target volume" and "Install Clover Preference Pane" when installing to the HDD. Installing RC scripts enables nvram variables required for iCloud and other services. It processes logs that are located in /Library/Logs/CloverEFI. You can also type bdmesg > Desktop/boot.txt in Terminal to get them manually. 3. Edit the config.plist from your boot disk in EFI/CLOVER/ by adding the following <dict> entries: a. Change boot flag to "nvda_drv=1" without "-v" <key>Boot</key> <dict> <key>Arguments</key> <string>nv_drv=1</string> </dict> NOTE: Ensure you have updated to the latest version FakeSMC kext. If your 'hack' happens to instant reboot loop randomly like mine did, to fix it I added cpus=1 in the boot arguments in Clover config.plist. Boot arguments: nvda_drv=1 cpus=1 SMBIOS: iMac14,2 system definition Situations may vary when accessing 10.11 with GTX 960 Video output should be connected through HDMI b. Hide UEFI partitions. To hide internal UEFI (i.e., "Boot Windows from Recovery", "Boot Windows from EFI") you have to use Scan/Legacy=false: <key>GUI</key> <dict> <key>Scan</key> <dict> <key>Legacy</key> <false/> </dict> c. Designate name of boot menu entries (Renaming Mac/Windows). In the Clover bootloader menu you will notice all EFI Windows partitions labeled "Boot Microsoft EFI boot menu from EFI [or SYSTEM]". The Windows partition is called EFI but there's also a Mac partition called EFI which is hidden by default in the Clover boot menu so it's a nonfactor. The volume names are what Clover shows by default. In order to change what the Clover boot menu shows your volume name to be you will have to specify its details under GUI/Custom/Entries section in your config.plist. There are 3 <key> tags necessary to edit in this section: Volume, FullTitle, and Type. You can refer to my personal settings below for help. E.g., in my config.plist, my OS X volume is called "ELCAP" because that's what I named the partition I installed OS X on. It can also be seen as a bootloader screen entry as "Boot Mac OS X from XXXXXXXX" where XXXXXXXX is the volume name. "FullTitle" is the name you want the entry to say, i.e.: OS X 10.11 El Capitan. "Type" is where you indicate what type of OS it is, i.e.: OSX (or Windows). Tags such as "Hidden" and "Disabled" are self-explanatory, while the "NoCaches" tag designates whether you want to boot without caches. NOTE: Adding "InjectKexts" causes infinite loading on the Apple logo screen. NOTE: Although you’re able to indicate if the "VolumeType" you are using is Internal, External, Optical or FireWire, I have found through tests that after adding the "VolumeType" tag for the OS X volume in the config.plist followed by restarting my system, it would initiate a constant reboot loop, making my system incapable POSTing and requiring a CMOS reset to fix: YOU HAVE BEEN WARNED. <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Volume</key> <string>EFI</string> <key>FullTitle</key> <string>Windows 10</string> <key>Hidden</key> <false/> <key>Disabled</key> <false/> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Volume</key> <string>ELCAP</string> <key>FullTitle</key> <string>OS X 10.11 El Capitan</string> <key>Hidden</key> <false/> <key>Disabled</key> <false/> <key>InjectKexts</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>VolumeType</key> <string>Internal</string> </dict> </array> </dict> d. Remove Recovery partition. Deleting and merging a partition with 'diskutil' from the command line is the most precise method to remove the partition since it targets the recovery disk directly and merges it with the full El Capitan partition. ○ Launch the Terminal and type the following into the command line: diskutil list ○ This will print out your drives partition scheme and look something like this: ○ Look for "Recovery HD" and see which identifier it is uses. In this screenshot it’s disk2s3. ○ To remove that partition we use the following command (you can also use the volume name): diskutil eraseVolume HFS+ Blank /dev/disk2s3 ○ The partition will be erased. You’ll now have a blank partition sitting around, so you’ll want to merge that with your other El Capitan partition: diskutil mergePartitions HFS+ ELCAP disk2s2 disk2s3 ○ This will merge the two partitions, with disk2s2 absorbing the space from disk2s3 and expanding, it causes data loss so don’t expect this to preserve anything. 4. 10.11.0 breaks compatibility with native graphics kexts so you will not be able to boot without nv_disable=1 flag. a. Download and install NVIDIA Web Driver 346.03.02f02 to enable NVIDIA Graphics Cards because they won't work OOB without them. NOTE: Remember to go to the NVIDIA Driver Manager menu bar at the top, change the settings to use Web drivers. Changes will take effect after restart. 5. Reboot without the USB installer and choose the El Capitan boot disk. 6. Download CUDA 7.5.20 drivers (increases GPU computing performance) needed for 10.11.0 support and install. 7. [OPTION 1] Install AppleALC to enable native audio by injecting the layout id supported for ALC887 through dynamic patching without modifying any kexts. Audio will no longer be affected after each OS X update and SIP can remain enabled. More details here. NOTE: AppleHDA must be native, original and unpatched. a. Mount EFI partition and add the following entry under Devices/Audio in the config.plist to inject working layout id 11 (or 13 or 1). <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <integer>11</integer> </dict> b. Download the latest version of AppleALC and copy it to CLOVER/kexts/10.11 or CLOVER/kexts/Other. NOTE: Rebuild kext cache if you have removed a modded AppleHDA to replace it with a native one by using Kext Utility or 'force rebuild cache' in Terminal: sudo –s sudo touch /System/Library/Extensions 8. [OPTION 2] Install the following patch associated with Realtek ALC887 AppleHDA Audio (by Toleda): a. Mount EFI partition, verify "Disable SIP" entry CsrActiveConfig=0x3 is in config.plist. b. Download audio_cloverALC-110.command.zip and extract "audio_cloverALC-110_v1.0q10.command". c. No edits made to any native AppleHDA.kext file, 2-4 files added to Resources folder. NOTE: There may be noticeable pops before starting playback which is caused by OS X putting the audio codec to sleep. Disable AFGLowPowerState in config.plist with following <dict> entry: <key>Devices</key> <dict> <key>Audio</key> </dict> <key>AFGLowPowerState</key> <false/> </dict> If popping is still exists after using the method above, try using antipop. NOTE: There may be noticeable distortion after around 2 minutes of audio playback. Update to the latest version of Clover (or downgrade to ver. 3354) and add UseARTFrequency=false entry in the config.plist: <key>CPU</key> <dict> <key>UseARTFrequency</key> <false/> </dict> <key>Devices</key> <dict> 9. Create a DSDT??? (More to come later) 10. [OPTION 1] Create a SSDT (Secondary System Description Table) to configure the maximum clock speed. a. Download Pike's ssdtPRGen.sh script which should auto-copy into your home directory, 'Volumes/Users/<username>' folder. Open Terminal and type the following: curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh b. Next, set the execute/search bits: chmod +x ~/ssdtPRGen.sh c. Run ssdtPRGen.sh script for first time without any arguments and let it download all the data that you need: ./ssdtPRGen.sh d. The Skylake.cfg with Pentium information should have already downloaded. e. Once finished you will have the ssdt.aml on the ~/library/ssdtPRGen/. Move it to /EFI/CLOVER/ACPI/patched. NOTE: If you come across issues try the following: ○ Use Terminal to ensure Skylake.cfg is in the 'Data' folder by typing: open ~/library/ssdtPRGen/Data ○ You can remove any previously generated and downloaded script file by typing: sudo rm -R ~/Library/ssdtPRGen ○ You can rerun another freshly downloaded ssdtPRGen.sh script with your processor type: ./ssdtPRGen.sh ○ For additional help see also: ./ssdtPRGen.sh -help 11. [OPTION 2] Create a SSDT (Secondary System Description Table) to configure the maximum clock speed. a. Download the Pike’s script v14.1 (modified for i-core processors) and put it on your desktop. Use it only for the PC it is running from. The script reads some information specific about your CPU and its number of cores. b. Open Terminal and type "sudo" then leave a space and drag the script file into the Terminal window then leave a space and type in the Turbo Speed (Maximum Turbo Frequency) for your processor and then press enter. e.g., Intel Pentium G4500 type code: sudo /Users/"YourUsername"/Desktop/ssdtPRGen.sh -TURBO 3500 Type your password when prompted and press Enter. c. Ignore the following "Error: Unknown processor model ..." since the CPU is unsupported. d. A decompiled file called SSDT.aml will generate in a hidden folder "tmp". Type "open /tmp" (no quotations) to reveal its location. e. Mount EFI using EFI Mounter v3 and place SSDT.aml into /Volumes/EFI/EFI/CLOVER/ACPI/patched/ 12. Installing the following kexts/widget is optional. Mount the EFI partition to copy the kexts into the /EFI/CLOVER/KEXTS/10.11 folder. Install the widget using Launchpad → Dashboard: ○ HWSensors 6.19.1406 Binaries (with FakeSMC): Helps you monitor CPU, memory, disks, network, temperatures, fans, load/uptime, and processes. ○ Install iStat Pro 4.92 r2, a highly configurable widget that lets you monitor every aspect of your Mac including CPU, memory, disks, network, battery, temperatures, fans, load & uptime and processes. • STEP 5: Updating to 10.11.4 1. Download and install OS X El Capitan 10.11.4 Combo Update. 2. After restarting, booting from the El Capitan partition presents the following error: OsxAptioFixDrv: Error - requested memory exceeds our allocated relocation block a. This is caused by the lack of support for the OsxAptioFixDrv-64 in 10.11.4 which is intended to fix memory map issues on most UEFI systems, mainly in AMI BIOS. b. Plug the USB installer into another Mac (or Hackintosh) and reinstall the latest version of Clover (here) on the USB stick. Be sure to select the checkbox OsxAptioFix2Drv-64 instead of OsxAptioFixDrv-64. c. Once it completes, mount EFI of the USB stick using EFI Mounter v3 and remove OsxAptioFixDrv-64.efi from /EFI/CLOVER/drivers64UEFI/. 3. Reboot using the USB installer and choose the El Capitan install drive. Mount EFI of the El Capitan partition and remove OsxAptioFixDrv-64.efi and copy OsxAptioFix2Drv-64.efi from the USB stick to /EFI/CLOVER/drivers64UEFI/. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-110.command.zip [for OPTION 2]. 5. Accept the popup window that prompts you to download and install the latest the NVIDIA Web Driver 346.03.06f01 to proceed. Download CUDA 7.5.26 drivers needed for 10.11.4 support from NVIDIA and install and reboot. • STEP 6: Updating to 10.11.5 1. Download and install OS X El Capitan 10.11.5 Combo Update. 2. After restarting, accept the popup window that prompts you to download and install the latest the NVIDIA Web Driver 346.03.10f01 to proceed. 3. Download CUDA 7.5.29 drivers needed for 10.11.5 support from NVIDIA and install and reboot. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-110.command.zip [for OPTION 2]. • STEP 7: Updating to 10.11.6 1. Download and install OS X El Capitan 10.11.6 Combo Update. 2. After restarting, accept the popup window that prompts you to download and install the latest NVIDIA Web Driver 346.03.15f01 / NVIDIA Web Driver 346.03.15f02 to proceed. 3. Download CUDA 7.5.30 drivers needed for 10.11.6 support from NVIDIA and install and reboot. 4. Reinstall audio by patching AppleHDA with audio_cloverALC-110.command.zip [for OPTION 2]. config-WORKING for G4500 boot.plist.zip EFI-Mounter-v3.zip ssdtPRGen.sh-master.zip
  18. Hello guys, Greetings from Brazil! I am running Mac OS X El Capitan 10.11.6 on my hackintosh and I am getting kernel panic at start and / or restart. It's random. Sometimes it happens and sometimes it doesn't. My hackintosh is as described below: Mac OS X El Capitan 10.11.6 from AppStore Motherboard Gigabyte G41MT-S2P F3 Intel Core 2 Duo 8 Gigabytes of RAM Video GeForce 9500GT 1 Gigabyte 2 SATA HD Samsung 500 Gigabytes each NEC uPD720200 USB 3.0 Host Controller Any suggestions? Thank you very much. I really appreciate your time and help! Best regards,
  19. ASUS N550JV I'd been working on this computer since of the beginning of 2014 and I can say that OS X is pretty stable on it with El Capitan 10.11.4 [EDIT] Some news about Sierra Well... In June 2017 I finally cross the line and I bought the MacBook Pro 14,3 dropping my N550JV, that's why I'm not gonna help you with Sierra. However, since Apple hardware seems to be buggy sometimes (or bad luck ?), my MacBook Pro motherboard died after only 3 months. Not so good for a 3000€ laptop... Student, but also freelance web developper, I need my (working) laptop everyday. But Apple seems to considerate that paying a product 3000€ is not enough to get a free replacement device ASAP when a failure happens. The warranty will take the motherboard replacement fees, but my MacBook won't be available during 6 or 7 days : what a loss of income ! That's why I told the vendor that I have no choice but returning to Hackintosh to be able to work. And I decided to try to boot my Time Machine backup on my N550JV. After some ajustements, it worked and I'm now running my MacBook image on the N550JV. I fixed QE/CI, touchpad and wireless, but I still miss the TouchBar... I have no time to explain the steps to make it work but you can find the clover folder I used to run 10.12.6 right here. You just have to install the updated versions of BrcmPatchRam and VoodooHDA in /S/L/E to have Bluetooth and Audio. This work is dirty but I hope it will help you to get Sierra running on the N550JV. Components (submodel N550JV-CM193H) CPU : Intel i7-4700HQ IGPU : Intel HD 4600 DGPU : Nvidia Geforce 750M 4GB DDR3 Chipset : Intel HM86 Express WLAN + Bluetooth : Qualcomm AR9485 b/g/n 1x1x1 Mimo (HalfMiniPCIe) + AR3012 Bluetooth 4.0 (USB interface) LAN : Realtek RTL8168/8111 Sound : Realtek ALC 668 Touchpad : Elan Touchpad (v4 ?) Screen : 15.6" - 16:9 Resolution 1920 x 1080 + Touchscreen (Elan) Webcam : USB 720p by AzureWave SD Card reader : RTS 5139 Optical : Blu-Ray reader / writer Notes : I replaced the optical drive with an SSD (Crucial M550 512Gb) I replaced the AR9485 with the BCM94352 a/b/g/n/ac 2.4/5Ghz Wifi 2x2x2 Mimo -> needed to get WLAN working and after all, 2.4Ghz + 802.11n sucks when you try 802.11ac + 5Ghz Current State Working : Intel i7-4700HQ (near all P-States) Intel HD 4600 with native screen resolution and GFX acceleration Sound - Realtek ALC668 Sleep USB ports Ethernet WLAN with BCM94352 Bluetooth Elan touchpad Keyboard Battery (about 2h30 but my computer is near 3 years old) Touchscreen Webcam Not Working : Nvidia Geforce 750M (disable by DSDT because the card is not connected to the screen or external ports) SD Card reader (no drivers but passthought with VMware Fusion and Windows is working) Not checked : Sound on HDMI Bluetooth Handoff (should be working) Installation process (to complete) prepare OS X installer (Vanilla) install Clover EFI and use my clover folder (config + dsdt + kexts..) after installation, install BrcmFirmwareRepo and patchRam2 + VoodooHDA on /S/L/E config.plist is not completed. You have to add the serial number to get iCloud, iMessage, etc.. to work. I cannot share mines. Looks for TODO in the plist. CPU Section near all P-States are working (800Mhz to 3.4 Ghz in Turbo Boost) all cores work properly OEM CPU SSDT are dropped by clover SSDT is generated at boot by clover DMAR table is dropped so you can let VT-d activated IGPU Section Full QE/CI at native resolution thought internal screen (LVDS or eDP ?) Handled correctly my 2560 x 1440 monitor throught the Mini Display port HDMI is working fine to but seems to lock at max 1920 x 1080 Brightness is working (levels are defined in PNLF Device of DSDT) Config : ig-platform-id : 0x0a260006 FakePCIID_IntelHD to get the drivers attached to the device _DSM Method in DSDT Inject Intel : true (redondant) Bugs : Glitch at boot Glitch on installer screen : close and open the lid Glitch on external display connection : close and open the lid or put the computer to sleep at least once before connecting the external display DGPU Section The Nvidia card is connected to the IGPU (Optimus setup), but this configuration is not supported by OS X, so we can't use this card. disabled at boot and on wake by the DSDT no problems for the moment Sound Section 4 speakers with an EADP + 1 subwoofer I'm not convinced by AppleHDA sound quality at this time I'm using VoodooHDA 2.8.8 with a custom config and all is working great I'm not using the subwoofer so I can't say if it is working Bugs : sound stops for 3 seconds sometimes (quite rarely) There is no sound from internal speaker is you reboot from Windows or shutdown with fastboot enabled. -> can be fixed with codec Commander (mandatory kext if you choose to use AppleHDA) I didn't check sound on HDMI or DP USB Section USB ports take me a lot of time after the El Capitan update USB setup : 3 external USB 2 ports (inside USB 3) 3 external USB 3 ports 4 internal USB 2 ports : Webcam Touchscreen SD Card Reader USB interface for bluetooth on the MiniPCIe port With 10 ports we are under the 15 limit, so I decided to get away FakePCID_XHCmux EHCI drivers are not loaded by OS X, all is handle by the stock XHCI drivers : there is no EHCI routing at all, like we are used to see these time. All is handle in the DSDT, on the XHC section with a complete rewrite of the _UPC name, following the ACPI specs No mods are needed in Apple files Stay away from Android File Manager or patch it because it have a bad effect on USB drivers, even on real Macs Battery Section Battery registers are patched on DSDT following the Rehabman post AppleSmartBatteryManager kext to read the values from ACPI Sleep Section sleep works fine by closing the lid or waiting for the laptop to sleep I disabled the wake from network option because I'had some problems with it, and I don't use it Power nap is disabled too for me but it should work I didn't check sleeping with Apple Icon -> sleep Stay away from Android File Manager or patch it because it have a bad effect on USB drivers and this can affect sleep WLAN + Bluetooth AzureWave AW-CE123H HMB (Broadcom BCM94352 chipset) _DSM method to enable it 5 ghz working with clover patch + cosmetic patch Bluetooth enabled using BrcmFirmwareRepo and BrcmPatchRAM2 (installed on /S/L/E for best results) to upload the proprietary firmware at boot and on wake bluetooth works most of the time but sometimes the firmware upload fails and you have to restart to fix it BT Handoff should be supported but hasn't been checked ACPI Section I used Bios v208 (latest) DSDT and SSDT(s) are merged together because I'm too lazy to edit them separately All oem ssdts are dropped at boot -> could be change later Patchs (some of them) : add DTGP, B1B2 (for battery) rename GFX0 to IGPU rename EHC1 and EHC2 to EH01 and EH02 (not useful) patch XHC section to match the hardware (_UPC) replace _Q0E and _Q0F + add SKBL and GKBL for the touchpad and the FN keys -> see the EMlyDinEsH post add _DSM to IGPU, ARPT (BCM94352), PS2K, LPCB, EHC1, EHC2, XHC add MCHC, IMEI, SMCD, BUS0, PWRB patch HPET, RTC, TIMR, HDEF, HDAU 's IRQ disable DGPU at boot and at wake patch OS detection patch battery register -> see Rehabman post (B1B2, etc...) ​fix some warnings errors and warnings : WMI device and OEM _BCM method remarks : method serialized, _T_x to T_x TO DO complete the guide clean DSDT switch to AppleHDA bios patch to enable Haswell Lake Tiny Thanks A big thanks to all the people who have worked on it, like amokk - he has done most of work on the DSDT to get it fine for Mavericks. I edited it for Yosemite and El Capitan. I'm not the creator of the kexts or dsdt patch I used. We have to thank : - Rehabman - PikerAlpha - EMlyDinEsH - slice - Mieze - and all the others N550JV-OSX.zip
  20. Apple changed something in the CoreWlan.framework and the trick with airportd from Snow Leopard doesn't work now. I wrote a simple menubar app like the Apple's WiFi menu. This menubar app uses AirPort.framework from Snow Leopard instead of CoreWlan.framework and Apple80211.framework from El Capitan. Here is my step-by-step guide how to make Wi-Fi work: Put your working IO80211Family.kext from Snow Leopard into /System/Library/Extensions. Disable airportd: sudo -i (enter root password) cd /System/Library/LaunchDaemons/ launchtl unload com.apple.airportd.plist mv com.apple.airportd.plist com.apple.airportd.plist-disabled Put AirPort.framework into /System/Library/PrivateFrameworks/ Rebuild kext cache. Repair permissions. Reboot There is also a console version of the menubar app with some advanced options like iwconfig from linux. For example you can set a different locale code to get more channels, change power save mode or manually set transmission rate. Credits: Jonathan Levin - http://newosxbook.com/articles/11208ellpA-II.html Comex - https://gist.github.com/comex/0c19c1b3fa569f549947 Files.zip Version 2.0 (Requires Airport.framework from the Files.zip above): Aerodrome v2.zip Here is a build with default Apple82011.framework. Use it if you have OOB wlan and want to change locale code etc. aerodrome-apple80211.zip
  21. Boa noite, estou com dificuldades para atualizar o clover. Eu abro o clover configurator, baixo a ultima versão, instalo e reinicio porém ele nunca sai da versão 4200, sendo que quando eu abro o clover instalado na preferencias do sistema ele me mostra que estou na versão 4200 mostra que tem um atualização disponível mas quando clico para atualizar ele fala que está na ultima versão
  22. Hello, I was initially running a Hackintosh that I built and set up using TonyMac as a guide, but at the time I didn’t realize that TonyMac was closed-source. So now I have an Intel chip PC ( Intel Core i7-4770K Quad-Core Desktop Processor 3.5 GHZ 8 MB Cache ) with a Gigabyte motherboard GA-Z87MX-D3H. I would like to build a fresh Hackintosh setup using InsanelyMac as the guide, but I was wondering if there would be issues with my hardware and I was wondering where the best guide on InsanelyMac exists to do that.. I want to install OS X.11 El Capitan, but I notice that my Gigabyte motherboard ( GA-Z87MX-D3H ) has not been listed as a potential component for hardware compatibility for that OS: http://wiki.osx86project.org/wiki/index.php/HCL_10.11.6 It is important that I install El Cap because certain software that I use is not compatible with newer OS’es. I notice that this site doesn’t endorse TonyMac, yet it gives a link on the Installation Guide page ( http://wiki.osx86project.org/wiki/index.php/Installation_Guides ) to the “Always up to date guide to building a Hackintosh” on Lifehacker ( http://lifehacker.com/the-always-up-to-date-guide-to-building-a-hackintosh-o-5841604 ) which is a link that explains the TonyMac method of installation. And also there isn’t any information supplied about installing OS X11 on the initial link in this paragraph even though a header exists on the page for it. Where would the best information be for setting up an OS X11 installation which does’t use TonyMac? Should I just follow the instructions for a previous version of OS X and hope for the best? Am I better off giving my motherboard the priority or the OS version the priority when it comes to finding and choosing the instructions to follow since instructions don’t seem to exist for using both of them together? This OS X.11 El Capitan forum that I’m posting on now doesn’t have any info about my motherboard — http://www.insanelymac.com/forum/forum/503-osx86-1011-el-capitan/ … But the top pinned link on the forum seems to have important information but it doesn’t give enough background information for me to be able to make use of it.. http://www.insanelymac.com/forum/topic/306777-guide-usb-fix-el-capitan-1011/ .. But posts in other forums do exist which talk about my specific motherboard, including this post in Italian which explains how to install the previous OS X.10 on my motherboard.. https://translate.google.com/translate?hl=en&sl=it&tl=en&u=http%3A%2F%2Fwww.insanelymac.com%2Fforum%2Ftopic%2F306828-guida-installazione-mac-os-x-101x-clover-usb%2F .. Is the above Italian link the best one I can follow to install OS X.11 even though it is for OS X.10? In other words, where would be the best “InsanelyMac” introductory information be about creating a Hackintosh installer which uses Clover and not TonyMac for my motherboard? Thanks for your help!
  23. Hi folks, I see it as appropriate, when we talk here about the USB problems that arise when installing El Capitan on intel/AMD Hackintosh, or my approach to use Yosemite kext drivers to fix the USB problems. the first attempt V1, was for me the proof that it is the right way, the packet V2 has ultimately convinced me that it works. I do not need to patch any DSDT and all USB drives/ Ports operate as they have previously worked with Yosemite. see here: http://www.insanelymac.com/forum/files/file/521-usb-fix-for-el-capitan/?st=10#commentsStart
  24. Apple has taken a very long time and just the xnu source was finally released for El Capitan. So the source for OS X El Capitan released 7:00 +/- PM GMT https://opensource.apple.com/release/os-x-1011/
×