Contribute
Register

New VoodooPS2Controller, Keyboard, Trackpad

Status
Not open for further replies.
RehabMan said:
I think 'log' is generally very broken in Sierra. Apple fixed most of the problems with it in High Sierra.



It has this:
Code: 
2018-05-06 09:35:55.060771-0400  localhost kernel[0]: (VoodooPS2Trackpad) VoodooPS2SynapticsTouchPad: Version 1.8.32 starting on OS X Darwin 16.7.
2018-05-06 09:35:55.223748-0400  localhost kernel[0]: (VoodooPS2Trackpad) VoodooPS2Trackpad: Identify TouchPad command returned incorrect byte 2 (of 3): 0x00

Which, if this time "2018-05-06 09:35:55.060771-0400" represents a boot you had SSDT-DisableTrackpadProbe.aml active, .. indicates it is not working.
Click to expand...

I suspected that it wasn't working. I tried your SSDT-DisableTrackpadProbe.aml on my Thinkpad laptop. With the SSDT in CLOVER/ACPI/patched, the trackpad still worked (nothing was disabled), so it didn't work there either. Attached is a fresh set of debug files for my DIY Desktop that include my_kernel_log.txt. If this helps you to diagnose a problem with your SSDT, I'll keep testing. If this is a problem unique to my system, we don't need to fix this.
 

Attachments

  • debug_w_kernel_log.zip
    1.1 MB · Views: 89
deeveedee said:
I suspected that it wasn't working. I tried your SSDT-DisableTrackpadProbe.aml on my Thinkpad laptop. With the SSDT in CLOVER/ACPI/patched, the trackpad still worked (nothing was disabled), so it didn't work there either. Attached is a fresh set of debug files for my DIY Desktop that include my_kernel_log.txt. If this helps you to diagnose a problem with your SSDT, I'll keep testing. If this is a problem unique to my system, we don't need to fix this.
Click to expand...

Read post #2051.

Note: With SSDT-DisableTrackpadProbe.aml, your Thinkpad trackpad will still work, but as a mouse (ioreg will show ApplePS2Mouse).
 

Attachments

  • debug_PS2_v1.8.34.zip
    1.1 MB · Views: 101
deeveedee said:
It seems to be working. Now, I'm able to relax the vps2_findmousedelay to 425 (which, according to my strange logic, means that 1.8.34 and the SSDT are working). The fresh debug files are attached.
Click to expand...

I don't think this kernel log (my_kernel_log.txt) represents your current configuration.

But yes, DisableDevice for Synaptics should now be working as originally intended.
 
Last edited:
RehabMan said:
I don't think this kernel log (my_kernel_log.txt) represents your current configuration.
Click to expand...

I captured the kernel log after rebooting with VoodooPS2Controller.kext 1.8.34 installed. Note that the log indicates 1.8.34. I don't know how to capture anything more current, so if you want me to collect anything else, let me know.
 
deeveedee said:
I captured the kernel log after rebooting with VoodooPS2Controller.kext 1.8.34 installed. Note that the log indicates 1.8.34. I don't know how to capture anything more current, so if you want me to collect anything else, let me know.
Click to expand...

False alarm.

The line:
VoodooPS2SynapticsTouchPad: Version 1.8.34 starting on OS X Darwin 16.7.

Is output from init, which runs prior to probe.
It is a bit of a false message, because of course the driver does not start until start is called, and start will not be called because probe will fail.

We can tell that probe returned early without actually querying the PS2 mouse, since if it had we would have seen either:
"VoodooPS2Trackpad: Identify TouchPad command failed"
OR
"VoodooPS2Trackpad: Identify bytes = { ..."
"VoodooPS2Trackpad: Identify TouchPad command returned incorrect byte 2 (of 3):..."

But neither is present in your log.

I will consider this issue solved:
- default changed to 100ms
- DisableDevice for Synaptics is fixed
- example SSDT-DisableTrackpadProbe.dsl added to project
 
RehabMan said:
I will consider this issue solved:
- default changed to 100ms
- DisableDevice for Synaptics is fixed
- example SSDT-DisableTrackpadProbe.dsl added to project
Click to expand...

Glad I could help. You've been incredibly helpful to me - thanks!
 
@RehabMan - I am going to be switching the keyboard on my DIY Desktop from PS2 to USB. When I get the new USB keyboard (and have only a PS2 mouse connected to my system), would my system benefit from a SSDT-DisableKeyboardProbe.aml in a manner similar to your SSDT-DisableTrackpadProbe.aml?

Note - I don't yet have the keyboard, so I don't have any new debug files to share. My latest debug files (with the PS2 keyboard) are still attached to post #2054.

Thanks.
 
deeveedee said:
@RehabMan - I am going to be switching the keyboard on my DIY Desktop from PS2 to USB. When I get the new USB keyboard (and have only a PS2 mouse connected to my system), would my system benefit from a SSDT-DisableKeyboardProbe.aml in a manner similar to your SSDT-DisableTrackpadProbe.aml?

Note - I don't yet have the keyboard, so I don't have any new debug files to share. My latest debug files (with the PS2 keyboard) are still attached to post #2054.

Thanks.
Click to expand...

It would need to be all-on-one...
As in SSDT-DisableAllProbeExceptMouse.dsl:
Code: 
DefinitionBlock("", "SSDT", 2, "hack", "ps2", 0)
{
    Name(_SB.PCI0.LPCB.PS2K.RMCF, Package()
    {
        "Keyboard", Package()
        {
            "DisableDevice", ">y",
        },
        "Synaptics TouchPad", Package()
        {
            "DisableDevice", ">y",
        },
        "ALPS GlidePoint", Package()
        {
            "DisableDevice", ">y",
        },
        "Sentelic FSP", Package()
        {
            "DisableDevice", ">y",
        },
    })
}
//EOF
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top