[minibryan]

Hello,

I am having have a devil of a problem migrating my wife from a mini9 to her new 15' MacBook Pro. The problem has to do with the screen. It goes dark a short time after login and the brightness controls (F1-F2) are not responsive. I can move the slider bar in the system preferences->displays tab and the screen responds. Everything on the MBP is fine (screen controls are responsive, sleep and wake work) until I migrate her using the migration assistant.

After the migration and a reboot, the brightness controls no longer work, and the slider-bar to control brightness in the system preferences->displays tab no longer appears. I'm wondering if its not something similar to this post, but I wasn't sure...

Mini 9 to Mini 10v Migration: My Fix for Sleep Problem

Could this have something to do with the ketxs, or the dsdt.aml? Can someone perhaps help me with how to get them back to factory settings for the MBP?

Thanks,

Bryan

[Side.Step.Society]

I really have to advise against doing this. Migration Assistant will transfer all your files, including things like preference files that may or may not be compatible with your MBP.

I'd suggest finding the files, documents, music, etc, and manually transferring it over to the MBP.

To cure the problem, I would simply suggest formatting the drive and reinstalling Snow Leopard, just to be safe and prevent anything from possibly popping up in the future.

[minibryan]

It certainly seemed like a good idea at the time, but I have to admit it has not been much fun. Perhaps this thread will keep someone else from using the migration assistant and a time machine backup to move from a hackintosh into a new MBP.

At any rate, when I boot from the install disk and try to do the install, now the installer can't find the boot disk. Is there anything you could recommend besides a NVRAM (CMD-OPT-P-R) and PDU reset (pull battery out and hold power button down for 10 seconds) ?

[Side.Step.Society]

When you boot to the SL DVD/DVD that came with your Mac, open up Disk Utility and check for your disk there. If it's there, erase the drive and just double check that it's using the GUID partition table and Mac OS Extended (Journaled) file system.

[minibryan]

Doing that now. Just out of curiosity, why not Mac OS Extended (Journaled Case Sensitive) too?

Thanks for the help btw

[Side.Step.Society]

Case sensitive is more for heavy developers. It's not suggested for your average Snow Leopard install.

[minibryan]

Thanks again, could you recommend a line to read more about kexts and netbook installer? I'm keen to understand better what happend.

[Side.Step.Society]

Well, I don't believe it was a problem with copying kexts, because Migration Assistant won't copy those. I think it was something more to do with preference files and personal settings since M.A. will copy those so your new computer can be just like your old computer. This is just generally a bad idea, even from a real Mac to another real Mac.

[grassle]

You could try the Migration Assistant again, but select only User files, Network settings, and Applications, and NOT the other files. That should leave the MBP system pretty much alone.

Then log into the MBP as ANOTHER user than the migrated one (with admin rights) and put all files in in migrated user/Library (or the whole library) into a separate folder, eg. on that user's Desktop.

Now you can log in as the migrated user, but you will not have the preferences etc. set/installed on the Mini. You can manually put needed files back into the Library, but do so in small chunks to easily find the culprit if some file causes trouble.