Contribute
Register

New VoodooPS2Controller, Keyboard, Trackpad

Status
Not open for further replies.
RehabMan said:
Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Click to expand...

Currently the situation gone worse: touchpad doesn't work from the very start-up. PrefPane looks for a BT device, just as it had been doing before the fresh reinstall.
P.S.: ioreg might be also showing my mouse connected by a USB dongle.

Code: 
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext Lilu.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Broadcom_WiFi.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext PinConfigs.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 8CFEED8DC3627BA3C3C10EF08F3D04C8

output from kernel log:
Code: 
2017-06-29 12:43:53.103847+0300 0x115      Default     0x0                  0      kernel: (kernel) VoodooPS2SynapticsTouchPad: Version 1.8.26 starting on OS X Darwin 16.6.
2017-06-29 12:43:53.333294+0300 0x115      Default     0x0                  0      kernel: (kernel) VoodooPS2Trackpad: Identify TouchPad command failed
2017-06-29 12:43:53.620866+0300 0x115      Default     0x0                  0      kernel: (kernel) VoodooPS2Mouse: Version 1.8.26 starting on OS X Darwin 16.6.
 

Attachments

  • Archive.zip
    1.7 MB · Views: 86
AirAlarm said:
Currently the situation gone worse: touchpad doesn't work from the very start-up. PrefPane looks for a BT device, just as it had been doing before the fresh reinstall.
P.S.: ioreg might be also showing my mouse connected by a USB dongle.

Code: 
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext Lilu.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Broadcom_WiFi.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext PinConfigs.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 8CFEED8DC3627BA3C3C10EF08F3D04C8

output from kernel log:
Code: 
2017-06-29 12:43:53.103847+0300 0x115      Default     0x0                  0      kernel: (kernel) VoodooPS2SynapticsTouchPad: Version 1.8.26 starting on OS X Darwin 16.6.
2017-06-29 12:43:53.333294+0300 0x115      Default     0x0                  0      kernel: (kernel) VoodooPS2Trackpad: Identify TouchPad command failed
2017-06-29 12:43:53.620866+0300 0x115      Default     0x0                  0      kernel: (kernel) VoodooPS2Mouse: Version 1.8.26 starting on OS X Darwin 16.6.
Click to expand...

Your trackpad is not being detected.
Do EC reset.

You forgot to press F4 to collect ACPI/origin files. As a result, no further advice possible. Read FAQ, "Problem Reporting" again. Carefully this time.
 
AirAlarm said:
Sorry!
Click to expand...

Your ACPI/patched files are not in sync with ACPI/origin.
As per ACPI patching guide, you must re-extract/re-patch after any BIOS option change, BIOS upgrade, or hardware change.
 
RehabMan said:
Your ACPI/patched files are not in sync with ACPI/origin.
As per ACPI patching guide, you must re-extract/re-patch after any BIOS option change, BIOS upgrade, or hardware change.
Click to expand...

Is it possible that files could gone out-of-sync by themselves? I literally didn't do any of those steps (BIOS option change/BOOS upgrade/hardware change).
 
AirAlarm said:
Is it possible that files could gone out-of-sync by themselves? I literally didn't do any of those steps (BIOS option change/BOOS upgrade/hardware change).
Click to expand...

ACPI/patched files are dated Jun 17,2017.
Today is Jun 29,2017.
Hard for you to prove you made no changes to BIOS or hardware in the intervening 12 days.
Half of the time, such differences are caused from people trying to use patched ACPI provided by other people...
 
RehabMan said:
ACPI/patched files are dated Jun 17,2017.
Today is Jun 29,2017.
Hard for you to prove you made no changes to BIOS or hardware in the intervening 12 days.
Half of the time, such differences are caused from people trying to use patched ACPI provided by other people...
Click to expand...

I did the patching right after fresh reinstall. No BIOS or hardware changes were included afterwards. Moreover, no ACPI files from other users were taken.
So yes, maybe it's easy to prove me wrong... But I see no point in misleading you by my words nor in providing false information.
 
AirAlarm said:
I did the patching right after fresh reinstall. No BIOS or hardware changes were included afterwards. Moreover, no ACPI files from other users were taken.
So yes, maybe it's easy to prove me wrong... But I see no point in misleading you by my words nor in providing false information.
Click to expand...

It does not really matter. The files are different (SystemMemory addresses do not match). You need to re-extract/re-patch.

You probably just forgot about what you changed...
 
RehabMan said:
It does not really matter. The files are different (SystemMemory addresses do not match). You need to re-extract/re-patch.

You probably just forgot about what you changed...
Click to expand...

Ok. Could you please check if the files are currently in sync?
Maybe I am lacking a Fix_Regions patch in my config.plist?
 

Attachments

  • Archive.zip
    1.8 MB · Views: 103
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top