Jump to content

Search the Community: Showing results for tags 'igpu'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 8 results

  1. 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 0x3E92 0x3E91 - 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
  2. Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630 flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000 Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM? I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back. EFI DIRECTORY http://s000.tinyupload.com/index.php?file_id=97606131925137056003 HARDWARE CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU) CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front) Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI) RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot) GFX Card: Sapphire RX 580 NITRO+ SE SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4) HDD: generic DVD Drive: generic PSU: EVGA 500W Semi Modular (but you should get 650W!) Case: CoolerMaster CM590 III Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced. ADVICE With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly. I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence. Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card. Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC. With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well. Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly. My USB 3 ports seem to suffer from low power output, and I don't know why. Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
  3. HI, I'm trying to enable my HD530 (i7-6700k) along my GTX 970 to use QuickSync and get better render times and all the advantages of it... also I need to use airplay mirroring. As now all is working except it, and i'd like to get it working. My problem is that when fcpx or another app exports the IGPU usage always stays at 0%... How can I solve this? (Kexts Lilu,Whatevergreen,AppleALC,Realtek8111,fakesmc) MY config and gen debug results attached. debug_3335.zip config.plist
  4. Okay, I've been struggling with this for a while now, so I decided to post here. My Nvidia GTX 770 died a month or 2 ago so I removed it and I've been using the iGPU in my Intel i7 4790K CPU. My motherboard is a ASUS Z97-P (Here are the specs) I use a VGA cable to connect to my LG 1080p monitor. With OS X, I can't get the Intel HD 4600 graphics to work right. When I click the Launchpad everything there stutters and glitches. Hovering over tabs in Safari causes graphics glitches. Here is what System Information shows: Oh, PS: I use Clover, and I have "Inject Intel" on by default in the config.plst, and OS X won't boot like that. I have to go into clover options and uncheck that for it to boot. Here is my config.plst file: https://www.dropbox.com/s/xkzmly9vqtwijal/config.plist?dl=0&s=sl I will really appreciate any help.
  5. Is there any benefit to getting both of my graphics cards working? I currently have my GTX 760 working fine with HDMI audio. If I remove the card from the board I can use the HD4000 wihout any issues (don't remember if HDMI audio still works, but it was at one point) If I "enable" the internal graphics (instead of auto) I get a kernel panic that looks like a framebuffer issue. I think it's the same issue this guy is getting http://www.insanelymac.com/forum/topic/296122-please-help-me-with-a-kernel-panic/ I don't have any plans of using the onboard graphics but I'm curious if I'm missing out on anything, like, I don't know... proper cpu power management? I also have a little OCD problem, where I do like EVERYTHING to work right even if I don't plan on using it, but I have to weigh the effort/benefit of the situation. Is it a simple option I have to turn on in Clover? Or do I have to do some DSDT edits? Thanks guys
  6. Hi guys! I have not acceleration in my IGPU graphic card, the system says: 7mb vram and everything goes very slowly, neither can to change resolution. I used lilu.kext and inteligraphicsfixup.kext but nothing happens. I tried a lot of things but nothing changes. Tried changing my Fake ID Intel: 0x59128086 and Inject Intel ig-platform: 0x59120000 but nothing happens. I`ve got this issue from 20 days ago and I don´t find the solution. My specs: Desktop Asus H110M-D mobo i3 7100 Kaby Lake Intel HD 630 IGPU 4gb ddr4 ram 500GB HDD WD High Sierra 10.13 OSX Any suggestion will be very appreciated!! Thanks in advance
  7. Hi, im using my gpu geforce gtx 980 ti together with my igpu intel hd 530 for videos/processing a.s.o.. Usually in most forums it´s recommended to use the igpu as primary boot device. I like to use my geforce as primary boot device (PEG) because i get realy much better results.. (also in iStats Menus the gpu memory shows only when in bios PEG is set..) Problem is,.. when i set bios to use PEG i can work with my geforce and the igpu very well but after a couple, when i manually restarted the computer maybe 5 or 6 times (or after i installed any kind of new app or cleaning the cache) suddenly the igpu crashes when i try to use it with any kind of videotools.. If it is impossible on my system to set it in bios to use PEG (geforce as primary) why does it not crash already the first time/immediately when i try to use it with video processing?? Why does it work a couple of times before it crashes ? I already tried many different solutions in clover (patches.. injecting intel a.s.o) and also in bios (vram).. It´s always the same result. Would it be helpful to use a special configured dsdt or ssdt? Basically my goal is to get my system work with my geforce gtx 980 ti as primary device (PEG) because i get much better results on my system with this kind of configuration.. I only have sierra on my system,.. no windows... and this issue is happening on all sierra versions i used in the past. Big thanks for any hints or clues.. Gr. sv My specs: Mainboard: MSI Z170A-G45 Gaming (MS-7977), Chipset - Intel® Z170 Express Processor: 1151 - QuadCore Intel Core i7-6700K CPU: Oc: 4400 MHz , 32 GB Oc: 2800 MHz DDR4 GPU: NVIDIA GeForce GTX 980 Ti (6 GB) iGPU: intel HD530 Bootloader: Clover macOS Sierra 10.12.6 Beta (16G8c)
  8. Greetings everyone, I have the following specs: El Capitan 10.11.4, Clover ASRock H170M ITX/ac Intel Core i3 6100 3.7GHz 16GB Kingston RAM I'm stuck with the following problem: My config.plist only has C States & P States enabled, AppleRTC. I would appreciate any feedback.