Compatibility Issues - Unknown CPU model 0x3c

[lordzsolt]

You don't want to use Chimera's graphics injection (Graphics Enabler) as you are running with web driver support.

Set graphics card as your primary video adapter/initial display port on BIOS.
Disable Internel Graphics on BIOS.

Then try to boot with -f, once it is booted post your org.chameleon.boot.plist file.

Been playing around for a while, I'm able to boot fairly consistently (like 80% change my monitors will get signal) with this config:

        <key>EthernetBuiltIn</key>
    <string>Yes</string>
    <key>GraphicsEnabler</key>
    <string>No</string>
    <key>IGPEnabler</key>
    <string>Yes</string>
    <key>Kernel Flags</key>
        <string>kext-dev-mode=1 nvda_drv=1 Mode=1680x1050x32 PCIRootUID=0 -v</string>
    <key>Legacy Logo</key>
    <string>Yes</string>
    <key>Timeout</key>
    <string>2</string>
        <key>Graphics Mode</key>
        <string>"1680x1050x32"</string>
        <key>GenerateCStates</key>
        <string>Yes</string>
        <key>GeneratePStates</key>
        <string>Yes</string>
        <key>UseKernelCache</key>
        <string>Yes</string>
        <key>HDEFLayoutID</key>
        <string>01000000</string>
        <key>HDAEnabler</key>
        <string>Yes</string>

I'm curious, what does the PCIRootUID=0 =1 do? I know it has to do something with onboard and dedicated GPU, but what exactly? And which is which?

 

[Jithin.C.V]

Been playing around for a while, I'm able to boot fairly consistently (like 80% change my monitors will get signal) with this config:

        <key>EthernetBuiltIn</key>
    <string>Yes</string>
    <key>GraphicsEnabler</key>
    <string>No</string>
    <key>IGPEnabler</key>
    <string>Yes</string>
    <key>Kernel Flags</key>
        <string>kext-dev-mode=1 nvda_drv=1 Mode=1680x1050x32 PCIRootUID=0 -v</string>
    <key>Legacy Logo</key>
    <string>Yes</string>
    <key>Timeout</key>
    <string>2</string>
        <key>Graphics Mode</key>
        <string>"1680x1050x32"</string>
        <key>GenerateCStates</key>
        <string>Yes</string>
        <key>GeneratePStates</key>
        <string>Yes</string>
        <key>UseKernelCache</key>
        <string>Yes</string>
        <key>HDEFLayoutID</key>
        <string>01000000</string>
        <key>HDAEnabler</key>
        <string>Yes</string>

I'm curious, what does the PCIRootUID=0 =1 do? I know it has to do something with onboard and dedicated GPU, but what exactly? And which is which?

You have to little more changes on org.chameleon.boot.plist file

<key>Kernel Flags</key>
<string>kext-dev-mode=1 nvda_drv=1</string>

<key>IGPEnabler</key>
<string>No</string>

<key>UseKernelCache</key>
<string>No</string>

<key>Graphics Mode</key>
<string>"1680x1050x32"</string>

Save the file. Reboot and check the booting without entering any flags.

 

[lordzsolt]

You have to little more changes on org.chameleon.boot.plist file

<key>Kernel Flags</key>
<string>kext-dev-mode=1 nvda_drv=1</string>

<key>IGPEnabler</key>
<string>No</string>

<key>UseKernelCache</key>
<string>No</string>

<key>Graphics Mode</key>
<string>"1680x1050x32"</string>

Save the file. Reboot and check the booting without entering any flags.

Sadly,after these changes I'm 0/5 at monitors getting signal.

 

[Jithin.C.V]

Sadly,after these changes I'm 0/5 at monitors getting signal.

Boot with flag -v and check where your booting getting stuck.

 

[lordzsolt]

Boot with flag -v and check where your booting getting stuck.

The problem isn't booting. It boots every time, but sometimes it doesn't give signal to the monitors. This only happens when I have my monitor which is connected through a VGA to DVI adapter.

 

[Jithin.C.V]

The problem isn't booting. It boots every time, but sometimes it doesn't give signal to the monitors. This only happens when I have my monitor which is connected through a VGA to DVI adapter.

VGA not natively supported on Yosemite.

 

[lordzsolt]

VGA not natively supported on Yosemite.

Have played around with things today and I've managed to make my VGA monitor get signal every time. The only thing that I can think of which would affect this is enabling both the onboard and the external graphics adapter in BIOS.

 

[Ezzyme]

nvda_drv=1 was the solution to my problem after installing a 780 TI. Glad I found this and thank you so much for sharing