Sander van Grieken
sander at 3v8.net
Wed Jan 7 13:37:10 CET 2009
On Wednesday 07 January 2009 13:10:14 Sander van Grieken wrote:
> On Wednesday 07 January 2009 12:51:33 Andy Green wrote:
> > Somebody in the thread at some point said:
> > | In the end I only had to change bitbake's conf/local.conf and include
> > these
> > | lines to move over to 2.6.28 + comaptible frameworkd:
> > |
> > | PREFERRED_PROVIDER_virtual/kernel = "linux-openmoko-devel"
> > | PREFERRED_PROVIDER_frameworkd = "frameworkd-devel"
> > That sounds cool.
> > | - wifi seems to be toggled by each suspend/resume cycle. After boot
> > wifi is
> > | enabled (even though the interface is not marked 'auto' in
> > | /etc/network/interfaces). After the first suspend cycle it's disabled,
> > the
> > | next cycle it's enabled again, etc.
> > Thanks for the report about it, what does enabled or disabled mean for
> > Wifi? Say if it is in "disabled" situation, what does that look like?
> eth0 is up but lost its IP, wireless is not associated.
> An 'ifup eth0' immediately re-establishes the connection..
also, if wireless comes up disabled after a suspend cycle, and I bring it up
manually using ifup, the next suspend cycle disables it again. So it depends
on the runtime state of wireless, not on the suspend cycle #.
More information about the devel