AnVAL (ACPI Loader)

[DariosF]

i've tried your last work, but i hve the same problem. I've also change my bios setting (9.5 x instead 10x, with busratio=9.5 in my com.apple.boot.plist) but the bootloader doesn't read my oc settings.

[00diabolic]

Valv.. I tried a boot without fixFSB and I got 1/2 speed FSB and 1/2 speed CPU.. I updated my last post with details.. So for sure your new code is working now.

 

What I dont get is before with your previous code I got 733fsb so You mus have really overhauled the whole thing. I figured the only big change was the new FixFSB flag.

 

Looking forward to your next release.. Thanks :-)

[JBraddock]

@Valv, I am having random and rare KPs with the bootloader. I am using the beta3c. It happened with the previous versions as well. I used -v and noticed that It's something related to CPU. Could it be because of the fact that speed-step process hasn't been completed yet, which you already know?

[valv]

oops! I didn't remember which version that actually was

This one is intended to fix too much if not all those issues we 've been battling against, last days.

One thing though: Because of the complicated process implementing a floating-point function into the code, I preferred to go back to how it was handled before last change. Thus, busratio is multiplied by 10 again. Sorry to mess with your nerves; It played all day long with mine

 

here it is, beta4b.zip

Special Thanks: Kabyl and cparm

 

attention: again, we need to specify the busratio value x10. e.g.: for 10.5 we type 105. we'll stick with this for now,

till I get a working function for floating-points.

Greetz

[JBraddock]

@Valv, I tried the latest version but didn't use bus-ratio key as I don't know what it is. My cpu information and bus frequency are same as before. Booting with this version seems smoother. I'll keep an eye on it.

 

Anything else you want me to report?

[XLR]

Beta4b seems to boot 2 seconds faster than beta3b:

 

 

What busratio should i specify for my E6500? If it has multiplier=11 does it means busratio=110?

 

Should i try FixFSB=Yes?

[valv]

didn't use bus-ratio key as I don't know what it is.

busRatio is your cpu multiplier so to say. FSB * BusRatio = CPU.Frequency

 

What busratio should i specify for my E6500? If it has multiplier=11 does it means busratio=110?

 

Should i try FixFSB=Yes?

u 're right about the busratio's value, so should it be. But u don't need it if u don't use FixFSB as I concatenated the first into the second.

 

That's not the final idea though, as both can now be propagated to other models and become more of general use.

Initially those keys was intended to help everybody who's getting hard times to make OSX stick with correct FSB and CPU frequencies.

In the future it would be even possible to inject custom FSB values (thanks Azi for the idea). And then with a custom BusRatio we can begin a new era of over-clocking: on the boot-loader's side. Maybe it is not of a use to most of us, but those with limited bioses could enjoy it. And maybe am saying bullsh**t. we 'll see what the future reserves.

Greetz

[00diabolic]

Update on testing of beta4b.

 

Without FixFSB=No & Busratio=125 I get the following:

 

CPU Clock: 2500 MHz

FSB Clock: 736 MHz

Bus Clock: 184 MHz

 

* System speed is fine, system sounds fine and seems to run fast.

 

With FixFSB=Yes & Busratio=125 I get the following:

 

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

* system is slow and sounds are delayed and clock is slow.

 

Valv I have a question for you about restartfix.

 

Ive determined I only need restart fix for my restart. Here is what I get with restartfix=Yes or no.

 

No shutdown works.

Yes shutdown works

No restart = black screen

Yes restart = shutdown

 

Is there anything else you could suggest to me to fix this besides using evoreboot? That kext does solve my problem but it would be nice to figure out something else. You mentioned my FADT table but would just extracting it be enough? Also I still dont know how I can extract it. What do I use to extract it.

 

Thanks

[rednous]

valv, thanx a bunch for the beta4b

i'll test it thoroughly and report when i get back at home later.

 

Cheers

[mitch_de]

BETA4b (C2D 7300, OC 333 FSB (266 default), OC 9* Busratio(10*default) in BIOS)

Now busratio setting worked first time : 90 gives 9* , GREAT!

FSB is wrong: 266 MHz shown, not 333 , so CPU = 2,4 GHZ vs 3,00 GHz

[JBraddock]

@Valv, with the beta4b, resuming sleep doesn't work. It just starts the OSX but says nothing on wake kernel or something. There is a platform failure message in Console.

I tried with the beta3c and it is working in this sense.

Do you have a special key that I can add to the boot.plist to wake the OSX?

[valv]

With FixFSB=Yes & Busratio=125

Try to replace Busratio inside your boot.plist with busratio. Am not sure if it is case sensitive aware or not.

 

 

BETA4b (C2D 7300, OC 333 FSB (266 default), OC 9* Busratio(10*default) in BIOS)

Now busratio setting worked first time : 90 gives 9* , GREAT!

FSB is wrong: 266 MHz shown, not 333 , so CPU = 2,4 GHZ vs 3,00 GHz

Tried to boot without those 2 keys? For ease of use u can edit FixFSB value to No.

 

@Valv, with the beta4b, resuming sleep doesn't work. It just starts the OSX but says nothing on wake kernel or something. There is a platform failure message in Console.

I tried with the beta3c and it is working in this sense.

Do you have a special key that I can add to the boot.plist to wake the OSX?

It is working for me. Please post your boot.plist

[mitch_de]

BETA4b (C2D 7300, OC 333 FSB (266 default), OC 9* Busratio(10*default) in BIOS)

Now busratio setting worked first time : 90 gives 9* , GREAT! FSB is wrong: 266 MHz shown, not 333 , so CPU = 2,4 GHZ vs 3,00 GHz

Beta4B: Now back* and set FixFSB=No as you told me to do: Sir, yes Sir ! - leaved busratio=90 (i guess then BR isnt "seen" if FSB=No)

 

WORKS NOW !!! FSB +BUSRATIO is OK now: 333 * 9 = 3.0 GHz (FixFSB=Yes + busratio=90 = 266*9=2,4 Ghz)

GREAT - also Sleep + Shotdown works without any other .kext (no sleepenabler(is independend from boot), no openhaltrestart) by boot Beta3c+!!!

 

 

back* : I was i bit feared, because setting FixFSB=No in Beta4 (not new Beta4b) = system hangs with no screen.

[valv]

@mitch_de,

Thank u for the feedback, and glad it works now. but, always in a manner of testing, would u mind reverting back to initial bios values (266 * 10), and then using FixFSB (Yes) with altered busratio (something like 11 or 9).

Greetz,

[JBraddock]

It is working for me. Please post your boot.plist

 

Here is my boot.plist. I am not sure if it is related to this subject but I noticed that in your LegacyHdx18.kext file, there is a reference to ACPI_SMC_PlatformPlugin. I'd changed my mac model to MacBookPro5.4 and I wonder if I should install this kext or it is modified according to your CPU. I am using AHCIPortInjector, which as its name suggests adds ICH9 support. Should I remove it and use your kext?

 

Other than that, I am still using OpenHaltRestart.kext.

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Boot Graphics</key>
<string>Yes</string>
<key>GraphicsEnabler</key>
<string>y</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>arch=i386 boot-uuid=3978036E-5D31-38F6-9BE8-92CBDBA392F7</string>
<key>Legacy Logo</key>
<string>no</string>
<key>Quiet Boot</key>
<string>no</string>
<key>Theme</key>
<string>SnowKitty</string>
<key>Timeout</key>
<string>5</string>
<key>USBBusFix</key>
<string>Yes</string>
<key>UHCIreset</key>
<string>Yes</string>
<key>EthernetBuiltIn</key>
<string>yes</string>
<key>DropSSDT</key>
<string>No</string>
<key>DSDT</key>
<string>/Extra/dsdt.aml</string>
<key>SMBIOS</key>
<string>/Extra/smbios.plist</string>
<key>SMBIOSdefaults</key>
<string>Yes</string>
</dict>
</plist>

 

This is my smbios.plist file.

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>SMbiosvendor</key>
<string>Apple Computer, Inc.</string>
<key>SMbiosdate</key>
<string>06/15/2009</string>
<key>SMboardmanufacturer</key>
<string>Apple Computer, Inc.</string>
<key>SMfamily</key>
<string>MacBook Pro</string>
<key>SMmanufacturer</key>
<string>Apple Inc.</string>
<key>SMproductname</key>
<string>MacBookPro5.4</string>
<key>SMsystemversion</key>
<string>1.0</string>
<key>SMmemtype</key>
<string>19</string>
<key>SMmemspeed</key>
<string>800</string>
<key>SMmemmanufacter</key>
<string>Apple Computer Inc.</string>
<key>SMexternalclock</key>
<string>266</string>
<key>SMmaximalclock</key>
<string>2261</string>
</dict>
</plist>

 

I am not using Voodoopowermanagement or nullapplepowermanagement. I applied all the hacks you provided except RTC.

Finally, I set my sleep mode with the following code as "secure virtual memory" option is checked under the Security section.

 

sudo pmset -a hibernatemode 7

 

Sorry for the long post. I just don't know which information to provide you with so I just throw everything on the table.

[valv]

@JBraddock,

Try using same keys as me (as showed on the other topic). also use this instead sudo pmset -a hibernatemode 3

[JBraddock]

@JBraddock,

Try using same keys as me (as showed on the other topic). also use this instead sudo pmset -a hibernatemode 3

 

It resumed the sleep once I updated my boot.plist according to yours and unchecked "secure virtual memory" and changed hibernatemode to 3.

I didn't include oemDSDT, oemFADT,oemSSDT, FADT and ECDT keys as I don't have those two aml files.

 

It didn't wake with the power button but I am sure it is not something related to the bootloader.

[00diabolic]

Try to replace Busratio inside your boot.plist with busratio. Am not sure if it is case sensitive aware or not.

 

Valv... Ok I set it to busratio=125

 

It only slightly changed my results though..

 

In about this mac I now see that my CPU says 2.4ghz.. However the speed of the system is the same and in all other places the system reports the following:

 

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

I do get this from kext utility..

 

CPU TYPE: Intel® Core2 Duo CPU T9300 @ 2.50GHz

Core: 2400(2400) MHz x 12.0(12.0) Bus: 200 MHz FSB: 800 MHz

 

Interesting this is with busratio=125 and obviously kext utility pulls the same info as ATM. Its as if I does not see the 5 and takes a flat number of 12 as my multiplier. This might mean the busratio key has an issue with 1/2 values. Ill try 13.

 

I tried busratio=130 and it did see 13. See below. However this still does nothing for the real issue which is the system sounds running slow and other things sluggish and random KP which I have been getting for a while and did not attribute to your boot loader fixFSB till now.

 

CPU TYPE: Intel® Core2 Duo CPU T9300 @ 2.50GHz

Core: 2600(2600) MHz x 13.0(13.0) Bus: 200 MHz FSB: 800 MHz

 

With busratio=130 this remains the same. I really dont think the busratio key does anything for my system as far as me actually needing it I mean. Normally the boot loader correctly detects my busratio.

 

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

I also went ahead and tried my system again with no busratio key set but just FixFSB and my system does receive a higher busratio from using the fixFSB key.

 

CPU TYPE: Intel® Core2 Duo CPU T9300 @ 2.50GHz

Core: 2700(2700) MHz x 13.5(13.5) Bus: 200 MHz FSB: 800 MHz

 

So this explains why I get my 2700mhz instead of 2500mhz. Perhaps if you can fix that you can get the system speed issue corrected and the sounds and clock will run normal again.

 

So the still out standing issue is the system speed which is messed up and can cause KPs. I think using the busratio key is useless for my system it will not allow it to be fully used. So setting it higher is kinda superficial as my system will not use it.

 

Hope you can get this going. You mentioned custom FSB key.. Isnt that easier? Or isnt just forcing numbers rounded up easier? So an algorithm that looks at FSB and says no odd numbers allowed.. So if it gets 184fsb it forces 200mhz. I mentioned that before. Not sure you read it though.

 

Thanks

[valv]

Interesting this is with busratio=125 and obviously kext utility pulls the same info as ATM. Its as if I does not see the 5 and takes a flat number of 12 as my multiplier. This might mean the busratio key has an issue with 1/2 values.

Not True!

Actually, that's why I reverted back to "busratiox10" workaround. Thus the function behind this takes the string u where typing in front of "busratio" key and converts it into integer; no floating points there.

here are the resluts I normally get w/o busratio:

Then, if I add a busratio key and give 85 (my initial busratio is 9.5) to try with a BusRatio of 8.5, I get these:

Greetz,

[00diabolic]

Not True!

Actually, that's why I reverted back to "busratiox10" workaround. Thus the function behind this takes the string u where typing in front of "busratio" key and converts it into integer; no floating points there.

here are the resluts I normally get w/o busratio:

Then, if I add a busratio key and give 85 (my initial busratio is 9.5) to try with a BusRatio of 8.5, I get these:

Greetz,

 

Mmmm Well I was not sure about that but I had clearly set busratio=125 and it got it as 120 so something is wrong there. Either way busratio is not a value my system has trouble detecting.

 

I typically see it detected correctly without the flag.. as such..

 

CPU TYPE: Intel® Core2 Duo CPU T9300 @ 2.50GHz

Core: 2500(1200) MHz x 12.5(6.0)

 

I tried that version of beta4b you posted and just like when I tried this one last time. ATM gets my CPU right and everything is great with this one except the slow clock and system sounds just like the last few releases and the current when using FixFSB. There is something that is off and I'm not sure what it is. Its something like the realtime clock or something I have no idea I'm just guessing. Anyway this algorithm is great for me if the other part of its code can be fixed.

 

Thanks

00D

[jboehm]

Valv,

 

How does the busratio flag work? It is cosmetic, so the OS shows the correct frequency or is there real frequency changes?

 

How does busratio work on Nehalem family processors (core i*) where there is no FSB?

 

Thanks,

Jon

[bs0d]

has it not dawned on anyone ... just changing the fsb in osx doesnt actually change the speed ?

 

you need to change it in the hardware, and thats motherboard specific usually.

 

bs0d.

[kizwan]

has it not dawned on anyone ... just changing the fsb in osx doesnt actually change the speed ?

 

you need to change it in the hardware, and thats motherboard specific usually.

 

bs0d.

This is common sense. No need to bring it up, particularly in this thread. What everyone trying to do here is not to overclocked their CPU speed. They are trying to correct the CPU speed detection where CPU speed is not correctly detected in OS X.

 

Greetz,

[bs0d]

This is common sense. No need to bring it up, particularly in this thread. What everyone trying to do here is not to overclocked their CPU speed. They are trying to correct the CPU speed detection where CPU speed is not correctly detected in OS X.

 

Greetz,

 

the cpu is being detected correctly .. its the hardware thats set it up wrong.

 

the cpu detection in chameleon works well, but cant fix broken hardware.

[kizwan]

Valv,

 

How does the busratio flag work? It is cosmetic, so the OS shows the correct frequency or is there real frequency changes?

 

How does busratio work on Nehalem family processors (core i*) where there is no FSB?

 

Thanks,

Jon

Even though Nehalem processor family doesn't use FSB anymore, it use QPI which is the same thing (BUS) but with newer technology. Thus, busratio still relevant with Intel Core (i) Processor family. However, the calculation to get actual CPU speed might be different. (Please correct me if I'm wrong.)