Sorry I no longer have the laptop that I used that adapter in. I do still have the cardbus adapter, and if you would like to give me a mailing address, I'd be happy to send it to you. On Mar 29, 2012 6:36 AM, "Christopher M. Penalver" < christopher.penal...@gmx.com> wrote:
> Ryan Popelish, thank you for reporting this and helping make Ubuntu > better. This bug was reported a while ago and there hasn't been any > activity in it recently. We were wondering if this is still an issue? > Can you try with the latest development release of Ubuntu? ISO CD images > are available from http://cdimage.ubuntu.com/releases/ . > > If it remains an issue, could you run the following command from a > Terminal (Applications->Accessories->Terminal). It will automatically > gather and attach updated debug information to this report. > > apport-collect -p linux <replace-with-bug-number> > > Also, if you could 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. > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > ** Tags added: natty needs-upstream-testing > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/776069 > > Title: > [ath9k] ZyXEL Cardbus adapter (AR5008) fails to authenticate after > upgrade to Natty (from 10.10) > > Status in “linux” package in Ubuntu: > Incomplete > > Bug description: > After upgrade to Natty (official release) ZyXEL Cardbus adapter (AR5008) > fails to authenticate. > Networkmanager just keeps re-prompting for WPA keys. > If I remove the ZyXEL adapter and insert a Cisco aironet adapter > networkmanager connects properly. > the ZyXEL adapter worked properly in 10.10. > ssid is configured for WPA2-psk (WPA1-disabled) > > NETWORK > Network controller > Atheros Communications Inc. AR5008 Wireless Network Adapter > (rev 01) > Subsystem: ZyXEL Communications Corporation NWD-170N > 802.11bgn Wireless CardBus Adapter > > from syslog: > NetworkManager[623]: <info> (wlan0): driver supports SSID scans > (scan_capa 0x01). > NetworkManager[623]: <info> (wlan0): new 802.11 WiFi device (driver: > 'ath9k' ifindex: 6) > NetworkManager[623]: <info> (wlan0): exported as > /org/freedesktop/NetworkManager/Devices/4 > NetworkManager[623]: <info> (wlan0): now managed > NetworkManager[623]: <info> (wlan0): device state change: 1 -> 2 (reason > 2) > NetworkManager[623]: <info> (wlan0): bringing up device. > NetworkManager[623]: <info> (wlan0): preparing device. > NetworkManager[623]: <info> (wlan0): deactivating device (reason: 2). > kernel: [ 1523.345781] ADDRCONF(NETDEV_UP): wlan0: link is not ready > NetworkManager[623]: SCPlugin-Ifupdown: devices added (path: > /sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.1/0000:07:00.0/net/wlan0, > iface: wlan0) > NetworkManager[623]: SCPlugin-Ifupdown: device added (path: > /sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.1/0000:07:00.0/net/wlan0, > iface: wlan0): no ifupdown configuration found. > NetworkManager[623]: <info> (wlan0): supplicant interface state: > starting -> ready > NetworkManager[623]: <info> (wlan0): device state change: 2 -> 3 (reason > 42) > wpa_supplicant[805]: Failed to initiate AP scan. > kernel: [ 1524.232559] ath: Failed to stop TX DMA in 100 msec after > killing last frame > kernel: [ 1524.232638] ath: Failed to stop TX DMA! > NetworkManager[623]: <info> Activation (wlan0) starting connection 'SSid' > NetworkManager[623]: <info> (wlan0): device state change: 3 -> 4 (reason > 0) > NetworkManager[623]: <info> Activation (wlan0) Stage 1 of 5 (Device > Prepare) scheduled... > NetworkManager[623]: <info> Activation (wlan0) Stage 1 of 5 (Device > Prepare) started... > NetworkManager[623]: <info> Activation (wlan0) Stage 2 of 5 (Device > Configure) scheduled... > NetworkManager[623]: <info> Activation (wlan0) Stage 1 of 5 (Device > Prepare) complete. > NetworkManager[623]: <info> Activation (wlan0) Stage 2 of 5 (Device > Configure) starting... > NetworkManager[623]: <info> (wlan0): device state change: 4 -> 5 (reason > 0) > NetworkManager[623]: <info> Activation (wlan0/wireless): access point > 'SSid' has security, but secrets are required. > NetworkManager[623]: <info> (wlan0): device state change: 5 -> 6 (reason > 0) > NetworkManager[623]: <info> Activation (wlan0) Stage 2 of 5 (Device > Configure) complete. > NetworkManager[623]: <info> Activation (wlan0) Stage 1 of 5 (Device > Prepare) scheduled... > NetworkManager[623]: <info> Activation (wlan0) Stage 1 of 5 (Device > Prepare) started... > NetworkManager[623]: <info> (wlan0): device state change: 6 -> 4 (reason > 0) > NetworkManager[623]: <info> Activation (wlan0) Stage 2 of 5 (Device > Configure) scheduled... > NetworkManager[623]: <info> Activation (wlan0) Stage 1 of 5 (Device > Prepare) complete. > NetworkManager[623]: <info> Activation (wlan0) Stage 2 of 5 (Device > Configure) starting... > NetworkManager[623]: <info> (wlan0): device state change: 4 -> 5 (reason > 0) > NetworkManager[623]: <info> Activation (wlan0/wireless): connection > 'SSid' has security, and secrets exist. No new secrets needed. > NetworkManager[623]: <info> Config: added 'ssid' value 'SSid' > NetworkManager[623]: <info> Config: added 'scan_ssid' value '1' > NetworkManager[623]: <info> Config: added 'key_mgmt' value 'WPA-PSK' > NetworkManager[623]: <info> Config: added 'psk' value '<omitted>' > NetworkManager[623]: nm_setting_802_1x_get_pkcs11_engine_path: assertion > `NM_IS_SETTING_802_1X (setting)' failed > NetworkManager[623]: nm_setting_802_1x_get_pkcs11_module_path: assertion > `NM_IS_SETTING_802_1X (setting)' failed > NetworkManager[623]: <info> Activation (wlan0) Stage 2 of 5 (Device > Configure) complete. > NetworkManager[623]: <info> Config: set interface ap_scan to 1 > NetworkManager[623]: <info> (wlan0): supplicant connection state: > inactive -> scanning > kernel: [ 1525.436551] ath: Failed to stop TX DMA in 100 msec after > killing last frame > kernel: [ 1525.436626] ath: Failed to stop TX DMA! > kernel: [ 1542.700558] ath: Failed to stop TX DMA in 100 msec after > killing last frame > kernel: [ 1542.700637] ath: Failed to stop TX DMA! > kernel: [ 1543.124560] ath: Failed to stop TX DMA in 100 msec after > killing last frame > kernel: [ 1543.124637] ath: Failed to stop TX DMA! > kernel: [ 1549.016560] ath: Failed to stop TX DMA in 100 msec after > killing last frame > kernel: [ 1549.016641] ath: Failed to stop TX DMA! > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/776069/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776069 Title: [ath9k] ZyXEL Cardbus adapter (AR5008) fails to authenticate after upgrade to Natty (from 10.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/776069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
