226 replies to this topic

[imacken]

DigitalDJ, on Sep 30 2009, 01:39 PM, said:

The string is simply AQU= not AQU=0105.

Weird, putting AQU=0105 produced the right result!

DigitalDJ, on Sep 30 2009, 01:39 PM, said:

I personally put mine in /E/E, seemed to work fine. I will investigate though. Those having trouble, are you on Snow Leopard or Leopard?

Didn't work for me in E/E. Had to be S/L/E with Kext Utility.

DigitalDJ, on Sep 30 2009, 01:39 PM, said:

As for your 10.5 output...are you running any AppleSMBIOS/SMBIOS Extensions? They will likely conflict with this injector. It is mainly for use with Chameleon SMBIOS patching (and no SMBIOS injectors).

I don't use this injector on 10.5 as it already reports correctly the CPU info.  I was only wondering why there was more complete into there.

[DigitalDJ]

imacken, on Sep 30 2009, 11:08 PM, said:

I don't use this injector on 10.5 as it already reports correctly the CPU info.  I was only wondering why there was more complete into there.

It isn't complete info.

You have some sort of custom patched System Profiler. No actual Mac reports on CPU features or uses the full string of the CPU for the Processor Name. You're either using a patched System Profiler or some sort of extra injector. Either way, not vanilla

imacken, on Sep 30 2009, 11:08 PM, said:

Weird, putting AQU=0105 produced the right result!

It probably still works, but the data you entered is invalid. It's a Base64 encoded string, 0105 would be invalid, so it is probably ignored. It will work as simply AQU=

[yeehaa]

Apple.User, on Sep 30 2009, 05:22 AM, said:

But looking closer at the IORegistryExplorer using 10.5.8  I did have noticed something very interesting... there was one tiny difference: the ACPI_SMC_PlatformPlugin  is having the PerformaceStateArray (with 10 values) only while the dsdt is on P00x format(!) Any ideas why is this so? Why the P00x vs CPUx etc notation makes such difference ? Nevertheless, the system works at its best  and the IORegistryExplorer looks now the same with the macpro4,1.

you need to change every instance of Pxx to CPU. otherwise you will miss a lot of "features" like PerformanceStateArray (speedstep!!). this particular problem maybe because your SSDT table maybe referencing your Pxx objects rather than the CPU object. you have lot of readin to do

@DijitalDJ: thanks for the tip. and nice to see you active here!

[asapreta]

And processors like Pentium D's? How they should be recognized?

[Azimutz]

Yup.. works fine. But, i'm not planing using it.. i just prefer to edit About This Mac and see my real CPU there.. don't mind if it doesn't show on System Profiler. The problem is, this doesn't fool many apps (check pic.. it all depends on were the apps go get the info) and can only return CPU families used by Apple.
Anyway, that's just me not criticizing, or i wouldn't have tested it.

About loading the kext from Extra.. It loads fine from /Extra/Extensions.mkext.. it may need OSBundleRequired edited, from Safe Boot to Root or Local-Root to load from /Extra/Extensions. Don't think it's a dependencies problem (looking at the plist).

Thanks

p.s.: upss.. forgot about Regie SE and Processor Pane.. those say i have Pentium 4 on Snow, unknown on Leo.
And some (Onyx, some irc scripts) even say i have Intel 80486 (i486) ... whatever..

Attached Files

•  2009_09_30_1658.png   755.35K   348 downloads

Edited by Azimutz, 01 October 2009 - 01:29 AM.

[Apple.User]

yeehaa, on Sep 30 2009, 02:48 PM, said:

you need to change every instance of Pxx to CPU. otherwise you will miss a lot of "features" like PerformanceStateArray (speedstep!!). this particular problem maybe because your SSDT table maybe referencing your Pxx objects rather than the CPU object. you have lot of readin to do

Thanks @yeehaa


• I have an Asus Rampage II X58 motherboard I don't have an SSDT table!
  
• I just use the Chameleon RC3 with the default kexts.
  
• I have changed every instance of Pxx to CPUx.

The question is the following:
P001 ---> CPU0 or  P001 ---> CPU1?
And do I need to copy to each line this ( 0x00000810, 0x06)  like on MacPro 4,1?

I can see that the SSDT Table is definitely referencing Pxx objects...
How do I rectify this?
Thanks

[DigitalDJ]

asapreta, on Oct 1 2009, 02:00 AM, said:

And processors like Pentium D's? How they should be recognized?

Unfortunately, probably still Unknown. You can't force a different CPU type, the type needs to be valid for your CPU as far as I know. However, experiment with it. System Profiler does not have a string for Pentium Ds or Pentium 4s, maybe they'll show up as Core Solo/Duos? However, I'm not sure of that CPU type yet.

[Superhai]

DigitalDJ, on Sep 30 2009, 03:31 PM, said:

Do you happen to have the source for this laying around? Or any idea on the other cpu-types for other CPUs?

No I don't have the source with that mod anymore, this is like maybe two years ago. It is a two line add, so it is not hard. I looked at your source, first time you made a kext maybe? Anyway you do it very cumbersome.

I experimented with the cpu-types, they are of two bytes (if you have more you will get an error message) it was fun when it reported PowerPC, I don't remember which was for whom anymore.

[THe KiNG]

Hi and many thanks for this DigitalDJ
CPU is recognized now in about this mac and system profiler, still on interconnect-speed it say 533 MT/s instead 4.8 GT/s
Any idea how to fix this?
Also do u think Serial Number (processor tray) can be added?

Thanks!

P.S. on Reggie_SE still it say unknown cpu

[xhala_debru]

Kext installed in /E/E everything is fine.
Q9450 recognized as Xeon as said before.

Now I'll try to make my cpu speed right.

Thanks

[asapreta]

Azimutz, on Sep 30 2009, 01:45 PM, said:

Yup.. works fine. But, i'm not planing using it.. i just prefer to edit About This Mac and see my real CPU there.. don't mind if it doesn't show on System Profiler. The problem is, this doesn't fool many apps (check pic.. it all depends on were the apps go get the info) and can only return CPU families used by Apple.
Anyway, that's just me not criticizing, or i wouldn't have tested it.

About loading the kext from Extra.. It loads fine from /Extra/Extensions.mkext.. it may need OSBundleRequired edited, from Safe Boot to Root or Local-Root to load from /Extra/Extensions. Don't think it's a dependencies problem (looking at the plist).

Thanks

(Olá Azi)

Hello! which code did you used? I see you got a "Core2Duo" CPU. Aren't you using Chamaleon RC3 to get rid of Extensions.mkext?

Abraço

[Apple.User]

harshw, on Sep 30 2009, 01:01 PM, said:

On my ASUS P6T SE ...
Notice the 'alias' to 'CPU'

There is a definitely mapping  (P00x, CPUx) using Alias (SourceObject, AliasObject)
Arguably, creating objects for Processor Alias() is a "bad" idea; any idea why a BIOS author would do that? What was the purpose of those useless statements? One can load most OS like Linux and Windows without Alias(). And from a programmers perspective there is no actual need; actually these Processor Alias() statements produce more bugs and create unnecessary debugging variables in some Operating Systems. And thats why in OSX we have to remove them. Since AcpiWalkNamespace treats CPUx as the real Processor objects, the probe order for acpi(4) bus children will be P001, CPU1, P002, CPU2, P003, CPU3, P004, CPU4. This is very bad, because half of processors are attached twice and half -- aren't attached at all. Moreover, est (Enhanced SpeedStep cpufreq driver) isn't able to get _PSS for CPUx, so P-states will be missing for half of processors!

And that's why the great MacPro has no 'Alias' to 'CPU' statements.

Observing the objects "P001" and "CPU1", they have the same type and flags. In other words we shouldn't have to distinguish between the two. They should act the same according to the ACPI spec.

According to the ACPI specification: Alias (SourceObject, AliasObject)
Creates a new object named AliasObject that refers to and acts exactly the same as SourceObject. AliasObject is created as an alias of SourceObject in the namespace. The SourceObject name must already exist in the namespace. If the alias is to a name within the same definition block, the SourceObject name must be logically ahead of this definition in the block.

[amf5]

DigitalDJ, on Sep 30 2009, 06:34 AM, said:

Interesting. Would you mind trying "ioreg -l" at Terminal and posting the output here (as a text file)...Or take a look at tweak41's post and find that section.

Sure, here you go.

Attached Files

•  ioreg.txt   350.24K   0 downloads

[stickpin]

Nice one DigitalDJ!
Thanks alot!
Works great from EFI Partition in Extrantions.mkext.

[harshw]

yeehaa, on Sep 30 2009, 05:48 PM, said:

you need to change every instance of Pxx to CPU. otherwise you will miss a lot of "features" like PerformanceStateArray (speedstep!!). this particular problem maybe because your SSDT table maybe referencing your Pxx objects rather than the CPU object. you have lot of readin to do

@DijitalDJ: thanks for the tip. and nice to see you active here!

You mean like this ? But this comes even with the Pxx CPU identifier ... or should there be more values than 10 ?

 Screen_shot_2009_09_30_at_23.20.27.png   76.47K   229 downloads

[MeAngry]

Thanks for this, shows up nicely for my Core i7 (as Quad-Core Xeon) with the QPI value. For those of you using a CPU with a QPI, fill in the correct value divided by 4 in SMexternalclock. For example, I filled in 1200 to get a value of 4.8GT/s in System Profiler, which is correct for my i920.

I do have one remark though, I think the OSBundleRequired or dependencies aren't correct yet. The kext works fin in /E/E, but only when I boot with -v, which gives kexts a small delay in loading.
If I boot without -v, AppleIntelCPUPowerManagement panics immediately. I'm gonna try some different OSBundleRequired values now, and see if it helps.

[sbg]

Works for me in E/E folder on SL 10.6.1 (GA-P35-DS3P, E8500).
Thanks

[amf5]

For what it's worth, I was able to get this to load from the Extra directory on my EFI partition only after I changed OSBundleRequired to "Local-Root".

[xuanlian]

It's useful     my cpu is recognized

[THe KiNG]

MeAngry, on Oct 1 2009, 01:23 AM, said:

Thanks for this, shows up nicely for my Core i7 (as Quad-Core Xeon) with the QPI value. For those of you using a CPU with a QPI, fill in the correct value divided by 4 in SMexternalclock. For example, I filled in 1200 to get a value of 4.8GT/s in System Profiler, which is correct for my i920.

Thanks mate!
That did the trick(SMexternalclock=1200) now I have 4.8 GT/s