linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Alex Alouit <alexandre.alouit@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Module Carl9170, firmware won't load properly
Date: Thu, 17 May 2012 12:07:40 +0200	[thread overview]
Message-ID: <201205171207.40795.chunkeey@googlemail.com> (raw)
In-Reply-To: <loom.20120517T011514-623@post.gmane.org>

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

  reply	other threads:[~2012-05-17 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 23:19 Module Carl9170, firmware won't load properly Alex Alouit
2012-05-17 10:07 ` Christian Lamparter [this message]
2012-05-18 15:41   ` Alex Alouit
2012-05-18 16:42     ` Christian Lamparter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201205171207.40795.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=alexandre.alouit@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).