mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manuel Estrada Sainz <ranty@debian.org>
To: Greg KH <greg@kroah.com>
Cc: Joshua Kwan <joshk@triplehelix.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: orinoco USB driver
Date: Mon, 7 Jul 2003 20:32:11 +0200	[thread overview]
Message-ID: <20030707183211.GA31222@ranty.pantax.net> (raw)
In-Reply-To: <20030707055042.GA25011@kroah.com>

On Sun, Jul 06, 2003 at 10:50:42PM -0700, Greg KH wrote:
> On Mon, Jul 07, 2003 at 12:53:25AM +0200, Manuel Estrada Sainz wrote:
> > On Sat, Jul 05, 2003 at 05:16:01PM -0700, Joshua Kwan wrote:
> > > I'm currently trying to get my Avaya Wireless 'Silver' USB device to
> > > work with the orinoco_usb driver v0.2.1.
> > > 
> > > Firstly, it is not 'supported.' So I had to use force_unsupported=1.
> > > But the firmware you download is from Avaya's site, so it seems to me
> > > like it should work!
> > > 
> > > Here's what i get:
> > > 
> > > firesong:/usr/src/orinoco-usb-0.2.1# modprobe orinoco_usb debug=1 force_unsupported=1
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c: Device is not supported (you may want to set force_unsupported=1)
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c: Trying to handle device anyway as requested
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c:bridge_probe: ENTER
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c: No firmware to download
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c:bridge_remove_in_urb: no urb to remove
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c:bridge_delete: ENTER
> > > unregister_netdevice: device wlan%d/cf4f3000 never was registered
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c:bridge_delete: EXIT
> > > /usr/src/orinoco-usb-0.2.1/driver/orinoco_usb.c:bridge_probe: EXIT
> > > drivers/usb/core/usb.c: registered new driver Orinoco USB
> > > orinoco_usb.c v0.2.1 (Manuel Estrada Sainz <ranty@debian.org>)
> > > 
> > > The light does not come on and I don't get any device. I notice that the
> > > firmware is loaded from a .SYS file and installed into the hotplug
> > > /usr/lib directory. When is this loaded?
> > > 
> > > Do you have any pointers? It would be really nice to get the card to
> > > work!
> > 
> >  You need a working hotplug package for the new driver to work.
> 
> What do you mean?  Does the base linux-hotplug scripts need to be
> changed for this device somehow?

 Adding /etc/hotplug/firmware.agent is enough for request_firmware() to
 work. I currently include the 2.4 backport of request_firmware() with
 it.

 Once a more recent hotplug gets into Debian sid (currently it is
 0.0.20030117-7) I'll change it and use hotplug.d.

 Have a nice day

 	Manuel

-- 
--- Manuel Estrada Sainz <ranty@debian.org>
                         <ranty@bigfoot.com>
			 <ranty@users.sourceforge.net>
------------------------ <manuel.estrada@hispalinux.es> -------------------
Let us have the serenity to accept the things we cannot change, courage to
change the things we can, and wisdom to know the difference.

      reply	other threads:[~2003-07-07 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-06  0:16 Joshua Kwan
2003-07-06 22:53 ` Manuel Estrada Sainz
2003-07-07  5:50   ` Greg KH
2003-07-07 18:32     ` Manuel Estrada Sainz [this message]

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=20030707183211.GA31222@ranty.pantax.net \
    --to=ranty@debian.org \
    --cc=greg@kroah.com \
    --cc=joshk@triplehelix.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®