Todo #704
closed
Load cpufreq.ko when powerd is enabled
100%
Description
Looks like we need to load cpufreq.ko when powerd is enabled, and some systems also need to change their timecounter (but there may not be any automated way to accommodate that)
See: http://forum.pfsense.org/index.php/topic,26238.msg136719.html#msg136719
Updated by Jim Pingle over 14 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset c3b13d6082033ecd1d3f7672ca9b1533942ec00a.
Updated by Bipin Chandra over 14 years ago
im on the 30th june nanobsd snap and if i enable powerd, this is what i get in the console
powerd: lookup freq: No such file or directory
Updated by Jim Pingle over 14 years ago
What kind of hardware are you using?
I'm running it on my router (VIA CPU running a NanoBSD snapshot) and it loads without error, and does appear to be adjusting the CPU frequency properly:
dev.cpu.0.freq: 373 dev.cpu.0.freq_levels: 995/-1 870/-1 746/-1 621/-1 497/-1 373/-1 248/-1 124/-1
(run a few commands)
dev.cpu.0.freq: 497 dev.cpu.0.freq_levels: 995/-1 870/-1 746/-1 621/-1 497/-1 373/-1 248/-1 124/-1
Can you tell if cpufreq.ko is loaded? (run kldstat from a shell prompt)
Updated by Jim Pingle over 14 years ago
I got that error the next time I booted my router, so it may still be an issue. I'll look into it.
Does the ALIX even support multiple frequencies? If you load cpufreq by hand do you get output similar to what I show above?
Updated by Bipin Chandra over 14 years ago
kldstat
Id Refs Address Size Name
1 15 0xc0400000 c61cd4 kernel
2 1 0xc2c79000 e000 dummynet.ko
3 1 0xc2ee0000 b000 cpufreq.ko
dev.cpu.0.freq: 373
cpu.0.freq:: Too many argumentsdev.
Updated by Jim Pingle about 14 years ago
- Status changed from Feedback to Resolved
Closing this as the error given is due to ALIX not really supporting powerd with the default TSC timecounter, which is not the fault of cpufreq.ko which loads OK at boot time.
If we need some other mechanism to change timecounters (if that would even help) that would end up being a new feature and not really related to this ticket.