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.

 

[Edhawk]

How are the three systems connected to the KVM, DisplayPort, HDMI or other display connector/cable?

Which KVM switch are you using?

 

[Danish297]

How are the three systems connected to the KVM, DisplayPort, HDMI or other display connector/cable?

Which KVM switch are you using?

I have two system (machine A and machine B) connected through DisplayPort.
I'm using TESmart DKS402-M24-USBK

 

[leesurone]

I have two system (machine A and machine B) connected through DisplayPort.
I'm using TESmart DKS402-M24-USBK

Wow, that is one expensive solution. I have dual inputs on my monitor, and use a Mac Master Logitech Keyboard and mouse to switch machines. They can support three different devices using Bluetooth or USB or a combination there of.

 

[Danish297]

Wow, that is one expensive solution. I have dual inputs on my monitor, and use a Mac Master Logitech Keyboard and mouse to switch machines. They can support three different devices using Bluetooth or USB or a combination there of.

great, unfortunately Bluetooth is not working for me :-( what should I change in my configuration to make it work flawless.

 

[leesurone]

great, unfortunately Bluetooth is not working for me :-( what should I change in my configuration to make it work flawless.

The first question is what WIFI/Bluetooth solution are you using? The second is how are you trying to enable it meaning best to zip and upload your EFI.

 

[Danish297]

The first question is what WIFI/Bluetooth solution are you using? The second is how are you trying to enable it meaning best to zip and upload your EFI.

@leesurone @Edhawk plz check my EFI attached, my mother board Gigabyte Z970 AORUS Master X has Qualcomm wifi-bluetooth what changes need to do to fix EDID to use my KVM.

 

[leesurone]

@leesurone @Edhawk plz check my EFI attached, my mother board Gigabyte Z970 AORUS Master X has Qualcomm wifi-bluetooth what changes need to do to fix EDID to use my KVM.

According to Gigabyte these are the typical WIFI/ Bluetooth cards your motherboard (if it is version 1.0) comes with. Sounds like you have the first one which is fine but none of them are compatible with macOS WIFI hardware limitations. I have never tried to activate Bluetooth using one of the listed modules, I believe it could be made to work but you lack the supporting kexts and config.plist entries in the NVRAM section. I'm not at my desk now but later I can upload what I use on my ASUS Z790 board that has working Bluetooth.

Qualcomm® Wi-Fi 7 QCNCM865 (PCB rev. 1.0)

• 802.11a, b, g, n, ac, ax, be, supporting 2.4/5/6 GHz carrier frequency bands
• BLUETOOTH 5.4
• Support for 11be 320MHz wireless standard

MediaTek Wi-Fi 7 MT7927, RZ738 (PCB rev. 1.1)

• 802.11a, b, g, n, ac, ax, be, supporting 2.4/5/6 GHz carrier frequency bands
• BLUETOOTH 5.4
• Support for 11be 320MHz wireless standard

Intel® Wi-Fi 7 BE200 (PCB rev. 1.2)

• 802.11a, b, g, n, ac, ax, be, supporting 2.4/5/6 GHz carrier frequency bands
• BLUETOOTH 5.4
• Support for 11be 320MHz wireless standard

(Actual data rate may vary depending on environment and equipment)

The other issue I see is that Bluetooth requires a proper USB Map and one that correctly identifies the port of the Bluetooth controller. Yours does not and frankly your USB mapping is borked. You have only one USB controller Identified, you probably have two or three, all ports are designated as USB3 and you are well above the 15 port limit macOS tolerates. Until you get that under control Bluetooth is not going to ever work, you are going to have to make a better effort at mapping your ports. This is what Gigabyte says you have on that board:

Chipset:
- 3 x USB Type-C® ports, with USB 3.2 Gen 2x2 support (2 ports on the back panel, 1 port available through the internal USB header)
Chipset+2 USB 3.2 Gen 2 Hubs:
These are typically identified as type 9, possibly 10 for both ports (two per)
- 1 x USB Type-C® port on the back panel, with USB 3.2 Gen 1 support
Same as above
- 7 x USB 3.2 Gen 2 Type-A ports (red) on the back panel
Chipset+2 USB 3.2 Gen 1 Hubs:
These are type 3 for both ports
- 8 x USB 3.2 Gen 1 ports (4 ports on the back panel, 4 ports available through the internal USB headers)
Chipset+USB 2.0 Hub:
Same as above
- 4 x USB 2.0/1.1 ports available through the internal USB headers
These are type 0 if you are using them

I don't think you need to fix your EDID but that is only an opinion. I've never had that be an issue to resolve except for a specific monitor that wouldn't cooperate otherwise. Personally I would use Whatevergreen.kext instead of NootRX. Search for version 1.71d7 that works with Tahoe
InsanelyMac Forum: The specific WhateverGreen 1.7.1d7.kext is one place to find it. Tonymacx86 does as well

 

[leesurone]

One last thing is I don't see the need to be using IOSkywalkFamily.kext and downgrading it in the Kernel Block section of your config.plist. Should not be needed in your configuration.

 

[Danish297]

One last thing is I don't see the need to be using IOSkywalkFamily.kext and downgrading it in the Kernel Block section of your config.plist. Should not be needed in your configuration.

let me try with below:
1. WhateverGreen 1.7.1d7.kext will remove NootRX
2. will remove IOSkywalkFamily.kext
3. remap USB (can I use Hackintool for this also do I need to remove KVM while re-mapping the USB ?)

 

[leesurone]

let me try with below:
1. WhateverGreen 1.7.1d7.kext will remove NootRX
2. will remove IOSkywalkFamily.kext
3. remap USB (can I use Hackintool for this also do I need to remove KVM while re-mapping the USB ?)

Make all those changes to a bootable USB Disk

1. Good
2. Don't forget uncheck the Kernel/ blocked section of your config.plist of IOSkywalkFamily.kext
3. You can try Hackintool, I would try with the XHCIPortLimit quirk enabled and see if that works, if not then without and no kind of port mapping enabled.