speedstep-smi not detecting speedstep-capability with early Pentium 3 Coppermine
http://bugzilla.kernel.org/show_bug.cgi?id=5985
------- Additional Comments From [email protected] 2006-01-31 19:36 ------- Could you try with module options?
modprobe speedstep-smi smi_port=0xb2 smi_cmd=0x82 smi_sig=1
Driver ignores a broken information and try to proceed. There are many reports that some coppermine platforms have odd bios. I think these platforms might be made before Intel/Microsoft defined the interface specification.
In MS Windows, PC vendor can overwrite these parameters by setting the some registory values as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\P3\Parameters\HackFlags==0x5 or 0x1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\P3\Parameters\SmiCmdPort==SMI Cmd Data Port HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\P3\Parameters\SmiCmdData==SMI Cmd Data Value
You can find right values in pre-installed windows registory. These values may be set by Intel Speedstep Applet pre-installed or bandled. A registry location is defined in Microsoft's "Windows Native Processor Performance Control" document.
The situation 'perf_level:0x47534943' is not an offset change. These values are retrived in arch/i386/boot/setup.S:507
movl $0x0000E980, %eax # IST Support
movl $0x47534943, %edx #<-- # Request value
int $0x15 movl %eax, (96)
movl %ebx, (100)
movl %ecx, (104)
movl %edx, (108) #<--so this means BIOS doesn't return a proper value on %edx, because of setting %edx as signature before call BIOS.
Hiroshi Miura
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.