-
Notifications
You must be signed in to change notification settings - Fork 29
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
Comments
Another working ig-platform-id is 0x0a2e0008 - Haswell ULT E GT3. |
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 |
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. |
which version of OSX r u running? 10.10? |
10.11.5 (15F34). |
yes, i just came up with the issues submitted two years ago, #8 (comment) 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 😄 |
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. |
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 |
I'm using my own DSDT patched roughly according to your guide. |
Then injecting ig-platform-id through SSDT should have worked. No idea, but yeah, you can also keep staying with the clover configuration 😄 |
Yeah, in the end it works so I don't see any reason to bother. :) |
any ideas how convert this 0x0a16000c to such style 0x06, 0x00, 0x26, 0x0a, so we can insert iy to SSDT file ? |
@Virusak |
@Kaijun Thank you! |
i had tried 0x0a16000c for a while, seems good! |
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.
The text was updated successfully, but these errors were encountered: