InsanelyMac Forum > Project being halted for some time

mercurysquad

Feb 5 2009, 02:10 PM

Hi guys,

Since superhai's VoodooPower has surpassed this kext in more ways than a few, and the current stable version of the kext has been working ok for the target audience, I have decided to halt the project for some time.

Whether this 'some time' is a few days, weeks or months is unclear – I might make changes etc. as and when I have time or feel the need, but active development is taking a break for now because I have taken on other projects which need more attention.

mitch_de

Feb 5 2009, 02:13 PM

Thanks - you always give us very good informations of dev process !
PS: Can you update some news also in the voodoo news wiki if you have time ?
Latest was from 6. Jan, and i think even not finished , some dev messages always are interesting.

bachok83

Feb 7 2009, 05:02 PM

i wonder what happened to 1.4.5. the moment i install it, i get kernel panic.

yeh

Mar 4 2009, 01:22 PM

Hi mercurysquad,

I have a MacPro and I can see a use for IntelEnhancedSpeedStep.kext, and I'm wondering if what I want to do will work.

Basically I want to stop speedstepping all together, and lock down the CPU to 3GHz.
The reason for this to do with latency and audio.

I have applied:
sudo sysctl -w kern.cputhrottle_targetload=1

but the speedstep.app is still showing me that the CPU is jumping between speedsteps all the time (2400, 2800, and 3000)
I'm only use the speedstep.app for viewing purposes.

Is there something I can do to achieve a locked 3000 setting atm? or does this require extra coding?

Cheers,

mercurysquad

Mar 5 2009, 04:48 AM

QUOTE (yeh @ Mar 4 2009, 06:52 PM)

Hi mercurysquad,

I have a MacPro and I can see a use for IntelEnhancedSpeedStep.kext, and I'm wondering if what I want to do will work.

Basically I want to stop speedstepping all together, and lock down the CPU to 3GHz.
The reason for this to do with latency and audio.

I have applied:
sudo sysctl -w kern.cputhrottle_targetload=1

but the speedstep.app is still showing me that the CPU is jumping between speedsteps all the time (2400, 2800, and 3000)
I'm only use the speedstep.app for viewing purposes.

Is there something I can do to achieve a locked 3000 setting atm? or does this require extra coding?

Cheers,

I use this all the time while using Logic Pro, to lock the processor to highest freq, otherwise the audio drops out when starting playback.

Leave the targetload as it is. You should do this instead:

CODE

sudo sysctl -w kern.cputhrottle_auto=0
sudo sysctl -w kern.cputhrottle_curfreq=3000

First command will turn off auto-throttling, second command will lock the frequency to 3000 MHz (or the nearest frequency supported by your processor).

Once you are done, just set _auto back to 1, though I think there's a bug which causes autothrottle to not turn back on sometimes. If that happens and a restart is not possible, just set the speedstep.app to auto mode and let it control the kext.

QUOTE (bachok83 @ Feb 7 2009, 10:32 PM)

i wonder what happened to 1.4.5. the moment i install it, i get kernel panic.

Yeah it has some nasty bugs with pointers which I never bothered to fix. Will do some day.. Please use 1.4.0 until then.

yeh

Mar 5 2009, 05:48 AM

Thank you mercurysquad,
Exactlly what I wanted to hear.

Regards,

Raoul

yeh

Mar 9 2009, 11:05 AM

Thank you for the reply Mercurysquad, forums are up again, so posting here also.

I applied the above suggestion.

CODE

MacPro:~ macpro$ sudo sysctl -w kern.cputhrottle_auto=0
kern.cputhrottle_auto: 1 -> 0
MacPro:~ macpro$ sysctl kern.cputhrottle_curfreq
kern.cputhrottle_curfreq: 2800
MacPro:~ macpro$ sudo sysctl -w kern.cputhrottle_curfreq=3000
Password:
kern.cputhrottle_curfreq: 2400 -> 3000
MacPro:~ macpro$ sysctl kern.cputhrottle_curfreq
kern.cputhrottle_curfreq: 2800
MacPro:~ macpro$ sysctl kern.cputhrottle_curfreq
kern.cputhrottle_curfreq: 2400
MacPro:~ macpro$

is this normal?

The CPUs still seem to "dance" around...

CODE

MacPro:~ macpro$ sysctl -a | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 2800
kern.cputhrottle_curvolt: 1125
kern.cputhrottle_freqs: 2400 2800 3000 
kern.cputhrottle_factoryvolts: 1025 1125 1125 
kern.cputhrottle_ctl: 18209
kern.cputhrottle_auto: 0
kern.cputhrottle_targetload: 30
MacPro:~ macpro$ sysctl -a | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 3000
kern.cputhrottle_curvolt: 1125
kern.cputhrottle_freqs: 2400 2800 3000 
kern.cputhrottle_factoryvolts: 1025 1125 1125 
kern.cputhrottle_ctl: 18209
kern.cputhrottle_auto: 0
kern.cputhrottle_targetload: 30
MacPro:~ macpro$ sysctl -a | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 3000
kern.cputhrottle_curvolt: 1125
kern.cputhrottle_freqs: 2400 2800 3000 
kern.cputhrottle_factoryvolts: 1025 1125 1125 
kern.cputhrottle_ctl: 18209
kern.cputhrottle_auto: 0
kern.cputhrottle_targetload: 30
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 3000
kern.cputhrottle_curvolt: 1125
kern.cputhrottle_freqs: 2400 2800 3000 
kern.cputhrottle_factoryvolts: 1025 1125 1125 
kern.cputhrottle_ctl: 18209
kern.cputhrottle_auto: 0
kern.cputhrottle_targetload: 30
MacPro:~ macpro$ sysctl -a | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 2400
kern.cputhrottle_curvolt: 937
kern.cputhrottle_freqs: 2400 2800 3000 
kern.cputhrottle_factoryvolts: 1025 1125 1125 
kern.cputhrottle_ctl: 1554
kern.cputhrottle_auto: 0
kern.cputhrottle_targetload: 30

Regards,

Raoul.

©lip✟ ☣ 81

Mar 13 2009, 06:16 PM

Hallo!
first of all, I'd like to thank you for all the work you've done.
I've always used your speedstep (new and old), but I've always meet
a recognition error of the cpu...
my processor is an 2,4 but he think that's an 2,21 one.
if I do a control with a xbech he say me that the score is less.
you can find my hardware down (in my signature), could you help me, please?
I await for your reply and

i thank you.
bye

leitor

Jun 4 2009, 10:01 AM

Hi mercurysquad,

Nice work you have done on this kext, I have a doubt, can I change the default target load on the info.plist of the version 1.4.0 of the kext? the 1.4.0 info.plist does not come with the key TargetCPULoad on it, and looking by the changesets for the code it seems that it was implemented after 1.4.0? can I add myself the key to the 1.4.0 release info.plist and it will work?

Master Chief

Jun 4 2009, 01:35 PM

I have trouble understanding people here. I mean wasn't this an announcement? Come on guys. Read the title: "Project being halted for some time, but not abandoned" which most likely also includes support. There seems to be a better solution available right now, so please use that or be quiet.

@mercurysquad:

I personally can't remember if I ever used your work, but thanks for your contribution to the community anyway.

BTW: Do you have plans to merge/cooperate with Superhai(s team) and work together on a Open Source variant?

mercurysquad2

Jun 15 2009, 06:42 PM

QUOTE (Master Chief @ Jun 4 2009, 07:05 PM)

I have trouble understanding people here. I mean wasn't this an announcement? Come on guys. Read the title: "Project being halted for some time, but not abandoned" which most likely also includes support. There seems to be a better solution available right now, so please use that or be quiet.

@mercurysquad:

I personally can't remember if I ever used your work, but thanks for your contribution to the community anyway.

BTW: Do you have plans to merge/cooperate with Superhai(s team) and work together on a Open Source variant?

1. There's no need to ask people to be quiet. I still occasionally check the forums, and people still use the kext.

2. I already directly and indirectly collaborate with Superhai, but I've mentioned this before: both kexts have different goals and different user bases. I intend to continue using my own kext as it's more than enough for my needs (and I guess other people too). As long as I use it myself, there will be support for it. (hence the "not abandoned").

3. This kext is already open source: http://opensource.mercurysquad.com/xnu-speedstep

Master Chief

Jun 15 2009, 09:18 PM

Right, but that wasn't clear. At least not from your first post here. Anyway, thanks for the heads up