Difference between revisions of "Talk:How to get SpeedStep working on Coppermine-piix4-smi based ThinkPads"

From ThinkWiki
Jump to: navigation, search
(RELAXED_CAP_CHECK on T20)
 
Line 5: Line 5:
  
 
[[User:jmalonzo|Jan Alonzo]] {{CURRENTTIME}} {{CURRENTDAY}}-{{CURRENTMONTH}}-{{CURRENTYEAR}}
 
[[User:jmalonzo|Jan Alonzo]] {{CURRENTTIME}} {{CURRENTDAY}}-{{CURRENTMONTH}}-{{CURRENTYEAR}}
 +
 +
From the kernel config:
 +
  ┌────────────────────── Relaxed speedstep capability checks ──────────────────────┐
 +
  │ CONFIG_X86_SPEEDSTEP_RELAXED_CHECK:                                        │
 +
  │                                                                                │
 +
  │ Don't perform all checks for a speedstep capable system which would            │
 +
  │ normally be done. Some ancient or strange systems, though speedstep            │
 +
  │ capable, don't always indicate that they are speedstep capable. This            │
 +
  │ option lets the probing code bypass some of those checks if the                │
 +
  │ parameter "relaxed_check=1" is passed to the module.                            │
 +
  │                                                                                │
 +
 +
this option only lets you use relaxed_check=1, it doesn't solve anything.

Revision as of 13:03, 11 April 2005

RELAXED_CAP_CHECK on T20

On a Thinkpad T20 using Debian unstable and a stock kernel.org kernel 2.6.11.6, building the kernel with CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y doesn't seem to show the error you're experiencing while loading speedstep-smi. So that means loading speedstep-smi module results to no error at all.

Jan Alonzo 22:00 25-04-2024

From the kernel config:

 ┌────────────────────── Relaxed speedstep capability checks ──────────────────────┐
 │ CONFIG_X86_SPEEDSTEP_RELAXED_CHECK:                                         │
 │                                                                                 │
 │ Don't perform all checks for a speedstep capable system which would             │
 │ normally be done. Some ancient or strange systems, though speedstep             │
 │ capable, don't always indicate that they are speedstep capable. This            │
 │ option lets the probing code bypass some of those checks if the                 │
 │ parameter "relaxed_check=1" is passed to the module.                            │
 │                                                                                 │

this option only lets you use relaxed_check=1, it doesn't solve anything.