ahmed_ais Posted December 11, 2014 Share Posted December 11, 2014 Overview: This guide is intended to help Lenovo Y510p users to try OS X for educational purposes. You should buy Apple computer to be able to use Apple software legally in compliance with Apple's macOS EULA. It is very possible to install any OS X version from Yosemite (10.10.x) up to the most recent version Sierra (10.12.x). However, I only evaluate the most recent version on my system so I won't be able to support old versions. As some may have different partition layout or different hardware, it should be noted this is not a definite guide and you must adapt according to the situation you have For every step there might be other ways to do it better (or worse). The experts here in this forum may not agree with some of the steps mentioned here. This is what I had to do to get it working for my liking but comments and suggestions are very welcome indeed. This guide will always be incomplete (this is not a mac anyway) and I will refine it overtime time as needed The work introduced here is gathered and collected from many sources. My contribution is the least of all and I will try to give credit where it belongs as much as I remember. For any work I forgot to give credit I apologize for not remembering the source. Disclaimer: Although no one ever reported broken Y510p because of this guide, I still hold no responsibility for broken systems. Proceed at your own risk, read, read again, and ask before attempting something you are not OK with. Whoever is going to use part or all of this guide, please backup everything you are going to tinker with first. What Works and What Does notSimply put, almost everything works if the post-installation fixes are followed carefully. In summary:What Works Graphics with full acceleration QE/CI (using Intel GPU only) + HDMI Video Audio using AppleHDA HDMI Audio Ethernet (LAN) WiFi / Bluetooth (after replacing the Intel card (incompatible) with a compatible one like Broadcom BCM4352 for example Sleep (also sleep on Lid Close) Brightness Battery Keyboard / Touchpad CPU Power Management Web-Cam All USB ports Issues and What does not work Intel GPU / Restart issue: There is a problem related to graphics occurs when display goes off then on, like when system sleeps and wake or when changing display resolution for example, which results in no display on restart. These events requires re-initialization for the graphic driver but it seems the driver re-initialize incorrectly. As a result, the graphics related memory hold wrong data for some graphic registers which indirectly affects the restart functionality. Once the system is restarted in any of these scenarios, the POST (where Lenovo logo should appear) has no display and so is Clover and beyond if an OS is selected and booted using keyboard blindly. However, this is a graphic driver issue and has nothing to do with power or reboot function itself. Workarounds: If you did not trigger the graphic-restart issue (no display off/on switch) then use Restart function as you wish. If you triggered the graphic-restart issue then use Shutdown instead of Restart and Power on again. It is a good advice anyway not to hot-reboot between different OS's as some devices do not initialize properly. If you triggered the graphic-restart issue and used Restart already and stuck in a black screen, calm down and do not panic. Just know you are on Clover bootloader and control it using keyboard: If you were planning to boot OS X, blindly choose it using keyboard and hit Enter. Now press Ctrl+Shift+Eject to set the display to sleep then press any key and the display will return. [Eject key is mapped to Insert for VoodooPS2Controller.kext users] If you were planning to boot Windows, blindly choose it using keyboard and hit Enter and wait until Windows boots completely. Now press Fn+F1 to set Windows to sleep, then press any key to wake up the machine and display will be back on. VGA port: This will not work at all. A workaround when projecting to VGA display is to buy and use (male)HDMI-to-(female)VGA adapter. This adapter however have to be Active and NOT Passive to work. Wake on LID open: Currently is not working but I believe this one can be fixed. Nvidia GPU (built-in): This will have to be disabled as OS X does not support Optimus technology. Nvidia GPU (external/ultrabay, for those who have it): This will have to be removed before using OS X. It was possible to boot with this GPU and the built-in Nvidia GPU without Intel GPU like it is possible in Windows / Linux. However, there are issues prevents configuring those Nvidia GPUs correctly. There is a work started in this thread to try booting OS X with this graphics configuration but the work is in very early stage and seem halt as well as the interest of the community is quiet low for this regard. [sierra 10.12 ONLY] Keyboard Issues: This is not specific to Y510p but a general Sierra problem. Apple introduced a lot of changes for keyboard in the latest update 10.12 resulted in the following problems: Controlling volume and brightness using FN+Arrows is no longer functioning Caps-Lock is unreliable. I'm using SmartTouchpad kext and I find Caps-Lock works now by double pressing the key. I.e. double pressing Caps-Lock turn it on and another double press turn it off. Not sure if VoodooPS2Controller work the same now. Karabiner is not functioning anymore. The developer is aware and is currently developing the next generation of his software called Karabiner-Element. 1. Introduction This guide intends to help installing any version of OS X (starting from Yosemite) on Lenovo IdeaPad Y510p. There are many ways to install OS X on this machine but I will focus only on vanilla installation and only UEFI. So no myHack, no niresh, no iAtkos, no U-Beast, no what so ever with all respect to the developers behind these tools and distributions. Lenovo Y510P released with different configurations and is adjustable. My model have the built-in Hard Disk Drive (SSHD 1TB+8GB Cache SSD integrated) in addition to second Nvidia graphics card in the caddy. In Windows with the second Nvidia GPU present we see no trace of Intel card which means the first Nvidia (the built-in not the external) is apparently attached to the display in a configuration that OS X do not know so the only option for now is to skip both Nvidia GPUs altogether. Therefor, the external Nvidia GPU must be removed and the switchable Nvidia GPU (Optimus) should be disabled, to prevent other problems, either via BIOS or by DSDT/SSDT patches. There are many ways to dual boot Windows and OS X on Lenovo Y510p (and in general). In this guide I will stick with having Windows installed first in UEFI mode because this what any one would have initially once he buy this computer. At the beginning when I start writing this guide I only had the HDD and wrote that those who have SSD inside should not have any problem to adapt. Now that I have an SSD and booting off from it I will add it to the guide as well although nothing much would change. For those who think of doing like me (i.e. to get an SSD to put both Windows 8.1 and OS X and their apps on it and keep the HDD for data only), you first have to put the SSD in place of the HDD inside (to benefit from the connector speed). Normally you either don't have a place for the HDD or you are using a caddy but in all cases I suggest and advice to leave the HDD outside and work with the SSD only for now. Now you can proceed with the guide just as if installing on HDD with only one exception which is to fix TRIM after installation (explained later in the guide). Since Lenovo Y510P have Windows installed in UEFI mode, I will simply install OS X in EFI mode and use Clover EFI bootloader to be able to boot either OS since both would be installed in EFI. A problem that we might have for such type of configuration (both Windows and OS X in EFI on the same HDD) is that OS X needs bigger EFI partition than that created by Windows (assuming Windows is installed first). In this case, OS X installer will refuse to format the partition we prepared for OS X installation. We have to sort this problem out before trying to install OS X at all. This guide is split into several parts. First we create a space to install OS X in. Next we modify the size of EFI partition to remedy the mentioned problem. We then prepare a USB installer for OS X and use it to install. Finally we do some post-installation fixes to squeeze more juice from the system. Are you ready? Let's go ... 2. Preparing a Partition for OS X There are many ways to do this, the easiest is to use Disk Management in Windows to shrink the last partition and create a new one in the space. Any other partitioning tool can be used for that matter. My HDD was partitioned to have EFI partition, MS reserved partition, MS recovery partition, Windows partition, and Data partition. I used Disk Management in Windows to shrink a partition and free some space, then formatted that partition and labeled it “MacOSX”. The size of that partition is optional but I suggest to have it no less than 50GB to allow space for apps to be installed later on OS X. The label is optional too, we just need to keep record of that label so we don’t accidentally ruin any important partition later. Once we have the partition formatted (either fat32, exFat, or NTFS), we can proceed to the next step. 3. Increasing EFI Partition Size As I said above, there’s a problem when trying to format the created partition for OS X while trying to install it. OS X will fail to format the created partition (we labeled it “MacOSX”) as HFS+ because of small EFI partition size since OS X requires big ‘enough’ EFI partition. So before attempting to install OS X, we’ll have to increase the size of that partition. A default install of Windows 8.1 creates ~300MB Recovery partition, ~100MB EFI partition, and 128MB MSR (Microsoft Reserved) partition. This process (originally by RehabMan and slightly modified by me) removes the mentioned partitions and creates bigger EFI: Boot Windows installer USB (you should have one ready of course) Press Shift+F10 for recovery command line Type: diskpart Type: list disk (verify the disk number you want to work with, let's say it is 0) Type: select disk 0 Type: list part (you should see all partitions) Type: select part 2 (assuming part 2 is EFI part) Type: assign Type: list vol (to find out the drive letter assigned to EFI and Windows partitions, lets assume they were E: and C: respectively) press Shift+F10 for another command prompt Type: robocopy e:\efi c:\efi.bak /mir Switch back to original command prompt (the one running diskpart) Type: select part 1 Type: delete part override Type: select part 2 Type: delete part override Type: select part 3 Type: delete part override Type: create part efi size=528 (the space left by removing all three partitions Recovery, EFI, and MSR) Type: format quick fs=fat32 label="EFI" Type: assign Type: list vol (to find out new drive letter, assume it is F: ) Switch back to other command prompt window (the one just running cmd) Type: robocopy c:\efi.bak f:\EFI /mir Type: exit Switch to original command prompt (the one running diskpart) Type: exit Type: exit Hit: Alt+F4 at the Windows installer to quit Steps from 1 to 12 create backup of EFI partition contents so we can restore the contents after creating a bigger EFI and have Windows bootable. Then 13-18 it removes all three partitions Recovery, EFI, and MSR. Step 19 creates a new EFI partition with arbitrary size (put 528 which is the sum of previous EFI, Recovery, and MSR sizes). Step 20 format and label the new EFI partition, and finally step 24 restores EFI partition contents from the backup we created earlier. At this point, you should verify that Windows still boots and it should. 4. Preparing OS X USB Installer There are many guides on the web to do it, I will use virtual installation of OS X on windows to create the USB installer. If you have a working OS X somewhere else you could use that too. The USB should be no less than 8GB and you should have downloaded OSX Installer App from AppStore, ShowHiddenFiles app, Clover EFI bootloader, CloverConfigurator, HFSPlus.efi, FakeSMC.kext, and VoodooPS2Controller.kext / SmartTouchpad.kext. All these are available in Downloads section near the end of the thread. The following are the steps to create the USB installer: Plug the USB in and mount it in OS X. Open Disk Utility, select the USB from the list, click on Partition tab, choose 1 partition in Partition Layout, click options button, choose GUID Partition Table, and click Apply. You can format the created partition in the USB as Mac OS Extended and label it as “MacOSX Installer”. Selecting GUID scheme creates a hidden EFI partition on the USB so the USB actually contains 2 partitions with only 1 visible. Run ShowHiddenFiles app and click “Show Special Files” Go to Applications folder and right click the OS X Installer App > Show package Contents > Contents > SharedSupport > and mount InstallESD.dmg. This will mount a disk labeled “OS X Install ESD”. From the new window appeared, right click BaseSystem.dmg and choose Open. The image will be mounted as “OS X Base System”. Go back to Disk Utility and Restore the disk “OS X Base System” to our created USB partition “MacOSX Installer”. Close Disk Utility once it is done, we are not going to need it anymore. On the desktop there will be 2 disks with the label “OS X Base System”. One of them is mounted from BaseSystem.dmg and the other belongs to our USB which is the larger one. Rename the larger one to “MacOSX Installer”. Now open the disk labeled “OS X Install ESD” on desktop and copy both files BaseSystem.chunklist and BaseSystem.dmg to the root of “MacOSX Installer”. Also copy the folder “Packages” to “MacOSX Installer” > System > Installation after removing the link with the same name there. Finally, download and unzip the USB Installer EFI folder (link in downloads section) and put the resulting EFI folder in the USB EFI partition (you may need to use Terminal to mount it first). Now the USB installer is ready for prime time. 5. Installing OS X In this section we shall use the USB to install OS X but first make sure you have disable secured booting in BIOS. Power on the laptop and press F12 once Lenovo logo appears. Select the USB from the Boot menu that will appear. Clover will load in seconds, select “Boot from MacOSX Installer” and hit enter. In a minute or two the installer will be ready. Format the partition prepared earlier as “Mac OS Extended (Journaled)” and install OS X. The computer will restart after installation is finished. Boot again from the USB and this time select to boot from “MacOSX” entry. The installed OS X will run and you should have touchpad and keyboard working. Use them to finish the first time initialization and creating the account. Download CLOVER zip from Downloads section and unzip it into your HDD/SSD EFI partition (you may need to use Terminal to mount it first) Restart and boot from USB again, select “Clover Boot Options”, and choose “Add Clover boot options for all entries”. Restart without USB and Clover will boot off the EFI partition and you can boot straight into MacOSX. 6. Post InstallationOnce logged in, you will have a working system with full resolution 1920x1080 but with glitches and only 7MB (check Apple-Menu > About This Mac) which makes the experience awful. Also no Sound, no WiFi, no Brightness Control, no Battery Management, no Sleep, and more. Follow the steps below to fix most of the issues and have a better working system. Many of these steps will require DSDT/SSDT patching to get things working and unfortunately it is wrong for one to use patched tables of another one so an easy way to patch tables was needed. Our forum member intruder16 came out with a brilliant tool to automatically patch the tables for us which made the installation process very easy for a lot of users. As with everything, there will always be updates and new better ways to do things. Recently, there were some work initiated by the infamous Rehabman to revolutionize the DSDT/SSDT patching process in what is called SSDT-HACK. This method work by creating some patches through Clover's config.plist and using additional SSDT's to complement the native DSDT and SSDT's without touching them. This mean, using SSDT-HACK method allow us to share the same files without worry and no need to extract the native tables and patch them anymore. I have adapted this method and prepared the files to use which are already included in the CLOVER zip in the downloads section. So here's a summarization of what to do to fix everything: Have the CLOVER zip (attached in Downloads section) unzipped into EFI folder of your EFI partition. This will ensure you have the proper config.plist (including all kexts & acpi hot-patches among other important settings) in addition to the SSDT-HACK tables. Install all recent versions of the following kexts (links in Downloads section) in /S/L/E using EasyKext Utility: Get native Audio by fixing AppleHDA. Go to this page and follow the instructions. Done ! Note: The rest of this guide contain a lot of details about the post installation process for those who want to understand and learn. If you read on, you don't need to apply anything there as it will be already done and you may break things. Moreover, the some of the information given below might be outdated (newer patches are found or additional patches are needed). I was about to remove all that to keep the guide up-to-date but I thought to keep the whole thing FOR REFERENCE ONLY. 6.1 Graphics Apple hvae removed support for Intel Mobile HD4600 and to make it work we have to fake OS X to pretend it is another supported graphics card and this can be achieved in several ways. The most recent and clean method to use is OS-X-Fake-PCI-ID by RehabMan and I advice everyone to read about it in this topic and carefully apply the method. In brief, this is what should be done to fix the graphics and enable QE/CI: Download, decompress, and install FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext in /S/L/E. Add 9MB cursor framebuffer patch in Clover (as described in the linked topic) to fix few glitches that often appear when using ig-platform-id = 0x0a260006. Setting FakeID for IntelGFX of 0x04128086 either in Clover or by patching DSDT (as described in the linked topic). In addition, there are two additional things that should be covered here to fix some graphic glitches. 6.1.1 Fixing 16-bit colour (gradients)Normally, OS X will run in good colors after enabling QE/CI. However, it was found that anything sets the display off then on results in dirty graphics that have color gradients as described in this topic. To fix the 16-bit colour gradient issue, our forum member vusun123 suggested using a custom EDID (google EDID if you don't know what it is) and his suggestion worked brilliantly. <key>Graphics</key> <dict> <key>InjectEDID</key> <true/> <key>CustomEDID</key> <data> AP///////wAw5BYEAAAAAAAXAQSQIxN4ChXVnllQmCYOUFQAAAABAQEBAQEB AQEBAQEBAQEBGjaAoHA4H0AwIDUAWcIQAAAZAAAAAAAAAAAAAAAAAAAAAAAA AAAA/gBMRyBEaXNwbGF5CiAgAAAA/gBMUDE1NldGMS1UTEMyAGw= </data> .. .. .. .. .. </dict> Note: The config.plist in the linked CLOVER zip contain that custom EDID already for you so nothing more to do. 6.1.2 Fixing OS X boot graphic glitchThe following patch for IOGraphicsFamily.kext is required to fix a graphics glitch on second boot screen for Yosemite (10.10.2+) : <dict> <key>Comment</key> <string>Boot graphics glitch, 10.10.2+</string> <key>Find</key> <data> QYjE6xE= </data> <key>Name</key> <string>IOGraphicsFamily</string> <key>Replace</key> <data> QYjE6zE= </data> </dict> This one is for El Capitan 10.11.x: <dict> <key>Comment</key> <string>Boot graphics glitch, 10.11</string> <key>Find</key> <data> AQAAdRc= </data> <key>Name</key> <string>IOGraphicsFamily</string> <key>Replace</key> <data> AQAAdBc= </data> </dict> This is for Sierra 10.12.x: <dict> <key>Comment</key> <string>Boot graphics glitch, 10.12.x</string> <key>Find</key> <data> AQAAdSU= </data> <key>Name</key> <string>IOGraphicsFamily</string> <key>Replace</key> <data> AQAA6yU= </data> </dict> Note: There will still be a glitch in the transition between first and second boot stages which there is no fix for it at the moment. The only improvement that can be made is to enable Legacy Support in BIOS which will replace the transition glitch with black screen. Beware that enabling Legacy Support will trigger incorrectly initialization to graphic driver for OS X which will result in no display upon rebooting from OS X. 6.2 Audio 6.2.1 Enabling native AppleHDAThere are two methods to fix audio in OS X. The first is to use VoodooHDA which is a generic audio driver that support wider range of sound chips out of the box (acceptable with issues). The second method is to patch AppleHDA.kext for our audio chip to have native sound (better and clearer) which is a complicated process. Now that we have AppleHDA working perfectly, the guide will only offer using AppleHDA.Getting AppleHDA.kext patched to work correctly for our Y510p indeed toke much time reading guides and trying things. I have to give Mirone the credit he deserve for his awesome guide and the patched kext he provided that enabled most of the audio features but not external mic support. Our forum member intruder16 did his best and succeeded to get this the right way. Basically what have to be done is: Patching the binary of AppleHDA to support our audio chip (either in place or in Clover's config.plist) Adding the correct audio codecs to AppleHDA either directly or by using a helper kext to have all audio functions Making a change in DSDT or in Clover's config.plist to use the proper audio layout There is also an additional kext to install to help restoring audio after sleep/wake For those who want to learn (I recommend all to learn because this is why we are all here), you can find some good information in this post. Otherwise, head over Y510p-OSX-AppleHDA and use that script to create and install the helper kext. You will also find instructions on how to properly configure Clover so the audio solution is complete. From now on, these information will not be available in this guide to keep everything organized.6.2.2 Fixing HDMI & HDMI AudioConnecting the laptop to an external display through HDMI means the display will be responsible for audio output instead of the laptop audio system. This feature is broken on many hackintoshes (ours included) and here you will find the procedure to fix it: Make sure AppleHDA is working Patch the DSDT/SSDT that have the device at address 0x00030000 to rename it from B0D3 to HDAU. (The patch is included in Auto-Patcher so skip this step) Put FakePCIID_Intel_HDMI_Audio.kext in Clover's kexts folder (optionally can be installed in /S/L/E) Patch AppleIntelFramebufferAzul.kext for HDMI-audio in Clover's config.plist (there are other patches for other configurations if this one did not work for you) <dict> <key>Comment</key> <string>HDMI-audio, port 0105, 0x0a260005 0x0a260006, 0x0d220003, 0x0a2e000a, 0x0a26000a</string> <key>Find</key> <data> AQUJAAAEAACHAAAA </data> <key>Name</key> <string>AppleIntelFramebufferAzul</string> <key>Replace</key> <data> AQUJAAAIAACHAAAA </data> </dict> Set this option in clover's config.plist: <key>Devices</key> <dict> .... <key>UseIntelHDMI</key> <true/> </dict> Clear cache and reboot Now when you connect the laptop to an external display through HDMI you will find new entry in System Preferences > Sound > Output for HDMI which means sound is now controlled by the external display. HDMI Issues and workarounds: If HDMI display is connected after OS X is booted (hot plug), the display will be distorted on the built-in display. This may need a new patch for AppleIntelFramebufferAzul.kext to get fixed but a workaround is to use the external display to change the built-in display resolution to anything then back to 1920x1080 again. If HDMI display is turned off (or display mode is switched from HDMI) while OS X is running, OS X will freeze for second every few seconds. Turning the external display on (or switching to HDMI mode) again, or disconnecting the HDMI cable will fix the freezing and everything will be normal. 6.3 Ethernet (LAN) To fix Ethernet we can utilize the solution by Mieze by first downloading the driver AtherosE2200Ethernet.kext (link in downloads section) then following the steps from his topic: Goto /S/L/E and delete ALXEthernet.kext. (If you don't have this it is OK) Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface. 6.4 Wi-Fi The built-in WiFi card in Lenovo Y510P won’t work with OS X and I had to replace mine with Broadcom BCM4352 AC WLAN BT4.0 Wi-Fi card that is compatible with Y510P and OS X. For this card to work, OS X needs to see this card as one of those defined in AirPortBrcm4360.kext (inside IO80211Family.kext). Also, the same kext have to be patched to enable 5GHz.PS: if you have other chip than mine or the given patch didn't work for you, I advice you to visit Toleda's topic to find all the up-to-date information.6.4.1 Broadcom Airport ExtremeInstall FakePCIID_Broadcom_WiFi.kext in in /S/L/E.6.4.2 Enable AC (5GHz)There are 3 different Clover patches to try depending on the WiFi chip country. For me, the required patch is: <dict> <key>Comment</key> <string>10.10-BCM94352-5GHz-US-FCC-dv</string> <key>Find</key> <data> QYP8/3QsSA== </data> <key>Name</key> <string>AirPortBrcm4360</string> <key>Replace</key> <data> ZscGVVPrKw== </data> </dict> After putting the patch in config.plist, nothing more is needed but a reboot. 6.5 Bluetooth In order to use BCM4352 Bluetooth with OS X, we will use BrcmPatchRAM to activate it. Head over Rehabman's fork of BrcmPatchRAM (link in download section) and read how to install it. Basically, you will need to download BrcmPatchRAM and install two kexts from the archive depending on OS X version and install location. For Yosemite 10.10.x: install both BrcmPatchRAM.kext and BrcmFirmwareRepo.kext in /S/L/E For El Capitan 10.11 and Sierra 10.12.x: install both BrcmPatchRAM2.kext and BrcmFirmwareRepo.kext in /S/L/E Ignore the rest of the kexts in the archive. 6.6 Proper CPU Power Management This is important as it affects many aspects of the system specially sleep. To get proper CPUPM, either download and use the latest version of ssdtPRGen.sh to produce CPUPM SSDT.aml (Secondary System Description Table), or, use the one generated by AutoPatcher. Either way, put the resulting SSDT.aml into EFI/Clover/ACPI/patched among other patched tables. 6.7 Sleep At this moment the system might not sleep for many reasons like problems with USB, Network interrupting sleep, and not having AppleLPC.kext loaded on startup. If you are going to use AutoPatcher (recommended) then it will do everything for you and you can skip the rest of this section. If you will go manually and still reading, I’ll try to cover all the requirements for perfect sleep but this will involve DSDT patches so you should be familiar with the process. You have to know how to use MaciASL, extract native ACPI tables (from Clover), disassemble tables using iasl, and fix common problems while patching.The Laptop Patch Repository by Rehabman is a must have with MaciASL. Add it and it won’t harm to add his Debugging Patch Repository too.6.7.1 AppleLPC.kext is not loadingThis kext is essential for sleeping. To test if it is loaded or not fire off Terminal and issue the command kextstat then look for com.apple.driver.AppleLPC in the output. If it is there then the kext is loaded and nothing to do in this section. If not, make sure you used Auto-Patcher correctly to patch your DSDT then reboot and use kextstat again to confirm AppleLPC.kext is loaded fine.6.7.2 Fix EHC1/EHC2 Kernel AssertionsYou can test if there are problems prevents sleep using the command pmset -g assertions. If you got anything with EHC1 or EHC2 then it probably USB related problem and you need to make sure you used Auto-Patcher correctly to patch your DSDT.6.7.3 Workaround for EHC1/EHC2/XHC Instant-WakeIf you got OS X to sleep but found it to wake immediately then look for wake reason in system.log using Console app. If the reason is found related to either EHC1, EHC2, or XHC then the easy workaround is to delete/comment the code related to powering on/off to these devices from DSDT which is the name _PRW for each of them. (Auto-Patcher already do this for you)6.7.3 Sleep on LID closeOut of the box LID open/close is not functioning. A workaround is available in Rehabman's laptop patch repository and also in AutoPatcher that remove _PRW for LID but this method completely break the functionality of Wake on LID open. Since Wake on LID open is not working at the moment either way, this workaround is all what we have now. 6.8 Brightness Getting brightness to work perfectly is a two step process that I’ll cover in order of importance:6.8.1 Patching DSDT or SSDTSkip this if you have used Auto-Patcher OR PREFERABLY USED THE NEW SSDT-HACK. Either DSDT or one of the SSDTs (whichever contains IGPU definition) have to be patched with "Brightness fix (Haswel)" from Rehabman's Laptop Repository. Doing this correctly will result in having the brightness slider visible in System Preferences > Displays.6.8.2 [Deprecated] ACPIBacklight.kext6.8.2 IntelBacklight.kextThis is a must have kext that gets the job done assuming DSDT/SSDT is already patched. With this kext the brightness slider will function normally. 6.9 Battery Management This one is important but easy to fix, just download the latest version of “ACPIBatteryManager.kext” and put it in Clover’s kexts folder, reboot. 6.10 Keyboard and Touchpad In this section I will cover how to activate the keyboard and touchpad. Moreover, I will show how to control brightness using Fn+Up and Fn+Down.6.10.1 Activating Keyboard and TouchpadThere are two variants of Ideapad Y510p with regards to Touchpad so each variant will require different Kext to enable PS2Controller: The first one with Synaptics touchpad and basically VoodooPS2Controller kext by RehabMan is great and reliable. In addition, EMlyDinEsH updated his SmartTouchpad kext so now it works very nice with Synaptics Clickpad available on Y510p with more features and it is worth checking out (both links in downloads) The other one with Elantech touchpad and the driver by EMlyDinEsH is the only option which is great anyway for this hardware (link in downloads) 6.10.2 Controlling brightness using Fn+Up and Fn+Down [bROKEN FOR SIERRA 10.12]At the moment, you can control the brightness using the slider in System Preferences > Display. To get the default key combination for Y510P working we cannot use Karabiner or OS X shortcuts as the events are buried deep down. Therefore, the DSDT have to be patched and ACPIKeyboard kext by RehabMan may be required in addition. (link in Downloads) If you are using the SSDT-HACK method, make sure to ONLY use the relevant table in EFI/CLOVER/ACPI/patched folder. I.e., VoodooPS2Controller users should put SSDT-HACK-VoodooPS2.aml and SmartTouchpad users should put SSDT-HACK-SmartTouchpad.aml instead. YOU DON'T NEED TO EDIT config.plist FOR THAT. If you are still using Auto-Patcher to patch tables: If you have Synaptics touchpad and are using VoodooPS2Controller then choose VoodooPS2Controller when prompted by the Auto-Patcher script. You don't need ACPIKeyboard kext in this case as the needed functionality is built into VoodooPS2Controller already. If you have Synaptics or ELAN touchpad and are using SmartTouchpad kext by EMlyDinEsH then choose SmartTouchpad when prompted by the Auto-Patcher script. In this case, however, you will need ACPIKeyboard kext as the needed functionality is not built into SmartTouchpad. 6.11 Enabling SSD TRIM For those who are using SSD the OS should support TRIM which is a technology to removes any deleted file completely to enhance SSD performance and increase its lifespan. It is said that newer SSD have their own built-in technology to do this without any effort from the OS but not-so-new SSD's does not have this. To get OS X Yosemite to offer TRIM support to our SSD, we have to put this patch in Clover's config.plist:And reboot the system. 6.12 USB 3.0 [Yosemite] Both USB 3.0 ports will work OOB but may not power on again after wake from sleep (at least with 10.10). To fix this issue, we will patch AppleUSBXHCI, the native usb driver, with just one patch through clover: <dict> <key>Comment</key> <string>Enable USB3 after wake for Intel 8 series chipset</string> <key>Find</key> <data> xoDIAAAAAQ== </data> <key>Name</key> <string>AppleUSBXHCI</string> <key>Replace</key> <data> xoDIAAAAAA== </data> </dict> Links & Downloads This section contains all links to all the downloads required to get the best installation for Lenovo Y510p so far. ShowHiddenFiles app: Link Clover EFI bootloader: Link CloverConfigurator: Link HFSPlus.efi: Link RehabMan / FakeSMC: Link RehabMan / OS-X-ACPI-Backlight: Link RehabMan / OS-X-Intel-Backlight: Link RehabMan / OS-X-ACPI-Battery-Driver: Link RehabMan / BrcmPatchRAM: Link RehabMan / OS-X-Fake-PCI-ID: Link RehabMan / OS-X-EAPD-Codec-Commander: Link RehabMan / VoodooPS2Controller: Link EMlyDinEsH / SmartTouchPad: Link (register in the forum and download attachment on first post) RehabMan / OS-X-ACPI-Keyboard: Link Ahmed_ais / Y510p-OSX-AppleHDA: Link Mieze / AtherosE2200Ethernet: Link USB Installer EFI folder: Yosemite 10.10: Link El Capitan 10.11: Link Sierra 10.12: Link [i believe this one should work for 10.10 and 10.11 as well] [Link is updated 3/10/2016] Installed System Clover (Whole folder). This have almost everything needed for 10.10, 10.11,10.12. It lacks SMBIOS serial number. Choose any of the SSDTs provided depending on the keyboard&touchpad kext you use and put that SSDT into patched folder. [NOTE: due to the keyboard problem for Sierra, it won't matter which SSDT table you choose as keyboard shortcuts for volume and brightness will be broken anyway, until a fix is up]Clover_FULL_EFI_10.10-10.12_SSDT-HACK: Link Modified CloverEFI theme ios7: Link Need HELP?? Make sure you have CAREFULLY READ the entire guide. I have the same laptop as yours (mostly) so it is unexpected to have unique issue unless you have a faulty machine. Search the topic (and the web in general) for the things you have questions about before asking. The answer for your question may be few posts away so save your time and other's. If you still want to ask for help, you are welcome but you have to know that no one here have super powers to sense the problems without details. Some problems are well-known and small amount of evidence is enough for diagnosing them but many problems are not. Therefore, in general, this is my advice whenever you try to report a problem or ask for help: Introduce the problem in clear words Provide as much information as you can in form of logs, screenshots and/or dumps State whether the issue is reproducible and list some of the ways to reproduce it. State the things you have tried and the results you found CreditsSfairat, Mirone, intruder16, useletters, Rehabman, Mieze, vusun123, EMlyDinEsH, many more ....Change Log 26/9/2016 Added support for macOS Sierra 10.12 Included SSDT-HACK method and files in a step to make it mainstream to remove the manual/automatic ACPI tables patching in future Refined the guide so the most relevant information are on top. Other details are left for READING but might be removed in future Replaced OS-X-ACPI-Backlight with OS-X-Intel-Backlight which needs a small PNLF patch rather than the big and clumsy patch needed for OS-X-ACPI-Backlight. It is also designed to overcome changes made be Apple and is more supported now. 27/2/2016Added a workaround to use external VGA-only display/projector. 26/12/2015 Removed the modified version of Auto-Patcher as the author has his git up-to-date Some clean-ups 18/11/2015 Modified version of Auto-Patcher is added to Downloads section (until its author update his git) Added EFI folder for USB installer (both 10.10 and 10.11) in Downloads section More things have been removed/edited to update information 14/10/2015 Guide updated to support El Capitan Many things have been removed/edited to update information 07/07/2015 Added a section "Before Asking for HELP" to get the best out of this topic. Modified SMBIOS options after installing OS X to reflect the current situation. Updated Second boot stage glitch patch according to that topic. Updated the section "Enabling Keyboard and Touchpad" to include SmartTouchpad kext by EMlyDinEsH. Updated the section "Getting Fn+Up and Fn+Down to Control Brightness" to include instructions for SmartTouchpad kext users. 05/06/2015 Updated Graphics fix section to include 16-bit colour gradients issue that happen whenever the display is turned off then on. Updated What works and What doesn't section to represent the current situation of graphics-related problems. Updated config.plist to include the custom EDID for fixing the 16-bit colour gradients issue. 18/04/2015 Updated config.plist to include SortedOrder for SSDT's & other small edits. (The SortedOrder matches my SSDT's names, make sure to edit them to match yours) Removed my previously linked DSDT and SSDT's 12/04/2015 Added section for sleep on LID close Corrected the current issues section to exclude sleep on LID close. 11/04/2015 Removed the details on Enabling AppleHDA (and previous download links) and linked instead to intruder16's work (both description post and download page) Abstracted graphics fix details as they are better maintained in the original topic by the-darkvoid which is linked 10/04/2015 Added What's working and What's does not section Some cleanups and rearrangements 07/04/2015 Replaced FakeSMC.kext with Rehabman's version which includes a fix for the powerd[27]: Failed to read current rating(0xe00002f0) issue. Removed both Audio fixes VooodooHDA and non-update-safe patched AppleHDA, only the update-safe AppleHDA patch remains. Removed VoodooHDA and Patched AppleHDA.kext Links from downloads section. Removed boot glitch fix for Yosemite versions before 10.10.2, most of us are on latest version anyway. Removed nv_disable=1 boot-arg, not needed with Nvidia cards are disabled by other means. Removed -gux_defer_usb2 boot-arg, not needed while GenericUSBXHCI USB 3.0 Driver is not in use. Replaced manual BCM4352 patches with Fake-PCI-ID method + Clover patch (still not update safe). Modified SMBIOS setting for Installation section. Added section to fix Ethernet (LAN). Removed Fixing Home and End Keys using KeyBindings, not needed anymore I guess. Added BrcmPatchRAM method to bluetooth fix section and downloads 05/04/2015 Added a section for enabling the keyboard and touchpad for both Synaptics and Elan variants and the corresponding links in download section. Added a paragraph for using SSD instead of HDD in Introduction for those who have (or plan to get) one Added a section to enable TRIM support in Yosemite for SSD Added a section to fix USB 3.0 28/03/2015 Updated the patched ACPI files to include the missing CPUPM SSDT which was accidentally replaced by another useless SSDT. Updated Wrapping Up section to highlight the current state of the setup. Removed the Appendix, useless anyway. 17/03/2015 Removed all DSDT/SSDT patches from the guide in favour of Auto-Patcher by intruder16 Updated the already patched ACPI files (some useless tables are removed, and one table is included to allow Optimus disable) 27/02/2015 Updated section 6.2 Sound by adding update-safe method for a working AppleHDA Updated section 6.2 Sound by adding HDMI Audio fix Major clean up 25/02/2015 Updated section 6.2 Sound by adding sound fix using AppleHDA.kext. Added the patched AppleHDA.kext to Downloads section. Gave credit to who deserve it 19/02/2015Regenerated CPUPM SSDT using the latest ssdtPRGen.sh script to achieve better power management and updated Downloads section. 16/02/2015 Updated Clover 0x0a260006 9MB cursor bytes patch in section 6.1 Graphics to the latest. Removed Clover r2999 recommendation as I gave latest release r3168 a try and it seems working normally (thought not as straight forward as r2999). 10/02/2015Revamped the Keyboard section 6.9 to include system shortcuts and detailed information about Karabiner 08/02/2015Added a modified version of Clover EFI theme ios7 originally created by forum members Ukr55 and Winlog 03/02/2015Added more stuff in Downloads section. Now DSDT, SSDT's, config.plist, patched kexts, and extra kexts are all up! 01/02/2015 Edited section "6.1 Graphics" to added IOGraphicsFamily 10.10.2 patches to fix Boot graphics glitch in addition to those for 10.10.0 and 10.10.1. A lot of cleaning. 30/01/2015 Fixed 5GHz Wi-Fi patch for BCM4352 with 10.10.2. Few cleaning. 10/01/2015: Added the new Fake-PCI-ID to by Rehabman to "Downloads" section. Edited section "6.1 Graphics" section to replace old graphics patching methods (manual and clover) with the new one using OS-X-Fake-PCI-ID. Removed unnecessary HDMI Clover patch since it is achievable using FakePCIID_Intel_HDMI_Audio.kext from OS-X-Fake-PCI-ID. Few cleaning. 09/01/2015: Added a "Downloads" section contains links to all required kexts, additional .efi files, auxiliary apps. I will later update it with links to patched kexts, patched DSDT and SSDT, and Clover's config.plist. Edited section "4. Preparing OS X Yosemite USB Installer" to remove OsxAptioFix2Drv-64 from Drivers64UEFI selection while installing Clover (since v2999 does not have that option) and also to remove downloads from there. Edited section "5. Installing OS X Yosemite" to set SMBIOS in installation's Clover to iMac14,2. This fixes Firefox's issue with Flash player (I don't know why). Fixed custom keyboard issue in section "7. Wrapping up" by using the software properly. 30/12/2014:Edited section "6.1 Graphics" section to remove not required patch for AppleIntelFramebufferAzul.kext and rearrange the procedure. 11/12/2014:Initial version 15 2 Link to comment Share on other sites More sharing options...
soiggeli Posted December 30, 2014 Share Posted December 30, 2014 (edited) I was wondering am i using plist editor correctly when adding those patches ( http://www.macupdate...3/plistedit-pro ) EFI > Clover > config.plist > Opened with plisteditor pro > KernelAndKextPatches > KextsToPatch > "Then i just made new child (Class String) and then i copy pasted to "value" this patch <dict> <key>Comment</key> <string>QECI HD4600</string> <key>Find</key> <data> PYaAEgR0EOtd </data> <key>Name</key> <string>AppleIntelHD5000Graphics</string> <key>Replace</key> <data> PYaAFgR0EOtd </data> </dict> Edited May 18, 2016 by Allan Code box added Link to comment Share on other sites More sharing options...
ahmed_ais Posted December 30, 2014 Author Share Posted December 30, 2014 Save yourself the hassle skip the top part of PlistEdit Pro, just edit the file code directly from the lower part: Make sure to put the code block in its place without breaking any tag. 1 Link to comment Share on other sites More sharing options...
artas182x Posted January 1, 2015 Share Posted January 1, 2015 I followed all steps in this guide, but i have strange problem. When i select OS X installer in Clover menu i get black screen. No verbose output (enabled of course), just black screen. Led on USB Flash isn't blinking, so it doesn't load anything. Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 1, 2015 Author Share Posted January 1, 2015 I followed all steps in this guide, but i have strange problem. When i select OS X installer in Clover menu i get black screen. No verbose output (enabled of course), just black screen. Led on USB Flash isn't blinking, so it doesn't load anything. Post your config.plist Link to comment Share on other sites More sharing options...
artas182x Posted January 2, 2015 Share Posted January 2, 2015 Post your config.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <false/> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <true/> <key>AddHDMI_8000000</key> <true/> <key>AddPNLF_1000000</key> <true/> <key>DeleteUnused_400000</key> <true/> <key>FIX_ACST_4000000</key> <true/> <key>FIX_ADP1_800000</key> <true/> <key>FIX_RTC_20000</key> <true/> <key>FIX_S3D_2000000</key> <true/> <key>FixAirport_4000</key> <true/> <key>FixDarwin_0002</key> <true/> <key>FixDisplay_0100</key> <true/> <key>FixFirewire_0800</key> <true/> <key>FixHDA_8000</key> <true/> <key>FixHPET_0010</key> <true/> <key>FixIPIC_0040</key> <true/> <key>FixLAN_2000</key> <true/> <key>FixRegions_10000000</key> <true/> <key>FixSBUS_0080</key> <true/> <key>FixShutdown_0004</key> <true/> <key>FixUSB_1000</key> <true/> <key>NewWay_80000000</key> <true/> </dict> <key>Name</key> <string>DSDT.aml</string> <key>ReuseFFFF</key> <false/> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>CpuPm</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>Cpu0Ist</string> </dict> </array> <key>HaltEnabler</key> <true/> <key>SSDT</key> <dict> <key>DropOem</key> <false/> <key>Generate</key> <dict> <key>CStates</key> <true/> <key>PStates</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>-v slide=0 dart=0 darkwake=0 kext-dev-mode=1</string> <key>DefaultLoader</key> <string>boot.efi</string> <key>Legacy</key> <string>PBR</string> <key>Log</key> <false/> <key>Secure</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <false/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>ResetHDA</key> <true/> </dict> <key>FakeID</key> <dict> <key>IntelGFX</key> <string>0x0</string> </dict> <key>USB</key> <dict> <key>AddClockID</key> <true/> <key>FixOwnership</key> <true/> <key>Inject</key> <true/> </dict> </dict> <key>GUI</key> <dict> <key>Mouse</key> <dict> <key>Enabled</key> <false/> <key>Mirror</key> <false/> </dict> <key>Scan</key> <true/> <key>ScreenResolution</key> <string>1280x1024</string> <key>Theme</key> <string>bootcamp</string> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <true/> <key>NVidia</key> <false/> </dict> <key>InjectEDID</key> <true/> <key>ig-platform-id</key> <string>0x0a260006</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> </dict> <key>RtVariables</key> <dict> <key>MLB</key> <string>C02032109R5DC771H</string> <key>ROM</key> <string>UseMacAddr0</string> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>10/29/13</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>MBP111.88Z.0138.B03.1310291227</string> <key>Board-ID</key> <string>Mac-189A3D4F975D5FFC</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardType</key> <integer>10</integer> <key>ChassisAssetTag</key> <string>MacBook-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>08</string> <key>Family</key> <string>MacBook Pro</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <true/> <key>ProductName</key> <string>MacBookPro11,1</string> <key>SerialNumber</key> <string>C02L34Q7FGYY</string> <key>Trust</key> <false/> <key>Version</key> <string>1.0</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Detect</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> EDIT: Never mind. Now it boots on Nvidia card using this config: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Boot</key> <dict> <key>Arguments</key> <string>-v slide=0 dart=0 darkwake=0 kext-dev-mode=1 -x nv_disable=1</string> </dict> <key>Devices</key> <dict> <key>FakeID</key> <dict> <key>IntelGFX</key> <string>0x0</string> </dict> </dict> <key>GUI</key> <dict> <key>Mouse</key> <dict> <key>Enabled</key> <false/> <key>Mirror</key> <false/> </dict> <key>ScreenResolution</key> <string>1920x1080</string> <key>Theme</key> <string>bootcamp</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>10/29/13</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>MBP111.88Z.0138.B03.1310291227</string> <key>Board-ID</key> <string>Mac-189A3D4F975D5FFC</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardType</key> <integer>10</integer> <key>ChassisAssetTag</key> <string>MacBook-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>08</string> <key>Family</key> <string>MacBook Pro</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <true/> <key>ProductName</key> <string>MacBookPro11,1</string> <key>SerialNumber</key> <string>C02L34Q7FGYY</string> <key>Trust</key> <false/> <key>Version</key> <string>1.0</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <true/> </dict> </dict> </plist> Here are also some drivers for Nvidia cards. Nvidia has recently released aternate drivers, maybe it will work with 750m/755m SLI. http://www.hackintoshosx.com/files/file/4268-nvidia-webdrivers-installer-nvda4all-for-yosemite-10100/ http://www.nvidia.com/download/driverResults.aspx/81212/en-us Also for ASUS ROG notebooks (with 765m or 770m card) there is DSDT patch. These notebook has disabled Intel card. https://github.com/Arise/Asus-G750-Series-DSDT-Patches/blob/master/patches/graphics/GFX0-765m.txt Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 2, 2015 Author Share Posted January 2, 2015 I would first try these: Remove the key (ACPI>DSDT>Fixes) with its <dict> ... </dict> Remove the key (ACPI>DSDT>DropTables) with its <array> ... </array> Remove the key (ACPI>DSDT>HaltEnabler) with its <true/> value Also set CStates and PStates to <false/> for now. Link to comment Share on other sites More sharing options...
artas182x Posted January 2, 2015 Share Posted January 2, 2015 I would first try these: Remove the key (ACPI>DSDT>Fixes) with its <dict> ... </dict> Remove the key (ACPI>DSDT>DropTables) with its <array> ... </array> Remove the key (ACPI>DSDT>HaltEnabler) with its <true/> value Also set CStates and PStates to <false/> for now. Clover adds its own stuff which breaks booting. Now i'm thinking of bringing up 750m/755m card on SLI configurations. Now system boots only with disabled Nvidia kexts. Now they released their own drivers for Mac (my previous post). Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 2, 2015 Author Share Posted January 2, 2015 Clover adds its own stuff which breaks booting.Which is not holly and can be customized to allow better boot. Actually, this is one of Clover's advantages. When I said try removing them, that's because you do not need them as I did not. Now i'm thinking of bringing up 750m/755m card on SLI configurations. Now system boots only with disabled Nvidia kexts. Now they released their own drivers for Mac (my previous post).I would not be so optimistic but I will look into these links. As the current status of our notebook, you should be able to boot wheather disabled discrete nvidia card in bios or not without messing with any kext. The extra card have to be removed until any proven progress is made for this regard. Link to comment Share on other sites More sharing options...
soiggeli Posted January 3, 2015 Share Posted January 3, 2015 I followed all steps in this guide, but i have strange problem. When i select OS X installer in Clover menu i get black screen. No verbose output (enabled of course), just black screen. Led on USB Flash isn't blinking, so it doesn't load anything. I have the same problem! I would first try these: Remove the key (ACPI>DSDT>Fixes) with its <dict> ... </dict> Remove the key (ACPI>DSDT>DropTables) with its <array> ... </array> Remove the key (ACPI>DSDT>HaltEnabler) with its <true/> value Also set CStates and PStates to <false/> for now. I did not notice any difference even if I removed those things from .plist ( Sometimes i see apple logo and then computer restarts) Btw here is my .plist http://textuploader.com/65y1 Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 3, 2015 Author Share Posted January 3, 2015 I have the same problem! I did not notice any difference even if I removed those things from .plist ( Sometimes i see apple logo and then computer restarts) Btw here is my .plist http://textuploader.com/65y1 I see you are using a very recent build of Clover that I have not had much luck with. Try build 2999 (or around it) instead and give feedback here again. Edit: your config.plist is really a mess. You are adding too many DSDT patches and injecting both Intel and ATI? Why would you inject ATI anyway? Also adding a patch for Nvidia in DSDT patches (which are too many by the way)? Where did you get this config from? Link to comment Share on other sites More sharing options...
soiggeli Posted January 3, 2015 Share Posted January 3, 2015 Well now i used Clover build 2999. Now im getting OsxAptioFixDrv starting ovverides for System/Library/Coreservices/boot.efi Using relec block: yes ,hiberate wake: no Efi boot loaded from acpl(XXXXXXXXXXXXXXXXXXXXXX something) boot file path System/Library/Coreservices/boot.efi .Using safe mode ************************************* Root device .................... **************************************** http://txt.do/6537 Im so confusef atm.. Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 3, 2015 Author Share Posted January 3, 2015 Well now i used Clover build 2999. Now im getting OsxAptioFixDrv starting ovverides for System/Library/Coreservices/boot.efi Using relec block: yes ,hiberate wake: no Efi boot loaded from acpl(XXXXXXXXXXXXXXXXXXXXXX something) boot file path System/Library/Coreservices/boot.efi .Using safe mode ************************************* Root device .................... **************************************** http://txt.do/6537 Im so confusef atm.. The config.plist looks fine to me. Would you list the items you have in EFI/CLOVER/drivers64UEFI? Link to comment Share on other sites More sharing options...
soiggeli Posted January 3, 2015 Share Posted January 3, 2015 The config.plist looks fine to me. Would you list the items you have in EFI/CLOVER/drivers64UEFI? EmuVariableUefi-64 , FSInject-64 , HFSPlus-64 , OsxAptioFix2Drv-64 , OsxAptioFixDrv-64 , OsxFatBinaryDrv-64 , PartitionDxe-64 Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 3, 2015 Author Share Posted January 3, 2015 EmuVariableUefi-64 , FSInject-64 , HFSPlus-64 , OsxAptioFix2Drv-64 , OsxAptioFixDrv-64 , OsxFatBinaryDrv-64 , PartitionDxe-64 Okay try the attached HFSPlus.efi instead of HFSPlus-64.efi you have, I think this is where your issue is. PS: though not related to the issue, you could safely remove OsxAptioFix2Drv-64 it is not needed. HFSPlus.zip Link to comment Share on other sites More sharing options...
artas182x Posted January 3, 2015 Share Posted January 3, 2015 I installed OS X succesfully using your guide. I found out how to enable AppleHDA. You need to apply these patches to DSDT: "Audio Layout 12" (change layout-id from 12 to 3) and "IRQ Fix". Then repleace AppleHDA.kext with this: http://www.mediafire.com/download/dj73zt2e1qkmm21/AppleHDA.kext.zip. Using Kext Wizard repair permissions and rebuild cache. If you have Voodoo kext remove it. This method is tested on Yosemite 10.10.1. Something about Intel HD - I also applied GFX0 to IGPU patch to DSDT- my battery life is very good now. By the way there is graphic glitch on menu bar, but when i log off and log on again everything is OK. 1 Link to comment Share on other sites More sharing options...
soiggeli Posted January 3, 2015 Share Posted January 3, 2015 Okay try the attached HFSPlus.efi instead of HFSPlus-64.efi you have, I think this is where your issue is. PS: though not related to the issue, you could safely remove OsxAptioFix2Drv-64 it is not needed. Im still in same situation.. i deleted those files but did not work for me. I tried many times to boot from my usb.. and 1time i got kernel error or something ? Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 4, 2015 Author Share Posted January 4, 2015 I installed OS X succesfully using your guide. I found out how to enable AppleHDA. You need to apply these patches to DSDT: "Audio Layout 12" (change layout-id from 12 to 3) and "IRQ Fix". Then repleace AppleHDA.kext with this: http://www.mediafire.com/download/dj73zt2e1qkmm21/AppleHDA.kext.zip. Using Kext Wizard repair permissions and rebuild cache. If you have Voodoo kext remove it. This method is tested on Yosemite 10.10.1. I'm glad the guide helped. Regarding AppleHDA, I wanted to try getting it to work sometime ago but I had VoodooHDA working fine for my needs. It would be better of course to ditch VoodooHDA for a perfectly working AppleHDA and I'll try your suggestion. Something about Intel HD - I also applied GFX0 to IGPU patch to DSDT- my battery life is very good now. By the way there is graphic glitch on menu bar, but when i log off and log on again everything is OK. Yeah we have to use this patch and I didn't explicitly mention it assuming all would know about it. It's assumed being applied in Brightness fix section. There should not be any glitch if graphics are patched correctly. Have you changed the color profile? Have you applied 9mb patch for 0x0a260006? you can try other ig-platform-id as other Y510P users reported success with other values than 0x0a260006. Im still in same situation.. i deleted those files but did not work for me. I tried many times to boot from my usb.. and 1time i got kernel error or something ? Zip your EFI folder from USB and attach it here. Link to comment Share on other sites More sharing options...
soiggeli Posted January 4, 2015 Share Posted January 4, 2015 Zip your EFI folder from USB and attach it here. Well here it is ... https://mega.co.nz/#!Z1YChIAK!nOf5lWigA9RPSbNGS9R5lJZZKA334TliHZIWelXFW4o Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 4, 2015 Author Share Posted January 4, 2015 Well here it is ... https://mega.co.nz/#!Z1YChIAK!nOf5lWigA9RPSbNGS9R5lJZZKA334TliHZIWelXFW4o I see many of the files within Clover folder and subfolders have modified date 5th December while all files in Clover v2999 have modified date as 5th November. I told you to install v2999 and you said you did but it seems the existing files belongs to a later version. I suspect you installed v2999 on top of the previous install which did not downgrade the files and now you have mixed install which might not work. Backup your config.plist as I think it's fine and delete EFI/Clover folder from USB and reinstall Clover EFI v2999 so you have the correct files. Then, restore the backed-up config.plist and put HFSPlus.efi in place in addition to kexts. Regarding kexts, I see you have VoodooPS2Daemon in your kexts folder which is invalid. VoodooPS2Controller.kext only require that Daemon for the debug version which you do not need now, besides it's wrong location for that daemon anyway so remove it from the folder. Link to comment Share on other sites More sharing options...
newapple4g Posted January 4, 2015 Share Posted January 4, 2015 Does "fix permissions and clear cache, and boot Clover without caches" mean to tick repair permissions and rebuild cache on kext wizard then restart and boot via clover without caches ? Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 4, 2015 Author Share Posted January 4, 2015 Does "fix permissions and clear cache, and boot Clover without caches" mean to tick repair permissions and rebuild cache on kext wizard then restart and boot via clover without caches ? Yes. To boot through Clover without cache, select the boot partition while in Clover and press space then select "Boot Mac OS X without caches" Link to comment Share on other sites More sharing options...
newapple4g Posted January 4, 2015 Share Posted January 4, 2015 I know that, but i notice that it's not as same as mavericks without caches. In that case I can see how it is loading drivers and sometimes I find that audio kexts and audio patch-on-fly doesn't load even with kext-dev-mode=1 enabled does it mean that clover patch on fly complete work and it will not patch after second boot ? Link to comment Share on other sites More sharing options...
ahmed_ais Posted January 4, 2015 Author Share Posted January 4, 2015 I know that, but i notice that it's not as same as mavericks without caches. In that case I can see how it is loading drivers and sometimes I find that audio kexts and audio patch-on-fly doesn't load even with kext-dev-mode=1 enabled does it mean that clover patch on fly complete work and it will not patch after second boot ? Generally, Clover's patching on-the-fly works by patching the kexts loaded into cache. Booting without cache means there should be no patching on-the-fly for the first boot while OS X regenerates the cache. The patches should work, however, on second boot onward. The boot arg (kext-dev-mode=1) have no rule in this operation as it only allows OS X to load non Apple kexts (or modified Apple kexts) that resides in /S/L/E. You don't need this flag actually if you keep system kexts untouched (on disk) and only use patched kexts in Clover's folder or using Clover's patch on-the-fly. I hope this answers your question clear enough. Link to comment Share on other sites More sharing options...
newapple4g Posted January 4, 2015 Share Posted January 4, 2015 Thanks for that. I start installing by your guide but i wonder that without intelhd5000 patching my graphics card has been recognized and brightness work without acpibacklight kext And i dont have clover on fly patch settings for applehda but its changed some lines on applehda Link to comment Share on other sites More sharing options...
Recommended Posts