LinuxQuestions.org HCL - 8187B integrated USB Wireless interface controller

BobNutfield · 09-24-2008, 09:13 AM

When I first purchased this laptop in March 2008, I had studied the components and believed them to be completely Linux friendly. The RTL8187B internal USB chipset included with this laptop confused me because there were native Linux kernel drivers already available for the RTL8187, so I assumed this would be compatible. But as it turned out, this RTL8187B is not compatible with the RTL8187 driver. The RTL8187 will recognize the chipset, but will not connect with it. And, since it is an internal USB connection, lspci would not find it. So, I set out to get it going with Ndiswrapper. This took some investigation, but the Ndiswrapper solution is here:

http://www.linuxquestions.org/questions/linux-wireless-networking-41/configuring-a-rtl8187b-wireless-card-on-a-toshiba-satellite-a215-s5802-in-ubuntu-7.10-631453/?highlight=RTL8187B

It was very easy to get it going in Slackware 12.1 with Ndiswrapper using this solution. And, like most things in Slackware, it has been very reliable and has never failed. I simply put the config commands (iwconfig commands) in /etc/rc.local and it is available at boot. I have used the same method to get this chipset working with Ndiswrapper in three different distros (Slackware, Ubuntu and Puppy).

I had read somewhere on the net (don't remember where) that native Linux support would be included with the release of kernel 2.6.27. As of this date (September 2008), 2.6.27 is still in rc status. I downloaded and compiled this kernel and can confirm that this kernel does in fact have native support for this chipset and it worked right away with this driver. I installed this kernel just as a test to see if the new driver did in fact work, but will not use it as my default kernel until it is released officially and it should be noted that dmesg notifies that this driver is still experimental and the user does so at their own risk. I have had no issues with it, and it provides a stronger signal than I got with ndiswrapper.

Slackware has always been the most stable and reliable distro for me, and now, with ALL of my hardware natively supported, I couldn't be more pleased.

portamenteff · 12-23-2008, 01:16 AM

Since I upgraded to the Intrepid Ibex with the newer kernel, the thing just worked from the Live CD on. It did not work with AMD64 bit Ubuntu 8.10 though. It never worked before with earlier kernel images either. I spent dozens of hours working the problem in forums, and IRC channels.
It works now with only minor problems. When surfing with heavy traffic, lots of requests from my machine, it fails. I just disable wireless, (wlan0down)wait about a minute, then enable wireless, (wlan0up) and it finds the same network I was connected to at the time it failed.
WPA, WEP, they all have worked so far.
Great job you wifi driver builders, you unsung heroes!

lugoteehalt · 01-10-2010, 05:48 AM

lsusb:

Code:

Bus 001 Device 005: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
  idVendor           0x0bda Realtek Semiconductor Corp.
  iManufacturer           1 Manufacturer_Realtek

To make two points:

1/ I have a stick-type thing containing said wireless that plugs into an external USB port. It is called a Thomson TG123g. It gets sent to you if you subscribe to Thomson Broadband in the UK.

2/ Using Debian, the way, perhaps not the only way, to get it to work is to install the latest backport kernel. The process is described here: http://wiki.debian.org/rtl818x . The only thing I would add is that it was necessary to log into the router's web site and provide the password while the configuration procedure took place.