Please login or register.

Login with username, password and session length
Advanced search  


Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Author Topic: Atheros chipset questions  (Read 2485 times)


  • Member
  • *
  • Posts: 10
    • org.ecc - Java Blog
Atheros chipset questions
« on: May 31, 2007, 12:04:27 pm »

I have an Atheros chipset as well (in a Sony Vaio laptop), but using "ath_pci" for the DRIVER entry in interface.conf did'nt work for me (I couldn't get a WPA-PSK connection to work).

To have WPA-PSK working I had to use the generic "wext" driver; So, my /etc/wireless/interface.conf file contains:


(I don't know if I have a 'wlan0' interface)

Were you able to use WPA-PSK with the ath_pci driver ?


This is what is missing on the how to: to make sure /etc/wireless/interface.conf contains:


under "INTERFACE" in the place of "wlan0" there must be the name you chose to give your interface
under "DRIVER", in the place of "ath_pci" there must be its proper driver, in my case, as I was using a Atheros chipset, so it was the "ath_pci"

Somehow mine didnt, and after I entered it manually it worked. This should be included in the How-to, for future reference, will save many hours of aggravation for some people who believe the how to will contain all info that they will need.

How come the "how to" doesnt mention that one should check the /etc/wireless/interface.conf I dont know...
Vector Linux 5.8 SOHO Final   May-15-2007


  • Member
  • *
  • Posts: 19
Re: Atheros chipset questions
« Reply #1 on: May 31, 2007, 02:18:12 pm »

you are actually absolutely right my friend: while I was struggling to make it to work I found this thread:

and so I follow all the steps and I thought it was this bit:


that did the thing, because mine was blank, but actually my rc.local file contains this:

ifconfig ath0 down
ifconfig ath0 up
wpa_supplicant -dd -Dwext -iath0 -c/etc/wireless/wpa_supplicant.conf
dhcpcd ath0

Thus I am actually using the wext driver (see the nOOb I am, I didn't know the -D was to set the driver lol)

So I suppose I am in the same situation as you, but it works so yay (even though it seems a bit crooked in fact.