Jump to content
ahmed_ais

Help: Fixing Lenovo Y510p Nvidia GT 755M on OS X Yosemite 10.10.2

168 posts in this topic

Recommended Posts

Hello everyone,

 

I have a laptop(Lenovo Y510p) and I have a problem to get its Nvidia card working with OS X Yosemite. As the hardware configuration is unusual, I will make an introduction of the graphics system on this laptop first.

 

Introduction

 

The laptop mentioned above have three (yes three) graphics cards:

  1. Intel HD Graphics 4600 Mobile
  2. NVIDIA GeForce GT 755M (internal / built-in)
  3. NVIDIA GeForce GT 755M (external and connected through ultrabay)

It is important before I go further to describe clearly how these are configured. The laptop is in gaming category and that's why there are two Nvidia cards which are able to work in SLI mode in Windows (I know this is not supported in OS X and I don't ask about it). The laptop can run in three graphics modes (using stock BIOS of course):

  1. UMA (Intel card only): this is achievable when the external card is removed and the UMA option is selected in BIOS so the built-in Nvidia card is disabled.
  2. Dedicated: this is achievable when the external card is removed and the Dedicated option is selected in BIOS so the built-in Nvidia card is enabled. In this scenario, the built-in Nvidia card works somehow (but not exactly) like Optimus with the display being handled by Intel card.
  3. No Intel: this is achievable when the external card is connected so the BIOS will offer no graphics options at all. In this case, the built-in Nvidia card is the main for display and external Nvidia card is only available as a possible way for SLI if activated.

Not every configuration of this laptop comes with external graphics card but for those who have it like I do, the third graphic mode above certainly allow for completely disabling Intel card. Therefor, this thread is NOT to discuss Nvidia Optimus and that OS X will never utilize it, this is a totally different case.

 

The easiest way for me to install and use OS X Yosemite was to remove the external card and disable the internal Nvidia card using BIOS (or SSDT) so I rely only on Intel HD4600 which have a fix for Yosemite. Due to a problem we have with that fix for HD4600 that seems impossible to fix, I decided to ditch the Intel card and to try get Nvidia card working with Yosemite.

 

These are few questions (and their answers) that I hope they clarify the situation:

 

Q: What are you seeking?

A: To enable Nvidia built-in card (which is not Optimus and is fully connected to display) in OS X Yosemite, in the absence of Intel card

 

Q: Even if you successfully did, what do you expect to get from the external card?

A: Nothing. It will not work in SLI mode of course and it is not connected to display.

 

Q: So why do you mention / use this card at all?

A: Because it is the only way to disable Intel card completely without flashing a modded BIOS.

 

Q: Can you prove that using the external card will disable Intel card completely?

A: Definitely yes. Here's a screenshot from MSI Afterburner software with the mentioned configuration:

 

afterburner.png

 

The two Nvidia cards are almost identical and the differences between them can be seen from the image below. There are not much difference between them AFAIK.

 

both.png

 

 

The problem with OS X Yosemite

 

So I connected the external card and so Intel card is disabled and booted to Clover. As expected, Clover read only one card (the built-in Nvidia) and no sign of Intel card. I have no clue why the external card does not appear in Clover but OS X will see it after boot as I will show later on.

clover.png

 

So now I should know the proper Clover configuration for boot-args, graphics injection, and SMBIOS. I am not sure about any of these and it is the main question for this thread.

 

I tried few things to be able to boot and some of them actually worked:

  • Used SMBIOS: iMac 14.2 because one of the macs in this set actually have Nvidia GT 755M so it should be more compatible (frankly Macbook Pro 11.1 worked too).
  • Disabled dropping any ACPI table (i.e. use native tables because Nvidia may not be happy with IGPU patches I used to use before while using the Intel card)
  • Ticked Inject Nvidia (I tried with and without)
  • Ticked Inject EDID (I tried with and without)
  • Set FakeID: 0x10DE0FE9 (other FakeID I tried 0x10DE0FEA and 0x010DE0FE4 and both are for 750M)
  • Add boot-flag: nvda_drv=1, NVidia=False, npci=0x2000 (I tried all combinations)
  • Boot without caches

With some of this combinations I was able to boot OS X with Nvidia running the display:

About.png

Both Nvidia cards were recognised but the built-in card with VRAM = 0 MB the ultrabay card with a whooping VRAM = 2048 MB. This image is for the built-in card (the one connected to display):

Card1.png

This one next is for the external (ultrabay) card:

Card2.png

Now I don't know why the external one have full VRAM but the built-in card have 0 MB since both are almost the same chip. I think, since the external is correctly configured then I should not use any FakeID since it is natively supported by OS X but then I didn't have success to get the card working without any FakeID.

 

I'm sorry for the lengthy thread and all these images but I thought it is better to give all information I have. I would appreciate any help getting this to work correctly. I attached the native ACPI tables and my IOREG (with the mentioned configuration / no Intel).

 

Thanks in advance.

ACPI.zip

IOREG.zip

Share this post


Link to post
Share on other sites
Advertisement

The Nvidia 755M (Optimus technology) doesn't work in OS X, only HD 4600.

 

I'm sorry but it seems you just replied to the title. This is not Optimus and I was able to get it working because the card is configured as dedicated. I put all the details in the thread so please give it 5 minutes of your time to read though it. Thanks!

Edit:

 

From Nvidia website: http://www.geforce.com/hardware/notebook-gpus/geforce-gt-755m/description

Boost your notebook performance by up to 6.7x1 with the NVIDIA GeForce GT 755M dedicated graphics. 
Richer visuals and faster gaming for your thin and light notebook driven by the performance efficient NVIDIA Kepler™ architecture - up to 50% faster than the previous generation.2 Preview and create HD video up to 5x faster3 with GPU-accelerated video software. Perfect and share your photos in less than half the time4 with popular applications.

Share this post


Link to post
Share on other sites

Ok, read this too - From Nvidia website.

Enjoy great performance and long battery life - automatically - with NVIDIA® Optimus™ technology
The most dependable switchable graphics technology for notebooks5. The performance of dedicated graphics when you need it, battery conservation when you don’t. Perfectly balanced performance and battery life, whether you’re editing a video, surfing the web, or playing a 3D game.

NVIDIA® Optimus™ technology  ;)

Share this post


Link to post
Share on other sites

Alright ... tell me what you think about this image from my BIOS:

 

IMAG0359.jpg

 

It doesn't say SG (switchable graphics) but Discrete .. Also if it is Optimus, how am I able to boot with it alone and without Intel which I did?

Share this post


Link to post
Share on other sites

So I already gave you my opinion on this subject.

 

If you want, wait for more opinions of other users.  ;)

 

Okay, thanks for your time and I will wait.

Share this post


Link to post
Share on other sites

Okay, thanks for your time and I will wait.

 

The Optimus technology is only enabled when the Intel HD4600 is enabled. When running with both cards plugged in, the Intel card is disabled and so is Optimus. Instead, only the NVIDIA cards are active. I run my Linux install with both cards plugged in, no Optimus, and no SLI. This can be confirmed at Linux command line by running lspci and seeing no Intel HD 4600 graphics chip on the PCI-e bus when running with both NVIDIAs.

 

Therefore, I think we can run the same configuration in OS X: primary NVIDIA GPU drives the display, drives OS X. Second GPU will only serve to disable the Intel HD4600 and therefore Optimus.

 

We should also consider trying the following NVIDIA OS X drivers, especially the CUDA ones. I run the CUDA drives on my Linux install. They are designed for CUDA work, and one of the main cases for CUDA work is to run one GPU driving your display while other GPUs are doing CUDA/GPGPU work. I think this may be a reason why they could be helpful. However, I haven't confirmed that these drivers support the GT755M (or GT750M). Here are the driver links:

 

http://www.nvidia.com/download/driverResults.aspx/78853/en-us

http://www.nvidia.com/object/mac-driver-archive.html

 

By the way, I happen to have direct access to two Lenovo Y510Ps with dual GPUs, and I also have a couple of buddies and a cousin who own them too. All of them have the dual NVIDIA GPU configuration. I have OS X Yosemite 10.10.2 installed on one of them. 

 

Maybe one thing we can try is to fake the PCI ID of the 2nd GPU so OS X doesn't recognize it. I'm thinking OS X recognizes the 2nd GPU first, initializes it correctly, and leave the primary GPU uninitialized (and hence no VRAM detection). If we were to use Fake PCI ID to disable proper detection of the 2nd GPU, we might force it to initialize the first one properly.

Share this post


Link to post
Share on other sites

Hello!

 

Perhaps injecting an efistring is a possible way to get it working. The topic in the link is a bit old, but with correct inserted properties (real Apple ones) it could work for you: http://aquamac.proboards.com/thread/569?page=1

 

Have fun.

Thanks for this but it is really old.

 

Before doing anything I'm wondering why the external card is correctly identified while the internal card is not knowing that they are the same chip?

Share this post


Link to post
Share on other sites

Hello!

 

It is old, but principle should be working til now. No other gfx-injection is needed with correct efi string. GFX-card must be injected at early boottime. All other methods, especially DSDT edits, are coming to late.

 

Can you upload an Ioreg extracted with IORegestryExplorer 2... with your 2 NVDA cards being dedected? I will have a look at it, when i have time.

 

Have fun.

Share this post


Link to post
Share on other sites

Hello!

 

It is old, but principle should be working til now. No other gfx-injection is needed with correct efi string. GFX-card must be injected at early boottime. All other methods, especially DSDT edits, are coming to late.

 

Can you upload an Ioreg extracted with IORegestryExplorer 2... with your 2 NVDA cards being dedected? I will have a look at it, when i have time.

 

Have fun.

Thanks for offering help. Unfortunately, I currently have Windows only as I took the opportunity when InsanilyMac was down to focus on my work. I might install OS X in weekend but for now the only Ioreg I have is with IORegistryExplorer-SLRID_v10.6.3 (attached to post #1). If you want a different version I hope someone would offer it on my behalf or I will do next week end.

Share this post


Link to post
Share on other sites

Hello!

 

No attachment found for now - lost at breakdown. Also nice would be an origin IOREG of MBP 11,1 as txt file or extraced with same IORegestyexplorer.

 

Have fun.

Share this post


Link to post
Share on other sites

Ops, I wasn't expecting that as I read the tweet by InsanilyMac and thought it is a matter of time. I will install OS X again and get the files you requested.

 

Thanks.

Share this post


Link to post
Share on other sites

Ops, I wasn't expecting that as I read the tweet by InsanilyMac and thought it is a matter of time. I will install OS X again and get the files you requested.

 

Thanks.

You don't multiboot? I have OS X installed and could get you some files if you tell me exactly what you need and how I can get it for you.

Share this post


Link to post
Share on other sites

You don't multiboot? I have OS X installed and could get you some files if you tell me exactly what you need and how I can get it for you.

 

I used to dual-boot but currently I run Windows only to focus on my work (in which I only need Windows) and I removed OS X to avoid distraction. As styrian said, he needs a copy of ioreg which you can get by using IORegistryExplorer (read here where to download and how to use it). You need to get this while booting with both Nvidia GPUs so no trace of Intel card. He also asked for an origin IOREG of MBP 11,1 but I don't know exactly what would be different but I would assume he want another IOREG with Intel card while running with MBP 11,1 SMBIOS ... so here's what I think he wants:

  1. Copy of IOREG using IORegistryExplorer (from the link) while booting with both Nvidia GPUs and MBP 11,1 SMBIOS
  2. Copy of IOREG using IORegistryExplorer (from the link) while booting with only Intel GPU and MBP 11,1 SMBIOS

I hope he clarifies if he needs anything otherwise. Thanks for your help and of course for his help and time too.

Share this post


Link to post
Share on other sites

Hello!

 

IOREG from real MBP 11,1 would be nice. I want to look at the gfx-properties.

 

Have fun.

 

Hi,

 

I don't know this would be easy to get at least from me as I don't have this laptop.

Share this post


Link to post
Share on other sites

Hello!

 

Til now I could not find it by myself. I have got only the one of MBP 11,2. But this is a bit useless, because it has only IGPU. I must not get it from you. Perhaps anybody can help.

 

Have fun.

Share this post


Link to post
Share on other sites

Hello!

 

IOREG from real MBP 11,1 would be nice. I want to look at the gfx-properties.

 

Have fun.

I have an Early 2011 model MBP but the system info says MacBookPro8,2... Is this useful?

 

EDIT: Guess not.

 

EDIT 2: In the meantime, what can I get you from the Y510P? IOREG dump with the NVidia cards installed? Does it need to be on SMBIOS MBP 11,1? I have it on iMac 14,2 or whatever the recommended is at this point in time.

 

EDIT 3: I went from a booting OS X 10.10.2 with the config from the other thread to a broken 10.10.2 with this config. Kernel just restarts when it gets to the graphics boot part. I'm using the exact config from the first post. Do I have to do anything extra with ACPI tables except not drop any in my config? The attached ACPI tables file is gone. Any info on how to generate my own?

 

EDIT 4: I also removed the Intel patches I had from the other thread.

Share this post


Link to post
Share on other sites

Hello!

 

we should be a bit patient til the attachments have gotten restored. Using the SMB of MBP 11,1 is for sure not a bad idea. Try to set at clover screen temporary the boot argument: nv_disable=1, to make it boot.

 

Have fun.

Share this post


Link to post
Share on other sites

I have an Early 2011 model MBP but the system info says MacBookPro8,2... Is this useful?

 

EDIT: Guess not.

 

EDIT 2: In the meantime, what can I get you from the Y510P? IOREG dump with the NVidia cards installed? Does it need to be on SMBIOS MBP 11,1? I have it on iMac 14,2 or whatever the recommended is at this point in time.

 

EDIT 3: I went from a booting OS X 10.10.2 with the config from the other thread to a broken 10.10.2 with this config. Kernel just restarts when it gets to the graphics boot part. I'm using the exact config from the first post. Do I have to do anything extra with ACPI tables except not drop any in my config? The attached ACPI tables file is gone. Any info on how to generate my own?

 

EDIT 4: I also removed the Intel patches I had from the other thread.

 

 

Well, thanks for all this. 

 

I reinstalled OS X using both Nvidia GPU without intel and the installation went smooth as the case with Intel. The system booted normally and I was able to capture copies for IOREG for both SMBIOS's:

I also thought to give the EFI-String idea a try. I followed the guide here but without a success due to not being able to extract VBIOS for built-in Nvidia GPU. I understand it doesn't have a separate VBIOS as with the ultrabay GPU and its VBIOS is integrated into system BIOS. So here's what I was able to get (after suffering):

  • Ultrabay GPU VBIOS: VBIOS_UltrabayGPU.zip
  • System BIOS: (probably contains Windows license key so I prefer not to attach) 

I thought to continue with the mentioned guide above and was able to generate the efi-string xml file (EFI-String.zip) that would be used with Clover but it didn't work either.

 

I'm clueless at the moment ...

Share this post


Link to post
Share on other sites

Well, thanks for all this. 

 

I reinstalled OS X using both Nvidia GPU without intel and the installation went smooth as the case with Intel. The system booted normally and I was able to capture copies for IOREG for both SMBIOS's:

I also thought to give the EFI-String idea a try. I followed the guide here but without a success due to not being able to extract VBIOS for built-in Nvidia GPU. I understand it doesn't have a separate VBIOS as with the ultrabay GPU and its VBIOS is integrated into system BIOS. So here's what I was able to get (after suffering):

  • Ultrabay GPU VBIOS: attachicon.gifVBIOS_UltrabayGPU.zip
  • System BIOS: (probably contains Windows license key so I prefer not to attach) 

I thought to continue with the mentioned guide above and was able to generate the efi-string xml file (attachicon.gifEFI-String.zip) that would be used with Clover but it didn't work either.

 

I'm clueless at the moment ...

 

Can you upload your config.plist minus the SMBIOS as well? I tried modifying mine as per your initial post, but I still can't get it to boot. As soon as it goes to switch to graphics mode, it reboots. I'm willing to try messing with the NVIDIA drivers and try messing with FakePCIIID to get the second card to detect incorrectly. I think this might be the way to get the first card to initialize properly. My reasoning is that OS X initializes the UltraBay card correctly and skips the internal because of this.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      UPDATE:
       
      According to Vulgo, NoVPAJpeg.kext is now deprecated.
      In case its functionality is needed, use WhateverGreen.kext and add the following boot arguments:
      shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs (tested on my old MSi GTX 650)
       
      This is what I needed for my NVIDIA GPU and the MSI motherboard in the signature (*since then, I upgraded my GPU to my current RX 580). Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
       
      Cheers!
    • By ludufre
      Installing macOS Mojave on Lenovo ThinkPad L440

       
      There are two version of this laptop:
      - 20AS = Chipset QM87, without Express Card (mine).
      - 20AT = Chipset HM86, with Express Card.
      I strong believe is the same thing...
       

      Changelog:
       
      07/30/2019 14:56h GMT-0
      - Fixed typo in credits. Thanks @"Sniki"
       
      06/09/2019 14:16h GMT-0
      - Added missing parts in the post-install step. 
       
      06/04/2019 17:19h GMT-0
      - Updated Clover link. 
       
      06/02/2019 18:08h GMT-0
      - Added info about update 10.14.5. 
       
      03/13/2019 13:15h GMT-0
      - Updated info about touchpad replacement and CPU and 4G LTE modem.
       
      02/05/2019 18:47h GMT-0
      - Updated info about CPU replacement and 4G LTE modem.
       
      02/04/2019 15:24h GMT-0
      - Sometimes the VoodooHDA.kext doesn't work.
      - Added AppleHDADisabler.kext to fix that (attached bellow).
       
      01/24/2019 14:42h GMT-0
      - Added more adjustments to use of VoodooHDA.
      - Updated VoodooHDA links to 2.9.1 official (without installer).
      - Changed PCM volume from 90 to 180 in Info.plist (attached modified VoodooHDA.kext bellow)
      - Updated SSDT-L440.aml (Removed HDEF and HDAU, not needed).
      - Updated config.plist (Changed to user Audio layout to 1).
       
      01/22/2019 20:47h GMT-0
      - I gave up on the AppleALC.
      - Headset does not work.
      - Now with VoodooHDA is perfect and the sound even louder.
       
      01/22/2019 14:37h GMT-0
      - Added info about update 10.14.3. 
       
      01/22/2019 13:46h GMT-0
      - Added link to BIOS reassing guide.
       
      01/20/2019 11:49h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor: Intel Core i5-4300M ->  Work. All SpeedStep stages.
      - Video Card: Intel HD4600 ->  Work. QE/CI and Metal.
      - Chipset: Intel QM87 ->  Work.
      - Mini DisplayPort ->  Work. But no audio, yet.
      - VGA ->  Not work. Normal.
      - Audio: ALC292 ->  Work.
      - WiFi/Bluetooth: Intel AC 7260 ->  Not work. Replaced with DW1560 (need whitelist removal).
      - Ethernet: Intel I217-LM ->  Work.
      - Card Reader: Realtek RTS5227 ->  Not work.
      - Keyboard and Touchpad ->  Work.
      - Webcam ->  Work.
      - Fingerprint Reader ->  Not work. Normal.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
      - Airdrop, Handoff, Instant Hotspot and Continuity ->  Work after replaced wireless.
       
       
      Extras
       
      - FullHD 1920x1080 display upgrade: 
      Replaced with AU Optronics B140HAN01.1 30pin eDP (B140HAN01.2 and B140HAN01.3 also compatible).
      Apparently same screen as Dell Latitude E6440, E7440, Lenovo Ideapad U430 and E129.
       
      - CPU upgrade:
      Replaced the stock Intel Core i5 4300M 2.6Ghz (3.3Ghz turbo) 6M cache with Intel Core i7 4700MQ 2.4Ghz (3.4Ghz turbo) 6MB.
      I initially had problems with overheating. The processor ran at full load above 90 degrees.
      After using a quality thermal paste I can work between 70 and 80 degrees.
      Acceptable taking into consideration that the new processor has 47TDP versus 37TDP which is recommended.
      I also had no problem consuming the battery while charging. The original 65W source seems to have figured out.
       
      - Touchpad upgrade:
      Replaced the stock with T460 touchpad.
      This is serious: you have to do it! It should be stock. Touchpad with precision and absurd quality!
      Just do it!
       
      - RAM upgrade:
      No mistery here. Just upgade.
       
       
      Todo
       
      - Make DP audio work.
      - Make Card Reader work.
      - Upgrade CPU to i7-4712MQ (Ordered. It's on the way) Done, but received i7-4700MQ (47w TDP, with good paste I have no overheating)
      - Replace touchpad with T460 model (Ordered. It's on the way) Done. Sensitivity and perception of quality much better. I recommend 100%!
      - Sierra Gobi5000 4G LTE modem EM7355 (Ordered. It's on the way. I hope works. ) Done, but not work. Recognize but not connect. I already gave up...
      - Upgrade to 16GB RAM Done
      - Make trackpad appear in System Preferences
       
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover EFI
      - Clover Configurator
      - Some KEXTs and SSDT patches


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Install --nointeraction This will take about 30 minutes.
       


      Install bootloader

      Download the CloverEFI from SourceForge (used 4934) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - ApfsDriverLoader-64
      - UEFI Drivers - AptioMemoryFix-64


       
       
      Make things works

      Will be created a partition named EFI and mounted in Desktop.
      - Replace the /Volumes/EFI/CLOVER/config.plist with mine attached below
                    If you have modded BIOS with Advanced Menu and enabled 128MB DRAM-prealloc use 128MB_DRAM-prealloc_config.plist.zip
                    If no, then use 32MB_DRAM-prealloc_config.plist.zip
      - Put SSDT-L440.aml attached below in /Volumes/EFI/CLOVER/ACPI/patched/
       
      Generate your Serial, MLB and SmUUID
       
      - Open the replaced config.plist with Clover Configurator (used 5.3.2.0)
      - Go to SMBIOS, click few times in "Generate New" in Serial Number and SmUUID.
       
      Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the HWSensors 3 from here. I used the FakeSMC.kext, ACPIMonitor.kext and IntelCPUMonitor.kext inside of DMG version r196.
      - Download the VoodooPS2Controller.kext from here. I used version 2018-1008.
      - Download the IntelMausiEthernet.kext from here. I used the version 2018-1031.
      - Download the Lilu.kext from here. I used the version 1.3.6.
      - Download the VoodooHDA from here. I used the version 2.9.1 and patched the sound volume (attached below).
      - Download the WhateverGreen.kext from here. I used the version 1.2.9.
      - Download the AppleBacklightFixup.kext from here. I used the version 2018-1013.
      - Download the USBInjectAll.kext from here. I used the version 2018-1108.
      - Download the ACPIBatteryManager.kext from here. I used the version 2018-1005.
       
      - Download the VirtualSMC.kext from here. I used version 1.0.2. Replaced with FakeSMC of the HWSensors 3 r196 package.
      - Download the FakeSMC.kext from here. I used the version 2018-0915. Replaced with VirtualSMC.kext due 10.14.4 issues on update.
      - Download the AppleALC.kext from here. I used the version 1.3.4. Replaced with VoodooHDA.kext due mic not working.
       
       
      Wifi and Bluetooth (DW1560 / BCM94352Z)
       
      Unfortunately, some notebook manufacturers are currently blocking the replacement of wireless cards. They want you to only use the models sold by them. And of course, none of them from Lenovo for this notebook model is compatible with MacOS.
       
      If you try to start with an unauthorized wifi card for them, you will receive a screen error:
      1802: Unauthorized network card is plugged in - Power off and remove the network card. Since this check is done directly in the BIOS, the only solution is to modify it.
      But since nothing is easy in this life, there is one small big problem:
      - The BIOS update procedure does not allow you to use modded files as it used to be.
      - You will need to physically reach your BIOS on the motherboard and make use of a USB BIOS reader/writer.
       
      So what you need to do:
      1. Disassembly your laptop;
      2. Dump your BIOS with an USB BIOS reader with SOIC8 clip (to not desolder from the motherboard);
      3. Patch it (In addition to removing the whitelist, add the advanced menu);
      4. Fix RSA signature;
      5. Reflash BIOS;
      6. Replace wireless card;
      7. Remount your laptop;
      8. Done.
       
      Soon, I'll provide step by step in this process. Probably until end of this week.
      In the meantime, if you need to, send me your dump that I do steps 3 and 4 for you.
      I also add the Advanced Menu so you can increase to 128MB the DRAM-prealloc.
       
      To fix a Modded BIOS to remove the 5 beeps on boot, you need this guide: https://www.insanelymac.com/forum/topic/337333-guide-fix-insyde-h2o-bios-signature-5-beeps-on-lenovo (traduzido: pt-BR)
       
       
      After replaced the wireless card. Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the AirportBrcmFixup.kext from here. I used the version 2.0.0.
      - Download the BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext from here. I used the version 2018-0505.
      - Download the BT4LEContinuityFixup.kext from here. I used the version 1.1.2.
       
       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      My BIOS is the latest: 1.93 (J4ET93WW) 

      - Shutdown and insert the flash drive.
      - Power on with F1 pressed to enter BIOS setup.
      - Change value: Config - Intel(R) AMT - Intel(R) AMT Control to DISABLED
      - Change value: Security - Security Chip to DISABLED
      - Change value: Security - Anti-Theft - Intel(R) AT Module Activation to DISABLED
      - Change value: Security - Anti-Theft - Computrace to DISABLED
      - Change value: Security - Secure Boot to DISABLED
      - Change value: Startup - UEFI/Legacy Boot to BOTH, Legacy First and CSM Support = Yes
      - Save & Exit Setup (F10)
       
      - Now, hold the F12
      - In the list, select your flash drive.
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "Macintosh".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot. Maybe you have to press F12 again and select the flash drive.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the EFI folder inside your destination disk EFI parittion, with EFI folder inside flash card EFI partition.

      If the flash drive EFI partition of your destination disk or flash drive is unmounted:
      Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 0 for destination disk and 1 for flash drive.
       
      Then, eject the flash drive.
       
      Last step
       
      Move all Kexts from EFI partition to /Library/Extensions, with those commands in Terminal:
      sudo mv -R /Volumes/EFI/EFI/CLOVER/kexts/Other/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i / Restart the system.
       
       
      It's done!
       
       
      Updates
       
      System update 10.14.3
       
      - Updated with success;
      - Everything works perfectly after reboot;
       

       
       
      System update 10.14.4
       
      - Updated Clover to 4910.
      - Updated Lilu.kext to 1.3.5 and WhateverGreen to 1.2.7.
      - After first reboot the update progress stoped with:
      GTrace synchronization point 4 Unsupported CPU Unsupported PCH hmm.. mismatch sizes: 3100 vs 20 It was still possible to start the previous installation, selecting "Macintosh" as opposed to "macOS Install" in Clover.
      So I created a flash drive with Clover 4910 and put only my config.xml, SSDT-L440.aml, the updated Lilu.kext and WhateverGreen.kext. And I decided to test VirtualSMC instead of FakeSMC.kext.
      With this I was able to install update 10.14.4. After installation I can boot normally, even with FakeSMC.kext that already in /Library/Extensions.
      I do not know what exactly happened, but now works everything like was previously.
       


       
       
      System update 10.14.5
       
      - Updated Clover to 4934.
      - Updated Lilu.kext to 1.3.6 and WhateverGreen to 1.2.9.
      - After first reboot the update progress stoped again (like 10.14.4 update) with:
      GTrace synchronization point 4 Unsupported CPU Unsupported PCH hmm.. mismatch sizes: 3100 vs 20 It was still possible to start the previous installation, selecting "Macintosh" as opposed to "macOS Install" in Clover.
      I decided to rollback to FakeSMC.kext but this time with the version of HWSensors 3. Link above.
      With this I was able to install update 10.14.5. After installation I can boot normally.
       

       
       

      And last but not least

      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas, @"Sniki" and all others members involved directly or indirectly.
       
       
      Attachments
      32MB_DRAM-prealloc_config.plist.zip
      128MB_DRAM-prealloc_config.plist.zip
      SSDT-L440.aml
      VoodooHDA.kext.zip
      AppleHDADisabler.kext.zip
    • By Amit Meena
      This card is working OOB, but it has some graphical issues as per attachments.

      If someone has a solution please share.






    • By k.panic
      Hi to all!

      I've installed Yosemite on:
      - i5 4690
      - ASRock H87M Pro4 (with intel ethernet I219-V) (IntelMausiEthernet, AppleIntelE1000 and RehabMan for I219V kexts)
      - 8gb ddr3 RAM
      - 1tb hard disk
       
      If I disable I219-V from BIOS, when I shutdown it, don't reboots (tested with all kexts)
      If I enable I219-V from BIOS, when I shutdown it, the system reboots.
       
      How can I fix this? Thanks!
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
×