On Sat, Nov 20, 2010 at 7:29 PM, Petr Štetiar <[email protected]> wrote: > Digged into it more, added few printks, after reboot:
Sorry for the late reply and thanks for your effort > > [ 521.710000] ath9k_hif_usb_probe > [ 521.720000] ath9k_hif_usb_dev_init > [ 521.770000] ath9k_hif_usb_download_fw - before firmware download > [ 522.210000] ath9k_hif_usb_download_fw - after firmware download > [ 522.210000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: > 51280 > [ 522.220000] ath9k_htc_probe_device > [ 522.230000] ath9k_htc_wait_for_target > [ 522.470000] ath9k_htc_rx_msg - endpoint_id: 0x1 msg_id: 0x18 > [ 523.230000] usb 1-3: ath9k_htc: Target is unresponsive It is quite clear that the problem is loading the firmware.So can you please try with the latest firmware available in http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree I am sure you would have read http://wireless.kernel.org/en/users/Drivers/ath9k_htc > [ 523.230000] Failed to initialize the device > [ 523.250000] ath9k_hif_usb: probe of 1-3:1.0 failed with error -22 > [ 523.260000] usbcore: registered new interface driver ath9k_hif_usb > > after replug: > > [ 624.610000] usb 1-3: USB disconnect, address 2 > [ 626.050000] usb 1-3: new full speed USB device using ep93xx-ohci > and address 3 > [ 626.250000] usb 1-3: New USB device found, idVendor=0cf3, > idProduct=1006 > [ 626.250000] usb 1-3: New USB device strings: Mfr=16, Product=32, > SerialNumber=48 > [ 626.270000] usb 1-3: Product: USB2.0 WLAN > [ 626.270000] usb 1-3: Manufacturer: ATHEROS > [ 626.270000] usb 1-3: SerialNumber: 12345 > [ 626.290000] ath9k_hif_usb_probe > [ 626.290000] ath9k_hif_usb_dev_init > [ 626.370000] ath9k_hif_usb_download_fw - before firmware download > [ 626.740000] ath9k_hif_usb_download_fw - after firmware download > [ 626.750000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: > 51280 > [ 626.760000] ath9k_htc_probe_device > [ 626.760000] ath9k_htc_wait_for_target > [ 627.010000] ath9k_htc_rx_msg - endpoint_id: 0x0 msg_id: 0x1 > [ 627.010000] htc_process_target_rdy > [..snip..] > > So after the reboot, it seems to me, that the device is left in some wrong > state: > > [ 522.230000] ath9k_htc_wait_for_target > [ 522.470000] ath9k_htc_rx_msg - endpoint_id: 0x1 msg_id: 0x18 > [ 523.230000] usb 1-3: ath9k_htc: Target is unresponsive > I will try to reproduce the issue. > versus correct behaviour after replug: > > [ 626.760000] ath9k_htc_wait_for_target > [ 627.010000] ath9k_htc_rx_msg - endpoint_id: 0x0 msg_id: 0x1 > [ 627.010000] htc_process_target_rdy > > Endpoint is 1 vs 0 and msg_id is 0x18 and not as expected 0x1 > (HTC_MSG_READY_ID). > I'm quite clueless what's going on there, but I hope it helps at least... > > -- ynezz > _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
