kcculhwch

Q: SPI Keyboard/Trackpad on MacBookPro12,1 Not Working after 10.11.3

I'm having an issue where my keyboard and mouse are not reinitializing after waking up from sleep after the update to 10.11.3. I'm on MBP12,1. I can plug in usb or bluetooth devices which will work, but the internal keyboard and trackpad won't work until after I have shut down the computer and restarted it.

 

I'm seeing the following error in the logs:

 

2/11/16 11:32:41.000 AM kernel[0]: Error: Apple Internal Keyboard / Trackpad::IssueMessage Failed to issue message the bus error: 0xe00002eb

2/11/16 11:32:41.000 AM kernel[0]: Error: Apple Internal Keyboard / Trackpad::setPowerState AppleHSSPIDevice : Resume Device in Power On failed with error 0xe00002eb

 

I have reset pram and smc, re-run the 10.11.3 combo update, and run the disk utility on my hard drive. None of these have resolved the issue.

 

Has anybody else had a similar problem or found a resolution for MBP12,1 ?

MacBook Pro with Retina display, OS X El Capitan (10.11.3)

Posted on Feb 11, 2016 8:48 AM

Close

Q: SPI Keyboard/Trackpad on MacBookPro12,1 Not Working after 10.11.3

  • All replies
  • Helpful answers

Page 1 Next
  • by fsavje,

    fsavje fsavje May 9, 2016 11:25 PM in response to kcculhwch
    Level 1 (4 points)
    May 9, 2016 11:25 PM in response to kcculhwch

    I have exactly the same issue. Did you find any solution in the end, kcculhwch?

  • by iFireghost,

    iFireghost iFireghost Jul 6, 2016 12:36 PM in response to kcculhwch
    Level 1 (18 points)
    Jul 6, 2016 12:36 PM in response to kcculhwch

    Same here. After 4(!) repairs, Apple exchanged my MacBook Pro for a new one. Now, the new one is starting to show the same symptoms. Heading back to the store soon :/

  • by Terry Wilson4,

    Terry Wilson4 Terry Wilson4 Jul 8, 2016 3:46 PM in response to kcculhwch
    Level 1 (14 points)
    Jul 8, 2016 3:46 PM in response to kcculhwch

    Yep, I've got this exact same issue. Got progressively worse since 10.11.3. Got to the point where nothing a SMC/NVRMA isn't guaranteed to fix it.

     

    Curiously, this problem exhibits itself in Windows 10 via Bootcamp also.

  • by iFireghost,

    iFireghost iFireghost Jul 9, 2016 7:55 AM in response to kcculhwch
    Level 1 (18 points)
    Jul 9, 2016 7:55 AM in response to kcculhwch

    Good/bad new: I just came back from the Apple Store. According to the genius, this problem caused quite a discussion behind closed doors at the store today When she came back, she told me, that another and another repair will not solve the problem since this is clearly a software based issue. It's apparently not uncommon with 2015 Retina MacBook Pro models. Currently, there's no fix, according to the genius. Her only hope was a future software update. I assume this is a firmware thing, since macOS Sierra PB1 has the same issues. Her only advise for me: Call AppleCare, ask them to take the device back for a full refund and either pick a different model or wait for the next generation. So that's what I am up to now. Stay tuned!

  • by Terry Wilson4,

    Terry Wilson4 Terry Wilson4 Jul 9, 2016 10:59 AM in response to iFireghost
    Level 1 (14 points)
    Jul 9, 2016 10:59 AM in response to iFireghost

    Cheers for the info, this is going to make my Genius appointment very interesting. I mean right now, my machine is pretty bloody useless!

  • by cvigo,

    cvigo cvigo Jul 13, 2016 2:43 PM in response to Terry Wilson4
    Level 1 (4 points)
    Notebooks
    Jul 13, 2016 2:43 PM in response to Terry Wilson4

    Mine started to fail in the same way, after 1 year on intense use.

     

    Resetting SMC/NVRMA did not work

    Reinstalling OSX did not work

     

    The guy at the Apple Care Chat suggested to delete the disk and perform a fresh OSX installation. Anyone has tried this? and... did it solve the issue?

  • by Terry Wilson4,

    Terry Wilson4 Terry Wilson4 Jul 13, 2016 4:29 PM in response to cvigo
    Level 1 (14 points)
    Jul 13, 2016 4:29 PM in response to cvigo

    The reinstalling of the OS didn't help in the slightest. It did seem to be fine for a couple of hours, but then died again.

  • by iFireghost,

    iFireghost iFireghost Jul 20, 2016 9:40 AM in response to iFireghost
    Level 1 (18 points)
    Jul 20, 2016 9:40 AM in response to iFireghost

    So, couple of weeks later, Apple just called me back. I am getting a full refund since this problem cannot be solved at the moment. I am lucky to still have an older MacBook Air that will serve as a replacement until Apple releases a finished MacBook Pro 13".

  • by jotaplaza,

    jotaplaza jotaplaza Jul 20, 2016 9:44 AM in response to iFireghost
    Level 1 (8 points)
    Mac OS X
    Jul 20, 2016 9:44 AM in response to iFireghost

    Well good news for you. In my case I'm out the year warranty so no good news for me. U$2,000 for a 14 months of use, and now to the garbage

  • by Terry Wilson4,

    Terry Wilson4 Terry Wilson4 Jul 20, 2016 9:47 AM in response to iFireghost
    Level 1 (14 points)
    Jul 20, 2016 9:47 AM in response to iFireghost

    Luckily for me was just £55 for a replacement ribbon cable. Fingers crossed it stays working.

  • by iFireghost,

    iFireghost iFireghost Jul 20, 2016 9:47 AM in response to jotaplaza
    Level 1 (18 points)
    Jul 20, 2016 9:47 AM in response to jotaplaza

    Well, I bought mine in may 2015. Luckily, after so many failed repair attemts, Apple gave me a new Mac, restarting the warranty cycle. Have you checked in your Mac for repair before? If Apple was unable to fix it, you might be lucky too. Also, since they have finally recognised this problem, an out of warranty exchange might not be impossible. I am actually thinking a general recall program is around the corner.

  • by jotaplaza,

    jotaplaza jotaplaza Jul 20, 2016 9:50 AM in response to iFireghost
    Level 1 (8 points)
    Mac OS X
    Jul 20, 2016 9:50 AM in response to iFireghost

    Well, that may be possible. I'll get an 2011 MBP to work during the revision time. I'`ll let you know how it goes.

  • by cvigo,

    cvigo cvigo Jul 20, 2016 1:32 PM in response to kcculhwch
    Level 1 (4 points)
    Notebooks
    Jul 20, 2016 1:32 PM in response to kcculhwch

    I deleted the HD and reinstall: same issue

     

    I installed Bootcamp to see if Windows makes any difference... no issues in 18h with MacOS X

     

    Will see tomorrow

  • by cvigo,

    cvigo cvigo Jul 21, 2016 12:09 PM in response to cvigo
    Level 1 (4 points)
    Notebooks
    Jul 21, 2016 12:09 PM in response to cvigo

    36 hours without getting the issue.

Page 1 Next