Tue Bui Posted July 16, 2013 Share Posted July 16, 2013 Hi everyone. I'm currently trying to install ML 10.8.4 in my just bought laptop. I have an old version of this laptop series that is the R830 integrated sandy bridge CPU, which I installed successfully ML 10.8.4 and have been using for over a year. But things become complicated in this new one with HD 4000 in it. I can boot in the safe mode and also in a normal mode without AppleIntelGraphicsHD4000 there. I couldn't get to the login screen If I ignored the kernel cache. I get stuck right here without any noticeable errors, so don't know how to fix now after trying inject device properties into DSDT, boot.plist, patched AppleintelFramebufferFB (or maybe i didn't do it right). SO, any help would be much appreciated. I attached files DSDT and smbios, boot.plist, system log for your reference. Let me know if you need anything else. Thanks r935.zip Link to comment Share on other sites More sharing options...
artur_pt Posted July 16, 2013 Share Posted July 16, 2013 hello the error is graphics u only have hd 4000 ? have u try to boot with GraphicsEnabler=No or remove or rename the *caprifb.kext and boot -f -v GraphicsEnabler=No about the intel hd 4000 Intel HD 4000 good hack Link to comment Share on other sites More sharing options...
Tue Bui Posted July 16, 2013 Author Share Posted July 16, 2013 hello the error is graphics u only have hd 4000 ? have u try to boot with GraphicsEnabler=No or remove or rename the *caprifb.kext and boot -f -v GraphicsEnabler=No about the intel hd 4000 Intel HD 4000 good hack Hi there, thanks for helping. First, HD 4000 is the only graphic card the laptop has. Second: I did read the instructions for installing HD4000 via the link before. Using "aapl, ig-platform-id" injection in the boot.plist makes me stuck at the NTFS scanning as you've seen in the pic above. I did try to patch DSDT as well, and thought It could be closer to the solution than using EFI string because It could get through the NTFS scanning above, but I got the black screen. Searching through different hackintosh sites, some said that *capriFB.kext needs patching as the graphics outputs in the wrong pipe or so. I used the new DSDT that has the platform-id 01660003 in it (did try 0004, 0001, 0000 too): Device (GFX0) { Name (_ADR, 0x00020000) Method (_DSM, 4, NotSerialized) { Store (Package (0x0A) { "@0,built-in", Buffer (One) { 0x01 }, "AAPL00,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "device-id", Buffer (0x04) { 0x66, 0x01, 0x00, 0x00 }, "AAPL,ig-platform-id", Buffer (0x04) { 0x03, 0x00, 0x66, 0x01 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Again, appreciated your help. I tried GraphicsEnabler=No or delete *capri.kext but nothing changed Link to comment Share on other sites More sharing options...
artur_pt Posted July 16, 2013 Share Posted July 16, 2013 hello try to use Clover to boot.. many have sucess with ... u can prepare a pen to test if any sucess install it in the hd, u can try in legacy boot or uefi must read how to.. clover config all new good hack Link to comment Share on other sites More sharing options...
Tue Bui Posted July 17, 2013 Author Share Posted July 17, 2013 Have tried, but get still the same problem: Black screen. It seems like the graphics card was loaded but the internal display couldn't show up. Thanks Link to comment Share on other sites More sharing options...
Tue Bui Posted July 18, 2013 Author Share Posted July 18, 2013 Well, not sure if I made any progress. I deleted *capri.kext and then I can boot into ML without the black screen. But the UI is not so responsive and pretty laggy. Link to comment Share on other sites More sharing options...
Tue Bui Posted July 22, 2013 Author Share Posted July 22, 2013 Hi all, It's me again. I did make some progress. QE/CI works with HDMI, but no matter how hard I tried my internal display couldn't work. I did use every LVDS hex codes possible: 01 00 00 00 00 02 00 00 30 00 00 00, 05 03 00 00 02 00 00 00 30 00 00 00 or even 05 03 00 00 02 00 00 00 30 02 00 00. My HDMI out could work with following hex: 02 05 00 00 00 04 00 00 07 04 00 00 or 04 06 00 00 08 00 00 06 00 00 00. I run out of ideas now. Any help, please? ioreg.zip Link to comment Share on other sites More sharing options...
Tue Bui Posted July 23, 2013 Author Share Posted July 23, 2013 OMG. I finally hacked it. The problem was my LCD panel EDID couldn't be recognized by MAC and BIOS. So patching AppleIntelFrameBufferCapri.kext didn't help. I noticed some ppl in the forum had the same problem as mine. They thought the internal display may be connected in the different port than those have been discovered. To solve this problem, I injected my EDID (got from switchResX by logging in Safe Mode) in to DSDT. Some said you could do this by using Clover boot loader as well but I haven't tried it yet. So here is my injection: Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x0A) { "device_type", Buffer (0x08) { "display" }, "built-in", Buffer (One) { 0x01 }, "AAPL,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL00,override-no-edid", Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x51, 0xF3, 0x91, 0x50, 0x04, 0x00, 0x00, 0x00, /* 0010 */ 0x0E, 0x10, 0x01, 0x03, 0x80, 0x1D, 0x11, 0xFF, /* 0018 */ 0x2F, 0x00, 0x00, 0xA0, 0x57, 0x49, 0x9B, 0x26, /* 0020 */ 0x10, 0x48, 0x4F, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0xC6, 0x1D, /* 0038 */ 0x56, 0x02, 0x51, 0x00, 0x0C, 0x30, 0x22, 0x70, /* 0040 */ 0x12, 0x00, 0x27, 0xA6, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0xDA, 0x13, 0x56, 0x02, 0x51, 0x00, 0x0C, 0x30, /* 0050 */ 0x22, 0x70, 0x12, 0x00, 0x27, 0xA6, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x49, /* 0060 */ 0x6E, 0x74, 0x65, 0x72, 0x6E, 0x61, 0x6C, 0x20, /* 0068 */ 0x4C, 0x43, 0x44, 0x0A, 0x00, 0x00, 0x00, 0xFD, /* 0070 */ 0x00, 0x00, 0x3C, 0x00, 0x3D, 0x08, 0x00, 0x00, /* 0078 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xA7 } Then: Mac will accept the input from my internal display: I didn't include ig-platform-id (0x01660003) in this because I used GraphicsEnabler module of the Chameleon. Hope this would help for the others who couldn't light up their LVDS after trying > 10 ig-platform-id(s). Bye for now. Link to comment Share on other sites More sharing options...
Recommended Posts