You are not logged in.
Pages: 1
For some strange reason, my wireless device requires me to take the following steps before I get a connection:
modprobe -r ath5k
modprobe ath5k
iw wlp7s0 connect my_essid key 0:xxxxxxxxxx
dhcpcd wlp7s0
or
modprobe -r ath5k
modprobe ath5k
iwconfig wlp7s0 essid my_essid key xxxxxxxxx
iwconfig wlp7s0 essid my_essid
dhcpcd wlp7s0
If I don't follow these specific steps dhcpcd just times out. If I enter the key without the ssid then I can no longer change the ssid that I'm trying to connect to... It's just being quirky as hell.
I'm using a netgear pci-card, lspci:
07:00.0 Ethernet controller: Qualcomm Atheros AR5212/AR5213 Wireless Network Adapter (rev 01)
Any ideas?
Last edited by Square (2013-08-16 13:52:23)
Offline
Sorry for not providing any pointers regarding your problem, but FWIW in my experience ath5k has always been a bit quirky. I may have had bad luck with the chipset I was running. I finally decided to get rid of that card and find one that ran with ath9k.
Offline
Pages: 1