Dell e6230 fn keys for brightness messed HELP please

[edgarrosandy]

First you need to instrument the method so you know:
1) that it is called
2) which path is taken for brightness up vs. brightness down

Then change the code to send the required Notifies to the keyboard driver.



Of course not.

I dont even understand any of the code. kinda confused where to start changing codes

 

[RehabMan]

I dont even understand any of the code. kinda confused where to start changing codes

Basic coding skills required. Did you instrument the method yet?

 

[edgarrosandy]

Basic coding skills required. Did you instrument the method yet?

By instrument the methode you mean like looking at the system.log while pressing my brightness keys after i installed ACPIDebug & patch ec queries&add debug methode?

 

[RehabMan]

By instrument the methode you mean like looking at the system.log while pressing my brightness keys after i installed ACPIDebug & patch ec queries&add debug methode?

In this case, by "instrument" I mean to add debug code to your DSDT to see which path the code takes when you press the keys.

Read the ACPIDebug.kext README. Using debug output (aka "trace code") is a basic programming skill...

 

[edgarrosandy]

In this case, by "instrument" I mean to add debug code to your DSDT to see which path the code takes when you press the keys.

Read the ACPIDebug.kext README. Using debug output (aka "trace code") is a basic programming skill...

i think i did add debug methodes on the dsdt after installed ACPIDebug.kext ?

 

[RehabMan]

i think i did add debug methodes on the dsdt after installed ACPIDebug.kext ?

You will need to add code (for example to BRT6) to determine the path that is taken...
Read the ACPIDebug README.

 

[edgarrosandy]

You will need to add code (for example to BRT6) to determine the path that is taken...
Read the ACPIDebug README.

I already read it over and over. none of these make sense to me. soo confused.
I dont know which code im supposed to add to the DSDT.

 

[edgarrosandy]

You will need to add code (for example to BRT6) to determine the path that is taken...
Read the ACPIDebug README.

IS this the code im supposed to add to the DSDT ? and change DBG0 to BRT6 ?

Method(DBG0, 1, Serialized)
{
   \RMDT.P2("DBG0 Arg0=", Arg0)
   If (LEqual(Arg0, 5))
   {
      \RMDT.P1("You set dbg0 to 5")
   }
   Else
   {
      \RMDT.P1("You set dbg0 to something other than 5")
   }
}

 

[RehabMan]

IS this the code im supposed to add to the DSDT ? and change DBG0 to BRT6 ?

Method(DBG0, 1, Serialized)
{
   \RMDT.P2("DBG0 Arg0=", Arg0)
   If (LEqual(Arg0, 5))
   {
      \RMDT.P1("You set dbg0 to 5")
   }
   Else
   {
      \RMDT.P1("You set dbg0 to something other than 5")
   }
}

Place the RMDT.P1 (or P3/P3/etc) calls into whatever method you want to instrument.

 

[edgarrosandy]

In this case, by "instrument" I mean to add debug code to your DSDT to see which path the code takes when you press the keys.

Read the ACPIDebug.kext README. Using debug output (aka "trace code") is a basic programming skill...

Okay so this is what ive put on tho the Method BRT6, is this correct ?

         Method (BRT6, 2, NotSerialized)                         
            {
                \rmdt.p1("BRT6 enter")
                If (LEqual (Arg0, One))
                {
                    Notify (LCD, 0x86)
                }

                If (And (Arg0, 0x02))
                {
                    Notify (LCD, 0x87)
                    \rmdt.p1("BRT6 exit")
                }
            }

This is what shows up on the console when i hit my brightness keys

Sep 30 09:59:52 localhost kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 09:59:55 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 09:59:57 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 09:59:59 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:01 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:03 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:05 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:07 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:09 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:11 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:12 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:12 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:13 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:27 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:42 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:00:51 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:01:22 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:01:43 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"
Sep 30 10:02:03 Brilliants-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q66 enter"