Jump to content

Chameleon 2.4svn Official PKG Installer


ErmaC
 Share

4,261 posts in this topic

Recommended Posts

?

 

 

I believe that you will fail to read a few pages back. 
What you've seen is a test done previously by Ermac. 
 
ErmaC do a release to test here, and when  Ensure that  it work from some people, he made ​​a commit in the svn. After became a official revision of Chameleon!
Link to comment
Share on other sites

Lol thought it was funny.

So here is the result when I try to boot Yosemite with Chameleon, same as before: attachicon.gifImageUploadedByTapatalk1402868411.969844.jpg

Stuck at PCI Configuration Begin. For no reason. Lol the install works perfectly with Clover and the Mavericks install boots fine with both. Just Yosemite throws this error.

Haven't gotten this error since my AMD rig lol

try

-v npci=0x2000 kext-dev-mode=1

this work

npci=0x2000 or 0x3000 fix PCI Configuration Begin :thumbsup_anim:

Me get also this error first time with r2377 :D

Link to comment
Share on other sites

When I google for Chameleon revisions, they come up in a thousand places. Where is a good solid place to get them from? The wizard isn't working.

The one I downloaded was from here, a few pages back.

I tried npci boot flags last time but I'll try again :)

Link to comment
Share on other sites

When I google for Chameleon revisions, they come up in a thousand places. Where is a good solid place to get them from? The wizard isn't working.

From the svn or at the InsanelyMac download section (where ErmaC upload the new release), but you can't find any r2380 ATM...try to guess why?

Link to comment
Share on other sites

I have no idea man. Thanks.

<?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>DSDT</key>

    <string>Extra/DSDT.aml</string>

    <key>EthernetBuiltIn</key>

    <string>Yes</string>

    <key>GraphicsEnabler</key>

    <string>Yes</string>

    <key>HDAEnabler</key>

    <string>Yes</string>

    <key>Kernel</key>

    <string>/System/Library/Kernels/kernel</string>

    <key>Kernel Flags</key>

    <string>-v npci=0x2000 kext-dev-mode=1 -xcpm</string>

    <key>Legacy Logo</key>

    <string>Yes</string>

    <key>PciRoot</key>

    <string>1</string>

    <key>SMBIOS</key>

    <string>/Extra/smbios.plist</string>

    <key>SystemType</key>

    <string>1</string>

    <key>Theme</key>

    <string>Default</string>

    <key>UseKernelCache</key>

    <string>Yes</string>

 

Try like this Boot plist file,work fine

Link to comment
Share on other sites

I use most of those strings already, besides GraphicsEnabler and HDAEnabler (my graphics card doesn't require it), and SystemType.  I'll try messing with PciRoot and whatnot, see what I can do.


This is the .plist I've always used, that worked (and still works) with Mavericks.  Anyone see any red flags?  

<?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>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>GenerateCStates</key>
	<string>Yes</string>
	<key>GeneratePStates</key>
	<string>Yes</string>
	<key>Graphics Mode</key>
	<string>1680x1050x32</string>
	<key>GraphicsEnabler</key>
	<string>No</string>
	<key>IGPEnabler</key>
	<string>No</string>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string>-gux_nosleep darkwake=0 nvda_drv=1</string>
	<key>Legacy Logo</key>
	<string>Yes</string>
	<key>Quiet Boot</key>
	<string>Yes</string>
	<key>Scan Single Drive</key>
	<string>Yes</string>
	<key>Theme</key>
	<string>Choose_Your_OS</string>
	<key>Timeout</key>
	<string>0</string>
	<key>UseKernelCache</key>
	<string>Yes</string>
</dict>
</plist>


I'm booting with kext-dev-mode=1 by hand.  

Link to comment
Share on other sites

I use most of those strings already, besides GraphicsEnabler and HDAEnabler (my graphics card doesn't require it), and SystemType.  I'll try messing with PciRoot and whatnot, see what I can do.

Dont't tell me..you need to  run on your AMD Phenom II X6 1075T? :hysterical:

  • Like 2
Link to comment
Share on other sites

    Kernel

    /System/Library/Kernels/kernel

    Kernel Flags

    -v npci=0x2000 kext-dev-mode=1 -xcpm

 

From your boot plist I understand the auto kernel path don't work?

 

Fabio

Link to comment
Share on other sites


I use most of those strings already, besides GraphicsEnabler and HDAEnabler (my graphics card doesn't require it), and SystemType.  I'll try messing with PciRoot and whatnot, see what I can do.

This is the .plist I've always used, that worked (and still works) with Mavericks.  Anyone see any red flags?  

<key>IGPEnabler</key>
    <string>No</string>
    <key>Kernel</key>
    <string>mach_kernel</string>

I'm booting with kext-dev-mode=1 by hand.  

You must review your config, the key from Chimera does not work with Chameleon, and the mach_kernel no longer exist in Yosemite

 

Try to delete:

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

or edit like that if does not work

<key>Kernel</key>
    <string>/System/Library/Kernels/kernel</string>
Link to comment
Share on other sites

From your boot plist I understand the auto kernel path don't work?

 

Fabio

need to be change any?on boot plist?

on my system now with 2380 got only one error-SMC Platform plugin,but me toomuch understand from where get it(i Dont have time to enable Thermal profile)

this is..

Link to comment
Share on other sites


You must review your config, the key from Chimera does not work with Chameleon, and the mach_kernel no longer exist in Yosemite

 

Try to delete:

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

or edit like that if does not work

<key>Kernel</key>
    <string>/System/Library/Kernels/kernel</string>

 

I use most of those strings already, besides GraphicsEnabler and HDAEnabler (my graphics card doesn't require it), and SystemType.  I'll try messing with PciRoot and whatnot, see what I can do.

This is the .plist I've always used, that worked (and still works) with Mavericks.  Anyone see any red flags?  

<?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>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>GenerateCStates</key>
	<string>Yes</string>
	<key>GeneratePStates</key>
	<string>Yes</string>
	<key>Graphics Mode</key>
	<string>1680x1050x32</string>
	<key>GraphicsEnabler</key>
	<string>No</string>
	<key>IGPEnabler</key>
	<string>No</string>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string>-gux_nosleep darkwake=0 nvda_drv=1</string>
	<key>Legacy Logo</key>
	<string>Yes</string>
	<key>Quiet Boot</key>
	<string>Yes</string>
	<key>Scan Single Drive</key>
	<string>Yes</string>
	<key>Theme</key>
	<string>Choose_Your_OS</string>
	<key>Timeout</key>
	<string>0</string>
	<key>UseKernelCache</key>
	<string>Yes</string>
</dict>
</plist>

I'm booting with kext-dev-mode=1 by hand.  

For me..need to forget:

    <key>GenerateCStates</key>

    <string>Yes</string>

    <key>GeneratePStates</key>

    <string>Yes</string>

For me..need to forget:

    <key>GenerateCStates</key>

    <string>Yes</string>

    <key>GeneratePStates</key>

    <string>Yes</string>

this is Yosemite,not Mavericks

Link to comment
Share on other sites

Hence my question: can I dual boot Mavericks and Yosemite off the same drive? If I can't use my Mavericks boot.plist then how am I supposed to boot Mavericks?

Wouldn't each OS need its own drive with it's own /Extra dir with it's own boot.plist??

Link to comment
Share on other sites

Hence my question: can I dual boot Mavericks and Yosemite off the same drive? If I can't use my Mavericks boot.plist then how am I supposed to boot Mavericks?

Wouldn't each OS need its own drive with it's own /Extra dir with it's own boot.plist??

Tommorow me plaining Quadro boot and tell you ..if Ok

Link to comment
Share on other sites

Hence my question: can I dual boot Mavericks and Yosemite off the same drive? If I can't use my Mavericks boot.plist then how am I supposed to boot Mavericks?

Wouldn't each OS need its own drive with it's own /Extra dir with it's own boot.plist??

Read HFS+ file: [hd(0,2)/Extra/org.chameleon.Boot.plist] 2334 bytes.

Well, Chameleon seem to be able to read each org.chameleon.Boot.plist!

 

But one "quesite":

 

you have a gux_nosleep flag, so your usb key is plugged into a USB 3.0 port?

If the answer is Yes, you can try to plug it into a USB 2.0 port?????

Why? the GenericXHCI.kext can be buggy in Yosemite

Link to comment
Share on other sites

HUSABER

 

Can you try to remove this entry

<key>Kernel</key>    <string>/System/Library/Kernels/kernel</string>
from your boot.plist?

 

I would like to know if the detection work...

Link to comment
Share on other sites

Read HFS+ file: [hd(0,2)/Extra/org.chameleon.Boot.plist] 2334 bytes.

Well, Chameleon seem to be able to read each org.chameleon.Boot.plist!

 

But one "quesite":

 

you have a gux_nosleep flag, so your usb key is plugged in a USB 3.0 port?

If the answer is Yes, you can try to plug it into a USB 2.0 port?????

 

The guy wants his Clover....not to confuse more :wink_anim:

HUSABER

 

Can you try to remove this entry

<key>Kernel</key>    <string>/System/Library/Kernels/kernel</string>
from your boot.plist?

 

I would like to know if the detection work...

 

but me dont use mach_kernel in Root

  • Like 1
Link to comment
Share on other sites

but me dont use mach_kernel in Root

Maybe I missed some of your previous reply...

But what are your kernel entry in your Yosemite boot plist?

 

Can you post your org.chameleon.Boot.plist (Yosemite)? Plssss

 

ErmaC

Link to comment
Share on other sites

ErmaC has introduced the ability to "auto set" the kernel path, he want to know if it works

wait,i try

Link to comment
Share on other sites

 Share

×
×
  • Create New...