Bug 248267
| Summary: | NetworkManager should turn off the radio if wireless is disabled | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jason Merrill <jason> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | abartlet, jeremy, jns, redhat-bugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-16 22:33:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jason Merrill
2007-07-14 19:15:44 UTC
So this is made more important because some wireless hardware (iwlwifi specifically) can't receive rfkill interrupts when down, since the interrupts are handled by the firmware which is only loaded when the card is IFF_UP. So instead of downing devices on rfkill or wireless-enabled, we should simply set the txpower off instead and leave them up. Drivers that don't support the txpower setting need to be fixed anyway. *** Bug 441994 has been marked as a duplicate of this bug. *** As a note, we can't do this until we get some HAL additions to be able to check hardware power state independently of soft power state. Currently, if you 'txpower off' on some cards (mostly Intel) it looks to HAL and therefore NM like a hardware killswitch has been thrown, and you cannot re-enable the device from the menu because HAL/NM think its disabled in hardware. We need to add a method to the HAL killswitch interface for GetHardwarePower(). Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Network Manger does many great things, but as I understand it, it still can't turn off the radio. It does; it sets the device down when you turn off wireless. It's then the device's responsibility to consume power as appropriate when the driver knows that the device is unused. That's the best we get until 2.6.32 where a sane rfkill framework has appeared. At that point, we can at least try to rfkill stuff when you uncheck "enable wireless". Before then, no. But when the interface is down (which NM does when you disable wireless), the driver is free to unload firmware and powersave. |