AnVAL (ACPI Loader)

[00diabolic]

@00Diabolic ~~, try it without FixFSB key

 

Same no change at all

 

I added it to my boot.plist as so..

 

<key>FixFSB</key>

<string>Yes</string>

 

Does that matter or no?

[valv]

Same no change at all

 

I added it to my boot.plist as so..

 

<key>FixFSB</key>

<string>Yes</string>

 

Does that matter or no?

forgot to mention, it is yes by default. try altering the value to No. That was a confusing mistake from me, as future release would have the value to No as default.

[00diabolic]

I changed the Yes to No.. But same results as before.. CPU 2700 and sounds are distorted.

[JBraddock]

I too tried with No as a value. Same results.

[valv]

I changed the Yes to No.. But same results as before.. CPU 2700 and sounds are distorted.

As mitch_de explained, u should really look if u can get a drop into VoodooPower or whatever u 're using. Also if you oc 'ed it is not a good idea to keep same busratio. I 'd suggest u go with 12.5. Last but not least, it is bests to go with vanilla speed-steps and getting rid of 3rd party kexts as those could give false results (with most respect to SuperHai).

Greetz.

[00diabolic]

As mitch_de explained, u should really look if u can get a drop into VoodooPower or whatever u 're using. Also if you oc 'ed it is not a good idea to keep same busratio. I 'd suggest u go with 12.5. Last but not least, it is bests to go with vanilla speed-steps and getting rid of 3rd party kexts as those could give false results (with most respect to SuperHai).

Greetz.

 

I am working toward dropping Voodoopower to use native speedstep but I want to make sure its done right. So one step at a time. I have vanilla S/L/E now. I have not OC'ed my system at all. Its not even possible with my bios in the first place. When I refer to OC its because my cpu is being detected at a higher clock then its supposed to be. From my understanding in OSX you can only OC by increasing the fsb that OSX uses. I have no interest in doing that.

 

All that is at play here is the bootloader mis-identifying my T9300 cpu @2700mhz compared to @2500. Sorry if that was unclear before.

 

The only real issue with your bootloader beta3c is the system sounds being distorted and or delayed. I honestly could care less about the cpu detection because I can clean that up with smbios.plist and it does not affect performance (unlike having the FSB detected wrongly).

 

Hope you can get over this last hurdle Valv. Your bootloader is nearly there.

 

Thanks :-)

[donkey]

This is very good and easy method to dump your ACPI tables under Ubuntu

 

Thank You!

[DariosF]

Also with this boot file i get 3.33 ghz instead 4.3, and my clock is too fast.

[rednous]

valv, beta3c is OK for me again , thanx

 

sysctl -a | grep cpufreq

hw.cpufrequency = 2930000000
hw.cpufrequency: 2930000000
hw.cpufrequency_min: 2930000000
hw.cpufrequency_max: 2930000000

 

sysctl -a | grep busfreq

hw.busfrequency = 1064000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1064000000

[mitch_de]

My first test with 3c (Intel C2D 7300, 266/2660 @ 333/3000 (333 FSB , 9* Multi), PSTATES Vanilla 6*..9* 333 FSB)

All working here !

I uses WAIT= Yes to see all informations. Good: Much less messages like "ssdt1.aml not fond" than my old boot used before - i dont use any other than dsdt.aml.

I seen , without any special boot keys in .plist (only WAIT=Yes) :

Restart FIX injected, generated UUID xyz, PCI-UID 0 (cant remember others )

THANKS

sysctl -a | grep freq 
[size=1]hw.busfrequency = 1332000000 (OK; OC 333*4)
hw.cpufrequency = 3000000000 (OK, even OC 333*9 )
hw.tbfrequency = 1000000000
hw.busfrequency: 1332000000
hw.busfrequency_min: 1332000000
hw.busfrequency_max: 1332000000
hw.cpufrequency: 3000000000
hw.cpufrequency_min: 3000000000
hw.cpufrequency_max: 3000000000
hw.tbfrequency: 1000000000[/size]

 

UPPS ! I forgot that in my smbios.plist there were FSB + CPU Clock set as 333 / 3000

I removed those entries.

NOW

sysctl -a | grep freq hw.busfrequency = 1064000000  // 266 FSB <> 333 set in BIOS
hw.cpufrequency = 2670000000 // 2660 (266*10) <> 333*9 = 30000
[size=1]hw.tbfrequency = 1000000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1064000000
hw.cpufrequency: 2670000000
hw.cpufrequency_min: 2670000000
hw.cpufrequency_max: 2670000000
hw.tbfrequency: 1000000000[/size]

 

BUT : Speed is 100% same as before , Geekbench+XBench run same speed even shown now less FSB/less CPU Mhz !

So that FSB/CPU MHZ is onlycosmetic - at least in my case.

[00diabolic]

BUT : Speed is 100% same as before , Geekbench+XBench run same speed even shown now less FSB/less CPU Mhz !

So that FSB/CPU MHZ is onlycosmetic - at least in my case.

 

Exactly what I've been saying also. Thanks for confirming it

[valv]

All that is at play here is the bootloader mis-identifying my T9300 cpu @2700mhz compared to @2500.

Also with this boot file i get 3.33 ghz instead 4.3, and my clock is too fast.

It is easy to say that's actually not working, or even the whole thing is bullsh**t. what about fixing own issues (dsdt, speed-steps...). It can also be related to bad Bioses (not the case of most people over here).

@00Diabolic ~~, I 'll take Kabyl's own words from the other place:

"Well, after all this discussion, the conclusion is this:

• Your issue is in the BIOS.
  
• Maybe it can be fixed in the booter by hardcoding it to what your FSB is supposed to be.
  

Now, if someone cares to do it for you, that would be nice of him, but don't expect much because your issue is rare."

 

That is, I did not work "hardly" on this just to see other people concluding the boot-loader would not work for them, after reading special cases issues.

Now what? I did add another option, especially for you guyz. don't hate me for what i was saying

the new boot-loader has one new key: busratio. this is used to help u specify which multiplier u actually want to stick with.

That said, u 'd need to specify the Multiplier x 10 (momental Floating-Point workaround).

e.g.: if I would like to specify Multiplier 6, I type 60. For 10.5 I specify 150. Do not expect this one to work from first try.

Thus, if u have issues with it, u tell me and I correct myself (like we used to do in the past).

Also, I reverted FixFSB key to be false by default (default value: No). hope it actually works.

 

So that FSB/CPU MHZ is onlycosmetic - at least in my case.

maybe u 're right, but I 'd say it in another way: In your case edited values (Bios oc 'ed) take precedence over untouched stock values (actual code seems to stick only with those ones). even though, the boot-loader injects those last values in its possession (stock values). The intriguing point for me here is that the MSRs on which the detection algo relies on don't seem to reflect edited values, only stock frequencies seem to be handled. why this? to be honest I never was an accurate oc 'er. my knowledge in this "art" hits the wall of ignorance.

But, how could man then explain sound distortions some guyz are having. It seems to be more than cosmetic (in their case). It could also be caused by other kexts, but again the sound issue seems to occur only when the algo comes into play (same kexts, same conditions).

One thought is the fact that actual algo does not even rely on tsc, could let one pretend distortions are tsc related. how could this be explained? this is "Schwachsinn" so to say. am lost. I assume hpet and IRQs could be related to sound distortions also.

 

back to honorable testers, beta3d.zip

Please do try those new keys (on boot.plist), and to give feedback for each case. thank u very much for your support.

Greetz.

[rednous]

valv, here's mine beta3d report:

 

beta3d is no good for me: the sound glitches appeared again as in previous alphas (as far as i can recall 7 & 8). reverted back to beta3c.

 

beta3d reports my bus as 400MHz (i saw it's actually 266MHz on the first boot screen of my mobo after fresh restart) --> i don't care about the correct/ incorrect bus frequency display in OS X I care about flawless OS X performance

 

tried FixFSB with Yes and No, also busratio=11 but in all the combinations i get those nasty sound glitches

 

maybe somehow those keys (accompanied code) interact with the sound.

[00diabolic]

Thus, if u have issues with it, u tell me and I correct myself (like we used to do in the past).

 

Valv. No disrespect at all. I was just trying to clear up what I said before. I knew it came out a lil harsh. Sorry about that. I know that you are really helping me here by adding this extra code to your bootloader that fixes my bad bios. I hope a few other people can appreciate it like me.

 

Thank You again and Ill get right on testing this next release. Also an update.. I now have an almost vanilla system. I am still using voodoopower but I am about to delete it after this post. Already off nullcpupowermgmt and onto appleintelcpupowermgmt. I do not believe voodoopower is being used right now anyway. So we can safely rule it being an issue with regards to any problem I'm having with cpu detection.

 

:-)

[valv]

@rednous,

the new keys don't seem to have any effect. not good. I need to revise their respective implementations.

do u see any verbose message starting with "CPU: " at boot time (maybe use of Wait key would be necessary to be able catch something here)?

 

@00Diabolic ~~,

I fully understood what u meant. that's not the point. I actually tried to explain to those just discovering the boot-loader, to not get false conclusions when reading about your issue or DariosF's one. that's all I meant.

[JBraddock]

@Valv, I tried the latest build but it gave me KP and didn't let me to boot. Things I could note from KP message:

 

- panic (cpu 0 caller 0x2aa4f2)

- Mac Os Version: Not yet set

- BSD process name corresponding to current thread: Unknown...(I didn't remember the rest.)

 

Things that may help you diagnose the reason:

 

- I'd built a smbios.plist with the same settings you use

- I didn't use those two keys you mentioned.

 

Finally, generally speaking, things that I did notice with your bootloader

 

- After Chameleon menu, you know when we see that Apple logo, normally, my wifi and bluetooth indicator turns into blue once the image starts to spin. But it seems that with your bootloader, this process appears to be slower. I am not talking about a huge difference but may be it is something you need to know.

- I had two keyboards input set up and after your bootloader, one of them disappeared.

- I hadn't set up Time Machine icon to be shown in my menubar but it appeared in menu bar after your bootloader.

[rednous]

@rednous,

the new keys don't seem to have any effect. not good. I need to revise their respective implementations.

do u see any verbose message starting with "CPU: " at boot time (maybe use of Wait key would be necessary to be able catch something here)?

 

nope, i don't see CPU related messages (Wait=Yes as you told me at the beginning), and also don't see any after the Chameleon loads and the black OS X verbose screen appears. also now i checked the kernel.log --> all seems normal and no CPU related messages.

 

valv, today is debugging and testing day

[valv]

Finally, generally speaking, things that I did notice with your bootloader

 

- After Chameleon menu, you know when we see that Apple logo, normally, my wifi and bluetooth indicator turns into blue once the image starts to spin. But it seems that with your bootloader, this process appears to be slower. I am not talking about a huge difference but may be it is something you need to know.

- I had two keyboards input set up and after your bootloader, one of them had disappeared.

- I hadn't set up Time Machine icon to be shown in my menubar but it appeared in menu bar after your bootloader.

Thank you for posting those infos. But, are those happening only with latest beta3d, or since which one?

 

 

tried FixFSB with Yes and No, also busratio=11 but in all the combinations i get those nasty sound glitches

dear, I was actually explaining that if u need to go with 11 u need to type 110. One other thing, this should be inputted into boot.plist file and not as boot arg. key:busratio and its value: 110.

[00diabolic]

@00Diabolic ~~,

I fully understood what u meant. that's not the point. I actually tried to explain to those just discovering the boot-loader, to not get false conclusions when reading about your issue or DariosF's one. that's all I meant.

 

 

Ohh ok.. No harm no foul.. I have no voodoopower loaded on my system now.. Yippie.. Just need to add some more p-states for apple speedstep.

 

I just did my first boot with beta3d.. I got the following.. with fixFSB=No

 

CPU Clock: 1350 MHz

FSB Clock: 400 MHz

Bus Clock: 100 MHz

 

Sounds play fine again but the whole system is in hyper mode. Icons move fast and clock is running fast also. Thats the only issues I see.

 

I will try with Yes now..

 

As for busratio question.. My max is 12.5. So do I set it to 125? Please correct me if I'm wrong but isnt setting a busratio a fix for a system where the busratio is not detected by OSX through the bios? Mine is seen fine at 12.5 so I would think I would never need to set this. It does nothing to address my FSB issue from what Ive seen. All it does it mess with my CPU which I have had no issue with.

 

Thanks

[rednous]

dear, I was actually explaining that if u need to go with 11 u need to type 110. One other thing, this should be inputted into boot.plist file and not as boot arg. key:busratio and its value: 110.

 

yep, im a little bit dizzy all the time :-D

i'll try it right now and report back yep, in the boot.plist

[valv]

As for busratio question.. My max is 12.5. So do I set it to 125? Please correct me if I'm wrong but isnt setting a busratio a fix for a system where the busratio is not detected by OSX through the bios? Mine is seen fine at 12.5 so I would think I would never need to set this. It does nothing to address my FSB issue from what Ive seen. All it does it mess with my CPU which I have had no issue with.

It will not work, those new keys are not working. no need to test again. revert back to reasonable beta till I get those keys working. btw, u 're right about 125. but, regarding multiplier and fsb, having ratio at 12.5 and fsb at 200 should give u 2500 cpu, and not 2700. actually that was the point of adding busratio key.

[rednous]

valv, tried again the beta3d with key busratio=110 in boot.plist; busfreq is displayed as 400MHz in both System Profiler and Terminal --> sound glitches again going back to beta3c

[JBraddock]

- After Chameleon menu, you know when we see that Apple logo, normally, my wifi and bluetooth indicator turns into blue once the image starts to spin. But it seems that with your bootloader, this process appears to be slower. I am not talking about a huge difference but may be it is something you need to know.

- I had two keyboards input set up and after your bootloader, one of them disappeared.

- I hadn't set up Time Machine icon to be shown in my menubar but it appeared in menu bar after your bootloader.

 

 

Thank you for posting those infos. But, are those happening only with latest beta3d, or since which one?

 

Keyboard and Time Machine things happened when I first installed the beta3b. It didn't repeat the same action after the following versions. What I mean is that i added the deleted keyboard input again and it didn't disappear afterwards.

 

I don't know what you call that process, mounting or something else but it seems slower with all the versions I tried with compared to Chameleon RC4. But again, I am talking about a huge difference and i can't really say that overall boot time is slower.

 

Another thing I noticed:

 

I don't know if you read my other post in HDX topic but after applying some hacks that you provided, my audio information got lost and only Audio ID= 12 remained. In addition to this, there is new HDMI / DisplayPort Output information appeared under the Audio section. But with RC4, this audio information thing was not stable. Sometimes, it showed me the information below and sometimes the above one (Audio ID and HDMI / DisplayPort Output )

Intel High Definition Audio:

Audio ID:	12
Headphone:
Connection:	1/8-Inch Jack
External Microphone / iPhone Headset:
Connection:	1/8-Inch Jack
Speaker:
Connection:	Internal
External Microphone / iPhone Headset:
Connection:	1/8-Inch Jack
Internal Microphone:
Connection:	Internal
S/PDIF Optical Digital Audio Output:
Connection:	RCA

 

With your bootloader, as far as I noticed it shows me the above one. I am not sure what this exactly means but there it is.

 

Finally, I did already say that your bootloader fixed my scrolling problem appeared after dsdt fixes.

[jboehm]

@Valv ABSOLUTELY Wonderful!!!! Thanks so much!!

 

I'm using beta3c on a GA-EX58-UD5 with a Core i7-980x. Before beta3c I had problems with the OS time clock running fast and About This Mac reporting incorrect Processor speeds. These problems existed with AsereBLN-1.1.9, RC5Pre12, and your 6/4 build. Part of the problem has been that the 980x was just Apple 'supported' with the new kernel in 10.6.4.

 

In my current functional set up, I went with a very minimal /Extra folder. I build all of the *.aml file I could get my hands on thru Ubuntu and threw them in /Extra. The DSDT I build via d00d's method -- http://www.insanelymac.com/forum/index.php?showtopic=196771

 

With beta3c everything appears to be very useable. I need to go exploring all of the options with boot.plist and smbios.plist. SMBIOSdefaults=Yes is the only AnVAL specific flag I'm using so far and I'm not sure I understand that. It just sounded important.

 

Interesting things I've seen.

 

Processor in "About this Mac" says Unknown. But machdep.cpu.brand_string is correct. I still assume this is the current level of support for this new proc in 10.6.4 and don't know that there is anything your boot loader can do about it.

 

More a curiosity than an issue. System Profiler/Hardware/Bus Speed: 667Mhz. I assume this is bclk. My bclk is 166Mhz, up from the Core i7 default of 133Mhz. Whatever your doing, it works. My clock works and the computer knows my correct processor speed even if it displays the bclk incorrectly.

 

BIG Thanks Again!!

 

If you need any diagnostic dumps from me please ask.

 

Jon

[kizwan]

Hi valv,

 

Thank you for your works. I'm very happy with alpha5. It works wonderfully. Today I have the opportunity to test your beta3d and these are the results. I included alpha5 results for comparison. Tested on Acer Aspire 9420. It have vanilla speedstep.

alpha5 sysctl results:-

kizwans-MacBook-2:~ kizwan$ sysctl -a | grep freq
hw.busfrequency = 664000000
hw.cpufrequency = 997000000
hw.tbfrequency = 1000000000
hw.busfrequency: 664000000
hw.busfrequency_min: 664000000
hw.busfrequency_max: 664000000
hw.cpufrequency: 997000000
hw.cpufrequency_min: 997000000
hw.cpufrequency_max: 997000000
hw.tbfrequency: 1000000000
kizwans-MacBook-2:~ kizwan$ sysctl -a | grep CPU
machdep.cpu.brand_string: Intel® Core™2 CPU         T5600  @ 1.83GHz
kizwans-MacBook-2:~ kizwan$ sysctl -a | grep -i CPU
hw.ncpu = 2
hw.cpufrequency = 997000000
hw.availcpu = 2
hw.ncpu: 2
hw.activecpu: 2
hw.physicalcpu: 2
hw.physicalcpu_max: 2
hw.logicalcpu: 2
hw.logicalcpu_max: 2
hw.cputype: 7
hw.cpusubtype: 4
hw.cpu64bit_capable: 1
hw.cpufamily: 1114597871
hw.cpufrequency: 997000000
hw.cpufrequency_min: 997000000
hw.cpufrequency_max: 997000000
machdep.cpu.max_basic: 10
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel® Core™2 CPU         T5600  @ 1.83GHz
machdep.cpu.family: 6
machdep.cpu.model: 15
machdep.cpu.extmodel: 0
machdep.cpu.extfamily: 0
machdep.cpu.stepping: 6
machdep.cpu.feature_bits: 3219913727 58301
machdep.cpu.extfeature_bits: 537921536 1
machdep.cpu.signature: 1782
machdep.cpu.brand: 0
machdep.cpu.features:  FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX 
FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM
machdep.cpu.extfeatures:  SYSCALL XD EM64T LAHF
machdep.cpu.logical_per_package: 2
machdep.cpu.cores_per_package: 2
machdep.cpu.microcode_version: 199
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.sub_Cstates: 139808
machdep.cpu.thermal.sensor: 1
machdep.cpu.thermal.dynamic_acceleration: 0
machdep.cpu.thermal.invariant_APIC_timer: 0
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.arch_perf.version: 2
machdep.cpu.arch_perf.number: 2
machdep.cpu.arch_perf.width: 40
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.events: 0
machdep.cpu.arch_perf.fixed_number: 0
machdep.cpu.arch_perf.fixed_width: 0
machdep.cpu.cache.linesize: 64
machdep.cpu.cache.L2_associativity: 6
machdep.cpu.cache.size: 2048
machdep.cpu.tlb.inst.small: 128
machdep.cpu.tlb.inst.large: 8
machdep.cpu.tlb.data.small: 16
machdep.cpu.tlb.data.small_level1: 256
machdep.cpu.tlb.data.large: 16
machdep.cpu.tlb.data.large_level1: 32
machdep.cpu.address_bits.physical: 36
machdep.cpu.address_bits.virtual: 48
machdep.cpu.core_count: 2
machdep.cpu.thread_count: 2

beta3d sysctl results:-

kizwans-MacBook-2:~ kizwan$ sysctl -a | grep freq
hw.busfrequency = 400000000
hw.cpufrequency = 997000000
hw.tbfrequency = 1000000000
hw.busfrequency: 400000000
hw.busfrequency_min: 400000000
hw.busfrequency_max: 400000000
hw.cpufrequency: 997000000
hw.cpufrequency_min: 997000000
hw.cpufrequency_max: 997000000
hw.tbfrequency: 1000000000
kizwans-MacBook-2:~ kizwan$ sysctl -a | grep CPU
machdep.cpu.brand_string: Intel® Core™2 CPU         T5600  @ 1.83GHz
kizwans-MacBook-2:~ kizwan$ sysctl -a | grep -i CPU
hw.ncpu = 2
hw.cpufrequency = 997000000
hw.availcpu = 2
hw.ncpu: 2
hw.activecpu: 2
hw.physicalcpu: 2
hw.physicalcpu_max: 2
hw.logicalcpu: 2
hw.logicalcpu_max: 2
hw.cputype: 7
hw.cpusubtype: 4
hw.cpu64bit_capable: 1
hw.cpufamily: 1114597871
hw.cpufrequency: 997000000
hw.cpufrequency_min: 997000000
hw.cpufrequency_max: 997000000
machdep.cpu.max_basic: 10
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel® Core™2 CPU         T5600  @ 1.83GHz
machdep.cpu.family: 6
machdep.cpu.model: 15
machdep.cpu.extmodel: 0
machdep.cpu.extfamily: 0
machdep.cpu.stepping: 6
machdep.cpu.feature_bits: 3219913727 58301
machdep.cpu.extfeature_bits: 537921536 1
machdep.cpu.signature: 1782
machdep.cpu.brand: 0
machdep.cpu.features:  FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX 
FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM
machdep.cpu.extfeatures:  SYSCALL XD EM64T LAHF
machdep.cpu.logical_per_package: 2
machdep.cpu.cores_per_package: 2
machdep.cpu.microcode_version: 199
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.sub_Cstates: 139808
machdep.cpu.thermal.sensor: 1
machdep.cpu.thermal.dynamic_acceleration: 0
machdep.cpu.thermal.invariant_APIC_timer: 0
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.arch_perf.version: 2
machdep.cpu.arch_perf.number: 2
machdep.cpu.arch_perf.width: 40
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.events: 0
machdep.cpu.arch_perf.fixed_number: 0
machdep.cpu.arch_perf.fixed_width: 0
machdep.cpu.cache.linesize: 64
machdep.cpu.cache.L2_associativity: 6
machdep.cpu.cache.size: 2048
machdep.cpu.tlb.inst.small: 128
machdep.cpu.tlb.inst.large: 8
machdep.cpu.tlb.data.small: 16
machdep.cpu.tlb.data.small_level1: 256
machdep.cpu.tlb.data.large: 16
machdep.cpu.tlb.data.large_level1: 32
machdep.cpu.address_bits.physical: 36
machdep.cpu.address_bits.virtual: 48
machdep.cpu.core_count: 2
machdep.cpu.thread_count: 2

diff between alpha5 & beta3d:-

kizwans-MacBook-2:~ kizwan$ diff alpha5 beta3d 
2c2
< hw.busfrequency = 664000000
---
> hw.busfrequency = 400000000
5,7c5,7
< hw.busfrequency: 664000000
< hw.busfrequency_min: 664000000
< hw.busfrequency_max: 664000000
---
> hw.busfrequency: 400000000
> hw.busfrequency_min: 400000000
> hw.busfrequency_max: 400000000

alpha5 About this Mac:-

beta3d About this Mac:-

alpha5 hardware:-

beta3d hardware:-

alpha5 memory:-

beta3d memory:-

alpha5 MSR Tools:-

beta3d MSR Tools:-

alpha5 Geekbench result:-

beta3d Geekbench result:-

 

smbios.plist:-

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>SMbiosversion</key>

<string>MB51.88Z.0073.B06.0810291326</string>

<key>SMmanufacter</key>

<string>Apple Inc.</string>

<key>SMproductname</key>

<string>MacBook5,1</string>

<key>SMsystemversion</key>

<string>1.0</string>

<key>SMserial</key>

<string>W89039YA1AQ</string>

</dict>

</plist>

 

com.apple.Boot.plist:-

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>arch=i386</string>

<key>Timeout</key>

<string>5</string>

<key>SMBIOSdefaults</key>

<string>Yes</string>

<key>Legacy Logo</key>

<string>Yes</string>

<key>RestartFix</key>

<string>No</string>

</dict>

</plist>

I use RestartFix=No because I already have correct FADT/FACP table.

 

Sorry for long post.