reenabling wireless does not work

Bug #545287 reported by supercompman
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Lucid by supercompman

Bug Description

On my Asus Eee PC 900HA using Ubuntu 10.04 Beta 1, as long as wireless is enabled on boot the wireless works fine, but if the wireless is disabled then reenabled, the network manager insists that the wireless is "not ready" and never shows a list of available wireless networks. The only way I've found to get the wireless to work again is to enable the wireless then reboot.

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Mar 23 12:59:52 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.153.0/24 dev eth0 proto kernel scope link src 192.168.153.46 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.153.1 dev eth0 proto static
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Package: network-manager-gnome 0.8-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
RfKill:
 0: eeepc-wlan: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager-applet
Uname: Linux 2.6.32-16-generic i686

Revision history for this message
supercompman (supercompman) wrote :
Revision history for this message
supercompman (supercompman) wrote :

This bug is still not corrected in 10.04 RC.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This is a driver issue with the one used for wifi on the EeePC, reassigning to the 'linux' package.

affects: network-manager-applet (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi supercompman,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.