You are not logged in.
Pages: 1
When I installed Arch (a month or so ago), I set up PHC using the wiki page and it was working fine, but now I've just noticed it's not working. Conky wasn't reporting temperature properly for a while until I got around to fixing it, a couple of days ago, and I noticed it was higher than it should've been. I checked for PHC files where the wiki page says to, and there are none:
[j@j-laptop ~]$ ls /sys/devices/system/cpu/cpu*/cpufreq/
/sys/devices/system/cpu/cpu0/cpufreq/:
affected_cpus ondemand scaling_governor
bios_limit related_cpus scaling_max_freq
cpuinfo_cur_freq scaling_available_frequencies scaling_min_freq
cpuinfo_max_freq scaling_available_governors scaling_setspeed
cpuinfo_min_freq scaling_cur_freq
cpuinfo_transition_latency scaling_driver
/sys/devices/system/cpu/cpu1/cpufreq/:
affected_cpus ondemand scaling_governor
bios_limit related_cpus scaling_max_freq
cpuinfo_cur_freq scaling_available_frequencies scaling_min_freq
cpuinfo_max_freq scaling_available_governors scaling_setspeed
cpuinfo_min_freq scaling_cur_freq
cpuinfo_transition_latency scaling_driver
phc-intel is still installed, and at the latest version (0.3.2-12). I'm not sure when it stopped working, so it's hard to find updates in Pacman's log that might be related. acpi-cpufreq is in rc.conf's MODULES array and it seems to be running.
[j@j-laptop ~]$ lsmod | grep cpufreq
cpufreq_ondemand 7480 2
acpi_cpufreq 5101 1
freq_table 2007 2 cpufreq_ondemand,acpi_cpufreq
processor 22529 3 acpi_cpufreq
mperf 987 1 acpi_cpufreq
dmesg gives nothing. Help?
Offline
Did you reinstall the package after upgrading the kernel?
ᶘ ᵒᴥᵒᶅ
Offline
Huh, I didn't even notice the kernel upgrade; that is around the time it would've happened, yes. And, while I think it's strange reinstalling the same package again makes a difference, that has fixed it, so thank you very much. I guess the filesystem tree makepkg produces depends on the installed kernel?
Offline
I don't know for sure but my guess would be that PHC's installation actually replaces the acpi-cpufreq module.
Edit: this is wrong, see ROOKIE's answer below .
Last edited by stqn (2011-02-07 16:42:12)
Offline
Huh, I didn't even notice the kernel upgrade; that is around the time it would've happened, yes. And, while I think it's strange reinstalling the same package again makes a difference, that has fixed it, so thank you very much. I guess the filesystem tree makepkg produces depends on the installed kernel?
Check the PKGBUILD, it clearly references the currently running kernel.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
I don't know for sure but my guess would be that PHC's installation actually replaces the acpi-cpufreq module.
Nope, it just adds a .conf file to /etc/modprobe.d which will load phc instead of acpi-cpufreq/powernow_k8/whatever, much like what is done to load ehci_hcd before loading ohci_hcd when trying to load ohci_hcd.
However like ngoonee says, the module needs to be rebuilt for every kernel update.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Huh, I didn't even notice the kernel upgrade; that is around the time it would've happened, yes. And, while I think it's strange reinstalling the same package again makes a difference, that has fixed it, so thank you very much. I guess the filesystem tree makepkg produces depends on the installed kernel?
Please mark your thread solved J.
ᶘ ᵒᴥᵒᶅ
Offline
Pages: 1