Re: SMC2662W V.3 Problems

Hi Joerg,

Thanks for the reply.

OK, if I look in dmesg I have the following:

usb.c: USB device 2 (vend/prod 0xd5c/oxa002) is not
claimed by any active driver.
usb.c: registered new driver usbvnetr
usb vendor/product=d5c/a002
vnet_kernel.c: Reseting Usb Device
vnet_kernel.c: Reset completed.
Reg Domain
usbvnetr: driver 1.01, compiled Jul 12 2003 19:39:11
(dbg_mask x0)
MAC addr 00:04:E2:79:DE:C8 firmware 1.101.2.84
divert: allocating divert_blk for eth0
Multicast is enabled
divert: allocating divert_blk for eth0
divert: freeing divert_blk for eth0
vnetusba.c: usb eth0 initialized and registered
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6
len 18 ret -6
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6
len 18 ret -6
ohci1394: pci_module_init failed
ip_tables: (C) 2000-2002 Netfilter core team
**********************
REASSOCIATION RESPONSE
**********************

From iwconfig I get:

eth0     
ATMEL RFMD503A  ESSID:"Myrtoum" Nickname:"Myrtoum"
Mode:Managed Channel:1 Access Point: 00:05:5D:ED:1F:8A
Bit Rate:2Gb/s
RTS thr=2347 B Fragment thr=2346 B
Encryption key:0000-0000-00 Encryption mode:restricted
Encryption mode:open
Link Quality:100 Signal level:20 Nosie level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Notice that the key is listed as ten zeros, I have
tried inputing in Red Hat config as (this is NOT my
real key):
1234567890ABCDEF1234567890
or
1234567890abcdef1234567890
or 
1234-5678-90ab-cdef-1234-5678-90

In iwconfig I have tried with and without s:

In all cases iwconfig reports key:0000-0000-00

The hardware supports the longer key (I have used the
long key in win2k)

Thanks for any help.

I might give the other driver a try later, but for now
I would like to get this one working, if possible.

R.

--- Joerg Albert <[email protected]> wrote:
> 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


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com