Jump to content
GhostRaider

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

2,079 posts in this topic

Recommended Posts

You do realise that run run Mojave on unsupported graphics, right? And that the tricks to get graphics acceleration on 1st gen Intel HD are just that: tricks.

 

My D630 with unsupported nVidia Quadro NVS 135M does just about the same in 10.14.1, except that the screen goes black as opposed to grey/white. Can't remember if I had the same with unsupported HD3000...

Share this post


Link to post
Share on other sites
Advertisement
10 hours ago, Hervé said:

You do realise that run run Mojave on unsupported graphics, right? And that the tricks to get graphics acceleration on 1st gen Intel HD are just that: tricks.

 

My D630 with unsupported nVidia Quadro NVS 135M does just about the same in 10.14.1, except that the screen goes black as opposed to grey/white. Can't remember if I had the same with unsupported HD3000...

2

 

Totally. I'm just trying to identify the problem and understand if a fix exists or is *known not-fixable* due to the way things are. 

 

Thanks for confirming a similar problem with your nVidia based system. Appreciate it.

Share this post


Link to post
Share on other sites

Hi, which Clover should I download in order to install Sierra/High Sierra/Mojave? I am trying to install one of these on my Acer 4820T (i3 350m, 8gb ram, 250hhd).

I don t have the choise "Install X Installer"

Edited by PotatoBoyInUk

Share this post


Link to post
Share on other sites

Hi!
I managed to install Sierra on my laptop (Acer 4820T) and I am now trying to enable QE/CI Graphics.
I have proceeded in this way:
- Delete all IntelHDGraphics kexts from S/L/E
- Rebuilt cache and rebooted
- Used Kext Utility and installed the kexts for 10.12 (Tried different buffers)
- Modify clover config file to : Delete the fake intel id, uncheck inject intel and check patch vbios

When I reboot however the screen gets stuck during the loading and I cannot proceed further.

Here I am attaching the files:

EFI folder - https://www.dropbox.com/s/70bcrla46zx4mzs/EFI.zip?dl=0
DSDT - https://www.dropbox.com/s/tkm0u2nlnxi4h9f/DSDT.zip?dl=0
https://imgur.com/a/SoMgU7W
https://imgur.com/a/w0qxR1n

Hardware Specs: https://pastebin.com/FJPupeVn
Graphics analysis: https://pastebin.com/xN1i3St1

Share this post


Link to post
Share on other sites
On 9/15/2018 at 3:46 AM, jgil00 said:

That is if there is hope for snow leopard, full QE / CI, Toshiba L500-sp6018m, i3 330M, Linkwidht 1 LVDS, I currently have High Sierra but I need to experiment, I really want to use Intel HD in Snow Leopard, Thanks , :) Thanks , Thanks.  

can extract FB of Snow leopard iatkos s3 v2 and patch Giofrida old version

This method was still working long time ago under Snow Leopard (10.6.8) on my laptop with IntelHD 1st Gen graphics.

I attached my worked FB kext if you wanna give a try (also provided on above link, actually. Not sure if mine will give diff. result).

 

On 11/20/2018 at 1:30 PM, nijhawank said:

Can someone please help me solve the flickering at around 60-70% apple logo progress bar (before the login screen appears) or even any pointers what it is? I have tried the second stage boot graphics glitch patch but it didn't help, probably not the same thing.

 

It's i3-370m with Mojava 10.14.1 with patched fb kext from El Capitan for DualLink and Normal FB.

I have QE/CI working but this flickering before login screen appears is really annoying. Scroll the video to 0:08. After the flicker, it returns to apple logo/progress bar and continues to login as normal.

It was "2nd Stage Boot Glitch" WhateverGreen already solved this issue, tested upto 10.14.3 (18D43) and it works. Another method is using KextToPatch via Clover. Below is for 10.13.x - 10.14.x:

 

 

 


<key>KextsToPatch</key>
        <array>
            <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>
        </array>
 

 

Choose only one, between WEG or KextToPatch and don't use altogether.

AppleIntelHDGraphicsFB.kext_10.6.8.zip

Edited by Badruzeus

Share this post


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

It was "2nd Stage Boot Glitch" WhateverGreen already solved this issue, tested upto 10.14.3 (18D43) and it works. Another method is using KextToPatch via Clover. Below is for 10.13.x - 10.14.x:

 

  Hide contents

 


<key>KextsToPatch</key>
        <array>
            <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>
        </array>
 

 

Choose only one, between WEG or KextToPatch and don't use altogether.

AppleIntelHDGraphicsFB.kext_10.6.8.zip

 

Are you saying that you fixed this flicker in 10.14.3 with Intel 1st Gen Graphics? Because I did try using WEG and the kext patch separately and neither helped. It's quite a strong / heavy flicker (look at the video) and not like a slight glitch that I believe the second stage boot glitch fix fixes. Let me know your thoughts.

Share this post


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

Are you saying that you fixed this flicker in 10.14.3 with Intel 1st Gen Graphics? Because I did try using WEG and the kext patch separately and neither helped. It's quite a strong / heavy flicker (look at the video) and not like a slight glitch that I believe the second stage boot glitch fix fixes. Let me know your thoughts.

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.

Edited by Badruzeus

Share this post


Link to post
Share on other sites
14 hours ago, 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.

 

Hello Badruzeus,

 

Are you using AppleIntelHDGraphicsFB (and related) kexts from High Sierra? How did you patch them, because there's no documentation on how to patch them for Sierra and above. 

 

I followed the guide in the below thread 

https://www.insanelymac.com/forum/topic/286092-guide-1st-generation-intel-hd-graphics-qeci/

and used Giofrida's Intel® HD Graphics Patcher with the "Intel HD Graphics QECI Legacy 10.12.zip". I believe the Legacy FB Kext is from the El Capitan. I used "Normal", Linkwidth X1 and DualLink options to patch for my laptop which is a Lenovo T410. If you know how to patch these for High Sierra, can you tell me the instructions for Normal, Linkwidth X1 and DualLink or send me the appropriately patched kext and I will do the testing.

 

Thanks for any help in advance.

Share this post


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

@Badruzeus do you have any comments on my previous post?

Oh, I just realized that my last reply isn't posted on this thread.. was on Phone previously and bit bz; sorry.

 

16 hours ago, nijhawank said:

Are you using AppleIntelHDGraphicsFB (and related) kexts from High Sierra? How did you patch them, because there's no documentation on how to patch them for Sierra and above. 

Yes, my last attempt was using AppleIntelHDGraphics* from 10.13.6 (17G5019) and confirmed it' s working fine on 10.14.3 (SingleLink, LVDS, LW1).

 

16 hours ago, nijhawank said:

If you know how to patch these for High Sierra, can you tell me the instructions for Normal, Linkwidth X1 and DualLink or send me the appropriately patched kext and I will do the testing.

My KextToPatch method is following Goldfish64's ArrandaleGraphicsHackintosh repo (which actually is also based on vertex & GhostRaider guides for IntelHD 1st Gen).

 

For DualLink, test & report are needed. Plz give it a try:

 

# DualLink Patch 1 (MatchOS: 10.11.x,10.12.x,10.13.x,10.14.x)
Find	:	0F 45 C8 42
Replace	:	90 90 90 42

# DualLink Patch 2 (MatchOS: 10.11.x)
Find	:	498B8424 98060000 0FB64018 C1E01341 0B466C41 89466C49 8B8C2498 00000089 810C000F 00498B84 24980600 000FB640 18C1E013 410B4668
Replace	:	418B466C 25FFFFC7 FF0D0000 00009090 90909041 89466C49 8B8C2498 00000089 810C000F 00418B46 6825FFFF C7FF0D00 00000090 90909090

# DualLink Patch 3 (MatchOS: 10.12.x,10.13.x,10.14.x)
Find	:	498B8424 98000000 8B880C00 0F004189 4E6C8B90 00010600 41895668 81C90020 00004189 4E6C8988 0C000F00 BF190000 00E80000 0000418B
Replace	:	418B466C 25FFFFC7 FF0D0000 00009090 90909041 89466C49 8B8C2498 00000089 810C000F 00418B46 6825FFFF C7FF0D00 00000090 90909090

# DualLink Patch 4 (MatchOS: 10.12.x,10.13.x,10.14.x)
Find	:	498B8424 98000000 89880C00 0F00498B 8C249806 00000FB6 5118C1E2 13418B76 6C09D641 89766C89 B00C000F 00410B56 68418956 68899000
Replace	:	418B466C 25FFFFC7 FF0D0000 00009090 90909041 89466C49 8B8C2498 00000089 810C000F 00418B46 6825FFFF C7FF0D00 00000090 90909090

=============================================================

 

I Attached AppleIntelHDGraphics* (Vanilla 10.13.6 Build 17G5019) below; also dosdude1's "PlatformSupport.plist" for using with SMBios version higher than MBP6,2 (on my case is using MBP10,1 for NightShift support) located on "/System/Library/CoreServices". Thanks.

AppleIntelHDGraphics_10.13.6.7z

 

#EDIT: ..and plz note that for KextToPatch to works, make sure prelinkedkernel && kernelcache are properly rebuilt. Also on my case, there's difference if using "BundleIdentifier" compared to "BundleExecutable" for KTP Name. The 2nd is not working on my case, so.. 

 

Use: com.apple.driver.AppleIntelHDGraphicsFB // BundleIdentifier

Not: AppleIntelHDGraphicsFB // BundleExecutable

(If you ask me why, I got no clear answer either).

 

Screenshots:

 

 


Screenshot 2019-02-05 at 15.10.22.png

Screenshot 2019-02-05 at 15.15.35.png
 

 

Edited by Badruzeus

Share this post


Link to post
Share on other sites

Hello friends with IntelHD 1 st Gen.,
... with 10.14.4 is game over with old graphics without Metal.
WindowServer no longer starts if there is no metal graphic in the system. :(

 

With 10.14.3 my laptop is still working fine.
R.I.P. with 10.14.3 :bye:

Share this post


Link to post
Share on other sites
10 minutes ago, MacPeet said:

Hello friends with IntelHD 1 st Gen.,
... with 10.14.4 is game over with old graphics without Metal.
WindowServer no longer starts if there is no metal graphic in the system. :(

 

With 10.14.3 my laptop is still working fine.
R.I.P. with 10.14.3 :bye:

Yes, currently testing 10.14.4 Beta 2 on my L645 laptop (Arrandale).

As far as can tell, not only IntelHD 1st Gen but also HD3000, Nvidia Tesla, etc.. that are not-Metal capable.

(Guessing, my Fermi GT 520M with OpenGL is the only that' s working under 10.14.4 Beta 1-2 #atm LoL).

Edited by Badruzeus

Share this post


Link to post
Share on other sites

Yes. IntelHD 1 st Gen., HD3000, all older Nvidia, my GT330M only with nv_disable=1 with 10.14.4 DP1 or 2 ...all, game over. :(

My Optiplex with GT710 Metal graphics works OOB with 10.14.4. :thumbsup_anim:

Edited by MacPeet

Share this post


Link to post
Share on other sites
7 minutes ago, MacPeet said:

Yes. IntelHD 1 st Gen., HD3000, all older Nvidia, my GT330M only with nv_disable=1 mit 10.14.4 DP1 or 2 ...all, game over. :(

My Optiplex with GT710 Metal graphics works OOB with 10.14.4. :thumbsup_anim:

Actually, it' s working.. but only, has no Display :hysterical: LoL

Share this post


Link to post
Share on other sites

Inevitable in the end... Call it a slower/softer death than what older GMA 950/X3100 or GeForce 7xxx experienced with Mountain Lion back in the days!

Edited by Hervé

Share this post


Link to post
Share on other sites

No, the way for IntelHD 1 st gen was very long. I am satisfied with it. At some point, everything comes to an end. No problem.

Share this post


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

Oh, I just realized that my last reply isn't posted on this thread.. was on Phone previously and bit bz; sorry.

 

Yes, my last attempt was using AppleIntelHDGraphics* from 10.13.6 (17G5019) and confirmed it' s working fine on 10.14.3 (SingleLink, LVDS, LW1).

 

My KextToPatch method is following Goldfish64's ArrandaleGraphicsHackintosh repo (which actually is also based on vertex & GhostRaider guides for IntelHD 1st Gen).

 

For DualLink, test & report are needed. Plz give it a try:

 


# DualLink Patch 1 (MatchOS: 10.11.x,10.12.x,10.13.x,10.14.x)
Find	:	0F 45 C8 42
Replace	:	90 90 90 42

# DualLink Patch 2 (MatchOS: 10.11.x)
Find	:	498B8424 98060000 0FB64018 C1E01341 0B466C41 89466C49 8B8C2498 00000089 810C000F 00498B84 24980600 000FB640 18C1E013 410B4668
Replace	:	418B466C 25FFFFC7 FF0D0000 00009090 90909041 89466C49 8B8C2498 00000089 810C000F 00418B46 6825FFFF C7FF0D00 00000090 90909090

# DualLink Patch 3 (MatchOS: 10.12.x,10.13.x,10.14.x)
Find	:	498B8424 98000000 8B880C00 0F004189 4E6C8B90 00010600 41895668 81C90020 00004189 4E6C8988 0C000F00 BF190000 00E80000 0000418B
Replace	:	418B466C 25FFFFC7 FF0D0000 00009090 90909041 89466C49 8B8C2498 00000089 810C000F 00418B46 6825FFFF C7FF0D00 00000090 90909090

# DualLink Patch 4 (MatchOS: 10.12.x,10.13.x,10.14.x)
Find	:	498B8424 98000000 89880C00 0F00498B 8C249806 00000FB6 5118C1E2 13418B76 6C09D641 89766C89 B00C000F 00410B56 68418956 68899000
Replace	:	418B466C 25FFFFC7 FF0D0000 00009090 90909041 89466C49 8B8C2498 00000089 810C000F 00418B46 6825FFFF C7FF0D00 00000090 90909090

=============================================================

 

I Attached AppleIntelHDGraphics* (Vanilla 10.13.6 Build 17G5019) below; also dosdude1's "PlatformSupport.plist" for using with SMBios version higher than MBP6,2 (on my case is using MBP10,1 for NightShift support) located on "/System/Library/CoreServices". Thanks.

AppleIntelHDGraphics_10.13.6.7z

 

#EDIT: ..and plz note that for KextToPatch to works, make sure prelinkedkernel && kernelcache are properly rebuilt. Also on my case, there's difference if using "BundleIdentifier" compared to "BundleExecutable" for KTP Name. The 2nd is not working on my case, so.. 

 

Use: com.apple.driver.AppleIntelHDGraphicsFB // BundleIdentifier

Not: AppleIntelHDGraphicsFB // BundleExecutable

(If you ask me why, I got no clear answer either).

 

Screenshots:

  Reveal hidden contents

 


Screenshot 2019-02-05 at 15.10.22.png

Screenshot 2019-02-05 at 15.15.35.png
 

 

 

Hi Badruzeus,

 

Apologies if I'm asking too many questione. Can you please share your clover config.plist?

 

Where did you find those Dual Link patches because I found no Dual Link patches in the repository you mentioned.

Also do I have to try one of those Dual Link patches or just try one by one all and find which one works?

 

Also, are you using MacBookPro10,1 for your computer with Intel 1st Generation Graphics? Because per this thread, the appropriate SMBIOS is off MacBookPro6,1 which is what I'm using.

 

Many thanks in advance.

Share this post


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

Apologies if I'm asking too many questione. Can you please share your clover config.plist?

Goldfish64 provides sample config.plist on his repo, mine has (almost) empty options checked bcoz using patched DSDT (guided by this thread). Will be useless on your mach, but I could attach it for reference only.

 

31 minutes ago, nijhawank said:

Where did you find those Dual Link patches because I found no Dual Link patches in the repository you mentioned.

 I made binaries comparison my self, for testing purpose. There's no guarantee it will work, that's why report is needed.

 

31 minutes ago, nijhawank said:

Also do I have to try one of those Dual Link patches or just try one by one all and find which one works?

Take a look for "MatchOS"; if using HighSierra, then Enable (select) all patches which contain "10.13.x".

 

31 minutes ago, nijhawank said:

Also, are you using MacBookPro10,1 for your computer with Intel 1st Generation Graphics? Because per this thread, the appropriate SMBIOS is off MacBookPro6,1 which is what I'm using.

Platforms with SMBios lower than MBP10,1 have been dropped by Apple since Mojave, using MBP6,2 w/o modified PlatformSupport.plist on "/System/Library/CoreServices" will prevent your mach for booting:

MacOS is not supported on this Platform

#CMIIW. Definitely, even using MBP15,1 as SMBios is also possible.. but consider about PowerManagement, non-Functional USB Ports, etc. On my case is safe with MBP10,1 (also safe for update with APFS, getting no "This software is not supported by your system" error on progress). Yeah, updating Mojave on unsupported macs will be different topics (eg. with the help of Gengik84 & PMHeart's MacOS_Updater script).

config_10.14.3_KTP.zip

Edited by Badruzeus

Share this post


Link to post
Share on other sites

@Badruzeus

 

I tried AppleIntelHDGraphics kexts from 10.13.6 (what you provided, also did a "kextcache -i /" afterwards) and the KextsToPatch entries from GoldFish64 repository. I removed all the SingleLink patches (as my screen has a resolution of 1440x900 hence requires Dual Link) and created Dual Link patches using Clover and Find/Replace entries that you provided. However, the macOS resets at the around 70% when the FB initializes.

 

Here are the KextsToPatch entries that I'm using...

			<dict>
				<key>Comment</key>
				<string>Stride patch 10.7+ x64</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				D0XIQomM
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x,10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				kJCQQomM
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>DualLink Patch 1 (MatchOS: 10.11.x,10.12.x,10.13.x,10.14.x)</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				D0XIQg==
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.11.x,10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				kJCQQg==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>DualLink Patch 2 (MatchOS: 10.11.x)</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				SYuEJJgGAAAPtkAYweATQQtGbEGJRmxJi4wkmAAAAImB
				DAAPAEmLhCSYBgAAD7ZAGMHgE0ELRmg=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.11.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				QYtGbCX//8f/DQAAAACQkJCQkEGJRmxJi4wkmAAAAImB
				DAAPAEGLRmgl///H/w0AAAAAkJCQkJA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>DualLink Patch 3 (MatchOS: 10.12.x,10.13.x,10.14.x)</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				SYuEJJgAAACLiAwADwBBiU5si5AAAQYAQYlWaIHJACAA
				AEGJTmyJiAwADwC/GQAAAOgAAAAAQYs=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				QYtGbCX//8f/DQAAAACQkJCQkEGJRmxJi4wkmAAAAImB
				DAAPAEGLRmgl///H/w0AAAAAkJCQkJA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>DualLink Patch 4 (MatchOS: 10.12.x,10.13.x,10.14.x)</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				SYuEJJgAAACJiAwADwBJi4wkmAYAAA+2URjB4hNBi3Zs
				CdZBiXZsibAMAA8AQQtWaEGJVmiJkAA=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				QYtGbCX//8f/DQAAAACQkJCQkEGJRmxJi4wkmAAAAImB
				DAAPAEGLRmgl///H/w0AAAAAkJCQkJA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Link width 1 patch 10.12-10.13</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				QYlObEmLhCSYAAAAiYgMAA8ASYuMJJgGAAAPtlEYweIT
				QYt2bAnWQYl2bImwDAAPAEELVmg=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				u///x/+6AAAAACHZCdFBiU5sSYuEJJgAAACJiAwADwBB
				i05oIdkJ0YnKkJCQSYuMJJgGAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Link width 2 patch 10.12-10.13</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				QYlObEmLhCSYAAAAiYgMAA8ASYuMJJgGAAAPtlEYweIT
				QYt2bAnWQYl2bImwDAAPAEELVmg=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				u///x/+6AAAIACHZCdFBiU5sSYuEJJgAAACJiAwADwBB
				i05oIdkJ0YnKkJCQSYuMJJgGAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Link width 3 patch 10.12-10.13</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				QYlObEmLhCSYAAAAiYgMAA8ASYuMJJgGAAAPtlEYweIT
				QYt2bAnWQYl2bImwDAAPAEELVmg=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				u///x/+6AAAQACHZCdFBiU5sSYuEJJgAAACJiAwADwBB
				i05oIdkJ0YnKkJCQSYuMJJgGAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Link width 4 patch 10.12-10.13</string>
				<key>Disabled</key>
				<true/>
				<key>Find</key>
				<data>
				QYlObEmLhCSYAAAAiYgMAA8ASYuMJJgGAAAPtlEYweIT
				QYt2bAnWQYl2bImwDAAPAEELVmg=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.12.x,10.13.x,10.14.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				u///x/+6AAAYACHZCdFBiU5sSYuEJJgAAACJiAwADwBB
				i05oIdkJ0YnKkJCQSYuMJJgGAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Disable FBCControl patch</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				RkJDQ29udHJvbAA=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				WFhYQ29udHJvbAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Disable FeatureControl patch</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				RmVhdHVyZUNvbnRyb2wA
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>Name</key>
				<string>com.apple.driver.AppleIntelHDGraphicsFB</string>
				<key>Replace</key>
				<data>
				WFhYdHVyZUNvbnRyb2wA
				</data>
			</dict>

 

Share this post


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

@Badruzeus

 

I tried AppleIntelHDGraphics kexts from 10.13.6 (what you provided, also did a "kextcache -i /" afterwards) and the KextsToPatch entries from GoldFish64 repository. I removed all the SingleLink patches (as my screen has a resolution of 1440x900 hence requires Dual Link) and created Dual Link patches using Clover and Find/Replace entries that you provided. However, the macOS resets at the around 70% when the FB initializes.

Try changing this on your config:

<dict>
	<key>Comment</key>
	<string>DualLink Patch 2 (MatchOS: 10.11.x)</string>
	<key>Disabled</key>
	<true/>
  	...
</dict>

If it still won't work, neither me know how to. On my case is using SingleLink (1366x768).

 

#EDIT: Ah, but above change doesn't make sense, since you're using "MatchOS=10.11.x". I have no idea then.

Edited by Badruzeus

Share this post


Link to post
Share on other sites

@Badruzeus

 

I fixed the problem by removing the dual link patches. They are not required as the kexts are by default for dual link and we need single link patches. If one has dual link, no need for any patches.

 

Thanks for your help else I'd have stuck with that weird flicker. 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)

Share this post


Link to post
Share on other sites

 

Hello! I have a problem. Install the framebuffer until you get the macOS booted. and now the screen was distorted by having put the LW1. Try to inject the kext of intelHD from the clover as the past times and it does not fit, I can not access the macOS in any way. What I can do?

I have the High Sierra and everything was fine until I selected that Framebuffer. What I did to jump bootlop was to inject the Intel HD from the Clover. But now that solution no longer works for me and the screen is still distorted. I have an Intel Core i3-370M and it is an HP G42 with its factory display. Until now I came to Alternative 2 IOPCI and it was because it could pass the bootlop, but it distorted

Edited by RyuDragon
Lack of information

Share this post


Link to post
Share on other sites

Hey guys can you told me how to get Mac os high Sierra USB installer for Intel first gen .

I tried making USB installer but after dsmos arrived it says 

Unsupported CPU

Unsupported PCH

 

And after that some strange type graphics come on screen.

 

 

Specs : i5-520m

              Lenovo g560

 

 

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 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
×