- Joined
- Mar 29, 2019
- Messages
- 226
- Motherboard
- Zbook G4 17
- CPU
- i7-7820HQ
- Graphics
- HD630+WX4150
- Mac
- Classic Mac
- Mobile Phone
Hi everyone!
The latest build is on the link:
Github repositories
As it easier to synchronize with desktop and modifications
The entire thread is for research posts and discussion
Follow the manual to make all things working correct.
Please report of any glitches or problems of build!
=== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====
Hi everyone!
Zbook G3\G4 doesn't have an option like G5 have to force power thunderbolt device. So every time if you want to use Thunderbolt or USB-C device - you need to plug-in it before the boot. The tool that can change that is TbtForcePower.efi, but it is good for basic needs, but it doesn't have sleep\wake functionality.
After deeper research of DSDT i have found this:
And first tests were perfect, except one thing: when the device is disconnected, something at dsdt will powerOFF thunderbolt again. But that is great, that this way gives more stability. So to find notification that is disabling device could be a bingo to connect notification to enable power Event.
The project results are not stable enough for day-by-day usage. But can help push even further results.
=== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====
SSDT-TB3HP.aml Is for proper naming of Thunderbolt
SSDT-TBMacOSDebug/SSDT-TBWindowsDebug are test builds
TbtForcePower.efi - is efi that injects Thunderbolt Power but doesn't take care of sleep and wake
The latest build is on the link:
Github repositories
As it easier to synchronize with desktop and modifications
The entire thread is for research posts and discussion
Follow the manual to make all things working correct.
Please report of any glitches or problems of build!
=== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====
THE OLD POST =>
=== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====Hi everyone!
Zbook G3\G4 doesn't have an option like G5 have to force power thunderbolt device. So every time if you want to use Thunderbolt or USB-C device - you need to plug-in it before the boot. The tool that can change that is TbtForcePower.efi, but it is good for basic needs, but it doesn't have sleep\wake functionality.
After deeper research of DSDT i have found this:
This method injects Arg2, Arg3 to SGOV, which is basicaly PCH GPIO. After query of CGWR arguments:Code:Method (CGWR, 4, Serialized) { If (LEqual (Arg0, Zero)) { If (CondRefOf (\_SB.SGOV)) { SGOV (Arg2, Arg3) } } ElseIf (LEqual (Arg0, One)) { If (CondRefOf (\_SB.PCI0.GEXP.SGEP)) { ^PCI0.GEXP.SGEP (Arg1, Arg2, Arg3) } } }
So that was clear that injecting 0x01060010 and 0x1 to SGOV will enable power to thunderbolt. So that can be used to build ACPI method which will PowerOn thunderbolt on Boot, PowerOff on sleep and back online on wake.CGWR (FPAT, FPEN, FPGN, FPLV)
FPAT x4 = 00000000 = ARG0
FPEN x4 = 00000004 = ARG1
FPGN x4 = 01060010 = ARG2 (GPIO ADDRESS)
FPLV x4 = 00000001 = ARG3 (GPIO STATE)
And first tests were perfect, except one thing: when the device is disconnected, something at dsdt will powerOFF thunderbolt again. But that is great, that this way gives more stability. So to find notification that is disabling device could be a bingo to connect notification to enable power Event.
The project results are not stable enough for day-by-day usage. But can help push even further results.
=== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====
THE OUTDATED ATTACHMENTS =>
=== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ====SSDT-TB3HP.aml Is for proper naming of Thunderbolt
SSDT-TBMacOSDebug/SSDT-TBWindowsDebug are test builds
TbtForcePower.efi - is efi that injects Thunderbolt Power but doesn't take care of sleep and wake
Attachments
Last edited: