orinoco_cs: Resource temporarily unavailable
David Gibson
david at gibson.dropbear.id.au
Mon Feb 4 15:26:13 EST 2002
On Sun, Feb 03, 2002 at 11:23:01PM -0500, PinkFreud wrote:
> On Sun, Feb 03, 2002 at 09:50:43PM +1100, David Gibson babbled thus:
> > Date: Sun, 3 Feb 2002 21:50:43 +1100
> > From: David Gibson <david at gibson.dropbear.id.au>
> > To: PinkFreud <pf-wireless at mirkwood.net>, wireless at lists.samba.org
> > Subject: Re: orinoco_cs: Resource temporarily unavailable
> > Mail-Followup-To: PinkFreud <pf-wireless at mirkwood.net>,
> > wireless at lists.samba.org
> > User-Agent: Mutt/1.3.25i
> >
> > > Jan 24 01:45:05 edoras cardmgr[335]: socket 1: Lucent Technologies
> > > WaveLAN/IEEE Adapter
> > > Jan 24 01:45:05 edoras cardmgr[335]: executing: 'modprobe hermes'
> > > Jan 24 01:45:05 edoras cardmgr[335]: executing: 'modprobe orinoco'
> > > Jan 24 01:45:05 edoras cardmgr[335]: executing: 'modprobe orinoco_cs'
> > > Jan 24 01:45:06 edoras cardmgr[335]: get dev info on socket 1 failed:
> > > Resource temporarily unavailable
> >
> > The problem lies in the update to the pcmcia code, not in the orinoco
> > driver - this message is generated before the driver is activated.
>
> However, wvlan_cs works just fine, with the same pcmcia code. Even
> switching back to 2.2.20 and trying to load the orinoco_cs driver
> included with pcmcia-cs yields the same error.
There must be a pcmcia configuration problem that is associated with
the switch between the drivers - the orinoco driver hasn't even
attempted to do anything at the point this message appears.
--
David Gibson | For every complex problem there is a
david at gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
More information about the wireless
mailing list