network manager does not connect with ath5k

Bug #327940 reported by Richard Fairthorne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

On a fresh install of jaunty, my intel based laptop connected to my wireless network perfectly. My acer aspire one, on the other hand, does not connect without manual intervention. It is using the ath5k driver which loads sucessfully, but the network manager applet does not "see" that there is a wireless card (Enable wireless is grayed out) and I have to configure the network by hand.

To configure the network I merely typed:

iwconfig wlan0 essid obstaclesgone_com key=somekeythatiuse
dhclient wlan0

It works flawlessly but refuses to configure with Network Manager. Need any info.. just ask and I'll post it.

uname -a
Linux mini-me 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:43:21 UTC 2009 i686 GNU/Linux

root@mini-me:/home/richard# lspci | grep -i ath
03:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

wlan0 IEEE 802.11bg ESSID:"obstaclesgone_com"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:1D:7E:B8:CF:62
          Bit Rate=1 Mb/s Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2352 B
          Encryption key:B4BA-DB00-B5 Security mode:open
          Power Management:off
          Link Quality=71/100 Signal level:-54 dBm Noise level=-100 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Running iwlist scanning returns many networks.

Revision history for this message
Richard Fairthorne (richard-fairthorne) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

driver bug. moving to linux package for further triage.

Revision history for this message
Richard Fairthorne (richard-fairthorne) wrote :

Could anyone explain to me how this is a driver bug? I write code, and I'd certainly fix it if I understood how it was determined that the fault was with the driver.

I'd like to note that the interface operates flawlessly if I manually configure the link and run dhcp.

If iwconfig and iwlist can determine that it's a wireless interface, why can't network manager?

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.