Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
Write an article for LinuxForums Today! Win Great Prizes!
I've spent the last couple of days trying to set up a wireless connection to an encrypted network at my Uni, but I refuse to go to the IT services guys - just because I'm too stubborn.
After adding a WPA Supplicant config file, when I go on to use the 'wpa_supplicant' command in terminal, I always get given the response that my driver is not supported.
So far I have been putting in my Interface name (card name) as 'ath0' and I have been, up until now, pretty sure that that driver name was 'ath_pci' ... but I'm guessing that is probably wrong as Linux isn't liking me at the moment.
I know that wireless works since I am currently using it on the Uni's unencrypted/more restricting wireless network. The configuration of which using 'Interface: Wifi 802.11g (ath0)' / 'Driver: 11g_ath_pci' (and I have also tried using the name 11g_ath_pci as my driver name too).
If I am correct (and my knowledge of Linux is pretty poor), ath_pci is a name used by Madwifi for its Atheros drivers???
So in short ... what the hell is my Wireless card driver name if it isn't ath_pci/11g_ath_pci/Madwifi?
Cheers in advanced
PS ... to give you some more info to work on. These are the instructions my Uni gives. So far I've tried both install types, manual seems to easier as it gives me more feedback.
I can give you more info if you need but I am ... reasonably ... confident that ath0 is the interface name and the driver is Madwifi, it is just something about the driver name I am inputting that is wrong.
I am no wireless expert, but I know what commands the experts here will ask you to use and then post the results from terminal in your next post. They are going to be:
dmesg | grep firmware
lsmod
lspci
lsusb (that is lower case L for first letter)
Open a Termiunal and post the outputs on the terminal screen in your next post. Better members than me will be able to help you out better then.
P.s. Include your distro and kernel and computer specs for best results. To get kernel version type into terminal
uname -r
Good luck.
__________________ Free Linux Books
Linux Registered User # 475019 And I’ll keep using Linux until they pry it from my cold dead fingers.
The system is Linpus (Acer's Fedora based own operating system) with the Kernel being 2.6.23.9lw. The laptop is one of the Acer Aspire One - 1.6GHz, 512MB memory, 8Gig Flash Hard Drive with an Atheros Wireless Card (it says Atheros AR5BXB63 on the back - I read somewhere that sometimes the AR500x stuff sometimes gets misidentified on the system, not sure if it is true here but the system says it is an AR5006EG on the PCI output).
I'm guessing you can all probably figure out the rest of the specs from looking at the PCI list, I have no USB attachments except for a webcam so I won't bother adding that list.
For the 'dmesg | grep' command I'm not too sure what specifically to search for, so I searched for 'ath' and 'wlan' as both are quite prominent prefixes in the module list. So...
dmesg | grep ath
Code:
ath_rate_atheros: Version 2.0.1
ath_rate_atheros: driver unloaded
ath_rate_atheros: Version 2.0.1
[root@localhost ~]# dmesg | grep ath
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.1 (AR5212, RF5111, RF5112, RF2413, RF5413)
ath_dfs: Version 2.0.0
ath_rate_atheros: Version 2.0.1
ath_pci: 0.9.4.5 (Atheros/multi-bss)
ath_pci: Acer-5.3.2.13-2008-June-13
<ath_vap_create> sc_softled = 0
ath_vap_create: LED ON
ath_stop_locked: LED OFF 2
ath_stop_locked: LED OFF 2
ath_pci: driver unloaded
ath_rate_atheros: driver unloaded
ath_dfs: driver unloaded
ath_hal: driver unloaded
ath_hal: 0.9.17.1 (AR5212, RF5111, RF5112, RF2413, RF5413)
ath_dfs: Version 2.0.0
ath_rate_atheros: Version 2.0.1
ath_pci: 0.9.4.5 (Atheros/multi-bss)
ath_pci: Acer-5.3.2.13-2008-June-13
<ath_vap_create> sc_softled = 0
ath_vap_create: LED ON
ath_stop_locked: LED OFF 2
and dmesg | grep wlan
Code:
wlan: 0.8.4.2 (Atheros/multi-bss)
wlan: mac acl policy registered
wlan: mac acl policy unregistered
wlan: driver unloaded
wlan: 0.8.4.2 (Atheros/multi-bss)
wlan: mac acl policy registered
I feel like I have just spammed the forum with all my information, I should probably stop otherwise I'll end up giving out my Bank Account details and Mother's maiden name!
Just say if I left something useful out or if I searched for the wrong thing in the 'dmesg' search.
The output of dmesg isn't as important right now. But it can be an effective tool in diagnosing problems. I do see a lot of "driver unloaded" messages, as a driver can't work if it's unloaded. But since we see it in the list, I won't worry right now.
Have you configured the wireless as a new network card? If it is similar to Fedora ( I think it is) you want to run the Network program from the main menu. When that opens, your network connections should be listed. The wireless will be either wlan0 or ath0. Click on it to highlight it, and then click on the "Edit" icon on the top. In this section, you want to select these choices:
-Controlled by NetworkManager
-Allow All Users To Enable and Disable This Device
-Automatically obtain IP address settings with DHCP
-Automatically obtain DNS information from provider
Once that is done, close that window, and save the new settings with File--->Save. Now click the green "Activate" button at the top. You now may need to reboot.
After the reboot, there should be an icon in the system tray (taskbar) for the NetworkManager. Right click it to make sure "Enable Wireless" is checked. Now left click to see a list of available networks. You can click on it to connect.
If there is a password, it should ask to save it either in a keyring manager, or KWallet. Say yes, and give the keyring/Wallet a password of it's own. Now all future passwords will also be saved, and accessed with a single password. No more remembering multiple wireless passwords.
My instructions are for Fedora, so Linpus may be a bit different.
If there are still connection problems, you may need to install an updated driver. Let me know how it works out.
__________________
Paul
Please do not PM me with requests for help. I will not reply.
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe