Jump to content
janek202

Chameleon Wizard - Utility for Chameleon.

681 posts in this topic

Recommended Posts

New test version.

 

http://dl.dropbox.com/u/7085278/Chameleon_...aller/CW_TV.zip

 

Added French translation and updated Chinese ones.

Added new Mac Minis sbioses + serial generations.

 

Added new Info.plist keys: "Skip revision check at startup" and "Skip revision check always". Setting it to <true/> should prevent crashing on systems with raid.

 

However Chameleon Wizard does not support raid volumes and probably never will.

 

A small aesthetic issue. In EFI mode, when I select 'Target partition' = EFI, the description displays wrongly: 'No chameleon installed on selected partition'.

Works fine here.

Share this post


Link to post
Share on other sites
Advertisement
Added new Info.plist keys: "Skip revision check at startup" and "Skip revision check always". Setting it to <true/> should prevent crashing on systems with raid.

 

However Chameleon Wizard does not support raid volumes and probably never will.

 

Works fine here.

 

That's OK.

For Raid volumes, we have to use EFI partition for /Extra and boot, so every things are yet here to work. I can see EFI partitions on the combo box but the mount menu did not work (even on my USB key).

 

Fr translation update:

fr.lproj.zip

Share this post


Link to post
Share on other sites

Hello!

 

Excellent app, janek and by this app you helped me a lot!

 

By this app I could update easily my chameleon and I love it.

 

But I have a very annoying problem.

 

History

My currently installed Chameleon's version is 1465 and putting GraphicsEnabler to Yes in this version makes my OSX to recognize my VGA much better. (I have a VTX3D Radeon 5670 device id: 68B9).

I'm using Lion for months and I had QE/CI without problems after putting my device id to the right kexts. but! A few applications simply crashed on launch( DVD Player, Counter-Strike Source, Team Fortress, Heroes of Newerth).

 

After installing the new Chameleon and putting GE to Enabled my OSX can start ALL of these applications without problems.

 

But. Right now the OSX doesn't recognizing the right settings for my monitor. It does detects that I have two monitors attached and only lets me to set 4:3 ratio resolutions so I can't use my monitor's native resolution which is 1440x900

 

The dual-monitor recognizing isn't a true problem because in system prefrences I set the second monitor to mirroring so that does not matter anymore.

 

The question is: How can I make my OSX or chameleon or whatever to detect the right resolutions? Can I extract the right information from a well-working status? Because I can boot by an older chameleon if needed.

Can I force a resoltion somehow or is there any method?

 

Thank you,

Chris

Share this post


Link to post
Share on other sites

Since day 1 my ati hd4870 card just worked out of the bos and still does except if i dont use GraphicsEnabler to Yes in the boot my source games wont load they just crash so GraphicsEnabler to Yes is a good idea even if card works out of box

Share this post


Link to post
Share on other sites
Since day 1 my ati hd4870 card just worked out of the bos and still does except if i dont use GraphicsEnabler to Yes in the boot my source games wont load they just crash so GraphicsEnabler to Yes is a good idea even if card works out of box

 

Yes, GraphicsEnabler=Yes helps me to get everything working. But by this I can't get wide-screen resolution on my monitor only 4:3 resolutions are allowed.

So somehow I have to tell my osx or vga or chameleon that I'm having a wide-screen monitor with native 1440x900 resolution.

Share this post


Link to post
Share on other sites
New test version.

 

http://dl.dropbox.com/u/7085278/Chameleon_...aller/CW_TV.zip

 

Added French translation and updated Chinese ones.

Added new Mac Minis sbioses + serial generations.

 

Added new Info.plist keys: "Skip revision check at startup" and "Skip revision check always". Setting it to should prevent crashing on systems with raid.

 

However Chameleon Wizard does not support raid volumes and probably never will.

 

 

Works fine here.

 

 

hello janek

 

i revised the portuguese from Portugal translation , little mistakes

 

en.lproj.zip

 

tanks four yours good work

Share this post


Link to post
Share on other sites

All translations included in the latest version.

 

Also added new feature: Premade SMBios and Serial generator updater. Now there's no need to update whole application only to add new items.

Share this post


Link to post
Share on other sites
I use them as my itx build is spec wise identical to a mac mini 5,1 and my old one was an almost copy of the 3,1 one.

The 3,1 one has worked for almost 3 years now without issues!

For me it would be no problem getting all the different values for the MacBook air.

One final thing about mac mini 5,x, since the HD3000 can be made to work now using a macmini5,1 smbios does make a lot of sense. Just to bad I have HD2000 on my cpu now and that can't be made to work yet.

 

If you want to use the HD2000 without acceleration, but else full resolution and even dual / triple monitors you can do the following:

 

This is based on the standard 10.7.1 version of the AppleIntelxxGraphicxx kexts, the 10.7.1 update (updated / later build) for the Macmini5,1 AppleIntelxxGraphicxx kexts are not tested yet...

 

0. Enable screen sharing as the very first thing you do and verify that it works - then you can later connect and fix any problems as if the connector tables are wrong or do not match you motherboard you will get stuck in various variants of the grey boot screen.. The system are still up and running, but only have not connected properly to the motherboard connectors, but screen sharing works...

1. Use "Graphics Enabler = No" with Chameleon Wizard (/E/org.Chameleon.Boot.plist)

2. Use Macmini5,1 in the smbios.plist (change the MacMini text string to Macmini to get proper representation in the SystemInformation and in finder of other Mac´s)

3. Remove the device id (0x01028086 or what your system shows as the id) from the Gen6 - IOPCIPrimaryMatch string in the info.plist /S/L/E/AppleIntelHDGraphics.kext

4. In the info.plist of the /S/L/E/AppleIntelSNBGraphicsFB.kext - the device id (0x01028086) should only be found in the IOPCIPrimaryMatch of the AppleIntelSNBGraphicsController2 section and NOT in the AppleIntelSNBGraphicsFB section..

NB! the device id should be found ONLY once in this info.plist...

5. If the display connectors do not work properly with your motherboard - inject the proper data with this method:

http://www.tonymacx86.com/viewtopic.php?f=15&t=30464

6. In the BIOS setup allocate the maximum amount of shared RAM to the HD2000/3000 graphics

 

Now the HD2000 should work with full resolution and the IORegistryExplorer and SystemInformation should display it as a Intel HD3000 with 512MB (8GB system RAM), 384MB (4GB system RAM) or 288MB (2GB system RAM).

If you use "Graphics Enabler = Yes" it will be displayed as a "unknown GPU" so Chameleon do not work properly with the device id´s of the HD2000 yet...

 

The majority of motherboards cannot assign the full 512MB shared RAM so to avoid graphics distortion / glitches you can reduce the system RAM so the BIOS setup of shared RAM and the rapported use of VRAM match...

This is a motherboard issue / fault as there are motherboards around that can assign up to above 1600MB to the Intel HD graphics..

Share this post


Link to post
Share on other sites
All translations included in the latest version.

 

Also added new feature: Premade SMBios and Serial generator updater. Now there's no need to update whole application only to add new items.

 

Hi janek202,

Thanks for continued support :thumbsup_anim:

The new version does not see my old SMBios... am I missing something?

post-702132-1315137994_thumb.png post-702132-1315138020_thumb.png

The wizard does not see what Chameleon sees on my Hack :unsure:

Share this post


Link to post
Share on other sites
All translations included in the latest version.

 

Also added new feature: Premade SMBios and Serial generator updater. Now there's no need to update whole application only to add new items.

 

Is it possible to make some changes to the "GraphicsEnabler = Yes" function in org.chameleon.Boot.plist??

Intel HD2000 graphics with device id 0x01028086 are identified as "Unknown".

 

With "GraphicsEnabler = No" it is identified (wrongly?) as Intel HD3000..

 

Is it also possible to change the SMproductname from MacMini5,1 to Macmini5,1 in the smbios.plist generator??

For my setup the MacMini5,1 gives the picture of a monitor in both "about this mac" and in finder of other Mac´s.

Macmini5,1 gives the correct Mac mini picture in both instances.

 

The SMfamily name MacMini also gives some strange behaviors.

Macmini or Mac mini works better...

 

Thanks for the Chameleon Wizard :(

Share this post


Link to post
Share on other sites
Is it possible to make some changes to the "GraphicsEnabler = Yes" function in org.chameleon.Boot.plist??

Intel HD2000 graphics with device id 0x01028086 are identified as "Unknown".

 

With "GraphicsEnabler = No" it is identified (wrongly?) as Intel HD3000..

It's an issue with Chameleon bootloader, not my application. I'm not a chameleon developer, I can't do anything about that.

 

Is it also possible to change the SMproductname from MacMini5,1 to Macmini5,1 in the smbios.plist generator??

For my setup the MacMini5,1 gives the picture of a monitor in both "about this mac" and in finder of other Mac´s.

Macmini5,1 gives the correct Mac mini picture in both instances.

 

The SMfamily name MacMini also gives some strange behaviors.

Macmini or Mac mini works better...

 

Should be ok now. Update the Premade SMBioses database by clicking on the refresh button.

Share this post


Link to post
Share on other sites
Should be ok now. Update the Premade SMBioses database by clicking on the refresh button.

 

There is still an "bug" with the Chameleon Wizard app.

 

If the SMfamily name are written with a "M" in Mini either as "MacMini" or "Mac Mini" Chameleon Wizard displays the correct picture of a Mac mini.

 

If the SMfamily name are written with a "m" in mini either as "Macmini" or "Mac mini" Chameleon Wizard displays the picture of monitor and not the picture of a Mac mini.

 

In "about this Mac" / Systeminformation there is the correct picture and the text "Mac mini" so this works and it is only a display issue with Chameleon Wizard.

 

The issues with SMproduct was cured with the Macmini5,1 fix.

Share this post


Link to post
Share on other sites
If the SMfamily name are written with a "m" in mini either as "Macmini" or "Mac mini" Chameleon Wizard displays the picture of monitor and not the picture of a Mac mini.

 

I know. I arleady fixed the code. But it's not that big issue, that requires release of the whole new version right now.

 

Edit: Never mind I fixed some other bugs. Released.

Share this post


Link to post
Share on other sites
Could you make a screenshot of your /Extra directory?

 

Thanks.

 

Hi, for some reason my SMBios was missing from /Extra. Replaced SMBios and all is good :)

Share this post


Link to post
Share on other sites

I used Chameleon Wizard a while ago to upgrade to 1098 fron 643 and it worked fine. I now tried to update to a newer version (tried several actually) and I renamed Boot.plist to org.Chameleon.Boot.plist etc. I have an nVidia 8400GS and it lost the settings for it and changed the res and hz etc and no DVI output. Also no Chameleon GUI even though its selected. And worse yet the audio and video is choppy. As there was no option in Chameleon Wizard to go back before rev 1200 I ended up reinstalling 643 from the dmg installer and now all is well. Another problem - If I changed anything at all in the Boot.plist with the editor in Wizard and saved the changes when I reboot I get KP and have to delete Boot.plist and replace it with an old copy to boot again. What am I doing wrong?

Thanks

Share this post


Link to post
Share on other sites
what about a PciRoot "detect" option?

 

Lizard uses "gfxutil -f display"

 

Does

ioreg -l | grep -15 "AppleACPIPCI\ " | grep UID

work the same way?

Share this post


Link to post
Share on other sites
Does

ioreg -l | grep -15 "AppleACPIPCI\ " | grep UID

work the same way?

I think so, gfxutil also gets it from ioreg

				// Obtain the I/O Kit root service.
			service = IORegistryGetRootEntry(kIOMasterPortDefault);
			assertion(service, "can't obtain I/O Kit's root service");							

			status = IORegistryEntryCreateIterator(service, kPlane, 0, &iterator);
			assertion(status == KERN_SUCCESS, "can't obtain children");

			RecursiveFindDevicePath(iterator, optarg, kPlane, &DevicePath, &match);
			if( (DevicePath != NULL) && match )
			{
				devpath_text = ConvertDevicePathToText(DevicePath, 1, 1);
				if(devpath_text  != NULL) printf("DevicePath = %s\n",(devpath_text != NULL)?devpath_text:"???");
				free(devpath_text);
				free(DevicePath);
			}
			else
			{
				printf("DevicePath not found!\n");
			}
			return 0;

Share this post


Link to post
Share on other sites

Thanks for this great util! I used it to replace Chimera with Chameleon and discovered some settings that I didn't know about :|

 

Dr. Hurt posted an installer for the final, stable build of Chameleon 2.0 (r1393). Maybe it'd be a good idea to add that to the list of Chameleon packages?

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By fighttoby
      I have tried to install clover via no UEFI legacy mode (and with UEFI method) using the method here (http://www.tonymacx86.com/yosemite-desktop-guides/144426-how-install-os-x-yosemite-using-clover.html)
      both times I can get to just past the clover boot screen and it freezes after that.
      I have verbose (-v) selected in boot options: On the non-UEFI install then it hangs on:
      "Waiting on <dict ID="0"><key>IOProviderClass</key>...."
       
      I have had a lot of issues with trying to get the installer working and many different things that had to be disabled but now it just gets to here and stops. Some times it will glitch out on this screen and give me a the circle with the line through it and text garbage around it where the text in the pictures are.
       
      Need help please.
       
      This is the laptop im using the specs are the same nothing has changed.
      https://www.asus.com/Laptops/ASUS_VivoBook_X202E/


      config.plist
    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • By grisno
      Hi people,
       
      This is a preliminary installer to activate the Combo Mini PCIe Atheros QCWB335 in MacOS.
       
      I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
       
      Status:
      AIRPORT : OK Atheros QCWB335 (AR9565) (168c:0036) Mini PCIe * BLUETOOTH : OK Atheros AR3012 (0cf3:3121) USB 2.0 ** AIRDROP : Not Tested HANDOFF : Not Tested CONTINUITY : Not Tested WOL : Not Tested IMESSAGE : OK FACETIME : OK ICLOUD : OK APPSTORE : OK   Known Issues:
       
      - Partial support with a maximum speed of 10Mbits (10.11.0+) *
      - Don't support Bluetooth Power Off/On by Software (10.10.0+) **
      - Sometimes Lost Bluetooth After Sleep WakeUp (10.10.0+) **
       
      Sources:
       
      Insanelymac
    • By grisno
      Installer to activate the Combo Mini PCIe AZUREWAVE AW-CE123H in macOS (10.8.5+)
       
      Status:
      AIRPORT : OK AzureWave AW-CE123H (14e4:43b1) [Broadcom BCM94352 HMB] Mini PCIe BLUETOOTH : OK AzureWave AW-CE123H (17cf:0b05) [Broadcom BCM20702A1] USB 2.0 AIRDROP : OK HANDOFF : OK CONTINUITY : OK WOL : Not Tested IMESSAGE : OK FACETIME : OK ICLOUD : OK APPSTORE : OK SIRI : OK   I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
×