Tahoe - Intel UDH 630 - dual monitor problems

[verdazil]

@fermento, @deeveedee,

Please note that for the 3E9B0007 ig-platform-id (Comet Lake) all connectors are ConnectorDP, however, the second (besides DP) physical port on the motherboard is HDMI. 

Therefore, boot-arg -igfxlspcon must be added (This works with WhateverGreen.kext.)

[fermento]

Thanks @deeveedee! Here is my current config.

 

Quote

can you tell which logical connectors (con0, con1, con2) are connected to displays?

con0 and con2

 

 

• DVMT pre-alloc set to 96MB
• From the motherboard HDMI output an HDMI cable connected to an adapter HDMI to DVI and the adapter connected to the Dell monitor
• OpenCore version 1.0.6

deeveedee.config.plist

[deeveedee]

@verdazil It's certainly possible, but I don't use that boot-arg on my HDMI ports.  While there are some that require the boot-arg, fermento is using HDMI->DVI adapter (not true HDMI).  Also, see my notes at the bottom of this post.  I listed lspcon as one of the things we'll try after getting dual-monitors working.  Thank you for your suggestion.  It is one of the things we'll try.

 

EDIT: @fermento I'm going to be away from my desk for a while without access to this thread.  If you still want more help diagnosing the remaining issues with your two displays, upload your latest "working" config.plist and answer the question here about the Hackintool connector list and someone here will help you.  Good luck!

Edited December 17, 2025 by deeveedee

[brumas2025]

16.12.2025 в 10:05 пользователь brumas2025 написал:

Привет всем, прошу помощи! У меня на Hackintosh установлены macOS Sequoia и Tahoe, к плате подключены два монитора: один через DVI-D, другой через HDMI, оба работают под Windows. На Mac был монитор, подключенный через HDMI, и я недавно увидел конфигурацию, которая повернута, выводим изображение на второй монитор, подключенный через DVI-D, но монитор, подключенный через HDMI, перестал работать, то есть либо один, либо другой. Предлагаю планы для разных наблюдателей. Как мне добиться одновременной работы двух мониторов?

 

  конфиг DVI-D.plist 29,23 кБ  ·  0 загрузок конфиг HDMI.plist 28,67 кБ  ·  0 загрузок

 

 

 

Edited December 18, 2025 by brumas2025

[fermento]

At the moment, I have dual monitor. The problems I have are:

 

• The flickering of the displays for a long time when system starts, like in the video I uploaded in previous post
• When the displays turn off because inactivity, on wake up only the main display turns on

 

Any help will be appreciated as always 🙏

[deeveedee]

@fermento I'm just able to look at this again.  I looked at the last config.plist that you posted (deeveedee.config.plist) and see that you have made many of your own changes.  That's great!  You'll need to be patient with trial and error, making changes before each new test.  You have many changes in this latest config.plist that you posted, so I'm not sure what is working and what is not at this point.  How is it working for you?

 

@brumas2025 Your question has been lost in this thread which is focused on solving fermento's issue.  It would be best for you to start your own thread so that it gets the attention it deserves.

Edited December 18, 2025 by deeveedee

[deeveedee]

@@fermento I see that I responded after you had already posted your update - sorry about that.  I did not see your latest post.  Are the problems that you described (flickering displays as shown in your video, second display doesn't wake after sleep) occurring with the last config.plist that you posted here (named "deeveedee.config.plist")?  If so, is this behavior any different from your original config.plist (the first one you posted in this thread) with WhateverGreen.kext's MaxKernel fixed for Tahoe?  Is this behavior any different from what you observe with earlier versions of macOS?

 

Each of us has our own debugging methods that work for us.  I have found that it is best to make limited changes between tests.  When I make too many changes between tests, it is hard for me to determine which changes helped to fix the problems.

[fermento]

@deeveedee I see, I also noticed that, baby steps are needed 😁.

 

- The flickering displays is a long term issue I had been carrying since I set dual displays in my computer 🙈🙉🙊

- The second display not wake up after sleep is an issue I have since Tahoe

 

I played around with Framebuffer patch in the last few ours without any progress.

 

This is my current state where I touched:

 

Boot Arguments:

                    <key>boot-args</key>
                    <string>amfi=0x80 e1000=0 igfxfw=2 -v</string>
 

Framebuffer:

 

                <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
                <dict>
                    <key>#framebuffer-con1-busid</key>
                    <data>BgAAAA==</data>
                    <key>#framebuffer-con1-enable</key>
                    <data>AQAAAA==</data>
                    <key>#framebuffer-con1-pipe</key>
                    <data>EgAAAA==</data>
                    <key>#framebuffer-con1-type</key>
                    <data>AAgAAA==</data>
                    <key>AAPL,ig-platform-id</key>
                    <data>BwCbPg==</data>
                    <key>AAPL,slot-name</key>
                    <string>Internal@0,2,0</string>
                    <key>device_type</key>
                    <string>VGA compatible controller</string>
                    <key>enable-hdmi20</key>
                    <data>AQAAAA==</data>
                    <key>enable-lspcon-support</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con0-busid</key>
                    <data>AAAAAA==</data>
                    <key>framebuffer-con0-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con0-pipe</key>
                    <data>CAAAAA==</data>
                    <key>framebuffer-con0-type</key>
                    <data>AgAAAA==</data>
                    <key>framebuffer-con2-busid</key>
                    <data>BAAAAA==</data>
                    <key>framebuffer-con2-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con2-has-lspcon</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con2-pipe</key>
                    <data>CgAAAA==</data>
                    <key>framebuffer-con2-preferred-lspcon-mode</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con2-type</key>
                    <data>AAgAAA==</data>
                    <key>framebuffer-patch-enable</key>
                    <data>AQAAAA==</data>
                    <key>hda-gfx</key>
                    <string>onboard-1</string>
                    <key>model</key>
                    <string>Intel UHD Graphics 630</string>
                </dict>

 

[Asural]

@fermento  I use an HP Prodesk 400 G5 SFF, and I experienced the same problem as you when using SMBIOS = Macmini8,1 with Sequoia.
In the end, the UHD630 display stabilized with SMBIOS = iMac19,2.
I've heard that SMBIOS = iMac20,1 is more efficient when using a 10th generation CPU UHD630 with Sequoia, so why not try changing the SMBIOS?
 

[deeveedee]

@fermento I hope to be able to look at this later today and also hope that others offer suggestions.  Please upload your actual config.plist (instead of posting just the DeviceProperties listing).  If you do experiment and have any changes to report, please upload the new config.plist with each new status report.  The reason that it will be important for you to upload a new config.plist with each of your status reports is so that we can easily see what has changed from one test to the next.  Thank you.

[fermento]

@Asural interesting suggestion. In my other partition where I have Ventura, my SMBIOS is iMac20,1 and the flickering is present.

 

@deeveedee thanks ! I leave my config here, sorry for that.

 

 

off-topic ( Moderators )

When this restriction for my content being approved by a moderator will end? Do I need to do something? Yesterday took more than 10 hours for my post to be approved, is difficult to keep a conversation like that.

20251219.config.plist

[deeveedee]

@fermento Can you please test the attached config.plist and report results?  The attached config.plist makes the following changes:

• I don't think lspcon is relevant to your hack, so I have disabled those properties
• I'd like to see whether the pipes actually need to be redefined
• I have added a few properties, including changing the framebuffer flags, to see if your hack benefits from a mobile framebuffer

20251219.config.plist.zip

[fermento]

@deeveedee the DELL display turns off on macOS login

[deeveedee]

@fermento The fact that your posts are still awaiting moderator approval explains why I'm not seeing some of you posts.  If this is still a problem for you, feel free to Private Message me.  I don't know if PM have the same moderator delay, but it's worth a try.

Edited December 19, 2025 by deeveedee

[deeveedee]

Ok - That's interesting.  The challenge is that we know that your displays are connected to con0 and con2, but we don't know which display is connected to which logical connector.

 

I'd like to go back to the very first config.plist that you posted and make a couple of minor changes:

• Enable WhateverGreen.kext for Tahoe (delete MaxKernel)
• Remove fbmem, stolenmem, unifiedmem properties

Please test the attached config.plist.  After booting macOS, confirm that both displays are still working.  Then, physically disconnect the Dell display and open Hackintool.  Which logical connector is still active?  This will be the logical connector for the Gigabyte display.  Thank you.

 

 

EDIT: Note that I was confused about how your displays are connected.  I thought you had one display connected from the Motherboard HDMI -> Display HDMI and the other display connected from the Motherboard DP -> Display DVI-D.  Now I understand that you have one display (Gigabyte) connected from Motherboard DP -> display DP and the second display (Dell) connected from Motherboard HDMI -> display DVI-D.  Now we just need to figure out the association of logical connectors con0 and con2 to the motherboard ports DP and HDMI.

 

EDIT2: For everyone else who is following this and wants to learn or help, here's how the displays are connected:

Connector		Motherboard				Displays

con0 or con2		DP					DP (Gigabyte)
con1			No Display			
con0 or con2		HDMI					DVI-D (Dell)

 

config-test1.plist.zip

Edited December 19, 2025 by deeveedee

[verdazil]

@deeveedee, This is an interesting topic and I am following it. And I had a question, why there is doubt about con0 or con2? If you open IORegistryExplorer, you can clearly see which connector the display is connected to and the display's DeviceID.

AppleDisplay --> DisplayProductID && DisplayVendorID

[deeveedee]

@verdazil If the Hackintool strategy doesn't work, we'll try that.  Thanks.

[fermento]

1 hour ago, deeveedee said:

Ok - That's interesting.  The challenge is that we know that your displays are connected to con0 and con2, but we don't know which display is connected to which logical connector.

 

I'd like to go back to the very first config.plist that you posted and make a couple of minor changes:

• Enable WhateverGreen.kext for Tahoe (delete MaxKernel)
• Remove fbmem, stolenmem, unifiedmem properties

Please test the attached config.plist.  After booting macOS, confirm that both displays are still working.  Then, physically disconnect the Dell display and open Hackintool.  Which logical connector is still active?  This will be the logical connector for the Gigabyte display.  Thank you.

 

 

EDIT: Note that I was confused about how your displays are connected.  I thought you had one display connected from the Motherboard HDMI -> Display HDMI and the other display connected from the Motherboard DP -> Display DVI-D.  Now I understand that you have one display (Gigabyte) connected from Motherboard DP -> display DP and the second display (Dell) connected from Motherboard HDMI -> display DVI-D.  Now we just need to figure out the association of logical connectors con0 and con2 to the motherboard ports DP and HDMI.

 

EDIT2: For everyone else who is following this and wants to learn or help, here's how the displays are connected:

Connector		Motherboard				Displays

con0 or con2		DP					DP (Gigabyte)
con1			No Display			
con0 or con2		HDMI					DVI-D (Dell)

 

config-test1.plist.zip 6.47 kB · 1 download

 

Flickering persist. The strange thing is that now I see con0 and con1 not con2 mi😁

 

[deeveedee]

@verdazil I had already reviewed that and determined that 5T33ZO's DeviceProperties were the same as the original config.plist posted in this thread.

 

@fermento Let's assume for now that con0 is connected to the Gigabyte display (DP).  I have made the change to my proposed config.plist attached.  Note that I have changed the type of con1 and con2.  Please test this and report results along with the Hackintool connector screenshot.  Thank you.

 

 

EDIT: @fermento I uploaded the correct version of config-test2 (attached). Sorry about my mixup.  I made my test2 revisions to the wrong config.plist.  Please test this and report results.  thank you.

config-test2-corrected.plist

Edited December 19, 2025 by deeveedee

[fermento]

37 minutes ago, verdazil said:

Colleagues, please review this information. 5T33Z0 is a reputable developer, you can trust him.

https://github.com/5T33Z0/Gigabyte-Z490-Vision-G-Hackintosh-OpenCore/blob/main/Additional_Files/Graphics/Intel_UHD_630_HDMI_DP_Framebuffer-Patch.plist

 

My config is based in this user config.

[fermento]

44 minutes ago, deeveedee said:

@verdazil I had already reviewed that and determined that 5T33ZO's DeviceProperties were the same as the original config.plist posted in this thread.

 

@fermento Let's assume for now that con0 is connected to the Gigabyte display (DP).  I have made the change to my proposed config.plist attached.  Note that I have changed the type of con1 and con2.  Please test this and report results along with the Hackintool connector screenshot.  Thank you.

 

 

config-test2.plist.zip 6.39 kB · 2 downloads

 

I was not able to boot with this config

[fermento]

The corrected version doesn't boot either

 

 

 

- Boot with framebuffer-flags enabled (IMG_2238)

- Boot with framebuffer-flags disabled (IMG-2239)

Edited December 19, 2025 by fermento

[fermento]

Changes

• Uncomment framebuffer-con2-busid
• Comment-out igfxfw

Result: Not able to boot

[deeveedee]

On 12/18/2025 at 8:20 PM, Asural said:

@fermento  I use an HP Prodesk 400 G5 SFF, and I experienced the same problem as you when using SMBIOS = Macmini8,1 with Sequoia.
In the end, the UHD630 display stabilized with SMBIOS = iMac19,2.
I've heard that SMBIOS = iMac20,1 is more efficient when using a 10th generation CPU UHD630 with Sequoia, so why not try changing the SMBIOS?
 

I think you make a good point about the SMBIOS.  fermento is using SMBIOS iMac20,2.  The real iMac20,2 has a dGPU with a headless iGPU.  I would think that MacMini8,1 might be a good SMBIOS to test.

 

The last config.plist I posted here (config-test2-corrected.plist) would not boot macOS.  The only way this hack boots is when the indices and pipes for con1 and con2 are swapped.  I have never seen this before.  Currently the config.plist here (config-test1.plist) boots macOS with a long delay while the screens flicker and then the login screen is finally displayed.  After booting, both displays work and they both sleep and wake.

 

@fermento Please feel freel to correct anything I've stated or add anything that might help others to generate ideas and suggestions.

[Asural]

3 hours ago, deeveedee said:

The last config.plist I posted here (config-test2-corrected.plist) would not boot macOS.  The only way this hack boots is when the indices and pipes for con1 and con2 are swapped.  I have never seen this before.  Currently the config.plist here (config-test1.plist) boots macOS with a long delay while the screens flicker and then the login screen is finally displayed.  After booting, both displays work and they both sleep and wake.

According to the OpenCore specification, if required information is undefined, it is unclear what will be set (it always results in the worst value).
framebuffer-conX-enable, framebuffer-conX-index, and framebuffer-conX-busid are required information, and WEG should not be left to its own devices.
I recommend setting all of con0, con1, and con2.

The information you set for framebuffer-conX-pipe, framebuffer-conX-type, and framebuffer-conX-flags is not necessarily reflected, so after setting the information using Hackintool or similar, I overwrite the settings with the information from IORegistryExplorer once the screen display stabilizes.
 

@fermento I re-read the thread and there doesn't seem to be any mention of connecting a cable from the DP socket on the Gigabyte Z490 to the M27Q, is it a DP to DP connection?
Also, could you please attach an IORegistryExplorer file showing a stable display?