Jump to content
arsradu

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

312 posts in this topic

Recommended Posts

6 hours ago, JaredTop said:

This topic is like a real treasure chest. Thanks!

 

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

Edited by arsradu

Share this post


Link to post
Share on other sites
Advertisement

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

Share this post


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

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


Sent from my iPhone using Tapatalk

Share this post


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


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


Sent from my iPhone using Tapatalk

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

Share this post


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

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

 

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

 

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

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

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

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

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

Share this post


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

 

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

 

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

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

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

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

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

 

I am not using WhateverGreen. 

1. I added my HW info to my signature!

2. My SMBIOS is iMac 18,1

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

 

Thanks!

Share this post


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

 

I am not using WhateverGreen. 

1. I added my HW info to my signature!

2. My SMBIOS is iMac 18,1

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

 

 Thanks!

 

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

 

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

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

 

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

 

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

Edited by arsradu

Share this post


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

 

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

 

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

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

 

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

 

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

i activate hardware acceleration through this patching whatevergreen.kext.

Share this post


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

i activate hardware acceleration through this patching whatevergreen.kext.

 

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

Share this post


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

 

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

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

Share this post


Link to post
Share on other sites

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

Intel Core i3 4150 
Intel HD 4400
macOS Mojave

 

Spoiler

Zrzut ekranu 2018-11-22 o 21.41.00.png

 

Spoiler

IMG_5013.jpg

 

Edited by pprommelus

Share this post


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

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

Intel Core i3 4150 
Intel HD 4400
macOS Mojave

 

  Reveal hidden contents

Zrzut ekranu 2018-11-22 o 21.41.00.png

 

  Reveal hidden contents

IMG_5013.jpg

 

Have you tried WhateverGreen.kext?

Share this post


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

Have you tried WhateverGreen.kext?

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

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

 

This is my config.plist file

Edited by pprommelus

Share this post


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

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

 

This is my config.plist file

Are you using FV2?

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

Which smbios are you using now?

 

 

Sent from my iPhone using Tapatalk

Share this post


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

Are you using FV2?

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

Which smbios are you using now?

 

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

Share this post


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

Now i'm using SMBIOS - iMac14,2 

Yes you can remove quite a few.

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

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

 

 

Sent from my iPhone using Tapatalk

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

 

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

config.plist

Edited by SavageAUS

Share this post


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

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

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

config.plist

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

 

Share this post


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

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

 

 

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

 

 

EDIT:

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

config2.plist

Edited by arsradu

Share this post


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

 

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

.........


 

Thank you for your help and commitment :)

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

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


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

 

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

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

Edited by pprommelus

Share this post


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


 

Thank you for your help and commitment :)

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

 


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

 

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

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

 

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

 

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

Share this post


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

 

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

 

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

 


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

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


 

Share this post


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

 


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

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


 

 

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

 

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

 

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

 

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

 

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

 

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

 

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

Edited by arsradu

Share this post


Link to post
Share on other sites

Hello,

 

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

 

Hardware is:

 

8700k

Rog Strix Z390-i

Gigabyte RX560

970 Pro M.2

 

Running Mojave 10.14

 

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

 

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

Share this post


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

Have you enabled iGPU?


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

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

Create an account

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

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Spoofing Intel CPU Gen
      If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
       
      Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - S/L/E/AppleIntelSNBGraphicsFB.kext
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
      - AAPL,snb-platform-id (desktop): 0x00030010 (default)
      - AAPL,snb-platform-id (laptop): 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - S/L/E/AppleIntelFramebufferCapri.kext
      - Support started with OS X 10.8.x
      - device-id: 0x0152 0x0156 0x0162 0x0166
      - AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
      - AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - S/L/E/AppleIntelFramebufferAzul.kext
      - Support started with OS X 10.9.x
      - device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
      - AAPL,ig-platform-id (desktop): 0x0D220003 (default)
      - AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
      - Support started with OS X 10.10.2
      - device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
      - AAPL,ig-platform-id (desktop): 0x16220007 (default)
      - AAPL,ig-platform-id (laptop): 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
      - Support started with macOS 10.12.6
      - device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
      - AAPL,ig-platform-id (desktop): 0x59160000 (default)
      - AAPL,ig-platform-id (laptop): 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
      - AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Hackintool File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Hackintool File->Import->IOReg Dump menu
       
      3. Using Hackintool Framebuffer->macOS 10.14 menu
       
      Debug Output
      To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help

      To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.

      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
    • 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 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, 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.5_18F132
      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.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.5.zip
       
       
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo

      View full article
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo
×