Comment 174 for bug 210725

2860 chipset on an Encore Electronics ENLWI-N PCI card.

The latest Jaunty kernel as of writing (2.6.28-9) x86 recognizes this card and seems to function semi-properly.

I cannot connect to my 802.11N AP with WPA2 security though. It can associate with the AP, but not authenticate properly. Here is some kernel log output:

Mar 16 10:57:44 dell-desktop kernel: [ 4115.044274] RTMPSetPhyMode: channel is out of range, use first channel=1
Mar 16 10:57:44 dell-desktop kernel: [ 4115.045298] MCS Set = ff ff 00 00 01
Mar 16 10:57:44 dell-desktop kernel: [ 4115.046856] <==== RTMPInitialize, Status=0
Mar 16 10:57:44 dell-desktop kernel: [ 4115.046919] 0x1300 = 00064300
Mar 16 10:57:49 dell-desktop kernel: [ 4120.066100] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 244
Mar 16 10:57:55 dell-desktop kernel: [ 4125.724012] ra0: no IPv6 routers present
Mar 16 10:58:10 dell-desktop kernel: [ 4140.081219] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 244
Mar 16 10:58:10 dell-desktop kernel: [ 4140.081520] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)
Mar 16 10:58:25 dell-desktop kernel: [ 4155.097085] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 244
Mar 16 10:58:25 dell-desktop kernel: [ 4155.097354] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)

And some entries from the daemon log:

Mar 16 11:11:16 dell-desktop NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Mar 16 11:11:16 dell-desktop NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Mar 16 11:11:16 dell-desktop NetworkManager: <info> Activation (ra0) Stage 2 of 5 (Device Configure) complete.
Mar 16 11:11:16 dell-desktop NetworkManager: <info> Config: set interface ap_scan to 1
Mar 16 11:11:16 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: disconnected -> scanning
Mar 16 11:11:21 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: scanning -> associating
Mar 16 11:11:31 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: associating -> disconnected
Mar 16 11:11:31 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: disconnected -> scanning
Mar 16 11:11:36 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: scanning -> associating
Mar 16 11:11:46 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: associating -> disconnected
Mar 16 11:11:46 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: disconnected -> scanning
Mar 16 11:11:47 dell-desktop NetworkManager: <info> ra0: link timed out.
Mar 16 11:11:51 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: scanning -> associating
Mar 16 11:12:01 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: associating -> disconnected
Mar 16 11:12:01 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: disconnected -> scanning
Mar 16 11:12:06 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: scanning -> associating
Mar 16 11:12:16 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: associating -> disconnected
Mar 16 11:12:16 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: disconnected -> scanning
Mar 16 11:12:17 dell-desktop NetworkManager: <info> Activation (ra0/wireless): association took too long.
Mar 16 11:12:17 dell-desktop NetworkManager: <info> (ra0): device state change: 5 -> 6
Mar 16 11:12:17 dell-desktop NetworkManager: <info> Activation (ra0/wireless): asking for new secrets
Mar 16 11:12:17 dell-desktop NetworkManager: <info> (ra0): supplicant connection state: scanning -> disconnected