Intel HD4000 stopped displaying after upgrading lcd

[mgaffar]

Hey guys,

 

I have an alienware m14xr2 with a 1366x768 lcd and an intelhd4000. I had the intel hd4000 working perfectly with the the 1366x768 original lcd that came with the laptop. I wanted to upgrade my screen to a 900P screen (1600x900). I checked both my OSX and Win7 partitions before installing the lcd and they both loaded fine. I installed the lcd into the laptop and booted into windows 7 to verify it worked fine before putting the laptop together. I verified the resolution also and windows 7 was using 1600x900. Then i tried to boot into OSX (10.8.3) and it went to the chameleon screen, then apple screen popped up. After the pinwheel stopped spinning the screen flickered and went blank. I know the system is booted because i can hear the volume changer dinging.

 

I have also tried all the efi strings for the intel hd4000 by creating copies of my chameleon.boot.plist file and loading it through boot flags when i launch my osx system.

 

Does anyone have any ideas as to why this is happening? I also cant boot into safe mode, the screen is still blank. I was thinking of removing the intelhd4000 kexts but was looking for any other suggestions before doing that.

 

Thanks in advance,

 

Sorry for the repost, i posted it in the hardware/graphics section and no one responded. Please guys help me out as the hd4000 was working flawlessly on the 720p screen but i wanted more resolution.

 

Is there a device id i can edit into a plist somewhere? Maybe the .kext is still connected to the old lcd vs the new one i installed. The model number for the new one is LGD0362.

 

 

These are the strings i tried.

 

ig-platform-id: 01660000, Stolen RAM for FB: 96MB, Pipes: 3, Ports: 4, FBMem: 3
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000000006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 01660001, Stolen RAM for FB: 96MB, Pipes: 3, Ports: 4, FBMem: 3
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000001006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 01660002, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 1, FBMem: 1
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000002006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 01660003, Stolen RAM for FB: 64MB, Pipes: 2, Ports: 2, FBMem: 2
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 01660004, Stolen RAM for FB: 32MB, Pipes: 3, Ports: 1, FBMem: 1
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000004006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 01660008, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000008006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 01660009, Stolen RAM for FB: 64MB, Pipes: 3, Ports: 3, FBMem: 3
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000009006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 0166000A, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d00690064000000080000000a006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>
ig-platform-id: 0166000B, Stolen RAM for FB: 32MB, Pipes: 2, Ports: 3, FBMem: 2
Code:
<key>device-properties</key>
<string>7f0000000100000001000000730000000200000002010c00d041030a000000000101060000027fff04002c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d00690064000000080000000b006601140000006800640061002d0067006600780000000d0000006f6e626f6172642d31</string>

[kpkp]

You should try to use the DSDT patch, with dual-link patch and most likely AAPL,ig-platform-id: 01660004. Now with higher resolution you need that Dual-link patch or the screen gets black.

 

That is the patch i use, maybe will come handy:

#   Inject HDMI info and dual-link into GFX0/IGPU   */
into method label _DSM parent_adr 0x00020000 remove_entry;
into device name_adr 0x00020000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
   If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
   Return (Package()\n
   {\n
    "AAPL00,DualLink",\n
    Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 },\n
    "hda-gfx",\n
    Buffer (0x0A) { "onboard-1" },\n
    "AAPL,snb-platform-id",\n
    Buffer (0x04) { 0x00, 0x00, 0x01, 0x00 },\n
    "AAPL,ig-platform-id",\n
    Buffer (0x04) { 0x04, 0x00, 0x66, 0x01 },\n
   })\n
}\n
end;

[mgaffar]

thanks man, ill try that.

 

 

EDIT>..

I tried what you said and it still brought up a black scren.

 

quick question, my system worked good with the 01660003 platform id. How do i edit that patch to work with the 003 id?

 

im assuming it is under the platform id line, after the brackets. So i think that one is already set to 0x03 correct?

 

the 1660003 platform id worked perfect for me. I tried to do a duallink/platform id injection in dsdt but it still wont work. Maybe i did it wrong? I have attached the original dsdt, the edited dsdt with duallink and the patch i used. Can someone please help me?

 

Files are,

 

DSDT.aml/DSDT.dsl = dsdt's that i was using before i swapped the lcd. Everything worked great

 

DSDTORIG.dsl = extracted a fresh dsdt using dsdt editor

 

duallink = the patch i used to inject the duallink/platform-id

 

alienwarem14x.txt = the patch i used from olarila to patch my dsdt

 

DSDTpatched.aml/.dsl = the DSDT that worked great before swapping lcds, that is patched using the duallink patch. When i patched it there was an error that said _dsm already exists. So under the GFX0 section i deleted the _dsm method that was causing a conflict. Basically i guess the patch created a new _dsm so i just removed the older entry. Maybe this is the reason why?

Extra.zip

[p.H]

From my perspective, after you change your lcd you should re-generate your dsdt and modify it just like you used to.

And dual-link is no doubt needed. Good luck.

[mgaffar]

Thanks p.H, i took your advice and completely redid my dsdt. Instead of using a specific patch for my motherboard that someone created, i created my own patch with everything i needed. My system is working great now, found out i had to use a different device id hex string because the old string wouldnt work with this resolution or lcd screen. Only downside is that memory went down from 512mb for the hd4000 to 384 for the hd4000.

[tluck]

@mgaffar - you have something can fix my problem. i have HD 4000 1600x900 but it won't display properly with ig_platform_id =3

 

what strings i.e. or device did you change?

[mnfesq]

Now, I use Clover so I can't really advise you as to what changes to make in Chameleon but, if I had your problem, I would try generating my EDID in Windows and injecting it into my bootloader config file.

[tluck]

thanks.

well yes i am using clover.it just got ahold of this g780 and got it working mostly. it is getting the EDID injected properly.

 i have done a bit more research on this. 

i could be wrong that ig_platform_id =3 will not support 1600x900 resolution. however,  ig-platform-id =4 works at this resolutoin. but i don't have HMDI with id=4. so one step at time. there must be a way to edit the buffers to add ports? not sure

[pokenguyen]

For 1600x900 laptop you have to use ig_platform_id=0x01660004.

 

To get external ports work with this id, you have to apply the patch:

Patch HDMI-DP port HD4000 1600x900
Name: AppleIntelFramebufferCapri

Find:
040066010103010100000002
Replace:
040066010102040200000004

Find:
300200000000000001000000400000000000000001000000400000000000000001000000400000000000000000000000
Replace:
300200000205000000040000070400000304000000040000810000000406000000080000060000000000000000020011

Note: this was discussed more than 1 year ago, you should have searched for it. It's also included in my HVT tool.

[tluck]

@pokenguyen - thanks - I did search but find a lot of {censored}. I should have looked at your page  - you are one of my trusted advisors!

 

i very much appreciate the response. As you know i am an expert on HD 3000 (T420...)  but just coming up to speed on HD 4000. trying to get this Lenovo G780 set up for my daughther.

 

the new system works pretty well with just clover dsdt patching. just need to figure out why it won't sleep when i close the lid! 

 

Update

 

- The Clover Patch fixed/added the HDMI port. excellent. i used the HVT.

- as far as lid and sleep - i needed to patch the LID Device (i removed _PTR method). there is probably a more elegant solution to fix LID device. but right now closing the lid will sleep it. although, opening the lid will do nothing (meaning keeps sleeping until I hit a key - so its workable.

[pokenguyen]

Did you patch pnlf + acpibacklight?