Wireless network conectivity

If your adaptor uses Broadcom chipset you may need to install a piece of firmware to make it work. I had a similar problem with my Linux netbook that had Ralink wifi. It booted up but said that there was no WiFi as no firmware was loaded! After much searching the solution is at http://linuxwireless.org/en/users/Drivers/b43.

The B43 package installs the firmware needed to run the Broadcom chipset. As its not GPL it can't be released with any Linux package, but is able to be extracted from the Windows driver. This package is already to go, just install!

I required the firmware-b43-installer package. Not sure if it's in the RasPi repositories as I haven't got mine to play with yet... :-( But the above site it fairly comprehensive!

Hope it works.

i have had issues with broadcom on various laptops using different distro's of linux, this is the best solution i have found so far. i also cant confirm at the moment if the b43 firmware is in the repositories. i will check tonight and see if it is.

i cant actually try this on the R-Pi as i dont have a USB wifi adapter with the broadcom chipset.

http://ubuntuforums.org/showpost.php?p=10527475&postcount=5

hope this helps.

Hello Fergus, although not an answer to the question directly above, have you had a look at the Adafruit distro for the Pi ? From what I remember reading, this has drivers built in for some wireless cards andf may be worth giving a go with your current usb adaptor ?

Morgaine has posted in this forum with links to the distro.

Trying to answer your actual question, have a look at the drivers that come with the adaptor (even if you have got it yet, you can normally find a web page that will supply you the drivers, hopefully from the place you are buying it from) for Windows, and they will give a fair idea. BE something like Drivers\windows\realtek or hopefully something equally as useful.

Steve

I ahev the drivers, I just can't install them becasue I am a Linux n00b.

Could you help with this and this would solve my problem.

Fergus

See: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=13482&p=143746#p143746 for files that I need help with.

Fergus Byrne wrote:

 

I ahev the drivers, I just can't install them becasue I am a Linux n00b.

 

Could you help with this and this would solve my problem.

 

Fergus

 

See: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=45&t=13482&p=143746#p143746 for files that I need help with.

Here is the instructions from the readme file that I don't understand/can't find the correct agruments to fill-in.  Could you PLEASE fill-in what I can't and then post back here.  please .

          define the linux kernel source include file path LINUX_SRC

                     modify to meet your need.

3> In os/linux/config.mk

          define the GCC and LD of the target machine

          define the compiler flags CFLAGS

          modify to meet your need.

          ** Build for being controlled by NetworkManager or wpa_supplicant wext functions

             Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'.

             => #>cd wpa_supplicant-x.x

             => #>./wpa_supplicant -Dwext -ira0 -c wpa_supplicant.conf -d

          ** Build for being controlled by WpaSupplicant with Ralink Driver

             Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n'.

             => #>cd wpa_supplicant-0.5.7

             => #>./wpa_supplicant -Dralink -ira0 -c wpa_supplicant.conf -d

4> $make

          # compile driver source code

          # To fix "error: too few arguments to function ¡¥iwe_stream_add_event"

            => $patch -i os/linux/sta_ioctl.c.patch os/linux/sta_ioctl.c

5> $cp RT2870STA.dat  /etc/Wireless/RT2870STA/RT2870STA.dat

6> load driver, go to "os/linux/" directory.

    #[kernel 2.4]

    #    $/sbin/insmod rt2870sta.o

    #    $/sbin/ifconfig ra0 inet YOUR_IP up

    #[kernel 2.6]

    #    $/sbin/insmod rt2870sta.ko

    #    $/sbin/ifconfig ra0 inet YOUR_IP up

7> unload driver   

    $/sbin/ifconfig ra0 down

          $/sbin/rmmod rt2870sta

Hello Fergus, i'm afraid as I said above, i'm very much a Linux noob too, and other than looking like those instructions are for re-compiling the kernal with the drivers included (and even that is probably wrong) I can't help much

All I can say is that to get my USB stick working, I didn't have to do any this, just the instructions I posted a way back up this thread. I think there must be an easier way than doing the above.

Thats ok.  but I found this site which looks interesting, I am posting it here so I can find it later

http://linux.die.net/man/8/iwconfig

For fixing a file I messed up.

http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29

I bought the Edimax EW-7811Un but I need help setting it up, Steve, could you please help me with this one.  The RPi wiki says that it is verified but there is no guide to set-up this device for Raspbian.  I found this guide: http://www.ctrl-alt-del.cc/2012/05/raspberry-pi-meets-edimax-ew-7811un-wireless-ada.html but it has not worked for my RPi.  I think it has something to do with me not being able to get the rpi-update thing.  I tried to get this but failed.  Everytime I run rpi-update it returns:

/usr/bin/rpi-update: line 1: syntax error near unexpected token `newline'

/usr/bin/rpi-update: line 1: `<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Trans                                                                             itional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">'

Can this be fixed so that I can update the firmware?

Wireless card help would be nice as well .

I noticed from the link that Edimax uses the rtl8192cu driver.  I have another adapter (Asus USB-N13) which uses that driver and it did not work by default with the current Raspbian Wheezy image.  However, it did work ok with Adafruit's new image as it includes that driver, so you may want to give that a try: http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/occidentalis-v0-dot-1

With the EDIMAX, it gives me the errors:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The "name of the parts" are all different.

What can be done to fix this issue?  This might sovle my problem.

How do you unpack a .ko file?

I didn't unpack mine.  this could be leading to the above issues.

Message was edited by: Fergus Byrne

Drew Fustini wrote:

 

I noticed from the link that Edimax uses the rtl8192cu driver.  I have another adapter (Asus USB-N13) which uses that driver and it did not work by default with the current Raspbian Wheezy image.  However, it did work ok with Adafruit's new image as it includes that driver, so you may want to give that a try: http://learn.adafruit.com/adafruit-raspberry-pi-educational-linux-distro/occidentalis-v0-dot-1

I do not really want to change image (right now).  But I might give it a go in the future.

Right now though, I just want to get this adapter working.

My guess is that the 8192cu.ko module you have doesn't agree with the version of the kernel your running.  a .ko file is a kernel module file and shouldn't have to unpacked.  the utility "modinfo" will print out information about the module.  could you run that and paste the output?  also, could you paste what "uname -a" outputs?  it might be that the kernel versions don't agree.

My guess is that the 8192cu.ko module you have doesn't agree with the version of the kernel your running.  a .ko file is a kernel module file and shouldn't have to unpacked.  the utility "modinfo" will print out information about the module.  could you run that and paste the output?  also, could you paste what "uname -a" outputs?  it might be that the kernel versions don't agree.

will do

Drew Fustini wrote:

 

My guess is that the 8192cu.ko module you have doesn't agree with the version of the kernel your running.  a .ko file is a kernel module file and shouldn't have to unpacked.  the utility "modinfo" will print out information about the module.  could you run that and paste the output?  also, could you paste what "uname -a" outputs?  it might be that the kernel versions don't agree.

Here's the output from uname -a:

Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux

I also fixed the problem of the :

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

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

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

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

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

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

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.

I can now also tell you that the output of lsusb is:

Bus 001 Device 007: ID 7392:7811 Edimax Technology Co.,Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

I hope this helps you solve my problem.  I also found someone who had the same problem and am reading what they did now: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=6256&hilit=edimax&start=575

Thanks

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

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.