[driverloader] Intermittent connection on Thinkpad T40p with
Atheros chip set
Linuxant support (Jonathan)
support at linuxant.com
Mon May 2 14:56:21 EDT 2005
please try with different versions of the Windows XP driver to see if
there is a difference.
Technical specialist / Linuxant
support at linuxant.com
John Pedersen wrote:
> I've been experiencing intermittent connectivity issues under FC 3 on a
> TP T40p using the Atheros chip set and what I believe is their latest
> windows driver (ar5211.sys, version 18.104.22.168). My AP is a Linksys
> WRT54G with firmware 3.03.6.
> The thinkpad is a dual boot, FC3/XP machine and I use the same driver
> and access point under linux and windows. I have no connectivity
> problems under windows. I can put the laptop in suspend mode and start
> it up hours later without a hitch.
> Under linux, I have had no problem making an initial connection and
> getting the dhcp information for the system. As far as I can tell, the
> IP address gets assigned properly and the proper dns information makes
> its way into /etc/resolv.conf.
> Generally, at some point in a session, a client (web browser or mail
> client usually) will start failing to resolve or connect. If I look at
> ifconfig, the IP address will be set properly; in iwconfig the essid and
> key are properly set, and the dns hosts are properly set in
> /etc/resolv.conf - but a ping to the ap will fail. I have started
> running a continuous ping upon connecting on the theory that some sort
> of timeout might be occurring.
> In this case, the connection failed in the middle of the ping. I then
> went and did a dldrconfig -d. The text files for both are attached.
> For what it's worth, my general practice to connect to an ap, is to use
> iwlist to confirm the essid, then use iwconfig to explicitly set the
> essid and key. I then run up neat (system-config-network), and activate
> the network connection through it. I confirm that essid and key in neat
> are the same as the essid and key that was passed directly to iwconfig.
> (I've yet to get neat to successfully configure the password for the
> wireless interface and so do things by hand.)
> I would love to get this running reliably. Even in its current state
> though, it was worth the cost of the license.
> Any thoughts as to how to proceed?
> John Pedersen
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader