Jump to content

Chameleon RC5 mode with mem detection enabled and automatic P-States & C-States generation for native power managment


kozlek
 Share

1,214 posts in this topic

Recommended Posts

Apple never shipped anything with a Core 2 Quad CPU.

 

Having your CPU identified as a quad core Xeon is better for compatibility, some apps will refuse to install/run at all if they don't see a CPU type that Apple use.

 

Ah yes i suspected that might be the case, but thought there were some imacs released with quad core. That explains that. So i guess the only issue with cpu identification is on system 1 where it does not identify the core i3-530. If there is no exact match i guess having it identifies as a core i5 would be better than unknown?

Thanks,

g\

Link to comment
Share on other sites

Hello all,

many thanks for the continued work. some very cool features in these releases.

 

I went ahead and installed rev411 on a fourth system and it went very very well!

System 4:

Asus P6T7 WS Super Computer (yes, thats the real name - its an x58 chipset), i7-920 OC to 4ghz.

Only fakesmc, ioahciblockstorage, and legacyhda in /E/E

 

Well it seems everything works great on this system

- CPU is identified correctly as i7.

- All speeds are correctly reported. CPU, QPI and RAM.

- Pstates worked before and after update (i am not even using the c.a.b.p tags on this system)

- I have not tested sleep but will report back on this

- stripped down the smbios.plist and it looks good with system identified as macpro4,1

 

So on this system it looks like a total success.

 

I seek some clarification from someone in the know. As it seems P states work natively on i7 systems, what about C states?

Should i be seeing these as well in ioreg? do i need to enable them using the c.a.b.p tag GenerateCStates? i ask because i am not seeing Cstates on either system 1 (i3) or system 4 (i7). i am using the c.a.b.p tags on system 1 but not on system 4.

 

 

Thanks for all the hard work,

g\

Link to comment
Share on other sites

Hi all.

 

Just a curiosity...

I use 5 extra tables (SSDT), so DSDT,SSDT,SSDT-1,SSDT-2,SSDT-3,SSDT-4...

ok until now...

but why in the boot log I see it load two time?

Same for the Restart Fix applied... is normal??

Of course.. I use DropSSDT option in c.a.B.p

[size=1] Last login: Sun Aug 22 03:15:41 on console
/Extra/Util/bdmesg ; exit;
Fabios-Mac-Pro:~ iFabio$ /Extra/Util/bdmesg ; exit;
msr(204): platform_info 00001600
msr(207): flex_ratio 00000000
CPU: Vendor/Model/ExtModel: 0x756e6547/0x1a/0x1
CPU: Family/ExtFamily:      0x6/0x0
CPU: MaxCoef/CurrCoef:      0x0/0x16
CPU: MaxDiv/CurrDiv:        0x0/0x0
CPU: TSCFreq:               2940MHz
CPU: FSBFreq:               133MHz
CPU: CPUFreq:               2940MHz
CPU: NoCores/NoThreads:     8/16
CPU: Features:              0x000002ff
Attempting to read GPT
Read GPT
Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B
Reading GPT partition 2, type 48465300-0000-11AA-AA11-00306543ECAC
Reading GPT partition 3, type 48465300-0000-11AA-AA11-00306543ECAC
Read HFS+ file: [hd(0,2)/Extra/com.apple.Boot.plist] 559 bytes.
Attempting to read GPT
Read GPT
Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B
Reading GPT partition 2, type 48465300-0000-11AA-AA11-00306543ECAC
Reading GPT partition 3, type 48465300-0000-11AA-AA11-00306543ECAC
Attempting to read GPT
Read GPT
Reading GPT partition 1, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B
Reading GPT partition 2, type 48465300-0000-11AA-AA11-00306543ECAC
Reading GPT partition 3, type 48465300-0000-11AA-AA11-00306543ECAC
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/theme.plist] 2798 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/background.png] 966 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/logo.png] 10718 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_generic.png] 60835 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_generic_o.png] 60178 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsplus.png] 63997 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsplus_o.png] 64117 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsraid.png] 64789 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_hfsraid_o.png] 64940 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ext3.png] 63452 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ext3_o.png] 63208 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_fat.png] 62724 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_fat_o.png] 62467 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ntfs.png] 65689 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_ntfs_o.png] 65621 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_cdrom.png] 60698 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_cdrom_o.png] 60537 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_selection.png] 454 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_scroll_prev.png] 4566 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/device_scroll_next.png] 4381 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_boot.png] 182 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_verbose.png] 182 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_ignore_caches.png] 182 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_single_user.png] 182 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_memory_info.png] 180 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_video_info.png] 180 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_help.png] 180 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_verbose_disabled.png] 187 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_ignore_caches_disabled.png] 187 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_single_user_disabled.png] 187 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/menu_selection.png] 236 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/progress_bar.png] 349 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/progress_bar_background.png] 179 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/text_scroll_prev.png] 632 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/text_scroll_next.png] 650 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/font_console.png] 3499 bytes.
Read HFS+ file: [hd(0,2)/Extra/Themes/Default/font_small.png] 5525 bytes.
Read HFS+ file: [hd(0,2)/Extra/com.apple.Boot.plist] 559 bytes.
Setting boot-uuid to: 6FFBEA3A-1A3B-3EB4-93A9-0A11584686EE
Read HFS+ file: [hd(0,2)/System/Library/CoreServices/SystemVersion.plist] 479 bytes.
Loading Darwin 10.6
Loading kernel mach_kernel
Read HFS+ file: [hd(0,2)/mach_kernel] 4096 bytes.
Read HFS+ file: [hd(0,2)/mach_kernel] 5576574 bytes.
LoadDrivers: Loading from [/Extra/Extensions.mkext]
Read HFS+ file: [hd(0,2)/Extra/Extensions.mkext] 4096 bytes.
Read HFS+ file: [hd(0,2)/Extra/Extensions.mkext] 43806 bytes.
LoadDrivers: Loading from [/system/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext]
Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext] 4096 bytes.
Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext] 4049521 bytes.
Read HFS+ file: [hd(0,2)/Extra/DSDT.aml] 41319 bytes.
Using PCI-Root-UID value: 0
nVidia Quadro FX 5600 1536MB NV50 [10de:019d] :: PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)
No SMBIOS replacement found
Intel NHM IMC DRAM Controller [8086:3405] at 00:00.0
Frequency detected: 534 MHz (1069) Triple Channel 20-8-8-0
Slot: 0 Type 24 2048MB (DDR3 SDRAM) 1069MHz Vendor=Corsair
     PartNo=CM3X2G1600C8D SerialNo=00000000
Slot: 2 Type 24 2048MB (DDR3 SDRAM) 1069MHz Vendor=Corsair
     PartNo=CM3X2G1600C8D SerialNo=00000000
Slot: 4 Type 24 2048MB (DDR3 SDRAM) 1069MHz Vendor=Corsair
     PartNo=CM3X2G1600C8D SerialNo=00000000
CPU is Intel® Core(tm) i7 CPU         940  @ 2.93GHz, family 0x6, model 0x1a
Patched DMI Table
Found SMBIOS System Information Table 1
Customizing SystemID with : 00020003-0004-0005-0006-000700080009
Read HFS+ file: [hd(0,2)/Extra/DSDT.aml] 41319 bytes.
Read HFS+ file: [hd(0,2)/Extra/SSDT.aml] 5372 bytes.
Read HFS+ file: [hd(0,2)/Extra/SSDT-1.aml] 1590 bytes.
Read HFS+ file: [hd(0,2)/Extra/SSDT-2.aml] 835 bytes.
Read HFS+ file: [hd(0,2)/Extra/SSDT-3.aml] 509 bytes.
Read HFS+ file: [hd(0,2)/Extra/SSDT-4.aml] 276 bytes.
[color="#0000ff"]FADT: Restart Fix applied![/color]
[color="#ff0000"]FADT: Using custom DSDT![/color]
[color="#808080"]RSDT: Added 5 SSDT table(s)[/color]
[color="#0000ff"]FADT: Restart Fix applied![/color]
[color="#ff0000"]FADT: Using custom DSDT![/color]
[color="#696969"]Added 5 SSDT table(s) into XSDT[/color]
Starting Darwin x86_64

logout

[Processo completato][/size]

 

Fabio

Link to comment
Share on other sites

iFabio,

 

yep, for now it's normal :) no worries.

Rekursor was on to that stuff on his latest commits; this one, for instance

Patched DMI Table
was printed (executed) 3 times.
Link to comment
Share on other sites

Hi,

this project sounds awesome. I have a already running setup with the Extra folder on the hidden EFI partition what would happen, if I just ran the installer? Would it override the boot process from the EFI partition and create a new setup on my main HD? Would it suffice to just extract the boot file from the package and put it in my existing Extra folder or is there more to the package? And do I still need the CPUPowermanagementDisabler kext when using this version? Sorry, but I'm not that knowledgeable about this stuff.

Thank you for your help. I love this project and the energy that is put into it. You guys are amazing.

 

Regards

Johannes from Munich, Bavaria

Link to comment
Share on other sites

Hi,

this project sounds awesome. I have a already running setup with the Extra folder on the hidden EFI partition what would happen, if I just ran the installer? Would it override the boot process from the EFI partition and create a new setup on my main HD? Would it suffice to just extract the boot file from the package and put it in my existing Extra folder or is there more to the package? And do I still need the CPUPowermanagementDisabler kext when using this version? Sorry, but I'm not that knowledgeable about this stuff.

Thank you for your help. I love this project and the energy that is put into it. You guys are amazing.

 

Regards

Johannes from Munich, Bavaria

Before go on with the working partition, try it on a usbdrive.

Use the installer to install chameleon on the drive and copy you /Extra contents in the /Extra folder on the usb. be shure to have correct permissoin in the /Extra/Extensions folder with kext utility (just drag the folder on the icon of the app).

And then reboot from the usb (you need to check your bios or use something like F8 on some mobo to se the boot drive list of your bios).

 

For CPUPower just try with and without starting in verbose to see if there are erros at boot.

 

I love you man

work great

 

I haven't done anything, all the love goes to all the chameleon staff :(

thank's guys!

 

Hello all,

many thanks for the continued work. some very cool features in these releases.

 

I went ahead and installed rev411 on a fourth system and it went very very well!

System 4:

Asus P6T7 WS Super Computer (yes, thats the real name - its an x58 chipset), i7-920 OC to 4ghz.

Only fakesmc, ioahciblockstorage, and legacyhda in /E/E

 

Well it seems everything works great on this system

- CPU is identified correctly as i7.

- All speeds are correctly reported. CPU, QPI and RAM.

- Pstates worked before and after update (i am not even using the c.a.b.p tags on this system)

- I have not tested sleep but will report back on this

- stripped down the smbios.plist and it looks good with system identified as macpro4,1

 

So on this system it looks like a total success.

 

I seek some clarification from someone in the know. As it seems P states work natively on i7 systems, what about C states?

Should i be seeing these as well in ioreg? do i need to enable them using the c.a.b.p tag GenerateCStates? i ask because i am not seeing Cstates on either system 1 (i3) or system 4 (i7). i am using the c.a.b.p tags on system 1 but not on system 4.

 

 

Thanks for all the hard work,

g\

 

Please, can you post your

dmesg

results?

Link to comment
Share on other sites

It boots quickly. It reports everything correctly in Sys Profile. Theme: the best best looking theme so far and I suspect it will be the De-Facto theme for some time to come.

Question: how do I make the Apple boot background the same color as this theme?

I really appreciate this.

Link to comment
Share on other sites

I keep getting the errors below in bold and underlined for a while maybe since rev. 361 if I remember correctly. What needs to changed to correct this issue? Thanks in advance.

 

Below from bsmseg

 

msr(204): platform_info 00011401

msr(207): flex_ratio 00011400

CPU: Vendor/Model/ExtModel: 0x756e6547/0x1a/0x1

CPU: Family/ExtFamily: 0x6/0x0

CPU: MaxCoef/CurrCoef: 0x0/0x14

CPU: MaxDiv/CurrDiv: 0x0/0x0

CPU: TSCFreq: 4000MHz

CPU: FSBFreq: 200MHz

CPU: CPUFreq: 4000MHz

CPU: NoCores/NoThreads: 8/16

CPU: Features: 0x000002ff

Attempting to read GPT

Read GPT

.... cut from message

Setting boot-uuid to: 33A28CAA-DFFE-3323-911A-E8DBAB2692B5

Read HFS+ file: [hd(0,2)/System/Library/CoreServices/SystemVersion.plist] 479 bytes.

Loading Darwin 10.6

Loading kernel mach_kernel

Read HFS+ file: [hd(0,2)/mach_kernel] 4096 bytes.

Read HFS+ file: [hd(0,2)/mach_kernel] 7444208 bytes.

LoadDrivers: Loading from [/Extra/Extensions.mkext]

Read HFS+ file: [hd(0,2)/Extra/Extensions.mkext] 4096 bytes.

Read HFS+ file: [hd(0,2)/Extra/Extensions.mkext] 30342 bytes.

LoadDrivers: Loading from [/system/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext]

Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext] 4096 bytes.

Read HFS+ file: [hd(0,2)/System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext] 4924845 bytes.

Read HFS+ file: [hd(0,2)/Extra/DSDT.aml] 23452 bytes.

Using PCI-Root-UID value: 1

LAN Controller [168c:001b] :: PciRoot(0x1)/Pci(0x1e,0x0)/Pci(0x0,0x0)

Setting up lan keys

Read HFS+ file: [hd(0,2)/Extra/smbios.plist] 869 bytes.

Slot: 0 Type 24 2048MB (DDR3 SDRAM) 1066MHz Vendor=OCZ

PartNo=OCZ3G2000LV2G SerialNo=00000000

Slot: 2 Type 24 2048MB (DDR3 SDRAM) 1066MHz Vendor=OCZ

PartNo=OCZ3G2000LV2G SerialNo=00000000

Slot: 4 Type 24 2048MB (DDR3 SDRAM) 1066MHz Vendor=OCZ

PartNo=OCZ3G2000LV2G SerialNo=00000000

CPU is Intel® Core i7 CPU 930 @ 2.80GHz, family 0x6, model 0x1a

Patched DMI Table

Found SMBIOS System Information Table 1

No UUID present in SMBIOS System Information Table

[ERROR] UUID='0123456789ABCDEF' syntax error

Customizing SystemID with :

Read HFS+ file: [hd(0,2)/Extra/DSDT.aml] 23452 bytes.

FADT: Restart Fix applied!

FADT: Using custom DSDT!

Found ACPI CPU: CPU0

Found ACPI CPU: CPU1

Found ACPI CPU: CPU2

Found ACPI CPU: CPU3

Found ACPI CPU: CPU4

Found ACPI CPU: CPU5

Found ACPI CPU: CPU6

Found ACPI CPU: CPU7

Found ACPI CPU: CPU8

Found ACPI CPU: CPU9

Found ACPI CPU: CPUA

Found ACPI CPU: CPUB

Found ACPI CPU: CPUC

Found ACPI CPU: CPUD

Found ACPI CPU: CPUE

Found ACPI CPU: CPUF

SSDT with CPU C-States generated successfully

RSDT: Added 1 SSDT table(s)

Starting Darwin x86

Link to comment
Share on other sites

I've had trouble installing the latest TRUNK build (416) to a USB stick. Manually it works fine but when using the install pkg, it usually fails but on the odd occasion that it says it completed correctly nothing was actually installed to the HDD to make it bootable.

Link to comment
Share on other sites

Please, can you post your
dmesg

results?

 

Hi scrax,

when i run dmesg from terminal it lists just a bunch of fakeSMC key info not found. Is this what you want or do i need to run this right after boot?

thanks,

g\

Link to comment
Share on other sites

CPU is Intel® Core i7 CPU 920 @ 2.67GHz, family 0x6, model 0x1a

 

 

FADT: Restart Fix applied!

FADT: Using custom DSDT!

Found ACPI CPU: CPU0

Found ACPI CPU: CPU1

Found ACPI CPU: CPU2

Found ACPI CPU: CPU3

Found ACPI CPU: CPU4

Found ACPI CPU: CPU5

Found ACPI CPU: CPU6

Found ACPI CPU: CPU7

Found ACPI CPU: CPU8

Found ACPI CPU: CPU9

Found ACPI CPU: CPUA

Found ACPI CPU: CPUB

Found ACPI CPU: CPUC

Found ACPI CPU: CPUD

Found ACPI CPU: CPUE

Found ACPI CPU: CPUF

SSDT with CPU C-States generated successfully

Unsupported CPU: P-States not generated !!!

RSDT: Added 1 SSDT table(s)

FADT: Restart Fix applied!

FADT: Using custom DSDT!

Unsupported CPU: P-States not generated !!!

Added 1 SSDT table(s) into XSDT

Starting Darwin x86_64

 

 

(Unsupported CPU: P-States not generated !!!)

 

I have installed the Cameleon2 RC5 r416 what happening with the P-States?

 

Thank you for your time.

Link to comment
Share on other sites

(Unsupported CPU: P-States not generated !!!)

 

I have installed the Cameleon2 RC5 r416 what happening with the P-States?

 

Thank you for your time.

 

Someone correct me if i am wrong, but i7 P-states work native. You dont need to use the GeneratePStates tag in c.a.B.p. Your Pstates will work without it. And without it you wont get that error message.

 

Now my question is about Cstates, do i7 owners have to use GenerateCStates tag? on my i7 system i dont use the tag, with my i3 system i do use it, but neither cpu shows Cstates in ioreg.

 

Thanks,

g\

Link to comment
Share on other sites

Also one more issue that i would like to add since this is a good dev thread. I have posted this in voodooprojects forum as well and had many people confirm the issue.

 

All versions of chameleon i have ever tried run very, very slow on i7 machines (i3 too). the countdown goes very slowly (set to 3 seconds but easily >10 seconds); there is lag on all keybaord input, etc.

The worst is when you use -f -v and have to sit through several minutes of kexts appearing one after the other on the screen. This command combination usually flies by on non core ix machines. On every core 2 system i have used the interface is snappy. Do we know why this is happening?

Thanks,

g\

Link to comment
Share on other sites

Also one more issue that i would like to add since this is a good dev thread. I have posted this in voodooprojects forum as well and had many people confirm the issue.

 

All versions of chameleon i have ever tried run very, very slow on i7 machines (i3 too). the countdown goes very slowly (set to 3 seconds but easily >10 seconds); there is lag on all keybaord input, etc.

The worst is when you use -f -v and have to sit through several minutes of kexts appearing one after the other on the screen. This command combination usually flies by on non core ix machines. On every core 2 system i have used the interface is snappy. Do we know why this is happening?

Thanks,

g\

 

 

Check my bench in cinemabench 11.5

 

 

in the picture show the test on windows 7 x64 and snowleopard 10.6.4

 

the process you see clearly the performance between in the two operating systems with same machine.

 

Intel Core i7 920

3 GB 1333 MHZ DDR3

EVGA GeForce GTX 260 Core 216 Superclocked

Link to comment
Share on other sites

Also one more issue that i would like to add since this is a good dev thread. I have posted this in voodooprojects forum as well and had many people confirm the issue.

 

All versions of chameleon i have ever tried run very, very slow on i7 machines (i3 too). the countdown goes very slowly (set to 3 seconds but easily >10 seconds); there is lag on all keybaord input, etc.

The worst is when you use -f -v and have to sit through several minutes of kexts appearing one after the other on the screen. This command combination usually flies by on non core ix machines. On every core 2 system i have used the interface is snappy. Do we know why this is happening?

Thanks,

g\

 

most likely its because of the MTRR for the framebuffer is no longer is setup to use write combining in the bios, its now left to the graphics driver to setup.

Link to comment
Share on other sites

I havent tried RC5 yet, but my question about chameleon is.... How can i boot EVERY TIME with -v (verbose mode)?

What i must write in com.apple.boot.plist ?

 

I get some KP, that i cant figure out what cause them and Console var/log doesnt help so much.

Link to comment
Share on other sites

 Share

×
×
  • Create New...