Re: SMC2662W V.3 Problems

Hi Richard,

On Mon, 14 Jul 2003, Richard Osborne wrote:

> I then added the X System development packages to my
> system and recompiled (e.g. make clean all install)
> did I need to do something else?  It seemed to install
> OK, but still does not work, I still get the message
> about the device has not been claimed by a driver, so
> I am confused.

I get the same message, but the driver is loaded afterwards
by hotplug. If not for you, you either miss the hotplug
package or its config is broken.

> The device seems to sense that there is an AP
> transmitting (I get a radio signal strength report
> when I run iwconfig) but iwconfig never reports the
> Key that I input using the Red Hat network dialog. I
> also tried using iwconfig to set the Key but that did
> not seem to work either. My AP is restricted and has
> WEP128 set, Is there something else I need to do to
> enable WEP128 besides:
> iwconfig eth0 key xxxxxxxxxxxxxxxxxxxxxxxxxx (that is
> 26 hex digits 0-9, A-F)?

IMHO you must add a prefix "s:" for ascii keys in iwconfig:
	iwconfig eth0 key s:this_is_my_very_secret_key

Be aware that ASCII keys may get translated into hex by your AP config
tool (in a vendor-specific way), it's usually better to input hex keys on
both sides. And even better to switch WEP off during the first try.

You may consider using the alternative driver
	http://at76c503a.berlios.de
which does not need X11 includes, comes with iwconfig support only and
calls its netdevices wlanX (which you may change to anything using a
module parameter).

/Jörg