[Debian] 2.6.34 Openmoko kernel package available

Timo Jyrinki timo.jyrinki at gmail.com
Fri Dec 17 10:28:53 CET 2010

2010/12/16 Neil Jerram <neiljerram at gmail.com>:
> Even after removing the /dev/input files as you suggested (in
> /etc/rc.local), my observation is that XOrg still eats all CPU after
> an initial boot-up, but that if I then do "/etc/init.d/nodm stop" and
> "/etc/init.d/nodm start", it returns to using a normal (small) amount
> of CPU.  Is that as you would expect?

That doesn't happen to me, but it's probably related to starting X in
parallel with rc.local, so X gets to probe those before they are

Anyway, if one can come up with a perfect xorg.conf that disables the
extra devices there and only configures glamo + touch input + hw
buttons, that'd be nice.

> I noticed that wifi is powered on after boot-up.  Is that expected?
> Note that I am not currently running frameworkd or other FSO daemons -
> so perhaps this is normal, and I haven't seen it before because the
> FSO daemons turn wifi OFF when they start up.  (Alternatively, could
> wicd be powering on the wifi?)

If I recall correctly that was always so in the old kernels as well,
so even though it makes not much sense it may be so also now. But I'm
using FSO so possibly it shuts the power off when starting (although,
on the other hand, I wouldn't expect the FSO1 to know the sys paths in
2.6.34). For me, iwconfig shows the device but om wifi power confirms
that it's not "really" powered up (and iwconfig says Tx-Power=off). I
guess the interface is always there as ar6000 support is compiled into
the kernel?


More information about the community mailing list