Olarila HackBook Lenovo IdeaPad S145 8th Gen Full DSDT Patches / OpenCore

[user748832]

[ref]user748832[/ref], use VoodooI2C.kext and VoodooI2CHID.kext and extract one send_me

--Run_Me

RunMe.app

https://www.youtube.com/watch?v=k9wmIfGLe3A

 

Here is the attachment.. Thanks.

Send me MacBookldiMarco.station.zip

[MaLd0n]

[ref]user748832[/ref], ur table have a sbfg and sbfb, try a returnt in crs to sbfg and sbfb

[user748832]

[ref]user748832[/ref], ur table have a sbfg and sbfb, try a returnt in crs to sbfg and sbfb

 

Assuming TPD0 is the device I have to look at, this is my initial _CRS method:

 

Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
           {
               If ((OSYS < 0x07DC))
               {
                   Return (SBFI) /* \_SB_.PCI0.I2C0.TPD0.SBFI */
               }

               Return (ConcatenateResTemplate (SBFB, SBFI))
           }

 

The GPIO pinning guide is a bit unclear at final step 2e, where it states:

------------------

Step 2e: Ensuring your DSDT notifies the system that your device is GPIO pinned

Finally, make sure that there are no other Return statements in your _CRS method apart from the following at the end:

 

Return (ConcatenateResTemplate (SBFB, SBFG))

------------------

So, I did a couple of tests (both unsuccessfull):

Test 1: just touch the final Return statement

 

Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
           {
               If ((OSYS < 0x07DC))
               {
                   Return (SBFI) /* \_SB_.PCI0.I2C0.TPD0.SBFI */
               }

               Return (ConcatenateResTemplate (SBFB, SBFG))
           }

 

Test 2: also, remove the IF which contain another Return statement

 

Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
           {
               Return (ConcatenateResTemplate (SBFB, SBFG))
           }

 

Can I try something else?

ref: https://voodooi2c.github.io/#GPIO%20Pinning/GPIO%20Pinning

EDIT - As for the GPIO Pin, I first tried to leave this as is (assuming it is well-pinned)

 

Name (SBFG, ResourceTemplate ()
           {
               GpioInt (Level, ActiveLow, ExclusiveAndWake, PullDefault, 0x0000,
                   "\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, ,
                   )
                   {   // Pin list
                       0x0000
                   }
           })

 

Then, I replaced 0x0000 with 0x6e and 0x42, no luck. (calculated as per above guide)

[onemanosx]

Then, I replaced 0x0000 with 0x6e and 0x42, no luck. (calculated as per above guide)

You are to refer to CannonPointLP IRQ table

In normal circumstance, a native GPI0pin requires no modification.

Your Elan device most likely will work with a different satellite i.e VoodooI2CELAN

[user748832]

VoodooI2CELAN

 

Are you saying that the GPIO pinning guide is incorrect? I see that "hexadecimal APIC pin number" = 0x6e which is NOT less than 0x2F

So I had to follow all the other steps before installing the I2C kext files in CLOVER/Kexts/Other

And yes I used the CannonPointLP IRQ tables to calculate the new PIN (0x42, 0x6e)

And yes I used the VoodooI2CELAN kext (after tried with VoodooI2CHID kext)

My Touchpad is still not working

[onemanosx]

And yes I used the CannonPointLP IRQ tables to calculate the new PIN (0x42, 0x6e)

The decimals are 82 and 53 for hexadecimal 0x6e thereby giving pins of 0x52 and 0x35 respectively.

[user748832]

The decimals are 82 and 53 for hexadecimal 0x6e thereby giving pins of 0x52 and 0x35 respectively.

 

Just to clarify: I didn't test pin numbers 82 and 53 (0x52 and 0x35) because of this sentence in the Guide:

 

On newer chipsets (Cannon Point and newer), there is a mismatch between the GPIO pin and the hardware pin number. If you are using such hardware, you will need to convert the hardware pin number you have found to a GPIO pin, to allow the driver to use the pin

 

So, by following the same Guide, I did the conversion as follows:

82 - 68 + 96 = 110 = 0x6e

53 - 51 + 64 = 66 = 0x42

Anyway, as you suggested, I have just tried those pin numbers without any conversion (0x52 and 0x35) with same results.

One observation: I noticed that, without GPIO Pin Change, I see this for TPD0

While, after pin change the device has a different content (IOInterruptSpecifiers is gone!)

Maybe the kext file are still not supporting this ELAN device?

[kuarahy@icloud.com]

Hi ,

I've got the same machine, mine is an i7 though.

Is there a problem if the graphic doesn't match , I mean, yours is Iris Plus Graphics 655, mine is UHD 620

Regards

[MaLd0n]

[ref]kuarahy@icloud.com[/ref], same patch work, use my full efi and check if work

[onemanosx]

So, by following the same Guide, I did the conversion as follows:

82 - 68 + 96 = 110 = 0x6e

53 - 51 + 64 = 66 = 0x42

You are referencing to the wrong table

Can you reboot with this DSDT and upload new sendme files at I2C thread?

 

DSDT.aml.zip

[kuarahy@icloud.com]

[ref]kuarahy@icloud.com[/ref], same patch work, use my full efi and check if work

Hi, almost everything worked.

It throws an error with my nvme secondary drive.

Attached the IOreg file and the screenshot of the nvme error

I would really appreciate it if you could have a look at it.

Thanks

Archive.zip

[user748832]

You are referencing to the wrong table

Can you reboot with this DSDT and upload new sendme files at I2C thread?

DSDT.aml.zip

 

@onemanosx. Uploading here new sendme file, using your DSDT.aml + I2C/I2CELAN kexts

( Not sure where is I2C thread? )

Thank you!

Send me MacBookldiMarco.station.zip

[onemanosx]

[ref]user748832[/ref], Your I2C device is fully loaded. Remove VoodooI2CHID kext. Only use VoodooI2C and VoodooI2CELAN kexts.

If you had installed any 3rd party kexts in S/L/E (or L/E), this is a good time to remove them from the folder and only use Clover/Kexts/Other

Remove VoodooI2CHID, rebuild kextcache and reboot.

https://imgur.com/HJ6Qj9o

 

Not sure where is I2C thread?

https://Olarila.com/forum/viewtopic.php?f=46&t=8087

[user748832]

[ref]user748832[/ref], Your I2C device is fully loaded. Remove VoodooI2CHID kext. Only use VoodooI2C and VoodooI2CELAN kexts.

If you had installed any 3rd party kexts in S/L/E (or L/E), this is a good time to remove them from the folder and only use Clover/Kexts/Other

Remove VoodooI2CHID, rebuild kextcache and reboot.

https://imgur.com/HJ6Qj9o

 

https://Olarila.com/forum/viewtopic.php?f=46&t=8087

 

Heeeelp! I have big problems by using your DSDT:

- First, with VoodooI2CELAN TouchPad still not working

- Second, with VoodooI2CHID.. for the first time the TouchPad is responding but pointer movement is strange (pointer will continue to move after the touch)

- Third, CPU1 is almost 100%, the Power LED is flashing like when Laptop is in sleep. I have turned OFF, then turn ON, Power LED still flashing!!! How can I reset the Laptop? I think something has been corrupted in the BIOS

[onemanosx]

Second, with VoodooI2CHID.. for the first time the TouchPad is responding but pointer movement is strange (pointer will continue to move after the touch)

If this is the case, edit DSDT to polling mode instead of interrupt mode. You can continue to use VoodooI2CHID. You can also experiment with other pins in interrupt mode.

The high CPU usage might come from using interrupt mode in I2C.

[MaLd0n]

[ref]kuarahy@icloud.com[/ref], extract send_me

--Run_Me

RunMe.app

[kuarahy@icloud.com]

[ref]MaLd0n[/ref],

[ref]kuarahy@icloud.com[/ref], extract send_me

--Run_Me

RunMe.app

Thank you for your help

Here is the requested file.

Send me MacBook-Pro.zip

[MaLd0n]

[ref]kuarahy@icloud.com[/ref], ur model is very diff, have a dgpu etc, first try drop my dsdt and check if nvme load

https://Olarila.com/forum/viewtopic.php?f=28&t=9303

[kuarahy@icloud.com]

[ref]kuarahy@icloud.com[/ref], ur model is very diff, have a dgpu etc, first try drop my dsdt and check if nvme load

https://Olarila.com/forum/viewtopic.php?f=28&t=9303

[ref]MaLd0n[/ref],

Dropping your DSDT didn't even boot. Anyway, with your patch almost everything works. So I am happy with it.

The second nvme drive is for windows, so right now is not a priority. I'm using a ssd sata for Mojave, I wanted to use the pci ssd instead.

Thanks

[MaLd0n]

[ref]kuarahy@icloud.com[/ref], Use it for disable nvidia

DSDT.aml.zip