HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

**hypoluxa68** · August 13th, 2008

thanks for your help. still trying to figure out all this linux stuff. hope to be wireless soon

**maxy04** · August 15th, 2008

excuse me for the question, i'm italian and i can't understand all you wrote.
i have an RTL8187B, and i use wpa-tkip.
can i use wpa with that card and ndiswrapper?
i tryed the driver from cuervo and win98 drivers + ndiswrapper, but either say "wpa is not supported".

**Tom--d** · August 15th, 2008

Originally Posted by maxy04

excuse me for the question, i'm italian and i can't understand all you wrote.
i have an RTL8187B, and i use wpa-tkip.
can i use wpa with that card and ndiswrapper?
i tryed the driver from cuervo and win98 drivers + ndiswrapper, but either say "wpa is not supported".

Do not use the drivers from Cuervo. They are very very very buggy.

The Win98 Windows Driver (which is on the 3rd post I think (I made it as an attachment)..download that. Install that Driver with Ndiswrapper. (Just follow the 1st post on this thread).

I have used WPA Passphrase on it. I don't know about tkip as I only have WEP at my home wireless network. Try it and find out.
Post back here if you need any more help.

**Mincher** · August 28th, 2008

Hi,

I'm investigating this to try and get my wireless working (Toshiba Satellite L40-18Z). No luck as of yet.

Just to make you aware, my wireless device seems to link to wlan1 rather than wlan0.

**Tom--d** · August 28th, 2008

Originally Posted by Mincher

Hi,

I'm investigating this to try and get my wireless working (Toshiba Satellite L40-18Z). No luck as of yet.

Just to make you aware, my wireless device seems to link to wlan1 rather than wlan0.

That doesn't matter, at all. All it means is that you have used another wireless card and which is the name of wlan0.
Your other wireless card is wlan1.

JUST make sure, for the RTL8187B card, use the right name. wlan0/wlan1

**aa_siempre** · August 30th, 2008

Hi there. I've managed to follow your directions perfectly (I have an 8197, same Toshiba laptop as OP). Windows Wireless Drivers reports that the hardware is present, so obviously it's all going well. Wrong.

I have a 64-bit machine - both drivers report that the hardware is detected. I'm running KDE, which makes the latter part of your directions...different.

When I open the KDE network manager, it doesn't detect any wifi interface.
I tried using wifi-radar, but that won't even start.

Any suggestions anybody?

**Tom--d** · August 30th, 2008

Originally Posted by aa_siempre

Hi there. I've managed to follow your directions perfectly (I have an 8197, same Toshiba laptop as OP). Windows Wireless Drivers reports that the hardware is present, so obviously it's all going well. Wrong.

I have a 64-bit machine - both drivers report that the hardware is detected. I'm running KDE, which makes the latter part of your directions...different.

When I open the KDE network manager, it doesn't detect any wifi interface.
I tried using wifi-radar, but that won't even start.

Any suggestions anybody?

There are a few things around this

Post the outcome of:

Code:

iwconfig

then

Code:

sudo ifconfig wlan0 up && iwconfig

**u_lone** · August 31st, 2008

Hi,

I have a Toshiba A300D-14D. Here is the lsusb outcome:

Code:

Bus 006 Device 002: ID 0ea0:2168 Ours Technology, Inc. Transcend JetFlash 2.0 / Astone USB Drive
Bus 006 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 005 Device 004: ID 0bda:8197 Realtek Semiconductor Corp. 
Bus 005 Device 003: ID 04f2:b008 Chicony Electronics Co., Ltd 
Bus 005 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 004: ID 15ca:00c3  
Bus 001 Device 001: ID 0000:0000

I've followed the steps. It seems to work because after I go System > Admin > Windows Wireless Drivers and install the driver, it says:

net8187b
Hardware Present: Yes

As the Network Manager was not working, I've installed the wifi-radar. But it is not working too.

Here some outcome...

Code:

$ ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2240 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2240 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:117360 (114.6 KB)  TX bytes:117360 (114.6 KB)

wlan0     Link encap:Ethernet  HWaddr 00:16:44:e5:9b:48  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0:avahi Link encap:Ethernet  HWaddr 00:16:44:e5:9b:48  
          inet addr:169.254.7.34  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1

Code:

$ iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Bit Rate:54 Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Code:

$ lshw -C network
WARNING: you should run this program as super-user.
  *-network
       description: Wireless interface
       physical id: 2
       logical name: wlan0
       serial: 00:16:44:e5:9b:48
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=ndiswrapper+net8187b driverversion=1.52+Realtek Semiconductor Corp. multicast=yes wireless=IEEE 802.11g

Code:

$ iwlist scan
lo        Interface doesn't support scanning.

wlan0     No scan results

I've also followed this thread and on the last step (sudo dhclient wlan0) I got this:

Code:

There is already a pid file /var/run/dhclient.pid with pid 7538
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:44:e5:9b:48
Sending on   LPF/wlan0/00:16:44:e5:9b:48
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

And nothing more happens.

I don't know how WiFi Radar was suppose to work, but I had to put my connection manually and after that try to connect. It try to acquire an IP, but 30 seconds later it stops.

**Tom--d** · August 31st, 2008

Originally Posted by u_lone

Hi,

I have a Toshiba A300D-14D. Here is the lsusb outcome:

Code:

Bus 006 Device 002: ID 0ea0:2168 Ours Technology, Inc. Transcend JetFlash 2.0 / Astone USB Drive
Bus 006 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 005 Device 004: ID 0bda:8197 Realtek Semiconductor Corp. 
Bus 005 Device 003: ID 04f2:b008 Chicony Electronics Co., Ltd 
Bus 005 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 004: ID 15ca:00c3  
Bus 001 Device 001: ID 0000:0000

I've followed the steps. It seems to work because after I go System > Admin > Windows Wireless Drivers and install the driver, it says:

net8187b
Hardware Present: Yes

As the Network Manager was not working, I've installed the wifi-radar. But it is not working too.

Here some outcome...

Code:

$ ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2240 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2240 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:117360 (114.6 KB)  TX bytes:117360 (114.6 KB)

wlan0     Link encap:Ethernet  HWaddr 00:16:44:e5:9b:48  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0:avahi Link encap:Ethernet  HWaddr 00:16:44:e5:9b:48  
          inet addr:169.254.7.34  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1

Code:

$ iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Bit Rate:54 Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Code:

$ lshw -C network
WARNING: you should run this program as super-user.
  *-network
       description: Wireless interface
       physical id: 2
       logical name: wlan0
       serial: 00:16:44:e5:9b:48
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=ndiswrapper+net8187b driverversion=1.52+Realtek Semiconductor Corp. multicast=yes wireless=IEEE 802.11g

Code:

$ iwlist scan
lo        Interface doesn't support scanning.

wlan0     No scan results

I've also followed this thread and on the last step (sudo dhclient wlan0) I got this:

Code:

There is already a pid file /var/run/dhclient.pid with pid 7538
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:44:e5:9b:48
Sending on   LPF/wlan0/00:16:44:e5:9b:48
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

And nothing more happens.

I don't know how WiFi Radar was suppose to work, but I had to put my connection manually and after that try to connect. It try to acquire an IP, but 30 seconds later it stops.

Wifi Radar will not work.
You will need iwconfig to work and dhclient but I see it doesn't.

How about try other Drivers and modify them? (like the Windows XP one Windows ME etc. (Not Vista, Nidswarpper doesn't have support for them, yet).

**u_lone** · August 31st, 2008

Originally Posted by Tom--d

Wifi Radar will not work.
You will need iwconfig to work and dhclient but I see it doesn't.

How about try other Drivers and modify them? (like the Windows XP one Windows ME etc. (Not Vista, Nidswarpper doesn't have support for them, yet).

It didn't work too.

I've also tried to change the approach following this, but didn't work too. I got an error on this step:

Code:

$ sudo ./wlan0up
insmod: can't read 'ieee80211_crypt-rtl.ko': No such file or directory
insmod: can't read 'ieee80211_crypt_wep-rtl.ko': No such file or directory
insmod: can't read 'ieee80211_crypt_tkip-rtl.ko': No such file or directory
insmod: can't read 'ieee80211_crypt_ccmp-rtl.ko': No such file or directory
insmod: can't read 'ieee80211-rtl.ko': No such file or directory
insmod: can't read 'r8187.ko': No such file or directory

Thread: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Thread Tools

Display

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Re: HOWTO: Get RTL8187B (ID: 8197) Working. Step by Step

Bookmarks

Bookmarks

Posting Permissions