Contribute
Register

Lenovo s340 Keyboard working, touchpad not

Status
Not open for further replies.
Joined
Sep 18, 2019
Messages
7
Motherboard
MSI
CPU
Intel I-5-7500
Graphics
Radeon rx-580 8 gig
Laptop: Lenovo s340 14 inch
I-5 8265u
8 gig DDR4
256 gig SSD (running exclusively macOS)
Intel UHD 620 (this is also not working, 7mb of VRAM showing up in 'about this Mac'. Currently using RehabMan's UHD 630 plist as there's no UHD 620, any help about this problem would be much appreciated)


Hey everyone, I did my first hack a couple years ago and so I decided to try it again on my new Lenovo s340. I got Mojave up and running after a bit of hassle, and now I'm trying to fix the trackpad not being detected by the system while the keyboard is. I've tried VoodooPS2, I've tried ApplePS2SmartTouchPad, and I've tried the i2 patch as well. VoodooPS2 and i2 both enabled the keyboard, and smart touchpad didn't work with any of the hardware.

I don't know what other solutions there are so I'm writing here. I don't see why this touchpad wouldn't be compatible. I feel like this is just out of my reach and I can't quite see the solution.

Thanks
 
Hello. I have a same one. I recommend you follow the guide which I link below.
 
You should modify device(TPAD), not device(TPD0) in dsdt.
Don’t use appleps2smarttouchpad kext. Because it is not compatible for this laptop. You can use voodoops2 and voodooi2c kext.
 
Hello. I have a same one. I recommend you follow the guide which I link below.
I did follow the guide but I still am having these issues. I’ll go back and review the instructions for the graphics and the touchpad tonight

Also, I could get the graphics to load with rehab’s hd_615_620_630 or something along those lines plist file, only problem was the brightness got turned all the way down and I can’t adjust it
 
You should modify device(TPAD), not device(TPD0) in dsdt.
Don’t use appleps2smarttouchpad kext. Because it is not compatible for this laptop. You can use voodoops2 and voodooi2c kext.
Please tell me why I can not boot after changing the TPAD. If possible,
can give a EFI folder to start the system. Thank you I apologize for my English
 
Last edited:
I think, your original pin list in name (SBFG) is 0x0038. This cause booting error or delay.
If you change this 0x0055, you can solve boot issue.

Scope (_SB.PCI0.I2C0)
{
Device (TPAD)
{
Name (_ADR, One) // _ADR: Address
Name (_UID, One) // _UID: Unique ID
Name (_S0W, 0x03) // _S0W: S0 Device Wake State
Name (HID2, Zero)
Name (TPID, Package (0x02)
{
Package (0x05)
{
0x04,
0x2C,
0x20,
"MSFT0001",
"PNP0C50"
},

Package (0x05)
{
0x08,
0x15,
One,
"MSFT0001",
"PNP0C50"
}
})
Name (SBFB, ResourceTemplate ()
{
I2cSerialBusV2 (0x0000, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "\\_SB.PCI0.I2C0",
0x00, ResourceConsumer, _Y43, Exclusive,
)
})
Name (SBFI, ResourceTemplate ()
{
Interrupt (ResourceConsumer, Level, ActiveLow, ExclusiveAndWake, ,, )
{
0x00000050,
}
})
Name (SBFG, ResourceTemplate ()
{
GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x0000,
"\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0038 ---------> change this value to 0x0055
}
})
 

Thanks you !
 
I think, your original pin list in name (SBFG) is 0x0038. This cause booting error or delay.
If you change this 0x0055, you can solve boot issue.

Scope (_SB.PCI0.I2C0)
{
Device (TPAD)
{
Name (_ADR, One) // _ADR: Address
Name (_UID, One) // _UID: Unique ID
Name (_S0W, 0x03) // _S0W: S0 Device Wake State
Name (HID2, Zero)
Name (TPID, Package (0x02)
{
Package (0x05)
{
0x04,
0x2C,
0x20,
"MSFT0001",
"PNP0C50"
},

Package (0x05)
{
0x08,
0x15,
One,
"MSFT0001",
"PNP0C50"
}
})
Name (SBFB, ResourceTemplate ()
{
I2cSerialBusV2 (0x0000, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "\\_SB.PCI0.I2C0",
0x00, ResourceConsumer, _Y43, Exclusive,
)
})
Name (SBFI, ResourceTemplate ()
{
Interrupt (ResourceConsumer, Level, ActiveLow, ExclusiveAndWake, ,, )
{
0x00000050,
}
})
Name (SBFG, ResourceTemplate ()
{
GpioInt (Level, ActiveLow, Exclusive, PullUp, 0x0000,
"\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0038 ---------> change this value to 0x0055
}
})


It still writes an error. you do not share your DSDT.aml?
 

Attachments

  • photo_2019-09-22_18-29-30.jpg
    photo_2019-09-22_18-29-30.jpg
    126.1 KB · Views: 285
It still writes an error. you do not share your DSDT.aml?
I share you my dsdt and config.
I think there are not causing any issue, in my experience.
Good luck!
 

Attachments

  • s340-14iwl.zip
    62.6 KB · Views: 346
Last edited:
Status
Not open for further replies.
Back
Top