Jump to content
arsradu

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

320 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 MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • 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
       
      Adjusting the brightness on a laptop
      1. Method 1
      Enable Clover DSDT fix AddPNLF. Enable SetIntelBacklight and SetIntelMaxBacklight. A specific value is not necessary - it will be automatically injected according to the processor installed.
      2. Method 2
      Use this ACPI table: SSDT-PNLF.dsl SSDT-PNLF.aml
      Do not use both methods at the same time!
       
      Digital Audio (HDMI / DVI / DP)
      To enable digital audio it is necessary to set the necessary properties and, usually, patch the connectors.
      To enable audio in general and HDMI in particular use WEG along with AppleALC.kext.
      On 10.10.5 and above, WEG automatically changes the connector-type of DP (00040000) to HDMI (00080000) if no custom patches are used.
      The actual connection may be of any type (HDMI / DVI / DP), but for the digital audio to function the connector-type must explicitly be HDMI.
       
      VGA support
      In most cases with Intel Skylake and newer it works by default.
      For Ivy Bridge and possibly other generations there are the options to patch your connectors with the following:
      06020000 02000000 30000000 // Option 1
      06020000 01000000 30000000 // Option 2
      On OS X 10.8.2 and newer it is impossible to have VGA on Ivy Bridge systems.
      Hot-plugging VGA usually does not work.
      In case this doesn't help - there are no other known solutions at this time.
       
      EDID
      EDID is usually correctly identified, so no actions are required. In rare cases, EDID needs to be injected manually.
      An EDID dump can be obtained, for example, with Linux. The correct EDID must be put into *AAPL00,override-no-connect* property for IGPU, where the second 0 stands for the display number.
      In some cases the EDID dump may be incompatible with macOS and leads to distortions. For some EDID in such cases you can use this script, which corrects a provided EDID and saves it to your desktop.
       
      HDMI in UHD resolution with 60 fps
      Add the enable-hdmi20 property to IGPU, otherwise you will get a black screen. Or instead of this property use the boot-arg -cdfon
       
      Disablng a discrete graphics card
      Add the disable-external-gpu property to IGPU. Or instead of this property, use the boot-arg -wegnoegpu
       
      Fix the invalid maximum link rate issue on some laptops (Dell XPS 15 9570, etc.)
      Add the enable-dpcd-max-link-rate-fix property to IGPU, otherwise a kernel panic would happen due to a division-by-zero. Or instead of this property, use the boot-arg -igfxmlr.
      You could also manually specify a maximum link rate value via the dpcd-max-link-rate for the builtin display.
      Typically use 0x14 for 4K display and 0x0A for 1080p display. All possible values are 0x06 (RBR), 0x0A (HBR), 0x14 (HBR2) and 0x1E (HBR3). If an invalid value is specified, the default value 0x14 will be used instead. If this property is not specified, same as above.  
      Fix the infinite loop on establishing Intel HDMI connections with a higher pixel clock rate on Skylake, Kaby Lake and Coffee Lake platforms
      Add the enable-hdmi-dividers-fix property to IGPU or use the -igfxhdmidivs boot argument instead to fix the infinite loop when the graphics driver tries to establish a HDMI connection with a higher pixel clock rate, for example connecting to a 2K/4K display with HDMI 1.4, otherwise the system just hangs (and your builtin laptop display remains black) when you plug in the HDMI cable.  
      1. General Notes
      For those who want to have "limited" 2K/4K experience (i.e. 2K@59Hz or 4K@30Hz) with their HDMI 1.4 port, you might find this fix helpful. For those who have a laptop or PC with HDMI 2.0 routed to IGPU and have HDMI output issues, please note that this fix is now succeeded by the LSPCON driver solution, and it is still recommended to enable the LSPCON driver support to have full HDMI 2.0 experience.  
      (You might still need this fix temporarily to figure out the connector index of your HDMI port. See the LSPCON section below.)
      LSPCON driver support to enable DisplayPort to HDMI 2.0 output on IGPU
      1. Brief Introduction
      Recent laptops (Kaby Lake/Coffee Lake-based) are typically equipped with a HDMI 2.0 port. This port could be either routed to IGPU or DGPU, and you can have a confirmation on Windows 10. Intel (U)HD Graphics, however, does not provide native HDMI 2.0 output, so in order to solve this issue OEMs add an additional hardware named LSPCON on the motherboard to convert DisplayPort into HDMI 2.0.
      LSPCON works in either Level Shifter (LS) or Protocol Converter (PCON) mode. When the adapter works in LS mode, it is capable of producing HDMI 1.4 signals from DisplayPort, while in PCON mode, it could provide HDMI 2.0 output. Some onboard LSPCON adapters (e.g. the one on Dell XPS 15 9570) have been configured in the firmware to work in LS mode by default, resulting a black screen on handling HDMI 2.0 connections.
      Starting from version 1.3.0, WhateverGreen now provides driver support for the onboard LSPCON by automatically configuring the adapter to run in PCON mode on new HDMI connections, and hence solves the black screen issue on some platforms.
       
      2. Before you start
      LSPCON driver is only applicable for laptops and PCs with HDMI 2.0 routed to IGPU. LSPCON driver is necessary for all newer platforms unless the new IGPU starts to provide native HDMI 2.0 output. Supported Intel Platform: Skylake, Kaby Lake, Coffee Lake and later.
      Skylake Case: Intel NUC Skull Canyon; Iris Pro 580 + HDMI 2.0 with Parade PS175 LSPCON.
      Coffee Lake Case: Some laptops, e.g. Dell XPS 15 9570, are equipped with HDMI 2.0 and Parade PS175 LSPCON. If you have confirmed that your HDMI 2.0 is routed to IGPU and is working properly right now, you don't need to enable this driver, because your onboard LSPCON might already be configured in the firmware to work in PCON mode.
      3. Instructions
      Dump your kernel log and you should also be able to see something simillar to lines below.
       
      // When you insert the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] Found the LSPCON adapter: Parade PS1750. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] The current adapter mode is Level Shifter (DP++ to HDMI 1.4). igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has detected the onboard chip successfully. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has been initialized successfully. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x01. igfx @ (DBG) SC: LSPCON::setMode() DInfo: [FB2] The new mode is now effective. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] The adapter is running in preferred mode [Protocol Converter (DP++ to HDMI 2.0)]. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. // When you remove the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver (at 0xffffff802ba3afe0) has already been initialized for this framebuffer. igfx @ (DBG) SC: LSPCON::setModeIfNecessary() DInfo: [FB2] The adapter is already running in Protocol Converter (DP++ to HDMI 2.0) mode. No need to update. igfx @ (DBG) SC: LSPCON::wakeUpNativeAUX() DInfo: [FB2] The native AUX channel is up. DPCD Rev = 0x12. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. Additionally, you can find these properties injected by the driver under the corresponding framebuffer.
      (Only available in DEBUG version)
       
      fw-framebuffer-has-lspcon indicates whether the onboard LSPCON adapter exists or not.
      fw-framebuffer-preferred-lspcon-mode indicates the preferred adapter mode. 1 is PCON, and 0 is LS.
       
      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 gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By poles89
      System Config:
      Mobo: Gigabyte GA-H170-D3H
      RAM: Corsair Vengeance 8GB RAM
      CPU: Intel i3-6100 3.7 GHz
      Graphics: Intel HD 530
      Storage: Gigabyte 240 GB SSD
       
      I installed Mojave 10.14.6 on this system.
      Everything works fine except sleep/wake. When I manually sleep my machine & if I wake up quickly after that, it works. But if I wake up after 10 mins or wake up after automatic sleep it leads to restart.
       
      So far I tried :
      Darkwake -> 0,2,4,8
      Clover Fix Shutdown
      SMBIOS 14,2 -> 17,1
      sudo pmset -a standby 0
      Custom SSDT for power management
      Custom SSDT for USB
      Delete all Power management files from /Library/Preferences
      But nothing works. Any help will be appreciated.
      Here is the attached config & ssdt files.
      config.plist
      SSDT-UIAC.aml
      ssdt.aml
×