Contribute
Register

Problems with my Laptop after installing Yosemite

Status
Not open for further replies.
The correct patches for brightness are documented in post #5.

Ah! Finally, brightness bar works in System Prefs > Display :headbang: Thank you so much

Now, can you guide me how to map them to keyboard (My f2 and f3 keys are used for low and high respec.)

Thank you again for such a patient help :)

SilleBille
 
Ah! Finally, brightness bar works in System Prefs > Display :headbang: Thank you so much

Now, can you guide me how to map them to keyboard (My f2 and f3 keys are used for low and high respec.)

Thank you again for such a patient help :)

SilleBille

Which ps2 drivers are you using?

If you have Synaptics trackpad and are using mine here: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller

As far as getting brightness buttons working, first use the debug VoodooPS2Controller to see if they generate PS2 codes or not (probably not). Monitor system.log with Console.app while you press each key. If they generate a ps2 code, see custom keyboard mapping via Info.plist: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Use-Custom-Keyboard-Mapping

If no ps2 codes in system.log, then they are likely handled via ACPI. See here: https://github.com/RehabMan/OS-X-ACPI-Debug, install the kext, apply "Add DSDT Debug Methods" and "Instrument EC Queries". Look in system.log as you press the key to determine which _Qxx methods handle the keys.

Then patch DSDT:

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, 0x0205)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0285)\n
end;
into method label _Q11 replace_content
begin
// Brightness Up\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0206)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0286)\n
end;
 
Which ps2 drivers are you using?

If you have Synaptics trackpad and are using mine here: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller

As far as getting brightness buttons working, first use the debug VoodooPS2Controller to see if they generate PS2 codes or not (probably not). Monitor system.log with Console.app while you press each key. If they generate a ps2 code, see custom keyboard mapping via Info.plist: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Use-Custom-Keyboard-Mapping

If no ps2 codes in system.log, then they are likely handled via ACPI. See here: https://github.com/RehabMan/OS-X-ACPI-Debug, install the kext, apply "Add DSDT Debug Methods" and "Instrument EC Queries". Look in system.log as you press the key to determine which _Qxx methods handle the keys.

Then patch DSDT:

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, 0x0205)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0285)\n
end;
into method label _Q11 replace_content
begin
// Brightness Up\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0206)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0286)\n
end;
My Trackpad is Synaptics. But, I'm not sure about my keyboard! o_O

Here is the output of voodoo debug :

Code:
Thu Dec 11 21:47:46 2014: VoodooPS2Daemon 1.8.13 starting...
name = 'HP Truevision HD'
name = 'BCM20702A0'
name = 'VendorSpecificDevice'
name = 'HubDevice'
name = 'HubDevice'
name = 'XHCI Root Hub USB 2.0 Simulation'
name = 'XHCI Root Hub SS Simulation'
name = 'EHCI Root Hub Simulation'
name = 'EHCI Root Hub Simulation'

How will I find whether my keyboard is Synaptic?
 
My Trackpad is Synaptics. But, I'm not sure about my keyboard! o_O

Here is the output of voodoo debug :

Code:
Thu Dec 11 21:47:46 2014: VoodooPS2Daemon 1.8.13 starting...
name = 'HP Truevision HD'
name = 'BCM20702A0'
name = 'VendorSpecificDevice'
name = 'HubDevice'
name = 'HubDevice'
name = 'XHCI Root Hub USB 2.0 Simulation'
name = 'XHCI Root Hub SS Simulation'
name = 'EHCI Root Hub Simulation'
name = 'EHCI Root Hub Simulation'

How will I find whether my keyboard is Synaptic?

Synaptics does not make keyboards. They make trackpads. Read what I wrote carefully.
 
Synaptics does not make keyboards. They make trackpads. Read what I wrote carefully.

I'm really sorry. I was little excited when I fixed my brightness and battery. I'll try that and post back the results :)

SilleBille
 
Which ps2 drivers are you using?

If you have Synaptics trackpad and are using mine here: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller

As far as getting brightness buttons working, first use the debug VoodooPS2Controller to see if they generate PS2 codes or not (probably not). Monitor system.log with Console.app while you press each key. If they generate a ps2 code, see custom keyboard mapping via Info.plist: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Use-Custom-Keyboard-Mapping

If no ps2 codes in system.log, then they are likely handled via ACPI. See here: https://github.com/RehabMan/OS-X-ACPI-Debug, install the kext, apply "Add DSDT Debug Methods" and "Instrument EC Queries". Look in system.log as you press the key to determine which _Qxx methods handle the keys.

Then patch DSDT:

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, 0x0205)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0285)\n
end;
into method label _Q11 replace_content
begin
// Brightness Up\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0206)\n
    Notify(\_SB.PCI0.LPCB.PS2K, 0x0286)\n
end;

Hi Rehabman,

I tried using the debug version and monitored my System.log. I got some entries for f1 to f12:

Code:
Dec 12 21:42:20 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3b=7a down
Dec 12 21:42:22 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3c=78 down
Dec 12 21:42:24 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3d=63 down
Dec 12 21:42:24 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3e=76 down
Dec 12 21:42:25 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3f=60 down
Dec 12 21:42:25 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 40=61 down
Dec 12 21:42:26 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 41=62 down
Dec 12 21:42:27 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 42=64 down
Dec 12 21:42:27 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 43=65 down
Dec 12 21:42:28 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 44=6d down
Dec 12 21:42:28 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 57=67 down
Dec 12 21:42:32 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 58=6f down

I tried custom mapping as per your instructions. When I opened your info.plist located in VoodooPS2Controller.kext/Contents/Plugins/VoodooPS2Keyboard/Contents/info.plist I found many Custom PS2 map. Which one am i supposed to edit?

I have attached the info.plist. Also, there are only 2 or 3 keys inside every Custom PS2 map. Should I add manually for all function keys?

SilleBille
 

Attachments

  • Info.plist.zip
    4.3 KB · Views: 31
Hi Rehabman,

I tried using the debug version and monitored my System.log. I got some entries for f1 to f12:

Code:
Dec 12 21:42:20 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3b=7a down
Dec 12 21:42:22 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3c=78 down
Dec 12 21:42:24 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3d=63 down
Dec 12 21:42:24 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3e=76 down
Dec 12 21:42:25 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3f=60 down
Dec 12 21:42:25 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 40=61 down
Dec 12 21:42:26 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 41=62 down
Dec 12 21:42:27 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 42=64 down
Dec 12 21:42:27 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 43=65 down
Dec 12 21:42:28 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 44=6d down
Dec 12 21:42:28 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 57=67 down
Dec 12 21:42:32 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 58=6f down

Those are your normal F1...F12 keys. You are interested in the Fn+F1...F12.
 
Those are your normal F1...F12 keys. You are interested in the Fn+F1...F12.
This is the output for f1 to f12. Previous post was for fn + Fx.
Code:
Dec 12 21:50:33 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e05b=3a down
Dec 12 21:50:33 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3b=7a down
Dec 12 21:50:35 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3f=60 down
Dec 12 21:50:35 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e010=4d down
Dec 12 21:50:35 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e022=34 down
Dec 12 21:50:36 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e019=42 down
Dec 12 21:50:36 Dineshs-MacBook-Pro.local iTunes[3802]: ### PlayQueue::StartPlayingNextInternal: played off the end of the queue
Dec 12 21:50:36 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e02e=49 down
Dec 12 21:50:37 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e030=48 down

Also to add a note: In my windows, I press simply f2 and f3 for brightness down and up. Whereas to rename and do original function key actions, I press fn+fx.

f5 doesn't have any alternate option.

Here is my function key layout structure:
fx
fn + fx
Help Help
Brightness Low Rename
Brightness High
(I don't know)
Change O/P Display (I don't know)
Refresh Refresh
Previous track (I don't know)
Play/Pause (I don't know)
Next Track (I don't know)
Reduce Volume (I don't know)
Increase Volume (I don't know)
Mute/Unmute Full Screen
Toggle WiFi (I don't know)


SilleBille
 
This is the output for f1 to f12. Previous post was for fn + Fx.
Code:
Dec 12 21:50:33 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e05b=3a down
Dec 12 21:50:33 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3b=7a down
Dec 12 21:50:35 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key 3f=60 down
Dec 12 21:50:35 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e010=4d down
Dec 12 21:50:35 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e022=34 down
Dec 12 21:50:36 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e019=42 down
Dec 12 21:50:36 Dineshs-MacBook-Pro.local iTunes[3802]: ### PlayQueue::StartPlayingNextInternal: played off the end of the queue
Dec 12 21:50:36 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e02e=49 down
Dec 12 21:50:37 Dineshs-MacBook-Pro kernel[0]: ApplePS2Keyboard: sending key e030=48 down

Also to add a note: In my windows, I press simply f2 and f3 for brightness down and up. Whereas to rename and do original function key actions, I press fn+fx.

Yes... it is common on new computers to reverse the function of Fn+F1...F12 and F1...F12. Yours is reversed, so your brightness keys are without Fn. Note that there is usually a BIOS option to revert this reversing...

You need to determine if your brightness keys generate a code. Since you didn't provide any info on what keys generate the output above, no idea for you...
 
Yes... it is common on new computers to reverse the function of Fn+F1...F12 and F1...F12. Yours is reversed, so your brightness keys are without Fn. Note that there is usually a BIOS option to revert this reversing...

You need to determine if your brightness keys generate a code. Since you didn't provide any info on what keys generate the output above, no idea for you...
It's weird! My f2 and f3 keys don't generate any code o_O I have made a decision to map fn+f2 to brighness low and fn+f3 to brightness high.

In your instruction (from link above), you have asked to modify Custom PS2 Map. In the info.plist, there are about 5 Custom PS2 map. :crazy:

Which one should I edit? And also there are only 2 or 3 entries under every custom PS2 map. But, in the tutorial you have mentioned there will be 12. :confused:

SilleBille
 
Status
Not open for further replies.
Back
Top