Jump to content

Chameleon RC5 mode with mem detection enabled and automatic P-States & C-States generation for native power managment


kozlek
 Share

1,214 posts in this topic

Recommended Posts

Taruga, i see... Maybe you could find something in my DSDT. Maybe those sound stutters are somehow related to IRQs in the HPET, or similar in the DSDT (just an assumption)...

 

 

Yeah, maybe you're right. I need to check it all very carefully

Link to comment
Share on other sites

Yep, at least it could be helpful, although DSDT checking and comparison is boring for me :D

I think your sound problem is "visible" and small enough at the same time to stay hidden.

Link to comment
Share on other sites

Yep, at least it could be helpful, although DSDT checking and comparison is boring for me :D

I think your sound problem is "visible" and small enough at the same time to stay hidden.

 

 

Well, not small enough as you say. When I boot my pc, It has a lower CPU frequency, so if I try to watch a youtube video I get sound problems and video problems also (like a lot o video pauses). The weird thing is that if a run Garage Band all gets fine and CPU starts to work much faster.

 

I have 4 pstates, and it seems that when I boot the pc, the cpu is locked at the lower pstate. But if I run Garage Ban, it switches to higher cpu frequencies and all goes well from that point on.

Link to comment
Share on other sites

Well, not small enough as you say. When I boot my pc, It has a lower CPU frequency, so if I try to watch a youtube video I get sound problems and video problems also (like a lot o video pauses). The weird thing is that if a run Garage Band all gets fine and CPU starts to work much faster.

 

I have 4 pstates, and it seems that when I boot the pc, the cpu is locked at the lower pstate. But if I run Garage Ban, it switches to higher cpu frequencies and all goes well from that point on.

 

With small I meant something small in the DSDT, for example. What you describe is really strange behavior.

By the way using these latest Chameleon RC5 builds i removed all the P and C state statements in my DSDT and left only the _PR scope (with 2 or 4 CPUs declared - depends if Core 2 Duo or Quad), and GerenratePStates=Yes, GenerateCStates=Yes in boot.plist. But maybe you've seen this in my DSDT already. Did you find something helpful in my DSDT?

 

EDIT: I read now Q6600 doesn't have C states. My CPU (E7500) also is at it's lowest frequency when i boot OS X, and stays at it until i start some CPU intensive application. My intuition tells me this nasty sound bug is somehow related to the DSDT, i hope your CPU isn't involved somehow in the stuttering.

Link to comment
Share on other sites

With small I meant something small in the DSDT, for example. What you describe is really strange behavior.

By the way using these latest Chameleon RC5 builds i removed all the P and C state statements in my DSDT and left only the _PR scope (with 2 or 4 CPUs declared - depends if Core 2 Duo or Quad), and GerenratePStates=Yes, GenerateCStates=Yes in boot.plist. But maybe you've seen this in my DSDT already. Did you find something helpful in my DSDT?

 

EDIT: I read now Q6600 doesn't have C states. My CPU (E7500) also is at it's lowest frequency when i boot OS X, and stays at it until i start some CPU intensive application. My intuition tells me this nasty sound bug is somehow related to the DSDT, i hope your CPU isn't involved somehow in the stuttering.

 

So, you must have the same problem with sound as I do when you boot your pc and try to watch a youtube video... or not ?

 

Edit: You were right, C states are the problem here. If I use GenerateCStates=No I get sleep back and audio doesn't stutter.

Link to comment
Share on other sites

So, you must have the same problem with sound as I do when you boot your pc and try to watch a youtube video... or not ?

 

Nope, i never had such a problem. When im not at home, my machine is sleeping all the time and iTunes is started, when get back home i wake it from sleep and with F8 i start iTunes to play the online radio(s) i use to listen to.

 

EDIT: aha... poor C States. There have to be a solution for them and the nasty sound bug... You're not the only one with Q6600 and im sure someone found the solution already. :D Then why don't you go for the scheme that's working for you with the GenerateCStates=No, functional Sleep and sound?

Link to comment
Share on other sites

.....

 

Qpi interconnect speed is correctly detected 6,48 GT/s overclocked to 21x184.

 

.....

 

All of that other stuff was fixed or is being worked on by mozodojo, rekursor and the chameleon team. That specific boot file was just for testing detection of SMbusspeed. Thanks for the report. Any i5 or i3 testers?

Link to comment
Share on other sites

@anibalin

 

Good to see that it works on LGA1136 too.

 

I think the developers would find it useful if you post your CPU info if it's not being detected correctly. Run this in a Terminal window:

 

sudo sysctl -a | grep machdep.cpu

 

and post these lines e.g.:

 

machdep.cpu.brand_string: Intel® Core i7 CPU 920 @ 2.67GHz

machdep.cpu.family: 6

machdep.cpu.model: 26

machdep.cpu.extmodel: 1

machdep.cpu.extfamily: 0

 

or post a CPU-Z screenshot from Windows.

Link to comment
Share on other sites

And what about the extended model number ?

is it the same ?

If not, we can distinguish them :)

 

machdep.cpu.brand_string: Intel(R) Core(TM) i5 CPU 760  @ 2.80GHz
machdep.cpu.family: 6
machdep.cpu.model: 30
machdep.cpu.extmodel: 1
machdep.cpu.extfamily: 0

 

machdep.cpu.brand_string: Intel® Core™ i7 CPU 920 @ 2.67GHz
machdep.cpu.family: 6
machdep.cpu.model: 26
machdep.cpu.extmodel: 1
machdep.cpu.extfamily: 0

 

Seems like extended model number will not help... Maybe machdep.cpu.signature could be used ?

Link to comment
Share on other sites

Hello dgobe

 

 

here is mine

 

 

machdep.cpu.brand_string: Intel® Core i7 CPU 860 @ 2.80GHz

machdep.cpu.family: 6

machdep.cpu.model: 30

machdep.cpu.extmodel: 1

machdep.cpu.extfamily: 0

 

 

Thanks

Link to comment
Share on other sites

not c2 c3 c4!

Has the boot here the "AI" to know what cpu type needs for C-States? I am a bit confused now about that dsikussion with Q6600 cpu.

I also have an CPU which has C1 working but no other C states.

Can boot handle that (i use dsdt cstate 1 config, which works).

Link to comment
Share on other sites

My Asus laptop Core i7 720QM processor is wrongly being reported as Core i5 in system profiler.

 

And I am unfortunately getting the reboot bug when enabling CStates and PStates.

 

Thanks.

 

Here's my processor details:

 

grepcpu.png

cpuza.jpg

 

 

Scope (_PR)

{

Processor (CPU0, 0x01, 0x00000410, 0x06) {}

Processor (CPU1, 0x02, 0x00000410, 0x06) {}

Processor (CPU2, 0x03, 0x00000410, 0x06) {}

Processor (CPU3, 0x04, 0x00000410, 0x06) {}

Processor (CPU4, 0x05, 0x00000410, 0x06) {}

Processor (CPU5, 0x06, 0x00000410, 0x06) {}

Processor (CPU6, 0x07, 0x00000410, 0x06) {}

Processor (CPU7, 0x08, 0x00000410, 0x06) {}

}

Link to comment
Share on other sites

Has the boot here the "AI" to know what cpu type needs for C-States? I am a bit confused now about that dsikussion with Q6600 cpu.

I also have an CPU which has C1 working but no other C states.

Can boot handle that (i use dsdt cstate 1 config, which works).

 

 

Can you share your dsdt so I can check up some things ?

Link to comment
Share on other sites

Can you share your dsdt so I can check up some things ?

 

Yep : (i use valv boot (doesnt has Pstate/C-state generator)) therefore cpu part within the dsdt. Working.

C2D, 45 nm, E7300 (also only C1E for my knowledge, CST limited in dsdt to 1)

    Scope (_PR)
  [size=1] {
       Processor (CPU0, 0x00, 0x00000410, 0x06) {}
       Processor (CPU1, 0x01, 0x00000410, 0x06) {}
       Processor (CPU2, 0x02, 0x00000410, 0x06) {}
       Processor (CPU3, 0x03, 0x00000410, 0x06) {}
   }

   Scope (\)
   {
       Name (CFGD, 0x02048302)
       Name (PDC0, 0x80000000)
       Name (PDC1, 0x80000000)
       Name (PDC2, 0x80000000)
       Name (PDC3, 0x80000000)
   }

   Scope (_PR.CPU0)
   {
       Name (_PSS, Package (0x07)
       {
           Package (0x06)
           {
               0x0BB5, 
               0x00013A97, 
               0x0A, 
               0x0A, 
               0x0922, 
               0x00
           }, 

..........
           Package (0x06)
           {
               0x07CE, 
               0xB341, 
               0x0A, 
               0x0A, 
               0x0614, 
               0x06
           }
       })
       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
                           ,)
                   }, 

                   One, 
                   One, 
                   0x03E8
               }
           })
       }
   }

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

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

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

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

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

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

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

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

       Method (_CST, 0, NotSerialized)
       {
           Return (^^CPU0._CST ())
       }
   }[/size]

Link to comment
Share on other sites

I just wanted to say thanks.

 

with this new boot file i'm able to get speedstep working on my hp dv6t i7 laptop.

 

 

 

EDIT:

 

ok....i spoke too soon.

 

 

something is wrong....it seems that even since i started using this on my laptop, i get random reboots when the machine is idling.

 

Is there anything anyone can do to help me diagnose what might be causing this? This would be perfect for me if it didn't reboot.

Link to comment
Share on other sites

 Share

×
×
  • Create New...