ASRock H310M-HDV - dual monitor problems

[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

[deeveedee]

@brumas2025 Your Hackintool screenshots show the same logical connector (con1, index 2) for each display.  This means that one of your displays isn't being shown by Hackintool.  Since it seems that one of your displays is on logical connector con1, have you determined whether your other display is on con0 or con2?

 

Could you please convert your "config HDMI" graphics framebuffer patches from all-data format to individual Device Properties (like your "config DVI") and then re-post your revised config-HDMI.plist?  That would make it easier for us to read and edit.

 

My initial thoughts are as follows:  I have seen this exact behavior (where the connection of one display results in a black screen on the other display) when the wrong framebuffer (AAPL,ig-platform-id) is used.  Have you tested other CoffeeLake frame buffers?  You may need to try all CoffeeLake frame buffers (defined here) until you find one that works better.  Take notes as you are testing so you can compare results for each framebuffer test.

 

EDIT: I know you know this, but for others who are reading this and posibly learning from it, the CoffeeLake framebuffers that you test should only be those with 3 connectors.  You may actually find that the best framebuffer for your hack is a "mobile" framebuffer.

Edited December 18, 2025 by deeveedee

[brumas2025]

9 hours ago, deeveedee said:

You may need to try all CoffeeLake frame buffers (defined here) until you find one that works better.  Take notes as you are testing so you can compare results for each framebuffer test.

Thanks! I'm working on it now.  Do I need to try with the configuration where the DVI monitor works?

[brumas2025]

9 hours ago, deeveedee said:

Could you please convert your "config HDMI" graphics framebuffer patches from all-data format to individual Device Properties (like your "config DVI") and then re-post your revised config-HDMI.plist?  That would make it easier for us to read and edit.

Is that what you meant?

[deeveedee]

@brumas2025 Yes - that's what I meant.  Could you please test this new "config HDMI" plist to make sure it still works like your original "all-data" version?  After you have tested it, please upload it here.

 

I hope to have time to look at this later today.  Hopefully others can help and offer suggestions, too.  Sorry if you already provided this information, but please answer/confirm the following:

1. What CPU are you using?  I see that it is i3-9100 from the other thread.
2. Please confirm that when you boot macOS with "config-DVI-D.plist", only your DVI-D display is working. The HDMI display is black.
3. Please confirm that when you boot macOS with "config-HDMI.plist", only your HDMI display is working.  The DVI-D display is black.
4. Please specify the port types on the displays (e.g., the display connected to the motherboard's DVI-D port has a DVI-D port and the display connected to the motherboard's HDMI port has a HDMI port)

Edited December 19, 2025 by deeveedee

[brumas2025]

 

• What CPU are you using?  I see that it is i3-9100 from the other thread.  yes
• Please confirm that when you boot macOS with "config-DVI-D.plist", only your DVI-D display is working. The HDMI display is black. yes
• Please confirm that when you boot macOS with "config-HDMI.plist", only your HDMI display is working.  The DVI-D display is black.  yes
• Please specify the port types on the displays (e.g., the display connected to the motherboard's DVI-D port has a DVI-D port and the display connected to the motherboard's HDMI port has a HDMI port) - The DVI output of the motherboard is connected via a VGA adapter to a monitor with a VGA input. The HDMI output of the motherboard is connected directly to a monitor with an HDMI input.t.

 

config DVI-D.plist

 

Edited December 19, 2025 by brumas2025

[deeveedee]

@brumas2025 In my experience with adapters that convert to VGA, they sometimes have syncronizing problems that interfere with the other connected display.  I don't know why this is the case, but I'm letting you know that we may not be able to resolve this (but I won't give up that easily).  Give me some time to review your two config.plists and I'll return with a proposed solution.  Hopefully others can review and suggest solutions, too.

 

EDIT: Hopefully, because your displays work in Windows, we can get them to work in macOS, too.

 

EDIT2: For others who are watching this to learn or help, the displays are connected as follows:

Connector		Motherboard		Display
Unknown			DVI			VGA
Unknown			HDMI			HDMI

 

Edited December 19, 2025 by deeveedee

[deeveedee]

@verdazil Would you mind helping @brumas2025 to determine the connector map (con0, con1...) using your IORegistry technique?

[deeveedee]

@brumas2025 You posted your config-DVI-D.plist but I was looking for your revised config-HDMI.plist.  I have revised your config-HDMI.plist (converting from all-data format) so that it is easier for me to read and edit (I hate the all-data format, sorry  ).  Please test the attached config.plist to make sure it still behaves as your original config-HDMI.plist.  thank you.

config HDMI.plist.zip

[verdazil]

16 minutes ago, deeveedee said:

@verdazil Would you mind helping @brumas2025 to determine the connector map (con0, con1...) using your IORegistry technique?

Spoiler

 

[brumas2025]

25 minutes ago, deeveedee said:

@brumas2025 You posted your config-DVI-D.plist but I was looking for your revised config-HDMI.plist.  I have revised your config-HDMI.plist (converting from all-data format) so that it is easier for me to read and edit (I hate the all-data format, sorry  ).  Please test the attached config.plist to make sure it still behaves as your original config-HDMI.plist.  thank you.

config HDMI.plist.zip 6.08 kB · 1 download

The HDMI monitor was loaded with this config.

[brumas2025]

17 часов назад Вердасил сказал:

  Раскрыть скрытое содержимое

 

 

 

 

Here are my IORegistryExplorer , one for HDMI, the other for DVI.

iMac DVI.ioreg.zip iMac HDMI.ioreg.zip

Edited December 20, 2025 by brumas2025

[deeveedee]

@brumas2025 As I look at the connector photo that you posted, I see that your motherboard has a VGA connector.  it may be easier for us to find a working solution if you connect your VGA display to the VGA connector on your motherboard.  Do you have a VGA -> VGA cable?

[brumas2025]

11 часов назад deeveedee сказал:

@brumas2025Когда я смотрю на фотографию разъема, которую вы разместили, я вижу, что ваша материнская плата имеет разъем VGA. Нам может быть легче найти рабочее решение, если вы подключите дисплей VGA к разъему VGA на вашей материнской плате. У вас есть кабель VGA -> VGA?

Okay, but I'll connect it to the VGA connector. My responses take a very long time to moderate and don't arrive quickly....

Edited December 20, 2025 by brumas2025

[brumas2025]

11 часов назад deeveedee сказал:

 У вас есть кабель VGA -> VGA?

I tried to connect it directly to the VGA connector. When booting with the DVI configuration, both monitors have a black screen, and with the HDMI configuration, only HDMI works. in DVI mode, I connected via Anydesk - I attach a screenshot.

iMac VGA.ioreg.zip

[deeveedee]

@brumas2025 With the VGA->VGA cable, we'll need to modify your DeviceProperties.

 

 

14 hours ago, brumas2025 said:

Here are my IORegistryExplorer , one for HDMI, the other for DVI.

IORegistry shows what you observed in Hackintool: when the displays are connected to your motherboard DVI-D and HDMI ports, both displays appear to be connected to the same logical framebuffer connector (con1).  I'm going to review your two config.plists and see if I have a proposed new config.plist.  I hope that others can look at this and propose solutions as well.

Edited December 20, 2025 by deeveedee

[brumas2025]

2 минуты назад deeveedee сказал:

@brumas2025 Я собираюсь просмотреть ваши два config.plists и посмотреть, есть ли у меня предлагаемый новый config.plist. Я надеюсь, что другие смогут посмотреть на это и также предложить решения.

Thank you, I will be waiting for your suggestions.

[deeveedee]

@brumas2025 Please test your VGA display (connected by VGA -> VGA cable) with the attached config.plist.  Disconnect the HDMI display (so that your motherboard has only the VGA display connected and no other displays).  If your VGA display works with this config.plist, please post the Hackintool connector screenshot.  Thank you.

config-VGA.plist.zip

[brumas2025]

2 часа назад deeveedee сказал:

@brumas2025 Please test your VGA display (connected by VGA -> VGA cable) with the attached config.plist.  Disconnect the HDMI display (so that your motherboard has only the VGA display connected and no other displays).  If your VGA display works with this config.plist, please post the Hackintool connector screenshot.  Thank you.

config-VGA.plist.zip 5.94 kB · 1 download

Booted up with your trial config, only the cable is connected directly to the VGA connector. The black screen!!! I connected via Anydesk - screenshots are attached.

 

Расценки

 

Расценки

Edited December 20, 2025 by brumas2025

[deeveedee]

@brumas2025 is there a BIOS setting for your motherboard that configures the VGA behavior?  If so, is VGA set to the primary or default display in BIOS?

 

EDIT: Your use of AnyDesk to connect to the Shared Desktop is very clever.  Well done!

 

EDIT2: @brumas2025 Please make sure that your VGA display works with the VGA -> VGA cable when booting Windows.

Edited December 20, 2025 by deeveedee

[brumas2025]

1 час назад deeveedee сказал:

@brumas2025 

is there a BIOS setting for your motherboard that configures the VGA behavior?  If so, is VGA set to the primary or default display in BIOS? - there is only a setting where it is disabled, but I have it enabled.

 

EDIT: Your use of AnyDesk to connect to the Shared Desktop is very clever.  Well done! Yes. thanks

Please make sure that your VGA display works with the VGA -> VGA cable when booting Windows. Yes, everything is working.

 

Edited December 20, 2025 by brumas2025

[deeveedee]

@brumas2025 I can't read the label for that BIOS setting.  it looks like "IGPU Multi Monitor."  Have you tested after setting "IGPU Multi Monitor" to Disabled?

 

Also, please post your full OC folder with the OC/ACPI and OC/Kexts folders.  Thank you.

 

EDIT: I see that your BIOS configuration for Primary Graphics Adapter is "Onboard."  That looks correct, but it would be good to check the other options.

Edited December 20, 2025 by deeveedee

[brumas2025]

43 минуты назад Дивиди сказал:

see that your BIOS configuration for Primary Graphics Adapter is "Onboard." That looks correct, but it would be good to check the other options

. I tried, but nothing changed..

 

20-12-25.zip

Edited December 20, 2025 by brumas2025

[deeveedee]

I reviewed your full EFI.  You definitely know what you are doing.  Since your hack does not have a dGPU (you're only using the Intel iGPU graphics), Whatevergreen.kext 1.7.1d7 is not necessary.  You can stay with Acidanthera's WhateverGreen.kext 1.7.0. it does not matter, but if I were you, I would stay with Acidanthera's kext for now.

 

Since macOS does not appear to recognize your motherboard's VGA port, we'll need to continue using your DVI-D -> VGA adapter as you have already done.  I'm sorry I wasted your time with that experiment.  

 

At this point, since both of your displays appear to be mapped to logical framebuffer connector con1, I'm not sure how to proceed.  I'm hoping this has something to do with the fact that you are swapping the con1 and con2 indices and pipes in your config-DVID.plist.  Could you please restore your DVI-D->VGA adapter (don't use the VGA->VGA cable) and re-connect your HDMI display, then test with the attached config.plist.  This test config.plist changes all port types to HDMI and adds a property to disable iGPU AGDC.

 

If your hack boots with this config.plist, please post the Hackintool connectors screenshot.  thank you.

 

config-H31M-test1.plist.zip

[brumas2025]

46 minutes ago, deeveedee said:

 

If your hack boots with this config.plist, please post the Hackintool connectors screenshot.  thank you.

I booted up with your example, only one monitor (HDMI) is working, I changed the kext.

Quote

 

Edited December 20, 2025 by brumas2025