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

Done and done, no more smbios.plist! Thank You for the tip....

Your welcome :)

 

 

Azimutz, thanks for the pointers. I took your advice and fixed myself the Chameleon SMBIOS injection so that my mobile core i7 is recognized as mobile core i7 MacbookPro6,2.

 

in smbios_patcher.c, right underneath the MacbooPro section, I added a section for the Core i5/i7 MacBookpro....

 

Now Chameleon SMBIOS injection is correctly giving me mobile core i7 MacBookPro6,2 on trunk revision 517

Well, i suggested a simple change, you went a bit further so, i hope you know what you're doing ;)

 

 

Now you have to add that code in there every time you upgrade the bootloader.

Not necessarily... if he's working with a svn checkout, local changes are kept when updating the folder.

May need to resolve conflicts if there are changes that overlap the local ones, but that's it.

Link to comment
Share on other sites

Nice, that makes sense. I didn't know it worked like that.

 

I like to make a copy of the trunk folder and compile from that. No leftover obj folder to mess things up..you never know. Do you think that's good practice, or am I being superstitious?

yep... you are being a bit, Gringo :D

On the svn side, sym and obj folders are set to be ignored on properties; check the trunk folder, at the bottom of the page for the folder properties.

And let's not forget "svn help" on Terminal... i do a lot :P well, maybe not lately; "svn proplist" and "svn propget" do the job.

On the build side, keeping those folders makes the job of compiling a lot faster, since the compiler will only process the necessary files, according to the changes. There are some situations were a "make clean" is necessary, though.

Link to comment
Share on other sites

What info should be shown? The speed of the RAM module(s) or actual speed it is running on? How does this work?

 

Here's what I have in my HP notebook:

 

40zcy948nk1tmzm0bhbs.png

 

Two 9-9-9 (1.5v) 1333MHz modules, but they should be running @1066MHz because that's what my notebook supports.

Link to comment
Share on other sites

It's supposed to show the speed the memory is running at.

 

Don't worry, it's only cosmetic. If it bothers you, you can correct it via smbios.plist (SMmemspeed=1066) so that it shows correctly in System Profiler.

 

Download and run LSPCI with the -nn switch and look for the line that identifies the memory controller, here's mine for comparison:

00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 02)

I don't know if posting that info will be helpful but at least it's something.

Link to comment
Share on other sites

It's supposed to show the speed the memory is running at.

In that case I have to retract my previous positive.

 

Don't worry, it's only cosmetic. If it bothers you, you can correct it via smbios.plist (SMmemspeed=1066) so that it shows correctly in System Profiler.

Sure thing, but I thought that the goal was to make it work without the need of smbios.plist

 

Download and run LSPCI with the -nn switch and look for the line that identifies the memory controller, here's mine for comparison:

00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 02)

I don't know if posting that info will be helpful but at least it's something.

Neither do I, but let me just add it in case it is helpful:

00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02)
Subsystem: Hewlett-Packard Company Device [103c:143a]

Link to comment
Share on other sites

Why isn't there a "av-signal-type" property in ati.c? I ask this because I stumbled upon the following snippet in IOGraphicsTypes.h:

// CFNumber/CFData
#define kIOFBAVSignalTypeKey			"av-signal-type"
enum {
kIOFBAVSignalTypeUnknown = 0x00000000,
kIOFBAVSignalTypeVGA	 = 0x00000001,
kIOFBAVSignalTypeDVI	 = 0x00000002,
kIOFBAVSignalTypeHDMI	= 0x00000008,
kIOFBAVSignalTypeDP	  = 0x00000010,
};

Don't we want / need this?

 

Look here: grep -r -e av-signal-type .

Binary file ./ATIFramebuffer.kext/Contents/MacOS/ATIFramebuffer matches
Binary file ./NVDAResman.kext/Contents/MacOS/NVDAResman matches

Link to comment
Share on other sites

hi!

I have 2 hackintoshes:

1. Asus p5ql pro, c2d e7200, gf8800gts512

2. asus p5ql pro, pentum dulacore e6300, gf8400gs512

 

Latest cham RC5 r568.

On first everything works great

on second - no video detection, only default 1024x768 resolution

 

Using strings for video

GraphicsEnabler=yes - and my second mac even doesn't load!

When i'm using PCEFI 10.6 everything is ok...

But with first hackintosh everything is OK!

What's wrong???

Please, advice!

Link to comment
Share on other sites

hi,I'm using the rev570 with <key>DropSSDT</key>

<string>Yes</string>

<key>GeneratePStates</key>

<string>Yes</string>

<key>GenerateCStates</key>

<string>Yes</string>

 

but sometimes the cpu fan slow down and then turn back as always.sorry for my english.i need help

Link to comment
Share on other sites

hi!

I have 2 hackintoshes:

1. Asus p5ql pro, c2d e7200, gf8800gts512

2. asus p5ql pro, pentum dulacore e6300, gf8400gs512

 

Latest cham RC5 r568.

On first everything works great

on second - no video detection, only default 1024x768 resolution

 

Using strings for video

GraphicsEnabler=yes - and my second mac even doesn't load!

When i'm using PCEFI 10.6 everything is ok...

But with first hackintosh everything is OK!

What's wrong???

Please, advice!

 

i am not sure but it maybe the PCI device Number (of the GPU ) which handles PCEFI other than new Chameleon RC5.

Boot with PCEFI and look with IOregistryExplorer aufter the PCI device . It can be 0 or 1.

Add the PCI device number (0,1) as an key in the boot.plist and try again RC5.

 

 

hi,I'm using the rev570 with DropSSDT

Yes

GeneratePStates

Yes

GenerateCStates

Yes

 

but sometimes the cpu fan slow down and then turn back as always.sorry for my english.i need help

 

OCed CPU ? If yes, automatic P States Generation often fails (to less cpu Volts for overclocking and/or wrong multiplier if OCed by FSB OC together with less multiplier setting in BIOS OC).

With OC (at least major OC speedupds) you must often use "old way" of DSDT P-States/C-States .

Link to comment
Share on other sites

First of all, well done indeed, the new release is looking more and more like a finished, stable piece of code.

 

However, I have had some difficulties with an AMD HD 5850 card. Here's some more details:

 

None of the official releases work with GraphicsEnabler=y, ATY_Init.kext (32bit mode) or with the Ati ROM (in attachment) that I dumped in Windows and then added in the Extra folder. Here I explain the various tries I made with no avail:

 

- Graphicsenabler=y, ATY_INIT.kext, AtiRrom=y = OSX loads, but it gets into the desktop with a black screen.

 

- All other configurations will result in a KP at boot, no matter what. Even with -X or with any possible combination of settings.

 

- Using Kabyl's bootloader and GraphicsEnabler=y is the only way to get OSX to boot with success, and with full use of the Radeon 5850, but the bootloader seems to be short on several features compared to the official one, most noticeably for the lack of sleep and for my i7 and interconnection speed not being recognised at all.

 

Is there any way to integrate the pretty awesome Graphics Card support of Kabyl's bootloader into the main trunk?

 

Would solve a lot of issues.

 

Good job and thanks.

 

1002_6899.rom.zip

Link to comment
Share on other sites

Is there any way to integrate the pretty awesome Graphics Card support of Kabyl's bootloader into the main trunk?

Hi TorqueX86 - Kabyl's excellent work will make it in when he's happy it's final. :(

Notes:

- Once the testing is finished, I'll submit the patch to my branch and then eventually to trunk, please be patient!

- The booter is based on my branch, so it includes the newly rewritten SMBIOS patcher.

Link to comment
Share on other sites

What is the best way to determine if Speedstep is working?

 

EDIT: Tried mark-i but it did not seem to be updating and it did not know what to do with all 6 cores of the 980x... Is there any other?

 

Revert your DSDT to its vanilla regarding P & C State

Link to comment
Share on other sites

Revert your DSDT to its vanilla regarding P & C State

 

 

DSDT does not have the mods for P and C states. I'm using RC5 and SSDT files in /extra.

 

According to the boot messages, the SSDTs seem to be loading, but then there is a message about CPU not supported. So I'm not sure it is working.

 

EDIT: Just rechecked the boot message: IT says "Unsupported CPU: P-states not generated!" I'd have to say that's either a bug or some undocumented feature :)

Link to comment
Share on other sites

Can someone explain why I am getting this message?

 

Unsupported CPU: P-states not generated!

 

My processor does indeed support EST, so either there is a bug in the detection algorithm or something else. It does correctly detect the correct number of cores.

 

It does appear to load the c-states from the SSDTs.

 

# Identification

Vendor : GenuineIntel

Brand String : Intel® Core i7 CPU X 980 @ 3.33GHz

Model Number : 44

Family Code : 6

Extended Model : 2

Extended Family : 0

Stepping ID : 2

Signature : 132802

 

# Address Bits

Physical Addressing : 36

Virtual Addressing : 48

 

# Multi-Core Information

Logical Processors (Threads) per Physical Processor : 32 <--Wrong yes This is how EvOTools detects it

Cores per Physical Package : 16 <--- Should be 6 Cores 12 logical

 

# Caches

## L1 Instruction Cache

Size : 32K

Line Size : 64B

Sharing : shared between 2 processor threads

Sets : 128

Partitions : 1

Associativity : 4

 

## L1 Data Cache

Size : 32K

Line Size : 64B

Sharing : shared between 2 processor threads

Sets : 64

Partitions : 1

Associativity : 8

 

## L2 Unified Cache

Size : 256K

Line Size : 64B

Sharing : shared between 2 processor threads

Sets : 512

Partitions : 1

Associativity : 8

 

## L3 Unified Cache

Size : 12M

Line Size : 64B

Sharing : shared between 32 processor threads

Sets : 12288

Partitions : 1

Associativity : 16

 

# Translation Lookaside Buffers

Instruction TLBs : 7 large, 0 small

Data TLBs : 32 large, 64 small

 

# Features

ACPI : Thermal Monitor and Software Controlled Clock

APIC : On-Chip APIC Hardware

CLFSH : CLFLUSH Instruction

CMOV : Conditional Move Instruction

CX16 : CMPXCHG16B Instruction

CX8 : CMPXCHG8 Instruction

DE : Debugging Extension

DS : Debug Store

DS-CPL : CPL Qualified Debug Store

DTES64 : 64-Bit Debug Store

EST : Enhanced Intel SpeedStep Technology

FPU : Floating-Point Unit On-Chip

FXSR : FXSAVE and FXSTOR Instructions

HTT : HyperThreading

MCA : Machine-Check Architecture

MCE : Machine-Check Exception

MMX : MMX Technology

MONITOR : MONITOR/MWAIT Instructions

MSR : Model Specific Registers

MTRR : Memory Type Range Registers

PAE : Physical Address Extension

PAT : Page Attribute Table

PBE : Pending Break Enable

PDCM : Perfmon and Debug Capability

PGE : Page Global Enable

POPCNT : POPCNT Instruction

PSE : Page Size Extension

PSE-36 : 36-Bit Page Size Extension

SEP : Fast System Call

SS : Self-Snoop

SSE : Streaming SIMD Extensions

SSE2 : Streaming SIMD Extensions 2

SSE3 : Streaming SIMD Extensions 3

SSSE3 : Supplemental Streaming SIMD Extensions 3

SSE4.1 : Streaming SIMD Extensions 4.1

SSE4.2 : Streaming SIMD Extensions 4.2

TM : Thermal Monitor

TM2 : Thermal Monitor 2

TSC : Time Stamp Counter

VME : Virtual Mode Extension

VMX : Virtual Machine Extensions

xTPR : xTPR Update Control

 

# Extended Features

EM64T : Intel Extended Memory 64 Technology

XD : Execution Disable

Link to comment
Share on other sites

if using smbios override using smbios.plist macpro 3,1 i got temperature heatsink reading and geekbench recognize it as hackintosh when using chameleon rc5. but when using chameleon rc4 and smbios overide geekbench recognize it as mac book pro.. how to make it recognize as real mac pro since before i upgrade my chameleon to rc5 its all fine..

 

i dont want to goback to chameelon rc4 cause rc5 is seems a lot faster than rc4.

 

gracias!!

Link to comment
Share on other sites

Hi all.

 

No idea if is so easy...

but it possible add this GFX card?

NVIDIA GeForce GTS 450

 

{ 0x10DE0DC4, "GeForce GTS 450" },

GPU Device Id: 0x10DE 0x0DC4

Version: 70.06.08.00.04

NVIDIA GeForce GTS 450 VGA BIOS

Copyright © 1996-2010 NVIDIA Corp.

 

Info coming from >>HERE

 

Fabio

 

EDIT

GTS not GTX typo error... :)

Link to comment
Share on other sites

Btw, is there a complete list of currently supported graphic cards? :)

The last one i have is from AnVAL branch here. Any other models added since then?

 

(I'm particularly interested in Nvidia 210, G210 and GT210 series.)

Link to comment
Share on other sites

XLR,

 

use the source browser on voodoo.forge, and check ati.c and nvidia.c, libsaio folder.

Intel has no support on the trunk.

Link to comment
Share on other sites

 Share

×
×
  • Create New...