Jump to content
arsradu

[HOW TO] Fix QuickLook and Preview loading issues in Mojave

326 posts in this topic

Recommended Posts

6 hours ago, JaredTop said:

This topic is like a real treasure chest. Thanks!

 

Thanks, man. Appreciated. Wouldn't be possible without the help and constant feedback of some of the really nice people on this forum.

Edited by arsradu

Share this post


Link to post
Share on other sites
Advertisement

Hi all, I'd like to check if what I have done is ok: I enabled my internal GPU from my UEFI settings and I got quick look and preview working. However, the iGPU doesn't show on System Information. Under the graphics section, only my RX 580 is shown. I did not change my SMBIOS or installed any kext. Have done correctly? Thanks!

Share this post


Link to post
Share on other sites
Hi all, I'd like to check if what I have done is ok: I enabled my internal GPU from my UEFI settings and I got quick look and preview working. However, the iGPU doesn't show on System Information. Under the graphics section, only my RX 580 is shown. I did not change my SMBIOS or installed any kext. Have done correctly? Thanks!

Are you sure it’s enabled then? What’s your iGPU?


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
13 minutes ago, SavageAUS said:


Are you sure it’s enabled then? What’s your iGPU?


Sent from my iPhone using Tapatalk

that is right.. i aslo do that as he said.. hardware acceleration enabled on my rig.

Share this post


Link to post
Share on other sites
2 hours ago, reloadedhead said:

Hi all, I'd like to check if what I have done is ok: I enabled my internal GPU from my UEFI settings and I got quick look and preview working. However, the iGPU doesn't show on System Information. Under the graphics section, only my RX 580 is shown. I did not change my SMBIOS or installed any kext. Have done correctly? Thanks!

 

If you're using WhateverGreen, I think that will enable it without showing it in Graphics in your System Report.

 

Now, let's take them one by one:
1. Please, add your hardware information to your signture so we know what are we talking about. :) 

2. If you're using a MacPro SMBIOS, that will not show any IGPU since they've got none.

3. To make sure the iGPU is enabled on the OS side, as well, you need two things added to your config.plist, for as far as I know:

  • InjectIntel (should be checked)
  • correct ig-platform-id for your iGPU

So, in order to see what we are dealing with, we need to know which hardware are you using (aside from the RX 580 which was obvious). And which SMBIOS. If the iGPU is enabled in BIOS, and everything else is configured correctly on system side, it should show up.

Share this post


Link to post
Share on other sites
7 hours ago, arsradu said:

 

If you're using WhateverGreen, I think that will enable it without showing it in Graphics in your System Report.

 

Now, let's take them one by one:
1. Please, add your hardware information to your signture so we know what are we talking about. :) 

2. If you're using a MacPro SMBIOS, that will not show any IGPU since they've got none.

3. To make sure the iGPU is enabled on the OS side, as well, you need two things added to your config.plist, for as far as I know:

  • InjectIntel (should be checked)
  • correct ig-platform-id for your iGPU

So, in order to see what we are dealing with, we need to know which hardware are you using (aside from the RX 580 which was obvious). And which SMBIOS. If the iGPU is enabled in BIOS, and everything else is configured correctly on system side, it should show up.

 

I am not using WhateverGreen. 

1. I added my HW info to my signature!

2. My SMBIOS is iMac 18,1

3. Should I add those things since I have already solved the problem?

 

Thanks!

Share this post


Link to post
Share on other sites
46 minutes ago, reloadedhead said:

 

I am not using WhateverGreen. 

1. I added my HW info to my signature!

2. My SMBIOS is iMac 18,1

3. Should I add those things since I have already solved the problem?

 

 Thanks!

 

You mean the QuickLook/Preview issues? Yeah, the problem is fixed, but if I go this right, you want to have your iGPU displayed in System Report -> Graphics, right?

 

Which, I think is more of a cosmetic issue than anything else. :)) But it is displayed in my case. So...we can try InjectIntel and ig-platform-id 0x3E910003 or 0x3E920003 or 0x3E9B0007 and see if it makes any difference.

You can use Clover Configurator for a more user-friendly approach.

 

181989838_Screenshot2018-11-21at15_36_26.png.729bd01e2cd3d8ce6852f5565e073ebd.png

 

If it doesn't bother you that much, you can just as well ignore it. :)) But looks like something is not recognised.

Edited by arsradu

Share this post


Link to post
Share on other sites
2 minutes ago, arsradu said:

 

You mean the QuickLook/Preview issues? Yeah, the problem is fixed, but if I go this right, you want to have your iGPU displayed in Graphics under System Report, right?

 

Which, I think is more of a cosmetic issue than anything else. :)) But it is displayed in my case. So...we can try InjectIntel and ig-platform-id 0x3E910003 or 0x3E920003 or 0x3E9B0007 and see if it makes any difference.

You can use Clover Configurator for a more user-friendly approach.

 

181989838_Screenshot2018-11-21at15_36_26.png.729bd01e2cd3d8ce6852f5565e073ebd.png

 

If it doesn't bother you that much, you can just as well ignore it. :)) But looks like something is not recognised.

i activate hardware acceleration through this patching whatevergreen.kext.

Share this post


Link to post
Share on other sites
Just now, xtddd said:

i activate hardware acceleration through this patching whatevergreen.kext.

 

Yeah, as I said, WhateverGreen will do pretty much the same thing as the things I mentioned at point 3 above. But since reloadedhead doesn't use WhateverGreen, another way is by injecting Intel and adding ig-platform-id.

Share this post


Link to post
Share on other sites
1 minute ago, arsradu said:

 

Yeah, as I said, WhateverGreen will do pretty much the same thing as the things I mentioned at point 3 above. But since reloadedhead doesn't use WhateverGreen, another way is by injecting Intel and adding ig-platform-id.

injecting Intel and adding ig-platform-id can also works fine. i tested it 

Share this post


Link to post
Share on other sites

Hello! 
I still do not have a working preview.:( I tried NoVPAJpeg and changed smbios. does anyone have any idea how to fix it?

Intel Core i3 4150 
Intel HD 4400
macOS Mojave

 

Spoiler

Zrzut ekranu 2018-11-22 o 21.41.00.png

 

Spoiler

IMG_5013.jpg

 

Edited by pprommelus

Share this post


Link to post
Share on other sites
50 minutes ago, pprommelus said:

Hello! 
I still do not have a working preview.:( I tried NoVPAJpeg and changed smbios. does anyone have any idea how to fix it?

Intel Core i3 4150 
Intel HD 4400
macOS Mojave

 

  Reveal hidden contents

Zrzut ekranu 2018-11-22 o 21.41.00.png

 

  Reveal hidden contents

IMG_5013.jpg

 

Have you tried WhateverGreen.kext?

Share this post


Link to post
Share on other sites
1 hour ago, Cyberdevs said:

Have you tried WhateverGreen.kext?

Yes. I did clean installations from the scratch with WhateverGreen ;(

1589177456_Zrzutekranu2018-11-22o23_46_15.png.3e967a7a4cbdcd8aeec347915688ab05.png1026281985_Zrzutekranu2018-11-22o23_46_39.png.c00feb0a04a9904c9e8654e75d399ec6.png

 

This is my config.plist file

Edited by pprommelus

Share this post


Link to post
Share on other sites
Yes. I did clean installations from the scratch with WhateverGreen ;(

1589177456_Zrzutekranu2018-11-22o23_46_15.png.3e967a7a4cbdcd8aeec347915688ab05.png1026281985_Zrzutekranu2018-11-22o23_46_39.png.c00feb0a04a9904c9e8654e75d399ec6.png

 

This is my config.plist file

Are you using FV2?

If not your drivers64uefi folder can be trimmed.....a lot.

Which smbios are you using now?

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
20 hours ago, SavageAUS said:

Are you using FV2?

If not your drivers64uefi folder can be trimmed.....a lot.

Which smbios are you using now?

 

No, I don't use FV2, so you sugest that i can remove some drivers form drivers64uefi?
Now i'm using SMBIOS - iMac14,2 

Share this post


Link to post
Share on other sites
4 hours ago, pprommelus said:
No, I don't use FV2, so you sugest that i can remove some drivers form drivers64uefi?

Now i'm using SMBIOS - iMac14,2 

Yes you can remove quite a few.

I’ll update this post with a screenshot of my drivers64uefi folder non FV2.

Also can you post a screenshot of what it looks like when you try preview.

 

 

Sent from my iPhone using Tapatalk

1455574037_ScreenShot2018-11-24at1_14_36pm.png.3d1761de7fa1238a98953ff0e38347f9.png

 

Also backup your config.plist and try the one attached.

config.plist

Edited by SavageAUS

Share this post


Link to post
Share on other sites
On 11/24/2018 at 3:42 AM, SavageAUS said:

Also can you post a screenshot of what it looks like when you try preview.

Also backup your config.plist and try the one attached.

config.plist

Preview issue https://www.youtube.com/watch?v=QemQrYo2-_0&feature=youtu.be
When I try to boot with your config I got a "failed to get apfs volume key bag, err = 2"

 

Share this post


Link to post
Share on other sites
On 11/25/2018 at 8:42 PM, pprommelus said:

Preview issue https://www.youtube.com/watch?v=QemQrYo2-_0&feature=youtu.be
When I try to boot with your config I got a "failed to get apfs volume key bag, err = 2"

 

 

Do you have video acceleration? Cause it kinda looks like you don't... Also, that is not the Preview issue this thread is meant to fix. The Preview issue of this thread (but that's not your issue, for as far as I can see), is that when trying to open a jpeg file, the window will display a loading animation and freeze in that state. You don't get a picture at all. But as i said, this is not the issue in your case, for as far as I can see.

 

 

EDIT:

Are you using a patched SSDT/DSDT? If you do, please, remove them before attempting any of this.

 

Also, for as far as I could read online, in order to get Full QE/CI, you need to patch a few things, which looks like you didn't. So...as I was suspecting, you don't have full acceleration. And that issue seems to be the result of that.

 

You can try the attached config plist and see if it makes any difference.

 

I'm not sure if WhateverGreen is supposed to fix this...but it kinda looks like it doesn't help much here. Ooor...maybe this is a different issue specific to Mojave. But judging by the stuttering I saw in your video, my guess is that there is something wrong with your video acceleration. Also, it shows that your issue has nothing to do with the Preview issue that this thread is aiming to fix. :) But that's a different story.

 

I would recommend leaving the attached config's name "config2.plist", exactly as it is right now. Just in case there's something I messed up and you can't boot anymore. Also, I'm not sure that IntelGFX 0x04128086 is the correct value for you. I'd say, IF (and ONLY IF) you're planning on going this route, maybe try 0x0a168086 instead.

 

But first, try without anything, since the patches I added in Kernel and Kext Patches should (at least in theory) take care of that anyway. But as I said, if you wanna go that route, maybe try 0x0a168086 instead in Devices -> IntelGFX.

 

Now, how to use the config2.plist I gave you without replacing the original config. Well, just copy-paste it in Clover/config2.plist, and upon booting up, in Clover UI, go to Options -> Configs and select Config2.plist. Then Return, and boot normally by selecting your boot partition.

 

This way, you still keep your default config.plist, should you need it. And you can still try the changes I proposed in this new config without messing up your system.

 

Also, I left ig-platform-id 0x0D220003 in Graphics, but...I'm not sure that's correct either... I could be wrong though.

 

You can try to see if you get your iGPU properly recognised in About this Mac -> System Report -> Graphics/Displays. Maybe post a screenshot here, as well, if you can.

 

Also, as a side note, I would recommend getting a dedicat GPU, if possible. Even some older ones like the Nvidia GTX 650 are miles better than the on-board graphics. And they're very cheap. Not to mention, the GTX 650 works OOB including in Mojave.

config2.plist

Edited by arsradu

Share this post


Link to post
Share on other sites
On 11/25/2018 at 8:05 PM, arsradu said:

 

Do you have video acceleration? Cause it kinda looks like you don't... Also, that is not the Preview issue this thread is meant to fix. The Preview issue of this thread (but that's not your issue, for as far as I can see), is that when trying to open a jpeg file, the window will display a loading animation and freeze in that state. You don't get a picture at all. But as i said, this is not the issue in your case, for as far as I can see.

.........


 

Thank you for your help and commitment :)

Unfortunately, your system did not want to run with your config. It started when I turned off the Intel Inject, but there is absolutely no graphics acceleration.

1349380378_Zrzutekranu2018-11-27o21_17_49.thumb.png.47431f81b767e6cbd3a3684777682832.png


On my config, regardless of whether I type IntelGFX, ig-platform-id, Inject Intel, the graphics work, but there is still a problem with the preview.
1200002812_Zrzutekranu2018-11-26o23_59_19.thumb.png.992ef552e6c544efc146e7201d57b4c1.png

 

You probably are right that the graphics do not work 100%. According to what guide should I try to patch 4400 in Mojave?

Unfortunately I have no place on the GPU in my case, so I have to run Intel :((((((((

Edited by pprommelus

Share this post


Link to post
Share on other sites
9 minutes ago, pprommelus said:


 

Thank you for your help and commitment :)

Unfortunately, your system did not want to run with your config. It started when I turned off the Intel Inject, but there is absolutely no graphics acceleration.

 


On my config, regardless of whether I type IntelGFX, ig-platform-id, Inject Intel, the graphics work, but there is still a problem with the preview.
 

 

You probably are right that the graphics do not work 100%. According to what guide should I try to patch 4400 in Mojave?

Unfortunately I have no place on the GPU in my case, so I have to run Intel :((((((((

 

No idea.... I'm not sure it can be fixed... Especially if it worked fine with High Sierra. For as far as I can tell, it seems to be something specific to Mojave.

 

Anyway, which case are you using? Even really small ones still allow for a PCI graphics card... And the GTX 650 is small anyway. I'm sorry, I'm not sure how to fix this. What I can tell you is that you're definitely not the only one with this issue on the Intel HD 4400 and Mojave.

Share this post


Link to post
Share on other sites
32 minutes ago, arsradu said:

 

No idea.... I'm not sure it can be fixed... Especially if it worked fine with High Sierra. For as far as I can tell, it seems to be something specific to Mojave.

 

Anyway, which case are you using? Even really small ones still allow for a PCI graphics card... And the GTX 650 is small anyway. I'm sorry, I'm not sure how to fix this. What I can tell you is that you're definitely not the only one with this issue on the Intel HD 4400 and Mojave.

 


I use thermaltake core v1 and miniitx board and I have one PCIe slot in which I have a wifi adapter card. I would have to change the MOBO and case. then I could use the GPU. 

Maybe it would be good with another CPU? with HD4600, e.g. i3-43XX ??


 

Share this post


Link to post
Share on other sites
On 11/28/2018 at 1:17 AM, pprommelus said:

 


I use thermaltake core v1 and miniitx board and I have one PCIe slot in which I have a wifi adapter card. I would have to change the MOBO and case. then I could use the GPU. 

Maybe it would be good with another CPU? with HD4600, e.g. i3-43XX ??


 

 

Yeah...since that slot is already filled, and since this is a Mini-ITX board...not much you can do. That's one reason I hate Mini-ITX boards. You're just too limited. Full ATX is the best choice in my opinion. But yes, that also means more space taken by your computer. 

 

Also, it would have helped if the motherboard itself had built-in WiFi. But...unfortunately the ASUS H81i Plus does not. 

 

I'm using an i5-4570, supported OOB, with Intel Graphics HD 4600. And it does work in Mojave with only Inject Intel and ig-platform-id 0x0D220003. But...to advise you to buy another CPU just for this...would be madness.

 

If you want, a cheaper upgrade would probably be the motherboard itself. Take something with WiFI built-in so you don't waste the PCI slot with expansion cards. Like this H97N board form Gigabyte, for example. BUT keep in mind if you want wifi working on MacOS, you might wanna do a little bit of research and see if that chipset is supported or not. I've never had a WIFI-enabled motherboard. I'm not sure I need one for a Desktop computer... But if you really want WiFi and also a small chassis, that's another way to do it.

 

Another combo is indeed the motherboard and case, going Full/Standard ATX, or even Micro-ATX (2 PCI slots).

 

But my recommendation remains: you better get a dedicated GPU regardless which CPU are you using. Even if it's an older one (like the GTX 650 I mentioned before). As long as it's supported OOB, you're good to go. It's literally plug&play. No Inject Nvidia necessary, no Nvidia drivers necessary. It literally just works. And it will still perform better than any integrated GPU.

 

I don't know, you need to do your research, your calculations, see which possible combo works best for you. But...until then, this is not the topic for fixing that specific issue you're having. It is a Preview issue. But it's not this specific issue that this thread is meant to fix. Your Preview works fine in terms of opening photos. In the sense that it doesn't hang when doing that. The problem is somewhere else.

Edited by arsradu

Share this post


Link to post
Share on other sites

Hello,

 

Hackintosh noob, here!  I'm almost there with my first Hackintosh, and this is something that seems to not want to be fixed, hopefully you experts will know how! 

 

Hardware is:

 

8700k

Rog Strix Z390-i

Gigabyte RX560

970 Pro M.2

 

Running Mojave 10.14

 

My issue is that when I try to view images, the preview app tries to open the image and it just hangs there and has to be force quit.  So far, I have tried changing to 18,3 iMac, that seems to be the best fit all round, I have added the noVPAjpeg.kext and this had no effect at all.

 

Is there anything else I can do to fix this?  Thanks.

Share this post


Link to post
Share on other sites
Hello,
 
Hackintosh noob, here!  I'm almost there with my first Hackintosh, and this is something that seems to not want to be fixed, hopefully you experts will know how! 
 
Hardware is:
 
8700k
Rog Strix Z390-i
Gigabyte RX560
970 Pro M.2
 
Running Mojave 10.14
 
My issue is that when I try to view images, the preview app tries to open the image and it just hangs there and has to be force quit.  So far, I have tried changing to 18,3 iMac, that seems to be the best fit all round, I have added the noVPAjpeg.kext and this had no effect at all.
 
Is there anything else I can do to fix this?  Thanks.

Have you enabled iGPU?


Sent from my iPhone using Tapatalk

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 TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
    • By tonyx86
      This thread for installing Catalina on the Dell Latitude E6410 WITH NVIDIA GRAPHICS (BIOS A17, NVidia 3100m) will help you install a fresh installation of Catalina on your Dell Latitude E6410, it will help you upgrade from 10.15.2 to 10.15.3 (if you originally installed Catalina from this thread) and it will also help you upgrade from Mojave 10.14.6 if you have already installed Mojave by following the instructions here.  The instructions in this first post assume that you are installing Catalina in an APFS container.  If you are curious about the evolution of this solution and how sleep/wake was solved, review the Mojave installation thread.
       
      Important: This Thread is NOT intended to help you install macOS on a Latitude E6410 with Intel HD Graphics (without Nvidia graphics).  The DSDT attached to this first post (in E6410-Catalina.zip) is VERY SPECIFIC to the Nvidia graphics implementation and has not been edited for HD Graphics - there are elements required for HD Graphics that are missing from the attached DSDT and there are DSDT mods that have not been tested with HD Graphics.  Also, the kexts attached to this first post are specific to a Broadcom Wi-Fi card which must replace the original Intel Wi-Fi card.
       
      This first post will be modified to reflect lessons learned and to reflect the most current working state of my Latitude E6410 (with NVidia 3100m discrete graphics) running Catalina.  Issues, observations and performance tips are recorded toward the bottom of this first post.  My recommended CLOVER configuration is specified toward the bottom of this first post.
       
      *** If you want help with your installation, please post your issue along with problem reporting files generated using @black.dragon74's problem reporting tool.  Google 'GENERATE PROPER PROBLEM REPORTING FILES black.dragon74' to find it. ***.  If Catalina's Read-Only protections block your installation of black.dragon74's gen_debug script, please copy the attached gen_debug script to your Desktop, change script properties with the terminal command 'chmod a+x ~/Desktop/gen_debug' and run the script from your Desktop.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) Wi-Fi: Broadcom BCM 94352HMB (replaced original Wi-Fi card) BIOS (version A17) configured as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC:Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace:Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;   
      Versions of the software used in this installation are listed below the installation steps.  EFI and kexts for Catalina are attached to this first post in E6410-Catalina.zip.  CLOVER configuration is specified below the installation steps.
       
      Wi-Fi connection to an Access Point is delayed when using AppleALC for sound.  Do not use Apple ALC.  Use VoodooHDA pkg 2.9.2 v14 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
      Make sure that your system matches my system description above (including BIOS version, Wi-Fi card, BIOS settings) If performing an upgrade from Mojave or a previous version of Catalina, backup your Mojave or Catalina partition! (Carbon Copy or similar) Download Catalina Installer Download DosDude Catalina Patcher Use DosDude Patcher to create Catalina USB Installer Delete LegacyUSBInjector.kext (we're using @RehabMan's USBInjectAll.kext with custom SSDT) and delete SIPManager.kext (CLOVER is managing SIP) from Catalina USB Installer's /Library/Extensions folder Copy all but the FakeSMC sensor kexts in E6410-Catalina.zip (attached) LE folder to the Catalina USB Installer /Library/Extensions (copy all kexts (including FakeSMC.kext) but not the FakeSMC sensor kexts) Install CLOVER Bootloader (Legacy) on USB Installer using the EFI in the E6410-Catalina.zip (attached).  Use the CLOVER configuration specified below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Reset your Latitude E6410 NVRAM by doing the following (this may be important if you're making changes to your existing EFI and won't hurt anything if you're not making any changes) turn-off your laptop remove A/C power and main battery press and hold the power button for 30 seconds restore A/C power and battery Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 5-8. Select "Reinstall macOS" (note that I have existing installations of Mojave and High Sierra on my Latitude E6410, so it's possible that this menu item changes to "Install macOS" if you don't have any previous macOS installations). Select your Catalina destination partition (which will be your Mojave or previous Catalina partition if you are upgrading) After the Catalina Installer reboots the first time, boot from the "macOS Installer" partition on the disk that you selected as your Catalina destination (not the macOS installer on the USB) After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB Select the Post Install Patcher utility Select only the following Post Install Patches (no other patches / options) Install Patch Updater Legacy Video After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext If you are performing a fresh installation of Catalina: Install CLOVER on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Your EFI Clover/kexts/Other folder needs only FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext and VoodooPS2.kext.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Install all kexts in the attached E6410-Catalina.zip LE folder to your /Library/Extensions folder.  NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Copy HWMonitor from the application folder in the attached E6410-Catalina.zip to your Applications folder. Install VoodooHDA (I installed using the Classic method) Skip to Step 21 If you are upgrading from a previous version of Catalina using the instructions from this thread or from Mojave that you installed using the instructions here: Update Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /Library/Extensions) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Update IntelMausiEthernet.kext Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method) Ensure PROPER kext installation: If you're manually installing kexts in /Library/Extensions, make sure that you execute the following (in terminal) cd /Library/Extensions sudo chown -R root:wheel *.kext sudo chmod -R 755 *.kext sudo kextcache -i / After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your kext directory attributes are probably incorrect.  Repeat kext installation and try again. Reboot from your new/upgraded Catalina partition Welcome to macOS Catalina! Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type) Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys) Set hibernatemode: In terminal, execute sudo pmset -a hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo touch /var/vm/sleepimage sudo chflags schg /var/vm/sleepimage  
      Version Info at the time of this writing:
      Catalina Installer 10.15.3 CLOVER v2.5k r5103 DosDude Catalina Patcher: v1.3.0 Lilu.kext 1.4.1 AirportBrcmFixup.kext 2.0.6 BrcmFirmwareRepo.kext 2.5.1 BrcmBluetoothInjector.kext 2.5.1 BrcmPatchRAM3.kext 2.5.1 IntelMausiEthernet.kext 2.5.0
      VoodooHDA.kext 2.9.2 v14 (NOT AppleALC)
       
      What is not working (that was working in Mojave)
      SD Card Slot (had to remove VoodooSDHC.kext which caused system freeze on wake)  
      Known Issues and Their Solutions
      (No solution yet) Brightness slider does not work in System Preferences > Displays (can control brightness with Dell brightness keys).  Working on a solution later in this thread. I continue to refine the DSDT and CLOVER config.plist to optimize my Latitude E6410 for multi-booting between various macOS versions (High Sierra, Mojave and Catalina at the time of this writing). If you upgrade your Latitude E6410 EFI using my attached EFI, you may find that your Latitude E6410 is stuck in a boot-loop that ends in a white screen and reboots.  Clear your system by doing the following: turn off your laptop, remove A/C power, remove the main battery, press and hold the power button for 30 seconds, restore A/C power and battery, boot normally.  I have only found this to be necessary (very rarely) after making an EFI change, but you may find it helpful if making kext changes in /Library/Extensions as well. (Work-around - no permanent solution yet) Cannot turn on Bluetooth after shutting-down with Bluetooth off.  Work-around is to leave Bluetooth on.  I don't use Bluetooth and don't mind, so this will likely be solved by someone else.  If you experience this issue and can't turn-on Bluetooth, I have found that putting the laptop to sleep (Fn-F1) and then waking the laptop restores proper operation of Bluetooth.  I have posted a problem description, logs and problem reporting files in this thread for help with this problem. (Solved later in this thread, but not yet added to this first post) Laptop does not sleep when closing lid.  Solution is to implement Rehabman's lid polling mechanism.  This is implemented later in this thread and the laptop sleeps when the lid closes and wakes when the lid is opened. (No solution yet) No SD Card Slot (had to remove VoodooSDHC.kext) - I read somewhere that there is a solution that does not require any kexts (just a DSDT edit).  Haven't yet implemented this fix. (Not a problem that needs to be solved - leaving for historical purposes.  I am running Catalina without this.) - IOHWControl does not load under GFX0 (as observed in IORegistryExplorer).  Solution (if it needs to be solved) is to install AppleHWSensor.kext from a DosDude-patched Mojave /S/L/E in Catalina's /L/E.  Copy and install your own or use the kext attached to this post. (Solved - no further work required) Wi-Fi connection is delayed until a minute or so after boot - Use VoodooHDA and NOT AppleALC (Solved - no further work required) External USB ports do not work after waking from sleep (S3) - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Boot and shut-down time of Catalina is slower than Mojave - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Wi-Fi is not immediately available at OS startup - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Laptop freezes on wake - Remove VoodooSDHC.kext from /Library/Extensions  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z (I haven't noticed this issue for a while since I completed DSDT edits for Mojave, but keeping this here for historical purposes)  
      CLOVER Installation: Use these configuration options
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (legacy) booting Clover EFI 64-bits SATA BIOS Drivers, 64-bit Recommended drivers FSInject File System drivers ApfsDriverLoader Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane After clicking "Continue", if prompted with "This Clover package is incompatible with this version of macOS," install anyway  
      After CLOVER installation is complete Copy the following from the attached E6410-Catalina.zip ACPI patched contents config.plist (change XX-MASKED-XX values to your own) kexts/Other (remove all other kext folders) Remove christmas and new year folders from themes (if present)  
      Credits
      Thanks to those who contributed to my Mojave solution and to the DosDude team (for the incredible macOS patchers), I think this Catalina installation was the easiest macOS installation that I have experienced (so far).  Many thanks to @Slice and his team for the incredible work on CLOVER and for continuing to support old legacy systems like this.  Also, thanks to @Mieze and @headkaze and others I'm sure for maintaining the Brcm kexts.  And finally, I still prefer to manually apply patches to the DSDTs in my systems.  CLOVER offers extensive patching functionality, but I'm old-school and like to have an error-free, fully-patched DSDT with a simple CLOVER config.plist.  I think that this manual DSDT patching approach (which required an extensive review and debugging of the original unpatched DSDT in this thread) is the reason that this Latitude E6410 is such a perfect MacBookPro6,2.  Thank you @RehabMan for being a great teacher and for always insisting on problem reporting files .
       
       

      AppleHWSensor.kext.zip

      gen_debug
      E6410-Catalina-3v3.zip
    • By headkaze
      English: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md
      Russian: https://www.applelife.ru/threads/intel-hd-graphics-3000-4000-4400-4600-5000-5500-5600-520-530-630.1289648/
      Chinese: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.cn.md
    • By tonyx86
      *** I have started another thread for installing Catalina on the Dell Latitude E6410.  If you were thinking of installing Mojave, but would prefer to skip right to Catalina, click here. ***
       
      I was inspired by @duduclx post here for installing El Capitan on a Dell Latitude E6410, so I decided to install Mojave 10.14.5 and subsequently 10.14.6.  Everything works perfectly (including sleep).  I'm starting this thread hoping to help others install Mojave on their E6410s.  A brief installation guide is provided later in this first post.  The interested reader is encouraged to read the other posts in this thread to see how this solution evolved and to learn additional tips/details not provided in this first post (including dual-booting with macOS and Windows).
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) MacOS: Mojave 10.14.6 (APFS) (Patched with DosDude Mojave Patcher 1.3.3) MacModel: MacBookPro 6,2 (LPCB._DSM.Name "pci8086,3b09") Kexts: Lilu 1.3.6, VoodooHDA 2.9.2, AirportBrcmFixup 2.0.0, IntelMausiEthernet 2.4.1d1, ACPIBatteryManager 1.90.1, BrcmPatchRam2.kext, BrcmFirmwareRepo.kext, VoodooPS2Controller (the "Refined ALPS Touchpad" version - release 6 developed by @Dr. Hurt and compiled by @bronxteck), not the original version), USBInjectAll (with custom SSDT-UIAC), VoodooSDHC.kext (configured as shown here). Wi-Fi: Broadcom BCM 94352HMB (with AirportBrcmFixup.kext) CLOVER (Legacy): R4961  
      Configuration items that may be different from what you have seen in other E6410 configurations
      Addition of _OFF and _ON methods to _PTS and _WAK methods respectively (to control discrete graphics in order to enable sleep/wake) LPCB._DSM patched with device-id "3b09" AND "name", "pci8086,3b09" for native Nehalem power management with MacBookPro 6,2 ECDV renamed to EC so that AppleBusPowerController loads AGP.VID._DSM patched with device-id "0a29" so that AppleGraphicsPowerManagement loads No CLOVER Generate P or Generate C States (with the correct LPCB._DSM and MacBookPro 6,2, these CLOVER options are unnecessary for this architecture and only limit max multiplier and reduce number of P states) DSDT patched to include HDAU device (device-id 0x0be3)  
      What is NOT working:
      Display brightness can be controlled with keyboard keys, but cannot be controlled with slider in Display settings. Graphics Power Management - AGPM loads (because 10de,0a29 device is injected), but there's no evidence that 3100m frequency and voltage is changing.
        What is NOT tested:
      Smartcard Reader eSata (I have this disabled in my BIOS) Firewire Port (it does appear in the Network settings, just haven't tried it) Microphone Jack PC Card Slot (I have this disabled in my BIOS)  
      What IS working:
      SLEEP IS WORKING! Everything else not mentioned above.   Speedstep/CPUPowerManagement is perfect, system temps are low, CPU multiplier operates as expected, battery life is long Shutdown is fast Display/graphics acceleration is perfect (thanks to DosDude's Mojave patcher) Brightness (adjusted with brightness keys on keyboard) works perfectly Battery Manager works (battery status is displayed in menu bar) simply by installing ACPIBatterManager.kext. Wi-Fi (after changing to Broadcom BCM94352HMB and installing AirportBrcmFixup.kext) Audio (volume adjustable, volume indicator appears in menu bar).  Switched to VoodooHDA from AppleALC after AppleALC caused slow boot due to "IOHDACodecFunction timeout." Ethernet port (with IntelMausiEthernet.kext) Broadcom BCM20702A0 Bluetooth (with BrcmPatchRam2.kext and BrcmFirmwareRepo.kext) Optical Drive External VGA (with corrected NVCAP.  Need NVCAP 04000000 00000100 0E000000 00000007 00000000 (credit: here) for working external VGA display. Headphone jack Display Port (tested using DP > HDMI adapter) Camera SD Card Reader  
      Known issues and their solutions (These issues have all been resolved, with the solutions incorporated into the attached config files.  The issues are listed here for historical purposes and no further work is needed unless stated otherwise).
      Leaving this for historical purposes, but the CLOVER USBFix is no longer necessary after finding that I had incorrectly applied the DSDT _DSM patch for Device (EHC1).  The CLOVER USBFix is not needed after fixing the DSDT..  AAPL,clock-id and device_type do not appear in IORegistry for EHC1.  Solution is to use CLOVER on-the-fly patching/fixing/renaming for EHC1 and EHC2.  Thank you, @feartech, for this tip. ALPS trackpad performance is not good with the "standard" VoodooPS2Controller.kext that I initially used.  Switching to the "Refined ALPS TouchPad driver" is a big improvement.  I've implemented and tested this on my system.  The ALPS version of VoodooPS2Controller.kext mixes up a few keys.  Need to switch the Command and Option keys (System Preferences > Keyboard > Modifier Keys) and change keyboard type to ISO European. This configuration (captured in the attached config files) uses an injected device-id (10de,0a29) for NVidia 3100m to get AGPM to load.  While I haven't observed any performance differences, a better approach may be to inject AGPM properties for device 10de,0a6c (the actual device-id for the 3100m).  This AGPM method is discussed later in this thread.  I have briefly tested this "FakeSMC.kext method" for injecting AGPM attributes without any noticeable changes in laptop/graphics behavior. IOHWControl is not loaded under AGPM (Should be AGP > VID > NVDA,Display-A@0 > NVDATesla > AGPM > gpu-control > IOHWControl as viewed in IORegistryExplorer).  It is loaded on a real MacBookPro6,2 running Mojave and is loaded on this Dell Latitude E6410 running High Sierra.  If I "Inject NVidia" via CLOVER, IOHWControl loads properly. The Dell Latitude DSDT (BIOS A17) has a bug in Method (GNOT).  In the method, the expression  If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6))) always evaluates to TRUE, so the patched DSDT has no dependency on the value of OSYS.  I suspect that LOr should be replaced with LAnd, so that this expression is TRUE for variants of Windows 2001 and False for any other OS.  While this may have no affect on MacOS, it makes one wonder how such an obvious bug made it through Dell QA and is still present in BIOS A17.  Also makes one wonder whether the sleep problem (which no one has solved) was fixed in Windows to address another DSDT bug. The assigned value of ACOS and OSYS in the DSDT are conditional on the operating system.  There is no condition for "Darwin."  The solution is to add a condition for "Darwin" (making it equivalent to one of the defined operating systems (e.g. Linux, Win7, etc).  The attached config hard-codes ACOS and OSYS values equivalent to those for Linux.  Another way to handle this (different from the method employed in the attached config files) might be to override _OSI with XOSI (defined in a custom SSDT). The portType of the Internal Bluetooth device is portType=0 which, according to Rehabman's comments in SSDT-UIAC-All.dsl, is an external USB 2 port.  This should be an internal USB port (portType=2).  I learned through trial and error that the HUB1 and HUB2 definitions in Rehabman's SSDT-UIAC-ALL.dsl apply to the ports on the EHCx USB hubs.  The solution is to include the HUB1 definition in SSDT-UIAC.dsl and change portType to 2 for HP15.  This change doesn't appear to affect/fix sleep, but it may prevent instant wake if we get sleep working. There are minor differences between a real MacBookPro6,2 IORegistry dump and this HackBookPro6,2 IORegistry dump that can be resolved with simple DSDT edits.  I am now running with these changes, but haven't found these changes to make any difference in operational behavior.
      Rename Device (AC) -> Device (ADP1) Remove UID from Device (HPET) Add compatible ID "PNP0C01" to Device (HPET) Change ADP1:_STA from 0x0F to 0xFFFFFFFF Enable Ambient Light Sensor and renamed to Device (ALS0) from Device (ALS) Add compatible ID "smc-als" to ALS0 Rename LID -> LID0 Change "name" definitions to Buffers in _DSM methods Rename Device (PBTN) to PWRB Rename Device (SBTN) to (SLPB) Change HDAU.hda-gfx from "onboard-1" to "onboard-2" Change GFX0.hda-gfx from "onboard-1" to "onboard-2" Sleep / Wake does not work with the basic DSDT edits.  I have discovered that Sleep / Wake can be made to work by adding discrete graphics _OFF and _ON methods to _PTS and _WAK methods respectively (borrowed the concept and code from a working E6430 DSDT: Credit here: https://osxlatitude.com/forums/topic/9248-working-sleep-on-intel-hd-and-nvidia-nvs-on-dell-latitude-e6430-optimus-enabled-or-disabled/page/6/. The Clover boot arg should be changed to "darkwake=0" for reasons explained by @holyfield in this thread.  Leaving this for historical purposes: LCD screen is blank when waking laptop by opening lid (screen is not blank when waking with power button).  Solution is to add darkwake=8 to CLOVER boot args.  Thank you @Hervé for this tip.  
      Brief Installation Guide:
      Configure BIOS (version A17) as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC: Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace: Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;  Create your MacOS installer USB (Use DosDude's Mojave Patcher for Mojave) (start with High Sierra and not Mojave if you're new to hackintosh). Install CLOVER (Legacy) on installer USB using attached EFI as your guide for patched ACPI, kexts and config.plist Install MacOS to your SSD.  When you run DosDude's Mojave Patcher, DO NOT install LegacyUSBInjector.kext - you're going to use Rehabman's USBInjectAll.kext.  Also, do not install the DosDude SIP kext (you're using CLOVER to manage SIP). Install the following kexts in /Library/Extensions:  ACPIBatteryManager.kext, AirportBrcmFixup.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakeSMC.kext, FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_GPUSensors.kext, FakeSMC_LPCSensors.kext, IntelMausiEthernet.kext, Lilu.kext, USBInjectAll.kext, VoodooPS2Controller.kext (the "Refined ALPS Touchpad driver," not the original), VoodooSDHC.kext (configured as shown here). Switch Command and Option keys to compensate for Refined ALPS driver issue (System Preferences > Keyboard > Modifier Keys).  Also change keyboard type to ISO European to fix the [ ` ~ ] key (to the left of the "1" (one) key. Install VoodooHDA Install HWMonitor application  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z After applying Mojave updates, HWMonitor may not display discrete graphics attributes.  On systems with multiple displays, a second (or third display) may not be active after applying the Mojave update.  The solution to this is to run "sudo kextcache -i /" (in a terminal window) and reboot.  This will usually fix the issue.  If the issue is not fixed, run DosDude's Post Install Utility, apply the Legacy Graphics Patch, reboot and then run "sudo kextcache -i /" if necessary.  
      Credits
      In addition to those mentioned in this first post and in subsequent posts in this thread, much of this solution for the Latitude E6410 was made possible by the numerous contributions of @RehabMan.  I hope he's doing well, wherever he is.  Hopefully he has long since forgotten what a PIA I was (and still am) as I was (and still am) learning hackOS.  
       
       


      E6410-Mojave-6v2.zip
×