search

brucehuynhlee / xnu-speedstep

Automatically exported from code.google.com/p/xnu-speedstep
0 stars 0 forks source link

Crash if not unloaded/loaded after boot #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. iatkos 10.5.4 on d830 (nvidia, t7200), kernel 9.2.2, IESS 1.3.2
2. Reboot, start gui for speedstep (any) vith auto throttling, gray curtain of 
death
3. Reboo, unload IESS, load IESS, start gui, works gread 800,1200,1600,2000

What is the expected output? What do you see instead?
Throttling, panic.

What version of the kext are you using? On what kernel and processor?

1.3.2, 9.2.2, T72000

Please provide any additional information below.

Thanks, saves me an hour of working time when it works!
Please turn on DebugMessages in the Info.plist, reload the kext and try to 
reproduce the 
problem. Attach output of this command:
sudo dmesg | grep IntelEnhanced && sysctl hw.busfrequency && sysctl machdep.cpu 
&& uname -
a

In case you get kernel panic, boot up in single user mode (bootflag -s), load 
the kext manually, 
and note down or take a photo of the kernel panic message. Attach it as well.

Original issue reported on code.google.com by mailar...@gmail.com on 20 Aug 2008 at 2:41

GoogleCodeExporter commented 8 years ago 
What happens if you change KernelFeatures to 3 in the kext's Info.plist, and 
reboot 
with -f bootflag? That should fix it. If not, please post some more details 
(logs 
etc). Thanks.

Original comment by mercurys...@gmail.com on 25 Aug 2008 at 12:54

GoogleCodeExporter commented 8 years ago 
That worked, i don't really get why it does though :)

BTW: CPU is T7300, sorry for the missinformation.

Original comment by mailar...@gmail.com on 26 Aug 2008 at 2:22

GoogleCodeExporter commented 8 years ago 
-f is not needed, only the mysterious 3 in kernelfeatures

Original comment by mailar...@gmail.com on 28 Aug 2008 at 11:11

GoogleCodeExporter commented 8 years ago 
The kext has some features which only newer (unreleased) patched kernels 
support, so it tries to auto-detect if 
it's running on such a kernel. This includes clock recalibration and <1GHz 
support. Sometimes this 
autodetection fails. In this case you can force the kext to use a compatible 
mode by setting KernelFeatures to 1,2 
or 3 (the meaning of that will be described in the documentation).

Original comment by prashant...@gmail.com on 8 Sep 2008 at 11:35