Modify

Opened 4 years ago

Last modified 2 years ago

#16755 new defect

ath9k_htc: Failed to initialize the device

Reported by: angelos Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: packages Version: Trunk
Keywords: ath9k_htc wbmr-hp-g300h Cc:

Description

Hi there. I have compiled my own image for the Buffalo WBMR-HP-G300H (trunk 41050), and I included the ath9k_htc kernel module, but it doesn't work. Here is the log...

Wed Jun 11 10:35:32 2014 kern.info kernel: [75345.844000] usb 1-1: new high-speed USB device number 2 using ifxusb_hcd
Wed Jun 11 10:35:33 2014 kern.info kernel: [75346.068000] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
Wed Jun 11 10:35:35 2014 kern.info kernel: [75348.792000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
Wed Jun 11 10:35:36 2014 kern.err kernel: [75349.800000] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Wed Jun 11 10:35:36 2014 kern.err kernel: [75349.804000] ath9k_htc: Failed to initialize the device
Wed Jun 11 10:35:36 2014 kern.info kernel: [75349.808000] usb 1-1: ath9k_htc: USB layer deinitialized

Any ideas?

Attachments (0)

Change History (4)

comment:1 Changed 4 years ago by anonymous

I'm experiencing the same with WRT1900ac and Alfa AWUS036NHA with Atheros Chipset AR9271

comment:2 Changed 3 years ago by DnFnD

Hi,

I've the same problem with a arcadyan arv752dpw.

The dongle wn722 works without problems under AA 12.09 but after the upgrade to BB there's some error.

dmesg:

[ 3054.416000] usb 1-1.1: USB disconnect, device number 3
[ 3054.420000] usb 1-1.1: ath9k_htc: USB layer deinitialized
[ 3059.476000] usb 1-1.1: new high-speed USB device number 5 using ifxusb_hcd
[ 3059.600000] usb 1-1.1: ath9k_htc: Firmware htc_9271.fw requested
[ 3062.228000] usb 1-1.1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[ 3063.236000] ath9k_htc 1-1.1:1.0: ath9k_htc: Target is unresponsive
[ 3063.240000] ath9k_htc: Failed to initialize the device
[ 3063.244000] usb 1-1.1: ath9k_htc: USB layer deinitialized

I found some infos and it seems that this is a arm problem. When I understand right there is a problem in the powercycle after the new firmware image was transmitted to the stick. If the stick dont get a whole powercycle after that it will stuck unresponsive.

But maybe I understood something wrong, my englisch is not the best so dont be mad at me if this infos are wrong :)

Peace

dnfnd

comment:3 Changed 2 years ago by anonymous

Same problem with TP-Link WN722N.

comment:4 Changed 2 years ago by anonymous

maybe the new usb code doesn't work as expected? see /ticket/21929.html

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.