Other than this issue, I sometimes have a disconnect where I have to 
unload and reload the driver, but that is rare (happened 5 or 6 times in 
the past year, I can't reproduce it). Beyond this, I am running a fresh 
feisty install later upgraded to gutsy and the ipw2200 works perfectly 
in every situation I've managed to throw at it. I have never tried ad 
hoc networking with it but I've never had a problem connecting to a network.

Kliment

Alexander Sack wrote:
> On Mon, Jul 23, 2007 at 11:48:28AM -0000, Kliment Yanev wrote:
>> Public bug reported:
>>
>> Binary package hint: network-manager
>>
>> Use case: 
>> I tell network-manager to disable my wireless, expecting this to gain me 
>> some battery life or because I am entering a no-radio zone (airplane, 
>> hospital etc). My laptop has no hardware switch or led to indicate wireless 
>> status, so I assume network-manager has switched it off
>>
>> Current behavior: 
>> The radio interface is still active and the number of interrupts reported by 
>> powertop for the ipw2200 driver goes up drastically. The "disabled" 
>> interface thus uses more power and misleads the users. Using rf_kill 
>> manually disables the radio and stops the interrupts, as expected.
>>
>> I am using 2.6.22 on gutsy with all updates.
>>
>> Proposed solution:
>> Make network-manager aware of rf_kill state and disable radio when wireless 
>> is disabled.
> 
> OK, thanks for the report. maybe one of the next updates will help
> ... anyway, does your wireless setup in gutsy work with ipw2200 driver
> in general? What setup are you running?
> 
>  - Alexander
>

-- 
network-manager does not really deactivate ipw2200
https://bugs.launchpad.net/bugs/127711
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to