Dell Venue 11 Pro - Display Issue

[jhax01]

Dell Venue 11 Pro - Core i5 Haswell - HD4200 - Intel 8 series chipset

Short and simple, I cannot find a working mobile ig-platform-id that is compatible with the internal display. 0x0D220003 does work but then I lose sleep, etc. I've tried 0x0a260006, 0x0a260005, 0x0a260000, 0x0a160000, 0x0a2e0008, 0x0a2e000a both in UEFI only and Legacy mode and with/without an injected EDID. All either cause reboots or boot to a black screen. I'm currently using 0x0a260006, the internal screen is dark and seems undetected, but HDMI out works perfectly and is attached to an external monitor. Here's the standard support output, but under these circumstances, I'm not sure it's helpful. Any thoughts on what to try next? Again, using the desktop id does work, but then I have to abandon all the features that make a mobile device, well, mobile.

jhax01-DV11P:rehabman jhax01$ kextstat | grep -y acpiplat
   13    2 0xffffff7f82c66000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (4.0) 295F7A91-2DF7-3FFE-9550-A0C1A6F9D575 <12 11 7 6 5 4 3 1>
jhax01-DV11P:rehabman jhax01$ kextstat | grep -y appleintelcpu
jhax01-DV11P:rehabman jhax01$ kextstat | grep -y applelpc
   90    0 0xffffff7f8265e000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) 0C90B22D-637B-3000-8C44-B7955D57E10A <80 12 5 4 3>
jhax01-DV11P:rehabman jhax01$

 

[RehabMan]

Dell Venue 11 Pro - Core i5 Haswell - HD4200 - Intel 8 series chipset

Short and simple, I cannot find a working mobile ig-platform-id that is compatible with the internal display. 0x0D220003 does work but then I lose sleep, etc. I've tried 0x0a260006, 0x0a260005, 0x0a260000, 0x0a160000, 0x0a2e0008, 0x0a2e000a both in UEFI only and Legacy mode and with/without an injected EDID. All either cause reboots or boot to a black screen. I'm currently using 0x0a260006, the internal screen is dark and seems undetected, but HDMI out works perfectly and is attached to an external monitor. Here's the standard support output, but under these circumstances, I'm not sure it's helpful. Any thoughts on what to try next? Again, using the desktop id does work, but then I have to abandon all the features that make a mobile device, well, mobile.

jhax01-DV11P:rehabman jhax01$ kextstat | grep -y acpiplat
   13    2 0xffffff7f82c66000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (4.0) 295F7A91-2DF7-3FFE-9550-A0C1A6F9D575 <12 11 7 6 5 4 3 1>
jhax01-DV11P:rehabman jhax01$ kextstat | grep -y appleintelcpu
jhax01-DV11P:rehabman jhax01$ kextstat | grep -y applelpc
   90    0 0xffffff7f8265e000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) 0C90B22D-637B-3000-8C44-B7955D57E10A <80 12 5 4 3>
jhax01-DV11P:rehabman jhax01$

Did you try to inject EDID?

Did you check in Windows to see how the display is connected (is it eDP or LVDS?)

 

[jhax01]

Did you try to inject EDID?

Did you check in Windows to see how the display is connected (is it eDP or LVDS?)

According to Windows, the display is eDP. There are two EDIDs in the registry and I've tried them both with each of the platform ids I listed above both in UEFI only and legacy mode. :-/ For the most part, adding the EDID to a mobile ig-platform-id causes a reboot, without it, it will either boot to a black screen or reboot. The only one that I get a picture on the internal display with is the desktop id. Not sure if it is a quirk of the Venue or just the HD4200 in general, I haven't been able to find many other HD4200 examples.

 

[RehabMan]

According to Windows, the display is eDP. There are two EDIDs in the registry and I've tried them both with each of the platform ids I listed above both in UEFI only and legacy mode. :-/ For the most part, adding the EDID to a mobile ig-platform-id causes a reboot, without it, it will either boot to a black screen or reboot. The only one that I get a picture on the internal display with is the desktop id. Not sure if it is a quirk of the Venue or just the HD4200 in general, I haven't been able to find many other HD4200 examples.

You said it works with 0x0d220003, right?

If so, boot using it, then post ioreg...

Post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

 

[jhax01]

You said it works with 0x0d220003, right?

If so, boot using it, then post ioreg...

Post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

With all the mobile ids, injecting the EDID causes reboots, but with 0x0d220003, it will only boot if you inject the EDID. ioreg attached.

 

[RehabMan]

With all the mobile ids, injecting the EDID causes reboots, but with 0x0d220003, it will only boot if you inject the EDID. ioreg attached.

You could patch 0x0d220003 for eDP:

Name: AppleIntelFramebufferAzul
Find: <0105 0900 0004 0000 8700 0000>
Replace: <0105 0900 0400 0000 8700 0000>

Or even LVDS might be an interesting experiment:
Find: <0105 0900 0004 0000 8700 0000>
Replace: <0105 0900 0200 0000 8700 0000>

Then you might be able to implement backlight control and continue working on your sleep issue (depends on specifics).