Trackpad is not being recognized. Why?

[David Tirddea]

Hey folks! I know it's late but I am struggling for more than 2 weeks. My notebook: (L340)

CPU: Intel i5 9300H

iGPU: UHD 630

dGPU: GTX 1650 (disabled in DSDT)

Trackpad: Synaptics SYNA2B52 (from what i've seen it is I2C but as well as SMBUS)

 

The thing is that the trackpad doesn't want to work. I mean, I think it worked but when I rebooted to Windows, it was gone. I am running the latest version of BIg Sur. I've used VoodooI2C + VoodooI2CSynaptics satelite kext (with modified info.plist thing, i dont know why but it is the only thing that worked for me).

I've also tried VoodooRMI + VoodooI2C but no success. VoodooRMI + VoodooSMBUS too. 

 

This trackpad needs GPI0 Pinning, but instead I could use a temporary solution (boot-arg: -vi2c-force-polling) which worked, making it dead after sleep. Now after I rebooted to Windows, it doesn't even get recognized in the System Preferences. What could be the issue and how / what info do you need more? I can attach a IOReg, maybe you can click below on it. Do you need the EFI too? 

 

From my point of view, IOReg shows that I2C Controllers are not injected or however it is called. It's like when there's no SMBUS Fix as example. 

 

I don't think I am ready for GPI0 Pinning at the moment but if that's what I need to do, then I'l go on that way.

I want to credit MadL0n for the DSDT Patches, in case it is needed. 

 

Files / More Info:

iOReg (with DSDT loaded) : David's MacBook Pro.ioreg

EFI (OpenCore 0.7.9) : https://drive.google.com/drive/folders/1GpILK_tFUNLfx0Zs_u6oZ--FF0SZlSqH?usp=sharing

Trackpad APIC ID: TPD0 (from what I've seen in the DSDT and in the IOReg when the trackpad worked)

 

I would appreciate any help from you guys.

Thank you!!

 

 

 

Edited February 20, 2022 by David Tirddea

[Baio77]

Test this efi in USB  ioreg if start

EFI.zip

Edited February 21, 2022 by Baio77

[David Tirddea]

32 minutes ago, Baio77 said:

Test this efi in USB  ioreg if start

EFI.zip 10.22 MB · 0 downloads

It's working. I can make it work on my own by replacing the DSDT with SSDT tables and including the SSDT-XOSI + patch in config. That's the only way I can make it work on my own. But, I still want to use the DSDT. Do you need an IOReg? Thank you.

[Baio77]

Guys I don't understand some of your requests, you tell me you want to use the DSDT and it would be fine to me, but it's the worst solution you can use. Using SSDT is the best solution ....... The EFI I passed to you is proven, I made it long ago, in case it needs to be adapted to your system. Ioreg is basic, but you have to run it by booting with my EFI

[MaLd0n]

 

 

3 hours ago, Baio77 said:

The EFI I passed to you is proven

proven what? a bunch ssdts inject things into dsdt? u can inject direct in principal table(dsdt) and much more. ssdt is a easy way(premade things) for one incomplete solution. 

[David Tirddea]

4 hours ago, Baio77 said:

Guys I don't understand some of your requests, you tell me you want to use the DSDT and it would be fine to me, but it's the worst solution you can use. Using SSDT is the best solution ....... The EFI I passed to you is proven, I made it long ago, in case it needs to be adapted to your system. Ioreg is basic, but you have to run it by booting with my EFI

hey. i understand u. but the main thing here is the trackpad. since loading the dsdt instead of the ssdts its more "naturally" i woould go on this way. i've tried making my own efi with ssdts, everything else left untouched as today. it is more stable and safer to load the ssdts instead of loading a dsdt which may cause kp and many things but this dsdt is stable from what i've seen. I ve tried voodooRMI but no luck too. I dont know what to do anymore

[MaLd0n]

44 minutes ago, David Tirddea said:

hey.

Have some things for check.

 

1- Rename RDSM to _DSM into trackpad device TPD0. Many trackpad devices need OEM _DSM method

in folder above posted by Baio have only two things about ur trackpad

 

2- bootarg -vi2c-force-polling

 

3- ssdt gpi0

Quote

Scope (\)
    {
        If (_OSI ("Darwin"))
        {
            GPEN = One
        }

}

 

[David Tirddea]

23 hours ago, MaLd0n said:

1- Rename RDSM to _DSM into trackpad device TPD0. Many trackpad devices need OEM _DSM method

I renamed from RDSM to _DSM, into the TPD0 entry. Not working still. Don't know why. 

 

23 hours ago, MaLd0n said:

2- bootarg -vi2c-force-polling

I had it already but no changes at all.

 

23 hours ago, MaLd0n said:

3- ssdt gpi0

I did download the premade ssdt from Dortania since it gives me a error when I try to compile the code you gave me, in MaciASL. The code is the same as yours, so I don't think there's a problem. No changes at all too. 

 

Also I tried to modify the kext order in all ways possible. It used to work with the following:

VoodooI2CServices

VoodooGPI0

VoodooI2C

VoodooInput

VoodooI2CSynaptics..

 

I don't know what I did which caused to make it dead but as I said, I just booted to windows and then boom. 

It still happened a lot of times but I don't know why anymore. I've tried with VoodooRMI and also with VoodooSMBUS, no results.

 

 

IOReg (loaded with current EFI) : David's MacBook Pro.ioreg

EFI (with modified DSDT + VoodooI2C and satelite kext + SSDT-GPI0.aml): https://drive.google.com/drive/folders/1_MeZ1VZhso7PN9gSUlh9kpUsNfY2ZedF?usp=sharing

Edited February 22, 2022 by David Tirddea

[MaLd0n]

use this efi folder.  EFI 01.zip

reboot and post one Full Dump

https://www.olarila.com/topic/10301-olarila-runme-dumper/
https://olarila.com/files/Utils/RunMe.app.zip
https://youtu.be/DH5vRhE1P7U

and one Ioreg
https://olarila.com/files/Utils/IORegistryExplorer.app.zip

[Baio77]

 

 

Here is the DSDT of Mald0n breaks I2C0 and I2C1, you can see it from Ioreg, below the ioreg of the EFI I posted to you, performed by the user to whom I made the EFI.

 

[David Tirddea]

36 minutes ago, Baio77 said:

 

 

Here is the DSDT of Mald0n breaks I2C0 and I2C1, you can see it from Ioreg, below the ioreg of the EFI I posted to you, performed by the user to whom I made the EFI.

 

That's what I literally said above. It is not being injected or whatever. If I am attaching the XOSI SSDT and patch, it works as yours. But breaks after sleep which is not a big problem but, since Mald0n recommends to not use any sort of renames, then I'll be fine with the DSDT itself. 

 

37 minutes ago, Baio77 said:

Here is the DSDT of Mald0n breaks I2C0 and I2C1, you can see it from Ioreg, below the ioreg of the EFI I posted to you, performed by the user to whom I made the EFI.

I still don't know why both of them are off while running without XOSI patch. That's the only thing I wanna know. 

Thank you.

[MaLd0n]

45 minutes ago, David Tirddea said:

That's what I literally said above.

extract one sendme with my efi folder above and ill patch for u with no trackpad fix

SYNA devices with voodooi2c don't work after sleep with last version

if u use telegram add me there for fast trade files

Telegram: https://t.me/MaLd0n

[David Tirddea]

3 hours ago, MaLd0n said:

extract one sendme with my efi folder above and ill patch for u with no trackpad fix

Here you go: https://drive.google.com/file/d/15akySYuNN3amRP-Irv2vSp1OzY7wCLGN/view?usp=sharing

IOReg since RunMe failed to make it, don't know why: David's MacBook Pro a.ioreg

 

Also, can I know what are you doing? I am trying to understand the process if I don't bother. Thank you.

 

3 hours ago, MaLd0n said:

SYNA devices with voodooi2c don't work after sleep with last version

I found out there's a kext which enables and disables synaptics trackpads via prtsc key, I don't know if it's stable at the moment. Anyway, thank you again.

Edited February 23, 2022 by David Tirddea

[Avery B]

If it's Synaptics I2C, you could try using VoodooRMI as a drop in replacement for VoodooI2CSynaptics. It implements a few other functions for newer trackpads, plus should have sleep fixed.

[David Tirddea]

2 hours ago, 1Revenger1 said:

If it's Synaptics I2C, you could try using VoodooRMI as a drop in replacement for VoodooI2CSynaptics. It implements a few other functions for newer trackpads, plus should have sleep fixed.

I already mentioned that VoodooRMI doesn't work, samething to VoodooI2C.

Firstly, I tried to disable SMBUS from DSDT which I can't say I did it corectly. I don't know what I did, but I deleted some code related to SBUS, according of the VoodooSMBUS guide.

Tried adding some manuals values, no luck. It is dead like I2C. 

 

Also, forgot to tell that this trackpad has I2C and SMBUS support too. As I searched on Windows, it has Synaptics SMBUS Device in Device Manager. I really don't know what to do now

Edited February 23, 2022 by David Tirddea

[makk]

Well darn two schools of thought here. One being DSDT solves many problems and the other being SSDT hotpatches.

 

DSDT is absolutely the best solution in the short and long run due to the many details and intricacies ( as in SSDT's don't list every thing incomplete)

SSDT's work in the short term for testing. patch work.  well Hacky is patchwork to begin with. So the idea that SSDT's to use for patching then gets extensive with many SSDT's in the ACPI folder. Hey here try this one!  Just pop it in! Wella it don't work! Why? DSDT says no go.

 

DSDT is like the summary compendium, while SSDT 's are the footnotes.

I have SSDT hotpatch system which uses System DSDT but this does not solve all the issues it leaves gaps and holes.

 

The reality of Apple's constant upgrades makes SSDT's look very sweet and delicious but in the long term it is best to keep

a DSDT.dsl, several, one that is the Original and two is the Messes, the Three is the good one, then you can make more as you need.

This is how I was originally doing it until I realized these constant upgrades and updates to OS from Sierra to Monterey, with progressive massive changes internally. So what was good for Sierra is not 100% good for Monterey Bay Disco, Catalina Choo Choo, Big Surgeon, Mojave Desert, 

 

DSDT patching can be a pain in the arse.  Which is why I choose SSDT's until I get the full-blown Mac that I can eat Angus burger with.

 

 

Make a DSDT and that will help a great deal.