Jump to content

E5570: Garbled internal screen in Ventura


rdmo

Recommended Posts

  • Administrators

So, built-in screen still garbled with HDMI connected and running in mirror mode?

 

Looking at your IOReg, I can see that the built-in screen is fully detected on connector con0 ("AppleBacklightDisplay") with LVDS/eDP type (02000000). Strangely enough, I see that you patched connector con1 (used for external HDMI screen) to type LVDS/eDP too. What's the reason for that?

Link to comment
Share on other sites

I think it's because I tried to manually patch con0 as LVDS/eDP and/or I mirror the image to my external screen instead of using it as extended monitor.

 

With the patched con0, I can still display to HDMI but the internal screen still a mess. It's got no audio output though (possibly because it was detected as LVDS/EDP that has no audio output, my external screen has speaker)

 

To alleviate the problem now I simply put my laptop lid closed and restart it again. Turning both internal monitor while being a mess resulted in my screen having severe image retention that I fear might damage the screen.

Link to comment
Share on other sites

  • Administrators

HDMI audio requires connector to be patched to HDMI type (00080000); in your case (and as is usually the case): connector con1. No need to patch con0 to LVDS/eDP, it's its native setting.

ID: 59160000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000B0B
TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes)
Model name: Intel HD Graphics KBL CRB
Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00080000 87010000

 

I also see that you inject your screen's EDID. I guess it made no difference. Which tool did you grab it with?

Link to comment
Share on other sites

I think it's because I tried to manually patch con0 as LVDS/eDP and/or I mirror the image to my external screen instead of using it as extended monitor.

 

With the patched con0, I can still display to HDMI but the internal screen still a mess. It's got no audio output though (possibly because it was detected as LVDS/EDP that has no audio output, my external screen has speaker)

 

To alleviate the problem now I simply close my laptop lid and use the external screen, since keeping the internal display trying to output the display resulted in my laptop screen to have some image retention issue.

 

I use IOReg to grab my screen's EDID btw.

Link to comment
Share on other sites

  • Administrators

Ok, you misunderstood a few things:

  1. You do not patch a framebuffer's connector to set an external screen in mirror mode; that's done from the booted OS, either from the Display Preference Panel or with keyboard shortcuts ([COMMAND-low brightness] combination). Make sure you remove those incorrect patches in your bootloader config. The only patch you ought to have is to set con1 to HDMI type (00080000) in order to gain HDMI audio output. Framebuffer connectors effectively define physical video outputs.
  2. Grabbing your screen EDID from IOReg to then inject it in your bootloader's config is utterly useless; you effectively inject what the system natively detects. See this FAQ topic for details of the procedure to follow.

 

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...