Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not an issue, but a suggestion. #39

Closed
naorunaoru opened this issue Jul 20, 2016 · 15 comments
Closed

Not an issue, but a suggestion. #39

naorunaoru opened this issue Jul 20, 2016 · 15 comments

Comments

@naorunaoru
Copy link

naorunaoru commented Jul 20, 2016

        <key>ig-platform-id</key>
        <string>0x0a260006</string>

You have this piece of code in your Clover's config. That didn't work well on my V5-573g (i5-4200U, HD4400, FullHD display).
I've dug into some specs and found that i5-4200U's HD4400 has GT2 core (source), so the closest platform id is 0x0a16000c - Haswell ULT Mobile GT2 (source). That worked perfectly with 4k@30fps over HDMI with no graphics corruption and kernel panics.

You can add this info to your README if you like.

Oh and injecting ig-platform-id in SSDT didn't work at all.

@naorunaoru
Copy link
Author

Another working ig-platform-id is 0x0a2e0008 - Haswell ULT E GT3.

@Kaijun
Copy link
Owner

Kaijun commented Jul 20, 2016

I don't know what happened if you took 0x0a260006? Did the graphic still work with animations and effects? but only not compatible with 4k? or all things with graphic just don't work completely?

As i know, most HD4400/HD4600 devices are using 0x0a260006, i also tried some of other codes at the very beginning when i was hackintoshing this laptop, but only 0x0a260006 works... I can't remember if i have tried these two codes you mentioned.

And one more thing, i also injected the this codes into the SSDT-2, check the _DSM method under the IGUP device. Maybe Clover will override it with the code defined inside Clover.

@naorunaoru
Copy link
Author

0x0a26006 caused my menubar to glitch out with funny colors and sometimes I had KPs with AppleIntelFramebuffer as a reason. 4k also did not work.

About SSDT-2 injection: I've tried injecting platform-id into SSDT-5 (that's where my IGPU lies) and it didn't show up properly in IORegistryExplorer.

@Kaijun
Copy link
Owner

Kaijun commented Jul 20, 2016

which version of OSX r u running? 10.10?

@naorunaoru
Copy link
Author

10.11.5 (15F34).

@Kaijun
Copy link
Owner

Kaijun commented Jul 20, 2016

yes, i just came up with the issues submitted two years ago, #8 (comment)
and #14

They may have the same problem as yours.

it seems that 0x0a260006 is not universal for all HD4400 devices, and i also have no idea if the id u mentioned is suitable for me. I would try later. If it is the best one indeed, i'll update the repo 😄

@Kaijun
Copy link
Owner

Kaijun commented Jul 20, 2016

are u simply using my DSDT/SSDT or ur own files?

u said that IORegistryExplorer doesn't recognised your ig-platform-id. The reason could be wrong modification of DSDT/SSDTs.

@Kaijun
Copy link
Owner

Kaijun commented Jul 20, 2016

If u r interested in modifying ur own DSDT/SSDTs, a brief tutorial could be found here: https://github.com/Kaijun/Acer-V5-573g-DSDT

@naorunaoru
Copy link
Author

naorunaoru commented Jul 20, 2016

I'm using my own DSDT patched roughly according to your guide.

@Kaijun
Copy link
Owner

Kaijun commented Jul 20, 2016

Then injecting ig-platform-id through SSDT should have worked. No idea, but yeah, you can also keep staying with the clover configuration 😄

@naorunaoru
Copy link
Author

Yeah, in the end it works so I don't see any reason to bother. :)

@ghost
Copy link

ghost commented Jul 22, 2016

any ideas how convert this 0x0a16000c to such style 0x06, 0x00, 0x26, 0x0a, so we can insert iy to SSDT file ?

@Kaijun
Copy link
Owner

Kaijun commented Jul 22, 2016

@Virusak
it's reversed with each Byte actually
0x0a260006 -> 0x06, 0x00, 0x26, 0x0A
so
0x0a16000c -> 0x0C, 0x00, 0x16, 0x0A
and
0x0a2e0008 -> 0x08, 0x00, 0x2e, 0x0A

@ghost
Copy link

ghost commented Jul 22, 2016

@Kaijun Thank you!

Kaijun added a commit that referenced this issue Jul 22, 2016
Kaijun added a commit that referenced this issue Jul 22, 2016
@Kaijun
Copy link
Owner

Kaijun commented Jul 22, 2016

i had tried 0x0a16000c for a while, seems good!
changed the ig-platform-id overall both in config.plist and SSDT
Thx again!

@Kaijun Kaijun closed this as completed Jul 22, 2016
@Kaijun Kaijun reopened this Jul 31, 2016
@Kaijun Kaijun closed this as completed Aug 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants