Jump to content

Search the Community: Showing results for tags 'ig-platform-id'.

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 4 results

  1. Hello guys. I am setting up my first Hackintosh. Here are the specs: Mobo: Adlink M-342 with AMI Aptio 4 UEFI Intel i3 2120 SandyBridge 4GB RAM 500 GB SeaGate HDD So, here's the issue. The first part of the installation process works perfectly. At the end of the process, I am asked to perform a restart. I do that, it boots back to Clover. I select the HFS partition where I installed OSx, it loads for a while and then the screen goes blank. The only way I found so far to be able to boot to OSx is to set a FakeID in Clover's Graphics Injection menu. The only FakeID that works is this one: 0x041680862 Which is not even a real FakeID. There is no other way, at the moment, to boot to OSx but this one, which is far from a perfect solution (the screen flickers every now and then and I cannot select resolutions different from 1024x768). I really need help on this. HD4600 is known to be fully compatible with OSx, so nobody else has ever had this issue before (apparently). Thanks for your help.
  2. Hi guys, I've just faced with a strange problem of lacking QE/CI acceleration on a fresh 10.10.4 install on my Samsung NP900x3c, i7 ivy, HD4000, 1920x1080, ALC269VC, no dsdt patches, Clover 3259 bootloader. The thing is that with the same Clover config I can boot 10.9 and have full acceleration while 10.10 is booting but no QE/CI. Another thing is that 10.9 provides desktop and QE/CI only with the following ig-platform-id: 0x01660002 0x01660008 and 0x01660009, other ig-platform-id prevents 10.9 from booting, while 10.10 provides fully functional desktop with any ig-platform-id but no QE/CI at all I attached clover config, darwindump and ioreg of 10.10 Any help would be very much appreciated Thank you, Dmitry config.plist.zip Dmitry’s Samsung clover-only.zip DarwinDumper_2.9.8_Clover_X64_3259_Yos_dima.zip
  3. At last, I have working QE/CI via displayport with my built-in haswell HD Graphics 4600. My system is a gigabyte z87mx-d3h. Existing instructions suggest setting AAPL,ig-platform-id to either 00 00 26 0c or 00 00 16 0a, but these platform IDs map to layouts that leave my displayport blank. Upon investigation, these 2 layouts share the same port maps with port 0 being LVDS, port 1 DP (displayport) and port 2 HDMI. I can get video out of my gigabyte motherboard's DVI port with these, but the resolution is busted (driver attempts full 2560x1440 resolution, but motherboard doesn't do dual-link DVI, and so result is a distorted desktop display. The AAPL,ig-platform-id that works with DP on my system is 03 00 22 0d. That platform-id is the only one that maps to a layout that uses DP for port #0. To set the AAPL,ig-platform-id for gigabyte haswell systems, inject via DSDT a new device entry: Device (IGPU) { Name (_ADR, 0x00020000) Method (_DSM, 4, NotSerialized) { Store (Package (0x04) { "AAPL,ig-platform-id", Buffer (0x04) { 0x03, 0x00, 0x22, 0x0d }, "hda-gfx", Buffer () { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } The existing DSDT for this motherboard doesn't have anything for the IGPU device so you have to add the entire Device section, not just the injection method. You do of course have to add the DTGP method to your DSDT as well. I can explain more fully if there's interest. I can also detail decoding much of the haswell PlatformInformationList like I did for the hd graphics 3000 way back when sandy bridge was new. The result: % system_profiler SPDisplaysDataType Graphics/Displays: Intel Iris Pro: Chipset Model: Intel Iris Pro Type: GPU Bus: Built-In VRAM (Total): 1024 MB Vendor: Intel (0x8086) Device ID: 0x0412 Revision ID: 0x0006 Displays: HP ZR2740w: Resolution: 2560 x 1440 Pixel Depth: 32-Bit Color (ARGB8888) Display Serial Number: CNTXXXXXXX Main Display: Yes Mirror: Off Online: Yes Built-In: Yes Connection Type: DisplayPort %
  4. After several weeks' work with @lisai9093, now it's time to post a guide. GUIDE: Intel HD Graphics 5500 on OS X Yosemite 10.10.3 Before we get started: The basic idea to make Broadwell's integrated graphics card work does not change. If you have Intel HD Graphics 5300 or other IGPU models supported by AppleIntelBDWGraphicsFramebuffer.kext, you can try it by yourself. Brief Introduction: The basic idea to let Intel HD Graphics 5500 work is still injecting AAPL, ig-platform-id. However, Apple raised the minimum stolen memory in the AppleIntelBDWGraphicsFramebuffer binary of OS X Yosemite 10.10.3. Kernel panic will happen if the DVMT pre-allocated memory in BIOS settings is lower than 66MB. This is not a big deal for Desktop PCs users, because one can easily change the DVMT pre-allocated memory in BIOS. But this is catastrophic for laptop users, because (1) the default value of DVMT pre-allocated memory in most laptops BIOS is 32MB. (2) OEM will not unlock these advanced settings/menus for us. (3) We can try to modify BIOS but cannot pass the security check during flashing modified BIOS. Detailed Step-by-step guide: STEP 1: Check the current DVMT pre-allocated memory size. Open the Screen Resolution window, click the Advanced settings and check Dedicated Video Memory. After I played with changing DVMT pre-allocated memory in BIOS, the following pattern can be found. If Dedicated Video Memory = 0MB, then DVMT pre-allocated memory in BIOS settings is 32MB. If Dedicated Video Memory = 32MB, then DVMT pre-allocated memory in BIOS settings is 64MB. If Dedicated Video Memory = 64MB, then DVMT pre-allocated memory in BIOS settings is 96MB. If Dedicated Video Memory = 128MB, then DVMT pre-allocated memory in BIOS settings is 128MB. TABLES: Relationship between Dedicated Video Memory detected by OS and DVMT pre-allocated memory in BIOS settings. In general, if DVMT pre-allocated memory in BIOS settings is less or equal to 96MB, the StolenMemory that could be detected by OS is (DVMT - 32) MB. If DVMT pre-allocated memory in BIOS settings is larger or equal to 128MB, the StolenMemory that could be detected by OS is (DVMT) MB. (equal to the value of DVMT pre-allocated memory) Now let's come back to our main topic, Dedicated Video Memory >=64MB (i.e. DVMT pre-allocated memory >= 96MB) will pass the assertion/kernel panic. Note that OS X can not boot on some laptops if DVMT pre-allocated memory is >= 128MB. Therefore, if your current DVMT pre-allocated memory size <= 64MB (i.e. Dedicated Video Memory <= 32MB), you can either choose using our patch in STEP 2.1 or changing DVMT pre-allocated setting in STEP 2.2 STEP 2.1: Apply the patch to pass the Stolen Memory assertion. We need to patch AppleIntelBDWGraphicsFramebuffer binary file. Find 39CF763C and replace it with 39CF773C. After using this patch, in theory you don't have to change your BIOS settings. You can try to inject ig-platform-id and see what happens. If you encounter some problems, try to modify Framebuffer data in AppleIntelBDWGraphicsFramebuffer binary. Detailed information on Broadwell's framebuffer can be found on this page. STEP 2.2: Using EFI Shell to change DVMT settings in BIOS. (1) Prepare a bootable USB drive with EFI Shell Prepare a USB stick and format it with FAT32 filesystem. Download this EFI shell and you can find a folder named BOOT after extracting. Copy this BOOT folder to your USB stick. (2) Dump/Fetch a completed BIOS file. You can use specific BIOS utility to save a copy of your BIOS on Desktop. e.g. For AMI Aptio UEFI BIOS, you can use AMI BIOS Utility. (3) Extract BIOS Settings from a BIOS file. Download UEFITools from https://github.com/LongSoft/UEFITool/releases Open your BIOS file with UEFITools. Find the module labeled with Setup and extract the PE32 image section in this module as a binary file. Now, you will have a binary file on your Desktop. In my case, I name it Setup.bin. Next, download the Universal IFR Extractor (Windows version only) from http://donovan6000.blogspot.ca/2014/02/universal-ifr-extractor.html or from here: Universal IFR Extractor.exe. Open the Universal IFR Extractor in Windows, open the binary you just extracted from UEFITools and click Extract to save the BIOS settings in plain text format. Now open the extracted setup IFR.txt and find the keyword "DVMT". And you can find the variable representing DVMT pre-allocated memory and its values. In this case, DVMT pre-allocated memory's variable is 0x1C3. The value of 96MB is 0x3. Record these two values. Next, restart your computer and boot from the USB drive with EFI Shell. Here, we use setup_var command to change our BIOS settings. syntax: setup_var address value OK, now type the command in EFI shell. In this case, the command is setup_var 0x1C3 0x3. (Change the value of 0x1C3 to 0x3, which means changing the DVMT to 96MB.) After changing the DVMT pre-allocated memory, go back to Windows and double check whether your current Dedicated Video Memory is 64MB. (96 - 32 = 64MB) STEP 3: Injecting AAPL, ig-platform-id You can use either Clover or DSDT/SSDTs to inject AAPL, ig-platform-id. If you want to use Clover, let InjectIntel = True and ig-platform-id=0x16160002. If you want to use DSDT/SSDT to inject AAPL, ig-platform-id, 0x16160002 is working fine. Then open your DSDT, find Device (GFX0) or Device (IGPU) or Name (_ADR, 0x00020000) and add the Device-Specific Method. Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x08) { "device-id", Buffer (0x04) { 0x16, 0x16, 0x00, 0x00 }, "AAPL,ig-platform-id", Buffer (0x04) { 0x02, 0x00, 0x16, 0x16 }, "model", Buffer (0x17) { "Intel HD Graphics 5500" }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }) } Place your DSDT in /EFI/Clover/ACPI/Patched/ Restart your computer and you will find Intel HD Graphics 5500 is working now. Some Issues you may encounter: (1) Garbled Screen Issue Enable Legacy Support in your BIOS settings. (2) Screen Freeze Issue (GPU hang and restart) Using FakeSMC 5.3.820 or other 5.x.xxx version will decrease the opportunity to freeze. (Note that please delete CPUSensors.kext from FakeSMC.kext if you get kernel panic related to CPUSensors.kext) Reference and Special Thanks: Thanks to Rehabman for his advice on garbled screen issue. Thanks to nguyenmac for his clues on freeze issue. Thanks to sontrg for his direction to BIOS modification. Thanks to Google for providing information. Thanks to the-darkvoid for his QHD+ Guide on HD4600.