KVM display switching issue

[Danish297]

@Edhawk @Shaneee @leesurone @All

need your help again

My current Setup is as below:
Machine A
Dual-boot system:
Hackintosh (macOS 26.6)
Ubuntu Linux

Machine B
Windows 11 Pro

Hardware
Keyboard, mouse, and monitor are connected through a TESmart KVM switch.

Scenario 1: Windows 11 Pro + Ubuntu
When Machine B (Windows 11 Pro) and Machine A (Ubuntu) are connected through the TESmart KVM, display switching works correctly in both directions. The monitor detects the signal normally after switching.

Scenario 2: Windows 11 Pro + Hackintosh(macOS 26.6)
When Machine B (Windows 11 Pro) and Machine A (Hackintosh/macOS 26.6) are connected through the same TESmart KVM, display switching fails when switching to the Hackintosh. The monitor reports "No Signal" or "Signal Lost".

Troubleshooting Performed
Added the monitor's EDID information in OpenCore using DeviceProperties.
Attached my current config.plist for review.

 

[Danish297]

Mapping USB Ports is always a bit of trial and error and it can get frustrating but asking me to do it for you remotely, without direct access to your machine, raises the level of difficulty to a point I won't commit to. I see you added SSDT-UIAC.aml to your ACPI files, you do not want that enabled for what you are trying to do.
I uploaded your EFI with that and your USBPorts.kext disabled and the XHCIPortLimit Quirk enabled. It should boot and could enable all your USB ports for a temporary solution. It's possible none of your USB Ports will work though as well so make sure you are booting from a USB drive.

The last alternative would be install Sequoia so you can use USBToolbox to map your ports. You can add an APFS volume to the same drive as Tahoe and not hurt anything and its easy to delete later if desired. It give you a better chance at getting Bluetooth working if that is even possible with your Qulacomm card.

thanx, let me try this

 

[Danish297]

Mapping USB Ports is always a bit of trial and error and it can get frustrating but asking me to do it for you remotely, without direct access to your machine, raises the level of difficulty to a point I won't commit to. I see you added SSDT-UIAC.aml to your ACPI files, you do not want that enabled for what you are trying to do.
I uploaded your EFI with that and your USBPorts.kext disabled and the XHCIPortLimit Quirk enabled. It should boot and could enable all your USB ports for a temporary solution. It's possible none of your USB Ports will work though as well so make sure you are booting from a USB drive.

The last alternative would be install Sequoia so you can use USBToolbox to map your ports. You can add an APFS volume to the same drive as Tahoe and not hurt anything and its easy to delete later if desired. It give you a better chance at getting Bluetooth working if that is even possible with your Qulacomm card.

Thanks. Could you please check whether the attached USB mapping and full EFI configuration is correct now?

 

[leesurone]

Thanks. Could you please check whether the attached USB mapping and full EFI configuration is correct now?

Your USB Port mapping looks good, I can't really say if its right or not. As I mentioned before the tests I use is to determine if my mapping is working check if sleep/ wake behavior works as expected (no freezes, no reboot instead of shut down, system powers up and goes back to sleep consistently). Working Bluetooth is another test but may not be possible with your card.
The other issue with Bluetooth in your EFI is you seemed to have dropped IntelBluetoothFirmware.kext from your config.plist as well as the two lines II mentioned in an earlier post in your NVRAM/add section.

 

[Danish297]

Your USB Port mapping looks good, I can't really say if its right or not. As I mentioned before the tests I use is to determine if my mapping is working check if sleep/ wake behavior works as expected (no freezes, no reboot instead of shut down, system powers up and goes back to sleep consistently). Working Bluetooth is another test but may not be possible with your card.
The other issue with Bluetooth in your EFI is you seemed to have dropped IntelBluetoothFirmware.kext from your config.plist as well as the two lines II mentioned in an earlier post in your NVRAM/add section.

@leesurone @Edhawk @Shaneee @fabiosun @CaseySJ @AudioGod

need your help troubleshooting a display wake issue with my Hackintosh when using a TESmart DKS402-M24-USBK KVM switch.

Current Setup​

• Display switching works correctly through the KVM when both PCs are powered on.
• Display switching also works correctly when only one machine is running, so the KVM itself appears to be functioning properly.
• while connected through the KVM If I manually turn the monitor OFF and then ON, the display comes back without any issues.

Issue​

• When my Hackintosh goes to sleep and then wakes up while connected through the KVM, the display does not return automatically. I have to power the KVM OFF and ON to restore the display.
• If I connect the Hackintosh directly to the monitor (without the KVM), sleep and wake work normally, and the display comes back as expected.

Recent Changes​

My motherboard does not support Bluetooth, so I removed the Bluetooth-related kexts and the corresponding entries from config.plist

I've attached my updated EFI. Could you please review it and help with the following?

1. Is there any way to get the onboard Wi-Fi working, even if Bluetooth is not supported?
2. Are there any optimizations or corrections you would recommend for my config.plist or overall EFI configuration?
3. Has you encounter a similar KVM-related wake issue, and if so, how did it resolve?

Any suggestions would be greatly appreciated. Thank you!