Jump to content
10 posts in this topic

Recommended Posts

I finally made it and OSX lion is installed and working fine. So i figured it was only to install Chameleon on the new install and then boot, but nothing happens. There is only a blinking _ as when the HDD is blank. Have tried both standard and HFS EFI install.

 

I'm using Chameleon RC5 770.

 

Is this a partition table issue? My disk has the GUID pt..

Here are two guides on how to do a manual install of Chameleon from

Terminal. Are you dual-booting? Partition active?

 

http://forum.voodooprojects.org/index.php?topic=649.0 into hidden EFI

 

http://tonymacx86.blogspot.com/2009/11/how...ually-from.html

To your root SL partition and the initial 512 bit boot segment of your drive.

Thank you for the answer!

I was under the impression that the *.pkg installers where supposed to do this for you. Just have to do a fresh reinstall due some file system ownership issues. Then I will try out the EFI partition boot. Single boot, single HDD.

The *.pkg installers are supposed to do that for you, if you invoke installing Chameleon. [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] for instance, you have to check a box. But if you want something done right, do it yourself, it's hard to find good help. The nice thing about the EFI install is that it's stable and not ovewritten easily. I use Gparted, it can copy the EFI partition to another partition formatted HFS+.

Gparted as EFI partition backuper, or partition installer? I used the "svn" command to get the Chameleon source, it took forever, and I ended up with all the branches. How much do they differ and aren't there a optimized revision?

 

Again thanks for helping, you have probably save me from hours of non-productive problem solving:)

 

 

EDIT:

 

./fdisk -f boot0 -u -y /dev/rdisk0 -> bash: ./fdisk: No such file or directory

./fdisk -f boot0 -u -y /dev/rdisk0 -> fdisk: could not read MBR code: Is a directory

 

EDIT2:

 

Did not open the directory, it was uncompiled..

I've had the problem where the the SL partition has become unbootable and returns a Kernel Panic. To fix this, sometimes caused by a bad choice of an installed .kext, it's handy to have another copy of SL to boot from. The not working partition is still there just not booting, and one can repair the bad partition from the other install of SL.

 

My solution: Once you have your hidden EFI partition populated with your boot files (it starts off empty) make a backup booting, SL partition.

 

First I use Gparted to create a HFS+ partition on a usb stick. This makes

the 200mb hidden EFI partition; maybe the next step would do this as well.

 

While things are still working, mount a 16GB usb stick. Use Disk Utility

to partition it, choosing one partition, mac extended journal, and under Options, the GUID partition scheme. Before your original SL install gets to fat, clone your working SL to the usb stick. Use Carbon Copy Cloner (CCC) in the clone everything setting. This clones your working SL to your usb stick which now has the same working bootable installed files.

 

I cloned my Thunderbird +email and Firefox with bookmarks and about seven or eight other Apps, including CCC. One way this works is with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and a cd; the usb stick, SnowBakup, shows up on your Chameleon boot options. It works standalone this way. I used Gparted to copy my working EFI partition (200mb) containing boot files and /Extra to the empty usb stick EFI partition. The old EFI partition replaces the empty EFI partition on the new SL usb stick and is just as bootable. The clone used about 14.5GB out of 16GB available.

 

Suppose you have two drives with SL on the second. That SL uses the 512 byte Chameleon boot0 file and the other two Chameleon boot files which now reside on the EFI partition. If that SL on the drive becomes broken, then you can still boot to that drive (out of the Bios screen) while plugging in your usb stick. Chameleon will see/choose your SnowBakup usb stick and boot up from it normally because it hasn't become broken yet, it was cloned before the breaking event. So you don't need [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] in that case. If at some time your SL installation gets overwritten by another OS, and messes up EFI and boot0, and SL, you can reformat that hard drive and restore with CCC the working usb clone SL and EFI to that same hard drive. I think you would still have to write boot0 to the MBR as a final step.

 

So this idea provides you with a backup, just like a backup to some other drive, and can also function as a standalone boot drive with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]. What I mean by more than just a boot drive; it's a finished SL working install.

 

Why did you get the svn source? Gringo's guide,

http://forum.voodooprojects.org/index.php?topic=649.0 into hidden EFI

has a link to a newer Chameleon download. You have to login to see them,

C2RC5_default.zip for themes, and Chameleon_2.0_RC5_r750.zip **

 

Use a compiled version not source. It's often compressed in a *tar.gz

Uncompress it and all the needed Chameleon boot files are in the i386 folder. Navigate

(change directory = cd)to that i386 folder and issue your commands from there.

I think just fdisk will work and maybe not ./fdisk. tonymacosx wrote,

 

"The command will become: cd /Users/****/Desktop/Chameleon-2.0-RC2-r640-bin

7. Type cd i386"

 

Of course you can use a newer one, Google has several downloads for a newer compiled.

 

Every once in awhile, the different branches get merged. For this, the links ** I just provided will do well.

I didn't know how Chameleon was released, so I though e.g. only one branch (Kabyl) had the latest ATI compability. Did some reading and compiled the latest trunk (r780). Installed it like the guide you first gave me. Didn't take long, and worked perfectly! Now I have a Lion DP2 install using only Chameleon boot and one kext (FakeSMC).

 

Taking a EFI boot backup seems like an excellent idea. Never heard about CCC, but will do some research. Better safe than sorry:)

 

Thank you for all your help again!

Well done!

 

And...

 

Unnecessary quoting deleted from entire thread.

 

Guys, please trim your quotes, it really helps with readability when you don't have to scroll past lines of garbage text that you've already read.

I didn't know how Chameleon was released, so I though e.g. only one branch (Kabyl) had the latest ATI compability. Did some reading and compiled the latest trunk (r780). Installed it like the guide you first gave me. Didn't take long, and worked perfectly! Now I have a Lion DP2 install using only Chameleon boot and one kext (FakeSMC).

 

Taking a EFI boot backup seems like an excellent idea. Never heard about CCC, but will do some research. Better safe than sorry:)

 

Thank you for all your help again!

 

You are certainly welcome! I didn't realize from your first post that you were accomplished with Linux; I'm glad I refrained from making a deprecating comment about what appeared to me to be a newb grandiose embellishment of simple instructions! "Better safe than sorry." :) is like the golden rule for computers and conversation, so I think if you insult somebody, you should purposefully really mean it. Do they have a foot in the mouth emoticon. :D

 

I had wondered about a discrepancy between Gringo's guide and tonymac's = who says (and now I think it doesn't matter anymore)

  1. Add the DSDT=hd(0,1)/DSDT.aml flag to your as seen in the pictures below.
  2. Save com.apple.boot.plist

http://forum.voodooprojects.org/ is the Chameleon forum and is very helpful, Gringo is also a moderator there. The Gparted forum is also very helpful. Now you've made me jealous, Lion DP2 with only FakeSMC, that's like reaching Enlightenment.

 

Windows and I suppose Linux have quite a few good total clone tools; that dd command will clone one drive to another, but is slow.

CCC has the Everything, bit by bit method, and also a file method. I don't think the file method captures the MBR, where boot0 is located. My usb stick method relies on a boot0 already existing on the internal drive; or a Chameleon bootup cd. I would like to make it self-booting, like a personalized iPortable Snow x86 10.6.2 which is now defunct. Hackintosh has fewer good (free) cloning tools. As of now, I copy and replace a working EFI partition with Gparted, and clone the SL partition on the internal drive, not the whole drive.

I'm thinking that if I create an MBR partition table on the usb stick that perhaps I can place boot0 in the MBR and make it bootable? I've always thought of usb drives as data drives, which is *centric :D

I had wondered about a discrepancy between Gringo's guide and tonymac's = who says (and now I think it doesn't matter anymore)

  1. Add the DSDT=hd(0,1)/DSDT.aml flag to your as seen in the pictures below.
  2. Save com.apple.boot.plist

That should only be necessary if you're not using the default location for your dsdt.aml, which is /Extra/dsdt.aml.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...