Tiny Core Extensions > TCE Q&A Forum

cpufreq, cant get it to work.

<< < (2/3) > >>

Juanito:
It might be an idea to do this one step at a time - to make sure nothing is corrupted, it would be a good idea to delete hwmon-cpufreq-2.6.26.tcem and cpufreq.tcel, reboot and then download and "tce-load" these two extensions again.

Once this is done, and without starting the acpid or cpufreqd daemons, can you "sudo modprobe acpi-cpufreq"?

What does "which acpid" and "which cpufreqd" give?

pema:
Ok, reloaded the tce's, sudo modprobe acpi-cpufreq gives error inserting module, device or resource busy. Which acpid gives nothing, which cpufreqd tells /usr/local/sbin/cpufreqd.

Modprobing powernow-k7 always works, and after a couple of reboots I got the laptop_mode started and could get a scaling governor accepted. Seems right now as the cpu-scaling works, hasnt stressed it enough to be sure yet.
As I understand the howtos on internet, acpi is a universal cpu driver, and somehow depends on cpu type, the only driver I get to work is the powernow-k7(tried all) which also is the speced driver for my amd-k6 cpu.
I tried writing the modprobe commands to etc/init.d/rcS and opt/bootlocal.sh, letting them start the cpu-scaling but cant get it to work, can I use same syntax in bootscripts as in terminal ?. Are the rcs and bootlocal.sh "sudo's" ?

Juanito:
Here's the script I use to start things:
--- Code: ---#!/bin/sh -e
#
tce-load /mnt/sda1/extensions/hwmon-cpufreq-2.6.26.tcem
#
tce-load /mnt/sda1/source/buildtc/08_10_25/cpufreq.tcel
#
sudo modprobe acpi-cpufreq
sudo modprobe cpufreq_conservative
sudo modprobe cpufreq_ondemand
sudo modprobe cpufreq_powersave
sudo modprobe cpufreq_userspace
#
sudo acpid
sudo cpufreqd
sudo /etc/init.d/laptop-mode start
#
# EOF
--- End code ---

Note that "which acpid" should find acpid on your system otherwise the "sudo acpid" line in the script would not work...

If you want the above to happen at boot, you could put the two modules in your /tce folder where they would be auto-loaded at boot and call a script containing the rest of the  commands from bootlocal.sh - note that bootlocal.sh runs as root, so you could remove "sudo" from each of the lines.

pema:
Yes, thats how I did it, but I still have to start manually in terminal.
Today I cant start laptop_mode, when launching command sudo laptop_mode start, I get laptop mode tools 1.45, next line laptop mode disabled, not active, I have checked all conf files I can find in /etc/ and /proc/acpi.

One thing that bugs me is that Iam not able starting the acpi(I guess I need acpi whatever cpu I have), sudo modprobe acpi-cpufreq gives device or resource busy, it is available in the lib, same for acpid -f -d. I have re-read your advices and tried them over and over again, but Iam not getting the acpi started. Is there any log I can check or command for diagnose ?

Juanito:
I'm not sure laptop-mode would start reliably without acpid running - also, laptop-mode would start only when the right conditions are met, for example when the power cord is disconnected.

Do you have anything in your boot codes about "apm" or "acpi" that might prevent the acpid daemon from running? Does "dmesg | grep acpi" give any clues?

If you issue the "top" command, does it show that acpid is already running?

Sorry, but without access to the same cpu as you, it's kind of hard to give too many suggestions...

Navigation

[0] Message Index

[#] Next page

[*] Previous page