Opencore-Legacy-Patcher VS barrier

At a guess I would say probably using OCLP - https://github.com/dortania/OpenCore-Legacy-Patcher - lots of life left in old Mac’s using that tool !

I had this issue, too. But luckily, I've got a solution. First, you'll need to check your MacOS Sonoma version. If you're using 14.1 beta, this method will NOT work. In such cases, I recommend installing the official 14.0. Thankfully, this commit (https://github.com/dortania/OpenCore-Legacy-Patcher/commit/1aee2e5dfa12d10e218a51e4151ac2e96705ae9e) solved the problem! However, the latest OCLP 1.0.1 still doesn't have it. To use it, you can build OCLP from code or use the OCLP Nightly link found here. After you find the nightly link and download OCLP, build it onto your MBP, and after rebooting, install the patches. If you look carefully, you'll see that 'experimental T1 Patches' will be available in the list of post-installation patches.

From what I've assessed reading other posts, Monterey (Ventura has USB & stability issues) with OCLP 0.6.7 is the most stable install for this device (have not yet seen any reports using OCLP 1.0+, although happy to see some new non-Metal fixes going in). This is a bit of a bummer, as Monterey will not likely receive updates past end of 2024 (next year).

I'm not taking a position on OCLP being trustworthy or not, but at least the project appears to be 100% open source [0], which is more than we can say about Apple.

[0] https://github.com/dortania/OpenCore-Legacy-Patcher

Have you explored https://github.com/dortania/OpenCore-Legacy-Patcher?

I have used it before and, in my experience and everyone else I know who has used it, the vast majority of time the newer versions run absolutely fine with no issues. Occasionally some newer features don't work, but I'd but confident that 2015/2017 iMacs would be able to run the latest version no problem.

Link to pull request to track OLCP Sonoma support state, you can also read more info there: https://github.com/dortania/OpenCore-Legacy-Patcher/pull/1077

For software KVM you can use https://github.com/debauchee/barrier

I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)

libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?

For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through

And for host systems, it looks like xev only logs input events when the window is focused.

Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?

With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.

Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier

libei:

I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.

Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...

Barrier appears to handle PC switching only for the keyboard and mouse.

Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.

Barrier is a free and open source alternative.