Contribute
Register

Intel Core I3 8109U - Iris 655 : No output or low graphics (detailed approach)

Joined
May 28, 2011
Messages
12
Motherboard
Laptop make and model names > See Forum Rules!
CPU
i3-8109U
Graphics
Intel Iris Plus 655
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Hello everyone !

I'm requesting help for finalizing the setup of a Mini PC, Trigkey Speed S1 Mini PC.
The config :

- Intel® Core™ i3-8109U CPU @ 3.00GHz (Coffee Lake) --> Link to Intel website the connector is 3EA5.
- 8Gb RAM single channel (1600MHz)
- Intel Iris Plus Graphics 655 (Coffee Lake-U GT3e 28W)
- RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC
Full config can be browsed here.

The config is similar to an Intel NUC, and I'm using the SMBIOS of Macmini8,1.

The Mini PC itself :

6a3bf3f5430e9d0d7786651f4ee00e15f8a94f87_original.jpeg


As you can see, there are 2 HDMI ports, I'm connected directly to a 1080p screen via HDMI cable.

Most of the things work, except for graphics. Let me explain in detail what I have tried.

1) Setting up a AAPL,ig-platform-id with 0000A53E
By doing this, the boot process freezes at the end and I have some artifacts, and can't see login screen. Trying to RDP to the machine, it won't work (bad desktop size 0).
I have tried all values here (of course in "reversed" order, so 0900A53E for the 1st one) :

0x3EA50009
0x3E920009
0x3E9B0009
0x3EA50000
0x3E920000
0x3E000000
0x3E9B0000
0x3EA50004
0x3EA50005
0x3EA60005
0x3E9B0006
0x3E9B0008

2) Using -igfxvesa, or setting up device-id 3EA50000
With igfxvesa I can login in macOS but obviusly without acceleration. If I remove that flag and setup a device-id 3EA50000 (or any of the supported ones from This reference page), I also can boot but without acceleration.

Moreover, in IOReg explorer, there is no reference about AppleIntelFrame, but only .Display_boot :

Capture d’écran 2023-04-26 à 09.49.11.png


3) Enabling LSPCON
This didn't seem to have an effect. I'm suspecting that I really need this to work (see more details below).

4) Patching connectors

From the reference above, I have extracted the following :

ID: 3EA50000, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00030B0B
TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes)
Model name: Intel HD Graphics CFL CRB
Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 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: 0x00000400, flags: 0x00000187 - ConnectorDP
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000

With a nice table format :

[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
00000800 02000000 98000000

Bit Name Value
1 Port 00
2 Bus ID 00
3-4 Pipe Number 0800
5-8 Connector Type 02000000
9-12 Flags 98000000


[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
01050900 00040000 87010000


Bit Name Value
1 Port 01
2 Bus ID 05
3-4 Pipe Number 0900
5-8 Connector Type 00040000
9-12 Flags 87010000


[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
02040A00 00040000 87010000

Bit Name Value
1 Port 02
2 Bus ID 04
3-4 Pipe Number 0A00
5-8 Connector Type 00040000
9-12 Flags 87010000


I have guessed that my 2 physical ports are on BUS iD's 4&5 (two last values in table). I am forcing them to HDMI and not touching the first port (huge assumption here so let me know if it's not correct)

Proposed patch :

[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
00000800 02000000 98000000 (no change)

Bit Name Value
1 Port 00
2 Bus ID 00
3-4 Pipe Number 0800
5-8 Connector Type 02000000
9-12 Flags 98000000


[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
01050900 00080000 87010000


Bit Name Value
1 Port 01
2 Bus ID 05
3-4 Pipe Number 0900
5-8 Connector Type 00080000
9-12 Flags 87010000


[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
02040A00 00080000 87010000

Bit Name Value
1 Port 02
2 Bus ID 04
3-4 Pipe Number 0A00
5-8 Connector Type 00080000
9-12 Flags 87010000


Which gives me this in the config.plist of OpenCore :

Capture d’écran 2023-04-26 à 09.35.02.png


Sadly... No luck ! Still stuck after the verbose screen :(

I have also tried with LSPCON patching :

Capture d’écran 2023-04-26 à 09.37.41.png


Same issue.
I have tried similar approach with framebuffer value 3EA50004 & 3EA50009.



The machine is very similar (if not to say, a clone) to the Beelink SEi8 machine.
I have found this github repository, the difference here is that it's an I5 CPU instead of my I3 : https://github.com/daliansky/Beelink-SEi8-Hackintosh

What's curious, they use the AAPL,ig-platform-id with 0900A53E which has this values :

[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - ConnectorDP
00000800 02000000 98000000
01050900 00040000 C7010000
02040A00 00040000 C7010000

But instead, they use these values :

framebuffer-con0-alldata 00000800 00000000 98000000
framebuffer-con1-alldata 01010900 00080000 C7030000
framebuffer-con2-alldata 02020A00 00080000 C7030000


I understand that in con0, Pipe number set to 00 is disabling the port ?
But what I don't understand is that they seem to change the BUS ID from 05 & 04 to 01 & 02 for con1/con2, and the middle of flag from C701 to C703. Why ?
Obviously I have tried to copy/paste these values but no luck.

Please find attached my EFI (I don't care about the serial number, I'm not connected to iCloud and will only do it after graphics are ok with new serial).

Thanks a lot in advance !
 

Attachments

  • EFI-Trigkey.zip
    32.2 MB · Views: 45
Just posting a mini update, regarding the screenshots above I had put Framebuffer-patch-enable with wrong value (should be 01000000), but even with the correct value it is stuck.
I'm stuck here, notice the graphics corrupted on top of the screen

IMG_0437.jpeg



And this is my BIOS settings :


biosTrigkeyIGPU.jpg
 
Have you tried using 07009B3E framebuffer, as that one is recommended for UHD 630 IGPU in a NUC.
 
Have you tried using 07009B3E framebuffer, as that one is recommended for UHD 630 IGPU in a NUC.
Hi Edhawk !
I just tried it, unfortunately no luck, still stuck after the verbose screen. I have only set AAPL,ig-platform-id to 07009B3E and removed all other patches but I can't pass the boot sequence.
 
You would need two other patches for the framebuffer to work, if you removed all the others.

framebuffer-patch-enable > Data > 01000000
framebuffer-stolenmem
> Data > 00003001

These two patches are usually required when using the IGPU to drive the display, no matter which ig-platform-id you use. The first enables WhateverGreen.kext to patch the IGPU, the second sets minimum memory requirements, if they are not available to be edited in the bois.
 
You would need two other patches for the framebuffer to work, if you removed all the others.

framebuffer-patch-enable > Data > 01000000
framebuffer-stolenmem
> Data > 00003001

These two patches are usually required when using the IGPU to drive the display, no matter which ig-platform-id you use. The first enables WhateverGreen.kext to patch the IGPU, the second sets minimum memory requirements, if they are not available to be edited in the bois.

Thanks Edhawk, makes sense indeed for the patch-enable value.
I'm a bit puzzled for the stolenmem, as my BIOS seems to support it (see screenshot in my 2nd post).

I gave a go with the two extra values, sadly still stuck on the same step - artifacts on the verbose screen :(

Anything you believe I can try with LSPCON patching ?
 
Hi everyone,
I'm not giving up on this, but unfortunately still having issues getting that output working properly :(
As mentioned above, I guess my final guess is patching of LSPCON connectors, but I'm failing to understand it properly.
Would someone have some more info about it and how I could try and make it work in my case ?

Thanks !
 
Hi everyone,
I'm not giving up on this, but unfortunately still having issues getting that output working properly :(
As mentioned above, I guess my final guess is patching of LSPCON connectors, but I'm failing to understand it properly.
Would someone have some more info about it and how I could try and make it work in my case ?

Thanks !
As per rules, please update your hardware profile to allow others to help you easier
 
Back
Top