Dell XPS 12 9Q23: Yosemite 10.10 Almost Working (Clover Install)

[yves32]

It does not show in any files you provided thus far.



If your screen is changing to black, lack of properly implemented backlight control might explain it.

Made some progress, but not out of the woods yet.

I chose a configuration and got back to boot to black screen. Then connected to external monitor and saw the screen with full working graphics, but laptop screen remained black with backlight.
Then followed the guide of backlight fix, patched DSDT and placed the patched dsdt.aml into acpi/patched folder. Boot the laptop but still got black screen. Connecting to external monitor I saw the brightness control bar indicating the patch works.
Bottom line is the laptop can boot with working graphics but the internal screen remains black. Backlight patch does not fix the problem. Attached is clover folder and screen output with ioreg and a few commands for system information.

 

[RehabMan]

Made some progress, but not out of the woods yet.

I chose a configuration and got back to boot to black screen. Then connected to external monitor and saw the screen with full working graphics, but laptop screen remained black with backlight.
Then followed the guide of backlight fix, patched DSDT and placed the patched dsdt.aml into acpi/patched folder. Boot the laptop but still got black screen. Connecting to external monitor I saw the brightness control bar indicating the patch works.
Bottom line is the laptop can boot with working graphics but the internal screen remains black. Backlight patch does not fix the problem. Attached is clover folder and screen output with ioreg and a few commands for system information.

Check in Windows to see if your internal display uses LVDS... or if it uses eDP.
The HD4000 drivers do not support eDP. Your EDID indicates eDP...

You can obtain the info from the Intel Graphics applet...
Also, there are other ig-platform-id values you should try.
You can also extract EDID with the Intel applet and compare against the one you're injecting.

But your patches for HD4000 are out of order... (but it probably only would matter if you were at the point of trying to implement HDMI audio). The scrambled order was created when you edited your config.plist with Clover Configurator (bad idea). FYI: The original order in my files is the correct order.

 

[yves32]

Check in Windows to see if your internal display uses LVDS... or if it uses eDP.
The HD4000 drivers do not support eDP. Your EDID indicates eDP...

You can obtain the info from the Intel Graphics applet...
Also, there are other ig-platform-id values you should try.
You can also extract EDID with the Intel applet and compare against the one you're injecting.

But your patches for HD4000 are out of order... (but it probably only would matter if you were at the point of trying to implement HDMI audio). The scrambled order was created when you edited your config.plist with Clover Configurator (bad idea). FYI: The original order in my files is the correct order.

Windows says Embeded DisplayPort. Am I running against wall?

 

[RehabMan]

Windows says Embeded DisplayPort. Am I running against wall?

eDP is not supported by the HD4000 drivers.
You can probably use an ig-platform-id more typically used in desktop scenarios (it will use DP), but you will lose the ability to implement backlight control, lid sleep, etc (since it treats the display as external).

 

[yves32]

eDP is not supported by the HD4000 drivers.
You can probably use an ig-platform-id more typically used in desktop scenarios (it will use DP), but you will lose the ability to implement backlight control, lid sleep, etc (since it treats the display as external).

Thanks for the direction.
I tried desktop ig-platform-ids, 0x0166000A/B, but still got no image on internal display. Should I edit EDID values?

Update:
After so many tests I finally got the HD4000 graphics working with eDP now.I modified AppleIntelFramebufferCapri.kext by replacing hex codes in two places from
05 03 00 00 02 00 00 00 30 to 03 04 00 00 00 04 00 00 81 .
There are still some more work to get the system fully operating in OS X, but at least the graphics is working.
Thank you, RehabMan, for your endless help.

 

[RehabMan]

Thanks for the direction.
I tried desktop ig-platform-ids, 0x0166000A/B, but still got no image on internal display. Should I edit EDID values?

Update:
After so many tests I finally got the HD4000 graphics working with eDP now.I modified AppleIntelFramebufferCapri.kext by replacing hex codes in two places from
05 03 00 00 02 00 00 00 30 to 03 04 00 00 00 04 00 00 81 .
There are still some more work to get the system fully operating in OS X, but at least the graphics is working.
Thank you, RehabMan, for your endless help.

That patch changes the LVDS connector to DP. It will work, but you won't be able to implement backlight control, as the driver is treating the internal display as external.

 

[yves32]

That patch changes the LVDS connector to DP. It will work, but you won't be able to implement backlight control, as the driver is treating the internal display as external.

When I close lid the screen does shut off.

 

[RehabMan]

When I close lid the screen does shut off.

Probably done internally by ACPI.

 

[yves32]

Probably done internally by ACPI.

Agree. It makes osx more usable on the laptop.
The laptop was made with many special parts and requires uncommon patches. The next one I really like to fix is trackpad. It is cypress and I am using the latest voodoops2controller. Trackpad acts like mouse only, no scrolling or tapping. I tried an old cypress fork of voodoo controller, but it crashes the new Sierra. I know Rehabman does not have cypress device, but can you point me the directions for a fix? Is it possible to compile a cypress fork of voodoo controller since the source code is available?

 

[RehabMan]

Agree. It makes osx more usable on the laptop.
The laptop was made with many special parts and requires uncommon patches. The next one I really like to fix is trackpad. It is cypress and I am using the latest voodoops2controller. Trackpad acts like mouse only, no scrolling or tapping. I tried an old cypress fork of voodoo controller, but it crashes the new Sierra. I know Rehabman does not have cypress device, but can you point me the directions for a fix? Is it possible to compile a cypress fork of voodoo controller since the source code is available?

You could build the Cypress fork with the fix I made for 10.12. You will need some coding skills...