Steve Eugene

Q: 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.



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:21 PM

Close

Q: Unresponsive Keyboard and Trackpad problem FIXED/RESOLVED

  • All replies
  • Helpful answers

first Previous Page 20 of 26 last Next
  • by ImCanadianEh,

    ImCanadianEh ImCanadianEh Aug 17, 2011 2:09 PM in response to ImCanadianEh
    Level 1 (0 points)
    Aug 17, 2011 2:09 PM in response to ImCanadianEh

    Okay, so now that the install has been done and the computer is working, I figured I'd share that the result of the new ribbon cable was a SUCCESS!

     

    However, the install is not for the faint of heart or one with a shaky hand...you've got to be careful and have patience undoing the replacing the connectors and sticking the new cable in place.  If you're up to the task, the cable from http://www.pbparts.com/shop.php//%5E9228571 worked perfectly.

  • by slexus,

    slexus slexus Aug 18, 2011 3:07 AM in response to Steve Eugene
    Level 1 (0 points)
    Aug 18, 2011 3:07 AM in response to Steve Eugene

    so what do i do if my MacBookPro3,1 has a different ribbon cable layout? pressing on them doesn't do a thing. only a cold reboot restores functionality for an undetermined amount of time. only at one point in time have i managed to cause several reconnect-disconnects to happen when picking up the machine at a certain angle or whatnot. i have not been able to reproduce that no matter how much i've tried. it seemed to have happened from changing pressure to the top side of keyboard rather than the lower side where the ribbons are connected to.

     

    /___sbsstatic___/migration-images/159/15960343-1.jpg

    https://discussions.apple.com/message/15191433 is my debug log of this (yet another) heinous issue with this machine.

     

    what's different now in 10.6.8 compared to 10.6.7 is that these USB disconnection messages don't appear in system.log anymore. nice job again apple! i need to find out if dmesg has them right after it happens, but i doubt it, afaik dmesg is put into system.log. if i didnt have hardwaregrowler running i wouldnt even know when it happens.

  • by tjk,

    tjk tjk Aug 18, 2011 9:05 AM in response to slexus
    Level 7 (24,259 points)
    Mac OS X
    Aug 18, 2011 9:05 AM in response to slexus

    slexus wrote:

     

    what's different now in 10.6.8 compared to 10.6.7 is that these USB disconnection messages don't appear in system.log anymore.

     

    Hmmmm, isn't that interesting . . . .

  • by slexus,

    slexus slexus Aug 18, 2011 2:36 PM in response to tjk
    Level 1 (0 points)
    Aug 18, 2011 2:36 PM in response to tjk

    so tried re-seating the silver ribbon cable this morning. left the machine sitting there idling on its own for the day with working internal keyboard and trackpad.

     

    now it's midnight, numlock is lighted up, both internal keyboard and trackpad are dead. here's what's logged:

     

    lkraav@mobilitymac /var/log $ sudo grep Aug.\*USB *

    kernel.log:Aug  6 20:59:42 mobilitymac kernel[0]: USBMSC Identifier (non-unique): 251115006F695C06 0x204 0x6025 0x100

    kernel.log:Aug 14 18:10:34 mobilitymac kernel[0]: USBF: 1445369.930     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:19:33 mobilitymac kernel[0]: USBF: 1445908.942     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:20:02 mobilitymac kernel[0]: USBF: 1445937.942     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:20:08 mobilitymac kernel[0]: USBF: 1445943.942     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:20:18 mobilitymac kernel[0]: USBF: 1445953.943     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:21:17 mobilitymac kernel[0]: USBF: 1446012.944     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:21:22 mobilitymac kernel[0]: USBF: 1446018.944     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:21:34 mobilitymac kernel[0]: USBF: 1446029.944     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 14 18:26:18 mobilitymac kernel[0]: USBF: 1446313.951     AppleUSBEHCI[0x701c000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 3, EP: 0)

    kernel.log:Aug 16 22:18:05 mobilitymac kernel[0]: USBMSC Identifier (non-unique): 12345678901234567890 0x90c 0x6200 0x100

    kernel.log:Aug 16 22:19:46 mobilitymac kernel[0]: USBMSC Identifier (non-unique): 12345678901234567890 0x90c 0x6200 0x100

    kernel.log:Aug 16 22:29:12 mobilitymac kernel[0]: USBMSC Identifier (non-unique): 12345678901234567890 0x90c 0x6200 0x100

    kernel.log:Aug 16 22:29:41 mobilitymac kernel[0]: USBMSC Identifier (non-unique): 12345678901234567890 0x90c 0x6200 0x100

    kernel.log:Aug 16 22:36:50 mobilitymac kernel[0]: USBMSC Identifier (non-unique): 12345678901234567890 0x90c 0x6200 0x100

    kernel.log:Aug 17 00:41:22 mobilitymac kernel[0]: USBF: 1641615.915     AppleUSBEHCI[0x701c000]::SuspendUSBBus - port 4 was NOT already suspended (as it should have been) PROBLEMS AHEAD

    kernel.log:Aug 17 07:55:00 mobilitymac kernel[0]: The USB device Built-in iSight (Port 4 of Hub at 0xfd000000) may have caused a wake by being disconnected

    kernel.log:Aug 18 11:24:15 mobilitymac kernel[0]: USBF: 1712498.784     AppleUSBEHCI[0x701c000]::SuspendUSBBus - port 4 was NOT already suspended (as it should have been) PROBLEMS AHEAD

    kernel.log:Aug 18 11:29:54 mobilitymac kernel[0]: The USB device Built-in iSight (Port 4 of Hub at 0xfd000000) may have caused a wake by being disconnected

    kernel.log:Aug 18 12:01:20 mobilitymac kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0

    kernel.log:Aug 18 12:01:42 mobilitymac kernel[0]: Kext unloading is disabled (org.virtualbox.kext.VBoxUSB).

    kernel.log:Aug 18 12:03:05 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0

    system.log:Aug 18 12:01:27 mobilitymac com.apple.SystemStarter[50]: Loading VBoxUSB.kext

    system.log:Aug 18 12:01:41 mobilitymac SystemStarter[50]: VirtualBox Support and USB Drivers (248) did not complete successfully

    system.log:Aug 18 12:03:14 mobilitymac com.apple.SystemStarter[50]: Loading VBoxUSB.kext

    system.log:Aug 19 00:21:38 mobilitymac sudo[3075]: lkraav : TTY=ttys002 ; PWD=/private/var/log ; USER=root ; COMMAND=/opt/prefix/bin/grep --colour=auto Aug.*USB CDIS.custom DiagnosticMessages alf.log apache2 appfirewall.log appfirewall.log.0.bz2 appfirewall.log.1.bz2 asl cups daily.out fax fsck_hfs.log hdiejectd.log install.log install.log.0.bz2 install.log.1.bz2 ipfw.log kernel.log krb5kdc launchd-shutdown.log launchd-shutdown.log.1 mail.log monthly.out ppp sa samba secure.log securityproxy system.log system.log.0.bz2 system.log.1.bz2 system.log.2.bz2 system.log.3.bz2 system.log.4.bz2 system.log.5.bz2 system.log.6.bz2 system.log.7.bz2 uucp weekly.out windowserver.log windowserver_last.log

     

    USB errors on Aug 14 are from messing around with VirtualBox, which has issues of it's own in some versions. But no, uninstalling VirtualBox hasn't done a single thing to this problem, tried it. Boot time was around 12pm, as you can see from the "CSRUSBBluetoothHCIController::setupHardware" call, errors before that are from the VirtualBox residue.

     

    As we can see, not a single word for the whole month of August about "Hey dear user, few of your internal devices just died" in system logs. I mean, why would a user want to know about that? Let's see what dmesg has:

     

    lkraav@mobilitymac /var/log $ sudo dmesg

    npvhash=4095

    PAE enabled

    64 bit mode enabled

    Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386

    vm_page_bootstrap: 1021131 free pages and 19253 wired pages

    standard timeslicing quantum is 10000 us

    mig_table_max_displ = 73

    AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled

    AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled

    calling mpo_policy_init for Quarantine

    Security policy loaded: Quarantine policy (Quarantine)

    calling mpo_policy_init for Sandbox

    Security policy loaded: Seatbelt sandbox policy (Sandbox)

    calling mpo_policy_init for TMSafetyNet

    Security policy loaded: Safety net for Time Machine (TMSafetyNet)

    Copyright (c) 1982, 1986, 1989, 1991, 1993

            The Regents of the University of California. All rights reserved.

     

    MAC Framework successfully initialized

    using 16384 buffer headers and 4096 cluster IO buffer headers

    IOAPIC: Version 0x20 Vectors 64:87

    ACPI: System State [S0 S3 S4 S5] (S3)

    PFM64 0xf10000000, 0xf0000000

    [ PCI configuration begin ]

    console relocated to 0xf10030000

    PCI configuration changed (bridge=5 device=1 cardbus=0)

    [ PCI configuration end, bridges 7 devices 17 ]

    AppleIntelCPUPowerManagement: (built 16:44:45 Jun  7 2011) initialization complete

    mbinit: done (64 MB memory set for mbuf pool)

    FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe7b09a8; max speed s800.

    rooting via boot-uuid from /chosen: 446D3E9F-F836-3CE7-913B-BC797B4BCE98

    Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>

    com.apple.AppleFSCompressionTypeZlib kmod start

    com.apple.AppleFSCompressionTypeZlib load succeeded

    AppleIntelCPUPowerManagementClient: ready

    Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD river/C300-CTFDDAC064MAG Media/IOGUIDPartitionScheme/Untitled@2

    BSD root: disk0s2, major 14, minor 3

    [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)

    [Bluetooth::CSRHIDTransition] transition complete.

    systemShutdown false

    CSRUSBBluetoothHCIController::setupHardware super returned 0

    Previous Shutdown Cause: 5

    NVDANV50HAL loaded and registered.

    Atheros: mac 12.2 phy 8.1 radio 12.0

    DSMOS has arrived

    AirPort_AthrFusion21: Ethernet address 00:1c:b3:ba:fd:84

    IO80211Controller::dataLinkLayerAttachComplete():  adding AppleEFINVRAM notification

    AirPort: Link Down on en1. Reason 1 (Unspecified).

    AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA

    AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RX_MAX_LE 1024, TX_MAX_LE 768, ST_MAX_LE 3328

    yukon: Ethernet address 00:1b:63:92:be:fa

    ast_pending=0x2966cc

    cpu_interrupt=0x2b398d

    vboxdrv: fAsync=0 offMin=0x984 offMax=0xc90

    VBoxDrv: version 4.0.12 r72916; IOCtl version 0x180000; IDC version 0x10000; dev major=19

    VBoxFltDrv: version 4.0.12 r72916

    VBoxAdpDrv: version 4.0.12 r72916

    en1: 802.11d country code set to 'EE'.

    en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140

    AirPort: Link Up on en1

    AirPort: RSN handshake complete on en1

    AirPort: RSN handshake complete on en1

    AirPort: RSN handshake complete on en1

    hfs: Removed 4 orphaned / unlinked files and 0 directories

    AirPort: Link Down on en1. Reason 2 (Previous authentication no longer valid).

    Ethernet [AppleYukon2]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,af48,0de1,0200,cde1,2800]

     

    As we can see, everything since boot time is there. How about a word about some dead devices in your computer? Nah, not needed.

     

    I'm just enjoying my hand-made Gentoo Linux laptop more and more each passing day. Unless they starting coming standard with a lifetime warranty, my own money will not be going towards Apple laptops for a long while.

  • by slexus,

    slexus slexus Aug 19, 2011 11:17 PM in response to slexus
    Level 1 (0 points)
    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.

  • by slexus,

    slexus slexus Aug 20, 2011 5:17 AM in response to slexus
    Level 1 (0 points)
    Aug 20, 2011 5:17 AM in response to slexus

    /___sbsstatic___/migration-images/159/15976387-1.jpg

    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.

  • by tjk,

    tjk tjk Aug 20, 2011 5:22 AM in response to slexus
    Level 7 (24,259 points)
    Mac OS X
    Aug 20, 2011 5:22 AM in response to slexus

    slexus wrote:

     

    /___sbsstatic___/migration-images/159/15976417-1.jpg

    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 . . . .

  • by slexus,

    slexus slexus Aug 20, 2011 6:50 AM in response to tjk
    Level 1 (0 points)
    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.

  • by tjk,

    tjk tjk Aug 20, 2011 7:10 AM in response to slexus
    Level 7 (24,259 points)
    Mac OS X
    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?

  • by slexus,

    slexus slexus Aug 20, 2011 7:30 AM in response to tjk
    Level 1 (0 points)
    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:

     

    /___sbsstatic___/migration-images/159/15977004-1.jpg

    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.

  • by pantini,

    pantini pantini Aug 25, 2011 10:03 PM in response to slexus
    Level 1 (0 points)
    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

  • by slexus,

    slexus slexus Aug 26, 2011 1:40 AM in response to pantini
    Level 1 (0 points)
    Aug 26, 2011 1:40 AM in response to pantini

    installing is not an issue. finding a ribbon anywhere for a1229 seems to be. subscribed to some keyword search feeds on ebay now.

  • by ImCanadianEh,

    ImCanadianEh ImCanadianEh Aug 31, 2011 11:03 AM in response to slexus
    Level 1 (0 points)
    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!

  • by ImCanadianEh,

    ImCanadianEh ImCanadianEh Aug 31, 2011 2:02 PM in response to ImCanadianEh
    Level 1 (0 points)
    Aug 31, 2011 2:02 PM in response to ImCanadianEh

    slexus,

     

    Sorry - I've just had a look at the cable that I pulled out of my machine and in order to see the numbers, you have to be looking at the underside of the cable and yes, they're TINY...assuming it's the same for your a1229 then have a look at the image and you should know where to look.

     

    Cheers!

     

    FlexCable.jpg

  • by slexus,

    slexus slexus Oct 1, 2011 8:09 AM in response to ImCanadianEh
    Level 1 (0 points)
    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.

first Previous Page 20 of 26 last Next