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

[SavageAUS]

 
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

[arsradu]

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.

 

Edited December 19, 2018 by arsradu

[SavageAUS]

 
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.
 

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

[arsradu]

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.

 

 

 

 

[SavageAUS]

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.

 

 

 

 

This is my config. Quicklook and preview both work.

config.plist

Hardware_Info_V2018-11-13.zip

Edited December 20, 2018 by SavageAUS

[arsradu]

7 hours ago, SavageAUS said:

This is my config. Quicklook and preview both work.

config.plist

Hardware_Info_V2018-11-13.zip

 

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

 

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:

 

Aaaand....TA-DAAA!

 

I'll let you judge the result for yourself.

 

 

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

Edited December 20, 2018 by arsradu

[SavageAUS]

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

 
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:

 

Aaaand....TA-DAAA!

 

I'll let you judge the result for yourself.

 

 

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

[arsradu]

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.

 

 

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 December 20, 2018 by arsradu

[SavageAUS]

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.

 

 

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

 

But this one is iGPU

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

Edited December 20, 2018 by SavageAUS

[arsradu]

5 minutes ago, SavageAUS said:

This one is Audio yes

 

But this one is iGPU

 

Well, might be a typo there...?

 

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

Edited December 20, 2018 by arsradu

[SavageAUS]

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.

[arsradu]

1 minute ago, SavageAUS said:

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

Doesn't matter, it's working.

 

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.  

[SavageAUS]

 
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

[arsradu]

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 December 20, 2018 by arsradu

[NoiseCoalition]

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! 

[arsradu]

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 December 30, 2018 by arsradu

[LockDown]

Do people still using this on 10.14.3?

[unixb0y]

2 hours ago, ellaosx said:

Do people still using this on 10.14.3?

 

Use what? I still have this issue 

[kingkongw24]

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!

[arsradu]

On 3/7/2019 at 6:35 PM, unixb0y said:

 

Use what? I still have this issue 

 

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.

[unixb0y]

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

[arsradu]

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

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 March 27, 2019 by arsradu

[unixb0y]

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 

[arsradu]

Just now, unixb0y said:

 

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

 

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.

[unixb0y]

3 hours ago, arsradu said:

 

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.

 

 

That's possible, I don't know! Mine is Z370, pretty common.