Karmic Network Unstable

Bug #468492 reported by Bryan Moore
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

After installing Karmic, I noticed my Atheros AR5212 802.11abg NIC seemed to continually associate and disassociate from any network I was connected with, similar to Bug #414560 (https://bugs.launchpad.net/linux/+bug/414560) but I'm not using the ath9k driver; rather, I'm using ath5k. I do not use either NetworkManager nor wicd, opting to specifically define my environments through /etc/network/interfaces and /etc/wpa_supplicant.conf. There have been discussions on threads I've either started or to which I've contributed (http://ubuntuforums.org/showthread.php?t=1306855 and http://ubuntuforums.org/showthread.php?t=1300774), but none of the suggested "fixes" have yielded any help.

Here are some, hopefully, relevant details:

lshw -C Network
*-network DISABLED
       description: Ethernet interface
       product: NetXtreme BCM5752M Gigabit Ethernet PCI Express
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 02
       serial: 00:1b:24:09:29:ba
       capacity: 1GB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd
       autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.99 duplex=half firmware=5752m-v3.22
       latency=0 link=yes multicast=yes port=twisted pair
       resources: irq:16 memory:ee000000-ee00ffff
  *-network
       description: Wireless interface
       product: AR5212 802.11abg NIC
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wmaster0
       version: 01
       serial: 00:19:7e:25:8d:31
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list logical ethernet physical wireless
       configuration: broadcast=yes driver=ath5k ip=192.168.1.2 latency=0 multicast=yes wireless=IEEE 802.11abg
       resources: irq:17 memory:edf00000-edf0ffff
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: vboxnet0
       serial: 0a:00:27:00:00:00
       capabilities: ethernet physical
       configuration: broadcast=yes multicast=yes

iwconfig (when connected)
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11abg ESSID:"35moore"
          Mode:Managed Frequency:2.452 GHz Access Point: 00:14:6C:F8:DE:96
          Bit Rate=54 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=70/70 Signal level=-40 dBm Noise level=-95 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

vboxnet0 no wireless extensions.

/etc/network/interfaces
# LOOPBACK INTERFACE
auto lo
iface lo inet loopback

# ETHERNET
allow-hotplug eth0
iface eth0 inet dhcp

# WIRELESS
auto wlan0
iface wlan0 inet dhcp
 wpa-conf /etc/wpa_supplicant.conf
 wireless-rate 54M

# HOME
iface home inet static
 address 192.168.1.2
 netmask 255.255.255.0
 network 192.168.0.0
 broadcast 192.168.1.255
 gateway 192.168.0.1

/etc/wpa_supplicant
ctrl_interface=/var/run/wpa_supplicant

network={
 ssid="HOME"
 id_str="home"
 scan_ssid=1
 key_mgmt=WPA-PSK
 psk="PASSPHRASE"
}

network={
 ssid="WORK"
 key_mgmt=NONE
 wep_key0=WEP-KEY01
}

If there's any other information I'm leaving out, please let me know because I'm really not too sure which to include.

Revision history for this message
Bryan Moore (moore-bryan) wrote :

Am I to assume no one is looking into this and, instead, focusing on the Network-Manager bug? I would suggest this is the more base issue because I do not use NM and still seem to have the issue. If it's a time issue, I understand; could someone point me to the wpa_supplicant maintainers so I can continue this discussion with them?

Revision history for this message
Tyler Rusk (tdrusk) wrote :

This happens to me as well. I would love to see a fix. I tried installing linux-backports-modules-wireless-karmic-generic but it did not change anything.

Revision history for this message
Bryan Moore (moore-bryan) wrote :

According to conversations in different forums, this is a common occurence and yet LaunchPad is silent on a fix?

Revision history for this message
stuart (stuart-hayton) wrote :

This is a me too. With this. Going to look for dups.

                description: Wireless interface
                product: AR5212 802.11abg NIC
                vendor: Atheros Communications Inc.
                physical id: 0
                bus info: pci@0000:03:00.0
                logical name: wmaster0
                version: 01
                serial: 00:19:7e:56:f2:f2
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list logical ethernet physical wireless
                configuration: broadcast=yes driver=ath5k latency=0 multicast=yes wireless=IEEE 802.11abg
                resources: irq:17 memory:edf00000-edf0ffff

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello
Is this problem present with the latest updated Karmic's or Lucid's packages?
Thanks in advance
Fabio

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
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.