Contribute
Register

samsung np370r5e-s06

Status
Not open for further replies.
RehabMan said:
It is in the keyboard driver, VoodooPS2Keyboard.kext (a PlugIn of VoodooPS2Controller.kext).
Click to expand...

Found it. But what I should to do next?

I used debug version of the VoodooPS2Controller.kext so in verbose load have message
ApplePS2Keyboard::message: type=e0000230, provider=0xffffff80132f8900, argument=0xffffff88d5723cc0, argument=0000, cmp=e8828010
ApplePS2Keyboard::message: type=e0000230, provider=0xffffff80132f800, argument=0xffffff88d4c73cc0, argument=0000, cmp=e8828010
 
uniday said:
Done.
OS X started with black screen. (Brightness was on minmum level)
Using flashlight made login and increase brightness :)

But brightness control is not working... The same minimum level and "other"

include new files ioreg and patchmatic

View attachment 118059

View attachment 118058
Click to expand...

How did you "increase brightness" if "brightness control is not working"?
 
uniday said:
Found it. But what I should to do next?

I used debug version of the VoodooPS2Controller.kext so in verbose load have message
ApplePS2Keyboard::message: type=e0000230, provider=0xffffff80132f8900, argument=0xffffff88d5723cc0, argument=0000, cmp=e8828010
ApplePS2Keyboard::message: type=e0000230, provider=0xffffff80132f800, argument=0xffffff88d4c73cc0, argument=0000, cmp=e8828010
Click to expand...

You need to press the keys that are breakless, so you can determine which scan codes should be entered into "Breakless PS2" in the Info.plist.
 
RehabMan said:
How did you "increase brightness" if "brightness control is not working"?
Click to expand...

I'm already told you... (maybe I should describe the problem in more detail)
Brightness control is not working properly.... but it is working...
When I set minimum level brightness is almost looks like black screen... when using flashlight as back-light is possible to see the picture...
When set any other position brightness become on maximum level (if power is plugged in)
And if I disconnect the power from laptop brightness become on 80% (or so)
But if I set position of brightness control to maximum with disconnected power... nothing happens...
 
RehabMan said:
You need to press the keys that are breakless, so you can determine which scan codes should be entered into "Breakless PS2" in the Info.plist.
Click to expand...

I'm understand that for you this is that simple as fill the cap of water .... but I'm really really do not understand what are you writing )
Ok .... I installed OS-X-Voodoo-PS2-Controller using this guide https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Install
With one exception I cant do this step
cp ./ProBook/Trackpad-Info.plist ./Release/VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Trackpad.kext/Contents/Info.plist
cp ./ProBook/Keyboard-Info.plist ./Release/VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Keyboard.kext/Contents/Info.plist
because I cant find ./ProBook/ folder

Found this guide
https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Use-Custom-Keyboard-Mapping

Started Karabiner...
eventType:keyDown code:0x7a name:F1 flags:Fn misc:KeyCode::F1 characters:
eventType:keyUp code:0x7a name:F1 flags:Fn misc:KeyCode::F1 characters:
eventType:keyDown code:0x78 name:F2 flags:Fn misc:KeyCode::F2 characters:
eventType:keyUp code:0x78 name:F2 flags:Fn misc:KeyCode::F2 characters:
eventType:keyDown code:0x61 name:F6 flags:Fn misc:KeyCode::F6 characters:
eventType:keyUp code:0x61 name:F6 flags:Fn misc:KeyCode::F6 characters:
eventType:keyDown code:0x62 name:F7 flags:Fn misc:KeyCode::F7 characters:
eventType:keyUp code:0x62 name:F7 flags:Fn misc:KeyCode::F7 characters:
eventType:keyDown code:0x64 name:F8 flags:Fn misc:KeyCode::F8 characters:
eventType:keyUp code:0x64 name:F8 flags:Fn misc:KeyCode::F8 characters:


When I trying press Fn+F1 I have no respond ....
If I press FN+F6...F8 (sound control) all work correct but also no respond in table...
Single Fn button also have no respond in table.
 
uniday said:
...
With one exception I cant do this step
cp ./ProBook/Trackpad-Info.plist ./Release/VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Trackpad.kext/Contents/Info.plist
cp ./ProBook/Keyboard-Info.plist ./Release/VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Keyboard.kext/Contents/Info.plist
because I cant find ./ProBook/ folder
Click to expand...

Read carefully. That section is prefaced by "For versions 1.8.0, 1.8.1, and 1.8.2, ProBook users not using kozlek's branch of FakeSMC..."

Note:
- current version is 1.8.13 (not 1.8.0, 1.8.1, or 1.8.2)
- you don't have a Probook (ProBooks are an HP product, your laptop is Samsung)
- you are likely using kozlek's branch of FakeSMC

Found this guide
https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Use-Custom-Keyboard-Mapping

Started Karabiner...
eventType:keyDown code:0x7a name:F1 flags:Fn misc:KeyCode::F1 characters:
eventType:keyUp code:0x7a name:F1 flags:Fn misc:KeyCode::F1 characters:
eventType:keyDown code:0x78 name:F2 flags:Fn misc:KeyCode::F2 characters:
eventType:keyUp code:0x78 name:F2 flags:Fn misc:KeyCode::F2 characters:
eventType:keyDown code:0x61 name:F6 flags:Fn misc:KeyCode::F6 characters:
eventType:keyUp code:0x61 name:F6 flags:Fn misc:KeyCode::F6 characters:
eventType:keyDown code:0x62 name:F7 flags:Fn misc:KeyCode::F7 characters:
eventType:keyUp code:0x62 name:F7 flags:Fn misc:KeyCode::F7 characters:
eventType:keyDown code:0x64 name:F8 flags:Fn misc:KeyCode::F8 characters:
eventType:keyUp code:0x64 name:F8 flags:Fn misc:KeyCode::F8 characters:
Click to expand...

Karibiner has nothing to do with the process. The scan codes are output by the debug kext in system.log.
 
RehabMan said:
The scan codes are output by the debug kext in system.log.
Click to expand...

Thanks... Found it
Dec 16 17:58:52 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key e04e=90 down
it was FN+F1
Dec 16 17:58:53 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key e009=83 down
FN+F2
Dec 16 17:58:55 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key 1=35 down
I think it was ESC
Dec 16 17:59:05 MacBook-Pro-Denis.local Console[634]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
 
uniday said:
Thanks... Found it
Dec 16 17:58:52 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key e04e=90 down
it was FN+F1
Dec 16 17:58:53 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key e009=83 down
FN+F2
Dec 16 17:58:55 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key 1=35 down
I think it was ESC
Dec 16 17:59:05 MacBook-Pro-Denis.local Console[634]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
Click to expand...

Now determine which keys are breakless. If you use 'ioio -s ApplePS2Keyboard LogScanCodes 2', you can see both the down (make) and up (break) events. ioio: https://github.com/RehabMan/OS-X-ioio
 
RehabMan said:
Now determine which keys are breakless. If you use 'ioio -s ApplePS2Keyboard LogScanCodes 2', you can see both the down (make) and up (break) events. ioio: https://github.com/RehabMan/OS-X-ioio
Click to expand...

Done...

MacBook-Pro-Denis:~ UniDay$ ioio -s ApplePS2Keyboard LogScanCodes 2
argv[0] = { ioio }
argv[1] = { -s }
argv[2] = { ApplePS2Keyboard }
argv[3] = { LogScanCodes }
argv[4] = { 2 }
ioio: setting property 'ApplePS2Keyboard:LogScanCodes' as number to 2 (0x2)

Rebooted.... But system log is the same ... only "key down" messages
Dec 16 21:33:44 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key 3d=63 down
F3
Dec 16 21:33:47 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key e008=80 down
Fn+F3
 
uniday said:
Done...

MacBook-Pro-Denis:~ UniDay$ ioio -s ApplePS2Keyboard LogScanCodes 2
argv[0] = { ioio }
argv[1] = { -s }
argv[2] = { ApplePS2Keyboard }
argv[3] = { LogScanCodes }
argv[4] = { 2 }
ioio: setting property 'ApplePS2Keyboard:LogScanCodes' as number to 2 (0x2)

Rebooted.... But system log is the same ... only "key down" messages
Dec 16 21:33:44 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key 3d=63 down
F3
Dec 16 21:33:47 MacBook-Pro-Denis kernel[0]: ApplePS2Keyboard: sending key e008=80 down
Fn+F3
Click to expand...

Of course... why would you expect to get both keydown and keyup messages for keys which are breakless?

The entire point of this is to determine which keys do not send break codes.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top