Jump to content
arsradu

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

326 posts in this topic

Recommended Posts

36 minutes ago, SavageAUS said:

If i have my iGPU enabled to fix this issue should it show up in system info? I can't remember.

Screen Shot 2018-12-19 at 9.34.30 pm.png

 

It does in my case. :) But it also depends which SMBIOS are you using.

 

If you went the iMacPro/MacPro route to fix this, since those don't have iGPUs, they will also not display it in that section. If you went with something like the iMac14,2 which does have an iGPU, it should show up here, if everything is properly set up in Clover config.

Share this post


Link to post
Share on other sites
Advertisement
 
It does in my case.  But it also depends which SMBIOS are you using.
 
If you went the iMacPro/MacPro route to fix this, since those don't have iGPUs, they will also not display it in that section. If you went with something like the iMac14,2 which does have an iGPU, it should show up here, if everything is properly set up in Clover config.

Yeah everything is setup properly and ummm using imac17,1


Sent from my iPhone using Tapatalk

Share this post


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


Yeah everything is setup properly and ummm using imac17,1


Sent from my iPhone using Tapatalk

 

Can you upload the config (without the private stuff)? I can take a look, if you want.

 

Anyway, this is just a cosmetic issue. I will also check my personal setup when I get home. Maybe I'm wrong and maybe it doesn't show up in my case, either. But I remember seeing it there... 

 

Anyway, for as far as I remember, you need InjectIntel and the correct ig-platform-id, in order for the iGPU to show up there. Also, I think you might need WEG kext, as well. Not sure about that though. Since I think WEG is trying to force a specific ig-platform-id on its own. So..might not be related.

 

But you do need to set up InjectIntel and ig-platform-id in your config.

 

EDIT:

 

@SavageAUS Looks like it is properly displayed in my case. :) So...yeah, I'd say probably the config needs a bit more tweaking.

 

696798399_Screenshot2018-12-19at23_09_06.thumb.png.8236f27c9579dfe99a144b76be5a0b5c.png

1965952847_Screenshot2018-12-19at23_09_14.thumb.png.133796af0910cb356cf08f7627f1f8d8.png

Edited by arsradu

Share this post


Link to post
Share on other sites
 
Can you upload the config (without the private stuff)? I can take a look, if you want.
 
Anyway, this is just a cosmetic issue. I will also check my personal setup when I get home. Maybe I'm wrong and maybe it doesn't show up in my case, either. But I remember seeing it there... 
 
Anyway, for as far as I remember, you need InjectIntel and the correct ig-platform-id, in order for the iGPU to show up there. Also, I think you might need WEG kext, as well. Not sure about that though. Since I think WEG is trying to force a specific ig-platform-id on its own. So..might not be related.
 
But you do need to set up InjectIntel and ig-platform-id in your config.
 
EDIT:
 
[mention=1083558]SavageAUS[/mention] Looks like it is properly displayed in my case.  So...yeah, I'd say probably the config needs a bit more tweaking.
 
696798399_Screenshot2018-12-19at23_09_06.thumb.png.8236f27c9579dfe99a144b76be5a0b5c.png
1965952847_Screenshot2018-12-19at23_09_14.thumb.png.133796af0910cb356cf08f7627f1f8d8.png

I don’t use ig-platform-id or inject intel because I went down the “devices” path with Whatevergreen, but I do have the correct device id set for that. Take a look at intel framebuffer patching with Whatevergreen topic. I do remember seeing it there previously but I reset my bios to try and fix time issues and now it’s gone so maybe I’ll recheck bios settings.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Then maybe all you need is Inject Intel...? I don't know. I'm just saying.

 

I've never tried that method before. But in my experience, if you're only using WEG, it will not get you that iGPU information there. Of course, our hardwares are different and as you said above, you tried a slightly different approach with this. So...results might be different, as well. default_smile.png

 

 

 

 

Share this post


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

Then maybe all you need is Inject Intel...? I don't know. I'm just saying.

 

I've never tried that method before. But in my experience, if you're only using WEG, it will not get you that iGPU information there. Of course, our hardwares are different and as you said above, you tried a slightly different approach with this. So...results might be different, as well. default_smile.png

 

 

 

 

This is my config. Quicklook and preview both work.

config.plist

Screen Shot 2018-12-20 at 2.23.07 pm.png

Hardware_Info_V2018-11-13.zip

Edited by SavageAUS

Share this post


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

This is my config. Quicklook and preview both work.

config.plist

Screen Shot 2018-12-20 at 2.23.07 pm.png

Hardware_Info_V2018-11-13.zip


 

Not sure what you meant by Devices....cause I couldn't find any specific FakeID set there.

Screenshot_2018-12-20_at_12_48_53.thumb.png.86a1ad3f14210a410f4c0e904c4b57af.png

 

Anyway, I managed to get it working on a Skylake build, as well. Motherboard: GA-Z170-Gaming K3, CPU: 6600K, iGPU: Intel Graphics HD 530, dGPU: GTX 650 OC 2GB. iMac17,1 SMBIOS.

 

In BIOS, I set these things:

  1. Peripherals -> Initial Display Output -> iGFX
  2. Chipset -> Internal Graphics -> Enabled
         DVMT Pre-Allocation -> default 64M.
         DVMT Total Gfx Mem -> default 256M
  3. Save
  4. Reboot

In Clover config, I set these things:

101152012_Screenshot2018-12-20at12_45_27.thumb.png.57260e76c6d52e732c852e2cbfaac447.png

 

Aaaand....TA-DAAA!

 

I'll let you judge the result for yourself. :)

 

Screenshot_2018-12-20_at_12_41_52.png.fc92e1c54948a191becccd7bbef9f677.png

 

Oh, forgot to mention: QuickLook and Preview work, as well.

Edited by arsradu

Share this post


Link to post
Share on other sites

 
Not sure what you meant by Devices....cause I couldn't find any specific FakeID set there.
Screenshot_2018-12-20_at_12_48_53.thumb.png.86a1ad3f14210a410f4c0e904c4b57af.png
 
Anyway, I managed to get it working on a Skylake build, as well. Motherboard: GA-Z170-Gaming K3, CPU: 6600K, iGPU: Intel Graphics HD 530, dGPU: GTX 650 OC 2GB. iMac17,1 SMBIOS.
 
In BIOS, I set these things:
  1. Peripherals -> Initial Display Output -> iGFX
  2. Chipset -> Internal Graphics -> Enabled
         DVMT Pre-Allocation -> default 64M.
         DVMT Total Gfx Mem -> default 256M
  3. Save
  4. Reboot

In Clover config, I set these things:

101152012_Screenshot2018-12-20at12_45_27.thumb.png.57260e76c6d52e732c852e2cbfaac447.png

 

Aaaand....TA-DAAA!

 

I'll let you judge the result for yourself.

 

Screenshot_2018-12-20_at_12_41_52.png.fc92e1c54948a191becccd7bbef9f677.png

 

Oh, forgot to mention: QuickLook and Preview work, as well.


On that screenshot you posted of devices you have arbitrary highlighted at the bottom, if you select properties you will see where it’s set.


Sent from my iPhone using Tapatalk

Share this post


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


On that screenshot you posted of devices you have arbitrary highlighted at the bottom, if you select properties you will see where it’s set.


Sent from my iPhone using Tapatalk

 

You mean this?

If so, I don't know... Never used this method before. But...doesn't seem to work for what you're trying to accomplish.

 

1054541528_Screenshot2018-12-20at23_24_00.thumb.png.845d7ab2ff1fc590a7ad281d60ce163d.png

 

Also, I think I'm probably missing something here, but isn't Layout ID used for analog audio...? What does that have to do with the iGPU?

 

Anyway... You have an alternative method in my previous post, which I'm pretty sure it will work since both builds are using the exact same iGPU, if you wanna give it a try. :) I'd love to hear your results.

 

Edited by arsradu

Share this post


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

 

You mean this?

If so, I don't know... Never used this method before. But...doesn't seem to work for what you're trying to accomplish.

 

1054541528_Screenshot2018-12-20at23_24_00.thumb.png.845d7ab2ff1fc590a7ad281d60ce163d.png

 

Also, I think I'm probably missing something here, but isn't Layout ID used for analog audio...? What does that have to do with the iGPU?

 

Anyway... You have an alternative method in my previous post, which I'm pretty sure it will work since both builds are using the exact same iGPU, if you wanna give it a try. :) I'd love to hear your results.

 

This one is Audio yes

 613552665_ScreenShot2018-12-21at8_08_44am.png.b313e95460da56afc200ccf1e7670cbb.png

But this one is iGPU

256349958_ScreenShot2018-12-21at8_08_39am.png.b7e5218c8312a54e82fb9bbd868868cb.png

Wait, i see the problem, spelling mistake in platform.

Edited by SavageAUS

Share this post


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

This one is Audio yes

 613552665_ScreenShot2018-12-21at8_08_44am.png.b313e95460da56afc200ccf1e7670cbb.png

But this one is iGPU

256349958_ScreenShot2018-12-21at8_08_39am.png.b7e5218c8312a54e82fb9bbd868868cb.png

 

Well, might be a typo there...?

 

Should be ig-platform-id instead of ig-platford-id...?

Edited by arsradu

Share this post


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

 

Well, might be a typo there...?

 

ig-platford-id instead of ig-platform-id...?

Just fixed it and it still isn't showing up in system report.

Doesn't matter, it's working.

Screen Shot 2018-12-21 at 8.18.55 am.png

Screen Shot 2018-12-21 at 8.19.30 am.png

Screen Shot 2018-12-21 at 8.20.19 am.png

Share this post


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

Just fixed it and it still isn't showing up in system report.

Doesn't matter, it's working.

Screen Shot 2018-12-21 at 8.18.55 am.png

Screen Shot 2018-12-21 at 8.19.30 am.png

Screen Shot 2018-12-21 at 8.20.19 am.png

 

As I mentioned before, you might want to add Inject Intel, as well, to your Clover config. In my experience, it will not show up without it. :) 

 

Anyway, I'm glad it works. :) 

Share this post


Link to post
Share on other sites
 
As I mentioned before, you might want to add Inject Intel, as well, to your Clover config. In my experience, it will not show up without it.  
 
Anyway, I'm glad it works.  

Yeah I’ll give it a try after work but the framebuffer guide says to make sure you have that unchecked.


Sent from my iPhone using Tapatalk

Share this post


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


Yeah I’ll give it a try after work but the framebuffer guide says to make sure you have that unchecked.


Sent from my iPhone using Tapatalk

 

I see....well...as you could see in my screenshots above, on the same iGPU, it showed up properly, I had no issues with it...so...not sure what to say :))) 

 

I guess there's only one way to find out. Anyway...this is a small cosmetic issue. And of course, anyone would choose performance over it. But I just didn't happen to notice any issues in my tests today. So...personally I'd suggest giving it a try. If it works, YEY. If it doesn't, well, explore other options. :)) But my experience with it today was good so...I think you should be fine. :) 

Edited by arsradu

Share this post


Link to post
Share on other sites

First off, wanted to thank everyone for the plethora of info on this thread. I was having the same issue where Quicklook / Preview did not work with JPEG files. I was not able to successfully enable IGPU in BIOS but the NoVPAJpeg Kext fixed it right up.  

 

On another thread people with the same MOBO as me were able to enable IGPU in BIOS without any issues however when I enable IGPU in BIOS, my boot hangs at "Start ReadKernalCache" (screenshot attached). Was wonder if anyone here had any suggestions. I'm happy that my system is working 100% now but the troubleshooter in me is still curious about that IGPU BIOS snag. We tried all sorts of fixes to get IGPU working like fresh installs, various kexts, various SSDT's, rebuilding cache, etc. Figured I'd ask here and see if anyone had any fresh ideas.

System:

Vanilla Mojave 10.14.2
Intel i9-9900K
Gigabyte Z390 Designare MOBO - BIOS F4
Sapphire RX 580 Pulse
Corsair Vengeance LPX 32 GB DDR4-3200 RAM
Samsung 970 EVO 500 GB M.2 SSD (Main OS Drive)
Samsung 860 EVO 2 TB M.2 SSD

 

Thanks! 

IMG_5921.jpg

Share this post


Link to post
Share on other sites
On 12/28/2018 at 3:59 AM, NoiseCoalition said:

First off, wanted to thank everyone for the plethora of info on this thread. I was having the same issue where Quicklook / Preview did not work with JPEG files. I was not able to successfully enable IGPU in BIOS but the NoVPAJpeg Kext fixed it right up.  

 

On another thread people with the same MOBO as me were able to enable IGPU in BIOS without any issues however when I enable IGPU in BIOS, my boot hangs at "Start ReadKernalCache" (screenshot attached). Was wonder if anyone here had any suggestions. I'm happy that my system is working 100% now but the troubleshooter in me is still curious about that IGPU BIOS snag. We tried all sorts of fixes to get IGPU working like fresh installs, various kexts, various SSDT's, rebuilding cache, etc. Figured I'd ask here and see if anyone had any fresh ideas.

System:

Vanilla Mojave 10.14.2
Intel i9-9900K
Gigabyte Z390 Designare MOBO - BIOS F4
Sapphire RX 580 Pulse
Corsair Vengeance LPX 32 GB DDR4-3200 RAM
Samsung 970 EVO 500 GB M.2 SSD (Main OS Drive)
Samsung 860 EVO 2 TB M.2 SSD

 

Thanks!

 

Hmm...never seen that before. BUT I'm thinking the config.plist might bring some light into this.

 

So, if you could, I'd say remove the serials from SMBIOS and RT Variables sections and upload your config.plist here for analysis (you might need to zip it).

 

For Gigabyte motherboards, you should follow the instructions posted on the first page to enable the iGPU. That's on the BIOS side. But you still need to set up your Clover config file. I feel like the issue might be caused by some misconfigured parameters in there.

 

So, as you wish. :) You can keep it this way and enjoy your system. Ooor...you can clean up the sensitive information from the sections I mentioned above (SMBIOS and RT Variables) and post the config.plist file to take a look.

Edited by arsradu

Share this post


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

Do people still using this on 10.14.3?

 

Use what? I still have this issue :D:wallbash:

Share this post


Link to post
Share on other sites

Thanks so much, had this problem for a couple months and all i did was download the Lilu file and put it in my efi folder as instructed and restarted and it worked!

Share this post


Link to post
Share on other sites
On 3/7/2019 at 6:35 PM, unixb0y said:

 

Use what? I still have this issue :D:wallbash:

 

Which method did you choose to fix this issue? The iGPU needs to be enabled in BIOS. Unless you're using a MacPro or iMacPro SMBIOS.

Share this post


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

 

Which method did you choose to fix this issue? The iGPU needs to be enabled in BIOS. Unless you're using a MacPro or iMacPro SMBIOS.

 

Hey bro, I wanted to mention that I switched my SMBIOS to iMacPro and it instantly worked. My boot process takes minutes if I activate the iGPU so that's not an option for me :lol:

Share this post


Link to post
Share on other sites
3 minutes ago, unixb0y said:

 

Hey bro, I wanted to mention that I switched my SMBIOS to iMacPro and it instantly worked. My boot process takes minutes if I activate the iGPU so that's not an option for me :lol:

Hmm...that's weird... You probably have other things, as well...that drag the boot down. Such as Clover may be set to Debug. Which will make the boot up process really slow (that part is normal, though). So...you could check that.

 

But either way,  I'm glad you fixed it by changing SMBIOS. :) 

Edited by arsradu

Share this post


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

Hmm...that's weird... You probably have other things, as well...that drag the boot down. Such as Clover may be set to Debug. Which will make the boot up process really slow (that part is normal, though). So...you could check that.

 

But either way,  I'm glad you fixed it by changing SMBIOS. :) 

 

Nope, debug is actually off and "Fast" is on :D

458773653_Screenshot2019-03-27at20_53_49.png.4b70baab9958075e65ff5fdecc174404.png

Share this post


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

 

Nope, debug is actually off and "Fast" is on :D

458773653_Screenshot2019-03-27at20_53_49.png.4b70baab9958075e65ff5fdecc174404.png

 

Well, compared to the speed of a drunk snail on drugs, a few minutes is definitely fast. LOL

 

But...weird... I don't have this issue. Could be a problem with newer motherboards maybe....or could be something else related to the config... I don't know, I've never encountered this issue before, unless Debug was set to True. And even then it wasn't THAT long.

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 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 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.
       
      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.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
      If performing an upgrade from Mojave, backup your Mojave disk! (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 *** MASKED *** parameters in the attached config.plist with your own values. Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 4-7. 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 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 *** MASKED *** 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) If you are upgrading 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 If you're manually installing kexts in /Library/Extensions, make sure that you 'sudo chown -R root:wheel *.kext' and 'sudo chmod -R 755 *.kext' the kexts in /Library/Extensions and you execute 'sudo kextcache -i /'.  After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your install is not complete. 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)  
      Version Info at the time of this writing:
      Catalina Installer 10.15.2 CLOVER v2.5k r5102 DosDude Catalina Patcher: v1.3.0 Lilu.kext 1.4.0 BrcmFirmwareRepo.kext 2.5.0 BrcmBluetoothInjector.kext 2.5.0 BrcmPatchRAM3.kext 2.5.0 IntelMausiEthernet.kext 2.5.0
      VoodooHDA.kext 2.9.2
       
      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) 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) 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 *** MASKED *** 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 @headkaze, @vit9696 and others I'm sure for maintaining the Brcm kexts.
       
       
      E6410-Catalina.zip


      AppleHWSensor.kext.zip
    • By mrwlkr
      Hello everyone, I've an Acer Aspire E5-574 running Mojave at last update, everything is fine, except by the laggy mouse, as the attached, when the system needs the graphic card (Intel HD 520) it's generates a lag.
       
      Thanks

      final_5e2761c58c6b910015da7cf6_967905.mp4 Send me MacBook-Pro-de-Murilo.zip
    • By lizdav
      Hello People,
       
      I have a dual-boot system with both Win10 and MacOS on separate drives. MacOS on an SSD while Windows is on a standard laptop HD. At first it was working fine and I haven't thought much of it but recently MacOS started acting weird. The first thing I noticed was that Clover somehow "forgot" my primary boot drive. This wasn't a huge issue though, as it was booting just fine once I hit enter on the drive selected. I updated Windows 10 to a newer build, however, I did all of this with the SSD drive unplugged just to be sure. Now Windows is working properly while MacOS is having some quite frustrating errors which make it impossible for me to work...
       
      Anyway, the problems are the following:
       
      - random reboots
      - apps freeze or won't start just "bounce"
      - internet not working(eventhough every other device connects just fine)
      - system is laggy overall
       
      I have tried emptying NVRAM int Terminal but I only got a message saying 'Error clearing firmware variables'. I've been searching for solutions on the web for the issue at hand but struggled to find one... I would really appreciate some help.
       
      I attached my config.plist down below. If more information is required, please let me know.
       
      Thank you!!
       
       
       
      config.plist
    • By superdooper71
      Hi I wonder if you can help me out guys.
      I have few issues here
      • First
      when I boot the clover entry screen do not show the disk icons until i press enter
      (If I disconnect the keybord all is smooth, clover start, shows disk icons and boot from Mojave)
      • Second
      Randomly the keyboard and mouse become pretty unstable. The mouse cursor start flashing or the keyboard start to type repetedly <<<<<<<<<<< when i Press the spacebar or some other button
      (this behaviour is applied to all keyboard I have tried, actually 3 different ones)
      --------------------------------------------------------------------
      KB and Mouse are plugged on a USB 3.0 ports
      I have tried to reset the keyboard Pref but NO LUCK
      I have changed Keyboard - Same error
      --------------------------------------------------------------------
      I enclose IOREGregistry and config.plist
       
      MY CURRENT BUILD
      ASROCK Z270 PRO4
      i7 7700K
      32GB DDR4
      Gigabyte GTX 760
       
      I believe that there is some code conflict but I have no idea what is wrong
       
      Please HELP
      Cheers
      Franco
      config.plist
      iMac di imac27.ioreg.zip
    • By Bikash
      Hello.. 
      I am trying to install macOS Mojave in my laptop but the is very slow.. I tried different methods and tutorials but all have same result.
       
      Install of High Sierra, Sierra and El capitan is fast and have no issue.
       
      Specifications:
      hp notebook v5d75pa#acj
      i5-4210u
      Intel HD 4400
      4gb ram ddr3
×