Contribute
Register

Guide to Installing Mavericks on HP Probook

cahedger said:
...
kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0data (8e) from PS/2 controller
Click to expand...


It means your trackpad is resetting itself.

See if a sleep/wake cycle fixes it...
 
You mean putting it to sleep and waking it or the ec reset? Because I've done both and neither solves the problem... sorry I tried googling "sleep/wake cycle" and it all looks like methods I've tried already. The computer actually sleeps fine now... it will wake to a keystroke or if in deep sleep by tapping the power button. The time it crashes is completely at random, it could be when I'm 20-30 tracks deep into recording a song, or 15 minutes after I boot up while I'm browsing my hard drive.
 
cahedger said:
You mean putting it to sleep and waking it or the ec reset? Because I've done both and neither solves the problem... sorry I tried googling "sleep/wake cycle" and it all looks like methods I've tried already. The computer actually sleeps just fine now... it will wake to a keystroke or if in deep sleep by tapping the power button.
Click to expand...

A sleep/wake cycle will re-initialize your trackpad.
 
Ah, I gotcha... ya I'll try and do that and see if it fixes all those millions of ps2 errors I get. The trackpad works amazing, and the 2 finger gesture feature makes navigation really easy (I felt really dumb not knowing about that one). I don't know if this is going to fix the random crashing but at least it will hopefully clear out the logs so I can see what's going on.
 
I think I figured out what that ps2 error was... so I followed your suggestion and did the sleep wake cycle (I let it go into a deep sleep so I had to hit power to wake). That definitely took care of it... I cleared the logs and hit reload and let it sit for a few minutes... no errors. Then I touched the Point Stick (you know, the eraser nub looking thing in the middle of the keyboard)... and sure enough, it started spewing those error codes. So my guess is that is loading so many errors onto my system that it causes it to crash (esp since I run intensive programs and only have 4GB or RAM). Any suggestions, theories, contemplations? I'm gonna try and see if I can disable this feature in bios, if not I'll see about just unplugging it when I change my wifi card out. Sorry, I'm a persistent SOB.
 
cahedger said:
I think I figured out what that ps2 error was... so I followed your suggestion and did the sleep wake cycle (I let it go into a deep sleep so I had to hit power to wake). That definitely took care of it... I cleared the logs and hit reload and let it sit for a few minutes... no errors. Then I touched the Point Stick (you know, the eraser nub looking thing in the middle of the keyboard)... and sure enough, it started spewing those error codes. So my guess is that is loading so many errors onto my system that it causes it to crash (esp since I run intensive programs and only have 4GB or RAM). Any suggestions, theories, contemplations? I'm gonna try and see if I can disable this feature in bios, if not I'll see about just unplugging it when I change my wifi card out. Sorry, I'm a persistent SOB.
Click to expand...

The nub isn't supported, so it would be expected it would cause errors.
 
Ya I figured as much, though some of your updates in the other threads made it seem like you were trying to program a kext to support this (or 86 it altogether). Either way, I had no need for the nub nub... so I just decided to pop out the keyboard, disconnect the nub connector and tape it off... seems to work fine now (albeit a lil unorthodox). Hopefully this takes care of the crashing, I'll keep you posted (still waiting on that wifi card, sigh).
 
cahedger said:
Ya I figured as much, though some of your updates in the other threads made it seem like you were trying to program a kext to support this (or 86 it altogether). Either way, I had no need for the nub nub... so I just decided to pop out the keyboard, disconnect the nub connector and tape it off... seems to work fine now (albeit a lil unorthodox). Hopefully this takes care of the crashing, I'll keep you posted (still waiting on that wifi card, sigh).
Click to expand...

The kext supports some nubs (those that use the "passthrough" protocol). The Elitebooks use some other protocol -- could be the multiplex ps2 protocol [which would be a fair bit of work]).
 
Welp, I've been programming music all day and haven't had it crash once:) I think that disconnecting the pointer fixed it (I use the keyboard to play music, so I've probably been accidentally bumping that pointer and crashing it). Just installed that broadcom wifi card, booted up, and so far no problems (typing this from my "hackbook" as we speak). Didn't have to install anything, just worked like a boss. Thanks again for all your help, you guys are the best:clap:
 
hey guys i am new on here and i hope u can all help me :)
i have hp probook 4730s and i am tring to install yosemite, i did everything on that guide but when i boot with my usb the instaler starts to load and then just frezzes, the progress bar stops moving forward and i am just stuck with the apple logo and a progres bar. i can move the move tho.
any help would be welcome.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top