cc'ing linaro-dev
On Fri, Aug 6, 2010 at 10:59 AM, Amit Arora amit.arora@linaro.org wrote:
On Fri, Aug 6, 2010 at 1:14 PM, Yong Shen yong.shen@linaro.org wrote:
Hi Amit,
Clearly, we did not implement these nodes. See below. root@freescale ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies cat: can't open '/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies': No such file or directory root@freescale ~$ ls /sys/devices/system/cpu/cpu0/cpuidle ls: /sys/devices/system/cpu/cpu0/cpuidle: No such file or directory
Ok. How about contents of cpufreq/scaling_min_freq, cpufreq/scaling_cur_freq and cpufreq/scaling_max_freq ?
Sorry for troubling you on this. But, actually, sending a tarball of /sys/devices/system/cpu would have avoided all these questions. :)
About "Error opening terminal: vt100", I still have it. I believe I had already installed ncurse-bin package, since it was compiled with ncursesw togather. This error is printed by ncurses/base/lib_initscr.c. Still checking.
Yong, could you set your evironment variables TERM=linux and see if this error still occurs?
/Amit
Setting TERM to linux does not help. I am wondering if it has anything to do with my kernel command line "console=ttymxc0,115200".
Yong
On Fri, Aug 6, 2010 at 4:16 PM, Amit Kucheria amit.kucheria@linaro.orgwrote:
cc'ing linaro-dev
On Fri, Aug 6, 2010 at 10:59 AM, Amit Arora amit.arora@linaro.org wrote:
On Fri, Aug 6, 2010 at 1:14 PM, Yong Shen yong.shen@linaro.org wrote:
Hi Amit,
Clearly, we did not implement these nodes. See below. root@freescale ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies cat: can't open '/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies': No such file or directory root@freescale ~$ ls /sys/devices/system/cpu/cpu0/cpuidle ls: /sys/devices/system/cpu/cpu0/cpuidle: No such file or directory
Ok. How about contents of cpufreq/scaling_min_freq, cpufreq/scaling_cur_freq and cpufreq/scaling_max_freq ?
Sorry for troubling you on this. But, actually, sending a tarball of /sys/devices/system/cpu would have avoided all these questions. :)
About "Error opening terminal: vt100", I still have it. I believe I had already installed ncurse-bin package, since it was compiled with
ncursesw
togather. This error is printed by ncurses/base/lib_initscr.c. Still checking.
Yong, could you set your evironment variables TERM=linux and see if this error still occurs?
/Amit
Powertop works well with $TERM and $TERMINFO correctly setup. A snapshoot attached.
Yong
On Fri, Aug 6, 2010 at 4:31 PM, Yong Shen yong.shen@linaro.org wrote:
Setting TERM to linux does not help. I am wondering if it has anything to do with my kernel command line "console=ttymxc0,115200".
Yong
On Fri, Aug 6, 2010 at 4:16 PM, Amit Kucheria amit.kucheria@linaro.orgwrote:
cc'ing linaro-dev
On Fri, Aug 6, 2010 at 10:59 AM, Amit Arora amit.arora@linaro.org wrote:
On Fri, Aug 6, 2010 at 1:14 PM, Yong Shen yong.shen@linaro.org wrote:
Hi Amit,
Clearly, we did not implement these nodes. See below. root@freescale ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies cat: can't open '/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies':
No
such file or directory root@freescale ~$ ls /sys/devices/system/cpu/cpu0/cpuidle ls: /sys/devices/system/cpu/cpu0/cpuidle: No such file or directory
Ok. How about contents of cpufreq/scaling_min_freq, cpufreq/scaling_cur_freq and cpufreq/scaling_max_freq ?
Sorry for troubling you on this. But, actually, sending a tarball of /sys/devices/system/cpu would have avoided all these questions. :)
About "Error opening terminal: vt100", I still have it. I believe I had already installed ncurse-bin package, since it was compiled with
ncursesw
togather. This error is printed by ncurses/base/lib_initscr.c. Still checking.
Yong, could you set your evironment variables TERM=linux and see if this error still occurs?
/Amit
-
Amit Kucheria -
Yong Shen