Jump to content

Chameleon 2.4svn Official PKG Installer

ErmaC

By ErmaC,
in Chameleon

 Share
4,261 posts in this topic

Recommended Posts

HUSABER
HUSABER
Posted
Posted

 

 

Agreed, Clover is the future, no doubt.

 

But do not underestimate Chameleon, because is easy to use and is starting point for a long time... so much that everyone can give simple advice to new users. 
.....and the second step can be Clover, after obtaining the Desktop in OSx.
 
In this moment I can boot using Chameleon or Clover in UEFI mode,  because they are both on my hard drive, and can coexist.
 
And maybe some changes will come  to not disturb Clover operating in legacy mode..........(in testing) ;)
 

 

 

Chameleon last work well on DP2...try to upgrade :thumbsup_anim: i like this more than Clover :hysterical:

Link to comment
Share on other sites
crusher
crusher
Posted
Posted

My boot fast,but my reboot is vey slow!

My ocbp is:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Default Partition</key>
	<string>hd(0,2)</string>
	<key>DropSSDT</key>
	<string>Yes</string>
	<key>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>Graphics Mode</key>
	<string>1920x1200x32</string>
	<key>GraphicsEnabler</key>
	<string>Yes</string>
	<key>Kernel</key>
	<string>/System/Library/Kernels/kernel</string>
	<key>Kernel Flags</key>
	<string>darkwake=0 -xcpm</string>
	<key>ShowInfo</key>
	<string>Yes</string>
	<key>Timeout</key>
	<string>2</string>
</dict>
</plist>
Link to comment
Share on other sites
pinarek
pinarek
Posted
Posted

I have read in Download section for new Chameleon 2388 and 2390 this:

This revision of Chameleon contain the FileNVRAM revision 1.1.3
Spoiler

WHERE is ist ?? i can not find this 

 

when copy my FileNVRAM.dylib (is Version 1.1.3) from my Mavericks /Extra/modules  in Extra/modules in Yosemite.. not boot !!

 

Where is the Problem with this ?

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

I have read in Download section for new Chameleon 2388 and 2390 this:

This revision of Chameleon contain the FileNVRAM revision 1.1.3
Spoiler

WHERE is ist ?? i can not find this 

 

when copy my FileNVRAM.dylib (is Version 1.1.3) from my Mavericks /Extra/modules  in Extra/modules in Yosemite.. not boot !!

 

Where is the Problem with this ?

 

Yep I'm going to update the post...

but for any problem related with module please use the apposite topic -> FileNVRAM 1.1.3 Released

 

ErmaC

  • Like 1
Link to comment
Share on other sites
pinarek
pinarek
Posted
Posted

Ermac... thank you for this

 

 

So very disappointing, by now so many new Chameleonänderungen it is not possible to use iMessage and FaceTime, etc.,
just because it is not possible (which at Mavericks makes no problems) use the Filenvram.dylib. 
 
Will you love developer you probably finally deal with it! ? 
So the chameleon is currently unusable because yes this is for ME and many others, use the iMessage very important. 
 
At least Clever is the iMessage, although only under incorrect machine code (as a Mac mini Server 6.2) even though I have a hack than iMac 13.1.
But at least faring iMessage with a strange serial number and UUID other than Mavericks, but it works! 
 
I was always ready to work for chameleon so that it seemingly nothing but the best will be, you have to continue to use Clever, Sad but true.
Just because none of you developers are willing, this will not work to fix by iMessage.
 
And one Problem with my Intel HD4000 set ig-platform-id in Chameleon not work.. in Clover with only the Option "inject" by Intel work best !
 
Here see the errors in Chameleon an one Picture:
 
The right side is under Clover
 

post-6397-0-44484300-1403822019_thumb.png

post-6397-0-90287100-1403822406_thumb.png

Link to comment
Share on other sites
crusher
crusher
Posted
Posted

@Micky1979

I boot my Yosemite after use UseKernelCache=No

Look bdmesg and my ocbp.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>DropSSDT</key>
	<string>Yes</string>
	<key>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>Graphics Mode</key>
	<string>1920x1200x32</string>
	<key>GraphicsEnabler</key>
	<string>Yes</string>
	<key>Kernel Flags</key>
	<string>darkwake=0 -xcpm</string>
	<key>ShowInfo</key>
	<string>Yes</string>
	<key>Timeout</key>
	<string>2</string>
	<key>UseKernelCache</key>
	<string>No</string>
</dict>
</plist>
Link to comment
Share on other sites
The Real Deal
The Real Deal
Posted
Posted

Hi,

I used cham R2378 for weeks without trouble.

 

I just updated to r2391 and my installation is in trouble lol.

 

can't find mach kernel, i press a touch, boot verbose is lauching, then stuck at XPCM.

 

I used 10.9.4.

 

Any help would be appreciated, thanks.

 

 

Also

    <key>Kernel</key>
    <string>mach_kernel</string>

does not work despite the kernel is at the root of my installtion :/

Link to comment
Share on other sites
The Real Deal
The Real Deal
Posted
Posted

Hi Micky,

I have added the flag after for purpose but in both cases same message. I booted via a USB pen ; i have an Extra mirrored on the USB pen and at the root of the OS partition. Cache is rebuild, permissions repaired, etc, i tried with usekernelflag Y/N. nvm, i don't want to bother as i'm not 100% sure it's bootloader related.

Link to comment
Share on other sites
Bit Shoveler
Bit Shoveler
Posted
Posted

I finally found a workaround to my linker woes of a couple months ago: remove the '-x' option from the offending 'ld' command.

 

Working under latest XCode on 10.9.4. 'svn diff' below shows the change.

hackintosh_eth0:trunk chucko$ svn diff i386/modules/MakeInc.dir
Index: i386/modules/MakeInc.dir
===================================================================
--- i386/modules/MakeInc.dir	(revision 2390)
+++ i386/modules/MakeInc.dir	(working copy)
@@ -126,7 +126,7 @@
 	@ld -arch i386 \
 	-alias _$(MODULE_START) start \
 	-dylib -read_only_relocs suppress \
-	-S -x -Z -dead_strip_dylibs \
+	-S -Z -dead_strip_dylibs \
 	-no_uuid \
 	-current_version $(MODULE_VERSION) -compatibility_version $(MODULE_COMPAT_VERSION) \
 	-final_output $(MODULE_NAME) \
hackintosh_eth0:trunk chucko$

Well, grump. I hadn't tried to build Chameleon in a while and updated from the SVN repo. First the build barfed on unused functions. So I #ifdef'd them out. Then the linker blew up in uClibcxx.

 

Turns out the problem is Apple's custom version of ld. If code is compiled with Link Time Optimization, and the linker is set to do dead code stripping, the linker fails. Apple is aware of the problem but doesn't seem to have a fix yet.

 

If you have the latest XCode 5.1 installed on Mavericks 10.9.2, how do you build Chameleon?!

 

  • Like 3
Link to comment
Share on other sites
Pike R. Alpha
Pike R. Alpha
Posted
Posted

Q: Anyone here wants black boot mode to function in Chameleon?

 

Use my patch from here and add this to bootstruct.h

#ifndef kBootArgsFlagRebootOnPanic
#define kBootArgsFlagRebootOnPanic (1 << 0)
#endif

#ifndef kBootArgsFlagHiDPI
#define kBootArgsFlagHiDPI (1 << 1)
#endif

#ifndef kBootArgsFlagBlack
#define kBootArgsFlagBlack (1 << 2)
#endif

#ifndef kBootArgsFlagBlackTheme
#define kBootArgsFlagBlackTheme (1 << 6)
#endif 

and this to: bootstruct.c

#if REBOOT_ON_PANIC
bootArgs->flags = kBootArgsFlagRebootOnPanic;
#endif

#if UISCALE_2X
bootArgs->flags |= kBootArgsFlagHiDPI;
#endif

#if BLACKMODE
// This sets IODeviceTree:/chosen/IOProgressColorTheme (Number) to 0x1
bootArgs->flags |= (kBootArgsFlagBlack + kBootArgsFlagBlackTheme);
#endif

That's the most important thing you need. Implement like whatever suits you best.

  • Like 3
Link to comment
Share on other sites
  • 2 weeks later...
 Share
Go to topic listing
×
×
  • Create New...