Tahoe - Intel UDH 630 - dual monitor problems

[fermento]

UPDATE 2

- HDMI cable 2.1

- Displays

    - Gigabyte M27Q - 2‎560 x 1440 (QHD)

    - Dell E248WFP - 1920 x 1200 (FHD)

 

UPDATE 1

Change the motherboard model to the correct one.

 

 

Hi! I'm having issues with Tahoe in my Hackintosh, the second monitor power off when Tahoe starts. All previous versions of macOS work in my computer with dual monitor.

 

HARDWARE	DESCRIPTION
Motherboard	Gigabyte Z490 VISION G ATX LGA1200 revision 1.1
CPU	Intel Core i7-10700 2.9 GHz 8-Core Processor
Memory	G.Skill Trident Z RGB 32 GB (2 x 16 GB) DDR4-3600 CL16
SSD	Western Digital SN750 500 GB M.2-2280 NVME X 2
Wifi/BT	fenvi FV-T919 PCIe x1 802.11a/b/g/n/ac Wi-Fi Adapter BCM94360CD
Case	Gigabyte C200 Glass ATX
PSU	SeaSonic FOCUS 750 W 80+ Gold Certified Semi-modular

Here is my config.plist

 

What I tried:

 

• igfxonln=1
• igfxfw=2
• cdfon
• no_compat_check

I would appreciate any help 🙏

Edited January 7 by fermento
Change motherboard model

[MaLd0n]

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md#intel-uhd-graphics-610-655-coffee-lake-and-comet-lake-processors

[fermento]

What do you mean @MaLd0n? Is not what I have in my config?

               

 <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
                <dict>
                    <key>AAPL,ig-platform-id</key>
                    <data>BwCbPg==</data>
                    <key>AAPL,slot-name</key>
                    <string>Internal</string>
                    <key>device-id</key>
                    <data>mz4AAA==</data>
                    <key>force-online</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con0-busid</key>
                    <data>BQAAAA==</data>
                    <key>framebuffer-con0-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con0-flags</key>
                    <data>xwMAAA==</data>
                    <key>framebuffer-con0-index</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con0-pipe</key>
                    <data>CQAAAA==</data>
                    <key>framebuffer-con0-type</key>
                    <data>AAQAAA==</data>
                    <key>framebuffer-con1-busid</key>
                    <data>BAAAAA==</data>
                    <key>framebuffer-con1-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con1-flags</key>
                    <data>xwMAAA==</data>
                    <key>framebuffer-con1-index</key>
                    <data>AwAAAA==</data>
                    <key>framebuffer-con1-pipe</key>
                    <data>CAAAAA==</data>
                    <key>framebuffer-con1-type</key>
                    <data>AAgAAA==</data>
                    <key>framebuffer-con2-busid</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con2-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con2-flags</key>
                    <data>xwMAAA==</data>
                    <key>framebuffer-con2-index</key>
                    <data>AgAAAA==</data>
                    <key>framebuffer-con2-pipe</key>
                    <data>CgAAAA==</data>
                    <key>framebuffer-con2-type</key>
                    <data>AAQAAA==</data>
                    <key>framebuffer-fbmem</key>
                    <data>AACQAA==</data>
                    <key>framebuffer-patch-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-stolenmem</key>
                    <data>AAAwAQ==</data>
                    <key>framebuffer-unifiedmem</key>
                    <data>AAAAgA==</data>
                    <key>model</key>
                    <string>Intel UHD Graphics 630</string>
                </dict>

 

[deeveedee]

@fermento I examined your graphics DeviceProperties.  To help us understand your frame buffer patching strategy, please explain why you are doing the following:

• Swap the indices of con1 and con2, so that con1 index is 3 and con2 index is 2
• Change con2 busid from 6 to 1
• Swap con1 and con2 pipes, so that con1 pipe is 8 and con2 pipe is 10
• Change con1 type from DP to HDMI
• set fbmem, stolenmem, unified mem

Also, your DeviceProperties specify properties that don't change anything from the original definition of 3e9b0007.  I have modified your config.plist (attached) to simplify the DeviceProperties, so that your properties are easier for me to understand.

config.plist.zip

[Max.1974]

@fermento 

 

Maybe if you try using these patches in blue, you might be able to make it work. Remove all boot-args related to the iGPU, because they cause conflicts (they are the same as those in the device properties).

[deeveedee]

@Max.1974 I don't think any of those changes would explain why fermento's iGPU worked in earlier versions of macOS, but not Tahoe.  More likely has something to do with changing the connector indices.  He may just need to disable AGDC, but I'd like to hear his explanation of his patching strategy before making any more guesses.

Edited December 15, 2025 by deeveedee

[Max.1974]

 

Hi my dear. After months and weeks of work, my final device-properties configuration is working perfectly. USB-C, Thunderbolt, and HDMI video output are all working on my Lenovo T14 ports. I believe this configuration works because, after studying it many times and running several tests, everything is now functioning correctly. 

😃👊🏻

 

I also remember that the patches highlighted in blue in the left column must be followed, not the numbers of each iGPU. The bus ID sequence and port mapping, as well as the HDMI model (DVS / DP etc), must be respected. For each configuration, we need to know our own hardware details

Edited December 15, 2025 by Max.1974

[fermento]

Hey, thanks for the feedback. I really appreciate it. The bad news is that none of the changes worked.  Below is my current config but before this I tested exactly as @deeveedee proposed in the config. The same as before, the second monitor turns off on login.

 

@deeveedee unfortunately, I don't have any strategy, I have been using this framework patch since Monterrey and I didn't go deeper because was working. I'm all ears, I'm willing to follow any advice.

boot-args - String - amfi=0x80 e1000=0

 

Edited December 16, 2025 by fermento

[brumas2025]

Hi everyone, I'm asking for help! I have macOS Sequoia and Tahoe on my Hackintosh, two monitors are connected to the motherboard: one via DVI-D, the other via HDMI, both work on Windows. The Mac had a monitor that was connected via HDMI, and recently I saw a config that allowed me to get an image on a second monitor that was connected via DVI-D, but the monitor on HDMI stopped working, that is, either one or the other. I am attaching configs for different monitors. How do I achieve simultaneous operation of two monitors?

 

 config DVI-D.plist config HDMI.plist

 

Edited December 16, 2025 by brumas2025

[deeveedee]

@fermento I didn't propose any changes.   I only simplified your DeviceProperties by eliminating the properties that didn't do anything, so you shouldn't have seen any changes in behavior after using the config.plist that I provided.

 

EDIT: Have you searched for hackintosh solutions for your motherboard?  I did a quick search and found this.  That may be the easiest way to find a working solution.  If you want to figure this out yourself without copying someone else's work (the hard way), see my questions below.

 

Since you don't have a strategy, can you please answer the following:

• What are the physical graphics ports on your motherboard (e.g., DP, HDMI).  List the type of each port.
• What are the physical graphics ports on your displays (e.g., DP, HDMI).  What type of adapter (if any) are you using (e.g., DP -> HDMI).
• Have you mapped the physical ports on your motherboard to the logical connectors in your graphics DeviceProperties (e.g. con0, con1, con2).  If so, have you confirmed which logical connectors you're using (e.g., con0 and con2 are in use, but con1 is not used).
• Does your BIOS allow you to configure pre-allocated DVMT as 64MB?

Edited December 16, 2025 by deeveedee

[fermento]

Thanks for your help @deeveedee! I tried the config from SchmockLord but did not work.

 

Quote

What are the physical graphics ports on your motherboard (e.g., DP, HDMI).  List the type of each port.

 

Integrated Graphics Processor-Intel® HD Graphics support:
1 x HDMI port, supporting a maximum resolution of 4096x2160@30 Hz

- Support for HDMI 1.4 version and HDCP 2.3.
  1 x DisplayPort, supporting a maximum resolution of 4096x2304@60 Hz
- Support for DisplayPort 1.4 version, HDCP 2.3, and HDR.
  Maximum shared memory of 512 MB

 

Quote

What are the physical graphics ports on your displays (e.g., DP, HDMI).  What type of adapter (if any) are you using (e.g., DP -> HDMI).

1.   Gigabyte M27Q
   1. HDMI 2.0 x2, Display port 1.2 x1 (capable for HDR), USB Type-C x1
2.   Dell
   1. Analog, DVI-D (Digital) with HDCP -> HDMI to DVI adapter

 

Quote

Have you mapped the physical ports on your motherboard to the logical connectors in your graphics DeviceProperties (e.g. con0, con1, con2).  If so, have you confirmed which logical connectors you're using (e.g., con0 and con2 are in use, but con1 is not used).

 

I don't remember this, how can I verify it?
 

Quote

Does your BIOS allow you to configure pre-allocated DVMT as 64MB?

 

Yes
 

[deeveedee]

@fermento I didn't notice before that you have MaxKernel set to 24.99.99 for WhateverGreen in your config.plist.  This prevents WhateverGreen.kext from loading in Tahoe.  Remove MaxKernel (leave blank) in your config.plist and reboot.  Do your displays both work now?  If not...

 

@fermento Based on what you provided, your Motherboard DP is connected to Display DP (via DP -> DP cable) and your Motherboard HDMI is connected to Display DVI (via HDMI -> DVI adapter).  Is this correct?

 

Since your motherboard BIOS allows you to configure DVMT, you shouldn't be specifying fbmem and stolenmem in config.plist DeviceProperties.  However, you may need to configure DVMT more than 64MB (e.g., 96MB) (The need to increase DVMT was reported by another user when upgrading to Tahoe).  You will need to experiment with this starting with 64MB.  After you configure DVMT in BIOS, remove the following properties from your DeviceProperties:

• framebuffer-fbmem
• framebuffer-stolenmem
• framebuffer-unifiedmem

After setting DVMT in BIOS and removing fbmem, stolenmem and unifiedmem from DeviceProperties, reboot.  If you get a kernel panic or blackscreen, increase DVMT in BIOS to next incremental value and try again until you can boot with your revised DeviceProperties.

 

Are both displays working now?  If not...

 

There are multiple ways to determine which displays are connected to which logical frame buffer connectors con0, con1, con2....  I typically use Hackintool.  Download Hackintool if you don't already have it. 

 

Modify your config.plist so that you are not swapping the con1 and con2 indices/pipes as I have done in the attached config.plist.  Change the con2 type to HDMI as I have done in the attached config.plist.  Boot with the modified DeviceProperties (you should just be able to use my attached config.plist if you want to).

 

Are both displays working now?  If not...

 

Open Hackintool and navigate to Patch > Connectors.  The connectors con0, con1, con2... will be listed in order starting with con0.  From the listing, can you tell which logical connectors (con0, con1, con2) are connected to displays?  if not, can you boot with a previous "working" version of macOS and use Hackintool to determine which connectors are connected to displays?  If not, post a screenshot of your Hackintool connectors window.

 

EDIT: These are my notes for continued debugging.  Ignore these for now:

• Increase DVMT pre-alloc (see here)
• Boot Sequoia with revised config.plist
• busid = 1?
• Confirm Active HDMI->DVI adapter
• OC/Kexts (versions)
• Add igfxfw=2
• framebuffer-unifiedmem
• lspcon (unlikely)

 

config.plist

Edited December 17, 2025 by deeveedee

[deeveedee]

@fermento I didn't notice before that you have MaxKernel set to 24.99.99 for WhateverGreen in your config.plist.  This prevents WhateverGreen.kext from loading in Tahoe.  I have modified my previous post to address this first before we continue.

[jlrycm]

@fermento are you using laobamac fork of Whatevergreen to boot macOS Tahoe?

[Asural]

Question: The config.plist does not contain the USBMap.kext for the Tahoe. Normally this just means that the USB does not work, but will this not interfere with the UHD630?
 

[deeveedee]

@jlrycm fermento is using iGPU, not dGPU.  laobamac's fork doesn't help this hack.

 

EDIT: @Asural No, the USB map will not interfere with iGPU.  The config.plist adds an ACPI patch (SSDT) for USB, so for now, we don't know if USB is working propertly.  Maybe another thread? 

Edited December 17, 2025 by deeveedee

[jlrycm]

4 hours ago, deeveedee said:

 fermento is using iGPU, not dGPU.  laobamac's fork doesn't help this hack

So the fork would not help overcoming the Tahoe installation or OTA update stall issues experienced by most of us when using Whatevergreen in Tahoe? I know the thread was posted asking for help with the 630 dual monitor problem but since I saw Tahoe was referenced, I thought it would be good for the user to know that the fork exists and can help with Tahoe installation/OTA update stall issues.

Edited December 17, 2025 by jlrycm

[deeveedee]

@jlrycm No.  iGPU / Tahoe has no issues with Acidanthera's WhateverGreen.kext version 1.7.0.

[jlrycm]

6 minutes ago, deeveedee said:

No.  iGPU / Tahoe has no issues with Acidanthera's WhateverGreen.kext version 1.7.0

So just to confirm, you are saying that the issues experienced with WEG and Tahoe were the result of using dGPU and not iGPU?

[deeveedee]

Yes.  I'm typing this on my HackBookPro16,2 laptop which has only UHD630 iGPU and am using Acidanthera's WhateverGreen.kext 1.7.0.  Same with my HackMIni8,1 that has only UHD630 iGPU.  If you can find laobamac's github repo with the proposed changes, you'll see what is being fixed.  Nothing to do with iGPU.

Edited December 17, 2025 by deeveedee

[fermento]

8 hours ago, deeveedee said:

@fermento I didn't notice before that you have MaxKernel set to 24.99.99 for WhateverGreen in your config.plist.  This prevents WhateverGreen.kext from loading in Tahoe.  Remove MaxKernel (leave blank) in your config.plist and reboot.  Do your displays both work now?  If not...

 

@fermento Based on what you provided, your Motherboard DP is connected to Display DP (via DP -> DP cable) and your Motherboard HDMI is connected to Display DVI (via HDMI -> DVI adapter).  Is this correct?

 

Since your motherboard BIOS allows you to configure DVMT, you shouldn't be specifying fbmem and stolenmem in config.plist DeviceProperties.  However, you may need to configure DVMT more than 64MB (e.g., 96MB) (The need to increase DVMT was reported by another user when upgrading to Tahoe).  You will need to experiment with this starting with 64MB.  After you configure DVMT in BIOS, remove the following properties from your DeviceProperties:

• framebuffer-fbmem
• framebuffer-stolenmem
• framebuffer-unifiedmem

After setting DVMT in BIOS and removing fbmem, stolenmem and unifiedmem from DeviceProperties, reboot.  If you get a kernel panic or blackscreen, increase DVMT in BIOS to next incremental value and try again until you can boot with your revised DeviceProperties.

 

Are both displays working now?  If not...

 

There are multiple ways to determine which displays are connected to which logical frame buffer connectors con0, con1, con2....  I typically use Hackintool.  Download Hackintool if you don't already have it. 

 

Modify your config.plist so that you are not swapping the con1 and con2 indices/pipes as I have done in the attached config.plist.  Change the con2 type to HDMI as I have done in the attached config.plist.  Boot with the modified DeviceProperties (you should just be able to use my attached config.plist if you want to).

 

Are both displays working now?  If not...

 

Open Hackintool and navigate to Patch > Connectors.  The connectors con0, con1, con2... will be listed in order starting with con0.  From the listing, can you tell which logical connectors (con0, con1, con2) are connected to displays?  if not, can you boot with a previous "working" version of macOS and use Hackintool to determine which connectors are connected to displays?  If not, post a screenshot of your Hackintool connectors window.

 

EDIT: These are my notes for continued debugging.  Ignore these for now:

• Increase DVMT pre-alloc (see here)
• Boot Sequoia with revised config.plist
• busid = 1?
• Confirm Active HDMI->DVI adapter
• OC/Kexts (versions)
• Add igfxfw=2
• framebuffer-unifiedmem
• lspcon (unlikely)

 

config.plist 48.78 kB · 3 downloads

 

@deeveedee Thank you very much ❤️. I really appreciate a lot of the help you gave me. The main problem was the MaxKernel set to 24.99.99 on WhateverGreen. I thought I need that to run Tahoe for now but that was not true. So, after that change I have dual monitors in Tahoe.

 

But, because of all your information that you gave me, I will try to improve my Framebuffer patch during the following days. Mostly because on macOS login screen, the monitors flicker a lot for a consider amount of seconds, sometimes 30, before being able to use them. I will upload a video later.

 

In addition, I updated DVMT to 96MB. I can go 128, do you think will be usefuil?

 

I cleared the properties that you said I don't need.

 

@Asural I think my USB is working fine, at least the port I tried but when I get some time I will test all the ports.

 

Thanks again @deeveedee, you are the best!

 

 

 

[fermento]

6 hours ago, jlrycm said:

@fermento are you using laobamac fork of Whatevergreen to boot macOS Tahoe?

 

No, default WhateverGreen

[fermento]

9 hours ago, deeveedee said:

@fermento I didn't notice before that you have MaxKernel set to 24.99.99 for WhateverGreen in your config.plist.  This prevents WhateverGreen.kext from loading in Tahoe.  Remove MaxKernel (leave blank) in your config.plist and reboot.  Do your displays both work now?  If not...

 

@fermento Based on what you provided, your Motherboard DP is connected to Display DP (via DP -> DP cable) and your Motherboard HDMI is connected to Display DVI (via HDMI -> DVI adapter).  Is this correct?

 

Since your motherboard BIOS allows you to configure DVMT, you shouldn't be specifying fbmem and stolenmem in config.plist DeviceProperties.  However, you may need to configure DVMT more than 64MB (e.g., 96MB) (The need to increase DVMT was reported by another user when upgrading to Tahoe).  You will need to experiment with this starting with 64MB.  After you configure DVMT in BIOS, remove the following properties from your DeviceProperties:

• framebuffer-fbmem
• framebuffer-stolenmem
• framebuffer-unifiedmem

After setting DVMT in BIOS and removing fbmem, stolenmem and unifiedmem from DeviceProperties, reboot.  If you get a kernel panic or blackscreen, increase DVMT in BIOS to next incremental value and try again until you can boot with your revised DeviceProperties.

 

Are both displays working now?  If not...

 

There are multiple ways to determine which displays are connected to which logical frame buffer connectors con0, con1, con2....  I typically use Hackintool.  Download Hackintool if you don't already have it. 

 

Modify your config.plist so that you are not swapping the con1 and con2 indices/pipes as I have done in the attached config.plist.  Change the con2 type to HDMI as I have done in the attached config.plist.  Boot with the modified DeviceProperties (you should just be able to use my attached config.plist if you want to).

 

Are both displays working now?  If not...

 

Open Hackintool and navigate to Patch > Connectors.  The connectors con0, con1, con2... will be listed in order starting with con0.  From the listing, can you tell which logical connectors (con0, con1, con2) are connected to displays?  if not, can you boot with a previous "working" version of macOS and use Hackintool to determine which connectors are connected to displays?  If not, post a screenshot of your Hackintool connectors window.

 

EDIT: These are my notes for continued debugging.  Ignore these for now:

• Increase DVMT pre-alloc (see here)
• Boot Sequoia with revised config.plist
• busid = 1?
• Confirm Active HDMI->DVI adapter
• OC/Kexts (versions)
• Add igfxfw=2
• framebuffer-unifiedmem
• lspcon (unlikely)

 

config.plist 48.78 kB · 4 downloads

 

With the Framebuffer patch from this config I cannot boot.

[fermento]

@deeveedee This are the problems I'm having on boot, but is not new, I had them during all the year. If I can fix them, better 😁. Any suggestions?

 

 

 

[deeveedee]

@fermento Can you please upload your config.plist that works with dual-monitor in Tahoe?  I'd like to review it before making any more suggestions.  Thanks.

 

EDIT: There should be no need to increase DVMT pre-allocated beyond 96MB.

 

EDIT2: @fermento If you want help refining your framebuffer patches, I'll need the answers to the questions here in my previous post..

Edited December 17, 2025 by deeveedee