| 1 |
On Tue, Jun 2, 2009 at 7:24 AM, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
> I'm afraid that although my card is now recognised as wlan0, both |
| 3 |
> wpa_cli and gui insist on trying to connect to ath0, unless I specify |
| 4 |
> -iwlan0 at the terminal. I don't have (knowingly) specified ath0 in |
| 5 |
> any other configuration file ... where else could wpa_supplicant pick |
| 6 |
> this from? |
| 7 |
|
| 8 |
On my system I've got ath5k for wifi, too. It uses wpa_supplicant and |
| 9 |
my device is wlan0 and all works well enough. I switched 2 machines |
| 10 |
from madwifi to ath5k and only had to make 4 changes to my |
| 11 |
configuration: |
| 12 |
|
| 13 |
1. Edit /etc/modprobe.d/blacklist and add this line: |
| 14 |
blacklist ath_pci |
| 15 |
|
| 16 |
2. In /etc/conf.d/net I have changed this line: |
| 17 |
wpa_supplicant_ath0="-Dmadwifi" |
| 18 |
|
| 19 |
to this: |
| 20 |
wpa_supplicant_wlan0="-Dwext" |
| 21 |
|
| 22 |
3. In /etc/udev/rules.d/70-persistent-net.rules I deleted the old |
| 23 |
entry for my wireless card and let it re-create, which came out as: |
| 24 |
# PCI device 0x168c:0x001c (ath5k_pci) |
| 25 |
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", |
| 26 |
ATTR{address}=="00:15:af:15:e3:3e", ATTR{type}=="1", KERNEL=="wlan*", |
| 27 |
NAME="wlan0" |
| 28 |
|
| 29 |
4. Rename /etc/init.d/net.ath0 symlink to /etc/init.d/net.wlan0 and |
| 30 |
make sure it is in the "default" runlevel. |
| 31 |
|
| 32 |
And finally reboot. Good luck! |
Archives