Unable to use RTL8187L USB wifi adapter.
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
Unable to use RTL8187L USB wifi adapter.
Here's some general information of what I am starting with.
Computer: Toshiba Satellite Pro 480cdt
4gb HD
32mb Ram
333mhz processor
Dumped Windows ME for Puppy linux version 4.1.2 Retro.
Wifi: G-Sky Wireless USB adapter with Realtek RTL8187L chipset
I was running Windows ME when I first receiver this laptop and ran the drivers just fine, no problem with install except for some error messages and some boot and shutdown issues that would constantly freeze the computer. So I figured that because Windows ME is such a bad operating system I would try a version of linux, after spending a few days researching I finally got Puppy installed to my Hard Drive. Everything has been working fine but I just can't seem to figure out how to configure my USB Wifi adapter.
At first I looked for my driver to see if it was preinstalled on puppy and this was not the case. So I attempted to download the drivers and install using ndiswrapper. I had my two .sys and .inf in a directory named (WinXP.inf). However upon attempting to install the driver I sometimes get an invalid driver or sometimes it works but fails to recognize my Wifi adapter. I'm using the same drivers for Windows ME except made for Windows XP so I'm not quite sure where I have gone wrong or where to go from here, even with extensive research on the internet and google.
Keep in mind that I am a begginner with Linux.
Also a little off topic I can't seem to get Puppy to be full screen on my laptop, and it sometimes hinders my use with applications, still looking for a fix on this.
Computer: Toshiba Satellite Pro 480cdt
4gb HD
32mb Ram
333mhz processor
Dumped Windows ME for Puppy linux version 4.1.2 Retro.
Wifi: G-Sky Wireless USB adapter with Realtek RTL8187L chipset
I was running Windows ME when I first receiver this laptop and ran the drivers just fine, no problem with install except for some error messages and some boot and shutdown issues that would constantly freeze the computer. So I figured that because Windows ME is such a bad operating system I would try a version of linux, after spending a few days researching I finally got Puppy installed to my Hard Drive. Everything has been working fine but I just can't seem to figure out how to configure my USB Wifi adapter.
At first I looked for my driver to see if it was preinstalled on puppy and this was not the case. So I attempted to download the drivers and install using ndiswrapper. I had my two .sys and .inf in a directory named (WinXP.inf). However upon attempting to install the driver I sometimes get an invalid driver or sometimes it works but fails to recognize my Wifi adapter. I'm using the same drivers for Windows ME except made for Windows XP so I'm not quite sure where I have gone wrong or where to go from here, even with extensive research on the internet and google.
Keep in mind that I am a begginner with Linux.
Also a little off topic I can't seem to get Puppy to be full screen on my laptop, and it sometimes hinders my use with applications, still looking for a fix on this.
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
Well according to this it schould work on 4.2
generic USB Wireless-G Adapter+Antenna
Puppy versions tested:
Interface: USB
Chipset:
Device Driver (name & source): Realtek RTL8187L driver
WiFi Protocols that work (A, B, G, N):
Security Protocols confirmed working (WEP, WPA, WPA2):
Configured with (Wizard, Ndiswrapper, Manual, Other?):
Posted by & date: Aitch on August 28, 2009
Posted: http://www.murga-linux.com/puppy/viewto ... 193#336193
Notes & Issues: one that's listed & works, & is cheap, US $17.44/offers/freepost [ebay], uses Realtek RTL8187L driver, and has an aerial to boost weak signals! - you still need to configure security settings though....[
So I shall try upgrading and see what happens.
generic USB Wireless-G Adapter+Antenna
Puppy versions tested:
Interface: USB
Chipset:
Device Driver (name & source): Realtek RTL8187L driver
WiFi Protocols that work (A, B, G, N):
Security Protocols confirmed working (WEP, WPA, WPA2):
Configured with (Wizard, Ndiswrapper, Manual, Other?):
Posted by & date: Aitch on August 28, 2009
Posted: http://www.murga-linux.com/puppy/viewto ... 193#336193
Notes & Issues: one that's listed & works, & is cheap, US $17.44/offers/freepost [ebay], uses Realtek RTL8187L driver, and has an aerial to boost weak signals! - you still need to configure security settings though....[
So I shall try upgrading and see what happens.
-
- Posts: 812
- Joined: Thu 04 Feb 2010, 13:16
- Location: Australia, 1999 Toshiba laptop, 512mb RAM, no HDD, 431 Retro & 421 Retro
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Your wifi device is supported by the rtl8187 Linux driver, but this driver was often unstable and failed to support the most recent "B" versions of the Realtek RTL8187 chipset until the 2.6.30.5 kernel. So you probably just need to move up to Puppy 4.3.x (not 4.3-retro) which has this kernel.
Generally, 2.14X handles USB wifi well.
Your particular wifi device doen't represent all USB wireless devices.looseSCREWorTWO wrote:When I tested 2.14X it didn't handle USB Wireless at all.
Generally, 2.14X handles USB wifi well.
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
Well last night the computer went into a frenzy and wouldn't start when trying to use 2.14 rc5, so I figure I would leave it and just boot up tomorrow and today it seems to be good. I'm trying it now to see if it worked, also upgrading to 4.2.1 did nothing.
tempestuous- I can't move up to 4.3.x because that is the first one I tried installing on my laptop, it would get to a certain part on boot up while loading and said it was looking for the pup431-.sfs file and it would never be found and I couldn't get it to boot, I had looked up the problem and found htat older computers needed the older kernel to run, that is why I went with the retro.
tempestuous- I can't move up to 4.3.x because that is the first one I tried installing on my laptop, it would get to a certain part on boot up while loading and said it was looking for the pup431-.sfs file and it would never be found and I couldn't get it to boot, I had looked up the problem and found htat older computers needed the older kernel to run, that is why I went with the retro.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
If you need to stick with an earlier kernel, I compiled an updated (but not entirely stable) r8187 driver
for Puppy 4.1/4.2 (not retro) with the 2.6.25.15 kernel -
http://www.murga-linux.com/puppy/viewto ... 339#252339
or for Puppy 2.12-2.16 with the 2.6.18.1 kernel, get the rtl8187B-k2.6.18.1.pet from
http://dotpups.de/dotpups/Wifi/drivers- ... 2-to-2.14/
for Puppy 4.1/4.2 (not retro) with the 2.6.25.15 kernel -
http://www.murga-linux.com/puppy/viewto ... 339#252339
or for Puppy 2.12-2.16 with the 2.6.18.1 kernel, get the rtl8187B-k2.6.18.1.pet from
http://dotpups.de/dotpups/Wifi/drivers- ... 2-to-2.14/
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
So i added the rtl8187B-k2.6.18.1.pet and it says that the driver has installed successfully. Then a text file comes up explaining that my device should be recognized but it still doesn't seem to be and when I try to load it manually I can't find it under the modules list. Where do I go from here?
Also it says you can do it manually but where exactly do I type those codes in?
Also it says you can do it manually but where exactly do I type those codes in?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Some manual configuration of the r8187 driver is necessary because I compiled it back in the days before Puppy's current Network Wizard
... but wait. We still don't know the exact brand/model of your device, and more importantly its USB device ID, so much of what we're discussing is speculation.
I need you to positively identify your device ID. Please plug in your USB device, then run this command (in rxvt) -
then report the "Vendor" and "ProdID" values for your wifi device.
... but wait. We still don't know the exact brand/model of your device, and more importantly its USB device ID, so much of what we're discussing is speculation.
I need you to positively identify your device ID. Please plug in your USB device, then run this command (in rxvt) -
Code: Select all
cat /proc/bus/usb/devices
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
I had 2 different vendors and Prod id showes up, this is what came up.
First sectoin
Second section,
First sectoin
Code: Select all
Vendor=0000
ProdID=0000
Code: Select all
Vendor=Obda
ProdID=8187
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
USB device ID 0bda:8187 is one of the earlier Realtek USB chipsets, probably not the "B" version,
but since you have already installed "B" dotpet, let's try it.
The instructions were launched when you installed the dotpet, and you can find them at /root/my-applications/rtl8187B-README.txt
but I now realise the instructions are not quite right. The r8187 driver may have automatically loaded without the other sub-modules it relies upon.
So the first thing to do is unload the driver, as such -
Now load all related modules, and the main driver, like this -
now check if an interface has successfully been created -
If you don't see "wlan0" (your wifi interface) listed, then you probably need to install the other (non-"B") driver -
http://dotpups.de/dotpups/Wifi/drivers- ... 6.18.1.pet
reboot, and start again.
But if you do see "wlan0" listed, go ahead and bring up the interface -
then you can run the Network Wizard to configure your wifi connection.
but since you have already installed "B" dotpet, let's try it.
The instructions were launched when you installed the dotpet, and you can find them at /root/my-applications/rtl8187B-README.txt
but I now realise the instructions are not quite right. The r8187 driver may have automatically loaded without the other sub-modules it relies upon.
So the first thing to do is unload the driver, as such -
Code: Select all
rmmod r8187
Code: Select all
modprobe ieee80211_crypt-rtl
modprobe ieee80211_crypt_wep-rtl
modprobe ieee80211_crypt_tkip-rtl
modprobe ieee80211_crypt_ccmp-rtl
modprobe ieee80211-rtl
modprobe r8187
Code: Select all
ifconfig -a
http://dotpups.de/dotpups/Wifi/drivers- ... 6.18.1.pet
reboot, and start again.
But if you do see "wlan0" listed, go ahead and bring up the interface -
Code: Select all
ifconfig wlan0 up
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
Everything seemed to work up until I went to the networking wizard, I setup my wireless internet connection and it says that the connection fails even when moving right next to my router so it's not a range issue. Also the driver never stays installed after shutdown so I have to load it each time I boot the computer. Any command to keep it from doing this?
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
So I've had some spare time to work on it so I tried to setup my wifi through the command line. While entering my Wep key I kept getting messages even with trying the S:. So I entered "dmesg l grep orinoco" as well as dmesg and I kept getting error messages saying that ieeemodprobe8187_crypt_wep and the kernel is tainted. Also I kept getting other messages saying "error for wireless 'Set Encode' (8b2a). I will get a full mode list tomorrow for more information on my situation.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
In response to a private message from camarokid201:
First I need to repeat my earlier assertion in this forum thread that the r8187 driver for older kernel versions, such as the one in Puppy 2.14, is generally unstable and unreliable. You would be better off trying to get your device working with Puppy 4.2.x (not 4.2-retro).
But if you still want to persist with 2.14X ...
First install the correct driver version. As I understand it, you have rtl8187B-k2.6.18.1.pet installed, which is wrong because yours is not the "B" version of chipset.
Install rtl8187-k2.6.18.1.pet
from http://dotpups.de/dotpups/Wifi/drivers- ... 2-to-2.14/
This will overwrite the other version of the driver.
Now unplug your USB wifi device, and reboot. Once rebooted, you can plug in your USB device again.
There's a fair chance that Puppy will automatically load the correct driver, but it's worth going through the process manually just to be sure. Load the relevant modules, in this order -
If there are any error messages, you should report them. Obviously, I need to know exactly which command yielded the error, and the exact details of the error message.
Now you can try to connect to a wifi access point, using the Network Wizard. It would make common sense to configure your wifi router for NO encryption, and attempt a connection in this unencrypted state. This is common practice with all operating systems, not just Linux.
Once you know this works, you can re-enable encryption at the router, and reconfigure the Network Wizard to connect using encryption. Bear in mind that WEP encryption is more likely to successful with this driver than WPA encryption.
First I need to repeat my earlier assertion in this forum thread that the r8187 driver for older kernel versions, such as the one in Puppy 2.14, is generally unstable and unreliable. You would be better off trying to get your device working with Puppy 4.2.x (not 4.2-retro).
But if you still want to persist with 2.14X ...
First install the correct driver version. As I understand it, you have rtl8187B-k2.6.18.1.pet installed, which is wrong because yours is not the "B" version of chipset.
Install rtl8187-k2.6.18.1.pet
from http://dotpups.de/dotpups/Wifi/drivers- ... 2-to-2.14/
This will overwrite the other version of the driver.
Now unplug your USB wifi device, and reboot. Once rebooted, you can plug in your USB device again.
There's a fair chance that Puppy will automatically load the correct driver, but it's worth going through the process manually just to be sure. Load the relevant modules, in this order -
Code: Select all
modprobe ieee80211_crypt-rtl
modprobe ieee80211_crypt_wep-rtl
modprobe ieee80211_crypt_tkip-rtl
modprobe ieee80211_crypt_ccmp-rtl
modprobe ieee80211-rtl
modprobe r8187
Now you can try to connect to a wifi access point, using the Network Wizard. It would make common sense to configure your wifi router for NO encryption, and attempt a connection in this unencrypted state. This is common practice with all operating systems, not just Linux.
Once you know this works, you can re-enable encryption at the router, and reconfigure the Network Wizard to connect using encryption. Bear in mind that WEP encryption is more likely to successful with this driver than WPA encryption.
-
- Posts: 16
- Joined: Mon 07 Jun 2010, 18:06
I am useing the rtl8187 driver.
When using the command (ifconfig wlan0 up) it made everything not work for me so I didn't include it this time. It recognizes the live network and everything. So i tried it with no encryption and it worked great but was super slow, (100 times slower than Windows ME!) this allowed me to access the internet. Then I tried it with WEP encryption and it recognizes the live network but won't connect to the internet still.
When using the command (ifconfig wlan0 up) it made everything not work for me so I didn't include it this time. It recognizes the live network and everything. So i tried it with no encryption and it worked great but was super slow, (100 times slower than Windows ME!) this allowed me to access the internet. Then I tried it with WEP encryption and it recognizes the live network but won't connect to the internet still.