Contribute
Register

Thinkpad E540 Mojave 10.14 (update)

Status
Not open for further replies.
@eXoliner Here are the files for testing.
Use the attached config.plist & Patched Folder.
Reboot, test what is and what is not working

Install also Intelgraphicsfixup.kext -https://sourceforge.net/projects/intelgraphicsfixup/
Lilu.kext - https://github.com/vit9696/Lilu/releases
shiki.kext -https://github.com/vit9696/Shiki/releases

Create a folder on desktop with name IGPU and place shiki.kext, lilu.kext, intelgraphicsfixup.kext on that folder.

Open terminal:
Code:
cd desktop/IGPU
sudo cp -R *.kext /Library/Extensions/
then rebuild caches with:
Code:
sudo kextcache -i /

Reboot !

Open IOregistryExplorer

Grab a USB 2.0 Device (mouse/keyboard/2.0usb flash drive or whatever usb2 device).
Plug it on first usb port, hold it for 3 sec, eject, then plug it on the other port, repeat until you do this on all usb ports that your laptop has.

After you finnish.

Grab a USB 3.0 device (external HDD/USB3.0 Flash Drive or whatever usb3 device).
Do the same like above.

After you finish, Save a copy of IOREG and upload it here so i can create usb port injector to fix usb ports.

Installed Patch, config and kexts:
Battery status working
built-in display working
usb does not work
Added IOREG, after plugging in usb2.0 and usb3.0 device at each port.
twice warning: USB device needs power source.
THX.
 

Attachments

  • Thinkpad ioreg.ioreg
    7.2 MB · Views: 131
Installed Patch, config and kexts:
Battery status working
built-in display working
usb does not work
Added IOREG, after plugging in usb2.0 and usb3.0 device at each port.
twice warning: USB device needs power source.
THX.
Ok thats great,
For some reasons the usb port limit patch didn't work and you didn't include complete problem reporting files...

add this SSDT-USB into EFI/Clover/ACPI/Patched.
I left the used HSxx port and removed the unused ones, now we have to check which SSPx Ports do the USB3.0 Ports use.
Reboot, then do the capture again so i can see which Ports does 3.0 use.

Warning is expected until we create the complete USB Injector.
 

Attachments

  • SSDT-USB.aml
    582 bytes · Views: 151
Ok thats great,
For some reasons the usb port limit patch didn't work and you didn't include complete problem reporting files...

add this SSDT-USB into EFI/Clover/ACPI/Patched.
I left the used HSxx port and removed the unused ones, now we have to check which SSPx Ports do the USB3.0 Ports use.
Reboot, then do the capture again so i can see which Ports does 3.0 use.

Warning is expected until we create the complete USB Injector.
Uploaded new version of problem reporting files. which files are missing?
SSDT-USB installed.

repeated same procedure on USB ports.
Added new Ioreg.
USB is working, after deinstallation of USBInjectAll.kext
THX.
 

Attachments

  • Problem Reporting eXoliner.zip
    1.6 MB · Views: 70
  • exoliner ioreg.ioreg
    7.2 MB · Views: 114
Last edited:
I am struggling with your ACPI Debug, I applied Patch (debug.txt) and installed .kext as described in ReadMe: https://github.com/RehabMan/OS-X-ACPI-Debug.
I do not understand the third: "Third, add code to your DSDT to where you wish to cause trace messages to system.log (call \RMDT.PUSH)."
I do not understand
"- apply "Add DSDT Debug Methods"
- apply "Instrument EC Queries"" from the Brightness Control Guide, where Mapping Brightness Keys is described.
https://www.tonymacx86.com/threads/guide-patching-dsdt-ssdt-for-laptop-backlight-control.152659/

Thanks
 
I am struggling with your ACPI Debug, I applied Patch (debug.txt) and installed .kext as described in ReadMe: https://github.com/RehabMan/OS-X-ACPI-Debug.
I do not understand the third: "Third, add code to your DSDT to where you wish to cause trace messages to system.log (call \RMDT.PUSH)."
I do not understand
"- apply "Add DSDT Debug Methods"
- apply "Instrument EC Queries"" from the Brightness Control Guide, where Mapping Brightness Keys is described.
https://www.tonymacx86.com/threads/guide-patching-dsdt-ssdt-for-laptop-backlight-control.152659/

Thanks

You will see those patches if you add the ACPIDebug MaciASL repo to MaciASL->Preferences->Sources.
 
You will see those patches if you add the ACPIDebug MaciASL repo to MaciASL->Preferences->Sources.
Had to update Maciasl, did not showed any repo Patches in current version. Installed Patches.
Applied OS Check Fix.
After reboot, System Log does not show up any EC Query Codes, or anything referring to the Keys.
But consoles output for one key: Systemsoundserverd
"687: -> Incoming Request : actionID 4096, inClientPID 513(Console), inBehavior 1, customVibeDataProvided 0, loop 0, loopPeriod 0.000000, inFlags 0, inClientCompletionToken 144"

Added Patched DSDT and new Problem Report Files.
thx.
 

Attachments

  • DSDT.aml
    68.6 KB · Views: 126
  • debug_18023.zip
    1.7 MB · Views: 84
Had to update Maciasl, did not showed any repo Patches in current version. Installed Patches.
Applied OS Check Fix.
After reboot, System Log does not show up any EC Query Codes, or anything referring to the Keys.
But consoles output for one key: Systemsoundserverd
"687: -> Incoming Request : actionID 4096, inClientPID 513(Console), inBehavior 1, customVibeDataProvided 0, loop 0, loopPeriod 0.000000, inFlags 0, inClientCompletionToken 144"

Added Patched DSDT and new Problem Report Files.
thx.

You're renaming various _Qxx methods via config.plist and replacing them in SSDT-KBD.aml.
 
You're renaming various _Qxx methods via config.plist and replacing them in SSDT-KBD.aml.
I know, but system log does not show up any methods, used by Brightness keys.
But I installed, ACPI Debug Kext and referring DSDT Patches as well.
Only thing showing up is systemsoundreserved but in console output.
thx.
 
Status
Not open for further replies.
Back
Top