[lug] wireless lan problems

Ferdinand Schmid fschmid at archenergy.com
Thu Feb 8 13:28:43 MST 2001


Sean Reifschneider wrote:

> On Thu, Feb 08, 2001 at 11:52:03AM -0700, Ferdinand Schmid wrote:
> >I got a D-LINK DWL-650 wireless lan card based on the reports that it works
>
> That's a PrismII chipset, right?  Pick up the latest pcmcia_cs from
> ftp.sourceforge.net:/pub/pcmcia_cs

Excellent guess!  Yes, this card uses the PrismII chipset according to my
research.  I just downloaded the latest pcmcia_cs package.  Based on the HOWTO I
get the feeling that my 2.4.1 kernel should already include the essentials of
this package.  FYI - this is a RH 6.2 system.

Amazing what you guys know!  I got a step ahead and now am stopped with a
different problem:  My kernel has a pcmcia module called wavelan_cs but not one
called wvlan_cs.  A symbolic link (my dummy attempt for a quick fix) didn't
work.  Where is the appropriate place to get this wvlan_cs module?   Here is my
new syslog:
Feb  8 13:22:11 fps cardmgr[549]: initializing socket 0
Feb  8 13:22:11 fps cardmgr[549]: socket 0: Intersil PRISM2 11 Mbps Wireless
Adapter
Feb  8 13:22:11 fps cardmgr[549]: executing: 'modprobe wvlan_cs'
Feb  8 13:22:12 fps cardmgr[549]: + modprobe: Can't locate module wvlan_cs
Feb  8 13:22:12 fps cardmgr[549]: modprobe exited with status 255
Feb  8 13:22:12 fps cardmgr[549]: module /lib/modules/2.4.1/pcmcia/wvlan_cs.o
not available
Feb  8 13:22:13 fps cardmgr[549]: get dev info on socket 0 failed: Resource
temporarily unavailable


> I've got the Addtron cards, which are Prism II.  Note that the wavelan
> driver doesn't currently seem to support adhoc mode, so you're limited
> to using an Access Point.

I can live with this limitation for now (will have to).

>
>
> The Addtrons actually link to the wlan-ng driver, but that's woefully
> incomplete.  Samsung has a driver out for their cards which supports
> Adhoc mode, but so far it's the only driver that's actually made my
> machine panic.  The wavelan driver in pcmcia_cs seems to be the best
> bet, though it does lock up the machine for 15 to 30 seconds during heavy
> net load.
>
> I'm hoping to take a look at it and see if I can figure out what's causing
> it, but I haven't had a chance to yet.
>
> Sean
> --
>  "Fixing Unix is easier than living with NT."  -- Jonathan Gilpin
> Sean Reifschneider, Inimitably Superfluous <jafo at tummy.com>
> tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python

Many thanks,
Ferdinand

--
Ferdinand Schmid
Architectural Energy Corporation
http://www.archenergy.com
(303) 444-4149





More information about the LUG mailing list