Re: Prism2 Linux module

From: Scott Dixon (
Date: 2002-01-09 18:58:30 UTC

I've got a Netgear MA401 which shows signs of working with Prism2. I can get it to connect, either in Ad-hoc mode or to an AP as long as I don't use WEP. I can't seem to get a correct WEP key (40bit) set no matter how I give commands to iwconfig. It always seems to set to the same arbitrary and incorrect encryption key. However, the same card does work with WEP with either wlan-ng or with the Samsung binary driver (swld11_cs). I'm currently using the swld11_cs because it seems to give significantly higher receive speeds than wlan-ng (and I can't use prism2 until I can get WEP working). Regards,

On Wed, 2002-01-09 at 08:35, Jouni Malinen wrote:
> On Tue, Jan 08, 2002 at 05:39:25PM -0500, Aaron Longfield wrote:
> > Problem I am having is that the module loads, but no entry is made
> > in /proc and no network interface is created, so ifconfig and
> > iwconfig don't show anything for it. I've tried with several
> > devices: Cisco Aironet 340, Neatgear MA401, Proxim Rangelan DS, and
> > Lucent WaveLAN Silver.
> > Not sure if there's anything else to do, but I don't see any more to
> > try. Do I have to do more than insmod the object? It loads, and
> > drops a kernel message in dmesg with author info and such, but
> > nothing about the module finding hardware.
> Do you have cardmgr running? Did it recognize the cards? Are the cards
> working with another driver? Cisco Aironet cards will not work with
> this driver. I'm not fully sure about Netgear and Proxim, but they
> might work. Lucent WaveLAN should work partially (however, now Host AP
> mode with it).
> Loading the module does not initialize it. Cardmgr needs to notice the
> card and tell the driver to start configuring the card. In other
> words, you will need to make sure that cardmgr configurating is valid
> for the cards. If he problem persists, please check whether cardmgr
> wrote some error messages (usually via syslog to /var/log/messages).
> --
> Jouni Malinen PGP id EFC895FA

This archive was generated by hypermail 2.1.4.