Contribute
Register

[Guide] Patching DSDT/SSDT for LAPTOP backlight control

Joined
Aug 23, 2017
Messages
92
Motherboard
ASUS S451LB
CPU
i3-4010U
Graphics
HD 4400 / GT 740M
Mac
MacBook Pro
Mobile Phone
Android
I see no issue in that image. You will need to clarify your problem.
This file will tell you my problem, at the first boot the brightness level and also slider isn't working. But strangely when i do the sleep and then wake again, the brighntess level are working also the slider. So what is the main problem ?
 

Attachments

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,259
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
This file will tell you my problem, at the first boot the brightness level and also slider isn't working. But strangely when i do the sleep and then wake again, the brighntess level are working also the slider. So what is the main problem ?
Did you enable CSM/legacy boot in BIOS?
 
Joined
Aug 23, 2017
Messages
92
Motherboard
ASUS S451LB
CPU
i3-4010U
Graphics
HD 4400 / GT 740M
Mac
MacBook Pro
Mobile Phone
Android
CSM is often tied to legacy boot. Enable legacy, but still boot UEFI.
Oh man, i've enabled the legacy on my bios. And the brightness now work flawlessly. Thank you so much
But, anyway can you tell me why this can be happen ?
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,259
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
Oh man, i've enabled the legacy on my bios. And the brightness now work flawlessly. Thank you so much
But, anyway can you tell me why this can be happen ?
Enabling CSM (either independently or by enabling legacy boot) causes the BIOS to do a more complete initialization of graphics hardware registers.
 
Joined
Dec 1, 2018
Messages
13
Motherboard
Asus X99 Deluxe
CPU
i7-5820K
Graphics
GTX 980 Ti
Mac
iMac
Mobile Phone
Android
Hi,
I see 2 topic guide about backlight, use applebacklight.kext and patch dsdt/sdst. Can i do both? Install Applebacklight follow topic 1 and patch DSDT/SDSt follow topci 2?
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,259
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
Hi,
I see 2 topic guide about backlight, use applebacklight.kext and patch dsdt/sdst. Can i do both? Install Applebacklight follow topic 1 and patch DSDT/SDSt follow topci 2?
Best method depends on which version of macOS/OS X you're running.
 
Joined
Jan 12, 2019
Messages
16
Motherboard
HP Spectre 13-v130ng-Clover
CPU
i7-7500U
Graphics
HD 620, 1920x1080
Mobile Phone
Android
Brightness Keys

The brightness patch will only enable the slider in SysPrefs->Displays. Keyboard control is a separate issue, as the keyboard driver must generate the special codes used to trigger the OS X native backlight controls.

Your brightness keys (usually one of the Fn+F1...F12 keys) may be handled with PS2 or ACPI. Most newer computers use ACPI for these keys. If your trackpad is Synaptics and you're using my fork VoodooPS2Controller.kext (https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller), you can make either case work.

The first step is to determine if they are handled by PS2 or ACPI. With my driver, you can use 'ioio -s ApplePS2Keyboard LogScanCodes 1' to turn on the key logging to system.log. The ioio binary is available here: https://github.com/RehabMan/OS-X-ioio (please read the README for download locations). After turning on key logging, monitor system.log with Console.app to determine what PS2 codes (if any) are generated when you press your keys). If they generate PS2 codes, you can map them to backlight control by following the wiki: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Use-Custom-Keyboard-Mapping.

If your keys do not generate PS2 codes, it is likely they generate ACPI events. In order to intercept the ACPI events, you will need to determine which method(s) are called when the keys are pressed. Usually, media keys generate EC queries. A simple strategy is to use ACPIDebug.kext to instrument all EC query methods, then press the keys while monitoring system.log. When you press the keys, the name of the method will be output, which will allow you to patch that method.

Note: It is relatively common that the EC will not generate these events unless a certain version of Windows is being emulated by the DSDT. Make sure you patch DSDT as per the linked guide before getting to this. In particular, one of the "OS Check Fix" patches may be necessary before the EC query methods will be called.

Determining EC query methods:

- 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
- monitor system.log as you press your brightness keys

After you have determined which methods correspond to the brightness keys, you can patch the methods...

Assuming _Q10 is brightness down, and _Q11 is up.
Code:
into method label _Q10 replace_content
begin
// Brightness Down\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0405)\n
end;
into method label _Q11 replace_content
begin
// Brightness Up\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0406)\n
end;
The 0x0405 corresponds to PS2 keydown/keyup are automatic (e005/e085) for the brightness down key used by Dell laptops. In the default keyboard profile, these correspond to ADB codes 91/90 (brigthness down/up). If your laptop uses a keyboard profile other than the default, you may need to use different codes.

For 10.12+, you might want to generate F14/F15 due to problems with the "real" brightness key codes:
Code:
into method label _Q10 replace_content
begin
// Brightness Down\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0365) //F14\n
end;
into method label _Q11 replace_content
begin
// Brightness Up\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0366) //F15\n
end;
Note: For 10.12, VoodooPS2Controller.kext (version 1.8.25 or later) has been updated to generate F14/F15 instead of the brightness ADB codes. Make sure you have the latest version installed.

It is possible for both keys (up/down) to generate a call to the same EC query method. This is the case with the Haswell HP Envy, for example. By examining the code it is possible to determine how to disambiguate. As it turns out a variable in the EC is set to indicate the function to be performed when the _Q13 method is invoked. The patch for this case is as follows:

Code:
into method label _Q13 replace_content
begin
Store(HKNO, Local0)\n
If (LEqual(Local0,7))\n
{\n
// Brightness Down\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0405)\n
}\n
If (LEqual(Local0,8))\n
{\n
// Brightness Up\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0406)\n
}\n
If (LEqual(Local0,4))\n
{\n
// Mirror toggle\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x046e)\n
}\n
end;
Note: This patch also includes support for the "mirror toggle" function, where the standard PS2 code is 0e6e/0eee (make/break).

Of course, this code is based on the original code in the DSDT for the HP Haswell Envy. It is likely the details for disambiguation in your DSDT differs. You need to read the original code and make the adjustments to the replacement code as necessary.

As another example, some of the recent Dell laptops have a complex path from EC queries (or even a single query method) through NEVT that eventually lands in the BRT6 method. Resulting in the following patch:
Code:
into method label BRT6 replace_content
begin
    If (LEqual (Arg0, One))\n
    {\n
// Brightness Up\n
        Notify (^^LPCB.PS2K, 0x0406)\n
    }\n
    If (And (Arg0, 0x02))\n
    {\n
// Brightness Down\n
        Notify (^^LPCB.PS2K, 0x0405)\n
    }\n
end;
Recent laptops are showing even more complex scenarios. Some use GPE methods instead of EC queries (meaning you must instrument GPE methods to determine which one). And some funnel all events through one GPE method typically routing through a single method (typically NEVT). See here for a detailed walkthrough/example: http://www.tonymacx86.com/yosemite-laptop-support/152659-guide-patching-dsdt-ssdt-laptop-backlight-control-44.html#post1100377

Note: Not all DSDTs use PS2K as the name for the keyboard object. Search for PNP0303 or PNP030B. Also, not all DSDTs use LPCB as the LPC device. Use the actual path your DSDT uses.

Note on certain Dell laptops

Some Dell laptops generate PS2 codes for the brightness keys. There is built-in support for these PS2 codes in my VoodooPS2Controller.kext. But often these keyboards generate 'make' codes without 'break' codes. That is, they generate codes for the keys going down, but no code for the key being released. This causes the key to infinitely repeat.

The VoodooPS2Keyboard.kext driver has a mechanism to fix this called "Breakless PS2". And there is a built-in Dell profile that has the correct "Breakless PS2" setttings. But you have to select the profile with an SSDT.

The SSDT is checked into the VoodooPS2 project as SSDT-DELL-WN09.dsl: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller

To use it, save as AML, and place in ACPI/patched so it can be loaded by Clover. If you're using SortedOrder, make sure it refers to the file you place in ACPI/patched.


Note on ELAN (and other) drivers

If you are using another keyboard driver, instead of sending notifications to the PS2 object, you can send them to an object attached to ACPIKeyboard.kext The process is very similar to the process as written above (for ACPI), and is covered well at the ACPIKeyboard github README. See here: https://github.com/RehabMan/OS-X-ACPI-Keyboard

Some newer versions of the ELAN driver may have direct support with codes 0x10 and 0x20. So, no need for ACPIKeyboard.kext in this case.

See below for an example:
Code:
into method label _Q28 replace_content
begin
// Brightness Down\n
    Notify (PS2K, 0x20)\n
end;
into method label _Q30 replace_content
begin
// Brightness Up\n
    Notify (PS2K, 0x10)\n
end;
Regarding Brightness Keys and monitoring system.log a note regarding 10.12+ would help: With macOS Sierra the system.log output has changed. To actually see your key inputs use log show --predicate "processID == 0" --start YYYY-MM-DD --debug and replace YYYY-MM-DD with the current date.

After I finally found out why I didn't saw any key inputs by either using Console or cat system.log I don't have them on Q10/Q11 but Q11/Q12 and my buttons are working now. Thank you very much for all of your guides, patches and hard work!
 
Joined
Aug 21, 2012
Messages
38
Motherboard
Dell Precision M7510
CPU
Xeon E3-1505M
Graphics
HD530, NVIDIA Quadro M2000M
Use Rehabman's driver on my Dell laptop, without any modification for brightness keys mapping, I have Fn + F6 triggering brightness down. Any other Fx key, or Fn + Fx key combination doesn't trigger brightness up.
How can I map the keys to have brightness-up to work.
Following are related log shown when key pressed.

Code:
F1:
2019-01-19 14:56:14.851269+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3b=7a down
2019-01-19 14:56:14.851296+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=6dd2b0ea, cmp=e0028010
2019-01-19 14:56:14.851311+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=6dd2b0ea, cmp=e0028010

2019-01-19 14:56:14.934185+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3b=7a up
2019-01-19 14:56:14.934213+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=72c47c3d, cmp=e0028010
2019-01-19 14:56:14.934227+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=72c47c3d, cmp=e0028010


Fn + F1
2019-01-19 13:06:01.974751+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key e020=4a down
2019-01-19 13:06:01.974778+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=fb5f2c2e, cmp=e0028010
2019-01-19 13:06:01.974793+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=fb5f2c2e, cmp=e0028010

2019-01-19 13:06:02.047951+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key e020=4a up
2019-01-19 13:06:02.047970+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=ffbc3015, cmp=e0028010
2019-01-19 13:06:02.047980+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=ffbc3015, cmp=e0028010


==================================================================================================================================================
F2:
2019-01-19 12:48:34.038117+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3c=78 down
2019-01-19 12:48:34.038143+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=fd9cbe9a, cmp=e0028010
2019-01-19 12:48:34.038158+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=fd9cbe9a, cmp=e0028010

2019-01-19 12:48:34.086529+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3c=78 up
2019-01-19 12:48:34.086548+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=7f8744, cmp=e0028010
2019-01-19 12:48:34.086557+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=7f8744, cmp=e0028010


Fn + F2
2019-01-19 12:49:33.520831+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key e02e=49 down
2019-01-19 12:49:33.520858+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=d70cd512, cmp=e0028010
2019-01-19 12:49:33.520871+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=d70cd512, cmp=e0028010

2019-01-19 12:49:33.577019+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key e02e=49 up
2019-01-19 12:49:33.577032+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=da665a3e, cmp=e0028010
2019-01-19 12:49:33.577038+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=da665a3e, cmp=e0028010



==================================================================================================================================================
F3:
2019-01-19 12:53:17.634976+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3d=63 down
2019-01-19 12:53:17.634993+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=5436e07, cmp=e0028010
2019-01-19 12:53:17.635003+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=5436e07, cmp=e0028010

2019-01-19 12:53:17.676751+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3d=63 up
2019-01-19 12:53:17.676776+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=7c09d8c, cmp=e0028010
2019-01-19 12:53:17.676790+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=7c09d8c, cmp=e0028010


Fn + F3
2019-01-19 12:54:49.780372+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key e030=48 down
2019-01-19 12:54:49.780397+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=798b10e2, cmp=e0028010
2019-01-19 12:54:49.780411+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=798b10e2, cmp=e0028010

2019-01-19 12:54:49.838554+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key e030=48 up
2019-01-19 12:54:49.838574+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=7d031d20, cmp=e0028010
2019-01-19 12:54:49.838583+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=7d031d20, cmp=e0028010



==================================================================================================================================================
F4:
2019-01-19 13:00:17.042165+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3e=76 down
2019-01-19 13:00:17.042181+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=abd279c3, cmp=e0028010
2019-01-19 13:00:17.042187+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=abd279c3, cmp=e0028010

2019-01-19 13:00:17.106474+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 3e=76 up
2019-01-19 13:00:17.106491+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=afa791b0, cmp=e0028010
2019-01-19 13:00:17.106499+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=afa791b0, cmp=e0028010

Fn + F4:
No log



==================================================================================================================================================
F6:
2019-01-19 13:02:47.485773+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 40=61 down
2019-01-19 13:02:47.485798+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=b2f37dc7, cmp=e0028010
2019-01-19 13:02:47.485813+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=b2f37dc7, cmp=e0028010

2019-01-19 13:02:47.555998+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 40=61 up
2019-01-19 13:02:47.556023+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=b7230992, cmp=e0028010
2019-01-19 13:02:47.556038+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=b7230992, cmp=e0028010



Fn + F6             
(*** This trigger brightness down)
2019-01-19 13:01:54.976447+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 46=6b down
2019-01-19 13:01:54.976475+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=79288ce3, cmp=e0028010
2019-01-19 13:01:54.976489+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=79288ce3, cmp=e0028010

2019-01-19 13:01:55.035726+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 46=6b up
2019-01-19 13:01:55.035750+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=7cb0e7f0, cmp=e0028010
2019-01-19 13:01:55.035765+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=7cb0e7f0, cmp=e0028010




==================================================================================================================================================
F11:
2019-01-19 13:57:25.475046+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 57=67 down
2019-01-19 13:57:25.475073+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=e9ef848d, cmp=e0028010
2019-01-19 13:57:25.475087+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=e9ef848d, cmp=e0028010

2019-01-19 13:57:25.539327+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 57=67 up
2019-01-19 13:57:25.539359+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=edc3f07d, cmp=e0028010
2019-01-19 13:57:25.539380+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=edc3f07d, cmp=e0028010


Fn + F11:
No log




==================================================================================================================================================
F12:
2019-01-19 13:57:22.835021+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 58=6f down
2019-01-19 13:57:22.835048+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=4c93dc1f, cmp=e0028010
2019-01-19 13:57:22.835067+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=4c93dc1f, cmp=e0028010

2019-01-19 13:57:22.926774+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard: sending key 58=6f up
2019-01-19 13:57:22.926801+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff8066, provider=<private>, argument=<private>, argument=520c0988, cmp=e0028010
2019-01-19 13:57:22.926816+0000 0x104      Default     0x0                  0      0    kernel: (kernel) ApplePS2Keyboard::message: type=e3ff806e, provider=<private>, argument=<private>, argument=520c0988, cmp=e0028010


Fn + F12:
No log
 
Top