Jump to content

AnVAL (ACPI Loader)

valv

By valv,
in Chameleon

 Share
1,538 posts in this topic

Recommended Posts

valv
valv
Posted
  • Author
Posted

@kizwan,

The last beta seems to be facing the problem where the new keys aren't read from boot.plist, and thus the new algo is not even executed. Am working on this.

 

btw, I love your long posts :wacko: Greetz

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted
Processor in "About this Mac" says Unknown.
would u mind typing this on a terminal:

sysctl -a | grep cpu.model, and giving me the result. also, using IORegistryExplorer look at CPU0@0 and tell me what value is shoing at cpu-type item.

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted
valv, waitin' for the next beta to report :):)

Hopefully it is now fixed, thanks to Kabyl's support.

I also changed the type of busratio value to support floating-points. That means u specify the multiplier as is (no more x10),

e.g.: I need multiplier 7 I specify 7 and for 11.5 I specify 11.5

That's all for now ;)

 

test phase, continued boot3e.zip

use this one instead beta4.zip

don't forget to test out diffrent combinations of those two new keys.

 

edit1:

also, by default:

  • if u don't write the FixFSB key (Yes) on boot.plist, u wont be useing the new detection mode.
  • busratio value if unspecified will retain the default one (stock no oc')

edit2:

beta4 added. Please test this one instead

attension: busratio key is effective only when using FixFSB.

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted

@DariosF, again, use FixFSB and busratio from boot.plist out, and not as a boot argument.

If u don't specify FixFSB, noway to use busratio either (maybe for now).

Greetz,

 

also, would u mind, using Wait key to see if some verbose (starting with "CPU " is telling something) ?

Link to comment
Share on other sites
rednous
rednous
Posted
Posted

valv, beta3e report:

 

key FixFSB=Yes & key busratio=11

 

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

 

 

key FixFSB=Yes, key busratio is missing

 

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

 

 

with key FixFSB=No, key busratio is missing --> sound glitches and distortions!

sysctl -a | grep cpufreq
hw.cpufrequency = 2930000000
hw.cpufrequency: 2930000000
hw.cpufrequency_min: 2930000000
hw.cpufrequency_max: 2930000000

 

hw.busfrequency = 400000000
hw.busfrequency: 400000000
hw.busfrequency_min: 400000000
hw.busfrequency_max: 400000000

 

 

with key FixFSB=No and key busratio=11 --> sound glitches and distortions!

sysctl -a | grep cpufreq
hw.cpufrequency = 2933000000
hw.cpufrequency: 2933000000
hw.cpufrequency_min: 2933000000
hw.cpufrequency_max: 2933000000

 

sysctl -a | grep busfreq
hw.busfrequency = 400000000
hw.busfrequency: 400000000
hw.busfrequency_min: 400000000
hw.busfrequency_max: 400000000

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted

@rednous, thank u very much for the feedback. one more thing, would u mind altering your busratio below 11, (something like 10, or 10.5) just to see if the key is actually taken in count or not? thanks again.

 

Now, with your keys, no black screen, but cpu is always at 3.33 ghz...Now hdaenabler works.

give it one more try by altering the busratio to 14 (333Mhz x 14 = 4.33Ghz)

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted
same problem also with 14. My real busratio is 10...so...

And u 've been oc 'ing...so...review your specs

Link to comment
Share on other sites
rednous
rednous
Posted
Posted
@rednous, thank u very much for the feedback. one more thing, would u mind altering your busratio below 11, (something like 10, or 10.5) just to see if the key is actually taken in count or not? thanks again.

 

valv, here's the result with FixFSB=Yes & busratio=10:

 

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

 

going outside for a while and i'll continue to test and report later when i get back home :)

cheers

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted

@rednous,

thanks, busratio key doesn't seem to be working :) even though FixFSB is now ok.

I need more revision of the code. see u later.

Greetz,

 

edit: beta4 added on the above post (straight after beta3e)

Link to comment
Share on other sites
rednous
rednous
Posted
Posted

valv, beta4 report:

 

with FixFSB=yes, busratio=10

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

 

 

with FixFSB=yes, busratio=8

sysctl -a | grep cpufreq
hw.cpufrequency = 2930000000
hw.cpufrequency: 2930000000
hw.cpufrequency_min: 2930000000
hw.cpufrequency_max: 2930000000

[code]sysctl -a | grep busfreq
hw.busfrequency = 1064000000
hw.busfrequency: 1064000000
hw.busfrequency_min: 1064000000
hw.busfrequency_max: 1064000000

 

im keen on testing, so please if you need more in-depth details provide me with advanced instructions :)

 

im sure your code is OK, but there's some hidden little detail in the hardware interaction with the software, but you'll catch it, eventually, i know :(

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted

Just tested Beta4.. Here are the results.

 

First tried FixFSB=Yes with no busratio..

 

I got

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

*Sound is still distorted and clock is slow.

 

I then tried FixFSB=Yes with Busratio=12.5

 

I got

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

*Sound still distored and clock is slow.

 

I will be back to try with no FixFSB..

 

:-)

 

Update: I tried beta 4 with no FixFSB and busratio=12.5 i do get different results..

 

CPU Clock: 1350 MHz

FSB Clock: 400 MHz

Bus Clock: 100 MHz

 

Also icons are moving faster and clock is fast also and system sounds. So the new code is being accessed but with FixFSB everything is running slow and without it its on speed.. lol

 

Hope that helps.. :-)

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted
im sure your code is OK, but there's some hidden little detail in the hardware interaction with the software, but you'll catch it, eventually, i know ;)

please look if u could catch any verbose output related to cpu with Wait key. thanks

Link to comment
Share on other sites
mitch_de
mitch_de
Posted
Posted

Beta4 results (no FSB / no CPU Mhz set in smbios.plist).

Same as last Betas with C2D 333 MHz FSB (OC from 266) and Busratio = 9 (indest of 10).

I set FixUSB = Yes and busratio=9, should result in 3000 MHZ / 333 MHZ FSB.

But same FSB/CPU Speed as wiwthout that settings or latest Beta3c:

2.66 GHZ CPU, FSB 266 , as i would have busratio = 10 and FSB 266 (original).

 

I dont now how OS X works with that CPU/FSB settings.

Can it be that you do FIXFSB / RATIO ALL OK at boottime, but after that, some OS X code resets that FSB/BUSRATIO boot settings back to wrong (default CPU) values ?

(like IntelCPU drivers or other code from OS X)

 

At least for those people, like me which didnt have any sound / time speed problems, worikng old method of smbios.plist settings are OK. I woudl not sped to much time to get that problem fixed.

 

PS: The speed differences of Xench / Geekbench if something wrong DONT means real speed differences - the difference of the benches results by WRONG TIME MEASUREMENT. All benches measures some work/time and if time runs to fast/slow than the bench results are also wrong. But in real they are same - measn no real speed differences.

Link to comment
Share on other sites
valv
valv
Posted
  • Author
Posted

@mitch_de,

 

It could be possible, but as u may know regarding FSB, OSX does nothing more than sticking with the boot-loader's value as of this post. Also how could legacy kernels manage to make OSX stick with the booting values (as of busratio= & fsb=) knowing that even sysctl relies on MSRs to get the frequencies dumped: noway for the kernel to play the role of a man-in-the-middle (so to say).

Actually am stack at the busratio's key not knowing how to make it stick into the code. If u or anybody over here would like to give me a hand on this, just let me know.

Greetz,

Link to comment
Share on other sites
mitch_de
mitch_de
Posted
Posted

WARING BETA4 :

I set FixFSB = No and my system cant boot anymore ! Shows chameleon , than no screen anymore. Seems somethinh haangs in boot, isnt an OS X problem.

Went back to 3C.

 

EDIT :

I now checked my BIOS OC settings (was looong time not in the bios ;) )

I seen that in the past sometime the bios was reset to default FSB. Some BIOS (Gigabyte for example) do that if an boot fails automatic to default!

Now i set it back to 333 FSB / 9* Multi.

LOL: I run non OC (2.66 vs 3.00 GHz) for months without knowing that - without VAL i would stay unOCed until dead :(;)

 

boot 3C now works great !!!!

It shows FSB=333 and also CPU MHZ are 3000 - WITHOUT any smbios injection !

Sorry VAL and big THANKS !

 

HINT for all beta testers: Before submitting your sysctl -a | grep freq results, please check the REAL BIOS settings of FSB / MULTI in bios.

So VAL can be more sure to get valide user comments. Sorry that my results were not valide.

Link to comment
Share on other sites
jboehm
jboehm
Posted
Posted
would u mind typing this on a terminal:

sysctl -a | grep cpu.model, and giving me the result. also, using IORegistryExplorer look at CPU0@0 and tell me what value is shoing at cpu-type item.

 

Attached was taken using beta3c

 

Thanks,

Jon

post-358495-1277670582_thumb.png

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...