Karmic Network Unstable
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:/
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
latency=0 link=yes multicast=yes port=twisted pair
resources: irq:16 memory:
*-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
resources: irq:17 memory:
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: vboxnet0
serial: 0a:00:27:00:00:00
iwconfig (when connected)
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11abg ESSID:"35moore"
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/
# 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_
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=
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.
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?