Chimera 3.0 Update

[Stork]

Article: Chimera 3.0 Update

tried installing the new chimera 4 or 5 times. still previous version. is there a way to manually remove the previous version?

Are you sure you installed it to the correct disk?

 

[sctd32]

Article: Chimera 3.0 Update

is boot0 fixed in this release? or do we still have to run dd ?

 

[asmith1234]

Worked like a charm!

 

[pixelstand]

I used the latest Chimera 3.0.1 as of 5/18. Is the following correct as far as version information? I don't see chameleon based off svn-r2378; CPU frequencies are still off.

$ bdmesg | head -15
Chameleon 2.2svn (svn-r2371) [2014-02-02 16:58:41]
msr(416): platform_info f3012300
msr(420): flex_ratio 000f0000
Unusable flex ratio detected. Patched MSR now 000e0000
Sticking with [BCLK: 99Mhz, Bus-Ratio: 35]
CPU: Brand String: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
CPU: Vendor/Family/ExtFamily: 0x756e6547/0x6/0x0
CPU: Model/ExtModel/Stepping: 0x3c/0x3/0x3
CPU: MaxCoef/CurrCoef: 0x0/0x23
CPU: MaxDiv/CurrDiv: 0x0/0x0
CPU: TSCFreq: 3491MHz
CPU: FSBFreq: 99MHz
CPU: CPUFreq: 3491MHz
CPU: NoCores/NoThreads: 4/8
CPU: Features: 0x000002ff

 

[MacMan]

Article: Chimera 3.0 Update

I used the latest Chimera 3.0.1 as of 5/18. Is the following correct as far as version information? I don't see chameleon based off svn-r2378; CPU frequencies are still off.

$ bdmesg | head -15
Chameleon 2.2svn (svn-r2371) [2014-02-02 16:58:41]
msr(416): platform_info f3012300
msr(420): flex_ratio 000f0000
Unusable flex ratio detected. Patched MSR now 000e0000
Sticking with [BCLK: 99Mhz, Bus-Ratio: 35]
CPU: Brand String: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
CPU: Vendor/Family/ExtFamily: 0x756e6547/0x6/0x0
CPU: Model/ExtModel/Stepping: 0x3c/0x3/0x3
CPU: MaxCoef/CurrCoef: 0x0/0x23
CPU: MaxDiv/CurrDiv: 0x0/0x0
CPU: TSCFreq: 3491MHz
CPU: FSBFreq: 99MHz
CPU: CPUFreq: 3491MHz
CPU: NoCores/NoThreads: 4/8
CPU: Features: 0x000002ff

That is not Chimera 3.0 as it would be listed in the first line of the output from bdmesg.

 

[pixelstand]

Interesting. not sure what I did wrong. The version I used was from:

http://www.tonymacx86.com/downloads.php?do=file&id=223

and i verified that I installed to the correct partition. Is Chimera/Chameleon installed to the disk or a specific partition? I have an "admin" and "osx" partition, and I installed to my normal boot partition, "osx". "osx" is my 2nd partition: disk0s3

-px

 

[trumptor]

Article: Chimera 3.0 Update

super duper sure. still says version 2.2 on boot. The install always succeeds but the version number never changes. i'm using recommended drives and a gigabyte z77-ds3h.

 

[MacMan]

Article: Chimera 3.0 Update

super duper sure. still says version 2.2 on boot. The install always succeeds but the version number never changes. i'm using recommended drives and a gigabyte z77-ds3h.

To ensure full compatibility with closed source modules I need to not modify the boot banner. The only way to verify that you have Chimera is to look at the first line outputted by bdmesg. This is what you will see:

Chimera 3.0.1 Branch of Chameleon 2.2svn (svn-r2378) [2014-05-07 22:23:11]

 

[pixelstand]

Article: Chimera 3.0 Update

Interesting. not sure what I did wrong. The version I used was from:

http://www.tonymacx86.com/downloads.php?do=file&id=223

and i verified that I installed to the correct partition. Is Chimera/Chameleon installed to the disk or a specific partition? I have an "admin" and "osx" partition, and I installed to my normal boot partition, "osx". "osx" is my 2nd partition: disk0s3

-px

I got it installed.

I booted to my "admin" partition and installed chimera on every partition that showed up in the list during install. Rebooted to "osx" partition and now I get:

Chimera 3.0.1 Branch of Chameleon 2.2svn (svn-r2378) [2014-05-07 22:23:11]
CPU: Brand String: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
...
CPU: TSC Frequency: 3491 MHz
CPU: FSB Frequency: 99 MHz
CPU: CPU Frequency: 3392 MHz
CPU: Minimum Bus Ratio: 8
CPU: Maximum Bus Ratio: 35​

iMessage still doesn't work.

-px

 

[GeraldB]

Thank you. That has fixed my Memory Error in Diagnostic Info in Systeminformation. Keep up the good work for us .