Contribute
Register

ACPIDebug no output

Joined
Nov 16, 2016
Messages
2
Motherboard
HM77
CPU
i5-3210
Graphics
HD4000
Problem Description
ACPIDebug failed to start, there is no output about "ACPIDebug" in "system.log"("console" -> "system.log"). After a full day of Google/Baidu, I still have no idea about this problem. So I'm here for help. Thanks for all solutions.

The Steps I Followed
I followed this guide, http://www.tonymacx86.com/yosemite-...ching-dsdt-ssdt-laptop-backlight-control.html. Below is the detail:
- install ACPIDebug.kext: https://github.com/RehabMan/OS-X-ACPI-Debug
- add the ACPIDebug repo to MaciASL "Sources" per README
- apply ""Add DSDT Debug Methods"
- apply "Instrument EC Queries"
- reboot


The Way To Confirm Patch And Kext Applied Successfully
First, I confirm the patch like this:
- in terminal, run "patchmatic -extract"
- decompile dsdt.aml and see the following info

a.
Device (RMDT)
{
Name (_HID, "RMD0000") // _HID: Hardware ID
Name (RING, Package (0x0100) {})
Mutex (RTMX, 0x00)
Name (HEAD, Zero)
Name (TAIL, Zero)
Method (PUSH, 1, NotSerialized)
{
Acquire (RTMX, 0xFFFF)
Add (HEAD, One, Local0)
If (LGreaterEqual (Local0, SizeOf (RING)))
{
Store (Zero, Local0)
}

If (LNotEqual (Local0, TAIL))
{
Store (Arg0, Index (RING, HEAD))
Store (Local0, HEAD)
}

Release (RTMX)
Notify (RMDT, 0x80)
}

...
}
b.
Method (_Q1D, 0, NotSerialized) // _Qxx: EC Query
{
\RMDT.P1 ("EC _Q1D enter")
PCLK ()
\RMDT.P1 ("EC _Q1D exit")
}
...

Therefore, I think patch is OK.

Second, I confirm kext loaded by doing this:
- in terminal, run "dbmesg > t.txt"
- in t.txt I can see:

3:975 0:001 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
3:975 0:000 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
3:995 0:020 Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext
4:032 0:036 Extra kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext
4:047 0:015 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
4:063 0:016 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
4:064 0:000 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
4:074 0:010 Extra kext: EFI\CLOVER\kexts\Other\ACPIDebug.kext


Therefore, ACPIDebug is also loaded successfully.

Unfortunately, The ACPIDebug is still not working. Thanks for all answers.

Sorry for my poor English!

 

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,728
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Problem Description
ACPIDebug failed to start, there is no output about "ACPIDebug" in "system.log"("console" -> "system.log"). After a full day of Google/Baidu, I still have no idea about this problem. So I'm here for help. Thanks for all solutions.

The Steps I Followed
I followed this guide, http://www.tonymacx86.com/yosemite-...ching-dsdt-ssdt-laptop-backlight-control.html. Below is the detail:
- install ACPIDebug.kext: https://github.com/RehabMan/OS-X-ACPI-Debug
- add the ACPIDebug repo to MaciASL "Sources" per README
- apply ""Add DSDT Debug Methods"
- apply "Instrument EC Queries"
- reboot

The Way To Confirm Patch And Kext Applied Successfully
First, I confirm the patch like this:
- in terminal, run "patchmatic -extract"
- decompile dsdt.aml and see the following info

a.
Device (RMDT)
{
Name (_HID, "RMD0000") // _HID: Hardware ID
Name (RING, Package (0x0100) {})
Mutex (RTMX, 0x00)
Name (HEAD, Zero)
Name (TAIL, Zero)
Method (PUSH, 1, NotSerialized)
{
Acquire (RTMX, 0xFFFF)
Add (HEAD, One, Local0)
If (LGreaterEqual (Local0, SizeOf (RING)))
{
Store (Zero, Local0)
}

If (LNotEqual (Local0, TAIL))
{
Store (Arg0, Index (RING, HEAD))
Store (Local0, HEAD)
}

Release (RTMX)
Notify (RMDT, 0x80)
}

...
}
b.
Method (_Q1D, 0, NotSerialized) // _Qxx: EC Query
{
\RMDT.P1 ("EC _Q1D enter")
PCLK ()
\RMDT.P1 ("EC _Q1D exit")
}
...

Therefore, I think patch is OK.

Second, I confirm kext loaded by doing this:
- in terminal, run "dbmesg > t.txt"
- in t.txt I can see:

3:975 0:001 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
3:975 0:000 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
3:995 0:020 Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext
4:032 0:036 Extra kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext
4:047 0:015 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
4:063 0:016 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
4:064 0:000 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
4:074 0:010 Extra kext: EFI\CLOVER\kexts\Other\ACPIDebug.kext

Therefore, ACPIDebug is also loaded successfully.

Unfortunately, The ACPIDebug is still not working. Thanks for all answers.

Sorry for my poor English!


Keep in mind new system logging in Sierra (/var/log/system.log no longer used). Read Apple developer documentation for details.

You can verify ACPIDebug is loading by looking at ioreg.
 
Joined
Nov 16, 2016
Messages
2
Motherboard
HM77
CPU
i5-3210
Graphics
HD4000
Keep in mind new system logging in Sierra (/var/log/system.log no longer used). Read Apple developer documentation for details.

You can verify ACPIDebug is loading by looking at ioreg.

Nice, after running "log show --last 5" in terminal, I see some messages about ACPIDebug.
So excited.
Thank you very much!
 
  • Like
Reactions: SuY
Joined
Dec 27, 2011
Messages
146
CPU
i5-3317U
Graphics
HD4000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hello RehabMan,
I have same problem reported here, but El Capitan 10.11.6.
Please check files attached.

Thanks in advance.
 

Attachments

  • files.zip
    408.6 KB · Views: 109
Joined
Mar 29, 2019
Messages
1
Motherboard
MSI P65 Creator
CPU
i7-8750H/HM370
Graphics
HM370 + GTX 1070 Max-Q
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
I know this is an old topic, but I had the same problem on Mojave. I found a solution to be building from source after setting the target to "MacOS" rather than "macos10.8" (or whatever)... once built (and you can find the derived files)... you can install the kext to /Library/Extensions/.

Another tip to view the logs is to use this "log show" command:

log show --predicate 'processID == 0 && eventMessage CONTAINS[c] "ACPIDebug"' --start 2019-04-22 --debug

This will give the color-formatted output.

If I get time I might submit a PR to update the project, or even the built binaries.

Cheers!
-Sean

*UPDATE: Although this seems to show the ACPIDebug messages appearing in the log, I'm actually still not seeing any logs when I add some \RMDT.PUSH("...") statements in the DSDT.aml compiled code. I'm verifying the DSDT changes are loaded with IOExplorer as well. I'll be digging into this more tonight. I might start a new topic where I can provide more details (and have updated profile info for aid with debugging)

**UPDATE 2: I can confirm with some certainty that the debug logging works intermittently. I will either get no logging, or full logging. I suspect it may have something to with the loading order of the kexts. I might play with this some more.
 
Last edited:
Joined
Nov 12, 2018
Messages
18
Motherboard
ASRock Z390 PHANTOM ITX
CPU
i7-9700K
Graphics
RX 580 + UHD 630
Mac
  1. MacBook Pro
Classic Mac
  1. eMac
Mobile Phone
  1. Android
  2. iOS
**UPDATE 2: I can confirm with some certainty that the debug logging works intermittently. I will either get no logging, or full logging. I suspect it may have something to with the loading order of the kexts. I might play with this some more.

Any update here? I'm working on some DSDT changes and I'm getting a bit confused at this point as to whether it's running at all.
 
Top