Contribute
Register

Acer Aspire E5-571-30AB installation problems

Status
Not open for further replies.
Of course I can see them, but I thought that it was necessary to see different states really selected (between braces), and this appears only for states 8 and 17. Other states seem to nether been selected (I've made several tests with various CPU loads).
I may have misunderstood and that's really good news if my stepping works fine !

The other states were being used. If they weren't, they would not be in the list.
 
My laptop works pretty fine now and I should be able to write a guide shortly.

I'm just having these 2 minor bugs :

1/ Loosing touchpad after sleep. This is not systematic, but most of time the touchpad won't work after sleep/wake. Same result whether I inject VoodooPS2Controller.kext via Clover, or if I install it into S/L/E. I use Rehabman's version and I strictly followed the guide here : https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Install.
By the way, the "VoodooPS2daemon" is only usefull if I wan't to disconnect touchpad when I connect an USB mouse ? I've got it installed but I don't use this setting.
With kextstat, I've noticed that VoodooPS2Mouse gets unloaded after a while, but this doesn't seem to be related to touchpad malfunction.

2/ Clover theme won't load every time. This is also aleatory. I've installed only 1 theme. Sometimes clover will load with default theme only. I don't see the reason why.

I would like to solve these minor things before writing a full guide.
 
My laptop works pretty fine now and I should be able to write a guide shortly.

I'm just having these 2 minor bugs :

1/ Loosing touchpad after sleep. This is not systematic, but most of time the touchpad won't work after sleep/wake. Same result whether I inject VoodooPS2Controller.kext via Clover, or if I install it into S/L/E. I use Rehabman's version and I strictly followed the guide here : https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Install.
By the way, the "VoodooPS2daemon" is only usefull if I wan't to disconnect touchpad when I connect an USB mouse ? I've got it installed but I don't use this setting.
With kextstat, I've noticed that VoodooPS2Mouse gets unloaded after a while, but this doesn't seem to be related to touchpad malfunction.

Post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.


2/ Clover theme won't load every time. This is also aleatory. I've installed only 1 theme. Sometimes clover will load with default theme only. I don't see the reason why.

What version of Clover? Did you check your Clover log?
 
Here is my ioreg export :
View attachment 146065

Your PS2 drivers might not be up-to-date. Make sure kextstat shows 1.8.15.

But your trackpad is Synaptics.

Post ioreg when trackpad is not working. Also, you might check system.log to see if there are any related errors.

It might be other DSDT related problems...

Note: All kexts should be installed to /S/L/E.
 
Your PS2 drivers might not be up-to-date. Make sure kextstat shows 1.8.15.
Yes it is.

Post ioreg when trackpad is not working. Also, you might check system.log to see if there are any related errors.
Here it is :
View attachment TouchPad Not Working.zip

And system.log errors when touchpad doesn't load :
Aug 5 20:24:03 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (aa) from PS/2 controller
Aug 5 20:24:03 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller

On boot, this is what it shows in system.log :
Aug 5 20:15:23 localhost kernel[0]: VoodooPS2SynapticsTouchPad Version 1.8.15 loaded...
Aug 5 20:15:23 localhost kernel[0]: VoodooPS2Mouse Version 1.8.15 loaded...
Aug 5 20:15:23 localhost kernel[0]: VoodooPS2Trackpad starting: Synaptics TouchPad reports type 0x47, version 8.1



Note: All kexts should be installed to /S/L/E.
VoodooPS2 is installed in S/L/E. For the moment I'm keeping FakeSMC and FakePCIID and 2 others in Clover injection. Could this have an incidence on touchpad loading ?
 
Yes it is.


Here it is :
View attachment 146080

And system.log errors when touchpad doesn't load :
Aug 5 20:24:03 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (aa) from PS/2 controller
Aug 5 20:24:03 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller

Trackpad driver is still loaded in the ioreg. Not sure why you say "when touchpad doesn't load"... it has to load in order to output those messages to the log.

Sounds like it is not initializing correct after sleep.

More information about the logs would be needed. Try installing the debug version.

VoodooPS2 is installed in S/L/E. For the moment I'm keeping FakeSMC and FakePCIID and 2 others in Clover injection. Could this have an incidence on touchpad loading ?

All kexts should be installed for /S/L/E. Kext injection is only for installing and recovery.
 
Trackpad driver is still loaded in the ioreg. Not sure why you say "when touchpad doesn't load"... it has to load in order to output those messages to the log.

Sounds like it is not initializing correct after sleep.
You're right. It does load but fails initializing after sleep.

More information about the logs would be needed. Try installing the debug version.
Here is debug log when touchpad doesn't initialize after sleep :
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 1
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 47
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 44
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 2
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 74
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: initial commandByte = 47
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: new commandByte = 44
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 1
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: VoodooPS2Trackpad: sending final init sequence...
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 2
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 47
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key 1c=24 up
Aug 5 21:20:26 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (aa) from PS/2 controller
Aug 5 21:20:26 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
Aug 5 21:20:42 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:20:42 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up
Aug 5 21:20:43 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:20:43 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up
Aug 5 21:20:45 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:20:45 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up


And this is debug log when touchpad initializes fine after sleep :
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 1
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 47
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 44
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 2
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 74
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: initial commandByte = 47
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: new commandByte = 44
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 1
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: VoodooPS2Trackpad: sending final init sequence...
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 2
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 47
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key 1c=24 up
Aug 5 21:29:22 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:29:22 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up



Here is complete log file for testing sequence corresponding to : 1st boot (21:17:32), sleep (21:19:02), wake (21:20:23), 2nd sleep (21:24:04), wake (21:25:26)
2nd boot (21:27:49), sleep (21:28:39), wake (21:29:19)
View attachment VoodooPS2debug.log.zip
In this sequence, touchpad is lost after first 2 sleeps, and works fine after third sleep.

All kexts should be installed for /S/L/E. Kext injection is only for installing and recovery.
I'm planning to do that once all issues are solved.
 
You're right. It does load but fails initializing after sleep.


Here is debug log when touchpad doesn't initialize after sleep :
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 1
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 47
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 44
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 2
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:19:02 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 74
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: initial commandByte = 47
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: new commandByte = 44
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 1
Aug 5 21:20:23 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: VoodooPS2Trackpad: sending final init sequence...
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 2
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 47
Aug 5 21:20:24 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key 1c=24 up
Aug 5 21:20:26 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (aa) from PS/2 controller
Aug 5 21:20:26 MacBook-Pro-de-Pat kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
Aug 5 21:20:42 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:20:42 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up
Aug 5 21:20:43 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:20:43 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up
Aug 5 21:20:45 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:20:45 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up


And this is debug log when touchpad initializes fine after sleep :
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 1
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 47
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 44
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for sleep 2
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:28:39 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 74
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: initial commandByte = 47
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: new commandByte = 44
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 1
Aug 5 21:29:19 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: VoodooPS2Trackpad: sending final init sequence...
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: setCommandByte for wake 2
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: oldCommandByte = 44
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Controller: newCommandByte = 47
Aug 5 21:29:20 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key 1c=24 up
Aug 5 21:29:22 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e down
Aug 5 21:29:22 MacBook-Pro-de-Pat kernel[0]: ApplePS2Keyboard: sending key e048=7e up



Here is complete log file for testing sequence corresponding to : 1st boot (21:17:32), sleep (21:19:02), wake (21:20:23), 2nd sleep (21:24:04), wake (21:25:26)
2nd boot (21:27:49), sleep (21:28:39), wake (21:29:19)
View attachment 146091
In this sequence, touchpad is lost after first 2 sleeps, and works fine after third sleep.


I'm planning to do that once all issues are solved.

Try changing the WakeDelay to something else than the default.
 
I've made various WakeDelay changes. That seems to work ! I had to set a quite long delay (2500), even 2000 was not enough.

I'm keeping this in observation to be sure, but I think it's ok.

Thank you so much RehabMan for your help and the time spent on this forum.

The only thing which doesn't work on my hackintosh is the card reader. It is a PCI one and I think there is no way to get it work. This is not important for me, and can be replaced by an USB reader for those who really need it.

One last thing : can you tell me if VoodooPS2Daemon is really necessary and what is it for ? I don't like adding daemons running without knowing why.
 
Status
Not open for further replies.
Back
Top