Jump to content

Want to clean up system and switch to Chameleon ...

xj0hnx

By xj0hnx,
in OSx86 10.6 (Snow Leopard)

 Share
20 posts in this topic

Recommended Posts

xj0hnx
xj0hnx
Posted
Posted

So I used the ib0ot, and [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] to install out of ignorance, and now would like to get rid of the changes that MB added, and get my bootloader right so I don't have to use the disc to boot everytime. My system is very stable, and I have spent quite a many few hours getting it set up confortably, so I would rather not reinstall if I don't have to.

 

I'll start at the boot issue. I am guessing that my boot problems are based around having OSX on one disc, and Windows on another, with my Windows SSD being first in the boot order, and MB bootloader installed in the OSX HDD, which is second. HOwever when I select the OSX disc as first boot device the system hangs, and doesn't do anything after "Verifying DMI Pool ..." in boot up, which is the point at which the bootloader should start. I tried using EasyBCD to point to the OSX drive and add it to the boot options, and it did, but the same thing happens, it just hangs. At this point I am not sure what to do. Any ideas?

 

Second, I looked through Chameleon and there are a lot of good looking options, but I am worried about how selecting them, and the options already installed by MB would conflict. I am guessing I should remove/uninstall anything from MB I plan on replacing with Chameleon, is this correct? Would Chameleon overwrite the installed options? One I am particularly interested in is "force 64-bit", might it address my RAM issue too?

Link to comment
Share on other sites
3.14r2
3.14r2
Posted
Posted

I'll start at the boot issue. I am guessing that my boot problems are based around having OSX on one disc, and Windows on another, with my Windows SSD being first in the boot order, and MB bootloader installed in the OSX HDD, which is second.

There is nothing wrong in having separate drives for each OS. In fact IS better this way. System management is much more simple with separate disk. I've had a desktop PC with two disks and the boot drive being OS X drive with Chameleon. It all worked fine with no issues (well, there were problems with SP1 install, but this is Windows own issue). I'm not familiar with MB (have always used Chameleon), so don't know all the details.

 

Chameleon consists of few different parts:

  • Files/binaries written to disk/partition (boot0, boot1h, boot)
  • Configuration file (org.chameleon.Boot.plist/com.apple.Boot.plist)
  • Additional extras (DSDT, SMBIOS.plist, kexts, Chameleon modules)

 

These are the standard parts. MB may have something additional or may have less. I don't know for sure.

 

Then you install Chameleon, it should overwrite boot0, boot1h and boot files existing on the disk with the new version. Configuration files and Additional extras should be replaced manually (the /Extra folder).

 

The other important thing is to set "boot" flag to partition where Chameleon is installed. Otherwise it won't boot.

  • Like 1
Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

Thank you for the reply. I didn't mean the problem was them being on two separate disc, but that because they were on separate disc MB wrote the bootloader to the disc that was not set up to be booted from. After reading about the installation process I specifically choose to install them on separate disc because it is better situation :)

 

I am just worried that if I use Chameleon to install the boot loader to the right disc, the Windows disc, that it will over write my current MBR and if something is not correct I will be s.o.l. and not be able to get into either system.

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

Disconnect the disk you DON'T WANT to install Chameleon to (prior to installing it) and all should be OK.

 

But there in lays the problem, well, I guess it doesn't have to be. I have my Windows disc as first boot device, which is where Chameleon would need to be installed. I guess I could use my Raptor which is where OSX is installed as my first boot device, so long as Chameleon works. The problem that I encountered was that even though I installed MB's boot loader on the OSX drive, when I selected it as the first boot device it would just hang when the computer handed it off to the loader. Here is the Detailed (Debug Mode) Display Mode from EasyBCD:

Windows Boot Manager

--------------------

identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}

device partition=\Device\HarddiskVolume5

description Windows Boot Manager

locale en-US

inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

default {22a2b890-b9dd-11e1-a295-a7e0069318d6}

resumeobject {22a2b88f-b9dd-11e1-a295-a7e0069318d6}

displayorder {22a2b890-b9dd-11e1-a295-a7e0069318d6}

{22a2b893-b9dd-11e1-a295-a7e0069318d6}

toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}

timeout 10

Windows Boot Loader

-------------------

identifier {22a2b890-b9dd-11e1-a295-a7e0069318d6}

device partition=C:

path \Windows\system32\winload.exe

description Windows 7

locale en-US

inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}

recoverysequence {22a2b891-b9dd-11e1-a295-a7e0069318d6}

recoveryenabled Yes

osdevice partition=C:

systemroot \Windows

resumeobject {22a2b88f-b9dd-11e1-a295-a7e0069318d6}

nx OptIn

Real-mode Boot Sector

---------------------

identifier {22a2b893-b9dd-11e1-a295-a7e0069318d6}

device partition=H:

path \NST\AutoNeoGrub0.mbr

description Mac OS X

locale en-US

Link to comment
Share on other sites
3.14r2
3.14r2
Posted
Posted

I see... The thing is that AFTER Chameleon is installed, the partition it was installed to, should have a "boot" flag. If the above flag is not set, the disk COULDN'T be used as a boot volume (this is true with Windows as well it won't boot without the flag set to the volume with the boot loader). This can be checked/set using PartedMagic Live CD or using fdisk/fdisk440 tool.

 

More info:

http://www.insanelym...ly-v-2-and-v-1/

http://forum.voodoop...x.php/topic,649

http://forum.voodooprojects.org/index.php/topic,1141.0.html

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

Ok, so when I boot off the hdd I get to the chameleon boot loader, I select OSX "boot verbose", and then it hangs here ...

post-1137780-0-08205300-1364064339_thumb.jpg

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

The contents of the /Extra folder on this drive are ...

 

Extensions (folder)

Extensions.mkext

modules (folder)

org.chameleon.Boot.plist

smbios.plist

smbios.plist.bak

Themes (folder)

Link to comment
Share on other sites
eep357
eep357
Posted
Posted

Keep in mind Chameleon is the bootloader you were already using! Chameleon is the name of the overall project, Chimera and Enoch for example, are just branches/versions of that same bootloader. Think of it like this: "Windows 7 Pro", "Windows 7 Ultimate" and "Windows 7 Home" additions are still all just Windows 7 with maybe a few minor differences that most people won't ever use or even notice.

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

Ok, turns out I wasn't installing it on the right partition, it was going on disc1,1 and should have been on 1,2. So now it's on the right partition, but it keeps stopping at

 

FireWire (OHCI) PCI now active GUID xxxxxxxx max speed s400

 

But then stalls and says Still waiting for root device

 

It does that three times and then does the FireWire line again and then just loops

 

Here's a picture

post-1137780-0-32305600-1364099946_thumb.jpg

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

The screenshot is turned upside down :)

 

"Still waiting..." Indicates that there is no driver for the disk controller your MB has, present in OS X, so it is unable to see the disks.

But it boots with the disc, is it something I can install? Haha yea, I was posting from my phone, I didn't want to hook everything back up while troubleshooting just to post.
Link to comment
Share on other sites
3.14r2
3.14r2
Posted
Posted

You need to install to install LegacyAppleIntelPIIXATA.kext (make sure that drvice/vendor IDs of the controller are present in the Info.plist file of the above kext) if you have an Intel chipset, or other kext if you have nvidia or any other chipset. You can get the IDs via Windows (Device manager > device properties > hardware ID) or via Linux using lspci tool in terminal like:

sudo lspci -vnn > ~/Desktop/lspci.txt

this should create lspci txt file on the desktop.

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

Where can I read how to ad the ID's to the kext? And I am guessing I need to install the ID's from Device Manager > IDE ATA/ATAPI controllers > Intel® ICH10 Family 6 Port SATA AHCI Controller - 3A22? Or Standard ACH1.0 Serial ATA Controller

Link to comment
Share on other sites
3.14r2
3.14r2
Posted
Posted

ICH10 IS supported in OS X.OOB (used in Mac Pro). Check SATA mode in BIOS. It should be set to AHCI (not compatible/legacy) otherwise native support won't work. The LegacyAppleIntelPIIXATA.kext is mostly used for older systems (ICH5/ICH6) so not needed here (unless you want the controller to work in compatible/legacy mode).

 

Some motherboards have two SATA/IDE controllers. One for instance may be ICH7 (Intel), the other one for instance could be ASMedia/JMicron. If, for instance, your OS X disk is connected to ASMedia controller, you would need driver for ASMedia controller. So check what controllers your motherboard has and which controller OS X disk is connected to.

post-663344-0-76897000-1364175337_thumb.jpg

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

Good news, I reinstalled on my SSD, and used Chimera 2.0.1 and ...IT WORKS!!!! Everything works, well, except audio, but I didn't install the kext for it yet. It sees all 12GB, boots from the drive, etc ...The only thing I think I am going to need is the fix to get the App Store working.

 

edit: Audio is now working too. I need to add a line to which file to get App Store? something like Ethernet onboard?

 

I wish I knew what was the difference in it working for my SSD than my Raptor, different controller?

Link to comment
Share on other sites
xj0hnx
xj0hnx
Posted
  • Author
Posted

Congrats! As to App Store issue, there are fixes for that. I don't use the above (I have Snow Leopard which is less dependent on the App Store, then Lion or ML), so unable to help here.

 

I have Snow Leopard too :) haven't been able to get ML to install, I keep getting stuck on a white screen.

Link to comment
Share on other sites
eep357
eep357
Posted
Posted

For ML with 6870 installer can be problem, one option to delete the ATI6000 controller kext from the installer. After install there are sometimes problem with it's kext too. For more info see here http://www.insanelymac.com/forum/topic/280447-mountain-lion-gm-ati-radeon-6870-problem/page__hl__%2B6870+%2Binstall+%2Bmountain

here http://www.insanelymac.com/forum/topic/281484-ati-hd-6870-twin-frozr-ii-1gb-mountain-lion-not-working-help/page__hl__+6870%20+install%20+mountain#entry1848000

and probably other places if you search a bit

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...