DSDT Debugging/Tracing to system.log

RehabMan · May 1, 2015

Of course i mean both keys, and i was wrong with the kext it was loaded

I've traced like crazy, and the keystrokes depends on this wmi event

If (And (WMEV, 0x0800))
                    {
                        Store (EC0A (WMBU), WMBU)
                        CWEV (0x0800)
                    }

where the wmi buffer depends on EC register

here the EC0A method

Method (EC0A, 1, NotSerialized)
        {
            Acquire (QSEV, 0xFFFF)
            Store (ECRB (0x2B), Local1)
            Store (Zero, Local0)
            While (LLess (Local0, Local1))
            {
                Store (ECRB (0x2C), Local2)
                If (LLess (Local0, SizeOf (Arg0)))
                {
                    BBWR (Arg0, Local0, Local2)
                }

                Increment (Local0)
            }

            Release (QSEV)
            Return (Arg0)
        }

or i'm doing something wrong?

You're going to have to keep digging.

wern apfel · May 1, 2015

I will

But why is this code not working ?, ecrd 1 brightness increase, and ecrd 0 degrease

Store(ECRD, Local0)\n
If (LEqual(Local0,1))\n
{\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0205)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0285)\n
}\n
If (LEqual(Local0,0))\n
{\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0206)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0286)\n

RehabMan · May 2, 2015

I will

But why is this code not working ?, ecrd 1 brightness increase, and ecrd 0 degrease

Store(ECRD, Local0)\n
If (LEqual(Local0,1))\n
{\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0205)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0285)\n
}\n
If (LEqual(Local0,0))\n
{\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0206)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0286)\n

Use ACPIDebug to determine if each section of code is being reached. Use the debug VoodooPS2Controller.kext to see if it is receiving/translating the codes.

wern apfel · May 2, 2015

Both keys call the same event, with your key-up code only brightness increase, and down code only degrease

ApplePS2Keyboard::message: type=e0028010, provider=0xffffff800af38600, argument=0xffffff809a793eac, argument=0205, cmp=e0028010

ApplePS2Keyboard: sending key e005=91 down

ApplePS2Keyboard::message: type=e0028010, provider=0xffffff800af38600, argument=0xffffff809a793eac, argument=0285, cmp=e0028010

ApplePS2Keyboard: sending key e005=91 up

And the keys FN + q,w,e,r,t,a,s,d,f,g do the same.

I think i will stay with hotkoffys wmi kext

RehabMan · May 2, 2015

Both keys call the same event, with your key-up code only brightness increase, and down code only degrease

ApplePS2Keyboard::message: type=e0028010, provider=0xffffff800af38600, argument=0xffffff809a793eac, argument=0205, cmp=e0028010

ApplePS2Keyboard: sending key e005=91 down

ApplePS2Keyboard::message: type=e0028010, provider=0xffffff800af38600, argument=0xffffff809a793eac, argument=0285, cmp=e0028010

ApplePS2Keyboard: sending key e005=91 up

The messages above show it working for backlight down (0x91 is down, 0x90 is up).

If you have the native slider in SysPrefs->Displays, you should see the native on-screen display overlay as you press that key. If you don't have the brightness slider working in SysPrefs->Displays, you need to fix that first. It is a prerequisite.

Note: This assumes the VoodooPS2Controller.kext you're using has not been significantly changed from my version and 0x91 and 0x90 are still ADB codes for brightness.

wern apfel · May 2, 2015

Yes but this happens if both keys were pressed, can't get them work separately

And yes your latest VoodooPS2Controller.kext is loaded, prefpane slider is working

RehabMan · May 2, 2015

Yes but this happens if both keys were pressed, can't get them work separately

And yes your latest VoodooPS2Controller.kext is loaded, prefpane slider is working

You need to trace/debug the existing code to determine how it disambiguates between each key. Then add/patch the code to send the appropriate code to the PS2 driver.

wern apfel · May 2, 2015

I can't instrument this buffer "Name (WMBU, Buffer (0x80) {})"

can't compile dsdt

RehabMan · May 2, 2015

I can't instrument this buffer "Name (WMBU, Buffer (0x80) {})"

can't compile dsdt

Not sure what you're referring to. Name(WMBU, Buffer(0x80){}) creates a variable of type buffer, 128 bytes long, named WMBU.

Post more details on what you're doing...

It might be helpful if you posted your native DSDT, edited DSDT (with instrumentation you have so far), and output from ACPIDebug in system.log clearly noted with results from pressing each key (independently).

wern apfel · May 3, 2015

I'm sniffly, and at the moment my brain is not working very well

Here is my dsdt, search for //_ to see my findings

DSDT-org-nvs.zip

RehabMan · May 3, 2015

I'm sniffly, and at the moment my brain is not working very well

Here is my dsdt, search for //_ to see my findings

I notice your DSDT doesn't emulate a version of Windows for _OSI("Darwin"). But it probably doesn't matter if the WMI kext works.

Why not instrument the WMI methods (or review the WMI driver) with the WMI kext installed, so you can see where the data can be read that disambiguates each key?

Note: The answer is probably in EC0A and what ends up in the WMBU buffer. You can print the WMBU buffer with ACPIDebug eg. \rmdt.p2("WMBU is", WMBU)

wern apfel · May 4, 2015

I notice your DSDT doesn't emulate a version of Windows for _OSI("Darwin"). But it probably doesn't matter if the WMI kext works.

Why not instrument the WMI methods (or review the WMI driver) with the WMI kext installed, so you can see where the data can be read that disambiguates each key?

Note: The answer is probably in EC0A and what ends up in the WMBU buffer. You can print the WMBU buffer with ACPIDebug eg. \rmdt.p2("WMBU is", WMBU)

This is my native dsdt, my patched emulates _OSI win7, the WMBU buffer is known, like i mentioned on early posts 50 degrease and 48 increase brightness, but i don't no how to split the key control

When i boot with the HD3000 card and emulate linux, brightness change is working without that wmi controls

RehabMan · May 4, 2015

This is my native dsdt, my patched emulates _OSI win7, the WMBU buffer is known, like i mentioned on early posts 50 degrease and 48 increase brightness, but i don't no how to split the key control

When i boot with the HD3000 card and emulate linux, brightness change is working without that wmi controls

Post DSDT with instrumentation. Post output in system.log from ACPIDebug with clear attribution as it relates to the keys you're pressing. I previously suggested this in post #34. I won't ask a 3rd time.

wern apfel · May 4, 2015

Added this to _WED method \RMDT.P2 ("WMBU", WMBU)

acpidebug output brightness key up

ACPIDebug: { "WMBU", { 0x02, 0x00, 0x10, 0x00, 0x48, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, }, }

key down

ACPIDebug: { "WMBU", { 0x02, 0x00, 0x10, 0x00, 0x50, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, }, }

RehabMan · May 4, 2015

Added this to _WED method \RMDT.P2 ("WMBU", WMBU)

acpidebug output brightness key up

ACPIDebug: { "WMBU", { 0x02, 0x00, 0x10, 0x00, 0x48, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, }, }

key down

ACPIDebug: { "WMBU", { 0x02, 0x00, 0x10, 0x00, 0x50, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, }, }

Please read post #38.

The key is probably in EC0A, which appears to be used to transfer the info from EC to WMBU...

        Method (EC0A, 1, NotSerialized)
        {
            Acquire (QSEV, 0xFFFF)
            Store (ECRB (0x2B), Local1) // read count of bytes
            Store (Zero, Local0)
            While (LLess (Local0, Local1)) // roughly: for (Local0=0; Local0<count; Local0++)
            {
                Store (ECRB (0x2C), Local2) // reading next byte of data from EC
                If (LLess (Local0, SizeOf (Arg0)))
                {
                    BBWR (Arg0, Local0, Local2) // BBWR (Buffer Byte Write) writes Local2 to buffer(Arg0) at offset Local0
                }

                Increment (Local0)
            }

            Release (QSEV)
            Return (Arg0)
        }

wern apfel · May 4, 2015

Now it looks better

key down

ACPIDebug: { "EC0A Local2 is", 0x2, }