Wireless network conectivity

THIS IS A MUST ADD TO THE WIKI! (it is already there but is not advertised very well)

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=6256&hilit=edimax&start=600 

http://dl.dropbox.com/u/80256631/install-rtl8188cus.txt

and

http://dl.dropbox.com/u/80256631/install-rtl8188cus-latest.sh

These solved all my problems in less than 15minutes.  Keep in mind that it only works for some adapters, which are listed on the 1st link.

The script also installs all the latest updates for the RPi (rpi-update) as well as setting up your wireless.

Great job,  MrEngman

I still wonder how to install my other device though.  So if anyone finds this out, please let me know (it is not really that important now).

Fergus.

8192cu: disagrees about version of symbol <name of part>

8192cu: Unknown symbol <name of part> (err -22)

 

...by deleting the driver (8192cu.ko file).

 

Which leads me to suspect that the RPi s/ware didn't like it.

What those messages tell you is that the module you compiled was built against a different kernel than the one you're running. Sometimes this can be as simple as having the exact same kernel source, but just one option has been changed in the .config

To build external modules you need the correct kernel source tree and the .config from the running kernel. You can usually obtain this from the /proc/config.gz file.

It's difficult to cover every possible problem in just a few lines, but here's a basic outline of how it should be done - no idea if this would work for you though

cd /home/pi  - or wherever

git clone https://github.com/raspberrypi/linux.git - this should leave you with a 'linux' directory eventually, it will take some time

cd linux

cp /proc/config.gz .   - copy config of running kernel

gunzip config.gz       - unpack config

mv config .config      - move it to (dot)config that leading . is necessary !

make oldconfig         - this configures the kernel source with the config of your running kernel

if make oldconfig asks lots of confusing questions you don't know how to answer, try make silentoldconfig instead

at this point you can go and build your driver, but you must make sure it uses the kernel source tree you've just configured. You likely need to change two symlinks under /lib/modules/* for this to work properly like this:

rm /lib/modules/`uname -r`/build

rm /lib/modules/`uname -r`/source

ln -s /home/pi/linux /lib/modules/`uname -r`/build

ln -s /home/pi/linux /lib/modules/`uname -r`/source

now build and install your external driver module.

It's sometimes the case that you'll end up with two conflicting versions of a driver, you can search for them like this

find /lib/modules/`uname -r`/ -name 8192cu.ko

if that finds more than one, delete all of them and then re-run the drivers install.

When you're done, run depmod -a hopefully the driver install did it for you, but sometimes they don't.

You should then be able to run modprobe 8192cu to load the module. dmesg will show you any errors.

I hope some of the above helps, but no guarantees - too many assumptions in there for guarantees

Okay, thanks for the help, I really appreciate it Drew and I'll give this a go next time I hook up my Pi up to the internet. Hopefully it will work on adafruit's image because I didn't have much luck with it on Rasbian Wheezy, but it's worth a try.

Edit - Using the WICD software on the adafruit's image I successfully managed to connect to my router using a dongle. Thanks for the help, my Raspberry Pi can now connect to to the internet without an Ethernet cable (which has been an issue to me for quite a while)

Message was edited by: Ahmad A

selsinork wrote:

 

8192cu: disagrees about version of symbol <name of part>

8192cu: Unknown symbol <name of part> (err -22)

 

...by deleting the driver (8192cu.ko file).

 

Which leads me to suspect that the RPi s/ware didn't like it.

What those messages tell you is that the module you compiled was built against a different kernel than the one you're running. Sometimes this can be as simple as having the exact same kernel source, but just one option has been changed in the .config

 

To build external modules you need the correct kernel source tree and the .config from the running kernel. You can usually obtain this from the /proc/config.gz file.

 

It's difficult to cover every possible problem in just a few lines, but here's a basic outline of how it should be done - no idea if this would work for you though

 

cd /home/pi  - or wherever

git clone https://github.com/raspberrypi/linux.git - this should leave you with a 'linux' directory eventually, it will take some time

cd linux

cp /proc/config.gz .   - copy config of running kernel

gunzip config.gz       - unpack config

mv config .config      - move it to (dot)config that leading . is necessary !

make oldconfig         - this configures the kernel source with the config of your running kernel

 

if make oldconfig asks lots of confusing questions you don't know how to answer, try make silentoldconfig instead

 

at this point you can go and build your driver, but you must make sure it uses the kernel source tree you've just configured. You likely need to change two symlinks under /lib/modules/* for this to work properly like this:

 

rm /lib/modules/`uname -r`/build

rm /lib/modules/`uname -r`/source

ln -s /home/pi/linux /lib/modules/`uname -r`/build

ln -s /home/pi/linux /lib/modules/`uname -r`/source

 

now build and install your external driver module.

 

It's sometimes the case that you'll end up with two conflicting versions of a driver, you can search for them like this

 

find /lib/modules/`uname -r`/ -name 8192cu.ko

 

if that finds more than one, delete all of them and then re-run the drivers install.

 

When you're done, run depmod -a hopefully the driver install did it for you, but sometimes they don't.

 

You should then be able to run modprobe 8192cu to load the module. dmesg will show you any errors.

 

I hope some of the above helps, but no guarantees - too many assumptions in there for guarantees

I am a linux n00b,  I read something and think that was what the problem could be. Anyway, the problems are all solved for me anyway.

thanks for the help.

Message was edited by: Fergus Byrne

YEPPY!!

I worked it out after 6 months of trouble.

I found these instructions: http://elinux.org/RPi_Ralink_WLAN_devices

...Which I then used to install the card as my second Wireless interface.

Install the wpasupplicant and the ralink firmware:

1) sudo apt-get install wpasupplicant

2) sudo apt-get install firmware-ralink

Restrict access to /etc/interfaces so only root can read it (in this method, this file will contain your network password):

3) sudo chmod 0600 /etc/network/interfaces

Edit you /etc/network/interfaces:

4) sudo nano /etc/network/interfaces

5) The file already contains the configuration for eth0 (your Ethernet port) and looks something like this:

auto eth0 iface eth0 inet dhcp  

add the following lines below, enter you network name (ssid) and password:

iface wlan0 inet dhcp wpa-ssid <your network ssid here>  wpa-psk <your network password>  

6) save the file.

The network interface will connect every time the RPi boots up. To connect it now manually, run:

7) sudo ifup wlan0

I hope someone can now add this to the wiki as a working adapter.

Ralink Technology, Corp. RT2870 Wireless Adapter

ID: 148f:2870

Must be used with a powered hub and works out-of-the-box with Raspbian (August 16th 2012 --> From Raspberrypi.org Download page)

The only real instructions required are:

1. Image card and go through normal set-up

2. Plug in card and confirm that it is what it says it is using "lsusb" command

3. Type in "sudo nano /etc/network/interfaces"

4. Add the following lines:

auto lo

 

iface lo inet loopback

iface eth0 inet dhcp

 

allow-hotplug wlan0

 

auto wlan0

 

iface wlan0 dhcp

wpa-ssid <insert name of your ssid here using inverted commas " ">

wpa-psk < insert password of access point here using inverted commas " ">

5. Use the command "sudo ifup wlan0"

6. Let the device connect

7. You should be connected.

Thanks for all the help.

This problem is now SOLVED.

Fergus.