Re: error to load driver

"Luke Shen" <[email protected]>
Newsgroups gmane.linux.drivers.at76c503a.user
Message-ID <[email protected]>
Joerg, thank you very much for your tip. I got through the driver loading 
problem by replug the USB adapter or do a cold boot.

However, I was still not able to make through the whole process, though I am 
getting closer. Here is the new problem:

After I loaded the driver and configured it with <iwconfig>, I was able to 
ping my Linksys USB11 ver. 2.6 with the following command: <ping 
192.168.1.1>. All the packets are received. However, when I tried to ping an 
outside address <ping 64.68.82.204>, I got error message:

connect:network is unreachable

That IP address is actually where google is, and it worked when I tried to 
ping it on Windows.

Here is background info:

1. After loading driver, in the syslog, <dmesg> returns following info:

at76c503.c: firmware version 1.101.4 #84 (fcs_len 4)
at76c603.c: device's MAC 00:06:25:0e:10:1e, regulatory domain FCC (U.S) (id 
16)
divert: allocating divert_blk for wlan0
at76c503.c: registered wlan0

(I believe it is good so far.)

<lsmod> returns the following:

at76c503_rfmd   40320   0 (unused)
usbdfu               9324    0 [at76c503_rfmd]
at76c503           53888   0 [at76c503_rfmd]

(I believe it is good as well.)

2. after configuring driver, <iwconfig wlan0> returns the following info:

wlan0 IEEE 802.11-DS ESSID:"faosjtu" Nickname:"okuwlan"
Mode:Managed    channel: 6     Access Point: 00:06:25:B6:0B:41
Bit Rate:11Mb/s
RTS thr=1536 B Fragment thr=1536 B
Encryption key:B38D-D7B4-EF66-7CA1-0820-E2D6-71  mode: restricted
Power Management:off
Link Quality:0  Signal Level:27  Noise Level:0
Rx invalid nwid:8   Rx invalid crypt:0   Rx invalid frag: 0
Tx execssive retries: 0   Invalid misc: 0    Missed beacon: 0

("Link Quality:0" makes me suspicious, though I am not exactly sure what it 
means.)

3. <dmesg> return the following lines after I set <iwpriv wlan0 set_debug 
0x180003>:

at76c503.c: wlan0:PRIV_IOCTL_SET_DEBUG input 9: )x180003 -> x180003
at76c503.c: wlan0:PRIV_IOCTL_SET_DEBUG, old 0x0 new 0x180003
at76c503.c: wlan0: netif running 1   queue_stopped 0   carrier_ok 1

(somewhere in the mail archive I learned that I should expect keylen and 
index displayed here in some "param:" line and they must be 13 and 0. So 
something is wrong in my case.)

4. <route -n> returns following:

Kernel IP routing table
Destination        Gateway       Genmask            Flags Metric Ref Use 
Iface
192.168.1.0      0.0.0.0         255.255.255.0    U     0        0    0    
wlan0
169.254.0.0      0.0.0.0         255.255.0.0        U     0        0    0    
l0
127.0.0.0         0.0.0.0         255.0.0.0            U     0        0    0 
    l0

5. In order to verify that my configuration is correct, I did the following 
experimentation:

(1) replace "faosjtu" with a wrong string for "essid", <dmesg> reports 
"essid didn't match".
(2) use "faosjtu" for "essid", but set "key" to "off", <dmesg> reports 
"requires encryption".
(3) use "faosjtu" for "essid", but set "key" to some wrong value, <dmesg> 
reports:
"state 6->2 (AUTHENTICATING)
state 2->3 (ASSOCIATING)
state 3->7 (CONNECTED)
connected to BSSID 00:06:25:b6:0b:41"
(4) use "faosjtu" for "essid" and set "key" to the correct value, <dmesg> 
reports exactly the same thing as in step (3). (This seems odd to me.)

I also tried to ping the router and yahoo during the above 4 steps. In ALL 
steps, I was able to ping the router correctly, but got the same "network 
unreachable" error in the latter. (this also seems to be odd to me.)

6. I tried to disable WEP in the router and set "key" to "off" in 
configuring the driver, still to no avail.

So I am stuck again. Any advice? Thanks in advance.

Luke


>From: Joerg Albert <[email protected]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Re: [at76c503a-user] error to load driver
>Date: Sun, 25 Jan 2004 21:02:23 +0100 (CET)
>
>Hi,
>
>On Sat, 24 Jan 2004, Luke Shen wrote:
>
> > usbdfn.c: registered new driver at 76c503-rfmd
> > usb.c: registered new driver at 76c503-rfmd
> > usbdfu.c: interface class is not DFU
> > at76c503.c: Downloading external firmware
> > at76c503.c: ext fw, size left = 15428, bsize=1024, i=0
> > ...
> > at76c503.c: ext fw, size left =     68, bsize=1024, i=15
> > at76c503.c: getting firmware failed with 0, or version is 0
> > at76c503.c: this probably means that the ext. fw was not loaded 
>correctly
> > unregister new device: device eth%d/c9e13000 never was registered
> > at76c503.c: at76c503_new_device returned NULL
>
>I really wonder why the interface class of your device was "not DFU" - did
>it remain plugged-in from a former try (under Windows ?) ? Please try to
>load all modules first, then plug the WUSB11 v2.6 in.
>You may also consider trying the latest cvs snapshot.
>
>/Jörg
>_______________________________________________
>at76c503a-user mailing list
>[email protected]
>http://lists.berlios.de/mailman/listinfo/at76c503a-user

_________________________________________________________________
Scope out the new MSN Plus Internet Software — optimizes dial-up to the max! 
   http://join.msn.com/?pgmarket=en-us&page=byoa/plus&ST=1
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.