Automatic setup for RTL8188CUS based wifi adapters

[metaljay]

This is what i have: http://www.amazon.co.uk/Edimax-EW-7811U ... y_ce_img_b

And it works perfect

Honestly mate, all you have todo
Install Squeeze image, this will create 2 partitions (1 of which isn't visible to windows/mac)
The one that is visible, copy the script to the root.

Login to your pi
Prior to running startx, type the command to run the script

[MrEngman]

run the script prior to running the 'startx' command.
In other words after logging in

Ah, I can't do that as after I have installed a linux distribution to my SD card, my win 7 laptop thinks the card needs formatted and shows no writeable area, anyway around it? TBH I'm really trying to get this -

http://www.amazon.co.uk/gp/product/B004 ... 00_s00_i00

Working with it. Someone said they had it working no problem plugged directly into the pi, with the debian script. What I want to do is use that script with RaspbMC as that's the one I really want on my pi permamently.

Any ideas how to go about it? I am a complete linux noob and everything I've found on google over the past week has either contradicted other stuff or confused me. Any chance someone could give me a step by step line (accessing raspbmc using winSCP with putty) commands I should be sending to it?

Sounds like your image is not written correctly. How did you write the image to start with?

If you've used something like windd (dd for windows) be careful. If any file paths used by dd has any spaces in it it will probably not work correctly and you will get a disk Windows wants to format.

e.g "C:\Downloads\Raspberry Pi\Debian6\debian6-19-04-2012.img" this has a space in it between Rapberry and Pi and will not work. Replace the spaces with minus (-) or underscore (_) . e.g."C:\Downloads\Raspberry_Pi\Debian6\debian6-19-04-2012.img".

Found this out when trying an image writer, fedora-arm-installer-1.0.0, that used dd.

[texy]

I prefered your first answer
T.

[DirkS]

What I want to do is use that script with RaspbMC as that's the one I really want on my pi permamently.

That will not work (at least not with the latest Raspmbc release).

AFAIK people are still trying to get several types of wifi adapters to work. I think yours is in the category that's being discussed here: http://forum.stmlabs.com/showthread.php?tid=780

Gr.
Dirk

[Lob0426]

I just installed Wheezy. I installed network-manager-gnome. Both my adapters (WG111v2 netgear and WUSB54GC v1 linksys) are working with no driver installation required. Network Manager sets my hidden SSID and my WEP pass for use in X and at commandline.

[MrEngman]

Hi Everyone,

The RTL8188CUS automatic installation script has been updated. I have made several changes to the script as follows.

1. The script can now configure the driver for unsecured, WEP or WPA/WPA2 networks. The script will now ask whether the network being connected to is unsecured, or uses WEP or WPA/WPA2 security and configures the driver accordingly. In line with this feature if the network selected is unsecured then it will not ask for a password.

2. When inputting the SSID, and PASSWORD if configuring for a secure network, it will ask you to confirm they are correct before installing. If you have typed in either one incorrectly you will have the opportunity to correct it before it is used in the installation.

3. The hotplug feature has now been made optional. You will be asked whether you want it installed or not.

4. The DHCP update has now been made optional. You will be asked whether you want it installed or not.

5. The script has been altered to ensure only the /etc/apt/sources.list file for the Debian6-19-04-2012 release is changed to correct an issue with duplication of package sources, and the sources.list file in any other image will remain unaltered, just in case someone tries to use the script with any other image rather than Debian6-19-04-2012.

6. I have changed the naming convention for the script updates and driver updates which should make life a little easier when an update occurs. The latest script will now be named "install-rtl8188cus-latest.sh" and the latest tarred driver file will be named "8192cu-latest.tar.gz".

Now, rather than hunting out the correct script and driver which have a date code in the name to use to apply the latest update, you will only need to download the script "install-rtl8188cus-latest.sh" and/or the latest driver "8192cu-latest.tar.gz" if you need to manually upgrade the driver. If there has been a change it will be incorporated into these files atomatically. Pointers to these files are in the wiki on this page.. Look at the links associated with the "Micronet SP907NS, 11N Wireless LAN USB Adapter" wifi adapter.

Before using the script please download and read the installation instructions. Apart from giving details of how to apply the installation the instructions contain important information regarding images that the drivers can be installed on and also contains pointers to some alternative scripts for images other than the Debian6-19-04-2012 image that the script was originally designed to work with.

Have fun and enjoy your Pi.

MrEngman

[fenyvesi]

The link seems to be incorrect to the Installation instructions.

George Fenyvesi

[MrEngman]

The link seems to be incorrect to the Installation instructions.

George Fenyvesi

Thank you. Now fixed.

[NickT]

I just installed Wheezy. I installed network-manager-gnome. Both my adapters (WG111v2 netgear and WUSB54GC v1 linksys) are working with no driver installation required. Network Manager sets my hidden SSID and my WEP pass for use in X and at commandline.

For the sake of your own security, it's highly inadvisable to use WEP encryption these days. It's easily crackable with basic Linux skills and publicly available tools. Googling for 'WEP' + 'security' will give you lots of reasons why you should switch to WPA or WPA2.

[metaljay]

So I can simply re run the new script over my existing image?

Or should I start fresh?

[fenyvesi]

Dear EngMan,

Your work and assistance is great. I managed to use a SWEEX branded Wireless 150N Nano dongle. (It looks like the Edimax Wireless Nano).

Thank you.

George Fenyvesi

[MrEngman]

So I can simply re run the new script over my existing image?

Or should I start fresh?

To do what?

The script is really for initial installation and you need a new image to do that. If you are upgrading then you should do that manually and it's not difficult, 5 commands required I think. There are instructions how to somewhere back in this thread, although there is rather a lot to look through. Handling upgrading is something I would like to add to the script although it's not straight forward to include due to the number of possible different scenarios.

[pjc123]

I just installed Wheezy. I installed network-manager-gnome. Both my adapters (WG111v2 netgear and WUSB54GC v1 linksys) are working with no driver installation required. Network Manager sets my hidden SSID and my WEP pass for use in X and at commandline.

Did you install the gnome desktop before installing network-manager-gnome, or does it work with the LXDE desktop?

[pjc123]

MrEngman

I have an AirLink101 (Model AWLL5088) that someone was able to get working with Debian squeeze way back on the first page of this thread. So I purchased one and I am trying to get it to work with wheezy but it is failing to connect with my router.

A little background:
a) I am using install-wheezy-beta-rtl8188cus-20120619.sh
b) An lsusb command correctly shows the adapter as a RTL8188CUS
c) dmesg is showing the adapter as a Realtek Wireless N USB Adapter
d) The 5V rail measured at test points TP1 and TP2 fluctuates between 4.89 and 4.94 volts, the lower end voltage when the wifi blue light is on (I suspect it is transmitting). The voltages are within the 5V +/- 5% acceptable limits. A keyboard is plugged into the other usb port. My power supply is capable of supplying 1000ma.
e) My router is a Mixed B/G router without N capability.
f) Way before running your script, I had previously done an apt-get-update and apt-get-upgrade.

1) First Problem- Your script took the "\" characters out of my router WPA2 password. No problem as I just added them to the file (Hopefully the operating system can read them properly. I have not seen a problem with any other devices that I have however). I went through your script line by line and everything else looks as if it was created properly in the filesystem (files, lines added to files, etc)

2) Second Problem- During the boot process, these are the messages I am getting related to the network. Could this mean that my router is not within range, or is it a different problem?

Configuring network interfaces...
ioctl[SIOCSIWAP] Operation not permitted
ioctl[SIOCSIWENCODEEXT] Invalid argument
ioctl[SIOCSIWENCODEEXT] Invalid argument
[ 24.837837] NET: Registered protocol family 10
[ 24.860725] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 24.875935] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Internet Systems Consortium DHCP Client 4.2.2

Listening on LPF/wlan0/XX:XX:XX:XX:XX:XX
Sending on LPF/wlan0/XX:XX:XX:XX:XX:XX
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
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.
Unable to obtain lease on first try. Exiting.
Failed to bring up wlan0.
done

[bightf]

Hello,

I'm quite new to the whole raspberry thing and I was searching for a reliable wifi solution when I saw this post.

I'm hesitating between the Netgear WNA1000M and the Edimax EW-7811UN, because both of them seem to work good with the script provided.

So, which one is the best buy and can someone confirm they work without a powered usb hub (i.e. directly connected to the RasPi) ?

Thank you !

[MrEngman]

Hi pjc123,

Think I've a way round one of the problems.

Right first problem 1.

Backslash characters "\" have special meaning in scripts, so if you want to use a backslash as as text character you need to replace a single backslash by a pair of backslashes.

I changed my network password on my wireless access point to include a single backslash character and edited the /etc/network/interfaces file to use the same string. My Pi would not connect I then changed the single backslash in the /etc/network/interfaces file to a pair of backslashes and, lo and behold, the Pi now connected to the network.

I think what is happening is that the info in the /etc/network/interfaces file is being used in a script so each single backslash must be replaced by a pair of backslashes. Just speculation on my part. I don't know for certain this is what is happening. Now for the interesting bit. In the installation script the PASSWORD has to be set up to put a pair of backslashes in the /etc/network/interfaces file for each backslash in the access point password. So to put a pair of backslashes into the /etc/network/interfaces file using the installation script each individual backslash has to be replaced by a pair of backslashes. If my sums are correct this means each backslash in the wifi access point password must be replaced by 4 consecutive backslashes in the password in the installation script. Isn't Linux/Unix fun? I think that should fix problem 1.

Change the password in /etc/network/interfaces replacing each backslash with a pair of backslashes and see what happens.

Problem 2.
I see an identical string of messages but excluding this one "ioctl[SIOCSIWENCODEEXT] Invalid argument" when my system boots although I am using squeeze not wheezy. I'm not sure why this should happen but there is a lot on the internet about it. I'm not sure if it is significant in your case. Need to fix the network password first. This site may be helpful in find out what is happening by logging wpa_supplicant.

See if fixing the backslash issue gets you connected first.

MrEngman

[pjc123]

MrEngman.

As I suspected, Debian does not like the slash either. Shell scripting, as you said is always a delight with all the various gotchas; I have spent more than a day on some of the more obscure problems in the past. I will try the extra slash later today and let you know what happens, and while I am at it check for any other special characters in the string that may cause problems. Since there is the potential of causing problems with my other Linux OS's, which I have not tested with my wifi dongles, I will probably just change the password and remove the slashes and update the associated devices (Roku, laptop, etc.). This is what you get for using a very secure password ! Considering that both WEP and WPA are crackable using injection anyway, all I am doing is making it harder for someone.

PJC

[MrEngman]

Hello,

I'm quite new to the whole raspberry thing and I was searching for a reliable wifi solution when I saw this post.

I'm hesitating between the Netgear WNA1000M and the Edimax EW-7811UN, because both of them seem to work good with the script provided.

So, which one is the best buy and can someone confirm they work without a powered usb hub (i.e. directly connected to the RasPi) ?

Thank you !

I use the Edimax EW-7811Un and Micronet SP907NS and I normally connect them directly to the Pi. Keyboard and mouse are on the hub - which takes no power from the Pi unlike many these days. The Edimax can take a lot of power. I've seen a max of ~260mA but this was connected directly to the Pi and didn't cause any problems. NOTE: I do have a hefty power supply powering the Pi (switched mode 5+V/5A), not a low power phone/battery charger and I can adjust the voltage from the PSU to ensure the voltage on the Pi is 5v. I normally use the Micronet SP907NS. This takes rather less power, max ~115mA. My Pi is generally running 24/7 without problems.

To run any wifi adapter directly connected to the Pi you need to ensure you have a high quality power supply with a short high quality cable supplying the power to the Pi.

[bightf]

Hello,

I'm quite new to the whole raspberry thing and I was searching for a reliable wifi solution when I saw this post.

I'm hesitating between the Netgear WNA1000M and the Edimax EW-7811UN, because both of them seem to work good with the script provided.

So, which one is the best buy and can someone confirm they work without a powered usb hub (i.e. directly connected to the RasPi) ?

Thank you !

I use the Edimax EW-7811Un and Micronet SP907NS and I normally connect them directly to the Pi. Keyboard and mouse are on the hub - which takes no power from the Pi unlike many these days. The Edimax can take a lot of power. I've seen a max of ~260mA but this was connected directly to the Pi and didn't cause any problems. NOTE: I do have a hefty power supply powering the Pi (switched mode 5+V/5A), not a low power phone/battery charger and I can adjust the voltage from the PSU to ensure the voltage on the Pi is 5v. I normally use the Micronet SP907NS. This takes rather less power, max ~115mA. My Pi is generally running 24/7 without problems.

To run any wifi adapter directly connected to the Pi you need to ensure you have a high quality power supply with a short high quality cable supplying the power to the Pi.

Hi, thank you for this very detailed answer !

I'm currently using a 5V/1.2A power supply, this is the one recommended by RadioSpares that I bought with the RasPi. Here is the link : http://uk.rs-online.com/web/p/external- ... s/7263053/

I already have a Logitech Unifying receiver directly connected on the Pi, it's for a Logitech k400 keyboard+touchpad.

So, do you think I will have enough power for both the RF receiver and a WiFi adapter ?

[bightf]

To complete my answer : a "lsusb -v" indicates the Logitech Unifying receiver takes a "MaxPower" of 98mA. Is this value reliable ?

I can't find the max power / current for the Netgear WiFi adapter, it seems like I'm gonna have to buy it and test by myself

[MrEngman]

MrEngman.

As I suspected, Debian does not like the slash either. Shell scripting, as you said is always a delight with all the various gotchas; I have spent more than a day on some of the more obscure problems in the past. I will try the extra slash later today and let you know what happens, and while I am at it check for any other special characters in the string that may cause problems. Since there is the potential of causing problems with my other Linux OS's, which I have not tested with my wifi dongles, I will probably just change the password and remove the slashes and update the associated devices (Roku, laptop, etc.). This is what you get for using a very secure password ! Considering that both WEP and WPA are crackable using injection anyway, all I am doing is making it harder for someone.

PJC

I've just run up wheezy and installed the latest wifi driver manually - all OK. then ran apt-get update and apt-get upgrade and still OK.

I am now seeing all the error messages you are gettingincluding "ioctl[SIOCSIWENCODEEXT] Invalid argument"

Installed rpi-update and ran that, rebooted and all is still OK. Wifi looking good.

So looks like the issue is almost certainly the backslashes, or rather ensuring the right number of backslashes are there, in your password.

[pjc123]

So looks like the issue is almost certainly the backslashes, or rather ensuring the right number of backslashes are there, in your password.

Sorry to say adding the extra slash did not work. I then made the password only 8 characters long with no special characters and that didn't work. I moved the pi upstairs to within a few feet of the router and that did not work. Now I am going to try the dongle on my windows computer to make sure it is working. Then I am going to take a look at the debugging web page you provided as well as see what logs I can dig up and debugging I can turn on.

[pjc123]

Sorry to say adding the extra slash did not work. I then made the password only 8 characters long with no special characters and that didn't work. I moved the pi upstairs to within a few feet of the router and that did not work. Now I am going to try the dongle on my windows computer to make sure it is working. Then I am going to take a look at the debugging web page you provided as well as see what logs I can dig up and debugging I can turn on.

Finally got it working. I tried the dongle out on my Windows 7 computer and it worked right away with plenty of signal strength and signal quality. So I was looking at the router settings and figured I would try to enable SSID broadcast, and that fixed the problem. That is something I do not want to enable because it helps a little security-wise. No other device I have ever hooked up to the router has had a problem with this......until the dreaded pi (actually I should blame either the Debian OS or the Realtek driver). I imagine there is no way around this until if and when some piece of software gets upgraded, but at least I am up and running. Also the double backslash works.

I do have another question for you. I have been holding off getting a hub because of so many bad reports of various hubs from people (Wifi not working, keyboards not working, not enough power, mysteriously powering the pi, nothing working, etc.). All I want is to plug my keyboard and mouse into the hub so I can keep the wifi dongle in the other usb port and of course I want a powered hub. You mentioned that is your setup and yours works (although I am not sure yours is powered), so could you give me a brand and model # (Unless it is a European model and there is no American equivalent because the power cord will be wrong and it will be a pain to order).

[MrEngman]

Good to hear you've got it working.

As far as connecting to an access point that doesn't transmit it's ssid. I can't see why it shouldn't be possible from a Linux system, just need to find the right application to use. I think you may need to look at using wpa_supplicant or some network manager to configure your wifi. I've been trying to use wpa_supplicant but can't get my system to work with it yet. Just don't have the experience I guess.

The hub I use is a very old Belkin F5U224, no longer manufactured. I cannot recommend any others. I have a small Logik L4THUB10 and I would recommend NOT to use one of those. It sucks power from the Pi even when powered from its own supply. Probably the same with other Logik hubs as well. AndI think a common problem with many hubs nowadays.

These days I think many so called powered hubs can be powered from the host port when its own supply is turned off. I would avoid these if you can. They will suck power from the host port if their own supply cannot supply enough and very likely feed current back into the Pi when the Pi is powered down and the hub is still powered. The trouble is finding out if a hub works this way before actually trying it. May be a search through the wiki may help. Look at the power supply ratings to start with. There is only one there I would concider from that list apart from the one I use, another Belkin, the F4U040 4 port hub. It has a power supply, 5v 2.6A, with sufficient capacity to provide 500mA to each slave port and some left over. There are other 4 port hubs and their PSU's only appear to be rated at 1A. Would keep well away from those. Same issue with the 7 and 10 port hubs with PSU's with insufficient capacity to supply all ports with max current at the same time with some spare to supply the hubs own logic.

[Dilligaf]

Just picked this up yesterday http://www.bestbuy.com/site/Dynex%22+-+ ... Id=2120061
for only $10.00 it comes with a 5v 2.1 a power supply. Power does not feed back through it's input. With the Pi plugged in to it's input and the Pi power usb plugged into it's output it powers the Pi with no problems, as of now I have had no problems with it