Hi all,
A while back, I posted to the list looking for an AR7010+AR9280 USB
802.11n device that I could hopefully use with ath9k:
http://comments.gmane.org/gmane.linux.kernel.wireless.general/67252
One adapter that came up was the Xbox 360 802.11n adapter, which has
this chipset solution:
http://www.wikidevi.com/wiki/Microsoft_Xbox_360_Wireless_N_Networking_Adapter
I purchased one of the Xbox 360 802.11n adapters, and would now like
to get it working with ath9k_htc, but having some issues.
First, I added support for the USB device. I edited
./drivers/net/wireless/ath/ath9k/hif_usb.c ... and added this to
static struct usb_device_id ath9k_hif_usb_ids[]:
{ USB_DEVICE(0x045e, 0x02a8),
.driver_info = AR9280_USB }, /* Microsoft Wireless N */
After that, I rebuilt and got the module up and running. However,
when I plug in the device, I get the following errors:
After installing the new driver and plugging in the device, this is
the error I get:
[ 4599.236871] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 72996
[ 4600.237494] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
[ 4600.237494] Failed to initialize the device
[ 4600.240386] ath9k_htc: probe of 1-1:1.0 failed with error -22
[ 4600.248782] usbcore: registered new interface driver ath9k_htc
The light on the Xbox adapter goes solid, which makes me believe part
of the firmware was written to the device.
Has anyone had any experience with getting the Xbox 802.11n adapter to
work with compat-wireless? If not, does anyone have any suggestions
or direction I should go in?
Thanks!
George
Great, thanks Sujith! Are we positive that the Xbox adapter is also
not UB94 now that we have seen both of these with this problem? I am
not sure if this was speculation after seeing the initial error, or if
it is a known fact.
On Tue, May 10, 2011 at 12:13 PM, Sujith <[email protected]> wrote:
> George Nychis wrote:
>> > Hm, looks like 0x0411 doesn't match. Can you try this FW ?
>> >
>> >
>>
>> [ ?393.053564] usb 1-1: new high speed USB device using ehci_hcd and address 5
>> [ ?393.525139] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 73008
>> [ ?394.525196] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>> [ ?394.525335] Failed to initialize the device
>> [ ?394.548205] ath9k_htc: probe of 1-1:1.0 failed with error -22
>
> Well, looks like my FW hack didn't work out. I will be getting a UWA-BR100,
> so I'll play around with it and we'll see where it goes. :)
>
> Sujith
>
On Tue, May 10, 2011 at 2:24 AM, Sujith <[email protected]> wrote:
> Sujith wrote:
>> Sujith wrote:
>> > George Nychis wrote:
>> > > Is there anything more I can do to help here? I've tried older versions of
>> > > compat wireless with older firmware and I am having 0 luck.
>> >
>> > Nope, nothing from your side. I have asked internally if the card could
>> > be used by the HTC drivers without any changes, will update once I get an answer.
>>
>> Can you try the attached firmware ?
>
> Bleh, had a bunch of local changes.
> Can you try this instead ?
>
>
Yep, seems like the same error:
[ 206.642427] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 73008
[ 207.648520] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
[ 207.648549] Failed to initialize the device
[ 207.652281] ath9k_htc: probe of 1-1:1.0 failed with error -22
[ 207.656271] usbcore: registered new interface driver ath9k_htc
Thanks for trying to help
On Sun, May 1, 2011 at 1:23 AM, George Nychis <[email protected]> wrote:
> Has anyone had any experience with getting the Xbox 802.11n adapter to
> work with compat-wireless? ?If not, does anyone have any suggestions
> or direction I should go in?
>
> Thanks!
> George
>
I get a bit different output testing with a genuine Xbox360 adapter
and a Datel clone:
[ 1672.480528] usb 1-1: new high speed USB device using ehci_hcd and address 26
[ 1673.124132] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 73008
[ 1673.221623] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 48 credits
[ 1673.260411] ath: Invalid EEPROM Magic. Endianness mismatch.
[ 1673.260442] ath: Unable to initialize hardware; initialization status: -22
[ 1673.260470] ath: Unable to initialize hardware; initialization status: -22
[ 1673.260503] Failed to initialize the device
[ 1673.270156] ath9k_htc: probe of 1-1:1.0 failed with error -22
The USB connection with the genuine Xbox360 adapter also seems to be
rather finicky.
-mark
Has anyone tried either of these with ath9k_htc:
Sony UWA-BR100
TiVo AN0100
I'm curious if anyone has had success with them, and if they are UB94
based. It'd be great to know.
Sujith wrote:
> Sujith wrote:
> > George Nychis wrote:
> > > Is there anything more I can do to help here? I've tried older versions of
> > > compat wireless with older firmware and I am having 0 luck.
> >
> > Nope, nothing from your side. I have asked internally if the card could
> > be used by the HTC drivers without any changes, will update once I get an answer.
>
> Can you try the attached firmware ?
Bleh, had a bunch of local changes.
Can you try this instead ?
I finally have this working with compat-wireless-2011-05-13 on a third
machine, with v1.2 of the hardware. A little bit of weirdness in the
device name though:
wlan%d IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
"wlan%d" ... seems like a bug trying to insert the number in to the string.
Thank goodness this works... the difference between the machines? I'm
not sure yet. This is good news though.
Although the xbox 360 adapter is not UB94, I will still try it on this
machine tomorrow to see if it initializes or anything.
Is there anything more I can do to help here? I've tried older versions of
compat wireless with older firmware and I am having 0 luck.
On Fri, May 6, 2011 at 2:22 PM, George Nychis <[email protected]> wrote:
> BTW- same error with fw1.0, fw1.1, and fw1.2
>
Tried on a second machine with no luck still... could he get me his
exact build and firmware?
On Wed, May 11, 2011 at 11:33 AM, George Nychis <[email protected]> wrote:
> BTW - was this with your updated firmwares you sent me, or with the
> standard 1.2 firmware?
>
>
> On Wed, May 11, 2011 at 11:22 AM, George Nychis <[email protected]> wrote:
>> On Wed, May 11, 2011 at 11:14 AM, Sujith <[email protected]> wrote:
>>> George Nychis wrote:
>>>> Great, thanks Sujith! ?Are we positive that the Xbox adapter is also
>>>> not UB94 now that we have seen both of these with this problem? ?I am
>>>> not sure if this was speculation after seeing the initial error, or if
>>>> it is a known fact.
>>>
>>> Yes, the Xbox adapter is not based on UB94.
>>>
>>> And apparently no changes are required to use UWA-BR100, as an internal
>>> engineer was able to use ath9k_htc as is, after adding the PID/VID
>>> to the driver. So maybe the card that you have bought is different
>>> from the UWA-BR100 sample that he used. Will poke some more people and
>>> see if we're missing something.
>>>
>>
>> Maybe if we can compare lsusb of both devices to ensure that they are
>> actually the same.
>>
>> Could you have him read what the FCC ID is on the back of the stick?
>> My details are:
>>
>> IC: 409B-UWABR100
>> FCC ID: AK8UWABR100
>> ANATEL: 0010-10-4749
>>
>
George Nychis wrote:
> I decided to get the Sony BR100 and try it out, given that the
> WikiDevi page for the device seems to suggest that it works with
> ath9k_htc:
> http://www.wikidevi.com/wiki/Sony_UWA-BR100
>
> My confidence is also a little higher given that someone has it
> working in Windows, also.
>
> But, using the most recent firmware and compat-wireless, I get the
> same exact error that I did with the Xbox adapter:
> [ 1277.228258] usb 2-2: ath9k_htc: Transferred FW: htc_7010.fw, size: 72996
> [ 1278.228930] ath9k_htc 2-2:1.0: ath9k_htc: Target is unresponsive
> [ 1278.229788] Failed to initialize the device
> [ 1279.029952] ath9k_htc: probe of 2-2:1.0 failed with error -22
>
> The WikiDev page mentions that it worked as of Jan. 8, 2011. So I
> rolled back compat-wireless to that date and grabbed the old firmware
> from the old tree.
>
> Unfortunately, I still get the same error:
> [ 386.398366] usb 1-1: USB disconnect, address 4
> [ 388.412466] usb 1-1: new high speed USB device using ehci_hcd and address 5
> [ 389.113687] usb 1-1: ath9k_htc: Transferred FW: ar7010_1_1.fw, size: 70624
> [ 390.112282] usb 1-1: ath9k_htc: Target is unresponsive
> [ 390.112308] Failed to initialize the device
> [ 390.113658] ath9k_hif_usb: probe of 1-1:1.0 failed with error -22
>
> So, either this person had some form of magic, or I am missing
> something... I'd be curious to try it in Windows. BTW, it shows up in
> Mac OSX as "Buffalo" ...
>
> (CEWL 1):
>
> Product ID: 0x017f
> Vendor ID: 0x0411 (BUFFALO INC.)
> Version: 2.02
> Serial Number: 12345
> Speed: Up to 480 Mb/sec
> Manufacturer: BUFFALO
> Location ID: 0xfd100000
> Current Available (mA): 500
> Current Required (mA): Unknown (Device has not been configured)
This is UB94 based, so it should work with ath9k_htc.
Can you post the output of lsusb -v ?
Sujith
> This is ?UB94 based, so it should work with ath9k_htc.
> Can you post the output of lsusb -v ?
>
Sure:
Bus 001 Device 002: ID 0411:017f MelCo., Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0411 MelCo., Inc.
idProduct 0x017f
bcdDevice 2.02
iManufacturer 16 BUFFALO
iProduct 32 (CEWL 1)
iSerial 48 12345
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 60
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Sujith wrote:
> George Nychis wrote:
> > Is there anything more I can do to help here? I've tried older versions of
> > compat wireless with older firmware and I am having 0 luck.
>
> Nope, nothing from your side. I have asked internally if the card could
> be used by the HTC drivers without any changes, will update once I get an answer.
Can you try the attached firmware ?
Hi Sujith and Mark,
Thanks for the responses!
I can definitely help with any sort of debugging of new firmware for
the device. I thought it was UB94 based, but I guess not :)
Any firmware changes you make, I will definitely test. I did some
digging around about the firmware, but it appears the firmware is
closed-source. So, I'm not sure I can help out with any of the actual
coding/modifications to it. You must be on the Atheros-in, whereas I
am on the Atheros-out ;)
Is there something I can get to you initially to be of some help? Any
usbmon output or some state from the device?
- George
Sorry, missed a 5 at the end of the panasonic model: N5HBZ0000055
On Tue, May 3, 2011 at 9:30 AM, George Nychis <[email protected]> wrote:
>> Thanks, but unfortunately, the only option is for someone to port all
>> the HW support to htc_7010.fw. And I don't know if and when it would be done.
>>
>
> Your last e-mail sounded a little more hopeful, this e-mail makes it
> sound like I should jump ship on this hardware and track down another
> AR7010+AR9280 solution...
>
> It seems like the combo in production with UB94 is still not widely
> available. ?The Panasonic N5HBZ000005 is the only UB94 that seems is
> semi-available in the US. ?Maybe I'll jump back to AR9271+AR7010.
>
> - George
>
> Nice. :)
>
> What machine/distro did you use in which the card worked ?
>
> Sujith
>
yep yep, it's an x86 with Ubuntu 10.4 on it.
I tried the xbox adapter, and now I get the same error as Mark:
[333693.330144] usb 2-3: ath9k_htc: Transferred FW: htc_7010.fw, size: 73008
[333693.426523] ath9k_htc 2-3:1.0: ath9k_htc: HTC initialized with 48 credits
[333693.461026] ath: Invalid EEPROM Magic. Endianness mismatch.
[333693.461032] ath: Unable to initialize hardware; initialization status: -22
[333693.461036] ath: Unable to initialize hardware; initialization status: -22
[333693.461043] Failed to initialize the device
[333693.470044] ath9k_htc: probe of 2-3:1.0 failed with error -22
But, I'll move on with the Sony adapter for now. If you ever want to
try any different firmware for the Xbox adapter, just let me know!
George Nychis wrote:
> I finally have this working with compat-wireless-2011-05-13 on a third
> machine, with v1.2 of the hardware. A little bit of weirdness in the
> device name though:
>
> wlan%d IEEE 802.11abgn ESSID:off/any
> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Power Management:off
>
> "wlan%d" ... seems like a bug trying to insert the number in to the string.
>
> Thank goodness this works... the difference between the machines? I'm
> not sure yet. This is good news though.
>
> Although the xbox 360 adapter is not UB94, I will still try it on this
> machine tomorrow to see if it initializes or anything.
Nice. :)
What machine/distro did you use in which the card worked ?
Sujith
BTW- same error with fw1.0, fw1.1, and fw1.2
George Nychis wrote:
> On Tue, May 10, 2011 at 2:24 AM, Sujith <[email protected]> wrote:
> > Sujith wrote:
> >> Sujith wrote:
> >> > George Nychis wrote:
> >> > > Is there anything more I can do to help here? I've tried older versions of
> >> > > compat wireless with older firmware and I am having 0 luck.
> >> >
> >> > Nope, nothing from your side. I have asked internally if the card could
> >> > be used by the HTC drivers without any changes, will update once I get an answer.
> >>
> >> Can you try the attached firmware ?
> >
> > Bleh, had a bunch of local changes.
> > Can you try this instead ?
> >
> >
>
> Yep, seems like the same error:
>
> [ 206.642427] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 73008
> [ 207.648520] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
> [ 207.648549] Failed to initialize the device
> [ 207.652281] ath9k_htc: probe of 1-1:1.0 failed with error -22
> [ 207.656271] usbcore: registered new interface driver ath9k_htc
Hm, looks like 0x0411 doesn't match. Can you try this FW ?
> Hm, looks like 0x0411 doesn't match. Can you try this FW ?
>
>
[ 393.053564] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 393.525139] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 73008
[ 394.525196] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
[ 394.525335] Failed to initialize the device
[ 394.548205] ath9k_htc: probe of 1-1:1.0 failed with error -22
BTW - was this with your updated firmwares you sent me, or with the
standard 1.2 firmware?
On Wed, May 11, 2011 at 11:22 AM, George Nychis <[email protected]> wrote:
> On Wed, May 11, 2011 at 11:14 AM, Sujith <[email protected]> wrote:
>> George Nychis wrote:
>>> Great, thanks Sujith! ?Are we positive that the Xbox adapter is also
>>> not UB94 now that we have seen both of these with this problem? ?I am
>>> not sure if this was speculation after seeing the initial error, or if
>>> it is a known fact.
>>
>> Yes, the Xbox adapter is not based on UB94.
>>
>> And apparently no changes are required to use UWA-BR100, as an internal
>> engineer was able to use ath9k_htc as is, after adding the PID/VID
>> to the driver. So maybe the card that you have bought is different
>> from the UWA-BR100 sample that he used. Will poke some more people and
>> see if we're missing something.
>>
>
> Maybe if we can compare lsusb of both devices to ensure that they are
> actually the same.
>
> Could you have him read what the FCC ID is on the back of the stick?
> My details are:
>
> IC: 409B-UWABR100
> FCC ID: AK8UWABR100
> ANATEL: 0010-10-4749
>
> Thanks, but unfortunately, the only option is for someone to port all
> the HW support to htc_7010.fw. And I don't know if and when it would be done.
>
Your last e-mail sounded a little more hopeful, this e-mail makes it
sound like I should jump ship on this hardware and track down another
AR7010+AR9280 solution...
It seems like the combo in production with UB94 is still not widely
available. The Panasonic N5HBZ000005 is the only UB94 that seems is
semi-available in the US. Maybe I'll jump back to AR9271+AR7010.
- George
George Nychis wrote:
> Is there anything more I can do to help here? I've tried older versions of
> compat wireless with older firmware and I am having 0 luck.
Nope, nothing from your side. I have asked internally if the card could
be used by the HTC drivers without any changes, will update once I get an answer.
Sujith
> Has anyone had any experience with getting the Xbox 802.11n adapter to
> work with compat-wireless? ?If not, does anyone have any suggestions
> or direction I should go in?
BTW - this is with compat-wireless-2011-04-29, and firmware 1.2:
http://wireless.kernel.org/download/htc_fw/1.2/
George Nychis wrote:
> > Hm, looks like 0x0411 doesn't match. Can you try this FW ?
> >
> >
>
> [ 393.053564] usb 1-1: new high speed USB device using ehci_hcd and address 5
> [ 393.525139] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 73008
> [ 394.525196] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
> [ 394.525335] Failed to initialize the device
> [ 394.548205] ath9k_htc: probe of 1-1:1.0 failed with error -22
Well, looks like my FW hack didn't work out. I will be getting a UWA-BR100,
so I'll play around with it and we'll see where it goes. :)
Sujith
George Nychis wrote:
> Great, thanks Sujith! Are we positive that the Xbox adapter is also
> not UB94 now that we have seen both of these with this problem? I am
> not sure if this was speculation after seeing the initial error, or if
> it is a known fact.
Yes, the Xbox adapter is not based on UB94.
And apparently no changes are required to use UWA-BR100, as an internal
engineer was able to use ath9k_htc as is, after adding the PID/VID
to the driver. So maybe the card that you have bought is different
from the UWA-BR100 sample that he used. Will poke some more people and
see if we're missing something.
Sujith
George Nychis wrote:
> Hi all,
>
> A while back, I posted to the list looking for an AR7010+AR9280 USB
> 802.11n device that I could hopefully use with ath9k:
> http://comments.gmane.org/gmane.linux.kernel.wireless.general/67252
>
> One adapter that came up was the Xbox 360 802.11n adapter, which has
> this chipset solution:
> http://www.wikidevi.com/wiki/Microsoft_Xbox_360_Wireless_N_Networking_Adapter
>
> I purchased one of the Xbox 360 802.11n adapters, and would now like
> to get it working with ath9k_htc, but having some issues.
>
> First, I added support for the USB device. I edited
> ./drivers/net/wireless/ath/ath9k/hif_usb.c ... and added this to
> static struct usb_device_id ath9k_hif_usb_ids[]:
>
> { USB_DEVICE(0x045e, 0x02a8),
> .driver_info = AR9280_USB }, /* Microsoft Wireless N */
>
> After that, I rebuilt and got the module up and running. However,
> when I plug in the device, I get the following errors:
> After installing the new driver and plugging in the device, this is
> the error I get:
> [ 4599.236871] usb 1-1: ath9k_htc: Transferred FW: htc_7010.fw, size: 72996
> [ 4600.237494] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
> [ 4600.237494] Failed to initialize the device
> [ 4600.240386] ath9k_htc: probe of 1-1:1.0 failed with error -22
> [ 4600.248782] usbcore: registered new interface driver ath9k_htc
>
> The light on the Xbox adapter goes solid, which makes me believe part
> of the firmware was written to the device.
>
> Has anyone had any experience with getting the Xbox 802.11n adapter to
> work with compat-wireless? If not, does anyone have any suggestions
> or direction I should go in?
Bad luck. :(
AR9280+AR7010 USB dongles are based on UB94, the Xbox adapter is not, it's
based on a different reference design, so it is not surprising that ath9k_htc
fails to bring up the card.
Looks like a different firmware is required for the Xbox 360 adapter.
I am not sure how different the fw is from htc_7010, so it is hard to say
how much work has to be done to port the required changes to htc_7010.fw.
I don't have the adapter with me, so any fw change has to be tested by you. :)
Sujith
On Wed, May 11, 2011 at 11:14 AM, Sujith <[email protected]> wrote:
> George Nychis wrote:
>> Great, thanks Sujith! ?Are we positive that the Xbox adapter is also
>> not UB94 now that we have seen both of these with this problem? ?I am
>> not sure if this was speculation after seeing the initial error, or if
>> it is a known fact.
>
> Yes, the Xbox adapter is not based on UB94.
>
> And apparently no changes are required to use UWA-BR100, as an internal
> engineer was able to use ath9k_htc as is, after adding the PID/VID
> to the driver. So maybe the card that you have bought is different
> from the UWA-BR100 sample that he used. Will poke some more people and
> see if we're missing something.
>
Maybe if we can compare lsusb of both devices to ensure that they are
actually the same.
Could you have him read what the FCC ID is on the back of the stick?
My details are:
IC: 409B-UWABR100
FCC ID: AK8UWABR100
ANATEL: 0010-10-4749
I decided to get the Sony BR100 and try it out, given that the
WikiDevi page for the device seems to suggest that it works with
ath9k_htc:
http://www.wikidevi.com/wiki/Sony_UWA-BR100
My confidence is also a little higher given that someone has it
working in Windows, also.
But, using the most recent firmware and compat-wireless, I get the
same exact error that I did with the Xbox adapter:
[ 1277.228258] usb 2-2: ath9k_htc: Transferred FW: htc_7010.fw, size: 72996
[ 1278.228930] ath9k_htc 2-2:1.0: ath9k_htc: Target is unresponsive
[ 1278.229788] Failed to initialize the device
[ 1279.029952] ath9k_htc: probe of 2-2:1.0 failed with error -22
The WikiDev page mentions that it worked as of Jan. 8, 2011. So I
rolled back compat-wireless to that date and grabbed the old firmware
from the old tree.
Unfortunately, I still get the same error:
[ 386.398366] usb 1-1: USB disconnect, address 4
[ 388.412466] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 389.113687] usb 1-1: ath9k_htc: Transferred FW: ar7010_1_1.fw, size: 70624
[ 390.112282] usb 1-1: ath9k_htc: Target is unresponsive
[ 390.112308] Failed to initialize the device
[ 390.113658] ath9k_hif_usb: probe of 1-1:1.0 failed with error -22
So, either this person had some form of magic, or I am missing
something... I'd be curious to try it in Windows. BTW, it shows up in
Mac OSX as "Buffalo" ...
(CEWL 1):
Product ID: 0x017f
Vendor ID: 0x0411 (BUFFALO INC.)
Version: 2.02
Serial Number: 12345
Speed: Up to 480 Mb/sec
Manufacturer: BUFFALO
Location ID: 0xfd100000
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)
On Tue, May 3, 2011 at 2:39 PM, George Nychis <[email protected]> wrote:
> Has anyone tried either of these with ath9k_htc:
> Sony UWA-BR100
> TiVo AN0100
>
> I'm curious if anyone has had success with them, and if they are UB94
> based. ?It'd be great to know.
>