[ath9k-devel] ath9k (USB) "Target is unresponsive" - needs re-plugging to be functional

[ath9k-devel] ath9k (USB) "Target is unresponsive" - needs re-plugging to be functional

[Zbigniew]

Looking for a solution of my trouble, I've found an old thread at
http://comments.gmane.org/gmane.linux.drivers.ath9k.devel/7553 - where
exactly my problem has been described (without any solution,
unfortunately).

I'm also using TPLINK-WN722N, and the same is the problem I face:
during boot, when the device was already plugged, it doesn't become
initialized. I've got to unplug and plug it again after boot, to make
it work. Module removal - then insmod again - won't help.

The thread is old, therefore maybe there is a solution available yet?

WiFi: TP-LINK TL-WN722N, mobo K7Upgrade-600, kernel 3.7.0, Slackware 14.0
-- 
regards,
Zbigniew

[ath9k-devel] ath9k (USB) "Target is unresponsive" - needs re-plugging to be functional

[Zbigniew]

Examining the problem further, found a workaround (still no final
solution) for present situation: it turned out, that the misbehaviour
occurs always in case, when the dongle hasn't been used.

But it's enough to do at least initialization after each boot, like this:

/usr/sbin/iw wlan0 set type ibss
/usr/sbin/ip link set wlan0 up

(actually, essential is the second command, not just the first one)

...to avoid the need for replugging - during next boot the device
shall be "responsive". Maybe this can be a suggestion for developers,
what should be fixed?
-- 
regards,
Zbigniew