Jump to content
3 posts in this topic

Recommended Posts

Hi, everyone! I've got such a problem.

 

For example, I have 2 HDDs (in fact 4, but that doesn't affect anything). The first one has Snow Leopard 10.6.6 (we'll call it SL_1 and the HDD will be SL_1_HDD) installed one day over a Leopard. It's booted via Chameleon RC3, has own /Extra and works perfectly. The second HDD also has Snow Leopard 10.6.6 (SL_2, the HDD is SL_2_HDD) (freshly updated from 10.6.0). It's been installed from SL_1, from a disk image. The bootloader for this new system is Chameleon RC4. /Extra was copied from SL_1, also I copied from there IOATAFamily, IONetworkingFamily and JmictronATA.kext. The problem is:

 

If I select SL_1_HDD as boot disk, I get both systems completely working. But if I select SL_2_HDD as boot disk, I get internet and DVD-ROM not working. So the question is: how does Chameleon work? Where does it take the kexts from? Can I avoid copying all kexts from SL_1 to SL_2? I really don't want to do so cause there's a lot of trash there. So, what should I do?

Link to comment
https://www.insanelymac.com/forum/topic/248513-strange-bootloader-behavior/
Share on other sites

Chameleon supports separate "Extra" folders for 10.5 and 10.6, you can do this with Chameleon installed to one drive only. I can't help you with setting that up though, I've never done it myself so I don't know how it works.

 

Visit the VoodooProjects forum, Chameleon general board and read the Chameleon documentation posted there.

×
×
  • Create New...