>>>>> "Larry" == Larry Finger <Larry.Finger@xxxxxxxxxxxx> writes: Larry> On 06/17/2011 06:15 AM, peter@xxxxxxxxxxxxxxxxxx wrote: >> >> Hi. I'm trying out the rtl8192CU driver with an edimax wireless N >> dongle. The driver loads correctly, and wpa_supplicant can trigger >> an association with an access point, using WPA2/PEAP. I'm using >> the tip of Linus's kernel tree (3.0.0-rc2) >> >> But the interface then does nothing: it doesn't pick up an ipv6 >> address from radvd broadcasts, nor does it appear to send any dhcp >> requests, even though the TX packet counter increases. >> >> >> Do you have any ideas about how I could debug this? Larry> You should inspect the output from dmesg to see if anything is Larry> reported. In addition, use wireshark to see what is on the air. Nothing in dmesg, apart from the usual: Jun 20 09:30:41 localhost kernel: rtl8192cu: MAC address: 00:e0:4c:04:91:9c Jun 20 09:30:41 localhost kernel: rtl8192cu: Board Type 0 Jun 20 09:30:41 localhost kernel: rtl8192cu: rx_max_size 15360, rx_urb_num 8, in_ep 1 Jun 20 09:30:41 localhost kernel: ieee80211 phy1: Selected rate control algorithm 'rtl_rc' Jun 20 09:30:41 localhost kernel: usbcore: registered new interface driver rtl8192cu Jun 20 09:33:10 localhost kernel: rtl8192cu: MAC auto ON okay! Jun 20 09:33:10 localhost kernel: rtl8192cu: Tx queue select: 0x05 Jun 20 09:33:10 localhost kernel: rtl8192c: Loading firmware file rtlwifi/rtl8192cufw.bin Jun 20 09:33:11 localhost kernel: rtl8192c_common:_rtl92c_fw_free_to_go():<0-0> Polling FW ready fail!! REG_MCUFWDL:0x00000006 . Jun 20 09:33:11 localhost kernel: rtl8192c_common:rtl92c_download_fw():<0-0> Firmware is not ready to run! Jun 20 09:33:11 localhost kernel: ADDRCONF(NETDEV_UP): wlan2: link is not ready Jun 20 09:33:12 localhost kernel: wlan2: authenticate with 00:22:6b:73:a9:fa (try 1) Jun 20 09:33:12 localhost kernel: wlan2: authenticated Jun 20 09:33:12 localhost kernel: wlan2: associate with 00:22:6b:73:a9:fa (try 1 Jun 20 09:33:12 localhost kernel: wlan2: RX AssocResp from 00:22:6b:73:a9:fa (capab=0x411 status=0 aid=6) Jun 20 09:33:12 localhost kernel: wlan2: associated Jun 20 09:33:12 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready Jun 20 09:33:23 localhost kernel: wlan2: no IPv6 routers present Wireshark on the host which has the dongle inserted shows the key exchange, then the DHCP broadcast and a few mdns broadcasts using the ipv6 link-local address, then nothing. On an adjacent host, I see the key exchange, then nothing. It's as if the dongle shuts itself down after a few seconds. To test this, I let machine and dongle get cold, then booted with the dongle inserted. It managed to get an ipv6 address, but not an ipv4 address; and the monitoring host saw the dhcp send and reply, but the dongle did not see the reply. I tried recompiling with DBG_TRACE: I see many many calls to rtl8192c_common:rtl92c_dm_check_txpower_tracking_thermal_meter():<0-0> Trigger 92S Thermal Meter!! and rtl8192c_common:rtl92c_dm_txpower_tracking_callback_thermalmeter():<0-0> Initial reg0xa24 = 0x90e1317, cck_index=0xc, ch14 0 rtl8192c_common:rtl92c_dm_txpower_tracking_cal lback_thermalmeter():<0-0> Readback Thermal Meter = 0x13 pre thermal meter 0x11 eeprom_thermalmeter 0x11 delta 0x2 delta_lck 0x1 delta_iqk 0x1 Could there be something wrong with the auto-power adjustment in response to temperature measurements? The dongle does get quite warm to touch. Larry> What kind of connection is being tried? I'm still trying to get the device to get and keep an IP address so any kind of connexion can be tried on top. Peter C -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
