Contribute
Register

[Guide] Patching LAPTOP DSDT/SSDTs

Hello,
sorry for my language but I try to explain my Problem here, I installed Mojave on Dell Latitude E7440 and used this Guide to Patching DSDT, Now it stay one syntax error and I did not found any Forum, they speak about it.
so I hope to find help here :)
i will post screenshot from this error
 

Attachments

  • Bild 22.12.18 um 00.44.jpg
    Bild 22.12.18 um 00.44.jpg
    257.1 KB · Views: 142
Hello,
sorry for my language but I try to explain my Problem here, I installed Mojave on Dell Latitude E7440 and used this Guide to Patching DSDT, Now it stay one syntax error and I did not found any Forum, they speak about it.
so I hope to find help here :)
i will post screenshot from this error

You failed to attach the file that causes the error.
Also, attach full PR files as per FAQ.
 
You failed to attach the file that causes the error.
Also, attach full PR files as per FAQ.
Thank you for the answer, I trying today again and i have now another error. I do not patched any thing, I do only "If" syntax error like here in Guide and removed "Zero" syntax error.
I thank you in advance.
 

Attachments

  • DSDT Kopie.dsl
    611.1 KB · Views: 125
Thank you for the answer, I trying today again and i have now another error. I do not patched any thing, I do only "If" syntax error like here in Guide and removed "Zero" syntax error.
I thank you in advance.

You need to also attach native files extracted by Clover F4, to ACPI/origin.
 
Hi,

I have a question about DTGP. What is it and do I have to use it? I know that I can enable it in Clover.

I have seen various versions for DSDT hotfixes and some of them use it. For example @RehabMan Maintains the Null Ethernet Network Driver and in https://github.com/RehabMan/OS-X-Null-Ethernet/blob/master/SSDT-RMNE.dsl he uses this:

```
DefinitionBlock("", "SSDT", 2, "RehabMan", "_RMNE", 0x00001000)
{
Device (RMNE)
{
Name (_ADR, Zero)
// The NullEthernet kext matches on this HID
Name (_HID, "NULE0000")
// This is the MAC address returned by the kext. Modify if necessary.
Name (MAC, Buffer() { 0x11, 0x22, 0x33, 0x44, 0x55, 0x66 })
Method (_DSM, 4, NotSerialized)
{
If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }
Return (Package()
{
"built-in", Buffer() { 0x00 },
"IOName", "ethernet",
"name", Buffer() { "ethernet" },
"model", Buffer() { "RM-NullEthernet-1001" },
"device_type", Buffer() { "ethernet" },
})
}
}
}
```

However many many patches I have seen in github and other places use this version:

```
DefinitionBlock ("", "SSDT", 2, "hack", "_RMNE", 0x00000000)
{
External (DTGP, MethodObj) // 5 Arguments

Device (RMNE)
{
Name (_ADR, Zero) // _ADR: Address
Name (_HID, "NULE0000") // _HID: Hardware ID
Name (MAC, Buffer (0x06)
{
0x11, 0x22, 0x33, 0x44, 0x55, 0x66 // ."3DUf
})
Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
{
Local0 = Package (0x0A)
{
"built-in",
Buffer (One)
{
0x00 // .
},

"IOName",
"ethernet",
"name",
Buffer (0x09)
{
"ethernet"
},

"model",
Buffer (0x15)
{
"RM-NullEthernet-1001"
},

"device_type",
Buffer (0x09)
{
"ethernet"
}
}
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}
}
}
```

May I ask why is that and what is the right way to do it? And most importantly can someone give me a very brief explanation of what this DTGP does.

Thanks!
 
Hi, I am trying to patch a Xiaomi Mi Air 13.3’‘ Skylake-U 2016 running Mojave 10.14.2. I have the following very specific problems:

1. I am using @RehabMan hack-tools (really amazing toolkit) in order to generate a `LiluFriendLite.kext`. It seems that the `create_lilufriend.sh` does not take into account the `CPUFriendDataProvider.kext`. Do I need to add it manually in order to load it or `CPUFriend.kext` loads it since it is codeless?

2. When booting I am getting a lot messages of type power supply unavailable, assuming successful power for XXYY of 750 mWWakePower and 0 mWSleepPower. I inject USB power properties via SSDT-USBX.aml. What may be wrong:

Code:
2019-01-03 18:03:32.566401+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.566394 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS01 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.573344+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573338 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS02 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.573601+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573596 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS03 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.573883+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573878 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS04 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.574132+0200 0x65       Default     0x0                  0      0    kernel: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
2019-01-03 18:03:32.590052+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.590048 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS03 of 750 mWWakePower and 0 mWSleepPower

3. When booting I am getting a lot of these messages related to the camera. My camera works. Is this something I need to worry?

Code:
2019-01-03 18:03:41.027274+0200 0x1fc      Default     0x0                  0      0    kernel: Notice - new kext com.apple.driver.KextExcludeList, v14.0.3 matches prelinked kext but can't determine if executables are the same (no UUIDs).
2019-01-03 18:03:41.107540+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 14
2019-01-03 18:03:41.108071+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 21
2019-01-03 18:03:41.111504+0200 0x1fc      Default     0x0                  0      0    kernel: XiaoMi USB 2.0 Webcam: family specific matching fails
2019-01-03 18:03:41.111510+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.111514+0200 0x1fc      Default     0x0                  0      0    kernel: CDC Communications Control: family specific matching fails
2019-01-03 18:03:41.111517+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.111520+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 33

2019-01-03 18:03:41.113441+0200 0x1fc      Default     0x0                  0      0    kernel: XiaoMi USB 2.0 Webcam: family specific matching fails
2019-01-03 18:03:41.113445+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.113449+0200 0x1fc      Default     0x0                  0      0    kernel: CDC Communications Control: family specific matching fails
2019-01-03 18:03:41.113453+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.113455+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 35

4. And finally I get these messages that reference the battery and I am not sure if I am missing something:

Code:
2019-01-03 18:03:42.482981+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) High standby delay is not specified! Defaulting to 0x2a30
2019-01-03 18:03:42.482983+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) High standby delay is not specified! Defaulting to 0x2a30
2019-01-03 18:03:42.482989+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) Low battery threshold is not specified! Defaulting to 0x32
2019-01-03 18:03:42.482990+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) Low battery threshold is not specified! Defaulting to 0x32


Thanks for you time even reading my post.

I attach the debugging info. on the ACPI/patched I include the source .dsl files with my comments.

Thanks Again!!!!
 

Attachments

  • debug_6435.zip
    1.9 MB · Views: 91
Hi,

I have a question about DTGP. What is it and do I have to use it? I know that I can enable it in Clover.

I have seen various versions for DSDT hotfixes and some of them use it. For example @RehabMan Maintains the Null Ethernet Network Driver and in https://github.com/RehabMan/OS-X-Null-Ethernet/blob/master/SSDT-RMNE.dsl he uses this:

```
DefinitionBlock("", "SSDT", 2, "RehabMan", "_RMNE", 0x00001000)
{
Device (RMNE)
{
Name (_ADR, Zero)
// The NullEthernet kext matches on this HID
Name (_HID, "NULE0000")
// This is the MAC address returned by the kext. Modify if necessary.
Name (MAC, Buffer() { 0x11, 0x22, 0x33, 0x44, 0x55, 0x66 })
Method (_DSM, 4, NotSerialized)
{
If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }
Return (Package()
{
"built-in", Buffer() { 0x00 },
"IOName", "ethernet",
"name", Buffer() { "ethernet" },
"model", Buffer() { "RM-NullEthernet-1001" },
"device_type", Buffer() { "ethernet" },
})
}
}
}
```

However many many patches I have seen in github and other places use this version:

```
DefinitionBlock ("", "SSDT", 2, "hack", "_RMNE", 0x00000000)
{
External (DTGP, MethodObj) // 5 Arguments

Device (RMNE)
{
Name (_ADR, Zero) // _ADR: Address
Name (_HID, "NULE0000") // _HID: Hardware ID
Name (MAC, Buffer (0x06)
{
0x11, 0x22, 0x33, 0x44, 0x55, 0x66 // ."3DUf
})
Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
{
Local0 = Package (0x0A)
{
"built-in",
Buffer (One)
{
0x00 // .
},

"IOName",
"ethernet",
"name",
Buffer (0x09)
{
"ethernet"
},

"model",
Buffer (0x15)
{
"RM-NullEthernet-1001"
},

"device_type",
Buffer (0x09)
{
"ethernet"
}
}
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}
}
}
```

May I ask why is that and what is the right way to do it? And most importantly can someone give me a very brief explanation of what this DTGP does.

Thanks!

There is no need to use DTGP as the Apple specific _DSM can be implemented without it.
 
Hi, I am trying to patch a Xiaomi Mi Air 13.3’‘ Skylake-U 2016 running Mojave 10.14.2. I have the following very specific problems:

1. I am using @RehabMan hack-tools (really amazing toolkit) in order to generate a `LiluFriendLite.kext`. It seems that the `create_lilufriend.sh` does not take into account the `CPUFriendDataProvider.kext`. Do I need to add it manually in order to load it or `CPUFriend.kext` loads it since it is codeless?

2. When booting I am getting a lot messages of type power supply unavailable, assuming successful power for XXYY of 750 mWWakePower and 0 mWSleepPower. I inject USB power properties via SSDT-USBX.aml. What may be wrong:

Code:
2019-01-03 18:03:32.566401+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.566394 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS01 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.573344+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573338 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS02 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.573601+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573596 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS03 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.573883+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573878 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS04 of 750 mWWakePower and 0 mWSleepPower
2019-01-03 18:03:32.574132+0200 0x65       Default     0x0                  0      0    kernel: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
2019-01-03 18:03:32.590052+0200 0x77       Default     0x0                  0      0    <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.590048 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS03 of 750 mWWakePower and 0 mWSleepPower

3. When booting I am getting a lot of these messages related to the camera. My camera works. Is this something I need to worry?

Code:
2019-01-03 18:03:41.027274+0200 0x1fc      Default     0x0                  0      0    kernel: Notice - new kext com.apple.driver.KextExcludeList, v14.0.3 matches prelinked kext but can't determine if executables are the same (no UUIDs).
2019-01-03 18:03:41.107540+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 14
2019-01-03 18:03:41.108071+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 21
2019-01-03 18:03:41.111504+0200 0x1fc      Default     0x0                  0      0    kernel: XiaoMi USB 2.0 Webcam: family specific matching fails
2019-01-03 18:03:41.111510+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.111514+0200 0x1fc      Default     0x0                  0      0    kernel: CDC Communications Control: family specific matching fails
2019-01-03 18:03:41.111517+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.111520+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 33

2019-01-03 18:03:41.113441+0200 0x1fc      Default     0x0                  0      0    kernel: XiaoMi USB 2.0 Webcam: family specific matching fails
2019-01-03 18:03:41.113445+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.113449+0200 0x1fc      Default     0x0                  0      0    kernel: CDC Communications Control: family specific matching fails
2019-01-03 18:03:41.113453+0200 0x1fc      Default     0x0                  0      0    kernel: AppleUSBInterface: family specific matching fails
2019-01-03 18:03:41.113455+0200 0x1fc      Default     0x0                  0      0    kernel: Matching service count = 35

4. And finally I get these messages that reference the battery and I am not sure if I am missing something:

Code:
2019-01-03 18:03:42.482981+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) High standby delay is not specified! Defaulting to 0x2a30
2019-01-03 18:03:42.482983+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) High standby delay is not specified! Defaulting to 0x2a30
2019-01-03 18:03:42.482989+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) Low battery threshold is not specified! Defaulting to 0x32
2019-01-03 18:03:42.482990+0200 0x200      Default     0x0                  0      0    <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) Low battery threshold is not specified! Defaulting to 0x32


Thanks for you time even reading my post.

I attach the debugging info. on the ACPI/patched I include the source .dsl files with my comments.

Thanks Again!!!!

Off-topic.
 
Hi @RehabMan. A really fast question about patching and sorry for such a basic question. In the DSDT I see various ways of how a entity is written e.g.:

Code:
Scope (_SB.PCI0.LPCB.EC0)
Store (\_SB.PCI0.LPCB.EC0.MS0T, Local0)
External (_SB_.PCI0.LPCB.EC0_.CHRG, UnknownObj) 
Scope (\_GPE) (from a SSDT)

When should I use a \ and an _ after the symbol? Is Scope (_SB.PCI0.LPCB.EC0) the same as Scope (_SB_.PCI0.LPCB.EC0), Scope (\_SB_.PCI0.LPCB.EC0) and Scope (\_SB.PCI0.LPCB.EC0)

Thanks!
 
Hi guys! I've done install Mojave on my laptop but HDMI audio does not work (yet) and cannot manage how to make the keyboard backlights to work! I'll attach my patched DSDT (in .dsl mode, to be opened with MaciAsl). IS here someone with the same machine, who was managed how to turn on that stuff?
I tried these methods: AsusFnbKeys, with all methods (DSDT patch, kexts...), no luck AppleBacklightFixUp.kext and SSDT-PNLF from RehabMan (here I've done with basic screen backlight setup).
 

Attachments

  • DSDT.aml
    152.7 KB · Views: 169
  • DSDT.dsl
    1.2 MB · Views: 122
Back
Top