个人工具

“UbuntuHelp:WifiDocs/Driver/Atheros”的版本间的差异

来自Ubuntu中文

跳转至： 导航, 搜索
（→‎Built-in drivers/modules, tested only on Intrepid）
小
第2行： 第2行：
 
{{Languages|UbuntuHelp:WifiDocs/Driver/Atheros}}
 
{{Languages|UbuntuHelp:WifiDocs/Driver/Atheros}}
 
== Built-in drivers/modules, tested only on Intrepid ==
 
== Built-in drivers/modules, tested only on Intrepid ==
−
The module is on '''[[UbuntuHelp:UbuntuBackports|linux-backports-modules-intrepid]]''' and it's called ath5k. You just need to install the package, either using Synaptic or apt-get, and make sure that is activated on System/Administration/Hardware Drivers.
+
Look for the ath5k module, located in the package '''[[UbuntuHelp:UbuntuBackports|linux-backports-modules-intrepid]]'''. Install the package using either Synaptic or apt-get, and make sure it is activated on System/Administration/Hardware Drivers.
−
Follow these steps bellow '''only if this did not work'''. What might happened is a conflict with either ath_hal or ath_pci, or you might have ath5k blacklisted somewhere. So:
+
Follow the steps below '''only if ath5k module did not work'''. This may be the result of a conflict with either ath_hal or ath_pci, or ath5k might be blacklisted somewhere. So:
 
1) Hit "alt+f2" to run a command and type:
 
1) Hit "alt+f2" to run a command and type:
 
<pre><nowiki>
 
<pre><nowiki>
 
gksudo gedit /etc/modprobe.d/blacklist
 
gksudo gedit /etc/modprobe.d/blacklist
 
</nowiki></pre>
 
</nowiki></pre>
−
And add to the bottom of the file the following lines:
+
And add the following lines to the bottom of the file:
 
<pre><nowiki>
 
<pre><nowiki>
 
blacklist ath_hal
 
blacklist ath_hal
 
blacklist ath_pci
 
blacklist ath_pci
 
</nowiki></pre>
 
</nowiki></pre>
−
Reboot. If it's still not working you much probably have ath5k being blacklisted somewhere. Blacklisting might happen if you are coming from a Hardy upgrade and/or did not uninstall the madwifi driver before doing this. So:
+
Reboot. If it's still not working than it is very likely you have ath5k being blacklisted somewhere. Blacklisting may have occurred if you are coming from a Hardy upgrade and/or did not uninstall the madwifi driver before doing this. So try the following, but Be Extremely Careful - this next command opens nautilus with root privileges, which can change and/or damage any file on the system.
−
2) Be extremely careful, the next command opens a nautilus with root privileges which can change and damage any file on the system. Alt+f2 and do a
+
2) Hit "alt+f2" to run a command and type:
 
<pre><nowiki>
 
<pre><nowiki>
 
gksudo nautilus
 
gksudo nautilus
第22行： 第22行：
 
/etc/modprobe.d
 
/etc/modprobe.d
 
</nowiki></pre>
 
</nowiki></pre>
−
And check each and everyfile for a line that looks like:
+
Now check each and every file for a line that looks like:
 
<pre><nowiki>
 
<pre><nowiki>
 
blacklist ath5k
 
blacklist ath5k
第33行： 第33行：
 
Just remember you need to just comment lines that have "blacklist ath5k".
 
Just remember you need to just comment lines that have "blacklist ath5k".
 
This solution is based on this thread on the forums: http://ubuntuforums.org/showthread.php?p=6089169
 
This solution is based on this thread on the forums: http://ubuntuforums.org/showthread.php?p=6089169
−
==== If after everything you see a network but it doesn't connect ====
+
==== If after all the above you see a network but cannot connect ====
 
You might want to try changing the WPA Supplicant on your network manager to '''wext'''. On wicd it's the first option when you go into Preferences.
 
You might want to try changing the WPA Supplicant on your network manager to '''wext'''. On wicd it's the first option when you go into Preferences.
 
==== If after everything you don't see your network ====
 
==== If after everything you don't see your network ====
−
Remember that you might be trying to connect to an access point that is not broadcasting its name (hidden SSID), witch is a separate issue and can be checked by enabling SSID broadcast on the access point.
+
Remember that you might be trying to connect to an access point that is not broadcasting its name (hidden SSID), which is a separate issue and can be checked by enabling SSID broadcast on the access point.
−
 
+
 
== Manually installed drivers ==
 
== Manually installed drivers ==
 
sudo lshw -C network
 
sudo lshw -C network
−
I found these things helpful for me:
+
I found the following things helpful:
 
1)
 
1)
 
https://bugs.launchpad.net/bugs/182489
 
https://bugs.launchpad.net/bugs/182489
第49行： 第48行：
 
</nowiki></pre>
 
</nowiki></pre>
 
2)
 
2)
−
http://madwifi.org/ticket/1192
+
http://madwifi-project.org/ticket/1192
 
<pre><nowiki>
 
<pre><nowiki>
 
(Synopsis:
 
(Synopsis:
 
0. Connect to wired network and install build-essential (sudo apt-get install build-essential)
 
0. Connect to wired network and install build-essential (sudo apt-get install build-essential)
−
1. wget http: / /snapshots.madwifi.org/madwifi-hal-0.10.5.6/madwifi-hal-0.10.5.6-r3835-20080801.tar.gz
+
1. wget http://snapshots.madwifi.org/madwifi-hal-0.10.5.6-current.tar.gz
−
2. tar -zxvf madwifi-hal-0.10.5.6-r3835-20080801.tar.gz
+
2. tar -zxvf madwifi-hal-0.10.5.6-current.tar.gz
−
3. cd madwifi-hal-0.10.5.6-r3835-20080801
+
3. cd madwifi-hal-0.10.5.6-r*
 
4. sudo make
 
4. sudo make
 
5. sudo make install
 
5. sudo make install
第61行： 第60行：
 
7. sudo vi /etc/modprobe.d/blacklist -> blacklist ndiswrapper (Do this if you had tried ndiswrapper)
 
7. sudo vi /etc/modprobe.d/blacklist -> blacklist ndiswrapper (Do this if you had tried ndiswrapper)
  
−
This downloads and installs a non-free binary-only driver for the atheros chipset. You need to rebuild and reinstall the driver every time you update your kernel.
+
This will download and install a non-free, binary-only driver for the atheros chipset. You need to rebuild and reinstall the driver every time you update your kernel.
 
</nowiki></pre>
 
</nowiki></pre>
 
3) The wireless LED on my laptop does not work in linux. I may have pressed the wireless button while troubleshooting and turned off wireless without knowing it. So while fiddling around, I may have installed the right driver but not known it.
 
3) The wireless LED on my laptop does not work in linux. I may have pressed the wireless button while troubleshooting and turned off wireless without knowing it. So while fiddling around, I may have installed the right driver but not known it.

2009年5月12日 (二) 19:40的版本

Geographylogo.png 文章出处: 

https://help.ubuntu.com/community/WifiDocs/Driver/Atheros

Geographylogo.png 点击翻译: 

English

请不要直接编辑翻译本页，本页将定期与来源同步。

Built-in drivers/modules, tested only on Intrepid

Look for the ath5k module, located in the package linux-backports-modules-intrepid. Install the package using either Synaptic or apt-get, and make sure it is activated on System/Administration/Hardware Drivers. Follow the steps below only if ath5k module did not work. This may be the result of a conflict with either ath_hal or ath_pci, or ath5k might be blacklisted somewhere. So: 1) Hit "alt+f2" to run a command and type: 

gksudo gedit /etc/modprobe.d/blacklist

And add the following lines to the bottom of the file: 

blacklist ath_hal
blacklist ath_pci

Reboot. If it's still not working than it is very likely you have ath5k being blacklisted somewhere. Blacklisting may have occurred if you are coming from a Hardy upgrade and/or did not uninstall the madwifi driver before doing this. So try the following, but Be Extremely Careful - this next command opens nautilus with root privileges, which can change and/or damage any file on the system. 2) Hit "alt+f2" to run a command and type: 

gksudo nautilus

And navigate to 

/etc/modprobe.d

Now check each and every file for a line that looks like: 

blacklist ath5k

And just add a "#" character at the beginning of the line, thus commenting it. You might probably find this case on a file named "madwifi". 2.1) Alternatively, to quickly find where ath5k is being blacklisted, you can open a terminal (Applications/Accessories/Terminal) and type: 

grep -r "ath5k" /etc/modprobe.d/

Just remember you need to just comment lines that have "blacklist ath5k". This solution is based on this thread on the forums: http://ubuntuforums.org/showthread.php?p=6089169

If after all the above you see a network but cannot connect

You might want to try changing the WPA Supplicant on your network manager to wext. On wicd it's the first option when you go into Preferences.

If after everything you don't see your network

Remember that you might be trying to connect to an access point that is not broadcasting its name (hidden SSID), which is a separate issue and can be checked by enabling SSID broadcast on the access point.

Manually installed drivers

sudo lshw -C network I found the following things helpful: 1) https://bugs.launchpad.net/bugs/182489 

(Synopsis: Add the following line:
blacklist ath_pci
to the /etc/modprobe.d/blacklist file and reboot. If you are running an up-to-date Hardy, this should enable the free/libre ath5k driver.)

2) http://madwifi-project.org/ticket/1192 

(Synopsis:
0. Connect to wired network and install build-essential (sudo apt-get install build-essential)
1. wget http://snapshots.madwifi.org/madwifi-hal-0.10.5.6-current.tar.gz
2. tar -zxvf madwifi-hal-0.10.5.6-current.tar.gz
3. cd madwifi-hal-0.10.5.6-r*
4. sudo make
5. sudo make install
6. System -> Administration -> Hardware Drivers -> Uncheck both hal and Atheros support
7. sudo vi /etc/modprobe.d/blacklist -> blacklist ndiswrapper (Do this if you had tried ndiswrapper)

This will download and install a non-free, binary-only driver for the atheros chipset. You need to rebuild and reinstall the driver every time you update your kernel.

3) The wireless LED on my laptop does not work in linux. I may have pressed the wireless button while troubleshooting and turned off wireless without knowing it. So while fiddling around, I may have installed the right driver but not known it. __

取自“https://wiki.ubuntu.org.cn/index.php?title=UbuntuHelp:WifiDocs/Driver/Atheros&oldid=115642”