AnVAL (ACPI Loader)

[valv]

@XLR,

it could be helpful if u could only test the latest one: beta3b. thanks for asking.

 

@Andrew180,

can u post your smbios.plist file?

[Andrew180]

I'm not using smbios.plist... And I also found out, that sleep is gone. But I'm not sure if it's been working with ur branch release... gonna test that out. Now straight to the bed. Happy coding!

[XLR]

The beta3b works great, detects all speeds properly except my current memory model/manufacturer, but i haven't seen a bootloader yet that knows to detect Mushkin or Rendition memory. However, Kingston gets detected perfectly, even with serial numbers.

[valv]

The beta3b works great, detects all speeds properly except my current memory model/manufacturer, but i haven't seen a bootloader yet that knows to detect Mushkin or Rendition memory. However, Kingston gets detected perfectly, even with serial numbers.

Thank u for the great feedback

Have u tried booting with UseMemDetect (with Yes) from your boot.plist? btw, u can still inject those failing to be recognized with smbios.plist injection.

Greetz

[XLR]

Tried it right now, with UseMemDetect it gives a blank screen with "There wan an error while gathering this information." in the Profiler. (I'm using Mushkin memory stick at the moment) But i guess it's only a cosmetic issue that has nothing to do with performance or system stability/compatibility. That's why i avoid using smbios.plist since the release of PC EFI 10.4 and Chameleon RC2, when i can rely on autodetect.

[valv]

I'm not using smbios.plist... And I also found out, that sleep is gone. But I'm not sure if it's been working with ur branch release... gonna test that out. Now straight to the bed. Happy coding!

ok, post your boot.plist then. am pretty sure u missed some keys.

[00diabolic]

Testing testing testing..

 

Report on 3b as I tried it first.. Note that smbios.plist is clear of everything but a mac model, serial etc. No ram, cpu or fsb info

 

First thing I noticed is when it first boots it now says FADT loaded from DSDT.aml or something like that. I have no FADT table on my system and this was always skipped before like the other ones. Is this something new your doing or is that a glitch? I typed in the wait command to see this. It seemed odd to me so I figured I would let you know valv.

 

When OSX loads first thing I noticed is its slower then the last beta2b I used. Sounds are still delayed like in that release. Also voodoo monitor says I have a 2700mhz cpu but interestingly enough about this mac says 2.49ghz.

 

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

Here is my sysctl output

 

sysctl -a | grep freq

hw.busfrequency = 800000000

hw.cpufrequency = 2500000000

hw.tbfrequency = 1000000000

hw.busfrequency: 800000000

hw.busfrequency_min: 800000000

hw.busfrequency_max: 800000000

hw.cpufrequency: 2500000000

hw.cpufrequency_min: 2500000000

hw.cpufrequency_max: 2500000000

hw.tbfrequency: 1000000000

 

Shouldn't hw.tbfrequency be 2000000000? I never had 1000000000 there before.

 

Also my benchmark scores took a HUGE hit in this release. My system lost so much speed it was actually hard to use. The benchmarks confirmed it also. With 3b my scores dropped to 2700 from 3600. That is a huge drop and the worst I have see yet from any of your previous work.

 

________________I then decided to step back and try beta3.______________________

 

This one is a lot faster right off the bat.

 

Here are the things that are simular.

 

Still see the FADT table load at the beginning of boot as with 3b. Sounds are still delayed and play oddly. Clock is slow with this release also as I believe it is in 3b but I did not look. The sound and clock speed are related Im sure of that. Voodoo monitor still says I have 2700mhz cpu and about this mac says I have a 2.5ghz cpu.

 

The one huge difference is the benchmark scores. They are back to Geekbench Score 3659. So this release is better then 3b for me. Except for the clock/system sounds issue.

 

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

sysctl -a | grep freq

hw.busfrequency = 800000000

hw.cpufrequency = 2500000000

hw.tbfrequency = 1000000000

hw.busfrequency: 800000000

hw.busfrequency_min: 800000000

hw.busfrequency_max: 800000000

hw.cpufrequency: 2500000000

hw.cpufrequency_min: 2500000000

hw.cpufrequency_max: 2500000000

hw.tbfrequency: 1000000000

 

Valv start asking everyone if there clock is running slow. You had it running to fast before with the alphas. Whatever is calculating one of the system speeds was doing it to fast and now to slow. Its funny that everything CPU, FSB (not ram still says 800mhz) is correct but the system seems slower.. Your so close man..

 

Keep up the good work.

[rednous]

valv, thanx

beta3b is fine here

[Andrew180]

Alrigty, that sleep issue was my bad . I forgot to enable automatic startup after power failure... Still unknown CPU also with the beta3b. UseMemDetect gives me gathering information error and without UseMemDetect i have size, type and speed detected... no manufacturer or part number...

 

OK, attaching boot.plist, but nothing interesting there...

boot.rtf

[mitch_de]

I ask because i want to test also the new boot but would be better to understand that "problems" about speed loss (geekbench).

My system has E7300 2.66 @ 3.00 GHZ, OC by : FSB 266 > 333 , Multi 10 > 9 = 9*333 = 3.0 GHz, PStates 6*..9* working with vanilla speedstep

Question about that speed test some run here and whats going wrong in under the hood :

What i see , but not really understand now is that the CPU Informations in systemprofiler (cpu clk, bus clk) are not only cosmetic.

Why have some users prolems with their speed ?

Is that an OC Problem (normally by higher FSB clk, multi most not used for that) or can also happen on non OC Intel systems ?

Or only an problem with the speedstep + wrong PSTATES , or only happend on newer i5 / i7 CPUs ?

I thoughth that all speed is set in the BIOS (Multi + FSB = settings) and OS X doesnt change that. It only may switch to the PSTATES (if PSS are available) by access of the MSR Registers.

 

My only problem ever is /was that i must change the PSTATE Min in settings of voodoopower or voodoomini (as i tested them, not using them anymore)

If i dont do that limit to 9* FSB, i get Kernel Panic very fast/soon : voodoopwoer switch to 10* 333 = 3.33 GHz if i not limit the PSTATE to 9* (Pstate 1 = max).

[DariosF]

Always same error. 3.33 ghz instead 4.3 ghz and my clock time is too fast.

 

Also with legacy kernel there are the same problems.

[00diabolic]

Always same error. 3.33 ghz instead 4.3 ghz and my clock time is too fast.

 

Are u sure its not running to slow? Mine is losing time. Go up to change the clock settings and you see the clock jump forward a few mins. That is what mine is doing. In Valvs alphas the clock was running to fast & now hes cranked it back with these betas & its to slow.

[JBraddock]

@Valv,

 

I am trying to understand this whole "SSDT, ACPI Tables etc" and I have a question which may be related to these topics. I followed your HDX guide and enabled native speed step. Now the HDX can go to sleep but doesn't wake up with the power button. If I hold the power button and turn the HDX off and restart again, after the Chameleon menu, it says something about wake kernel and it directly shows me my desktop. I think I have problem with bluetooth and web cam. Anyway, this can be solved i guess. But my main problem is that after applying some hacks that you provided my speed step stopped working. It stuck at (P8400) 2.26mhz, which is the highest value.

 

I removed Nullpowermanagement and Voodoopowermini and applied LPC and SMBus but it is still the same. I have found this in my kernel log.

Jun 25 13:44:39 localhost kernel[0]: WARNING - ACPI_SMC_CtrlLoop::initCPUCtrlLoop - no sub-config match for MacBookPro4,1 with 4 p-states, using default stepper instead

 

Based on this topic, I tried to add my P-States to the DSDT, but I got syntax error. Below is the code I tried to add:

Scope (_PR.CPU0)
   {
       Method (_PSS, 0, NotSerialized)
       {
           Return (Package (0x06)
           {
               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x481F, 
                   Zero
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x081E, 
                   One
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x471C, 
                   0x02
               }

      Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x071B, 
                   0x03
               }

    Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x4619, 
                   0x04
               }

     Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0617, 
                   0x05
               }
           })
       }

       Method (_PSD, 0, NotSerialized)
       {
           Return (Package (0x05)
           {
               0x05, 
               Zero, 
               Zero, 
               0xFC, 
               0x04
           })
       }

       Method (_CST, 0, NotSerialized)
       {
           Return (Package (0x02)
           {
               One, 
               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x01,               // Bit Width
                           0x02,               // Bit Offset
                           0x0000000000000000, // Address
                           0x01,               // Access Size
                           )
                   }, 

                   One, 
                   0x9D, 
                   0x03E8
               }
           })
       }
   }

   Scope (_PR.CPU1)
   {
       Method (_PSS, 0, NotSerialized)
       {
           Return (^^CPU0._PSS ())
       }

       Method (_PSD, 0, NotSerialized)
       {
           Return (^^CPU0._PSD ())
       }

       Method (_CST, 0, NotSerialized)
       {
           Return (Package (0x04)
           {
               0x03, 
               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x01,               // Bit Width
                           0x02,               // Bit Offset
                           0x0000000000000000, // Address
                           ,)
                   }, 

                   One, 
                   Zero, 
                   0x03E8
               }, 

               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x08,               // Bit Width
                           0x00,               // Bit Offset
                           0x0000000000000414, // Address
                           ,)
                   }, 

                   0x02, 
                   One, 
                   0x01F4
               }, 

               Package (0x04)
               {
                   ResourceTemplate ()
                   {
                       Register (FFixedHW, 
                           0x08,               // Bit Width
                           0x00,               // Bit Offset
                           0x0000000000000415, // Address
                           ,)
                   }, 

                   0x03, 
                   0x55, 
                   0xFA
               }
           })
       }
   }

 

And this is error I am getting:

/Users/snowkitty/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl   788: 0x10, 
                   0x081E, 
                   0x01
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x471C, 
                   0x02
               }

         Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x071B, 
                   0x03
               }

      Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x4619, 
                   0x04
               }

      Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0617, 
                   0x05
               }
           }), 0x1C, 0x44, 
Error    4096 - syntax error, unexpected PARSEOP_PACKAGE, expecting ',' or '}' ^ 

 

 

Additionally, when I checked the Extensions loaded I can see that AppleIntelPenryProfile is loaded. But sometimes, other cpu profiles are also loaded alonside Penry (Merom etc.).

 

My HDX doesn't get hot even at this speed thanks to the hacks you provided. It's even cooler than before but I have this constantly running fan, which is annoying

 

I am not using smbios.plist and this is my system info:

Hardware Overview:

 Model Name:	MacBook Pro
 Model Identifier:	MacBookPro4,1
 Processor Name:	Intel Core 2 Duo
 Processor Speed:	2.26 GHz
 Number Of Processors:	1
 Total Number Of Cores:	2
 L2 Cache:	3 MB
 Memory:	4 GB
 Bus Speed:	1.07 GHz
 Boot ROM Version:	MBP41.0073.B00
 SMC Version (system):	1.30f3
 Serial Number (system):	SOMESRLNMBR
 Hardware UUID:	DF557FA2-C304-556B-A442-960AB835CB5D

 

I am using Chameleon RC4 right now. Apparently, SL can't read P and C States from bios.

[JBraddock]

I installed the beta3. Things I noticed.

 

- Rams are reported correctly, which is DDR2 800.

- CPU Detection is 2.26 GHz Intel Core 2 Duo (same with the RC4)

- Sleep is still the same. But, beta3 seems to be slower in terms of sleeping and waking.

- With RC4, When I press the power button my keyboard got frozen/ caplocks and numlocks led turned on whereas with Beta3 the same thing happen without that led thing.

 

I've added DropSSDT=No. Speed-step is still the same.

 

Anything else that I should report?

[valv]

First things first,

@mitch_de,

thank u for the great explanation. btw, am having hard times to get those oc'ed cpus correctly detected without sound glitches. probably tsc (not even relying on it for the fsb freqs calculation).

 

@JBraddock,

dear, don't get mixed. I did not forget u. also the most important part (about speed-step) is unfinished yet. Yes I got it working. and Yes I'll be providing u with what I know. But please don't hate me for letting you wait that long.

I'll be back as soon as the actual release becomes stable (or maybe even sooner )

 

Back to the topic, I added a new key to let most of u whom were happy with 06/04 release's detection to stick with that.

More clearly, now u have the choice to go with the old or the new algo, by just specifying one key on your boot.plist files.

The key is named FixFSB. If u specify it and give it Yes as a value, then u go with my last workaround. else u remain with the old one. Btw, this key is only effective for intel cpus with family 6 (except nehalem and its cousins, whom have there own section). Doesn't mean that amd cpus not being supported, they even have their part of the cake. In a hope that everyone get satisfied, I wish u gonna enjoy this one:

 

everyone is invited to test beta3c.zip

I count on you to feedbacks

Greetz

[JBraddock]

@Valv, that's never been a problem, trust me. I just thought it was supposed to work as I did everything you told us to do. Now I see that there is still work to do.

 

I've installed beta3b and now will install the latest one.

Apart from the things I mentioned above what should I be looking at?

 

Btw, my scrolling problem seems to be disappeared with beta3b.

[valv]

Apart from the things I mentioned above what should I be looking at?

look if fsb value is correct

[JBraddock]

look if fsb value is correct

 

I installed beta3c typed sysctl -a | grep freq and here is the result.

 

hw.busfrequency = 1064000000

hw.cpufrequency = 2261000000

hw.tbfrequency = 1000000000

hw.busfrequency: 1064000000

hw.busfrequency_min: 1064000000

hw.busfrequency_max: 1064000000

hw.cpufrequency: 2261000000

hw.cpufrequency_min: 2261000000

hw.cpufrequency_max: 2261000000

hw.tbfrequency: 1000000000

 

It seems fine I guess.

[valv]

@JBraddock,

was those without FixFSB? did u tried that key?

[JBraddock]

No, I didn't use that key. Since the fbs value was correct I didn't try that key.

Do you want me to try it?

[valv]

No, I didn't use that key. Since the fbs value was correct I didn't try that key.

Do you want me to try it?

yes, please

[JBraddock]

yes, please

 

I did and the output is still the same.

Fbs values are correct, right?

[valv]

@JBraddock,

it's ok.

 

anybody else wishing to give feedback?

[00diabolic]

Valv... beta 3c testing

 

CPU Clock: 2700 MHz

FSB Clock: 800 MHz

Bus Clock: 200 MHz

 

CPU is still off. Its 200mhz overclocked. Ram is still off with it detecting it at 800mhz instead of 667mhz... Also sounds are still delayed but it seems a lil better then before. I can only notice it with the glass sound. However some of the sounds are worse then they were before.. More distorted.

 

I noticed you fixed up that FADT table being loaded from DSDT goof on boot. I dont see it anymore.. Its back to saying no FADT table not found like it should.

 

Keep up the good work!

[valv]

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