|
|
 |
« Reply #15 on: September 12, 2009, 06:44:01 AM » |
|
Hi,
OK, having de-bricked using the V1.0 installer I came back to this method to get me to a working cpuidle!
The 2009/09/11 updated README-2.6.30.6 gets right to the end and then fails with $1 undefined, bizarrely, so I manually copied the 2.6.30.6 image into /boot rather than / (moving the old uImage aside), and the system will boot, but still on .2 rather than .6.
So, I too am puzzled...
Do we need to redirect stuff under /sys such as /sys/firmware, etc?
Rgds
Damon
PS. The error was:
... Extracting modules README-2.6.30.6: line 91: $1: unbound variable
|
|
|
|
« Last Edit: September 12, 2009, 06:59:02 AM by DamonHD »
|
Logged
|
|
|
|
|
wzzrd
Newbie
Karma: 0
Posts: 4
|
 |
« Reply #16 on: September 12, 2009, 07:20:38 AM » |
|
I have my kernel on Flash as it is, and I boot from a memory card with an ext3 filesystem on it, but I'd like to try UBIFS instead.
So I'm just wondering: if I flash the kernel to the Plug and then boot the kernel from the built-in Flash, I should be able to have a memory card with UBIFS as my root filesystem right? Since the modules are right there with the kernel on the built-in Flash. Right?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #17 on: September 12, 2009, 07:45:30 AM » |
|
The new V1.0 loader uses UBIFS from NAND, in case that helps...
Rgds
Damon
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #18 on: September 12, 2009, 07:58:20 AM » |
|
I see this kernel supports cpuidle, but not tickless. Is there any disadvantage if you enable tickless feature in the kernel (CONFIG_NO_HZ)?
Clearly there is a power usage/heat production advantage to enabling it, but is there a downside? if there isn't can this be added?
|
|
|
|
|
Logged
|
|
|
|
|
cbxbiker61
Global Moderator
Sr. Member
   
Karma: 37
Posts: 488
|
 |
« Reply #19 on: September 12, 2009, 12:54:58 PM » |
|
I see this kernel supports cpuidle, but not tickless. Is there any disadvantage if you enable tickless feature in the kernel (CONFIG_NO_HZ)?
Clearly there is a power usage/heat production advantage to enabling it, but is there a downside? if there isn't can this be added?
CONFIG_NO_HZ is enabled. Not sure what you saw that made you think it isn't.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #20 on: September 12, 2009, 04:15:44 PM » |
|
I see this kernel supports cpuidle, but not tickless. Is there any disadvantage if you enable tickless feature in the kernel (CONFIG_NO_HZ)?
Clearly there is a power usage/heat production advantage to enabling it, but is there a downside? if there isn't can this be added?
CONFIG_NO_HZ is enabled. Not sure what you saw that made you think it isn't. I made the seeminly false assumption by running "powertop" and seeing that orion_tick was the biggest cause of coming out of idle state. A quick google suggested that if the kernel was tickless, then I wouldn't be seeing this. PowerTOP version 1.11 (C) 2007 Intel Corporation
Cn Avg residency P-states (frequencies) C0 (cpu running) ( 0.7%) C0 7.5ms ( 8.8%) C1 36.0ms (90.5%)
Wakeups-from-idle per second : 37.0 interval: 20.0s
Top causes for wakeups: 31.9% ( 25.9) <interrupt> : orion_tick 27.1% ( 22.0) twonkymediaserv : hrtimer_start_range_ns (hrtimer_wakeup) 12.9% ( 10.4) <interrupt> : mvsdio 6.5% ( 5.2) <kernel core> : hrtimer_start (tick_sched_timer) 6.0% ( 4.8) <kernel core> : hrtimer_start_range_ns (tick_sched_timer) 3.7% ( 3.0) python : hrtimer_start_range_ns (hrtimer_wakeup)
Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option. Without HPET support the kernel needs to wake up every 20 milliseconds for some housekeeping tasks.
|
|
|
|
« Last Edit: September 12, 2009, 04:18:18 PM by mgillespie »
|
Logged
|
|
|
|
|
|
|
 |
« Reply #21 on: September 12, 2009, 10:21:54 PM » |
|
Ehhhm... could we talk about functionallity a little bit later, when booting 2.6.30.6 was successfull ? ;-) @ DamonHD: Do you want to boot from NAND or from MMC ? I am wondering about your error message while running README... @ cbxbiker61: Is there a HowTo, which explains, WHERE "uImage" is located ? My /boot is empty... The updated README only generates the file /sheeva-2.6.30.6-uImage Please look at http://plugcomputer.org/plugforum/index.php?topic=711.msg4437#msg4437Best regards. Bjoern EDIT: SOLVED BY MYSELF: http://plugcomputer.org/plugforum/index.php?topic=724.0
|
|
|
|
« Last Edit: September 12, 2009, 11:31:40 PM by nephilim1973 »
|
Logged
|
|
|
|
|
|
|
 |
« Reply #22 on: September 13, 2009, 01:06:35 AM » |
|
Hi,
I was going to boot from SD, but since it is now booting fast from NAND I'm happy to live with that for now.
I may not need to upgrade to .6 if there are no further power savings to be had yet.
Rgds
Damon
PS. Only thing I can find no evidence for is CONFIG_USB_SUSPEND; just plugging in a USB hub seems to raise consumption by 1W or so... In an older x86 kernel that I tuned for low power I set the .../power/autosuspend values to 1 in rc.local but I cannot see an equivalent available in this kernel.
|
|
|
|
« Last Edit: September 13, 2009, 02:23:41 AM by DamonHD »
|
Logged
|
|
|
|
|
jimmy
Newbie
Karma: 0
Posts: 2
|
 |
« Reply #23 on: September 18, 2009, 06:04:47 AM » |
|
FYI, There is no USB Bluetooth Dongle support in Kernel rc6
I used rc6 via Sheeva Plug installer alpha 6 and ended up having to replace this kernel with rc5 to get Bluetooth working.
|
|
|
|
|
Logged
|
|
|
|
|
jimmy
Newbie
Karma: 0
Posts: 2
|
 |
« Reply #24 on: September 18, 2009, 06:15:23 AM » |
|
Why is Sheeva Plug Installer V1.0 based on kernel 2.6.30-rc2 when the latest release is 2.6.30.1. Is there something special about rc2. Also, I found that Bluetooth does not work on rc6. What is the most stable kernel version for Bluetooth support via USB.
|
|
|
|
|
Logged
|
|
|
|
|
|