Integrated screen not recognized

[jam2412]

Hello everybody

I could not find a solution for my problem directly in the forum, so I'll open this thread now.

Information about the system:

Mainboard: Mitac PH10WI Thin mini ITX mainboard with H97 chipset and integrated 1x LVDS and 1x eDP interface, each 40 pin
CPU: I7 5775C
iGPU: Intel Iris Pro 6200
Housing: Intel Loop AIO with 21.5 “display, connected via LVDS.
Bootloader: OC
Kexts: Lilu, Opencore are up to date.
SMBIOS: iMac16.1
Build guide: dortania.github.io

The problem:

In VESA mode, both the integrated display and a monitor that I have connected via HDMI work. As soon as I enter a valid AAPL,ig platform id, the integrated monitor remains in the text in verbose mode and in the Apple boot logo in non-verbose mode. The dedicated monitor is depending on the platform id Detected immediately or must be briefly removed and then plugged in again. I've been struggling with framebuffer patching for 3 days now and just can't get it resolved. I have attached some pictures and my EFI. It would be very nice if someone could take the trouble and take a look. I must have forgotten something or ignored it. Unfortunately, I'm still a bit of a hacking noob and I'm in despair right now.

Thanks in advance,

Jan

 

[knur004]

Hi,

im in somewhat similiar situation - i have dq77kb with i7 3770s in aio pc with internal display connected to motherboard with lvds connector. And im also struggling on the same matter. But in your case at least your internal display is recognized in ioregistryexplorer, but in my case no internal display is recognized nor in ioregistryexplorer nor in hackintool. Only external monitor connected via hdmi or dp is recognized. I checked your efi and you have similar "devices" section as i have - ig paltform id, framebuffer con0 enabled, all data ad so on. But i just cant make my internal display to work.

 

[Edhawk]

The details for the framebuffer(s) have been extracted from the WhateverGreen.kext FAQ Intel HD page - https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md

These are the details for the 0x16220002 framebuffer you are using in your config.plist. This is for a Mobile/Laptop IGPU.

ID: 16220002, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00004B0A
TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
Camellia: CamelliaV2 (2), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000507 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000507 - ConnectorDP
00000800 02000000 30020000
01050900 00040000 07050000
02040A00 00040000 07050000

As can be seen this Framebuffer provides three connectors for the IGPU. LDVS, DP and a 2nd DP.

From the information you provided in the initial post you would expect this framebuffer to work. Obviously something is not matching between your system and the Framebuffer.

Are you sure the internal screen has an LDVS connection? Or is that what you are seeing in IOReg, while using this framebuffer?

What happens when you use the Desktop framebuffer 0x16220007?

ID: 16220007, STOLEN: 38 MB, FBMEM: 38 MB, VRAM: 1536 MB, Flags: 0x000BB306
TOTAL STOLEN: 77 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 153 MB, MAX OVERALL: 154 MB (162017280 bytes)
Camellia: CamelliaDisabled (0), Freq: 5273 Hz, FreqMax: 5273 Hz
Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000507 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000507 - ConnectorDP
[3] busId: 0x06, pipe: 8, type: 0x00000400, flags: 0x00000011 - ConnectorDP
01050900 00040000 07050000
02040A00 00040000 07050000
03060800 00040000 11000000

This Desktop framebuffer also provides three connectors but this time they are all DP connectors.

You would need to reverse the pairs when adding this or any other framebuffer to your config.

So 0x16220007 would be entered as 07002216 in the config.