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

[juanerson]

Maybe is something related to the OSBundleRequired "Safe Boot" present in the vanilla "Info.plist"? Maybe changing to "Root" this line. Sorry, I don't have installed clover, YET. No UEFI bios here on my laptop, but I want to try it soon if is possible (legacy mode?).

[GhostRaider]

Maybe is something related to the OSBundleRequired "Safe Boot" present in the vanilla "Info.plist"? Maybe changing to "Root" this line. Sorry, I don't have installed clover, YET. No UEFI bios here on my laptop, but I want to try it soon if is possible (legacy mode?).

 

I have Clover installed on a 200MB EFI partition that I created when I reformatted my whole hard drive. This was a long time ago. For sure I'm not using UEFI since I remember I checked the boxes that mentioned older support for BIOS in the Clover Installer.

[GhostRaider]

Okay, I wanted to see if the Clover's infoplist patch was detecting the information from the info.plist file so I messed with the config.plist file. Something seems wrong:

 

 

We know that it's suppose to detect PowerStates with a value of 1. If I mess with the config.plist and change it to find 12345 and changes it to 01234, it says patched, even though there is no such value in the AppleIntelHDGraphicsFB info.plist.

 

It's not verifying the actual values in the info.plist for some reason.

[Slice]

 

 

Hey Slice, so I noticed that the infoplist patch code you posted only works on this Clover X64 (3127) release. I tried it on an older version of Clover and it doesn't work. Its no problem.

 

The good news is that it appears that Clover has found the string and then it successfully patches it. But there is a problem. 

 

Sadly, the infoplist patch doesn't actually patch it. My computer freezes during boot when PowerStates is set to 1, so either the infoplist patch isn't working or the code being written to memory is not correct. I did notice that it adds a space when it patches it as seen in the screenshot. I'm not sure if thats a problem. 

 

If I modify the kext to have power states = 0, the computer boots correctly with the other kext patches.

 

Is there a way to check if the infoplist patch is actually working in this type of situation? For example, I can change "Watermarks" from 1 to 0 and it won't affect my computer when it boots. But once I boot into the desktop, I would like to see if this value actually changed correctly. Not sure if its possible.

Yes, 3127+ revision is able to patch infoplist. But I afraid this patch is not fully correct. I not invented how to check it rather then in real attempts.

For example we can change some unneeded kext to be loaded and see this in verbose boot.

 

 

Maybe is something related to the OSBundleRequired "Safe Boot" present in the vanilla "Info.plist"? Maybe changing to "Root" this line. Sorry, I don't have installed clover, YET. No UEFI bios here on my laptop, but I want to try it soon if is possible (legacy mode?).

 

Why not? Clover works in legacy mode even better then in UEFI mode because it contains bug-free UEFI 2.4.0 while BIOS contains old and buggy UEFI 2.0.

Long time I was using legacy Clover until resolve sleep issue with UEFI boot.

UEFI boot has advantage with real NVRAM that makes possible to save panic-log.

Okay, I wanted to see if the Clover's infoplist patch was detecting the information from the info.plist file so I messed with the config.plist file. Something seems wrong:

 

 

 

We know that it's suppose to detect PowerStates with a value of 1. If I mess with the config.plist and change it to find 12345 and changes it to 01234, it says patched, even though there is no such value in the AppleIntelHDGraphicsFB info.plist.

So will work further...

[GhostRaider]

Is there anything else to try at the moment or will this get fixed in later releases of Clover? Patching the binary values works great, the infoplist patch was the only thing left to allow people here, including myself to boot OS X without needing to remove these kexts everytime there is a new update.

[Slice]

Is there anything else to try at the moment or will this get fixed in later releases of Clover? Patching the binary values works great, the infoplist patch was the only thing left to allow people here, including myself to boot OS X without needing to remove these kexts everytime there is a new update.

I will be on holidays so there be will very long waiting. May be other developers do anything.

I may advice you to create legacy.kext

[juanerson]

This legacy worked for me (see IOReg). At least in Yosemite:

Note: It has only one change to "PowerStates = 0", but you can play with the rest of parameters inside "FBCControl" and "FeatureControl". For example all to "0" and see what happens. I tested, and this is absolutely free of risks.

LegacyIntelHDGraphicsFB.kext.zip

Edited January 15, 2015 by juanerson

[rizki_alkaf]

This legacy worked for me (see IOReg). At least in Yosemite:

Captura de pantalla 2015-01-14 a las 1.26.14.png

So, how to do this? I'm using Giofrida patch now, with single link, LW x4, LVDS+VGA, normal mode

[giofrida]

Hello to everyone. It's been a long time since I logged in the forum. Now that I've some more time I can help you.

I've just seen Clover patches, maybe you're interested in the binary patterns, aren't you?

Anyway, here they are:

- for kext version prior 10.8.5 the app uses verteks' utility

- for kext version after 10.8.5 (included) the app patches the kext with these binary patterns (the first line is the one you have to find, the second line is the one you have to replace)

I divided the patches in some categories to be as clearer as possible:

 

- General patch (for all the configurations):

0F 45 C8 42 89 8C 33 F0 01 00
90 90 90 42 89 8C 33 F0 01 00

- Singlelink patches:

- Singlelink patch 1:

- from 10.8.5 to 10.9.x:

C7 03 01 00 00 00 C7 43 20 00
C7 03 00 00 00 00 C7 43 20 00

- for 10.10.x only

C7 07 01 00 00 00 41 C7 47 20
C7 07 00 00 00 00 41 C7 47 20

- from 10.11.x on

C7 03 01 00 00 00 48 B8 0A
C7 03 00 00 00 00 48 B8 0A

- Singlelink patch 2

- for 10.8.5 only:

B9 00 00 00 09 C7 85 60 FF FF
B9 00 00 00 08 C7 85 60 FF FF

- for 10.9.x only:

41 B9 00 60 00 09 BA 00 60 00 04 C7 85 5C FF FF
41 B9 00 60 00 08 BA 00 60 00 04 C7 85 5C FF FF 

- from 10.10.x on

FF B8 00 60 00 09 BE 00 60 00 04 0F 44 F0 09 D6
FF B8 00 60 00 08 BE 00 60 00 04 0F 44 F0 09 D6

- Singlelink patch 3 (all configurations):

3C 03 30 80
00 03 30 80 

- Linkwidth patches (for both singlelink and duallink systems):

-Linkwidth x1

49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 6C 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 68
41 8B 46 6C 25 FF FF C7 FF 0D 00 00 00 00 90 90 90 90 90 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 41 8B 46 68 25 FF FF C7 FF 0D 00 00 00 00 90 90 90 90 90 

- Linkwidth x2

49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 6C 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 68
41 8B 46 6C 25 FF FF C7 FF 0D 00 00 08 00 90 90 90 90 90 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 41 8B 46 68 25 FF FF C7 FF 0D 00 00 08 00 90 90 90 90 90 

- Linkwidth x3

49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 6C 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 68
41 8B 46 6C 25 FF FF C7 FF 0D 00 00 10 00 90 90 90 90 90 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 41 8B 46 68 25 FF FF C7 FF 0D 00 00 10 00 90 90 90 90 90 

- Linkwidth x4

49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 6C 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 68
41 8B 46 6C 25 FF FF C7 FF 0D 00 00 18 00 90 90 90 90 90 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 41 8B 46 68 25 FF FF C7 FF 0D 00 00 18 00 90 90 90 90 90

- Linkwidth x1 for 10.12.x only (UNTESTED)

41 8B 4E 6C 83 C9 10 41 89 4E 6C 49 8B 84 24 98 00 00 00 89 88 0C 00 0F 00 49 8B 8C 24 98 06 00 00 0F B6 51 18 C1 E2 13 41 8B 76 6C 09 D6 41 89 76 6C 89 B0 0C 00 0F 00 41 0B 56 68
B9 FF FF C7 FF BB 00 00 00 00 41 8B 56 6C 83 CA 10 21 CA 09 DA 41 89 56 6C 49 8B 84 24 98 00 00 00 89 90 0C 00 0F 00 41 0B 56 68 21 CA 09 DA 90 90 90 90 90 49 8B 8C 24 98 06 00 00 

- Linkwidth x2 for 10.12.x only (UNTESTED)

41 8B 4E 6C 83 C9 10 41 89 4E 6C 49 8B 84 24 98 00 00 00 89 88 0C 00 0F 00 49 8B 8C 24 98 06 00 00 0F B6 51 18 C1 E2 13 41 8B 76 6C 09 D6 41 89 76 6C 89 B0 0C 00 0F 00 41 0B 56 68
B9 FF FF C7 FF BB 00 00 08 00 41 8B 56 6C 83 CA 10 21 CA 09 DA 41 89 56 6C 49 8B 84 24 98 00 00 00 89 90 0C 00 0F 00 41 0B 56 68 21 CA 09 DA 90 90 90 90 90 49 8B 8C 24 98 06 00 00 

- Linkwidth x3 for 10.12.x only (UNTESTED)

41 8B 4E 6C 83 C9 10 41 89 4E 6C 49 8B 84 24 98 00 00 00 89 88 0C 00 0F 00 49 8B 8C 24 98 06 00 00 0F B6 51 18 C1 E2 13 41 8B 76 6C 09 D6 41 89 76 6C 89 B0 0C 00 0F 00 41 0B 56 68
B9 FF FF C7 FF BB 00 00 10 00 41 8B 56 6C 83 CA 10 21 CA 09 DA 41 89 56 6C 49 8B 84 24 98 00 00 00 89 90 0C 00 0F 00 41 0B 56 68 21 CA 09 DA 90 90 90 90 90 49 8B 8C 24 98 06 00 00 

- Linkwidth x4 for 10.12.x only (UNTESTED)

41 8B 4E 6C 83 C9 10 41 89 4E 6C 49 8B 84 24 98 00 00 00 89 88 0C 00 0F 00 49 8B 8C 24 98 06 00 00 0F B6 51 18 C1 E2 13 41 8B 76 6C 09 D6 41 89 76 6C 89 B0 0C 00 0F 00 41 0B 56 68
B9 FF FF C7 FF BB 00 00 18 00 41 8B 56 6C 83 CA 10 21 CA 09 DA 41 89 56 6C 49 8B 84 24 98 00 00 00 89 90 0C 00 0F 00 41 0B 56 68 21 CA 09 DA 90 90 90 90 90 49 8B 8C 24 98 06 00 00

- Ports patches:

- VGA:

30 49 01 11 01 10 08 00
30 49 01 11 04 10 08 00

30 49 01 01 01 00 08 00
30 49 01 01 04 00 08 00

- DP:

30 49 01 11 01 10 08 00
30 49 01 11 10 10 08 00

30 49 01 01 01 00 08 00
30 49 01 01 10 00 08 00

- LVDS + VGA:

30 49 01 11 01 10 08 00
30 49 01 11 05 10 08 00

30 49 01 01 01 00 08 00
30 49 01 01 05 00 08 00

- LVDS + DP:

30 49 01 11 01 10 08 00
30 49 01 11 11 10 08 00

30 49 01 01 01 00 08 00
30 49 01 01 11 00 08 00

- VGA + DP:

30 49 01 11 01 10 08 00
30 49 01 11 14 10 08 00

30 49 01 01 01 00 08 00
30 49 01 01 14 00 08 00

So, for example, if you want to patch the kext with these parameters: Singlelink, X1, LVDS you have to use General patch, Singlelink patch 1, Singlelink patch 2, Singlelink patch 3 and Linkwidth X1.

For a duallink configuration with linkwidth X4 and LVDS+VGA you have to use General patch, Linkwidth X4 and LVDS+VGA.

 

Maybe next time I will add the x86 assembly instructions linked with these binary patterns (it's already documented in verteks' patcher but of course it's not updated to Yosemite version).

 

Just a question: what are PowerStates used for?

 

Bye, guys, keep up the good work! 

Edited January 27, 2017 by giofrida

[GhostRaider]

@Giofrida

 

Hey thanks for posting this. The original idea was to use Clover's on the fly patching process so that we can all boot OS X with the native kexts. That way we would never have to deal with deleting and reinstalling, all that painful process. 

 

The binary patches work correctly since I tested them out. The problem is that the info.plist patch does not work in Clover, which defeats the purpose of patching the kext on the fly. I'm not sure how many people don't need the info.plist patch but from what I've seen, a lot of people need the framebuffer with PowerStates = 0. 

 

Without this working, we can't use this method sadly so I decided not to write about it in the guide. It would confuse people and probably break their hackintosh. As for what PowerState does, I don't really know. I have to disable it or else my computer will freeze during boot. I'm just guessing but maybe PowerStates enables the "Power States" of the IGPU. That could be the key to maybe increasing performance but I don't know why some computers freeze with this enabled. 

 

By the way, how does one find out what to patch in the IntelHDGraphicsFB? How does one know that these HEX values control SingleLink, Linkwidth, etc? How did Verteks manage to find all of this out on his own? lol 

 

As mentioned by Juanerson, the other approach is to use what's called a Legacy Kext. This would only work when you have OS X installed and working. It would not work if you are booting to the OS X installer. 

[giofrida]

@Giofrida

 

Hey thanks for posting this. The original idea was to use Clover's on the fly patching process so that we can all boot OS X with the native kexts. That way we would never have to deal with deleting and reinstalling, all that painful process.

 

The binary patches work correctly since I tested them out. The problem is that the info.plist patch does not work in Clover, which defeats the purpose of patching the kext on the fly. I'm not sure how many people don't need the info.plist patch but from what I've seen, a lot of people need the framebuffer with PowerStates = 0.

 

Without this working, we can't use this method sadly so I decided not to write about it in the guide. It would confuse people and probably break their hackintosh. As for what PowerState does, I don't really know. I have to disable it or else my computer will freeze during boot. I'm just guessing but maybe PowerStates enables the "Power States" of the IGPU. That could be the key to maybe increasing performance but I don't know why some computers freeze with this enabled.

 

By the way, how does one find out what to patch in the IntelHDGraphicsFB? How does one know that these HEX values control SingleLink, Linkwidth, etc? How did Verteks manage to find all of this out on his own? lol

 

As mentioned by Juanerson, the other approach is to use what's called a Legacy Kext. This would only work when you have OS X installed and working. It would not work if you are booting to the OS X installer.

No problem dude. I should have done that a lot of time ago.

Thanks for your exhaustive explanations of the latest news.

I really don't know how verteks found all the x86 instructions to edit. It's not impossible using a decompiler such as IDA but it could be very hard if you don't have doumentations. In my opinion, he's working for Apple. But he weirdly disappeared from the community just after releasing the patcher and the useful documentations.

It's just for him if we can use our notebooks with the Intel GPU.

[GhostRaider]

No problem dude. I should have done that a lot of time ago.

Thanks for your exhaustive explanations of the latest news.

I really don't know how verteks found all the x86 instructions to edit. It's not impossible using a decompiler such as IDA but it could be very hard if you don't have doumentations. In my opinion, he's working for Apple. But he weirdly disappeared from the community just after releasing the patcher and the useful documentations.

It's just for him if we can use our notebooks with the Intel GPU.

 

Same, I believe he's working for Apple lol. Maybe he had a similar laptop with this IGPU so he decided to help us. One thing that concerns me about this 1st Generation Intel HD Graphics IGPU is its future. The problem is that Apple is shifting to OpenGL 3.0+ and this IGPU only supports up to OpenGL 2.1. We can see an example of this in Apple Maps (Yosemite) and the latest release of Pixelmator. Both of these apps display a white background. These apps probably use the Core profile which 1st Gen Intel HD Graphics doesn't have.

[4520s]

Hello all the brilliant people!

 

I managed QE on an external monitor with the LCD+VGA kext and a DSDT edit with the help of your guide. Now the only problem that remains is that the external monitor doesn't turn off when the display sleeps. I get a black screen with the display completely turned on. I use my laptop as an always on server and don't need the display most of the time so I need it to turn off automatically to save power.
 

Any help would be greatly appreciated. (sorry for the poor language)

[rizki_alkaf]

Hello all the brilliant people!

 

I managed QE on an external monitor with the LCD+VGA kext and a DSDT edit with the help of your guide. Now the only problem that remains is that the external monitor doesn't turn off when the display sleeps. I get a black screen with the display completely turned on. I use my laptop as an always on server and don't need the display most of the time so I need it to turn off automatically to save power.

 

Any help would be greatly appreciated. (sorry for the poor language)

So you're using external monitor with a clamshell mode? how is it going? Is it buggy? Any problems with the performance?

What DSDT edit you use to make this work?

[4520s]

So you're using external monitor with a clamshell mode? how is it going? Is it buggy? Any problems with the performance?

What DSDT edit you use to make this work?

 

Its not buggy at all! works really well and the performance is as good as can be expected from a 1st gen core i3.

I used the edits mentioned in the guide for using in clamshell mode.

I boot my laptop with the lid open. BIOS, chameleon & Apple logo are all displayed on the internal display and when OS X loads the framebuffer, it transfers to the external display. Now another problem is that when the display shifts, the internal LCD stays on also as black and does not turn off. Now I can close the lid to turn the internal display off.

Also if I turn on my laptop with the lid closed the BIOS shifts to the external display and everything after it but that ends with a blank white screen. I have never managed to make it work this way. All this means is every time I boot I have to be physically present to open & close the lid and can't use wake on LAN. And like I said before I prefer it as a server that makes wake on lan an essential feature.

 

So if there was a way to turn the lcd off when the framebuffer loads that would be the best since that way I can keep the lid always open. Or if I could boot directly from the external display i.e. with the lid closed that would work too. I just need to know how?

 

Again any help is greatly appreciated!

[warraisraw]

Hello to everyone. It's been a long time since I logged in the forum. Now that I've some more time I can help you.

I've just seen Clover patches, maybe you're interested in the binary patterns, aren't you?

Anyway, here they are:

- for kext version prior 10.8.5 the app uses verteks' utility

- for kext version after 10.8.5 (included) the app patches the kext with these binary patterns (the first line is the one you have to find, the second line is the one you have to replace)

I divided the patches in some categories to be as clearer as possible:

 

- General patch (for all the configurations):

0F 45 C8 42 89 8C 33 F0 01 00
90 90 90 42 89 8C 33 F0 01 00

- Singlelink patches:

- Singlelink patch 1 (for yosemite):

C7 07 01 00 00 00 41 C7 47 20
C7 07 00 00 00 00 41 C7 47 20

- Singlelink patch 2 (for yosemite):

FF B8 00 60 00 09 BE 00 60 00 04 0F 44 F0 09 D6
FF B8 00 60 00 08 BE 00 60 00 04 0F 44 F0 09 D6

- Singlelink - linkwidth x1

49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 6C 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 49 8B 84 24 98 06 00 00 0F B6 40 18 C1 E0 13 41 0B 46 68
41 8B 46 6C 25 FF FF C7 FF 0D 00 00 00 00 90 90 90 90 90 41 89 46 6C 49 8B 8C 24 98 00 00 00 89 81 0C 00 0F 00 41 8B 46 68 25 FF FF C7 FF 0D 00 00 00 00 90 90 90 90 90 

So, for example, if you want to patch the kext with these parameters: Singlelink, X1, LVDS you have to use General patch, Singlelink patch 1, Singlelink patch 2 and Singlelink Linkwidth X1.

For a duallink configuration with linkwidth X4 and LVDS+VGA you have to use General patch, Duallink linkwidth X4 and LVDS+VGA.

 

Maybe next time I will add the x86 assembly instructions linked with these binary patterns (it's already documented in verteks' patcher but of course it's not updated to Yosemite version).

 

Just a question: what are PowerStates used for?

 

Bye, guys, keep up the good work! 

 

Hi, I've applied the patches (with Clover) for SingleLink, X1, LVDS and I get pixelated screen. I applied the hex values in the post. 

I used the wrong values?

 

Note: If I take a screenshot don't show pixelated screen. 

 

Regards.

[vusun123]

@Giofrida for what kext do we apply the patch to ? AFAIK you patch the AppleIntelHDGraphicsFB.kext, but what about the others, just like each zip you make for each specific OS ?

[GhostRaider]

 

Hi, I've applied the patches (with Clover) for SingleLink, X1, LVDS and I get pixelated screen. I applied the hex values in the post. 

I used the wrong values?

 

Note: If I take a screenshot don't show pixelated screen. 

 

Regards.

 

 

Example, assuming you need LCD+VGA, SingleLink LW1, Yosemite patch for Clover (You must apply all patches listed): 

 

General Patch

Find: 0F45C842898C33F00100
Replace: 90909042898C33F00100 

LVDS+VGA Patch 1

Find: 3049011101100800
Replace: 3049011105100800 

LVDS+VGA Patch 2

Find: 3049010101000800
Replace: 3049010105000800

SingleLink Patch 1

Find: C7070100000041C74720
Replace: C7070000000041C74720

SingleLink Patch 2

Find: 3C033080
Replace: 00033080

SingleLink LW1

Find: 498B8424980600000FB64018C1E013410B466C4189466C498B8C249800000089810C000F00498B8424980600000FB64018C1E013410B4668

Replace: 418B466C25FFFFC7FF0D0000000090909090904189466C498B8C249800000089810C000F00418B466825FFFFC7FF0D000000009090909090

Yosemite Patch

Find: FFB800600009BE006000040F44F009D6
Replace: FFB800600008BE006000040F44F009D6

Spaces are removed because Clover only wants the hex values.

 

 

@Giofrida for what kext do we apply the patch to ? AFAIK you patch the AppleIntelHDGraphicsFB.kext, but what about the others, just like each zip you make for each specific OS ?

 

The information he posted is to patch the AppleIntelHDGraphicsFB.kext on the fly with Clover. I'm the one that makes those packages in InsanelyMac Downloads and the kexts you see inside that package are only there if you have deleted them or if you just want to start fresh. They are the original kexts that come with every release of OS X. The only thing that is patched is the framebuffer.

[vusun123]

So I decided to test out one of my nephew's old laptop. First off, I didn't test OTF patch yet, as I need to know which framebuffer I need first, and Alternate 1 LW1 is what I need. Then I proceed with a clean install, using OTF, surprise that it didn't work ( it booted in with no QE, CI works ). I remembered that when testing framebuffer, I need AppleIntelHDGraphicsFB to be " kernel backtrace " in order for it to work. Is something wrong here ?

[warraisraw]

SingleLink Patch 2

Find: 3C033080
Replace: 00033080

 

 

Thanks, that patch made the difference, now the screen is ok. 

 

Regards.

[giofrida]

 

Thanks, that patch made the difference, now the screen is ok. 

 

Regards.

 

 

I infact forgot some of the patches GhostRaider wrote. I updated my post with the ones I forgot. Now it should be ok for the on-the-fly patching.

[derek.zhu]

I infact forgot some of the patches GhostRaider wrote. I updated my post with the ones I forgot. Now it should be ok for the on-the-fly patching.

can you test it and post your work here if it indeed works plz?

[giofrida]

I'm sorry, but I don't understand what I should test. However this is the link of the patches: http://www.insanelymac.com/forum/index.php?/topic/286092-[GUIDE]-1st-Generation-Intel-HD-Graphics-QE/CI#entry2103034

[viloulo]

Hello,

 

First, congrats for this wonderful guide!! It was awesome to be able to use my Intel HD with QE/CI fully enabled!! I was even able to have QE/CI on an Intel P6100 before, even though now I have an Intel Core i3 350-m on my Lenovo ideapad z460.

 

I was wondering if you guys could help me wiith Clover Legacy. (I think my laptop can't boot pure UEFI).

 

I have Yosemite installed, and the only component not working is my ethernet card (unsupported - some kexts work, but they all cause random kernel panics).

 

My problem is using Clover and the patched Intel HD graphics kexts for 10.10.

 

The kexts work perfectly with Chameleon, but I can't get them to work if I use Clover.  I have made sure that config.plist has no Intel injection, and that VBios is patched.

 

I always used Single-Link - Normal - LCD+VGA - LW1 and the framebuffer is perfect with Chameleon, but with Clover the screen is scrambled, unusable.  Is there anything I need to do in order to use Clover?  Can someone point me in the right direction?

 

Thanks a bunch!! 

 

Lenovo ideapad z460

Intel Core i3 350-m

 

[warraisraw]

Hello,

 

First, congrats for this wonderful guide!! It was awesome to be able to use my Intel HD with QE/CI fully enabled!! I was even able to have QE/CI on an Intel P6100 before, even though now I have an Intel Core i3 350-m on my Lenovo ideapad z460.

 

I was wondering if you guys could help me wiith Clover Legacy. (I think my laptop can't boot pure UEFI).

 

I have Yosemite installed, and the only component not working is my ethernet card (unsupported - some kexts work, but they all cause random kernel panics).

 

My problem is using Clover and the patched Intel HD graphics kexts for 10.10.

 

The kexts work perfectly with Chameleon, but I can't get them to work if I use Clover.  I have made sure that config.plist has no Intel injection, and that VBios is patched.

 

I always used Single-Link - Normal - LCD+VGA - LW1 and the framebuffer is perfect with Chameleon, but with Clover the screen is scrambled, unusable.  Is there anything I need to do in order to use Clover?  Can someone point me in the right direction?

 

Thanks a bunch!! 

 

Lenovo ideapad z460

Intel Core i3 350-m

Hi, probably you need inject the AAPL,os-info with Clover (if you aren't using dsdt injection).

 

This is the code: 

600000000100000001000000540000000100000002010c00d041030a000000000101060000027fff04001e0000004100410050004c002c006f0073002d0069006e0066006f0000001800000030490111011008000001000000000000ffffffff

(In Clover Configurator go to "Devices", paste the code in "Properties" and mark "Inject")

 

Regards.