vpnoob.blogg.se

1. HOW TO PRINT RESUME ON MAC BOOK PRO NOT FRONT AND BACK HOW TO
2. HOW TO PRINT RESUME ON MAC BOOK PRO NOT FRONT AND BACK DRIVERS

FWIW I installed Mountain Lion on this problematic Mac in order to create a Fusion drive with a small SSD inside the Express card slot and the main HD. I hope this help somebody with this issue. kext that stops the system when it tries to rebuild the kextcache file should be deleted (that includes all in the above list and that was the way I was able to identify these “bad” drivers). Where Volume_name is the name of your boot disk. You can then try the following inside a Terminal session: You can identify which are the problematic ones if you are able to boot with another drive.

HOW TO PRINT RESUME ON MAC BOOK PRO NOT FRONT AND BACK HOW TO

Can anyone tell me how to install Ubuntu 12.04 on it I already have Windows installed via BootCamp. Inside the Contents/Plugin folder, delete every kext file with FireWire or Fire or FW in their name. I bought a MacBook Pro 9,1 (Mid 2012, 15inch, NOT retina). So what I did in order to be able to boot with my MacBook Pro 4,1 Core 2 Duo 2.4 GHz with a dead FireWire port was the following:ĭo a “show package contents” on the AppleStorageExtensions.kext.

HOW TO PRINT RESUME ON MAC BOOK PRO NOT FRONT AND BACK DRIVERS

There are also bad drivers that seem to depend on FireWire inside the AppleStorageExtensions.kext.ĭeleting this kext is not an option, as it includes useful things related to USB and SATA. It’s no longer sufficient to move the 5 IOFireWire*.kext extensions out of the System/Library/Extensions folder. The issue seems to be a bit more complicated with Mountain Lion (10.8). I as well have to repeat this operation after installing system updates. The solution was easy: to move IOFireWireFamily.kext out of /System/Extensions. Since my MacBook was out of warranty and I didn’t want to spend 350€ on a new logic board for a quite old computer, I decided to minimize the consequences. I confirmed all of these by contacting a technician of a local Apple reseller. Quick search revealed that the problem of dieing firewire ports is not uncommon for this generation of MacBook Pros, and the only way to repair it is to replace a logic board. I checked my firewire 400 port and it appeared to be broken. Obviously something was wrong with the firewire. Jun 21 03:06:20 Dae-MBP /usr/libexec/hidd: Timeout waiting for IOKit to be quiet Jun 21 03:02:15 Dae-MBP configd: InterfaceNamer: Jun 21 03:02:15 Dae-MBP configd: InterfaceNamer: MacBookPro2,2/AppleACPIPlatformExpert Jun 21 03:02:15 Dae-MBP configd: InterfaceNamer: MacBookPro2,2 To diagnose the problem, I booted in verbose mode (hold Cmd + V when it starts booting, later you may find the logs in Console.app) and noticed these lines: Jun 21 03:02:15 Dae-MBP configd: InterfaceNamer: Busy services : Update: for Yosemite instructions, see the comment by Douglas Santana. Both problems appeared simultaneously, so right from the start it was clear that they’re related.

Once I noticed that the booting process of my MacBook Pro 2,2 extended to 5-7 minutes (the longest phase of the startup process was the blue screen which usually appears right before the desktop) and additionally, sleep (hibernate) mode stopped working.