Jump to content
arsradu

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

331 posts in this topic

Recommended Posts

Advertisement
9 hours ago, jerryy2 said:

Did you do anything special when changing SMBIOS definitions to keep from having problems with Messages and / or FaceTime?

 

Well, you can keep the relevant serials for iMessage (MLB & ROM) in place, or get new ones for the new SMBIOS.

Edited by arsradu

Share this post


Link to post
Share on other sites
On 9/22/2018 at 2:22 AM, arsradu said:

 

Well, you can keep the relevant serials for iMessage (MLB & ROM) in place, or get new ones for the new SMBIOS.

 

Thank you.

Share this post


Link to post
Share on other sites
On 9/21/2018 at 5:03 PM, arsradu said:

 

Strange. This issue should not occur with the iGPU (and it didn't in my case). I know this is your first post, and I welcome you to this forum, but I'm gonna ask you to add your hardware information to your signature to see what we're dealing with. I can see you're using a Haswell system. But still, it would be nice to know a little more than that. :)

 

If your WhateverGreen kext is up to date (as it should be), you shouldn't need IntelGraphicsFixup kext anymore since it's already included into WEG. Could you try to remove it (or move it to Desktop, so you can put it back in case of anything) and try again?

 

About the config, I would strongly recommend you to always remove serial numbers from SMBIOS and RT Variables before uploading your config (or the entire EFI) for analysis.

 

Also, could you try iMac14,2 for once and see if it makes any difference? You can simply make a copy of your current config.plist, edit it, and rename the old one for iMac13,3 to configiMac13,3.plist or something, so you can access it from Clover GUI in case you need it (you can name it whatever you want, but it needs to contain the "config" part).

 

And could you please, check the option to Inject System ID in your config's System Parameters section?

879216540_ScreenShot2018-09-21at14_33_28.png.181605ccc7d899f35d6eb4ea185ec040.png

 

Otherwise, config looks ok.

Thank you for your response. 

 

I have tried your suggestions, removed IntelGraphicsFixup kext which I added just to experiment for the solution. Moreover, I tried changing SMBIOS to iMac14,2 and also Inject System ID but the problem is still there. 

 

I added my signature to give you more detail about my system. I have DP and VGA onboard on my system and the LCD is connected to Display Port. 

 

Thanks

Bhaggu

Share this post


Link to post
Share on other sites
43 minutes ago, bhaggu said:

Thank you for your response. 

 

I have tried your suggestions, removed IntelGraphicsFixup kext which I added just to experiment for the solution. Moreover, I tried changing SMBIOS to iMac14,2 and also Inject System ID but the problem is still there. 

 

I added my signature to give you more detail about my system. I have DP and VGA onboard on my system and the LCD is connected to Display Port. 

 

Thanks

Bhaggu

 

That motherboard is not looking good. I remember you said you don't use a dedicated graphics card, so, you can't switch to that, but can you share the video options you've got and their status (enabled/disabled etc) from your BIOS? Screenshots would be even better.

Config-wise, it looks good to me. So...I'm afraid all of this might go down to motherboard and BIOS.

 

I never liked these pre-built systems. They put all kinds of c**p in them.

Edited by arsradu

Share this post


Link to post
Share on other sites
On 9/24/2018 at 11:20 AM, arsradu said:

 

That motherboard is not looking good. I remember you said you don't use a dedicated graphics card, so, you can't switch to that, but can you share the video options you've got and their status (enabled/disabled etc) from your BIOS? Screenshots would be even better.

Config-wise, it looks good to me. So...I'm afraid all of this might go down to motherboard and BIOS.

 

I never liked these pre-built systems. They put all kinds of c**p in them.

 I have two option in Video Auto and Intel, I have tried both but no luck. 

 

EDIT: Updated to Final release but still same issue. :(

IMG_20180924_170828.jpg

Edited by bhaggu

Share this post


Link to post
Share on other sites

Thank you so much this is fixed my problem, preview was not responding

 

From the bios I enabled igpu then problem solved

 

i7 4770k mb:asus maximus vi extreme

Share this post


Link to post
Share on other sites

Hey all,

 

I've got this problem as well, and obviously would like to get it fixed. ...i gotta apologise up front, because I'm pretty new to the whole configuring clover stuff, so no nada about how to do anything really, except use clover config to mount EFI for me lol.

 

I'm on a Asus Maximus VIII (series 100 board), with i5-6600 and MSI ati vega 56 card

 

I've just done a fresh install of mojave following Maladon's guide on olaria - and right now using their standard clover package for 100 series boards from https://olarila.com/files/Clover.Folder/CLOVER.SERIES.100.200.300.zip

 

Right now all my hardware seems to be working ok, except it's not 100% as my PCI list in system info says I've got no PCI cards installed lol.

 

 

So is the best option to simply set my SMBIOS to match the closest apple machine by GPU (as the first post said) - which for me looks to be iMac Pro?

 

...and if so, how do you do that with CC?  (sorry I'm new, so don't know CC at all, and don't have a clue where/how to do it, or how to find out what string is right for that)

 

...or should I enable the iGPU?  (I've never used, I'm guessing my cpu has one lol)

 

 

thanks all - and sorry for the newbie questions!

 

 

 

Share this post


Link to post
Share on other sites
4 hours ago, yahbai said:

Hey all,

 

I've got this problem as well, and obviously would like to get it fixed. ...i gotta apologise up front, because I'm pretty new to the whole configuring clover stuff, so no nada about how to do anything really, except use clover config to mount EFI for me lol.

 

I'm on a Asus Maximus VIII (series 100 board), with i5-6600 and MSI ati vega 56 card

 

I've just done a fresh install of mojave following Maladon's guide on olaria - and right now using their standard clover package for 100 series boards from https://olarila.com/files/Clover.Folder/CLOVER.SERIES.100.200.300.zip

 

Right now all my hardware seems to be working ok, except it's not 100% as my PCI list in system info says I've got no PCI cards installed lol.

 

 

So is the best option to simply set my SMBIOS to match the closest apple machine by GPU (as the first post said) - which for me looks to be iMac Pro?

 

...and if so, how do you do that with CC?  (sorry I'm new, so don't know CC at all, and don't have a clue where/how to do it, or how to find out what string is right for that)

 

...or should I enable the iGPU?  (I've never used, I'm guessing my cpu has one lol)

 

 

thanks all - and sorry for the newbie questions!

 

 

 

Hey all - got this fixed.

 

In case anyone else with the same problem on a MSI Maximus VIII using and ATI video card (or likely any Maximus card):

 

The fix is to enable the integrated graphics in the bios (that's all).

 

- In the bios, go to the Advanced tab, then the System Agent Configuration, then Graphics Configuration

- then enable iGPU Multi-monitor (ie enable the iGPU)

- make sure that above that you still set the primary monitor to "PEG" (ie to use the video card as what's connected to the monitor).  you might be able to leave this as "auto", and have it detect which a monitor is connected to, but I didn't try that.

Share this post


Link to post
Share on other sites

@yahbai Hello and welcome to the forum.

 

For future posts, I would like to ask you a few things:

1. always read the first post of the thread before posting in that tread. I would also recommend that you read a few posts before yours just in case there's a new issue and other people are having it too.

2. don't quote your own post. :)). You can use the Edit button on the original post and add the missing/updated information.

3. add your hardware information to your signature. Believe me. It helps a lot.

Edited by arsradu

Share this post


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

@yahbai Hello and welcome to the forum.

 

For future posts, I would like to ask you a few things:

1. always read the first post of the thread before posting in that tread. I would also recommend that you read a few posts before yours just in case there's a new issue and other people are having it too.

2. don't quote your own post. :)). You can use the Edit button on the original post and add the missing/updated information.

3. add your hardware information to your signature. Believe me. It helps a lot.

will do!

Share this post


Link to post
Share on other sites

Hi guys, I followed the guide but something didn't work.

 

I see the 2 vga but still have problems with preview, and now it takes a loooong time to boot.

 

Can you help me?

 

My config MSI Tomahawk Z270, 7700k, R9 270X.

 

 

Schermata 2018-09-27 alle 12.46.45.png

config.plist

Edited by daeron666

Share this post


Link to post
Share on other sites
25 minutes ago, daeron666 said:

Hi guys, I followed the guide but something didn't work.

 

I see the 2 vga but still have problems with preview, and now it takes a loooong time to boot.

 

Can you help me?

 

My config MSI Tomahawk Z270, 7700k, R9 270X.

 

 

Schermata 2018-09-27 alle 12.46.45.png

 

 

I'm not an expert in AMD cards... Maybe @Cyberdevs can have a better insight on that. BUT I'm not sure you're supposed to inject both Intel and ATI in your config. Also, please, remove the serial numbers in SMBIOS and RT Variables when uploading a config.plist for analysis.

 

Also, which method did you try? I think you need to try the alternative medicine one. :)) 

 

For MSI motherboards (I've got one...so there might be some similarities)...I think you should have an option to switch from PEG to IGD in BIOS, under Advanced Settings or something like that (I'm not on my computer right now, so don't know for sure). You should probably try both (probably IGD first), while being connected to the dedicated GPU (the R9 card).

 

It was already confirmed to work, and your motherboard seems mainstream enough, so it should be fixable. :)

Edited by arsradu

Share this post


Link to post
Share on other sites
17 minutes ago, daeron666 said:

Hi guys, I followed the guide but something didn't work.

 

I see the 2 vga but still have problems with preview, and now it takes a loooong time to boot.

 

Can you help me?

 

My config MSI Tomahawk Z270, 7700k, R9 270X.

config.plist

You see two GPUs because you inject both AMD and Intel GPUs in your config.plist you don't need to inject any of them, Mojave will detect the iGPU automatically and the R9 270x doesn't need to be injected as well.

 

Remove all those injections and try again, make sure that you have a working backup of your existing EFI before making any changes to your current setting.

Share this post


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

You see two GPUs because you inject both AMD and Intel GPUs in your config.plist you don't need to inject any of them, Mojave will detect the iGPU automatically and the R9 270x doesn't need to be injected as well.

 

Remove all those injections and try again, make sure that you have a working backup of your existing EFI before making any changes to your current setting.

 

Damn, that was some fast summoning. :))) Many, many thanks for your feedback! This thread just wouldn't be the same without it.

Share this post


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

Damn, that was some fast summoning. :))) Many, many thanks for your feedback! This thread just wouldn't be the same without it.

Actually I was typing my response at the same time as you posted yours :D

Thanks to you my friend for creating this topic in the first place which is going to help lots of people specially now that the Mojave is released :thumbsup_anim:

 

Cheers mate :)

Share this post


Link to post
Share on other sites
14 minutes ago, Cyberdevs said:

You see two GPUs because you inject both AMD and Intel GPUs in your config.plist you don't need to inject any of them, Mojave will detect the iGPU automatically and the R9 270x doesn't need to be injected as well.

 

Remove all those injections and try again, make sure that you have a working backup of your existing EFI before making any changes to your current setting.

 

Don't get it. Your guide on the first page says; InjectIntel+ig-platform-id. I am using this guide since beta1 is this method changed?

 

But I didnt inject ATI just injectIntel+ig-platform-id and IGPU activated on BIOS primary is discrete GPU.

Edited by telepati

Share this post


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

Don't get it. Your guide on the first page says; InjectIntel+ig-platform-id is these changed?

If using those instructions isn't gonna result in a desired out come we can change the setting to see if that helps with the problem.

With the new versions of macOS Mojave the need for injection ig-platform-id is not needed anymore because macOS detects the iGPU automatically.

 

And for R9 270X has native support in Mac OS X and macOS and there's no need to inject the related settings. Just to clarify thing a little bit more when I discovered this workaround I was testing the early versions of macOS Mojave and a lot has changed since.

Share this post


Link to post
Share on other sites

Another addition:

When you use InjectIntel+ig-platform-id macOS will detect the iGPU as Intel HD 530/630 etc. (on Skylake/KabyLake and so fort with other Intel integrated GPUs) and if we don't inject the Intel related values macOS will load the default framebuffer for those GPUs

Share this post


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

 

I'm not an expert in AMD cards... Maybe @Cyberdevs can have a better insight on that. BUT I'm not sure you're supposed to inject both Intel and ATI in your config. Also, please, remove the serial numbers in SMBIOS and RT Variables when uploading a config.plist for analysis.

 

Also, which method did you try? I think you need to try the alternative medicine one. :)) 

 

For MSI motherboards (I've got one...so there might be some similarities)...I think you should have an option to switch from PEG to IGD in BIOS, under Advanced Settings or something like that (I'm not on my computer right now, so don't know for sure). You should probably try both (probably IGD first), while being connected to the dedicated GPU (the R9 card).

 

It was already confirmed to work, and your motherboard seems mainstream enough, so it should be fixable. :)

I tried but nothing changed. 

Share this post


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

If using those instructions isn't gonna result in a desired out come we can change the setting to see if that helps with the problem.

With the new versions of macOS Mojave the need for injection ig-platform-id is not needed anymore because macOS detects the iGPU automatically.

5

 

I didn't know that.

 

58 minutes ago, Cyberdevs said:

Another addition:

When you use InjectIntel+ig-platform-id macOS will detect the iGPU as Intel HD 530/630 etc. (on Skylake/KabyLake and so fort with other Intel integrated GPUs) and if we don't inject the Intel related values macOS will load the default framebuffer for those GPUs

 

Then no need to injectIntel and adding ig-platform-id, just activate IGPU and set to primary discrete card will solve the preview problem? 

 

Edit: I test it and it worked. I removed InjectIntel and ig-platform-id from config.plist. Preview working and SKL looks loaded.

 

1863470359_ScreenShot2018-09-27at15_35_53.png.3ff3a3584f7f722099fc043ff706e68c.png

 

Edited by telepati

Share this post


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

You see two GPUs because you inject both AMD and Intel GPUs in your config.plist you don't need to inject any of them, Mojave will detect the iGPU automatically and the R9 270x doesn't need to be injected as well.

 

Remove all those injections and try again, make sure that you have a working backup of your existing EFI before making any changes to your current setting.

I tried but nothing changed.

Otherwise it recognize as AMD Radeon HD 7xxx (even with inject ATI).

 

Please help me....

 

Added new modified config.plist

config.plist

Edited by daeron666

Share this post


Link to post
Share on other sites

Hi,

 

Here is my config :

MB Asus P8P67 Pro rev 3.1 without iGPU.

GPU is a Nvidia GT710 (A GT210 by the past, before Mojave).

Clover 4674.

I'm experiencing the same "JPG quick look issue".

Everything else works perfectly with this configuration that I've always used since OSX Lion (except for the recently installed GT710 for Mojave).

 

I never used Lilu and Watevergreen. Just installed this 2 kexts but still the problem. Is there particulars parameters to use with them ?379955718_Capturedcran2018-09-2715_09_46.png.e1be78c79944161609aeae196a8cbd59.png

config.plist

Edited by d.o.n.g.h.w.a.n

Share this post


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

I tried but nothing changed.

Otherwise it recognize as AMD Radeon HD 7xxx (even with inject ATI).

 

Please help me....

 

Added new modified config.plist

config.plist

Changing the AMD Radeon HD 7xxx to AMD Radeon HD 270X is cosmetic it has no effect on the performance, there are several fixes for that and the easies one is to use WhateverGreen+lilu. It will help macOS to detect the correct framebuffer for your AMD GPU and it also fixes the incorrect AMD GPU detection along with the fix for the preview and quick look.

 

You can also use the clover's Kernel and Kext Patches to fix 7xxx . What I suggest is to trying to fix the preview and quick look issue first and once it's fixed we can fix other issues.

 

 

Share this post


Link to post
Share on other sites

Now preview works, but I see only radeon hd 7xxx.

 

For best performance should I see the hd630 too? 

 

I see on cinebench now my score is 110, with high sierra it was 130...

Edited by daeron666

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.

Announcements

  • Similar Content

    • By ronaldduck
      Yesterday I was finally able to boot and install hackintosh on my pc but after the installation my hackintosh system won't able to detect my graphics card properly even NvidiaWeb drivers are installed(English isn't my main language)
      My Current EFI

      Kernel panic log:
      Bdmesg output:
      My system properties:
      Btw Gtx 1660 Super doesn't have any vga output.
    • By writyper
      I had an (almost) perfectly working hack, but then at some point I found mp4 files preview in Finder no longer works. It just rolls a circle but won't start. Other file types are not affected.
      Last changes I made before it broke were installing FCPX + Compressor + Pro Video Formats and then Xcode.
       
      I tried different troubleshooting tips but nothing worked. My backup 10.13 system still work just fine with the same EFI.
       
      This is an output I get in terminal:
       
       qlmanage -p /Volumes/RAID/Video/_Export/video.mp4 
       
      Testing Quick Look preview with files:
          /Volumes/RAID/Video/_Export/video.mp4
      objc[821]: Class QLMediaTranscoding is implemented in both /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Music.qldisplay/Contents/MacOS/Music (0x10e0c80c0) and /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Movie.qldisplay/Contents/MacOS/Movie (0x10e0fa110). One of the two will be used. Which one is undefined.
       
      objc[821]: Class QLMediaExportWindowController is implemented in both /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Music.qldisplay/Contents/MacOS/Music (0x10e0c8110) and /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/PlugIns/Movie.qldisplay/Contents/MacOS/Movie (0x10e0fa250). One of the two will be used. Which one is undefined.
       
      Anyone knows how to fix that ?
    • 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.x (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.  You MUST BE LOGGED-IN to download attachments from this forum.
       
      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 v15 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
       
      If you want to upgrade to 10.15.6, see instructions at this post.
       
      If you want to upgrade to 10.15.5, see instructions at this post.
       
      If you want to upgrade to 10.15.4, see instructions at this post.  
       
      Follow instructions below for 10.15.2 and 10.15.3.
       
      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 (LEGACY - NOT UEFI) on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  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. 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: Replace 3rd-party kexts in EFI/Clover/kexts/Other with those in the attached EFI folder.   Replace EFI/Clover config.plist with the attached config.plist (Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values) Replace EFI/Clover/ACPI/patched with the files in the attached EFI/Clover/ACPI/patched Replace 3rd-party kexts in /Library/Extensions with those in the attached LE folder Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method for Catalina) 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.6 CLOVER r5119 DosDude Catalina Patcher: v1.4.4 Lilu.kext 1.4.5 AirportBrcmFixup.kext 2.0.7 (not yet included in the attached E6410-Catalina.zip archive.  Get latest version here) BrcmFirmwareData.kext 2.5.3 BrcmBluetoothInjector.kext 2.5.3 BrcmPatchRAM3.kext 2.5.3 IntelMausi.kext 1.0.3 (Not IntelMausiEthernet.kext)
      EFICheckDisabler.kext 0.5
      VoodooHDA.kext 2.9.2 v15 (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
      (Not yet included in E6410-Catalina.zip archive attached to Post #1) There is a new version (2.0.7) of AirportBrcmFixup.kext here.  I hadn't noticed any issues with version 2.0.6, so this updated kext will be included in a future update to the E6410-Catalina.zip archive attached to this first post. (Solved - no further work required) Clover r5118 requires the config.plist key <key>NoDefaultProperties</key><false> to permit macOS to boot with Clover's "Inject Nvidia" = True.  See details here.  config.plist in the attached E6410-Catalina.zip archive includes this change. (Solved - no further work required) EFICheck is loaded.  Solution is to install EFICheckDisabler.kext which you can get here.  EFICheck.kext is included in the attached E6410-Catalina.zip archive. (Solved - no further work required) Some users experience display issues.  The solution is to remove Device (PNLF) from the DSDT.  Use the attached DSDT.  Removal of PNLF will disable sleep on lid closure.  Device (PNLF) can be added without modifying the DSDT by enabling the Clover PNLF ACPI patch.  The attached Clover config.plist enables the PNLF DSDT patch.  Disable the Clover PNLF patch if you experience display issues. (Solved - no further work required) USB sleep/wake power IORegistry keys are not injected (not included in Mojave's or Catalina's IOUSBHostFamily.kext).  Solution is to added SSDT-USBX.aml to EFI/CLOVER/ACPI/patched.  The attached SSDT-USBX.aml includes USB sleep/wake properties for MacBookPro6,2 from High Sierra 10.13.6 IOUSBHostFamily.kext. (No solution yet) Brightness slider does not work in System Preferences > Displays.  Brightness is easily controlled with Dell brightness keys.  There is some work on this later in this thread, but I will not be solving this as I'm content with the Dell brightness keys (and Ambient Light Sensor works to auto-adjust brightness). (No intention to solve) Display Settings in System Preferences are "garbled" when bright slider is visible.  This is a known issue with the legacy graphics patch and does not affect laptop operation. 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. (Solved - no further work required) Brcm firmware does not update when using BrcmFirmwareRepo.kext in /Library/Extensions.  Solution is to install BrcmFirmwareData.kext and BrcmPatchRAM3.kext in E/C/k/O with Clover "Inject Kexts" = YES. (Solved - no further work required) Laptop does not sleep when closing lid.  Solution appears to be a combination of adding Notify (LID0) code to Method (BTNV) and adding Device (PNLF) in the DSDT. I am using the same EFI for High Sierra 10.13.6, Mojave 10.14.6 and Catalina 10.15.3 and it works in all three macOSes. (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 (These configuration options configure Clover for LEGACY BIOS - NOT UEFI)
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (LEGACY - NOT UEFI) 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)  
      Screenshots
       
      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-5v2.zip
    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive.  Edit: Recommend 16GB or larger for macOS Catalina 10.16 Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.6_18G103
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
      Updated Download Links for macOS Catalina 10.15.6_19G73
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.6.zip
      InstallInfo.plist_edited_10.15.6.zip
    • By rawmassen
      Hi there,
       
      If anyone could help I'd be very grateful, I'm trying to move from Clover to OC but have hit a brick wall for the last 2 days.
       
      It's an ACPI table error: SB_.PCIO.XHC_RHUB.HS11, Namespace lookup failure.
       


      Skylake Build:
      OpenCore 0.5.9
      Mojave 10.14.6, iMac17,1
      Asus Maximus Hero VIII
      6700K
       
      I've attached the config.plist and ACPI folder.
       
      EFI Drivers: OpenRuntime.efi and HfsPlus.efi
      Kexts: IntelMausi, Lilu, VirtualSMC, Whatevergreen
       
      Things I've tried...
       
      1) Clearing NVRAM (as it was previously booted by Clover)
       
      2) Hackintool USB Mapping: both the SSDT files and the USBPorts.kext
       
      3) USBInjectAll.kext (with and without SSDT files)
       
      4) SSDT-RHUB.aml. This seems to be directly involved, spent a long time with this but with no luck.
       
      I followed this guide:
       
      https://dortania.github.io/Getting-Started-With-ACPI/Universal/rhub-methods/manual.html
       
      Everything is XHC in my DSDT, except these definitions at the top (line 72 and 73):
       
          External (_SB_.PCI0.XHC_.DUAM, MethodObj)    // Warning: Unknown method, guessing 0 arguments     External (_SB_.PCI0.XHC_.RHUB.INIR, MethodObj)    // Warning: Unknown method, guessing 0 arguments  
      So I edited the SSDT-RHUB.dsl to this:
       
      /* * Goal of this SSDT is to shut off the RHUB to force macOS into * manually building ports when the ACPI is screwed up */ DefinitionBlock ("", "SSDT", 2, "DRTNIA", "RhubOff", 0x00001000) { External (_SB_.PCI0.XHC.RHUB, DeviceObj) // Full pathing to RHUB, change to yours Scope (_SB.PCI0.XHC.RHUB) // Full pathing to RHUB, change to yours { Method (_STA, 0, NotSerialized) { If (_OSI ("Darwin")) { Return (Zero) // This disables the device only in macOS } Else { } } } } Which results in this AML version:
      DefinitionBlock ("", "SSDT", 2, "DRTNIA", "RhubOff", 0x00001000) { External (_SB_.PCI0.XHC_.RHUB, DeviceObj) Scope (_SB.PCI0.XHC.RHUB) { Method (_STA, 0, NotSerialized) // _STA: Status { If (_OSI ("Darwin")) { Return (Zero) } Else { } } } } But I get the same error. 
       
      I'm at a complete loss, can anyone help?
       
       
      config.plist
      ACPI.zip
×