ASRock H310M-HDV - dual monitor problems

[deeveedee]

@brumas2025 Thank you for clearing up the confusion.  I thought that the "wake from sleep" behavior was something new after we fixed the horizontal stripes.  

 

If you decide that you want to try to fix the wake behavior when you use two displays, you can follow the techniques that we employed here and you can always post again in this thread to ask for help.

[Max.1974]

14 hours ago, Asural said:

Parece que o reconhecimento da porta USB do USBMap.command está incorreto, por isso não pode ser criado.

Como todos os HSx são reconhecidos como USB 3.0, não há problemas com a operação, então acho que não há problema em usar.

 

A diferença na velocidade de comunicação entre USB2.0 e USB3.0 é claramente visível.
 

Se o USBMap.kext que anexei funcionar, forneça um instantâneo do USB no Hackintool.

 

Você tem um disco sobressalente para testar com uma versão diferente, como o Sequoia?
 

 

@Asural  @brumas2025 Hi ! Have you already tried using USBToolBox + UTBMap first on Windows 10/11? Then convert it (extract it, if everything is correct) with USBPorts and use the SSDTs rebuilt that way.

On Sequoia 26.2, this is how I managed to get full functionality of the ports, because my hubs and USB 2.0 devices were not being recognized on the USB 3.0 ports.

That’s how I did it. I also use a modified SSDT that I have, and I have an easy video showing how to adjust it.

 

 

 

 

 

 

[Asural]

9 minutes ago, Max.1974 said:

 

@Asural  @brumas2025 Hi ! Have you already tried using USBToolBox + UTBMap first on Windows 10/11? Then convert it (extract it, if everything is correct) with USBPorts and use the SSDTs rebuilt that way.

On Sequoia 26.2, this is how I managed to get full functionality of the ports, because my hubs and USB 2.0 devices were not being recognized on the USB 3.0 ports.

 I was using USBToolBox until Sequoia.
It was convenient because it didn't require selecting the SMBIOS, but even after modifying UTBMap on the Tahoe, it stopped working, so I switched to USBMap.
I was planning to ask @brumas2025 to try it with Sequoia if there were any problems, but there are no particular problems so I think it's fine to leave it as it is.
 

[deeveedee]

I may have missed this... Does brumas2025 have a USB problem that needs to be solved?  I thought his USB ports were all working.

[Asural]

25 minutes ago, deeveedee said:

I may have missed this... Does brumas2025 have a USB problem that needs to be solved?  I thought his USB ports were all working.

When comparing the original ioreg with the latest ioreg, the USB connection is the same, so I don't think there was a problem from the start.
The problem is that there are more than 14 port connections based on the DSDT.aml contents, but since they are not connected to anything other than USB, I think it's safe.
 

[Max.1974]

Maybe you need remap again with Windows, and maybe you could consider a simple solution that, in my case, improved the use of USB ports on the Hackintosh.

 

"Compile your SSDT-RHUB to better performance USB 3.0 in MacOs and Hackintosh build."

 

Spoiler

 

 

You can enable subtitles in your native language and easily understand the video. 

[Max.1974]

1 hour ago, Asural said:

 I was using USBToolBox until Sequoia.
It was convenient because it didn't require selecting the SMBIOS, but even after modifying UTBMap on the Tahoe, it stopped working, so I switched to USBMap.
I was planning to ask @brumas2025 to try it with Sequoia if there were any problems, but there are no particular problems so I think it's fine to leave it as it is.
 

 

The crucial point is that USBMap also throws errors, and I believe that Sequoia “prefers” reading SSDTs. That’s why, after doing the mapping in Windows, I boot into macOS and extract everything with Hackintool using USBToolBox + UTBMap, and with the SSDTs plus the USBPorts kext it works properly. If needed, the USBMap injector also works well.

I redid my USB mapping from scratch after updating my BIOS, both on the Lenovo T14 and on the Raptor Lake system, which are my main Hackintosh setups.

[deeveedee]

25 minutes ago, Max.1974 said:

The crucial point is that USBMap also throws errors, and I believe that Sequoia “prefers” reading SSDTs. That’s why, after doing the mapping in Windows...

 

Just offering my experimental conclusions as an alternative view: OCLP (Dortania/Acidanthera Open Core Devs) patches USB with USB Ports kext. I have not found any evidence of macOS 'preference'  for SSDT patches over kexts for USB.

[Asural]

2 hours ago, deeveedee said:

 

Just offering my experimental conclusions as an alternative view: OCLP (Dortania/Acidanthera Open Core Devs) patches USB with USB Ports kext. I have not found any evidence of macOS 'preference'  for SSDT patches over kexts for USB.

There is a difference between patching before booting up MacOS or patching after booting up, and I prefer patching after booting up.
Some devices require SSDT, so it depends on the situation.
As for USB, I don't want to go through the hassle.
 

 

3 hours ago, Max.1974 said:

 

 

The crucial point is that USBMap also throws errors, and I believe that Sequoia “prefers” reading SSDTs. That’s why, after doing the mapping in Windows, I boot into macOS and extract everything with Hackintool using USBToolBox + UTBMap, and with the SSDTs plus the USBPorts kext it works properly. If needed, the USBMap injector also works well.

I redid my USB mapping from scratch after updating my BIOS, both on the Lenovo T14 and on the Raptor Lake system, which are my main Hackintosh setups.

 

3 hours ago, Max.1974 said:

Maybe you need remap again with Windows, and maybe you could consider a simple solution that, in my case, improved the use of USB ports on the Hackintosh.

 

"Compile your SSDT-RHUB to better performance USB 3.0 in MacOs and Hackintosh build."

 

  Reveal hidden contents

 

 

You can enable subtitles in your native language and easily understand the video. 

We are currently in the functional testing stage, so it seems that any talk of performance improvements will come much later.
HackinTool displays USB transfer speeds, but it is unclear whether the device will actually operate at the displayed speeds.
Once any problems are found, it should be possible to take measures using SSDT or kext.
 

[brumas2025]

6 hours ago, deeveedee said:

@brumas2025 Thank you for clearing up the confusion.  I thought that the "wake from sleep" behavior was something new after we fixed the horizontal stripes.  

 

If you decide that you want to try to fix the wake behavior when you use two displays, you can follow the techniques that we employed here and you can always post again in this thread to ask for help.

thank you, I will try to edit the USB ports, since the transfer rate via usb 3 is very low, and then I will return to the problem with waking up.

[brumas2025]

12 hours ago, Max.1974 said:

 

@Asural  @brumas2025 Hi ! Have you already tried using USBToolBox + UTBMap first on Windows 10/11? Then convert it (extract it, if everything is correct) with USBPorts and use the SSDTs rebuilt that way.

On Sequoia 26.2, this is how I managed to get full functionality of the ports, because my hubs and USB 2.0 devices were not being recognized on the USB 3.0 ports.

That’s how I did it. I also use a modified SSDT that I have, and I have an easy video showing how to adjust it.

Following your advice, I created a UTBMap.kext  in Windows , additionally added USBToolBox.kext and the speed of the USB 3 port have increased significantly, thank you for the tip.

 

added: this did not affect the monitors waking up...

 

Quote

Quote

Quote

Quote

 

UTBMap.kext.zip iMac 8-01-26.ioreg.zip

Edited January 8 by brumas2025

[Asural]

39 minutes ago, brumas2025 said:

Following your advice, I created a UTBMap.kext  in Windows , additionally added USBToolBox.kext and the speed of the USB 3 port have increased significantly, thank you for the tip.

 

added: this did not affect the monitors waking up...

 

 

UTBMap.kext.zip 1.07 kB · 1 download iMac 8-01-26.ioreg.zip 3.67 MB · 0 downloads

On the USB display screen of HatckinTool, plug USB 2.0 into all 6 ports on the front, then plug USB 3.0 into two of the two USB 3.0 ports to display the results.
The inserted ports will turn green.
 

EDIT：

I checked the UTBMap.kext connection and USB 3.0/2.0 works fine.
It was just that the HatckinTool display was incorrect.
 

Edited January 8 by Asural

[Asural]

9 hours ago, brumas2025 said:

thank you, I will try to edit the USB ports, since the transfer rate via usb 3 is very low, and then I will return to the problem with waking up.

 Please try using the attached USBMap.kext on your Tahoe. Change the name as appropriate.

I was concerned that the usb-port-type for HS02, HS03, and HS04 was set to 3, but I fixed it according to UTBMap.kext.
 

H310M_USBMap.kext.zip

Edited January 8 by Asural

[brumas2025]

42 minutes ago, Asural said:

I was concerned that the usb-port-type for HS02, HS03, and HS04 was set to 3, but I fixed it according to UTBMap.kext.

Quote

Quote

After your edit, the speed is no worse than when using other kext (UTBMap.kext end USBToolBox.kext).

Thanks for the help!!!

This is an external USB 3 disk check.

iMac_new.ioreg.zip

[Asural]

36 minutes ago, brumas2025 said:

After your edit, the speed is no worse than when using other kext (UTBMap.kext end USBToolBox.kext).

Thanks for the help!!!

This is an external USB 3 disk check.

iMac_new.ioreg.zip 3.57 MB · 0 downloads

IIt seems to work the same as UTBMap on Ioreg, but since USBToolbox cannot be used on Tahoe, please use the attached USBMap.kext for screen testing.
(I still have some doubts, but I think it works for now.)
 

 I would like to share my system settings to continue display testing.
Are the following settings correct?
(I can't read them either, so please judge by the icon.)
 

Screensaver time setting.

Edited January 8 by Asural

[brumas2025]

1 hour ago, Asural said:

IIt seems to work the same as UTBMap on Ioreg, but since USBToolbox cannot be used on Tahoe, please use the attached USBMap.kext for screen testing.
(I still have some doubts, but I think it works for now.)
 

 I would like to share my system settings to continue display testing.
Are the following settings correct?
(I can't read them either, so please judge by the icon.)

but after all, with such settings, monitors will not be able to fall asleep at all? I wanted them to go out and light up when I needed to..

[Asural]

6 hours ago, brumas2025 said:

but after all, with such settings, monitors will not be able to fall asleep at all? I wanted them to go out and light up when I needed to..

 I would like to first confirm whether the screen display continues to operate normally and stably when sleep/wakeup is disabled and Sleep is not entered.
1. Does the OpenCore Menu appear on both screens after startup?
2. Does the Apple logo appear on both screens even if the WEG switches display modes after startup?
3. Which monitor is the main monitor?
4. Can I resume operation by shortening the screen saver time?

 

Regarding sleep/wakeup, I would like to first test Sleep in the Apple menu, and then try automatic Sleep.
Please also observe how many seconds it takes for the monitor to resume operation after Sleep, and wait about 5 minutes.
 

[Max.1974]

23 hours ago, deeveedee said:

 

Apenas oferecendo minhas conclusões experimentais como uma visão alternativa: OCLP (Dortania/Acidanthera Open Core Devs) patches USB com portas USB kext. Não encontrei nenhuma evidência de 'preferência' do macOS para patches SSDT em vez de kexts para USB.

 

Hello, I don’t use OCLP. I only use UTBMap + USBToolBox generated on Windows, and after everything is working, I extract USBPorts with Hackintool, generating the USBPorts.kext plus two SSDTs. If you didn’t understand, I can take a screenshot here. But I admit that I didn’t fully understand your question. 

 

Regarding the preference, the situation at the beginning is clear: the user used to spend a long time waiting for the USB map (kext) to “ruminate” the system and never install. I gave my opinion based on what I believe — that Tahoe prefers the SSDT-based approach rather than kexts. This is due to the fact that newer Macs use Thunderbolt, which is not controlled by common USB kexts. 

 

 

And the time I spent with my Lenovo T14 was, in my view, a long time to reach this understanding. Once I achieve high transfer speeds of up to 10 Gbps—whether through regular USB-C or Thunderbolt, since it has both, in addition to USB 3.2 and USB 3.0/2.0—I tested this myself. And certainly, OCLP does not test all possible hardware configurations. 

 

 

If possible, I don’t want to have to discuss whether this is true or not. I’m simply saying that, in my view, the preference is for SSDTs. And I use an SSDT for the USB ports (HS and SS) that is completely modified, as shown in the video I created. I also believe that the real difference would only affect a few users who still have older HDDs—like my good old WD Gold (2017) 4 TB, which still maintains legitimate and useful speeds—because since Sequoia this had been unusable, until I consolidated this approach and it stopped corrupting large files over 50 GB.  And speaking of that, I limit the speed to 8 GT/s to avoid conflicts on a single Thunderbolt port. Even so, I still achieve the same speed as the external NVMe indicated in System Preferences.

 

Spoiler

 

Edited January 8 by Max.1974

[Max.1974]

Thunderbolt External Acasis Nvme Crucial  8.0 GT/s speed (Lenovo T14) 

 

 

Internal WD SN 770 Black Nvme 8.0 GT/s 

 

[Asural]

4 hours ago, Max.1974 said:

Thunderbolt External Acasis Nvme Crucial  8.0 GT/s speed (Lenovo T14) 

Internal WD SN 770 Black Nvme 8.0 GT/s 

II think it's directed at me, but it doesn't seem like Type-C is interfering with the discussion over there, so I'll put it on hold for now.
 

[Max.1974]

49 minutos atrás, Asural disse:

Acho que é direcionado a mim, mas não parece que o Tipo-C esteja interferindo na discussão lá, então vou colocá-lo em espera por enquanto.
 

 

Hello Asural, I didn’t mention it directed at you specifically; I just wanted to say that the experience I had with SSDTs on Tahoe and other macOS systems was truly a game changer.

[brumas2025]

8 hours ago, Asural said:

 I would like to first confirm whether the screen display continues to operate normally and stably when sleep/wakeup is disabled and Sleep is not entered.
 

1. Does the OpenCore menu appear on both screens after startup? Yes, they do.
2. Does the Apple logo appear on both screens, even if WEG switches display modes after startup? After switching, it appears on the Hdmi monitor.
3. Which monitor is the main one? Hdmi.
4. Can I resume work by reducing the screen saver time? I didn't understand the question

 

Regarding sleep/wakeup, I would like to first test Sleep in the Apple menu, and then try automatic Sleep.
Please also observe how many seconds it takes for the monitor to resume operation after Sleep, and wait about 5 minutes. I'll try to wait 5 minutes.

 

Quote

 

Edited January 9 by brumas2025

[Asural]

1 hour ago, brumas2025 said:

4. Can I resume work by reducing the screen saver time? I didn't understand the question

Translation failed. Can you resume work after the screensaver starts?

 

Sleep/Wakeup itself should work normally, so I've attached a revised config-H31-test-7-6.plist file for you to try.

 

1. Deleted and disabled unnecessary APCI SSDTs.
2. Disabled Kernel/Add/HibernationFixup.kext.
3. Changed boot-args to "-v amfi=0x80". Please also test without -v and let me know if there's a difference.
4. It seems that LSPCON settings are required for framebuffer-con2, so added them.

 

ADD:

Do the two monitors have the same resolution?
 

Mod config-H31-test-7-6.plist.zip

Edited January 9 by Asural

[brumas2025]

58 minutes ago, Asural said:

Translation failed. Can you resume work after the screensaver starts?

 

Translation error. Can you resume your work after starting the screensaver?  Yes, it's fine.
 
 I have attached the corrected config-H31-test-7-6.plist file so that you can try it. loading into two black screens. it does not connect remotely. overheating only via the power button.

 
add:
Do two monitors have the same resolution? the resolution is the same 1080p.

[Asural]

3 hours ago, brumas2025 said:

 I have attached the corrected config-H31-test-7-6.plist file so that you can try it. loading into two black screens. it does not connect remotely. overheating only via the power button.

 

It looks like you'll need to modify config-H31-test-7-6.plist while checking the items.

 

1. Set SSDT-EC-USBX.aml in ACPI/Add/item1 to Enabled = NO. This has the same function as item3/SSDT-EC.aml.
2. Set HibernationFixup.kext in Kernel/add/item5 to Enabled = NO. Wakeup should be possible with SSDT.

 

Please check that the system boots normally in this state and that sleep/wakeup functions work.
 

@brumas2025 Does the HDMI cable use HDMI 2.0 (4K)?
 

Edited January 9 by Asural