S K wrote: > Hi, > > I already did the cpufreq.debug thing and it was using the > smi_speedstep driver instread of the acpi_speedstep (or whatever is > the right name). > > Alan already told me this is likely an ACPI issue. So, I already sent > the acpidump in a prev email (Aug 3rd 08). I'm don't have access to my > home machine right now. Will send it again later if you can't get my > prev email from the archives. > I could be completely wrong though! I'd not heard of speedstep_smi before (now I look, it doesn't seem to be an option in the cpu frequency scaling Kconfig menu?). I assumed the error messages you had about SMI were just flack. I thought acpi-cpufreq was the only option on recent machines - and that a quad core probably counts as recent. The error messages could be due to Fedora scripts unconditionally loading several different modules, to find one that works. I'm not sure how you can answer Zhao's question if you don't already know. I expect Fedora C7 does try loading acpi_cpufreq (as well as speedstep_smi). Whether your machine actually supports acpi_cpufreq is the question we're trying to answer. (This is where looking at Windows, or BIOS settings, would help). Alan -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
