HP Probook Installer Clover Edition

[dhpdhp]

Perhaps you neglected to re-patch ACPI after making the BIOS option change.

Perhaps I did, so to make sure everything's as supposed I've just tried it all again: back to 0x0a260006&32MB, re-patched DSDT and generated SSDT (this is the correct method, isn't it?):


Here's the result:View attachment dan's hp 840 g1 - DSDT&SSDT.zip

Unfortunately, the screen's getting constant glitches as I'm typing away this response after waking it up from sleep.

Strangely, this is what I've just found out:

Daniels-hpMBP:logs daniel$ pwd
/Users/daniel/Downloads/hp 840 g1/logs
Daniels-hpMBP:logs daniel$ md5 *.aml
MD5 (DSDT.aml) = fc1484e89fb442b3ccfa99d81d05d4a0
MD5 (SSDT-1.aml) = 932bc5f65c7e39202ecd382bfac1b30f
MD5 (SSDT.aml) = 97db2876cae47e7299b4281629878a92


Daniels-hpMBP:patched daniel$ pwd
/Volumes/EFI/EFI/CLOVER/ACPI/patched
Daniels-hpMBP:patched daniel$ md5 *.aml
MD5 (DSDT.aml) = fc1484e89fb442b3ccfa99d81d05d4a0
MD5 (SSDT-1.aml) = 97db2876cae47e7299b4281629878a92
MD5 (ssdt.aml) = 932bc5f65c7e39202ecd382bfac1b30f

SSDT and SSDT-1 seem to have changed places (the ones above have been extracted with patchmatic), also SSDT.aml installed by PBI-CE in EFI/CLOVER/ACPI/patched is lower-case. Is that anything to worry about?

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.

As requested: View attachment dan's hp 840 g1 - latest.ioreg.zip

Also:

md5 /usr/bin/VoodooPS2Daemon

Daniels-hpMBP:~ daniel$ sudo launchctl list | grep voo
Password:
44    0    org.rehabman.voodoo.driver.Daemon
Daniels-hpMBP:~ daniel$ md5 /usr/bin/VoodooPS2Daemon
MD5 (/usr/bin/VoodooPS2Daemon) = 11cfc64453afff1c0c55cb2b9a9f04f1
Daniels-hpMBP:~ daniel$ md5 ./Downloads/hp\ 840\ g1/RehabMan-Voodoo-2015-1101/Release/VoodooPS2Daemon 
MD5 (./Downloads/hp 840 g1/RehabMan-Voodoo-2015-1101/Release/VoodooPS2Daemon) = 11cfc64453afff1c0c55cb2b9a9f04f1
Daniels-hpMBP:~ daniel$

Make sure you have the option enabled in SysPrefs->Accessibility.

As requested:


It's already been like that since right after the installation of OS X, still no go.

 

[RehabMan]

Perhaps I did, so to make sure everything's as supposed I've just tried it all again: back to 0x0a260006&32MB, re-patched DSDT and generated SSDT (this is the correct method, isn't it?):
View attachment 161194

Assuming you pressed F4 in Clover to recapture native ACPI files prior...

SSDT and SSDT-1 seem to have changed places (the ones above have been extracted with patchmatic), also SSDT.aml installed by PBI-CE in EFI/CLOVER/ACPI/patched is lower-case. Is that anything to worry about?

You can check your Clover bootlog to see if the files are loading as you expect.

As requested: View attachment 161203

The ioreg shows MouseCount=0. It means either there is no detected USB mouse or VoodooPS2Daemon is not reporting it. You can use the debug VoodooPS2Daemon to get logs.

It could be your android software is interfering. It is hooking all USB devices for some reason. Remove it and see if anything changes.

 

[dhpdhp]

Assuming you pressed F4 in Clover to recapture native ACPI files prior...

I didn't (to be honest I didn't know I was supposed to, as the guide doesn't mention it) but I checked the dates and and some of the files in EFI/ACPI/origin were updated at the time of running PBI-CE, so I guess it's one of the things it does automatically.

I did it anyway, just to see if it helps, ALL files in EFI/ACPI/origin got updated (some actually changed - checked with md5), their number doubled, too. So I re-patched the ACPI, but the effect is the same - my screen's still getting constant glitches as I'm typing this after waking it up from sleep.

Unless there's a particular reason to not use 0x0a160000 (@512MB), I guess I'll just stick to that. Or do you think I should still try out anything else?

You can check your Clover bootlog to see if the files are loading as you expect.

I shall do that in a moment.

The ioreg shows MouseCount=0. It means either there is no detected USB mouse or VoodooPS2Daemon is not reporting it. You can use the debug VoodooPS2Daemon to get logs.

It could be your android software is interfering. It is hooking all USB devices for some reason. Remove it and see if anything changes.

Android software removed, your kext reinstalled (please see below), unfortunately - no change in behaviour.

Daniels-hpMBP:~ daniel$ kextstat | grep voo
   37    3 0xffffff7f80faa000 0xe000     0xe000     org.rehabman.voodoo.driver.PS2Controller (1.8.18) 72CC0569-7EAF-318A-AFD4-88F0E3B79B37 <11 7 5 4 3 1>
   60    0 0xffffff7f80fce000 0x6000     0x6000     org.rehabman.voodoo.driver.PS2Keyboard (1.8.18) 33462A66-68FF-37C2-B0AF-745A2AC1082A <37 34 7 6 5 4 3 1>
   61    0 0xffffff7f80fb8000 0xc000     0xc000     org.rehabman.voodoo.driver.PS2Trackpad (1.8.18) 59C17AD2-4631-30DC-BEFC-C22E3F762859 <37 34 7 6 5 4 3 1>
   62    0 0xffffff7f80fc8000 0x4000     0x4000     org.rehabman.voodoo.driver.PS2Mouse (1.8.18) 59B987E1-378F-3775-A106-3D579FEE7196 <37 34 5 4 3>
Daniels-hpMBP:~ daniel$ md5 /usr/bin/VoodooPS2Daemon
MD5 (/usr/bin/VoodooPS2Daemon) = 11cfc64453afff1c0c55cb2b9a9f04f1
Daniels-hpMBP:~ daniel$ md5 ./Downloads/hp\ 840\ g1/RehabMan-Voodoo-2015-1101/Release/VoodooPS2Daemon 
MD5 (./Downloads/hp 840 g1/RehabMan-Voodoo-2015-1101/Release/VoodooPS2Daemon) = 11cfc64453afff1c0c55cb2b9a9f04f1
Daniels-hpMBP:~ daniel$ sudo launchctl list | grep voo
Password:
44    0    org.rehabman.voodoo.driver.Daemon

It's a Logitech wireless mouse with a Logitech USB unifying receiver, and the system surely detects it as a mouse, since the window scroll bars are only visible with the receiver plugged in:
No receiver:
With the receiver:

Just in case - here's the ioreg saved again with the receiver plugged in (I'm not 100% sure it was when I saved the previous one): View attachment dan's hp 840 g1 - latest with receiver.ioreg.zip

My suspicion is that the OS either doesn't see the trackpad as a trackpad, but as a mouse (yet, the above scroll bar behaviour defies that logic, doesn't it?), or it doesn't see the trackpad as an internal one, thus doesn't ignore it as told in the settings. I'll check ioreg from both my 1201n (where the feature works) and a MacBook and get back to you about that.

 

[dhpdhp]

Surprise, surprise! With the mouse plugged in and the touchpad working here's what System Preferences had to say about the touchpad:

 

[RehabMan]

I didn't (to be honest I didn't know I was supposed to, as the guide doesn't mention it) but I checked the dates and and some of the files in EFI/ACPI/origin were updated at the time of running PBI-CE, so I guess it's one of the things it does automatically.

Not automatic. Clearly in guide:

Repatch DSDT

Download the required files

1. Boot to Clover from USB or HDD, press F4 at Clover screen.
...

Unless there's a particular reason to not use 0x0a160000 (@512MB), I guess I'll just stick to that. Or do you think I should still try out anything else?

Do what you like. No more ideas for you.

It's a Logitech wireless mouse with a Logitech USB unifying receiver, and the system surely detects it as a mouse, since the window scroll bars are only visible with the receiver plugged in:

You will need to use the debug VoodooPS2Daemon to gather further information/logs.

The ioreg shows MouseCount at zero, so either the daemon isn't running, or it isn't getting notified properly of USB plug/unplug events.

Scrollbar detection is done by the system. My kext is not using the same data (not sure where it is). Hence VoodooPS2Daemon.

Just in case - here's the ioreg saved again with the receiver plugged in (I'm not 100% sure it was when I saved the previous one): View attachment 161226

And when I look at your ioreg, I see no related pointing device under EHC1 or XHC nodes. There is a pointing device under AppleUSBLegacyRoot, which may be part of the problem. VoodooPS2Daemon doesn't look there for pointing devices... only to determine if one found under the main node is removable or not.

 

[RehabMan]

Surprise, surprise! With the mouse plugged in and the touchpad working here's what System Preferences had to say about the touchpad:
View attachment 161232

Yes... it is looking at different data. I'm not sure where it is looking ... if I did, I'd would have never written VoodooPS2Daemon. But.. I'm glad I did because OS X believes there is a USB mouse plugged in if you have a touch screen (even if it is non-removable), so it is a good thing I'm not using their data.

 

[RehabMan]

And when I look at your ioreg, I see no related pointing device under EHC1 or XHC nodes. There is a pointing device under AppleUSBLegacyRoot, which may be part of the problem. VoodooPS2Daemon doesn't look there for pointing devices... only to determine if one found under the main node is removable or not.

@dhpdhp

Try current build... 1.8.19.

 

[dhpdhp]

@dhpdhp

Try current build... 1.8.19.

You are awesome!!! It's working perfectly now Thanks!

Also, double tap in the top left corner works as well to turn it back on (or off) without having to change any settings in Accessibility, or unplugging the mouse.

 

[RehabMan]

...
Also, double tap in the top left corner works as well to turn it back on (or off) without having to change any settings in Accessibility, or unplugging the mouse.

Yes. I implemented that feature long ago...

 

[dhpdhp]

Yes. I implemented that feature long ago...

Thanks!