- Joined
- Sep 29, 2011
- Messages
- 8
- Motherboard
- HP 8300 CMT
- CPU
- I7-3770
- Graphics
- HD 4000
- Mac
- Classic Mac
- Mobile Phone
Greetings everyone!
I've been following the Hackintosh scene for some time now, thanks to this site and others, I ran an Asus P5Q Deluxe mobo with minimal problems for about 3 years, but I just upgraded my whole system to follow Tonymac's budget build. My new system is as follows:
Gigabyte GA-Z77-DS3H mobo
i5-3570k (I'm using HD4000, no extra GPU)
16GB RAM
120GB OCZ SSD
3TB WD drive for media storage
So.. I fitted all the new components into my existing case, booted from my UniBeast USB stick, and installed Mountain Lion onto my SSD.
It booted up fine!
Ran MultiBeast with the minimum of additions, rebooted, and all was still fine. Sleep works. Audio works. My previous system's hard drive, I just left fitted inside the case with my old Snow Leopard installation intact.
Then I decided to use Migration Assistant to transfer across all my preferences and applications. BIG MISTAKE. Migration Assistant worked perfectly, I was able to add another account, log into it and use all my apps and settings. I was fooling around for a couple of hours on what appeared to be a fully functioning system, and decided I'd better reboot and check everything was still working (after I'd used SuperDuper to back up my entire new installation onto a spare drive). And what do you know.. kernel panic.
The strange thing about it is that the error message on the KP screen went into detail about SleepEnabler.kext, which I'd not installed on the new system. I figured it must have been carried across with Migration Assistant, so I booted up from the USB stick again and got into Terminal and deleted all references to it. Still no go. The error message might have changed after I'd deleted it, I can't remember (it was pretty late at night by this point!) so I ended up wiping the SSD and re-installing ML again. (The SuperDuper backup had exactly the same problem.)
This time I tried to use Migration Assistant to JUST migrate the apps across - I figured I could easily change settings and preferences, but apps was the big deal; you can accumulate a LOT of stuff using the same computer for three years - and wouldn't you know, the same thing happened again once I'd rebooted.
I did all the usual stuff like clearing the kext cache, fixing permissions, etc, and still no joy at all. I did some extensive Googling and didn't really find anything applicable - at least not in the last year or so on modern components and software, anyway.
So here's my question: has anybody successfully used Migration Assistant, or will it break every installation? If you got it working, how did you do it?
I've now installed ML from my USB stick a third time and am running from scratch, and I really don't want to think about how long it's going to take to get everything back up to speed. Any advice would be much appreciated!
I've been following the Hackintosh scene for some time now, thanks to this site and others, I ran an Asus P5Q Deluxe mobo with minimal problems for about 3 years, but I just upgraded my whole system to follow Tonymac's budget build. My new system is as follows:
Gigabyte GA-Z77-DS3H mobo
i5-3570k (I'm using HD4000, no extra GPU)
16GB RAM
120GB OCZ SSD
3TB WD drive for media storage
So.. I fitted all the new components into my existing case, booted from my UniBeast USB stick, and installed Mountain Lion onto my SSD.
It booted up fine!
Ran MultiBeast with the minimum of additions, rebooted, and all was still fine. Sleep works. Audio works. My previous system's hard drive, I just left fitted inside the case with my old Snow Leopard installation intact.
Then I decided to use Migration Assistant to transfer across all my preferences and applications. BIG MISTAKE. Migration Assistant worked perfectly, I was able to add another account, log into it and use all my apps and settings. I was fooling around for a couple of hours on what appeared to be a fully functioning system, and decided I'd better reboot and check everything was still working (after I'd used SuperDuper to back up my entire new installation onto a spare drive). And what do you know.. kernel panic.
The strange thing about it is that the error message on the KP screen went into detail about SleepEnabler.kext, which I'd not installed on the new system. I figured it must have been carried across with Migration Assistant, so I booted up from the USB stick again and got into Terminal and deleted all references to it. Still no go. The error message might have changed after I'd deleted it, I can't remember (it was pretty late at night by this point!) so I ended up wiping the SSD and re-installing ML again. (The SuperDuper backup had exactly the same problem.)
This time I tried to use Migration Assistant to JUST migrate the apps across - I figured I could easily change settings and preferences, but apps was the big deal; you can accumulate a LOT of stuff using the same computer for three years - and wouldn't you know, the same thing happened again once I'd rebooted.
I did all the usual stuff like clearing the kext cache, fixing permissions, etc, and still no joy at all. I did some extensive Googling and didn't really find anything applicable - at least not in the last year or so on modern components and software, anyway.
So here's my question: has anybody successfully used Migration Assistant, or will it break every installation? If you got it working, how did you do it?
I've now installed ML from my USB stick a third time and am running from scratch, and I really don't want to think about how long it's going to take to get everything back up to speed. Any advice would be much appreciated!
