HP EliteOne 800 G1 Built-in display black screen (Catalina)

[McSonite]

I have done a lot of WEG patching in this case but whatever (<-  ) I do the built-in display stays black. I would appreciate if I got some help with this issue. @Hervé suggested that I should concentrate my efforts on con2 because it seems to be the FB for the built-in display. I have done this and more and now I'm out of ideas.

 

Only way I'm getting this PC to start to the OS is to use framebuffer layout 0D220003 and when I do this the only way to access it is to connect with VNC or attach an external display with DP cable to the additional DP port on the PC after the built-in display has gone black.

 

If I try to start the PC with display connected to DP the boot halts to a point where it says: Adding AGDP mode validate property. This happens also if I try to boot the PC with other Haswell Desktop ig-platform-ids.

 

This is what I have interpreted from the IOreg:

 

FB@0 = port 5

FB@1 = port 6 (this is where the external display connects to with DP cable)

FB@2 = port 0

 

The things I have done with the FB@2 are:

 

framebuffer-patch-enable    01000000                    DATA
framebuffer-con0-enable     01000000                    DATA
framebuffer-con0-busid      00000000                    DATA
framebuffer-con1-enable     01000000                    DATA
framebuffer-con1-busid      00000000                    DATA
framebuffer-con2-enable     01000000                    DATA
framebuffer-con2-type       02000000                    DATA
framebuffer-con2-busid      01000000                    DATA 

framebuffer-patch-enable    01000000                    DATA
framebuffer-con0-enable     01000000                    DATA
framebuffer-con0-busid      00000000                    DATA
framebuffer-con1-enable     01000000                    DATA
framebuffer-con1-busid      00000000                    DATA
framebuffer-con2-enable     01000000                    DATA
framebuffer-con2-type       02000000                    DATA
framebuffer-con2-busid      02000000                    DATA

and so forth for all the busids from 1-6 and with connector type LVDS. Idea for setting the con0 and con1 busid to 0 is to avoid them to clash with con2 busid.

 

framebuffer-patch-enable    01000000                    DATA
framebuffer-con0-enable     01000000                    DATA
framebuffer-con0-busid      00000000                    DATA
framebuffer-con1-enable     01000000                    DATA
framebuffer-con1-busid      00000000                    DATA
framebuffer-con2-enable     01000000                    DATA
framebuffer-con2-type       00040000                    DATA
framebuffer-con2-busid      01000000                    DATA 

framebuffer-patch-enable    01000000                    DATA
framebuffer-con0-enable     01000000                    DATA
framebuffer-con0-busid      00000000                    DATA
framebuffer-con1-enable     01000000                    DATA
framebuffer-con1-busid      00000000                    DATA
framebuffer-con2-enable     01000000                    DATA
framebuffer-con2-type       00040000                    DATA
framebuffer-con2-busid      02000000                    DATA

and so forth for all the busids from 1-6 and with connector type DP. 

 

I have also tested with boot-args: agdpmod=pikera, agdpmod=vit9696 and without these arguments. (Only one argument at a time)

 

One thing with this PC is that I don't know if this built-in display is LVDS or eDP type. BIOS suggests that it is LVDS, service manual refers to LVDS cable as spare part but Windows Intel HDA manager tells me that it is an eDP connector.

 

This might be a tough nut to crack or maybe not to you gurus out there.

[McSonite]

I knew that I hadn't grasped the patching even though I have read the manual.

 

Here is the IOreg output.

ioreg_20201212.zip

[McSonite]

I have now injected the parameters you, @Hervé, gave above (for testing purposes). Now there is another connector FB@3 and the port number for that is 0x0. Port number for FB@0 is also 0x0.

 

I have attached the IOreg from this setup.

 

Do you have ideas which FB is for the in-built display and what to test as parametrs for it? This help would be greatly appreciated.

ioreg_20201213.zip

[McSonite]

Thanks again for your answer. I noticed that there is no display under con2 and now I actually also found the parameter that says the con2 display is the boot display (AAPL,boot-display = True). Con2 is now set to type LVDS but unfortunately situation with the in-built display remains the same.

 

Just to check this boot argument agdp=pikera ... Is it like this? I have been using agdpmod=pikera

 

I have also earlier experimented with SMBIOS 14,4 and when running that SMBIOS and if a display is connected to the additional DP connector then the graphics get glitchy. With SMBIOS 14,4 the in-built display ... blackened.

 

Do you have any ideas what to do next? Or is this a lost cause?

 

I attached current config.plist and IOreg. 

config.plist.zip

ioreg.zip

[McSonite]

Does @Hervé or anyone have any tips for this? These would be greatly appreciated.

[McSonite]

I was trying to be funny and refer to one great metal band's song by using the word blackened . What I meant was that the situation was the same and in-built display still has a black screen.

 

Strangely enough with SMBIOS 14,1 all connectors seem somehow change to HDMI (0008000). If I use boot-arg -igfxnohdmi then they are as the layout defines them - that is all DP. With SMBIOS 14,4 there is no need to use boot-arg -igfxnohdmi and the connector types are as they should. 

 

Actually I took IOreg extract with SMBIOS 14,4 now. I have attached it here. Also config.plist uploaded.

 

I have once tried to inject the EDID with: AAPL00,override-no-connect | DATA | EDID (EDID being the actual edid of the display, extracted w/ Linux)

 

How is the AAPL0x defined? Should I use AAPL00, AAPL01 or AAPL02? 

 

 

ioreg 3.zip

config.plist.zip

Edited December 14, 2020 by McSonite
commented edid

[McSonite]

Thank you for being so kind and giving me help @Hervé. I have read loads of information about WEG patching and some of these guides have been written by you. I have tried almost everything that I have found under different Hackintosh sites but none of these guides have helped me out to get the display to register.

 

When I started this project I though that this might have something to do with fbmem, stolenmem and stuff like that but now I have learned that it didn't. Then I tried to change the indexes by using WEG patching but I also learned that you cannot do that. I also tried the busID patching following the guide by Dortania and that also left me out cold (went through all the possible iterations) . Somethings that I haven't played so much with are the pipe and flags settings - maybe that is something to look into. 

 

I'm trying to set this computer up as a Christmas present for my daughter so if anyone has anything that I could possibly try with this PC to get the in-built screen to work then that would be more than greatly appreciated.

[McSonite]

I have now generated a new EDID by reading https://github.com/acidanthera/WhateverGreen/blob/master/Manual/edid-gen.sh

 

I don't have the display.plist because the display is never attached to the framebuffer so I had to get creative. I just edited the EDID with the parameters that the script would do.

 

My guess is black screen but let's see. 

[McSonite]

I guessed right (all iterations AAPL00,..01,..02, override-no-connect, override-no-edid,.. connector types LVDS & DP) . Thank you, good bye. It's Linux for this PC then.

 

 

1 hour ago, McSonite said:

I have now generated a new EDID by reading https://github.com/acidanthera/WhateverGreen/blob/master/Manual/edid-gen.sh

 

I don't have the display.plist because the display is never attached to the framebuffer so I had to get creative. I just edited the EDID with the parameters that the script would do.

 

My guess is black screen but let's see. 

 

Original EDID

 

00FFFFFFFFFFFF0022F08910010000001517010380331D780AA040A656529D2710505400000001010101010101010101010101010101193880007138144060408400FE1F11000078000000FE005630370A202020202020202020000000FC00485051203830302041494F0A20000000FE004C4D3233305746332D534C4C3100A0

 

Edited EDID

 

00FFFFFFFFFFFF0022F08910010000001517010409331D780AA040A656529D2710505400000001010101010101010101010101010101193880007138144060408400FE1F11000078000000FE005630370A202020202020202020000000FC00485051203830302041494F0A20000000FE004C4D3233305746332D534C4C31008F

 

[Jief_Machak]

Hi, do you have a working Clover or OC folder for the EliteOne 800 G1 ?