Openmoko Bug #2171: stable-tracking 80f4b57/resume: eth0: ERROR while getting interface flags: No such device
Openmoko Public Trac
bugs at docs.openmoko.org
Tue Jan 13 07:01:41 CET 2009
#2171: stable-tracking 80f4b57/resume: eth0: ERROR while getting interface flags:
No such device
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
Okay, if you use power_on, that's expected. What power_on does is a reset
of the module, but completely behind the back of everything else.
Unbind/bind has pretty much the same effect (one layer above power_on),
so that's where you get the correct on/off action.
But what's the whole story ? Do you want to enter a power-saving state ?
There are currenly three choices for this that aren't specific to the
WLAN module: unbind/bind, suspend/resume (*), and module unload/load.
They all should produce the same effect, namely that the driver gets
removed and the module powers down.
(*) That is, unless you've set the "persist" option of the S3C MMC
driver.
Furthermore, you can use wmiconfig to disable the module without driver
removal. --power rec sets a sensible power consumption and --wlan disable
turns off transmission and rejects other ioctls until --wlan enable.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list