I bought one of these about 12 mths ago: http://www.jaycar.com.au/productView.asp?ID=YN8306&keywords=high+power+wireless+n&form=KEYWORD
I downloaded the drivers from the link above then installed them on a windows computer. How do I use these linux drivers/installers on the raspberry pi to get the wireless adaptor to work?
Will this work with the Raspberry Pi?
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. 
will do 
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 
