Jump to content

Guide for Installing OS X on Lenovo IdeaPad Y510p


ahmed_ais
 Share

1,428 posts in this topic

Recommended Posts

First of all there's no Clover partition. There's a Clover folder under "EFI" partition.

 

See Should I use Clover partition made By that Guy just to make A Yosemite Installer And Then I can Install Clover Using the Approach Given By you in the guide 

Do you think this is a good Idea Cause His clover Partition Is very Stable 

 

If you can boot to "Installer" using "his" clover files then its ok. But after installation follow the steps from guide and install/configure clover on your own.

 

I'm curious, post the clover folder here.

Link to comment
Share on other sites

Efi folder: https://drive.google.com/file/d/0B0pRSqWutwUSZ0N6WXhvN3A3WjA/view?usp=sharing

 

Can you give Me link for clover the one specified in Download Section is not working 

 

Your EFI folder seems fine to me. Also the config.list. There are some improvements though. 

  1. Update the ACPI tables (You can use my script for that)
  2. Add "SortedOrder" in config.plist.
  3. Check if NVRAM works properly without EmuVariableUEFI. If yes, then remove it.

For clover, download the latest one directly from its sourceforge site.

Link to comment
Share on other sites

Can you give Me link for clover the one specified in Download Section is not working 

 

Hi .. if you mean that the link in downloads section is dead, no it is not. But if the link is directing you correctly and you think it is not a good source for CloverEFI then you should know this is the official place to get Clover and you would not find a better package elsewhere. Instead of looking for other place to download it, let's focus on how to get it working for you.

 

I'm not sure what is the exact problem you have since I was not following up. But start with minimal configuration then keep adding stuff. That is, make sure you are able to boot with Clover:

  • Without ant DSDT or SSDT
  • Without any extra Kext than FakeSMC and *PS2Controller
  • Without any hotpatches in config.plist

If you can get this to work then everything should be good step by step. If not, be clear on what the problem is so we can offer better advice. Cheers!

Link to comment
Share on other sites

You should also add the "SortedOrder" in your config.plist under "Downloads" section. Its important.

AFAIK It is only important if the patched SSDT's are not in the same order as the OEM ones which is not the case on my machine. I would assume your Auto-Patcher keeps track of the correct order so no one here actually need this. Isn't it?

 

BTW, how many of the OEM SSDT's are you using (either patched or not)?

 

And also remove the custom entries under "GUI" in config.plist.

Yea it will not work as is with anyone but me due to different UUID for their partitions. But I left it on purpose so maybe someone will want to do the same cosmetic change to Clover so they just need to find the proper UUID. I will remove it after adding a note about it in the guide.

Link to comment
Share on other sites

AFAIK It is only important if the patched SSDT's are not in the same order as the OEM ones which is not the case on my machine. I would assume your Auto-Patcher keeps track of the correct order so no one here actually need this. Isn't it?...

 

No. Unlike DSDT (which is injected specifically by Clover), no matter how you keep your SSDT order or rename them, intermittently clover will inject them in wrong order. It doesn't even matter which machine it is. My script keeps the same order as it should be but its clover ultimately which will inject them. It sometimes inject them in wrong order. You can check it in your bootlog. Wrong injection order means, the SSDT's won't be used at all.

 

I found many logs/posts which clearly indicate wrong injection of SSDT's. That's why i said it's important.

 

If you don't believe me take a look at RehabMan's guide for "Patching DSDT/SSDT's".

 

BTW, how many of the OEM SSDT's are you using (either patched or not)?

 

I use 5 SSDT's. 2 of them patched. 1 is custom CPU and 2 other's unpatched. You can see which SSDT's i did not include in my script.

 

You can try and include native OEM CPU SSDT's to see if there's any performance gain. JayMonkey from TM is trying them. You can experiment too.

EDIT : IMP, If you use native OEM CPU SSDT's no need to patch PNOT in that case.

Link to comment
Share on other sites

If you don't believe me take a look at RehabMan's guide for "Patching DSDT/SSDT's".

 

No I believe you (why would you lie  :D ). I was reading Rehabman's guide you mentioned before I reply and I think I misunderstood his phrase:

Note regarding Clover v3062+: A change in the way SSDTs are loaded from ACPI/patched makes the order non-deterministic.[/size]

 

So yes. This complies with what you are saying and I will update that. Thanks.

 

 

I use 5 SSDT's. 2 of them patched. 1 is custom CPU and 2 other's unpatched. You can see which SSDT's i did not include in my script.

I wonder what are the other unpatched 2 SSDT's. I guess one of them is CB-01 but what is the other? following the script to find this out is not straight forward.

Link to comment
Share on other sites

 ....I wonder what are the other unpatched 2 SSDT's. I guess one of them is CB-01 but what is the other? following the script to find this out is not straight forward.

 

One of them is PTID (sensors) and the other one is CPU related OEM SSDT. I didn't check recently but i was not able to boot without it before.

 

I actually wanted to experiment using OEM CPU SSDT. There are reports that it actually works great (system feels more snappier, smooth etc). I even modified my script to use native CPU SSDT's but i've disabled it until i am sure.

 

If you go that route then you'll have to do some changes though like not patching PNOT in DSDT. You can see that explained and commented in "rename_ssdts" function in my script.

 

I am just waiting for my wifi card. Then i'll do all sorts of experiments.

Link to comment
Share on other sites

One of them is PTID (sensors) and the other one is CPU related OEM SSDT. I didn't check recently but i was not able to boot without it before.

 

I actually wanted to experiment using OEM CPU SSDT. There are reports that it actually works great (system feels more snappier, smooth etc). I even modified my script to use native CPU SSDT's but i've disabled it until i am sure.

 

If you go that route then you'll have to do some changes though like not patching PNOT in DSDT. You can see that explained and commented in "rename_ssdts" function in my script.

 

I am just waiting for my wifi card. Then i'll do all sorts of experiments.

 

I am able to boot without any of them actually. I currently only have the two SSDTs that contain graphics bits (number 3 and 4 after renaming in your script) and both are patched. In addition to CPUPM and a separate SSDT for disabling Optimus. So I don't use any OEM untouched SSDT at all.

 

EDIT: But I want to experiment with the CPU one as I'm not sure about the consequences of removing it.

Link to comment
Share on other sites

I am able to boot without any of them actually...

 

I am too. By "not able to boot" I meant because of KP. Don't remember the exact reason though. 

 

 ....I currently only have the two SSDTs that contain graphics bits (number 3 and 4 after renaming in your script) and both are patched. In addition to CPUPM and a separate SSDT for disabling Optimus. So I don't use any OEM untouched SSDT at all.

 

SSDT no. 4 is the one with Nvidia details (Optimus). So that makes a total of 3 SSDT's. 

 

The PTID one is useless in OS X actually. Also the OEM CPU one. I'll experiment.

 

...EDIT: But I want to experiment with the CPU one as I'm not sure about the consequences of removing it.

 

Me too.

Link to comment
Share on other sites

Well Your Patched Worked Out of the Box and my Battery is pretty Stable now 

 

:( But now I am in Other Problem Well the Left corner Text with  that Sysmbol is lookin disorted and The text like " safari Edit View " and Looking crappy restive the Things are perfectly fine .Did you guys faced it

Link to comment
Share on other sites

Well My android Phone is not getting detected when I plug it in My Yosemite and when I plug a pen drive It read It perfectly??

That's normal because you have to use Android File Transfer application for your android to be detected. Read the simple instructions and download the application here: https://www.android.com/intl/en_uk/filetransfer/

Link to comment
Share on other sites

Hey Can you Explain Me how to use the usb 3.0 section Its a bit confusing what you have written where should I put that Code

 

Try without it first. I asked others to check if its not needed. No feedback yet.

 

If USB ports are not working after putting system to "sleep", then copy that patch in "KextToPatch" section in config.plist.

Link to comment
Share on other sites

Well I am an android developer and want to want to connect my phone so I  can test my but it was not getting Detected so Thought I had not patched usb 3.0 drivers properly

 

Me too. If your phone supports "Mass Storage Mode" it should work like any other flashdrives. If not then follow @Ahmed's advice and download "Android File Transfer".

 

Have patience. It might take a while to detect your android phone in AFT.

Link to comment
Share on other sites

Well guys this is something rehab man  Told me after having a look at my Efi folder

 

May this help you to update your Guide

 

Rehabman:

VoodooPS2Daemon is not a kext and should not be present in Clover/kexts/10.10.

BTFirmwareUploader.kext is known to be buggy. You should use BrcmPatchRAM.kext instead.

Some of your kexts are old builds (ACPIBatteryManager, FakeSMC, FakePCIID*).

Only you can use your patched DSDT/SSDT files. Using files from another computer is a bad idea and can/will lead to hard to diagnose problems.

Your config.plist does not specify ACPI/SortedOrder. It is important. It is also a good idea to use DSDT "Fixes" FixRegions and NewWay.

It is all covered in my DSDT/SSDT patching guide: 

[Guide] Patching LAPTOP DSDT/SSDTs

, and the installation guide: 

[Guide] Booting the OS X installer on LAPTOPS with Clover UEFI


You may wish to reconsider publishing the serial# (smbios info) you're using on the internet.

Link to comment
Share on other sites

Well guys this is something rehab man  Told me after having a look at my Efi folder

 

May this help you to update your Guide

 

Rehabman:

  1. VoodooPS2Daemon is not a kext and should not be present in Clover/kexts/10.10.
  2. BTFirmwareUploader.kext is known to be buggy. You should use BrcmPatchRAM.kext instead.
  3. Some of your kexts are old builds (ACPIBatteryManager, FakeSMC, FakePCIID*).
  4. Only you can use your patched DSDT/SSDT files. Using files from another computer is a bad idea and can/will lead to hard to diagnose problems.
  5. Your config.plist does not specify ACPI/SortedOrder. It is important. It is also a good idea to use DSDT "Fixes" FixRegions and NewWay.

It is all covered in my DSDT/SSDT patching guide: 

[Guide] Patching LAPTOP DSDT/SSDTs

, and the installation guide: 

[Guide] Booting the OS X installer on LAPTOPS with Clover UEFI

You may wish to reconsider publishing the serial# (smbios info) you're using on the internet.

 

 

I agree. for points 1,2,3,4 and these are things you should do on your setup.

  1. The guide never mentioned using VoodooPS2Daemon
  2. BrcmPatchRAM.kext is present and recommended in the guide
  3. No kexts are linked directly but the main download website is linked instead which have the most up-to-date version. You should update regulary
  4. Patch yours. I will take down my ACPI files, the Auto-Patcher is sufficient anyway
  5. I will do that ...
Link to comment
Share on other sites

 Share

×
×
  • Create New...