Jump to content
GhostRaider

[GUIDE] 1st Generation Intel HD Graphics QE/CI

1,996 posts in this topic

Recommended Posts

@navinmithu, off-topic; this thread is about getting 1st gen Intel HD working, not about installing High Sierra on your Arrandale laptop. Open up your own thread to avoid polluting this one.

Share this post


Link to post
Share on other sites
Advertisement
On 2/10/2019 at 3:36 AM, nijhawank said:

Now I just need to patch that small second stage flickr. I cannot use whatevergreen as it breaks intelbacklight (which I must use because of my hardware which does not use expose pwm registers needed for native brightness control)

Since you didn't use WhateverGreen, what you need is "Fix Second Stage Boot Glitch" via KextToPatch method.

I see no reason why it doesn't work for you; on my case is fine with 10.13.6 & 10.14.3:

 

 

            <dict>
                <key>Comment</key>
                <string>Fix Second Stage Boot Glitch</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                AQAAdSI=
                </data>
                <key>InfoPlistPatch</key>
                <false/>
                <key>MatchOS</key>
                <string>10.13.x,10.14.x</string>
                <key>Name</key>
                <string>com.apple.iokit.IOGraphicsFamily</string>
                <key>Replace</key>
                <data>
                AQAA6yI=
                </data>
            </dict>

 

Also check config.plist - BootGraphics; leave "DefaultBackgroundColor" > Empty (Auto)

Edited by Badruzeus

Share this post


Link to post
Share on other sites
13 hours ago, Badruzeus said:

Since you didn't use WhateverGreen, what you need is "Fix Second Stage Boot Glitch" via KextToPatch method.

I see no reason why it doesn't work for you; on my case is fine with 10.13.6 & 10.14.3:

 

  Reveal hidden contents

            <dict>
                <key>Comment</key>
                <string>Fix Second Stage Boot Glitch</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                AQAAdSI=
                </data>
                <key>InfoPlistPatch</key>
                <false/>
                <key>MatchOS</key>
                <string>10.13.x,10.14.x</string>
                <key>Name</key>
                <string>com.apple.iokit.IOGraphicsFamily</string>
                <key>Replace</key>
                <data>
                AQAA6yI=
                </data>
            </dict>

 

Also check config.plist - BootGraphics; leave "DefaultBackgroundColor" > Empty (Auto)

 

"Fix Second Stage Boot Glitch" has not worked like many others reported. Apparently, it works for some and not for others, don't know what could be the reason.

Anyways, this glitch is far better than the previous hard flicker that lasted couple of seconds.

 

I discovered one more weird issue. I have a perfectly running hackintosh with just two issues (brightness and the above glitch). On brightness, my conclusion is that my hardware does not use IGPU PWM registers and therefore AppleBacklightFixup or the latest implementation in WhateverGreen is not compatible. However, I wanted to try one more time.

 

So I once again prepared what I needed to do for WEG and tested. And I never reached the login screen. Tried few more combinations but nothing helped. 

1. Eventually, I restored everything to the way it was and now my graphics is garbled, as if KextsToPatch entries are not working. I tried rebuilding kextcache many times by entering in single user mode and rebooting many times but it didn't help.

2 - I finally restored to the earlier statically patched El Capitan AppleIntelHDGraphics kexts and rebooted. It worked (of course with that hard flickr)

3 - I restored once again to the unmodified HS AppleIntelHDGraphics kexts and rebooted. It worked, but why?

 

There was absolutely no difference between step 1 and 3, except that I temporarily restored to statically patched kexts in step 2. 

 

One another question is what ig-platform-id do you use with WEG for Intel 1st Gen Graphics?

 

Share this post


Link to post
Share on other sites

ig-platform-id? What ig-platform-id ??? :lol:

 

Re: 2nd stage boot glitch, you probably don't have the correct IOGraphicsFamily patch in place...

75 22 to EB 22 in High Sierra and Mojave

Edited by Hervé

Share this post


Link to post
Share on other sites
On 11/9/2017 at 3:48 AM, Goldfish64 said:

Does anyone have functioning brightness control on 10.13 using the AppleBacklightInjector kext?

 

Nope, but old @mnorthern DSDT patching method is still working for getting my Native (ACPI) Brightness on macOS Mojave 10.14.3 with the help of Rehabman's IntelBacklight.kext. The only issue is Fn+Keys for Brightness change didn't work, neither Slider on Display pref (I've applied ACPIDebug + Intrument_QXX to get my Fn+Keys through patched DSDT, no issue with 10.11.x).

 

Ah, nevermind.. BergDesign's Brightness.app is still good; it uses ACPI way.. doesn't spread the Screen with Black Fill color. My screenshot below is when using the app on 50% level, if you see it darker on your screen.. probably I was wrong. (Slider & Bezel are just cosmetics #LoL Brightness is accessible via Top MenuBar, and it looks like hidden bcoz Mojave DarkMode)

 

Screenshot 2019-02-12 at 00.47.32.png

IntelBacklight.kext_v1.0.12.zip

Edited by Badruzeus

Share this post


Link to post
Share on other sites
30 minutes ago, Hervé said:

ig-platform-id? What ig-platform-id ??? :lol:

 

Re: 2nd stage boot glitch, you probably don't have the correct IOGraphicsFamily patch in place...

75 22 to EB 22 in High Sierra and Mojave

 

I'm using the patch provided by @Badruzeus

 

Ok so I take that ig-platform-id is not a thing with 1st Gen intel graphics. I am very new to hackintosh scene so learning it day by day. But anyways that's not important as I said, I can bear the minor glitch as its much better than the hard flickr with statically patched kexts from El Capitan.

 

However, the main weirdness is with this...

46 minutes ago, nijhawank said:

So I once again prepared what I needed to do for WEG and tested. And I never reached the login screen. Tried few more combinations but nothing helped. 

1. Eventually, I restored everything to the way it was and now my graphics is garbled, as if KextsToPatch entries are not working. I tried rebuilding kextcache many times by entering in single user mode and rebooting many times but it didn't help.

2 - I finally restored to the earlier statically patched El Capitan AppleIntelHDGraphics kexts and rebooted. It worked (of course with that hard flickr)

3 - I restored once again to the unmodified HS AppleIntelHDGraphics kexts and rebooted. It worked, but why?

 

 

Share this post


Link to post
Share on other sites

@nijhawank

You need non-modified (vanilla) AppleIntelHDGraphicsFB* && IOGraphicsFamily* for using with KextToPatch method.

If those kexts are modified (or already patched eg. by binary edit with HexFind.app); guessing KTP won't work bcoz binary missmatch or "Find" value got no result though you've rebuilt prelinkedkernel && kernelcache several times. Check them with: $ sudo kextcache -i / (for any invalid signature). Choose only one method, use Vanilla kexts + KTP.. or patched kexts only.

 

And if kexts that come from pre-installed macOS system named "Vanilla", there's no Vanilla AppleIntelHDGraphics* on LE/SLE since Mojave 10.14 bcoz Apple have removed it's support. On this case is using them from 10.12.x or 10.13.x; as long as binaries are not touched; we could named it as non-modified < so KextToPatch is still working.

 

Edited by Badruzeus

Share this post


Link to post
Share on other sites
33 minutes ago, Badruzeus said:

Nope, but old @mnorthern DSDT patching method is still working for getting my Native (ACPI) Brightness on macOS Mojave 10.14.3 with the help of Rehabman's IntelBacklight.kext. The only issue is Fn+Keys for Brightness change didn't work, neither Slider on Display pref (I've applied ACPIDebug + Intrument_QXX to get my Fn+Keys through patched DSDT, no issue with 10.11.x).

 

Ah, nevermind.. BergDesign's Brightness.app is still good; it uses ACPI way.. doesn't spread the Screen with Black Fill color. My screenshot below is when using the app on 50% level, if you see it darker on your screen.. probably I was wrong. (Slider & Bezel are just cosmetics #LoL Brightness is accessible via Top MenuBar, and it looks like hidden bcoz Mojave DarkMode)

 

I also use BergDesign's Brightness app along with either of IntelBacklight or ACPIBacklight. Both works, but I see that when using IntelBacklight, the brightness always get sets to minimum on reboot. I use EmuVariableUefi and the problem is not with ACPIBacklight. 

 

Do you face the same problem with IntelBacklight?

 

Share this post


Link to post
Share on other sites
5 minutes ago, Badruzeus said:

@nijhawank

You need non-modified (vanilla) AppleIntelHDGraphicsFB* && IOGraphicsFamily* for using with KextToPatch method.

If those kexts are modified (or already patched eg. by binary edit with HexFind.app); guessing KTP won't work bcoz binary missmatch or "Find" value got no result even you've rebuilt prelinkedkernel && kernelcache several times. Check them with: $ sudo kextcache -i / (for any invalid signature). Choose only one method, use Vanilla kexts + KTP.. or patched kexts only.

 

And if kexts that come from pre-installed macOS system named "Vanilla", there's no Vanilla AppleIntelHDGraphics* on LE/SLE since Mojave 10.14 bcoz Apple have removed it's support. On this case is using them from 10.12.x or 10.13.x; as long as binaries are not touched; we could named it as non-modified < so KextToPatch is still working.

 

 

Yes, in step 1, when I restored everything to the original working state, the kexts were vanilla High Sierra. That's why I said, there is no understandable difference between step 1 and step 3. Don't know how temporarily switching to statically patched El Capitan kexts, rebooting and reverting once again to vanilla kexts made it work.

Share this post


Link to post
Share on other sites
14 minutes ago, nijhawank said:

I also use BergDesign's Brightness app along with either of IntelBacklight or ACPIBacklight. Both works, but I see that when using IntelBacklight, the brightness always get sets to minimum on reboot. I use EmuVariableUefi and the problem is not with ACPIBacklight. 

 

Do you face the same problem with IntelBacklight?

I'm not having that issue, seems working fine here so far. I use Legacy only, so.. EmuVariable* is not in use.

Does your mach have UEFI support? Have you tried with AptioMemoryFix instead of OsxAptio+EmuVariable?

(But about UEFI or Aptio is #OffTopic here, I guess).

Edited by Badruzeus

Share this post


Link to post
Share on other sites
4 minutes ago, Badruzeus said:

I'm not having that issue, seems working fine here so far. I use Legacy only, so.. EmuVariable* is not used here.

Does your mach have UEFI support? Have you tried with AptioMemoryFix instead of OsxAptio+EmuVariable?

(But about UEFI or Aptio is #OffTopic here, I guess).

I know its off-topic but just wanted to reply. My machine is Lenovo T410 (with series 5 chipset). It does not have support for UEFI but only BIOS.

I tried AptioMemoryFix (and other versions, one by one) but it didn't work, so I resorted to using EmuVariableUefi.

 

 

Share this post


Link to post
Share on other sites
17 hours ago, nijhawank said:

I know its off-topic but just wanted to reply. My machine is Lenovo T410 (with series 5 chipset). It does not have support for UEFI but only BIOS.

I tried AptioMemoryFix (and other versions, one by one) but it didn't work, so I resorted to using EmuVariableUefi.

As far as I know, EmuVariable*, AptioMemoryFix*, OsxAptio* are for UEFI. Did you check "rc.script" when Clover Legacy install? Sorry, I guess you need fixing your hackintosh setups that are not related to IntelHD Graphics 1st Gen. So.., let's stop such #OffTopic. Create a new separated thread as @Hervé has said many many times..!!!

Edited by Badruzeus

Share this post


Link to post
Share on other sites
On 2/7/2019 at 8:33 AM, Badruzeus said:

I think you're using AppleIntelHDGraphics* from 10.12.x., I remember got those WhiteScreen for secs on boot (though, should be fixed with WEG or KTP above, tested all of them). Sometimes It's better installing Lilu + PlugIns on LE as @Herve has said. Or if you're playing with Clover, (and kexts located on \efi\clover\kexts\other) use config.plist - System Parameters - InjectKexts=Yes. I attached Lilu, WEG, and patched IOGraphicsFamily.kext (10.14.3) + AppleIntelHDGraphicsFB.kext (from old 10.13) below. You've to uncheck / Disable KTP related to IntelHD 1st Gen & IOGraphicsFamily if using these patched versions.

 

AppleIntelHDGraphicsFB.kext_10.13.x.zip

IOGraphicsFamily.kext_10.14.3.zip

Lilu_v1.3.3_20190128.zip

WhateverGreen__v1.2.7_20190103.zip

 

#EDIT: You also need using other AppleIntelHD* (kext + bundle) from 10.13.x, not only ~FB.kext above.

What about the sleep and wake from sleep with these kexts?

Since I upgraded to HSierra my hack won't wake from sleep, dark screen. But it works perfectly with Sierra.

Share this post


Link to post
Share on other sites
9 hours ago, calmesal said:

What about the sleep and wake from sleep with these kexts?

Since I upgraded to HSierra my hack won't wake from sleep, dark screen. But it works perfectly with Sierra.

 

It won't work on my case, not sure. Probably was laptop specific issue. I've patched _PRW methods on DSDT as well, should be no issue on another laptop with different gfx. Honestly I never use mach sleep, but only Display.

Share this post


Link to post
Share on other sites

@Badruzeus

 

I fixed the annoying second stage boot graphics glitch. The problem was that I was using Intel->Inject=True but without that it couldn't load the frame buffer. So I had it always enabled.

 

I re-read the 1st post in this thread, and in the troubleshooting section, it said if it stucks at spinning wheel and desktop never loads, you will need to inject certain properties in the DSDT. I had never tried this earlier, because for me it was working with Intel->Inject=True.

 

So I tried disabling it and I injected the following _DSM method to my IGPU device (and renamed the original one to XDSM) and voila it worked. No more that annoying flickr.

 

Thank you for being so patient with all my never ending questions and hats off to all the amazing people who have made all of this possible.

+                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
+                {
+                    Store (Package ()
+                        {
+                            "AAPL,os-info",
+                            Buffer ()
+                            {
+                                0x30, 0x49, 0x01, 0x11, 
+                                0x01, 0x10, 0x08, 0x00, 
+                                0x00, 0x01, 0x00, 0x00, 
+                                0x00, 0x00, 0x00, 0x00, 
+                                0xFF, 0xFF, 0xFF, 0xFF
+                            },
+                            
+                            "VRAM,totalsize",
+                            Buffer ()
+                            {
+                                0x00, 0x00, 0x00, 0x12
+                            },
+                            
+                            "model",
+                            Buffer ()
+                            {
+                                "Intel HD Graphics"
+                            }
+                            
+                        }, Local0)
+                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
+                    Return (Local0)
+                }                
+                                                

 

Share this post


Link to post
Share on other sites

Hey guys please help...

 

Will this guide work on Desktop of High Sierra (I can downgrade as per needed)? 

 

I have Intel core i3 540 with Intel HD graphics (clarkdale) with same device ID 0042 .

As referred from Wikipedia ™

 

Please tell if I can enable graphics !!

 

Any help would be appreciated !

Edited by RagK

Share this post


Link to post
Share on other sites

So the newest version of Mojave will not work on intel arrandale ?

I have this weird issue that booting the installer will shutdown my laptop right after start reading kernel cache

IMG_20190217_210425.jpg

IMG_20190217_210351.jpg

Share this post


Link to post
Share on other sites
10 hours ago, kiellig said:

So the newest version of Mojave will not work on intel arrandale ?

I have this weird issue that booting the installer will shutdown my laptop right after start reading kernel cache

IMG_20190217_210425.jpg

IMG_20190217_210351.jpg

Edit boot agrs and add UseKernelCache=No 

I had the same issue and I solved it..

Share this post


Link to post
Share on other sites

I used -v and -no_compat_check as well,

 

So i need to use no kernel cache as well ?

And i use uefi boot, maybe legacy boot is better ?

Share this post


Link to post
Share on other sites
17 hours ago, Kielligzind said:

I used -v and -no_compat_check as well,

 

So i need to use no kernel cache as well ?

And i use uefi boot, maybe legacy boot is better ?

Also try checking OsxAptioFixDrv-64 while installing Clover in Driver 64 UEFI and try legacy ...

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   1 member

  • Similar Content

    • By GhostRaider
      This download is only for users who have a laptop with a 2010 Intel® Arrandale Processor with Intel® HD Graphics:
       
      1st Generation Intel® Core™ Processor with Intel HD Graphics (Arrandale only)
      Intel® Celeron® Processor with Intel® HD Graphics (Arrandale only)
      Intel® Pentium® Processor with Intel® HD Graphics (Arrandale only)
       
      Make sure the Device ID and Vendor ID match with the following:
       
      Device ID: 0042 or 0046
      Vendor ID: 8086
       
      In here you will find my QE/CI and CI only packages for your 1st Generation Intel HD Graphics IGPU for OS X Mountain Lion, OS X Mavericks, OS X Yosemite, OS X El Capitan, macOS Sierra, and macOS High Sierra.
       
      Choose your package:
       
      Download the Intel® HD Graphics QE/CI package if your laptop is using the LVDS connector. This package has the necessary kexts to enable Quartz Extreme with Core Image (QE/CI). This enables full hardware/graphics acceleration.
       
      or
       
      Download the Intel® HD Graphics CI package if your laptop is using the eDP connector. This package enables Core Image (CI) only. This enables partial acceleration.
       
      Note: CI only (CI) is only available on OS X Mavericks 10.9.5 and below. Future releases of macOS requires full graphics acceleration (QE/CI) for optimal performance and stability.
       
      For more information about 1st Generation Intel® HD Graphics, everything is explained in my guide:
       
      http://www.insanelymac.com/forum/topic/286092-guide-1st-generation-intel-hd-graphics-qeci/
    • By jack-69
      DISM is your friend!
       
      Part 1: (For all the computers that don't have UEFI)
       
      Prepare two USB keys, one with El Capitan & one with Windows 10.
      First put the Windows USB, during the installation (when it asked the Windows code) press shift + f10 and will open the command prompt:
      diskpart list disk (list of your hdd) select disk 0 (0 is number of your hdd) clean (ATTENTION clean all your hard disk selected) convert gpt create partition efi size=200 (creates EFI partition) format fs=fat32 label=EFI We made a EFI partition.
      In my Hdd I have 3 partitions ( 1 for Mac, 1 for Windows=Ntfs & 1 in exFat for sharing files between the two systems).
      create partition primary size=100000 (1 partition for Mac OS X 100GB) format fs=fat32 quick label=Mac (after we will format in HFS+ with disk utility) create partition msr size=128 (creates Microsoft Reserved) create partition primary size=100000 (1 partition for Windows 10 100GB) format fs=ntfs quick label=Windows (format in Ntfs) create partition primary (creates a partition with the remaining space) format fs=exfat quick label=Hdd (format in exFat) Now the fun part.
      We should insert the letters for the partitions. Check
      select disk 0 list volume (check the assigned letters, REMINDS the letter assigned to the USB "example d") list partition (check the number of partition EFI "example partition 1") select partition 1 assign letter=h list partition (check the number of partition Windows "example partition 3") select partition 3 assign letter=g exit Then we have the letter "D:\" for the USB, "H:\" for the EFI partition & "G:\" for the Windows partition.
      Now we need to copy the installation files from the USB to the Windows partition.
      cd\windows\system32\ dism /apply-image /imagefile:d:\sources\install.wim /index:1 /applydir:g:\ Break....
      Now we need the Windows EFI boot files.
      cd\ g: bcdboot (check the command line) bcdboot g:\windows /1 en-us /s h: /f UEFI (in my case "/1 It-it") Restart the computer with the Mac USB "Clover bootloader", then select Microsoft EFI and start the installation of Windows 10 in FULL GPT. 
      If you don't see the exFat partition in Windows don't worry.
      (Take a program like Partition Wizard, format the partition in NTFS  and assigns the letter D:\. Now open the command prompt administrator and write:
      diskpart select disk 0 list partition (check the partition before-exFat = after-NTFS "example partition 4") select partition 4 format fs=exfat quick label=Hdd Now you must have the partition exfat visible and writable)
       
       
      Part 2:
       
      Important!  
      Don't format or delete the EFI partition.   
      From the Mac USB we need delete AppleIntelHDGraphicsFB.kext. 
       
      Now we go in to the installation of El Capitan, with disk utility format the partition "Mac" in HFS+ mac journaled, then install Mac OS X.
      While starting El Capitan from your hard drive, we must block AppleIntelHDGraphicsFB.kext and AppleIntelHDGraphics.kext. (& add cpus=1 or patch with clover)
      When El Capitan is started:
      Patch AICPM with Clover Configurator Install Clover like this  (of course without installation El Capitan) "Legacy mode" Replace the config.plist in EFI partition and add SMBIOS with clover configurator - macbook pro 6.1 Put the DSDT Put HFSPlus.efi, NTFS.efi in drivers64 folder Insert and replace all kext PS:During the first system start we must go in the system preferences, keyboard, shortcuts and change the key combination of brightness (f2- f3+).
       
       
      Work:  
       
      Intel Core i5 460M
      Intel HD Graphics                                      (Clean graphics without artifacts)
      Wifi & Ethernet                                          (Atheros AR9285 & Realtek 8111)
      Stereo speakers & Microphone                    (IDT92HD81B1X5)
      Keyboard & multi-touch touchpad
      Memory Card Reader
      Camera
      All USB
      Battery
      Sleep & Wake
      Brightness Values
      App Store
       
      Don't work: 
       
      ATI Mobility Radeon HD 5470                      (Blocked by BIOS)
      FaceTime                                                   (With Rom,SN,MLB valid work)
      iMessage                                                   (With Rom,SN,MLB valid work)
      Maps            
       
       
      Thanks : GhostRider - pokenguyen - Mirone & Micky1979 - RehabMan
       
       
      HP El Cpitan.zip
    • By newbie2379
      Good day,

      I'm trying to install OSX El Capitan on my laptop all the time.
      I have a laptop with a Intel CORE i5 430M Arrandale CPU and first generation Intel HD Graphics.
      The problem is the graphics card.
      I have deleted the kext for the graphics card to install El Capitan.
      After installing it boots also without error messages, but then comes a graphic error. The graphics error was already before I had deleted the Kext before installing.
      The graphics error should not come, however, if I had deleted the kext?

      I can install OSX successfully, but when booting comes a graphic error.

      I have also searched the Internet for solutions. The solutions I had found only work after a successful boot.

      I have tried it with other graphics kext, but without success.

      I also have no other computer with OSX.

      Best regards
×