Unresponsive Keyboard and Trackpad problem FIXED/RESOLVED

I've been dealing with this issue since early December myself.
I purchased the MBP in November and had nearly a month with out any issues.

I spent nearly two hours on the phone with Apple Care via a specialist trying to diagnose the problem yesterday.
He did mention that they believe neither the 10.5.1 update or the MBP 1.1 update were to blame for occurrence of this issue. (I remain slightly skeptical)

Let me give you a short rundown of my problems and what I've done to help resolve the issue. Hopefully it'll help some of you.. or help me (with some of everyone else insight) if it happens again.

The symptoms:
keyboard and trackpad become unresponsive.
The problem is intermittent but often is completely unresponsive at start up.
USB mouse and keyboards have full functionality.

Kernel panics often occur as well. Usually this occurs just after the keyboard and track pad experience extreme intermittent "on and off" periods.
The only option is to do a hard-restart which my or may not resolve the unresponsiveness.

Things I've addressed in my particular case:

1. The battery recall issue - my battery (6N745288YFTA) is OK.
2. Resetting the PMU - no change.
3. Re-installing both the 10.5.1 and MBP 1.1 updates - no effect.
4. pressing the Function + S key at start up and running /sbin/fsck -fy The HD is said to be OK
5. I just finished an Archive and reinstall of Leopard = this seems to have fixed the issue for the moment. I have not run the Updater to bring the OS back to it's fully updated form yet.


The Archive and Re-install DID NOT WORK.
Even upon downloading and installing the 10.5.1 and 1.1 update, I'm still back at square one.

I've also been experiencing these phantom keystrokes to the eject key and backlight myself lately.

I've resolved to wait for the 10.5.2 official release to see of that helps... If not then I'll break down and send my machine in for service.

_____________________________________
Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B05
SMC Version: 1.16f10
Sudden Motion Sensor:
State: Enabled

THE SOLUTION:

This is a HARDWARE problem!

After playing around with removing the battery and noticing that this often returned functionality to the keyboard I surmised that this had some sort of physical aspect.
Sure enough, there is a section of copper colored tape/wiring exposed in the batter slot that is slightly bowed where it's smallest.
When I depressed this with my finger tip on this portion to basically flatten it out flush against the housing; I found that all functionality was restored!

You can see the portion in the picture below.

User uploaded file

I haven’t had any problems AT ALL since I took a piece of napkin and taped it down to sustain pressure on this portion of bowed tape/wiring.


I have yet to call AppleCare to see what they suggest I do.
I will post a reply here when I hear their suggestion.

Mac Book Pro, Mac OS X (10.5.1), 2.4 GHz Intel Core 2 Duo, 2 GB 667 MHz SDRAM

Posted on Jan 27, 2008 3:18 PM

Reply
382 replies

Aug 19, 2011 11:17 PM in response to slexus

ok, finally something in the logs:


20.08.11 9:09:00 Notice login[779] USER_PROCESS: 779 ttys000

20.08.11 9:09:28 Notice /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[683] No valid tickets, timing out

20.08.11 9:12:56 Debug kernel USBF: 51370.286 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:02 Debug kernel USBF: 51376.287 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:08 Debug kernel USBF: 51382.288 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:14 Debug kernel USBF: 51388.288 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:20 Debug kernel USBF: 51394.289 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:26 Debug kernel USBF: 51400.289 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:32 Debug kernel USBF: 51406.290 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:38 Debug kernel USBF: 51412.290 AppleUSBUHCI[0x844b000]::Found a transaction which hasn't moved in 5 seconds on bus 0x5d, timing out! (Addr: 3, EP: 0)

20.08.11 9:13:38 Debug kernel USBF: 51412.549 [0x858e000] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x5d000000)

20.08.11 9:13:53 Debug kernel Apple Internal Keyboard / Trackpad::terminate(kIOServiceSynchronous) timeout

20.08.11 9:13:56 Debug kernel USBF: 51430.691 [0x858e000] The IOUSBFamily was not able to enumerate a device.


this off a fresh restart, couple of minutes after logging in and using my external USB keyboard.


it actually seems that internals will stay in working condition, *unless* i connect an external USB device to the bus.

Aug 20, 2011 5:22 AM in response to slexus

slexus wrote:


User uploaded file

ok took the memory chip cover 4 screws out and am now running on a easy-access topcase. noticed that's also where my ribbon cable runs with the bend and everything. this allows me to start applying pressure instantly after internal disconnection happens next time.


Remember, for some it's adding pressure, for others it's relieving pressure, and for all, that cable is rather delicate . . . .

Aug 20, 2011 6:50 AM in response to tjk

tjk wrote:


Remember, for some it's adding pressure, for others it's relieving pressure, and for all, that cable is rather delicate . . . .

right. well fiddling with the cable in all sorts of directions didnt do anything. then i just un- and replugged the connector in the the motherboard. instant reconnection and functionality again. so i guess it's safe to say the cable is somehow hosed. i just hope it isn't motherboard itself. time to go hunting for spare ribbon.

Aug 20, 2011 7:10 AM in response to slexus

slexus wrote:


tjk wrote:


Remember, for some it's adding pressure, for others it's relieving pressure, and for all, that cable is rather delicate . . . .

right. well fiddling with the cable in all sorts of directions didnt do anything. then i just un- and replugged the connector in the the motherboard. instant reconnection and functionality again. so i guess it's safe to say the cable is somehow hosed. i just hope it isn't motherboard itself. time to go hunting for spare ribbon.


And I had forgotten, but for some people simply securing the connection was all it took. Did you notice if it seemed fully seated when you disconnected it?

Aug 20, 2011 7:30 AM in response to tjk

tjk wrote:



And I had forgotten, but for some people simply securing the connection was all it took. Did you notice if it seemed fully seated when you disconnected it?

while it's a rather flimsy connector, it's sitting there just about as snug as it's going to ever get. the piece of yellow electric tape doesn't fasten it anymore, but i find it difficult to believe it has any actual real effect. electronics can't exactly make a "half way connection" for as long as these input devices do when they are working. either it's on or it's off.


i took a macro look at the cable itself, not liking the horizontal wearish looking spot visible on the bend part:


User uploaded file

yep bending it or straightening it while connected didnt exhibit a reacion of any kind. yet my previous experience of some kind of a upper topcase part pressure causing reconnects seems to correlate with the position of this bend.


i guess trying a working spare part is the only as close to concrete answer as there's going to be.

Aug 25, 2011 10:03 PM in response to slexus

Hi again everyone,


Please refer to my earlier post. It's just a matter of purchasing the cable. If you aren't comfortable installing it yourself and I have to admit it took about an hour, then just take the computer and cable to any computer repair shop and I'm sure they could do it for under a hundred dollars.


When I get a chance I'll post some installation photos on my career coaching website http://actiontraction.com.au/


Cheers,

Adrian

Aug 31, 2011 11:03 AM in response to slexus

slexus,


I've just called pbparts.com on your behalf, because they had provided me such a pleasant experience.


The cable you need for an a1229 is http://www.pbparts.com/shop.php//%5E9229018 - to make sure, before you order it, in very small print on your existing cable, the rep at pbparts told me you need to look for the following numbers:

821-0515 / 632-0528


There are also other numbers, if you visit the link above, in invisible print (for the search engines), if you "select all" on that page, they should be visible to you.


They have ONE in stock at the moment if you want it!


Good luck!

Oct 1, 2011 8:09 AM in response to ImCanadianEh

thanks for the help. in the meanwhile i've received a spare part off ebay for $30ish incl worldwide shipping. there is no apparent wear spot in the bend like demonstrated in my photo a few messages back. installed it today, but there seems to be no apparent change in the broken behavior. i left the machine alone for a few hours, only for the internal input devices to be dead again when i came back. not a **** thing in dmesg again. looks like the only thing that can pick up this event is HardwareGrowler and i've now set it to use MailMe plugin for USB disconnections.


while i was working on setting that up off a fresh cold boot (warm reboot wouldn't wake up the built-in input devices), i saw a disconnect/connect cycle take place. when and on what conditions it can reconnect itself, i have no clue so far.

Oct 1, 2011 8:29 AM in response to slexus

Spare part? As in, used, might not work, came out of another machine?


Or new, sealed, never used?


I've turned off notifications for this discussion...good luck! If it's not the ribbon cable, could be the rest of the top case assembly...not one person has shown me a permanent fix that was software or firmware related - I think you're going to be banging your head against this machine for a very long time if that's how you're approaching the problem

...again, good luck...

Dec 2, 2011 5:31 AM in response to alexandrafromhills

I just used masking tape but Imust warn you its back to acting up again. I am gonna try and rig it up agai nwith some elctrical tape and clean off the tips of the wires connected to that little MINI board or whatever its called. It was working great for a few weeks but now as once again stopped responding 😢

I will let you know how I get one but I reccomend using electrical tape to "press" down on the ribbon cables as per the original discussion.

Hope it works for you!

Cheers,

Nathan

Jan 17, 2012 3:21 PM in response to Steve Eugene

Well, 3 years later this post has saved another one! My macbook pro's keyboard and mouse slowly started to quit... after a few reboots they stopped completely. So, I took it into the apple store to the genius', lol, and they told me that it needed a topcase for about 300 bucks ooooor I could buy a new one for 2500 bucks. That's a lot to spend on a 3 year old laptop and I'm not ready to drop the cash for a new one!! But with a little help from google, and some creative googling, I used the napkin trick and it works great again!


Thanks!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Unresponsive Keyboard and Trackpad problem FIXED/RESOLVED

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.