Created attachment 133838 [details] dmesg for when I boot up
Description of problem: Using a Toshiba Satellite Pro A10. I have the cpufreq option set on services which causes the module to be loaded during the kernel loadup. However, during load up, I get an error that acpi_cpufreq cannot be loading - invalid argument Version-Release number of selected component (if applicable): kernel-2.6.17-1.2530.fc6 How reproducible: Always Steps to Reproduce: 1. Start machine 2. 3. Actual results: see dmesg file attached Expected results: acpi_cpufreq should load - it has in the past Additional info: Not sure if this is related to the other cpufreq bug already reported, though this is in rawhide and they seem to be FC4 related.
I am seeing the same, could be a compatibility problem with ACPI vs. SMP kernel? Notebook is Quanta ZW9.
2.6.17-1.2571.fc6 still the same
2.6.17-1.2573.fc6 still the same, I have also recompiled this kernel without SMP which made the acpi_cpufreq 116 KB big (instead of 16 KB in the SMP variant), but it still doesn't work
Not a notebook, but on asus P4C800E-Deluxe workstation boot after entering runlevel 5 and just after Checking for hardware changes: Starting readahead early: Starting background readahead [ok] [ok] Checking for hardware changes FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.17-1.2586.fc6/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): Invalid argument (hand transcried from digital pic of boot sequence. No msgs in /var/log that I can find) Bringing up loopback interface [ok] etc... This error has benn present for some time, but doesn't seem to affect anything on this workstation. HTH
Did an interactive startup and the error msg in comment #5 shows up immediately after Starting cpuspeed.
Googling acpi_cpufreq was beneficial. Found the following which fixed problem for me. http://www.redhat.com/archives/rhl-list/2005-November/msg03164.html
I have this problem too. My system is a tyan tiger 100 (S1832) dual processor capable (only 1 P3 850Mhz installed) with 256MB of RAM.
Still happens on 2.6.17-1.2597.fc6
I wonder if this is a kernel problem? Would it not be initscripts/cpuspeed since /etc/cpuspeed.conf DEVICE= is not being initialized properly? Who/what is supposed to provide the proper module name in cpuspeed.conf?
I think Clyde is right in that this is a cpuspeed problem.
It WORKS again in current kernel 2.6.17-1.2617.2.1.fc6
it works for me in kernel 2.6.17-1.2630.fc6. I did not try 2617.2.1.fc6 Thanks,
kernel 2.6.17-1.2630.fc6 works for me too