Jump to content

Chameleon 2.4svn Official PKG Installer

ErmaC

By ErmaC,
in Chameleon

 Share
4,261 posts in this topic

Recommended Posts

blackosx
blackosx
Posted
Posted

BubuXP. The Chameleon devs don't have much free time in their busy daily lives, so for somebody to develop Chameleon further to support ACPI patching for other OS's is a big request and will most probably not be on anyone's to do list. The source code is freely available if you or anybody else wants to do it.

Link to comment
Share on other sites
BubuXP
BubuXP
Posted
Posted
BubuXP. The Chameleon devs don't have much free time in their busy daily lives, so for somebody to develop Chameleon further to support ACPI patching for other OS's is a big request and will most probably not be on anyone's to do list. The source code is freely available if you or anybody else wants to do it.

 

I thought it was simpler, just moving the DSDT loading function in the code before the OS loading, but I don't consider that the ACPI patching must be adapted to the destination OS. If I thought that before, I didn't even make such request.

Excuse me and thanks for your time.

Link to comment
Share on other sites
sonicfire
sonicfire
Posted
Posted

Has/Is Chameleon RC5 only a 64-Bit Kernel??

 

I tried switching to 32 Bit Kernel for days with no luck. And i need it badly to get a 32 Bit Driver working.

 

I can switch Kernel Bootmode but not the Kernel itself. It´s always 64 Bit no matter what i try.

 

Help please! :-(

Link to comment
Share on other sites
sonicfire
sonicfire
Posted
Posted
sonicfire - Chameleon can boot the OS X kernel in 32-bit mode.

Add the following to your org.Chameleon.Boot.plist

<key>arch</key>
 <string>i386</string>

 

Thanks!

 

Unfortunately, there´s no plist like this one?

(Went to /Library/Preferences/SystemConfiguration).

 

There´s only the classic com.apple.Boot.plist. (Where i tried arch & i386 as well - no luck).

 

If it helps i installed this distri:

http://www.insanelymac.com/forum/index.php?showtopic=259253

(Also with legacy kernel, not sure if this has something to do with 32/64 Bits, guess not).

 

Forgive my stupidity - do i have to look somewhere else for the org.Chameleon.Boot.plist?

 

Thanks in advance

 

EDIT: Now i read somewhere else you can RENAME (?) com.apple.Boot.plist to org.chameleon.Boot.plist. Did that. Wonder why the machine even starts? (And it doesn´t change anything).

 

EDIT#2: Booting with -x32 or -v arch=i386 or -legacy doesnt change a thing.

It refuses to run in 32 Bits. :) After like trying 20 different boot and plist methods still nothing, nothing, nothing ... i can´t believe this! *lol* ...

Link to comment
Share on other sites
EnzoFX
EnzoFX
Posted
Posted

Just used the installer, worked perfectly. First on a USB drive, used it to boot Lion 10.7.2. Then on my Chameleon partition. When it installed on my Cham partition it skipped writing boot0md, which I know is fine, but why not just write the new one?

 

I was running 1174 (the last BlackOSX recommended on the EP45 thread! =)), and it wasn't booting 10.7.2, it stalled at waiting for root device. Works just fine now with 1620. Thanks!

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

Thanks for replying with feedback from using the beta package installer EnzoFX :)

 

After 561 downloads, it's a shame nobody else has bothered reporting their experiences. I have ideas to make it better but I won't do any more work on it until I know if it's working for everyone or not.

 

but why not just write the new one?

Well the boot0 code doesn't change very often so I thought why re-write the same code if it's not necessary. It will write a different version of boot0 if it thinks your drive need it.

 

I was running 1174 (the last BlackOSX recommended on the EP45 thread! =)), and it wasn't booting 10.7.2, it stalled at waiting for root device. Works just fine now with 1620. Thanks!

You can still keep up to date with the latest Chameleon changes at the forge and download the binaries created by the buildbot whenever you like. Just test the new version on a USB flash drive first before committing to your HDD to make sure everything is working for you first.

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
Unfortunately, there´s no plist like this one?

(Went to /Library/Preferences/SystemConfiguration).

There´s only the classic com.apple.Boot.plist. (Where i tried arch & i386 as well - no luck).

Chameleon uses a folder named /Extra to work from. In most cases, when starting out you will have to create your own /Extra folder and fill it will the files required for your system hardware. This is where the /Extra/org.chameleon.Boot.plist belongs. The package installer here will create an /Extra folder for you and populate it only with Modules, Themes and an org.chameleon.Boot.plist if those required options are selected when running the installer.

 

/Library/Preferences/SystemConfiguration is where Apple's com.apple.Boot.plist lives. You don't need to touch that, just work with the /Extra/org.chameleon.Boot.plist.

 

If it helps i installed this distri:

http://www.insanelymac.com/forum/index.php?showtopic=259253

(Also with legacy kernel, not sure if this has something to do with 32/64 Bits, guess not).

I had a quick look at regae's BootCD and interestingly I see it has an older version of the original Chameleon installer script which I'd previously edited/changed. Did it install Chameleon correctly for you? as I'm not sure the fdisk440 binary will be correctly located with that as it had been changed since? (though I don't know for sure as I haven't tried running it).

 

Anyway.. I see it references nawcom's kernel which I think you have installed. I don't know if that is the cause for you not being able to boot the OS X kernel in 32-bit mode but I wouldn't have thought so. I think it's a simple issue of you not using the correct /Extra/org.chameleon.Boot.plist.

 

Forgive my stupidity - do i have to look somewhere else for the org.Chameleon.Boot.plist?

See above

 

EDIT: Now i read somewhere else you can RENAME (?) com.apple.Boot.plist to org.chameleon.Boot.plist. Did that. Wonder why the machine even starts? (And it doesn´t change anything).

Did you rename the one in /Extra or /Library/Preferences/SystemConfiguration ?

 

EDIT#2: Booting with -x32 or -v arch=i386 or -legacy doesnt change a thing.

It refuses to run in 32 Bits. :P After like trying 20 different boot and plist methods still nothing, nothing, nothing ... i can´t believe this! *lol* ...

Double check you are using /Extra/org.Chameleon.Boot.plist

Link to comment
Share on other sites
sonicfire
sonicfire
Posted
Posted
Chameleon uses a folder named /Extra to work from. In most cases, when starting out you will have to create your own /Extra folder and fill it will the files required for your system hardware. This is where the /Extra/org.chameleon.Boot.plist belongs. The package installer here will create an /Extra folder for you and populate it only with Modules, Themes and an org.chameleon.Boot.plist if those required options are selected when running the installer.

 

Thanks, that was new to me. Something learned. On my maindrive (i only have one HDD in the machine) there´s an /Extra folder,yes. Contains the org.chameleon.Boot.plist and folders like Modules and Themes. There i also edited the Boot.plist and added

<key>arch</key>
<string>i386</string>

Did a reboot - still 64 Bits...

 

/Library/Preferences/SystemConfiguration is where Apple's com.apple.Boot.plist lives. You don't need to touch that, just work with the /Extra/org.chameleon.Boot.plist.

 

Ok, thanks!

 

I had a quick look at regae's BootCD and interestingly I see it has an older version of the original Chameleon installer script which I'd previously edited/changed. Did it install Chameleon correctly for you? as I'm not sure the fdisk440 binary will be correctly located with that as it had been changed since? (though I don't know for sure as I haven't tried running it).

 

Anyway.. I see it references nawcom's kernel which I think you have installed. I don't know if that is the cause for you not being able to boot the OS X kernel in 32-bit mode but I wouldn't have thought so. I think it's a simple issue of you not using the correct /Extra/org.chameleon.Boot.plist.

 

Oh, okay! It installed everything fine, running great from the beginning. (Except no working Audio and Ethernet, but that´s currently not that important, i plan to use the external FW Audiointerface and the Machine won´t connect to the internet anyway soon).

 

Did you rename the one in /Extra or /Library/Preferences/SystemConfiguration ?

The one in /Library(...). Now that i know that i shouldn´t touch it the question or the idea is obsolete i think.

 

Double check you are using /Extra/org.Chameleon.Boot.plist

 

How can i verify, Chameleon is using this Boot.plist? Or in other words, where to specify what Boot.plist to use? Can you help me on that?

 

Oh and one big thing, that i noticed:

From somewhere else i read, before you Boot up your machine / When the chameleon bootloader appears, you can press TAB and then type "arch=i386". And guess what - IT WENT 32 BIT !!!

Now if i only could make that permanent.

 

Thanks for help!

Link to comment
Share on other sites
EnzoFX
EnzoFX
Posted
Posted
You can still keep up to date with the latest Chameleon changes at the forge and download the binaries created by the buildbot whenever you like. Just test the new version on a USB flash drive first before committing to your HDD to make sure everything is working for you first.

 

That's definitely painless, but I think people sometimes (myself included haha), can't justify simply going with the latest one available. People usually stick with what's working for them and that's probably a recommended one that was in a guide they followed. We're aware at how builds can vary. Take the Lion FaceTime issue. People had to track down the older and then newer versions that implemented the fix. I also had a hard time finding what userkenelcache does and if I should use it =P. General fixes like these could be publicly and widely announced (New known issues as well).

 

With that said, The Cham blog really needs some action. Most of us could benefit from easy to find updates/info. This may be harder now that it's so actively developed, but it should be do-able in some form. It is easy to see why a source like the tonymacblog has become so popular, it's a centralized source of constant news/recommendations/reference builds/issues/etc. with lots of feedback.

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
I try your latest "commit(1629)" and now on the EFI system the boot-loader is correctly updated!

Congratulations! Good Job!

Thanks for testing and confirming it's working.

I'll post a revised installer soon after I've finished working on the next addition.. :(

 

That's definitely painless, but I think people sometimes (myself included haha), can't justify simply going with the latest one available. People usually stick with what's working for them and that's probably a recommended one that was in a guide they followed.

Fair point, though by not keeping up with the on-going changes it becomes hard to know what's been changed and why. So testing a release say 300 revisions newer than one used previously is bound to provide many questions.

 

We're aware at how builds can vary. Take the Lion FaceTime issue. People had to track down the older and then newer versions that implemented the fix.

It's only with regular testing and feedback to the Chameleon forge can points like this be identified sooner. If more users tested the new revisions on a bootable USB flash drive then they could A: not mess with their main installation on HDD, B: test for problems with the latest revisions and C: keep up to date with the latest and greatest.

 

I also had a hard time finding what userkenelcache does and if I should use it =P. General fixes like these could be publicly and widely announced (New known issues as well).

I understand your concerns as for as long as I've been playing with hacks, all knowledge I've gained has come from searching, reading, testing and communicating with others. The kernelcache fix had been discussed a few times here at InsanelyMac and most probably lots of other places too but as you've said, its all about finding that information in the first place.

 

There's so much to take in with this subject and there's plenty I don't know about and probably never will unless the need arises for me to find out, so yes, it would be useful to have one central place where everything was discussed. I guess that's why the voodooproject's forum was created, but the problem is not everyone uses it and those that do might not have the time or appropriate knowledge to make such announcements.

 

With that said, The Cham blog really needs some action. Most of us could benefit from easy to find updates/info. This may be harder now that it's so actively developed, but it should be do-able in some form.

Which blog are you referring to?

I guess the best there is from the forge is the updates and changes

 

It is easy to see why a source like the tonymacblog has become so popular, it's a centralized source of constant news/recommendations/reference builds/issues/etc. with lots of feedback.

I don't often visit there, but I do see a lot of talk posted about it.

 

For the new chameleon do we still need to generate an mkext in the extra folder?

I haven't used an /Extra/Extensions.mkext for a long time, and 10.7 no longer uses one for the system.

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

I have a new TEST installer. Now v1630 and replaces the previous v1620.

 

The changes include a fix to a bug with the EFI system partition installation and an attempt to catch whether or not the user is trying to install a secondary boot partition to the same disk. If they are and if there's a possibility of a b1f:error or boot1:error then the installer will attempt to fix potential problems.

 

As before,

So to anyone who would like to test this, please do so on a test rig and understand that this is a beta.

If for any unlikely reason that data loss should occur, I will not be held responsible. You test this at your own risk.

 

I look forward to hearing any feedback.

 

Thanks

 

EDIT:

20th October 16:40 - v1630 removed. New v1640 beta posted here in post #1033

Link to comment
Share on other sites
EnzoFX
EnzoFX
Posted
Posted

Running 1630 now. Thanks =). Just ran it on the Main install, figured I had the USB as a backup haha. Installed just the same as 1620. I was hoping it'd fix my iCloud login issue, which I just read there was a fix for in 1627, but no go. I'll have to keep trying the other solutions =P.

 

Oh, and I was referring to this old blog: chameleon.osx86.hu

=P. Of course something else could take it's place, I think it just comes down to the right people to more or less track what's going on in the development scene/forums and putting it up in a more user friendly (User friendly explanations as well, Like a blog) place. Not to mention the added benefit of more feedback. That Changes/Updates link is great, thanks.

 

Edit:

Just tried this 1627 from this first post: http://www.insanelymac.com/forum/index.php?showtopic=269425

Fixed my iCloud login issue.

Link to comment
Share on other sites
sonicfire
sonicfire
Posted
Posted
How can i verify, Chameleon is using this Boot.plist? Or in other words, where to specify what Boot.plist to use? Can you help me on that?

 

Oh and one big thing, that i noticed:

From somewhere else i read, before you Boot up your machine / When the chameleon bootloader appears, you can press TAB and then type "arch=i386". And guess what - IT WENT 32 BIT !!!

Now if i only could make that permanent.

 

Thanks for help!

 

....so can anyone *PLEASE* help me with this?

Link to comment
Share on other sites
EnzoFX
EnzoFX
Posted
Posted
....so can anyone *PLEASE* help me with this?

 

The org.chameleon.Boot.plist file that's used is at the root of the volume Cham is installed in, in the folder /Extra/

 

As for it booting 32-bit, this should have worked:

<key>arch</key>

<string>i386</string>

Strange, though I remember a long time ago an option being set in the boot.plist and it not working for me, so I ended up putting it in the "Kernel Flag's section of the same boot.plist and it worked. So could try putting arch=i386 into Kernel Flags section =P.

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
....so can anyone *PLEASE* help me with this?

You can verify Chameleon is using /Extra/org.chameleon.Boot.plist by changing or adding a boot option. Why don't you try the ShowInfo boot option? By default, when you see Chameleon's GUI, it'll present you with details on the currently selected partition and resolution.

 

To turn it off you will want to add the boot option to /Extra/org.chameleon.Boot.plist as follows:

	<key>ShowInfo</key>
<string>No</string>

or to turn it on, 

	<key>ShowInfo</key>
<string>Yes</string>

Note: If you have the following boot option then the ShowInfo option will be overruled, so make sure this is not present.

	<key>Boot Banner</key>
<string>No</string>

Try it now, then reboot and see what difference it makes. If you see a difference then you know that /Extra/org.chameleon/Boot.plist is being used.

 

As for typing a command at the Chameleon's GUI or text menu, this is a useful option for testing before making a permanent addition to /Extra/org.chameleon.Boot.plist. The fact that typing arch=i386 works to boot the OS X kernel in to 32-bit mode, shows you that Chameleon is functioning correctly and either A ) The org.chameleon.Boot.plist which you have been editing is not the one Chameleon is using, or B ) you have an error in your org.chameleon.Boot.plist.

 

Let me know what you find.

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
Running 1630 now. Thanks =). Just ran it on the Main install, figured I had the USB as a backup haha. Installed just the same as 1620.

Thanks for testing Enzo

 

I was hoping it'd fix my iCloud login issue, which I just read there was a fix for in 1627, but no go. I'll have to keep trying the other solutions =P.

I'm only working on the package installer and (I think) the Chameleon source in my branch is the same as the latest trunk. I merged it only recently. The current trunk has the Boot-UUID / chosen code (FaceTime/iCloud fix) removed as it caused issue for RAID users.

 

Oh, and I was referring to this old blog: chameleon.osx86.hu =P.

Ah. yes. Sorry to have not grasped that first time round. Well as far a as I know, that blog was superseded by the voodooproject's forum and so hasn't been updated.

 

Of course something else could take it's place, I think it just comes down to the right people to more or less track what's going on in the development scene/forums and putting it up in a more user friendly (User friendly explanations as well, Like a blog) place. Not to mention the added benefit of more feedback.

Absolutely, but it's all down to finding the person(s) to do it. Everyone involved that I know of volunteers their free time and for most it's a hobby. The developers time it wisely spent developing and the testers time is spent testing. I'm all for what you ask, it's just getting it going. I started putting together some Chameleon documentation the other day, but thats going to have to be a work in progress as I don't have the time to devote as I'd like.

 

That Changes/Updates link is great, thanks.

Yeah. It's a snapshot of now and a place to keep abreast of what's going on.

 

Just tried this 1627 from this first post: http://www.insanelymac.com/forum/index.php?showtopic=269425

Fixed my iCloud login issue.

I understand there's a desire to have a Chameleon build with the fix, hence why builds like that are popping up. You also have the option of using the slightly tweaked Chameleon branch named Chimera, the totally re-worked Chameleon stage 2 loader named RevoBoot, XPC or [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]. All I know is the Chameleon devs have said a fix will be added to the branch when one had been found to be compatible with RAID users.

  • Like 1
Link to comment
Share on other sites
jack kyle
jack kyle
Posted
Posted

<Update! Culprit found: its the Resolution module finally!! >

Deleting it allows chameleon to boot effortlessly Lion and have my graphic card works natively :)

It seems the graphic module refuse my 15" samsung CRT monitor :thanks_speechbubble:

Wild Guess: I think it finds my disabled intel igp in the dsdt and patch the vesa mode which hangs my Ati R5770 card :|

 

We need a simple command line at chameleon boot and in the .plist to disable it (if it doesn't exist yet).

instead of running windows7 with macdrive and deleting the module :P

<Thanks to all who helped me keep looking :) >

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

I am sorry but I don't know where to post my cry for help :P

Chameleon don't work anymore for me since the last working version :Chameleon-2.0-RC5-r760 !

I have an asus eah5770 CUcore (pciexpress ati r5770 1go) graphic card which was natively supported by osx without any injection or kext (had graphic enabler yes).

I recently tried updating my osx10.6.6 to lion 10.7.1 and found out that all versions after rc5 r760 don't even show their menu on my screen even if I plug in at the same time all the video outputs to my monitors. (used official rc5 installers and 2.1 svn installers)(tried r828 installer then up to 2.1 svn 1630 other branches too like chimera...)

 

now as soon as the boot starts up, my screen goes to blank. can't even see what i type. and osx doesn't finish the boot( used old version in 10.6.6 and 10.7.1 and enabled vnc) as soon as I use a recent version even 10.6.6 stops working.

thank god Chameleon-2.0-RC5-r760 makes lion work but I can't then upgrade like other mac enthusiast :wallbash:

I now use Chameleon-2.0-RC5-r760 with lion 10.7.1 with my 5770 without any injection or kext like in 10.6.6. there is one difference though is that I don't need to use the kvm switch and plug both dvi and vga output. now in lion it works just like in windows7 without a hitch natively. of course opencl and opengl works natively like in 10.6.6.

 

I tried all possible chameleon parameter related to graphic card (efi injection, on off, vanilla/original bios, ati ports ....) chameleon svn or rc5 760+ just don't boot my external graphic card.

I even enable or disable my custom dsdt without any success (DSDT have all beside the pci0 peg... ati card's dsdt couldn't edit others safely and make one).

I have the connectors info and my Graphic card bios and extracted my efi graphic string if anyone can help (T_T).

 

I am lost :(

 

I even found that my graphic card can be used to upgrade original macs natively :P

 

Thanks to anyone that can help :)

 

Hackintosh specs:

CPU: intel core 2 duo e6600 at 2400mhz (chameleon shows it in osx lion as core 2 solo even smbios cpu type edit or cpu=2 in chameleon don't help?! (was good in snow)).

RAM: 2*2 go kingston at 800mhz

MotherBoard: asus p5g41-m le (has intel igp disabled)(hopefully enabling it helped me install lion with new chameleon the after boot switch back to r760 and disabling the igp again :( )

HDD: sata.

my final kexts in lion's extra:fakesmc, intelcpumonitor, superiofamily

AUDIO: creative audigy

Link to comment
Share on other sites
DarwinX
DarwinX
Posted
Posted
I am sorry but I don't know where to post my cry for help :P

Chameleon don't work anymore for me since the last working version :Chameleon-2.0-RC5-r760 !

I have an asus eah5770 CUcore (pciexpress ati r5770 1go) graphic card which was natively supported by osx without any injection or kext (had graphic enabler yes).

I recently tried updating my osx10.6.6 to lion 10.7.1 and found out that all versions after rc5 r760 don't even show their menu on my screen even if I plug in at the same time all the video outputs to my monitors. (used official rc5 installers and 2.1 svn installers)(tried r828 installer then up to 2.1 svn 1630 other branches too like chimera...)

 

now as soon as the boot starts up, my screen goes to blank. can't even see what i type. and osx doesn't finish the boot( used old version in 10.6.6 and 10.7.1 and enabled vnc) as soon as I use a recent version even 10.6.6 stops working.

thank god Chameleon-2.0-RC5-r760 makes lion work but I can't then upgrade like other mac enthusiast ;)

I now use Chameleon-2.0-RC5-r760 with lion 10.7.1 with my 5770 without any injection or kext like in 10.6.6. there is one difference though is that I don't need to use the kvm switch and plug both dvi and vga output. now in lion it works just like in windows7 without a hitch natively. of course opencl and opengl works natively like in 10.6.6.

 

I tried all possible chameleon parameter related to graphic card (efi injection, on off, vanilla/original bios, ati ports ....) chameleon svn or rc5 760+ just don't boot my external graphic card.

I even enable or disable my custom dsdt without any success (DSDT have all beside the pci0 peg... ati card's dsdt couldn't edit others safely and make one).

I have the connectors info and my Graphic card bios and extracted my efi graphic string if anyone can help (T_T).

 

I am lost :(

 

I even found that my graphic card can be used to upgrade original macs natively :P

 

Thanks to anyone that can help :)

 

Hackintosh specs:

CPU: intel core 2 duo e6600 at 2400mhz (chameleon shows it in osx lion as core 2 solo even smbios cpu type edit or cpu=2 in chameleon don't help?! (was good in snow)).

RAM: 2*2 go kingston at 800mhz

MotherBoard: asus p5g41-m le (has intel igp disabled)(hopefully enabling it helped me install lion with new chameleon the after boot switch back to r760 and disabling the igp again :( )

HDD: sata.

my final kexts in lion's extra:fakesmc, intelcpumonitor, superiofamily

AUDIO: creative audigy

 

After you updated the Chameleon, did you rename your com.apple.Boot.plist to org.chameleon.Boot plist?

Link to comment
Share on other sites
Noisema
Noisema
Posted
Posted

Maybe here is not the right place to ask but I'll give it a try as I couldn't find further clear information trough a search on this forum and by searching with Google. Feel free to move to an other thread if needed ;)

 

I have a core i7 950 used on an p6X58D-E which seems to have a bit of problems with MTRR during boot (slow boot/slow redering of images during OS selection/text). For more info see here: http://forge.voodooprojects.org/p/chameleon/issues/113/

 

So now I'm wondering the following:

- What does MTRR do exactly? (I looked up the definition on Wikipedia but was not able to get clear what it does exactly, or better said I could use some layman's terms to get a better understanding about what it does).

- In which way does it affect the operation of OS X? Does it affect only during booting the OS, or could may it cause problems/give slowdowns when OS X is running?

- What is needed to solve this issue? I see it's planned for the Chameleon 2.1 final release, but I'm wondering if there's another way to solve it or to use a workaround for this.

 

Anyway, I'm willing to test if needed, hopefully I can help out others with this too.

 

Thanks in advance :(

Link to comment
Share on other sites
jack kyle
jack kyle
Posted
Posted
After you updated the Chameleon, did you rename your com.apple.Boot.plist to org.chameleon.Boot plist?

I did, yes :)

also pciroot and all other tries didn.t work.

I guess its something that hapened between rev 760 and 828. maybe the kabyl ati init or something else...

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