Module Carl9170, firmware won't load properly

Module Carl9170, firmware won't load properly

[Alex Alouit]

Hello, 

I want to use an Netgear WN111v2 (AR9170 usb wireless) with Vyatta 6.4, 
I copied the firmware (http://linuxwireless.org/en/users/Drivers/carl9170), 
(carl9170-1.fw in /usr/local/lib/firmware version 1.9.2 (kernel 3.0.23)) 
but it seems that the module doesn't load correctly the firmware. 


dmesg output: 
Code:

usb 1-1: new high speed USB device number 2 using ehci_hcd 
usb 1-1: New USB device found, idVendor=0846, idProduct=9001 
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48 
usb 1-1: Product: USB2.0 WLAN 
usb 1-1: Manufacturer: ATHER 
usb 1-1: SerialNumber: 12345 
usb 1-1: reset high speed USB device number 2 using ehci_hcd 
usbcore: registered new interface driver carl9170 
usb 1-1: driver   API: 1.9.2 2011-01-22 [1-1] 
usb 1-1: firmware API: 1.9.2 2010-12-25 
usb 1-1: firmware upload failed (-110). 


It's the module or firmware that is buggy? How can I fix this?

Excuse my English, is not my native language. 


Best regards

Re: Module Carl9170, firmware won't load properly

[Christian Lamparter]

On Thursday, May 17, 2012 01:19:56 AM Alex Alouit wrote:
> Hello, 
> 
> I want to use an Netgear WN111v2 (AR9170 usb wireless) with Vyatta 6.4, 
> I copied the firmware (http://linuxwireless.org/en/users/Drivers/carl9170), 
> (carl9170-1.fw in /usr/local/lib/firmware version 1.9.2 (kernel 3.0.23)) 
> but it seems that the module doesn't load correctly the firmware. 
that's pretty old. you can go with compat-wireless and a more recent firmware.
> 
> usb 1-1: new high speed USB device number 2 using ehci_hcd 
> usb 1-1: New USB device found, idVendor=0846, idProduct=9001 
> usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48 
> usb 1-1: Product: USB2.0 WLAN 
> usb 1-1: Manufacturer: ATHER 
> usb 1-1: SerialNumber: 12345 
> usb 1-1: reset high speed USB device number 2 using ehci_hcd 
> usbcore: registered new interface driver carl9170 
> usb 1-1: driver   API: 1.9.2 2011-01-22 [1-1] 
> usb 1-1: firmware API: 1.9.2 2010-12-25 
> usb 1-1: firmware upload failed (-110). 
> 
> It's the module or firmware that is buggy? How can I fix this?

-110 is -ETIMEDOUT (The driver hasn't received the "fw booted" event and the
upload timed out). This can be caused by a faulty module, firmware, linux's
usb subsystem, (Virtual Machine, if you run Vyatta in one) and/or hardware.

Regards,
	Christian

Re: Module Carl9170, firmware won't load properly

[Alex Alouit]

Christian Lamparter <chunkeey@...> writes:


> > (carl9170-1.fw in /usr/local/lib/firmware version 1.9.2 (kernel 3.0.23)) 
> > but it seems that the module doesn't load correctly the firmware. 
> that's pretty old. you can go with compat-wireless and a more recent firmware.


Same things with Debian Wheezy (kernel 3.2.0-2-amd64) 
with firmware 1.9.4 and 1.9.5.
They are more recent.

[57471.355695] usb 1-1: driver   API: 1.9.4 2011-08-15 [1-1]
[57471.355707] usb 1-1: firmware API: 1.9.5 2012-03-14
[57471.456617] usb 1-1: firmware upload failed (-110)

What do you think I should do?

Re: Module Carl9170, firmware won't load properly

[Christian Lamparter]

On Friday 18 May 2012 17:41:41 Alex Alouit wrote:
> Christian Lamparter <chunkeey@...> writes:
> > > (carl9170-1.fw in /usr/local/lib/firmware version 1.9.2 (kernel 3.0.23)) 
> > > but it seems that the module doesn't load correctly the firmware. 
> > that's pretty old. you can go with compat-wireless and a more recent firmware.
>
> Same things with Debian Wheezy (kernel 3.2.0-2-amd64) 
> with firmware 1.9.4 and 1.9.5.
> They are more recent.
> 
> [57471.355695] usb 1-1: driver   API: 1.9.4 2011-08-15 [1-1]
> [57471.355707] usb 1-1: firmware API: 1.9.5 2012-03-14
> [57471.456617] usb 1-1: firmware upload failed (-110)
> 
> What do you think I should do?
Depends on what are you doing. From the "-110" consistency
it sounds like you are trying to get the device working 
within a VM (mere USB emulation is known not to work,
if you want to use it in a VM you need a dedicated ehci
for that)

If that's not the case, you could check what's going on
on the usb protocol level. For Linux the easiest way
is probably to load the "usbmon" module and monitor the
traffic between the device and the driver.
(If you don't want to deal with the usb log yourself,
you can capture the data and sent the email to me
(without cc'ing the ML).)

Reagards,
	Christian