Re: error to load driver

Joerg Albert <[email protected]>
Newsgroups gmane.linux.drivers.at76c503a.user
Message-ID <[email protected]>
Hi,

On Mon, 26 Jan 2004, Luke Shen wrote:

> 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.
Guess you left the device plugged after a Windows run. The Windows drivers
uses a different firmware version, which remained in the device causing
the previous problem (firmware version 0).


> 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.

Looks like you miss a default route to your router.

> Here is background info:
> ...
> 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.)

no need to worry. The firmware in the device does not report link quality
nor noise level (except on Intersil radios).

> 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.)

no, looks fine as well - keylen/index is only displayed when the ioctl are
debugged and a new key is set.

> 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

That's your problem, you have no default route. How should the
network stack know where to send a packet with destination,
e.g. 64.68.82.204? I don't understand your network setup, what's the
169.254.0.0/16 network for (on the l0 device)?
Try to add a default route with
	route add default gw <your router ip address>


> 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.)

As long as you use "open system" authentication, you will be able to
connect to an AP, but the data packets (IP etc.) exchanged later will not
be correctly decoded.

> 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.)

Strange indeed. You are sure to have pinged your _router_ ,
not your own IP address (you've never mentioned these values)??
Or you pinged it on a wrong interface, not on wlan.

Ping times should be several milliseconds for 802.11b WLAN.
ping should succeed in case (4) only.

Be aware, that you've posted your WEP  key to the public!

/Jörg
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.