Hi list! On an old system with only USB 1.1, I tried to use a USB-dongle: NETGEAR WG111v2. The device works perfectly with same kernel (2.6.26-1 from debian lenny) on a new system with USB 2.0, using the "rtl8187" driver. However, on USB 1.1 I get: Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: Initial auth_alg=0 Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: authenticate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:17 jonspc kernel: [13991.380267] wlan1: authenticated Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:17 jonspc kernel: [13991.604259] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: Initial auth_alg=0 Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: authenticate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:18 jonspc kernel: [13992.136073] wlan1: association frame received from 00:1b:2f:0c:2f:28, but not in associate state - ignoredel: [13992.340113] wlan1: authenticate with AP 00:1b:2f:0c:2f:28 [Longer part of syslog follows later in this post] I tried to use the device on two USB 1.1 systems, both failed with the "association frame received ... but not in associate state - ignore", message. Is USB 2.0 required, or is there a workaround for this problem? Here is the output of lsusb: Bus 001 Device 066: ID 0846:6a00 NetGear, Inc. WG111v2 54 Mbps Wireless [RealTek RTL8187L] Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Below is a longer exerpt from syslog: no key needed. jonspc NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan1#011#011wext#011/var/run/wpa_supplicant#011'spc NetworkManager: <info> SUP: response was 'OK' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was '0' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 48656c676573' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK' Jan 17 17:25:01 jonspc kernel: [13975.564161] wlan1: authenticate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:01 jonspc kernel: [13975.564194] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:01 jonspc kernel: [13975.564194] wlan1: authenticated Jan 17 17:25:01 jonspc kernel: [13975.564194] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:02 jonspc kernel: [13975.788114] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:02 jonspc kernel: [13975.988110] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:02 jonspc kernel: [13976.188137] wlan1: association with AP 00:1b:2f:0c:2f:28 timed out Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: Initial auth_alg=0 Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: authenticate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:17 jonspc kernel: [13991.380267] wlan1: authenticated Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:17 jonspc kernel: [13991.604259] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: Initial auth_alg=0 Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: authenticate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:18 jonspc kernel: [13992.136073] wlan1: association frame received from 00:1b:2f:0c:2f:28, but not in associate state - ignoredel: [13992.340113] wlan1: authenticate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:18 jonspc kernel: [13992.343090] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:18 jonspc kernel: [13992.343116] wlan1: authenticated Jan 17 17:25:18 jonspc kernel: [13992.343126] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:18 jonspc kernel: [13992.343116] wlan1: authenticated Jan 17 17:25:18 jonspc kernel: [13992.343126] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:18 jonspc kernel: [13992.540122] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:19 jonspc kernel: [13992.740140] wlan1: associate with AP 00:1b:2f:0c:2f:28 Jan 17 17:25:19 jonspc kernel: [13992.940143] wlan1: association with AP 00:1b:2f:0c:2f:28 timed out -- Hans Ekbrand (http://sociologi.cjb.net) <hans@xxxxxxxxxxxxxxxxx> Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you.
Attachment:
signature.asc
Description: Digital signature
