Changes to I2C protocols with Sonoma and Sequoia?

So, I've spent hours attempting to install Sequoia on my Surface Laptop 3, and it's proved to be near-impossible. Closest I got was by running in an external mouse, and while I know that's classic troubleshooting, I'd tried a host of kexts and workarounds to enable the trackpad in sonoma/sequoia. Not one of them worked. So eventually I did what I had done originally. Not wanting to mess around with any more conflicting distros of kexts that don't play nice with Surface, I went back to a random EFI on github that is over 2 years old at this point. I know pre-builts/others' work is frowned upon around here, but I actually do know quite a bit about the process. This was really just another troubleshooting step. (https://github.com/WhyToFly/SurfaceLaptop3-OpenCore)

Please help me understand why everything works flawlessly in here. Some of the other repos don't work with Ventura or Sequoia, even though they're supposed to. I'm just genuinely so confused as to why all this is. Also worth noting that this EFI does NOT boot with a recovery image of Sonoma in place. Was there a fundamental change in the way macos receives I2C info from the kexts? jlempen on github suggested downgrading the UEFI, which is fine except it's on the motherboard so there's no way to do that. None of the updates or latest releases did anything. Pretty baffled here. At this point I'm sticking with Ventura unless one of you guys has some info for how to upgrade safely, but I'm really just curious if anyone knows what the issue is here.

submitted by /u/LoquaciousFool
[link] [comments]