Article: OS X 10.8.1 Update
I rolled back AppleAHCIPort.kext from a backup. Now able to boot. Since the installation failed not sure if it corrupted this file to was not supported. But the error I got was something to the effect that the vtable was malformed.
Replacing these 2 kexts with the ones from Lion worked for me.
AppleAHCIPort.kext
IOAHCIFamily.kext
Once I did this and and used UseKernelCache boot time went from 1:08 to 0:35 seconds
You're Welcome, thanks for the feedback.
I was down the same path, endless hours :beachball:, including fresh install, hopefully my mistakes and research will prevent others from having to go down the same path. I have only been in the hackintosh game for a few weeks. The great tools on this...
The particular fix I posted will address the issue with the Ethernet adapter appearing as not built in. Check the /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist file, does it show for your Ethernet adapter
<key>IOBuiltin</key>
<false/>
or
<key>IOBuiltin</key>...
I managed to finally get it working, there is some good information in my thread that may help.
http://www.tonymacx86.com/mountain-lion-desktop-support/64547-icloud-app-store-facetime-messages-unable-authenticate.html
Thanks for your replay,
This is a fix for some, I believe this has to do with the order the network adapters were added and addressed.
For example.
Your system recognized your wifi adapter first and internally addressed it (en0).
Then it recognized your Built In Ethernet adapter and...
Absolutely
1. Open the org.chameleon.Boot.plist file located in /Extra directory with TextEdit.
2. Append the following XML
<key>EthernetBuiltIn</key>
<string>Yes</string>
<key>device-properties</key>
<string>EFI String Placeholder</string>
3. Leave the TextEdit window open...
iCloud, App Store, FaceTime, Messages - Unable to Authenticate [Solved]
Well, I RESOLVED the issue, I feel like such a noob.
When I thought I was injecting the EFI string, I saw XML in the EFIStudio editor, I copied this part of it and pasted it in my boot plist...
Thanks for the suggestion,
I have used the chameleon wizard to do just that, have tried several times (meaning about 20-30 times) while also trying different systems type i.e. Mini Mac 5,1 iMac 8,1, ect.
Ok, after a bit more research this is what I come up with so far, maybe some of the experts can shed some light.
Checked my NetworkInterfaces.plist found in /Library/Preferences/SystemConfiguration
<key>IOBuiltin</key>
<false/>
From what I am reading the first network interface...
I have the same exact issue as you, went down the same exact rode. If I come across the fix I will let you know.
I think you might be on to something with the ethernet kext, I am using the AtherosL1cEthernet.kext myself. But then again, everything worked in SL and Lion like a dream.
Ok managed to get sleep to work, download a patched version AppleRTC.kext for Mountain Lion after attempting the patch myself. The patch I did myself caused some strange behavior, bluetooth did not work and menu did not show up on the top on boot. But the downloaded version seams to be...
Since upgrade to Mountain Lion I am unable to sign into Apple applications. They were working flawlessly with SL and Lion.
Applications have the following errors.
iCloud
Unable to sign in because of a problem communicating with iCloud.
Try signing again.
App Store
An unknown error...
Mountain Lion does not boot after install. [Resolved w/ Limited Function]
I managed to find a solution.
I changed the bootloader to Chameleon build 2039 (not sure if this part really mattered)
I managed to get my first boot after I installed kexts for my GT 520 that I found on osx86. Not...
Update: (Not yet resolved)
<insert emoticon of banging head again the wall here>
Well I have took the suggestion of a reinstall, I could not get the installer to boot without the xmove - multibeast method in safe mode. I tried UniBeast on 2 different USB drives just got the boot1: error...
Try using boot flag -F (captital F) this will instruct to ignore org.chameleon.Boot.plist. If your mobo was dependant on these settings it still may not boot, but this got me past the "magic number" issue. Hope this helps you get further than i got.
Thanks for the reply,
I will restore F3 version, didn't have any issues with it before ML. I will locate and download Carbon Copy. I will split the partition into 2 and backup to second partition. Delete the first partition and remake it. If this does not clear the boot loader I guess I...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.