AnVAL (ACPI Loader)

[valv]

@00Diabolic ~~, have u tried it with FixFSB No?

 

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?

Hi Jon, It is not cosmetic. And the FixFSB and busratio keys are not implemented for core (i) cpus.

 

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 not smbios injection, if that is what u meant.

btw, u seem to know a little about the subject. It 'd be nice if u preserve yourself from growing insults toward your little person. go buy a ps3 and let the nerds work on hackintoshes.

Rest In Peace.

[bs0d]

@00Diabolic ~~, have u tried it with FixFSB No?

 

Hi Jon, It is not cosmetic. And the FixFSB and busratio keys are not implemented for core (i) cpus.

 

This is not smbios injection, if that is what u meant.

btw, u seem to know a little about the subject. It 'd be nice if u preserve yourself from growing insults toward your little person. go buy a ps3 and let the nerds work on hackintoshes.

Rest In Peace.

 

grow up

[jboehm]

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.)

 

For Intel Core (i) Processor

bclk x Cpu Mulitplier = CPU Freq

bclk x Memory Mulitplier = Memory Freq

bclk x QPI Mulitpler = QPI Freq

 

QPI (QuickPath Interconnect) is not equivalent to FSB. They do some of the same things. bclk (base clock) is the fundamental knob that increases or decreases all of the above. The CPU, Memory, and QPI multipliers are also adjustable on unlocked parts.

[valv]

grow up

yeah exactly, shut the f**k up. u are unwelcome.

have a nice day

[00diabolic]

@00Diabolic ~~, have u tried it with FixFSB No?

 

Yes on your latest beta I am back to my 736fsb withFixFSB=No. With this beta4b which I currently have loaded it does not matter if I set FixFSB or not the results are the same everything is best in this one except system sounds and clock is running slow like the last few betas have been.

 

I have tried every combo I can think of bustratio=125/130 FixFSB=Yes/No and always have the slow clock/system sound problem and sometimes a random KP.

 

Hope that helps.. I am trying to get my head around vanilla p-states ATM.. Yowza is this confusing..

[jboehm]

Hi Jon, It is not cosmetic. And the FixFSB and busratio keys are not implemented for core (i) cpus.

 

Thank valv. You have a great project here!

 

Is there a place were all of the *.plist arguments are documented? I'm not sure what all of available arguments are and the names I've run across are not completely self explanatory to fresh eyes (example oemDSDT: does this mean extract from the real hardware or use a generic DSDT?)

 

At some point (the project might not be stable enough yet) it might save a great deal of time to document all of the args, what they do, what architectures are supported, default behavior, and clearly state if this is cosmetic or if it adjusts hardware behavior.

 

I know the user can get some documentation by using '?' at the boot loader. Is there a more convenient place to get this in the OS, were I can sit and study it?

 

Thanks again for the hard work ... truly impressive!!

[bs0d]

yeah exactly, shut the f**k up. u are unwelcome.

have a nice day

 

lmfao ... you clearly have no understanding.

 

thanks i will have a nice day

 

while you keep struggling with something that just aint going to work.

[valv]

Wake the dormants up! It is already working

[bs0d]

Wake the dormants up! It is already working

 

thats not what 00Diabolic ~~ says

 

but at least your language has improved

 

thanks

[kizwan]

@bs0d, please read from the first post to learn what this thread is all about. Bootloader available here is an advanced version of chameleon 2 bootloader. So, your comment about it is not accurate at all. For the 2nd time, this is not for overclocking the CPU.

[rednous]

Hi valv

 

my beta4b report follows (round 30-40 mins tests accompanied with restarts):

 

FSB=266MHz (BIOS stock FSB), Memory runs @ 800MHz (BIOS stock frequency); Im not keen on OCing my system.

 

with FixFSB=yes, busratio=110 --> sound is OK

sysctl -a | grep freq

hw.busfrequency = 1064000000
hw.cpufrequency = 2930000000
hw.tbfrequency = 1000000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1066666668
hw.cpufrequency: 2930000000
hw.cpufrequency_min: 2930000000
hw.cpufrequency_max: 2930000000
hw.tbfrequency: 1000000000

 

with FixFSB=yes, busratio=80 --> sound is OK

sysctl -a | grep freq

hw.busfrequency = 1064000000
hw.cpufrequency = 2930000000
hw.tbfrequency = 1000000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1066666668
hw.cpufrequency: 2930000000
hw.cpufrequency_min: 2930000000
hw.cpufrequency_max: 2930000000
hw.tbfrequency: 1000000000

 

with FixFSB=yes, busratio=60 --> sound is OK

sysctl -a | grep freq

hw.busfrequency = 1064000000
hw.cpufrequency = 2930000000
hw.tbfrequency = 1000000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1066666668
hw.cpufrequency: 2930000000
hw.cpufrequency_min: 2930000000
hw.cpufrequency_max: 2930000000
hw.tbfrequency: 1000000000

 

with FixFSB=no, busratio=110 --> small sound glitches on file read & write

sysctl -a | grep freq

hw.busfrequency = 400000000
hw.cpufrequency = 2933000000
hw.tbfrequency = 1000000000
hw.busfrequency: 400000000
hw.busfrequency_min: 400000000
hw.busfrequency_max: 400000000
hw.cpufrequency: 2933000000
hw.cpufrequency_min: 2933000000
hw.cpufrequency_max: 2933000000
hw.tbfrequency: 1000000000

 

It seems that with FixFSB=no & busratio=110 the bus frequency is detected almost correct - 400MHz (although mine is set to 266MHz in the BIOS), but i have sound glitches and noise with this combination

 

P. S. No CPU related message(s) in the Chameleon wait screen and in kernel.log booting in verbose mode with the above key combinations.

 

When is harder and harder we're closer to the success

[valv]

@rednous,

Thank u for the time giving to test. Just one thing though, make sure u 've been using beta4b as your results seem to be those from beta4

Greetz,

[rednous]

@rednous,

Thank u for the time giving to test. Just one thing though, make sure u 've been using beta4b as your results seem to be those from beta4

Greetz,

 

hahaaaa , i'll check now

 

EDIT: You're right , how's that possible? i'll update it right now and test!

 

Here's the beta4b RIGHT test

 

with FixFSB=yes, busratio=110 --> sound is OK

sysctl -a | grep freq

hw.busfrequency = 1064000000
hw.cpufrequency = 2933000000
hw.tbfrequency = 1000000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1066666668
hw.cpufrequency: 2933000000
hw.cpufrequency_min: 2933000000
hw.cpufrequency_max: 2933000000
hw.tbfrequency: 1000000000

 

 

with FixFSB=yes, busratio=80 --> sound is OK

sysctl -a | grep freq

hw.busfrequency = 1064000000
hw.cpufrequency = 2133000000
hw.tbfrequency = 1000000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1066666668
hw.cpufrequency: 2133000000
hw.cpufrequency_min: 2133000000
hw.cpufrequency_max: 2133000000
hw.tbfrequency: 1000000000

 

 

 

with FixFSB=no, busratio=110 --> sound is OK

sysctl -a | grep freq

hw.busfrequency = 1064000000
hw.cpufrequency = 2933000000
hw.tbfrequency = 1000000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1066721200
hw.cpufrequency: 2933000000
hw.cpufrequency_min: 2933000000
hw.cpufrequency_max: 2933000000
hw.tbfrequency: 1000000000

 

It seems now in my case the booter recognizes the CPU freq, but not the FSB. I have no more sound glitches with the key FixFSB=no Also the system boots a little bit faster

 

By the way i forgot to tell that i have Sleep, Shutdown, Restart and Wake implemented in my DSDT and they're working all the time no matter the booter version.

[valv]

It seems now in my case the booter recognizes the CPU freq, but not the FSB.

What's wrong with FSB? is it not showing the right value?

[rednous]

aham, mine is 266MHz (stock set in BIOS). Bus Speed: 1.07 GHz is shown in System Profiler. But anyway, personally im OK as far as my system works flawlessly

[valv]

ok, that's actually the right value. don't worry about it. If u meant when u edit the stock value from bios that it does pertain to show stock value, please let me know.

[rednous]

so it seems everything's OK for now

[mitch_de]

"aham, mine is 266MHz (stock set in BIOS). Bus Speed: 1.07 GHz is shown in System Profile"

For my knowledge thats right ! 266 MHz real is 1066 MHz Profiler Systemspeed.

Its same as with RAM MHZ. 1066 MHz RAM isnt clocked in real with 1066 MHz, its 266 MHz in real (DDR2).

333 FSB showed as 1.33 GHz in Systemprofiler what is also OK.

[00diabolic]

thats not what 00Diabolic ~~ says

 

but at least your language has improved

 

thanks

 

I never said Valv was overclocking through the bootloader it just does not calculate my cpu clock correctly with the new FixFSB flag used. The only way to actually OC in OSX is through the FSB unless you have a CPU with a unlockable multiplier (AKA busratio). Very few CPUS have a unlocked multiplier and in your real bios the only option you are given is the ability to push the FSB value higher. Even with a unlocked multiplier this option would not be available (or would not work) in OSX only in your real bios. The FSB overclock in theory based on how OSX works should be able to be pushed up by telling OSX it has a faster FSB then it does. I would imagine this would be much less stable then doing it in your real bios though. My system is a laptop and it has no options to OC at all and I dont really care about OCing. I just want the full speed my system has available to it since my Bios incorrectly passes my FSB as 736 I get crippled speed through out my system in OSX.

 

I'm not the only one with this problem, though I am the only one with an Intel system that has it. Lots of AMD users report the same issue.

[rednous]

"aham, mine is 266MHz (stock set in BIOS). Bus Speed: 1.07 GHz is shown in System Profile"

For my knowledge thats right ! 266 MHz real is 1066 MHz Profiler Systemspeed.

Its same as with RAM MHZ. 1066 MHz RAM isnt clocked in real with 1066 MHz, its 266 MHz in real (DDR2).

333 FSB showed as 1.33 GHz in Systemprofiler what is also OK.

 

well, valv & mitch_de, so beta4b really works

[gimox]

hi,

use a netbook with atom n280 and busratio and fixfsb not work. my rated fsb is 100 and is not correct.

 

I use smbios.plist to correct but i think is not good.

 

this is with fixfsb yes and busratio 10

hw.busfrequency = 100000000
hw.cpufrequency = 1000000002
hw.tbfrequency = 1000000000
hw.busfrequency: 100000000
hw.busfrequency_min: 100000000
hw.busfrequency_max: 666666668
hw.cpufrequency: 1166666669
hw.cpufrequency_min: 1000000002
hw.cpufrequency_max: 1666666670
hw.tbfrequency: 1000000000

 

 

 

this are my cpu info

 

hw.ncpu = 2
hw.cpufrequency = 1000000002
hw.availcpu = 2
hw.ncpu: 2
hw.activecpu: 2
hw.physicalcpu: 1
hw.physicalcpu_max: 1
hw.logicalcpu: 2
hw.logicalcpu_max: 2
hw.cputype: 7
hw.cpusubtype: 4
hw.cpu64bit_capable: 0
hw.cpufamily: 1114597871
hw.cpufrequency: 1166666669
hw.cpufrequency_min: 1000000002
hw.cpufrequency_max: 1666666670
hw.cputhreadtype: 1
machdep.cpu.max_basic: 10
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
machdep.cpu.family: 6
machdep.cpu.model: 23
machdep.cpu.extmodel: 1
machdep.cpu.extfamily: 0
machdep.cpu.stepping: 2
machdep.cpu.feature_bits: 3219782655 4244373
machdep.cpu.extfeature_bits: 1048576 1
machdep.cpu.signature: 67266
machdep.cpu.brand: 0
machdep.cpu.features:  FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 DSCPL EST TM2 SSSE3 TPR PDCM
machdep.cpu.extfeatures:  XD LAHF
machdep.cpu.logical_per_package: 2
machdep.cpu.cores_per_package: 1
machdep.cpu.microcode_version: 525
machdep.cpu.mwait.linesize_min: 0
machdep.cpu.mwait.linesize_max: 0
machdep.cpu.mwait.extensions: 0
machdep.cpu.mwait.sub_Cstates: 131616
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: 3
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: 1
machdep.cpu.arch_perf.fixed_width: 40
machdep.cpu.cache.linesize: 64
machdep.cpu.cache.L2_associativity: 8
machdep.cpu.cache.size: 512
machdep.cpu.tlb.inst.small: 32
machdep.cpu.tlb.data.small: 16
machdep.cpu.tlb.data.small_level1: 2028621756
machdep.cpu.tlb.data.large_level1: 64
machdep.cpu.address_bits.physical: 32
machdep.cpu.address_bits.virtual: 32
machdep.cpu.core_count: 1
machdep.cpu.thread_count: 2

[valv]

which version are u using?

good joke if it is one, but it seems like u merged your sysctl dump from E7500 and edited the brand_string with the one from N280

machdep.cpu.brand_string: Intel® Atom CPU N280 @ 1.66GHz

machdep.cpu.family: 6

machdep.cpu.model: 23

I thought N280 should have cpu model 28. Isn't ? If am wrong, correct me!

It seems you 're using this model

image source is here

confirmed here

[JBraddock]

@Valv, For some, it seems that they don't really appreciate what you are trying to do here. Either they don't exactly know what you are doing or there are some other reasons.

 

I must say this tough: I am really impressed with the effort that you put into this bootloader thing. I can't help but think that if I were in your shoes I am not sure if I would deal with those exceptional issues that people are having in ways that you do.

 

Finally, please accept this as a suggestion, it seems that this topic seems a little advanced for some. May be you should give more detail about your bootloader and explain in which ways this bootloader is different from other branches of Chameleon. I am saying this because it even took me for a while to understand and see the potential of what this bootloader could do.

[00diabolic]

@JBraddock...

 

I defiantly feel what valv is doing here is worthy of a lot of praise. I would basically be completely stuck with my 736fsb if it was not for his effort.

 

I have actually tried to draw more peoples attention to this bootloader simply because valv is trying to help everyone. I also wanted his work on the FSB fix to be used by more then just me. At times I feel hes doing this just for me, which I hate to think about since I cant afford to donate to him. I have been out of work for almost one year. I am on hijacked internet as we speak.

 

Anyway OSX has been a lot better since I found valvs bootloader and I will be grateful to him when this work is complete.

 

I do agree with you about better explanation of what hes doing though. I was last in the OSX scene around 10.5.0-10.5.4 and worked with the likes of Superhai and JaZ when they was roaming these threads helping people. I was around to see the first inception of chameleon and knew that it was basically PCEFI wrapped up in an edit of apples own bootloader. Back then installing EFI was all done through scripts or commands and then came chameleon which wrapped it all up. Amazing the changes since 10.5.0 came out. There was no DSDT back then and it was all hacked smbios/system kext files that were customized to your system. I had superhai make me my own Smbios to deal with my FSB issue back then when no one wanted to help and now I have AnVAL and I'm glad I do.

 

Thanks again Valv

[JBraddock]

@00Diabolic ~~,

 

Just to make it clearer.

 

When I said some people don't know and/or appreciate what Valv does, I didn't mean anyone in particular. I didn't want to offend anyone.

Dealing with one's specific problem is just really a patient requiring process and people should just appreciate the effort itself even if the outcome doesn't satisfy them.

 

I'll make donation to Valv not just because he is doing something which may ease my life but also to help compensate the time that he is spending on things that may help people.

"Doing something for someone" That's what got my heart here, in this great community.