Difference between revisions of "Rtl8187 wireless"

From ArchWiki
Jump to: navigation, search
(removed obsolete stuff)
m (Using the driver: fix link)
(20 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[Category:Communication and network (English)]]
+
[[Category:Wireless Networking]]
[[Category:HOWTOs (English)]]
+
 
 
This page describes how to get the '''rtl8187''' wifi-driver working
 
This page describes how to get the '''rtl8187''' wifi-driver working
  
Note: The rtl8187 driver is in the kernel (thus the driver comes with the kernel26 package)
+
Note: The rtl8187 driver is in the kernel (thus the driver comes with the linux package)
  
  
Line 24: Line 24:
  
 
If everything is right, you should have two new interfaces: wlan0 and wmaster0
 
If everything is right, you should have two new interfaces: wlan0 and wmaster0
If you don't see wlan0 just run
+
If you do not see wlan0 just run
 
  ifconfig wlan0 up
 
  ifconfig wlan0 up
  
Line 30: Line 30:
 
  iwlist wlan0 scan
 
  iwlist wlan0 scan
  
For more information about configuring your wifi-network see here: [http://wiki.archlinux.org/index.php/Wireless_Setup#Setup_and_Boot http://wiki.archlinux.org/index.php/Wireless_Setup#Setup_and_Boot]
+
For more information about configuring your wifi-network see here: [[Wireless_Setup#Setup_and_Boot|http://wiki.archlinux.org/index.php/Wireless_Setup#Setup_and_Boot]]
  
== What to do if your connection always times out? ==
+
= What to do if your connection always times out? =
  
=== Method 1: Lowering the transfer rate manually ===
+
The open source driver suffers from a lot of tx excessive retries and invalid misc errors for some unknown reason, resulting in a lot of packet loss and it keeps disconnecting, some times instantly.
The solution can be found in this thread: http://bbs.archlinux.org/viewtopic.php?pid=299642
+
 
 +
==Adjusting with iwconfig options==
 +
 
 +
=== Lowering the rate ===
 +
 
 +
The solution can be found in this thread: https://bbs.archlinux.org/viewtopic.php?pid=299642
  
 
Just set the rate to 5.5
 
Just set the rate to 5.5
 
  iwconfig wlan0 rate 5.5M auto
 
  iwconfig wlan0 rate 5.5M auto
  
Actually this worked for a while but it would still start revving out, so making the last
+
Fixed option should ensure, however, it doesn't change the rate on its own, thus making the connection a bit more stable:
item "fixed" ensures it does not spin.  Btw. If your wireless card has already gone into
+
meltdown issuing this command will get it working again.
+
  
 
  iwconfig wlan0 rate 5.5M fixed  
 
  iwconfig wlan0 rate 5.5M fixed  
  
I have also tried setting this in the IWOPTS, but it does not seem to be taking, so now what I do until I get this sorted out is:
+
Alternativelly find the $POST_UP option and append the above options to your profile config file:
  netcfg2 -c <your wireless profile>
+
  iwconfig wlan0 rate 5.5M fixed
+
  
And then it never times out (at least for me)
+
POST_UP="iwconfig wlan0 rate 5.5M fixed"
  
Found the $POST_UP option, so appending this to your profile config
+
Try various rates until you get the optimal setting, with no disconnection. In this case 12Mbits, as shown bellow:
file, sets the rate correctly when using the netcfg tools.
+
  
    POST_UP="iwconfig wlan0 rate 5.5M fixed"
+
POST_UP="iwconfig wlan0 rate 12M fixed"
 
+
Actually for my card setting the rate higher still works, so now this line looks like:
+
 
+
    POST_UP="iwconfig wlan0 rate 12M fixed"
+
  
 
Now calling;
 
Now calling;
  
    netfcg2 -c <wireless profile>
+
netfcg2 -c <wireless profile>
 
or  
 
or  
 
   netcfg-menu  
 
   netcfg-menu  
 
and choosing your profile works without extra commands.
 
and choosing your profile works without extra commands.
  
=== Method 2: Aircrack-ng patched driver ===
+
=== Lowering the txpower ===
Another method that works for some users are the Aircrack-ng patches for the rtl8187 driver. This driver can be installed by the [http://aur.archlinux.org/packages.php?ID=15375 rtl8187-ng] package from [[AUR]].
+
 
 +
You can try lowering the transmit power as well. This may save power as well:
 +
 
 +
iwconfig wlan0 txpower 5
 +
 
 +
or even as low as 0. Valid settings are from 0 to 20, auto and off for the stock kernel driver.
 +
 
 +
=== Setting rts and fragmentation thresholds ===
 +
 
 +
Default iwconfig options have rts and fragmentation thresholds off. These options are particularly useful when there are many adjacent APs or in a noisy environment.
 +
 
 +
The minimum value for fragmentation value is 256 and maximum is 2346. In many windows drivers the maximum is the default value:
 +
 
 +
iwconfig wlan0 frag 2346
 +
 
 +
For rts minimum is 0, maximum is 2347. Once again windows drivers use maximum as the default:
 +
 
 +
iwconfig wlan0 rts 2347
 +
 
 +
== Compat-wireless-patched ==
 +
 
 +
The [http://wireless.kernel.org/ Linux Wireless] project provides frequent stable releases of patched drivers for the latest kernels. These drivers fix the "fixed-channel -1" issue, whilst providing better injection.
 +
For further information and installation procedures please read the [[Wireless_Setup#compat-wireless-patched]] article.
 +
 
 +
== Using Ndiswrapper ==
  
=== Method 3: Using Ndiswrapper ===
 
 
If everything else fails, then you are left with using Ndiswrapper. Ndiswrapper takes Windows RTL8187 drivers and uses them to enable your card.
 
If everything else fails, then you are left with using Ndiswrapper. Ndiswrapper takes Windows RTL8187 drivers and uses them to enable your card.
  
Symptoms which suggest you may have better luck with Ndiswrapper:
+
'''Install ndiswrapper'''
 +
pacman -S ndiswrapper
  
* "iwlist wlan0 scan" results are irregular and/or don't show some APs.
+
'''Download the Windows drivers'''
* Everything seems to be working, except the DHCP request, which may just time out.
+
wget [http://db.tt/4NB0HbF6 http://db.tt/4NB0HbF6]
  
1. Install ndiswrapper:
+
'''Extract the drivers'''
    pacman -S ndiswrapper
+
unzip ndiswrapper.zip
  
2. Download the Windows drivers:
+
'''Unload the rtl8187 module'''
    wget http://www.kuratkull.com/ndiswrapper/ndisdrivers.tar.gz
+
modprobe -r rtl8187
  
3. Extract the drivers:
+
'''Remove any previously installed drivers (if any)'''
    gzip -dc ndisdrivers.tar.gz | tar xf -
+
  
4. If you have the rtl8187 module loaded, then do this:
+
ndiswrapper -r net8187b
    rmmod rtl8187
+
It is suggested that you remove previous ndiswrapper drivers, if you have installed them.
+
    ndiswrapper -l
+
    ndiswrapper -r <drivername>
+
  
Also add "ndiswrapper" and "!rtl8187" to /etc/rc.conf under MODULES - this will stop rtl8187 from loading on boot, and will enable ndiswrapper to load on boot.
+
'''Install the new drivers'''
  
5. Install the driver:
+
ndiswrapper -i ./ndiswrapper/net8187b.inf
If you have an older kernel(eg. older than 2.6.28.*), do:
+
  
    cd ./ndisdrivers/Win98-krnl24/
+
ndiswrapper -m
  
If you have a newer kernel (eg. 2.6.28.*), do:
+
depmod -a
+
    cd ./ndisdrivers/Win98seME-krnl28/
+
  
Proceed with:
+
'''Make sure that it is installed'''
    ndiswrapper -i net8187b.inf
+
 
    ndiswrapper -m
+
ndiswrapper -l
    modprobe ndiswrapper
+
 
 +
'''Try now loading the module'''
 +
 
 +
modprobe ndiswrapper
 +
 
 +
'''Kernel log shouldn't indicate any errors'''
 +
 
 +
dmesg | tail
 +
 
 +
'''If all steps are successful it should be visible now in the iwconfig interfaces list'''
 +
 
 +
iwconfig
 +
 
 +
'''Add ndiswrapper to the MODULES array in /etc/rc.conf'''
 +
 
 +
MODULES=(... powernow-k7 ndiswrapper ...)
 +
 
 +
'''Blacklist ''rtl8187'' in /etc/modprobe.conf.d/rtl8187.conf'''
 +
 
 +
blacklist rtl8187
  
 
Proceed to connect as you normally would.
 
Proceed to connect as you normally would.
 +
 +
{{Note|You may still have issues with disconnections, but in this case setting rates, rts and fragmentation thresholds actually work}}
  
 
=Misc Links=
 
=Misc Links=
*[http://rtl-wifi.sourceforge.net/ Project-page of the rtl-wifi driver project]
+
*[http://wireless.kernel.org/ The Linux Wireless project]
 +
*[http://aircrack-ng.org/doku.php?id=r8187 Aircrack-ng information for rtl8187 chips]

Revision as of 01:26, 6 December 2012


This page describes how to get the rtl8187 wifi-driver working

Note: The rtl8187 driver is in the kernel (thus the driver comes with the linux package)


The rtl8187 chip is made for usb-cards/dongles

It supports 802.11(a)/b/g and the following encryptions: WEP, WPA and WPA2

The driver's source is released under the GPL

Using and testing the driver/Troubleshooting

Make sure that you have loaded the rtl8187 module with

modprobe rtl8187

Then run

dmesg | grep rtl8187
You should see some output like this
 usbcore: registered new interface driver rtl8187 

If you see that line everything should be OK

Using the driver

If everything is right, you should have two new interfaces: wlan0 and wmaster0 If you do not see wlan0 just run

ifconfig wlan0 up

To list all available wifi-networks just run

iwlist wlan0 scan

For more information about configuring your wifi-network see here: http://wiki.archlinux.org/index.php/Wireless_Setup#Setup_and_Boot

What to do if your connection always times out?

The open source driver suffers from a lot of tx excessive retries and invalid misc errors for some unknown reason, resulting in a lot of packet loss and it keeps disconnecting, some times instantly.

Adjusting with iwconfig options

Lowering the rate

The solution can be found in this thread: https://bbs.archlinux.org/viewtopic.php?pid=299642

Just set the rate to 5.5

iwconfig wlan0 rate 5.5M auto

Fixed option should ensure, however, it doesn't change the rate on its own, thus making the connection a bit more stable:

iwconfig wlan0 rate 5.5M fixed 

Alternativelly find the $POST_UP option and append the above options to your profile config file:

POST_UP="iwconfig wlan0 rate 5.5M fixed"

Try various rates until you get the optimal setting, with no disconnection. In this case 12Mbits, as shown bellow:

POST_UP="iwconfig wlan0 rate 12M fixed"

Now calling;

netfcg2 -c <wireless profile>

or

  netcfg-menu 

and choosing your profile works without extra commands.

Lowering the txpower

You can try lowering the transmit power as well. This may save power as well:

iwconfig wlan0 txpower 5

or even as low as 0. Valid settings are from 0 to 20, auto and off for the stock kernel driver.

Setting rts and fragmentation thresholds

Default iwconfig options have rts and fragmentation thresholds off. These options are particularly useful when there are many adjacent APs or in a noisy environment.

The minimum value for fragmentation value is 256 and maximum is 2346. In many windows drivers the maximum is the default value:

iwconfig wlan0 frag 2346

For rts minimum is 0, maximum is 2347. Once again windows drivers use maximum as the default:

iwconfig wlan0 rts 2347

Compat-wireless-patched

The Linux Wireless project provides frequent stable releases of patched drivers for the latest kernels. These drivers fix the "fixed-channel -1" issue, whilst providing better injection. For further information and installation procedures please read the Wireless_Setup#compat-wireless-patched article.

Using Ndiswrapper

If everything else fails, then you are left with using Ndiswrapper. Ndiswrapper takes Windows RTL8187 drivers and uses them to enable your card.

Install ndiswrapper

pacman -S ndiswrapper

Download the Windows drivers

wget http://db.tt/4NB0HbF6

Extract the drivers

unzip ndiswrapper.zip

Unload the rtl8187 module

modprobe -r rtl8187

Remove any previously installed drivers (if any)

ndiswrapper -r net8187b

Install the new drivers

ndiswrapper -i ./ndiswrapper/net8187b.inf
ndiswrapper -m
depmod -a

Make sure that it is installed

ndiswrapper -l

Try now loading the module

modprobe ndiswrapper

Kernel log shouldn't indicate any errors

dmesg | tail

If all steps are successful it should be visible now in the iwconfig interfaces list

iwconfig

Add ndiswrapper to the MODULES array in /etc/rc.conf

MODULES=(... powernow-k7 ndiswrapper ...)

Blacklist rtl8187 in /etc/modprobe.conf.d/rtl8187.conf

blacklist rtl8187

Proceed to connect as you normally would.

Note: You may still have issues with disconnections, but in this case setting rates, rts and fragmentation thresholds actually work

Misc Links