Code: $ modinfo rtl8187 filename: /lib/modules/3.12.22+/kernel/drivers/net/wireless/rtl818x/rtl8187/rtl8187.ko license: GPL description: RTL8187/RTL8187B USB wireless driver author: Larry Finger author: Hin-Tak Leung author: Herton Ronaldo Krzesinski author: Andrea Merello author: Michael Wu srcversion: A707FEC6B464A70F7A04C69 It turns out that this driver for RTL8187L works ok but has some bugs, specially when it comes to using the Rpi as a AP. It also fails in monitor mode.

Luckily, the folks at Realtek have also released a more recent version of this driver: rtl8187L_linux_1041.0209.2012. The source is available at on.

Alfa awus036h. Chipset: Realtek Semiconductor Corp. RTL8187 wireless adapter; Device ID: 0bda:8187; Driver. I've tried it with Debian testing, Debian unstable. Cypress Drivers Touchpad. Wireless Drivers - Back. With the ever changing arena of the wireless driver world and the mac. Before you start your journey into Back.

I've been playing with this card for so long that to be honest I don't know where to start OK, I want to make myself a linux based wireless router.

Now, I'm trying to compile this source for my raspberryPi and that's where the problem starts. I was hoping I could get some help The first problem I bumped into was this. Recompiling the whole kernel is overkill and I wouldn't do that if I were you.

I haven't compiled a module myself, so I can't help you with that. But there should be plenty of tutorials etc either on this forum or on the internet. I just saw that you were running a rpf kernel and installing the raspbian kernel headers, which don't match and hence compiling a module won't work. The real solution should be that the rpf would supply a linux-headers- debian package.

But I don't know if/when that will happen. Also keep in mind that if you run rpi-update, that you would probably get a new kernel version and that means that you'd have to compile a module for your card again (. Code: $ make mrproper && make bcmrpi_defconfig && make modules_prepare && cp./firmware/extra/Module.symvers. Shallyverma wrote:HI MrEngman Though this is older post but i am struggling with an issue where any externally built kernel module insmod command returning with an Error:Invalid format. I stumbled down to this post through. I am just learning a way to compile, load and run a module on rpi.

Code: Linux Pi-B-Plus 3.18.7+ #755 PREEMPT Thu Feb 12 17:14:31 GMT 2015 armv6l GNU/LinuxNow look through the list of commits for one matching the date in the output from uname -a. If you cannot find a date to match the one in your uname -a output look for the next date after that. In the example uname -a output above the date is Feb 12 and this matches firmware commit 47bd0f0. Select the button ' ' to browse the code and look at file extra/uname_string and this will show the kernel version and build and these should match what you see in your uname -a command.

Using my example extra/uname_string shows. Code: # go to linux directory and select version 3.18.7+ #755 cd ~/src/linux git checkout 0be82f7 # go to firmware directory and select version for kernel 3.18.7+ #755 cd ~/src/firmware git checkout 47bd0f0 Sometimes you may find different commits in the firmware repository show the same kernel version and build. Using my example commits 47bd0f0, 89efbd4 and 8aca576 all show the same kernel version, build number and date in file extra/uname_string so any one of those commits can be used to select the firmware to use. If I was compiling a module for this version of the kernel I would usually select the newest commit-id, in this case 8aca576. If you update your Pi to a newer version of code you will probably need to re-compile your module. You can update your linux and firmware directories to add newer code using the command git pull in the linux and firmware directories.

If you see a message like 'You are not currently on a branch' when you use the git pull command in the linux directory use the command git checkout rpi-3.18.y and in the firmware directory the command git checkout master to reset them then run the git pull commands again. And an update for the new Pi B 2. When you look at the firmware repository and browse the code in the directory extra you will see several files including the number ' 7'. Module7.symvers, System7.map and uname_string7. These are files for the new version PI, the Pi B 2.

If you want to compile modules for the Pi B 2 instead of using the command make bcmrpi_defconfig to generate the.config file you will need to use the command make bcm2709_defconfig and instead of copying file Module.symvers to the linux directory you will need to copy the file Module7.symvers to file Module.symvers in the linux directory. Hope this helps you select the correct kernel and firmware version to compile your module and it now works. Shallyverma wrote:HI MrEngman Though this is older post but i am struggling with an issue where any externally built kernel module insmod command returning with an Error:Invalid format. I stumbled down to this post through. I am just learning a way to compile, load and run a module on rpi. Code: Linux Pi-B-Plus 3.18.7+ #755 PREEMPT Thu Feb 12 17:14:31 GMT 2015 armv6l GNU/LinuxNow look through the list of commits for one matching the date in the output from uname -a. If you cannot find a date to match the one in your uname -a output look for the next date after that.

In the example uname -a output above the date is Feb 12 and this matches firmware commit 47bd0f0. Select the button ' ' to browse the code and look at file extra/uname_string and this will show the kernel version and build and these should match what you see in your uname -a command. Using my example extra/uname_string shows. Code: # go to linux directory and select version 3.18.7+ #755 cd ~/src/linux git checkout 0be82f7 # go to firmware directory and select version for kernel 3.18.7+ #755 cd ~/src/firmware git checkout 47bd0f0 Sometimes you may find different commits in the firmware repository show the same kernel version and build. Using my example commits 47bd0f0, 89efbd4 and 8aca576 all show the same kernel version, build number and date in file extra/uname_string so any one of those commits can be used to select the firmware to use.

If I was compiling a module for this version of the kernel I would usually select the newest commit-id, in this case 8aca576. [Shally] Now, i am successful in doing this. Now i could retrieve Kernel source code matching version 3.18.7+ on Pi and now can both build and load module by compiling on Pi itself and also through cross compiler. Only key point is both cross compiler and pi must have same kernel source code. If you update your Pi to a newer version of code you will probably need to re-compile your module. You can update your linux and firmware directories to add newer code using the command git pull in the linux and firmware directories.

If you see a message like 'You are not currently on a branch' when you use the git pull command in the linux directory use the command git checkout rpi-3.18.y and in the firmware directory the command git checkout master to reset them then run the git pull commands again. [Shally] Next i wanted to understand this. I tried to boot Pi through newer kernel code 3.18.9+. As per instructions on this page, I built kernel, copy /linux/arch/arm/boot/Image /boot/kernel.img and replug the SD card on board. On console messages, it shows linux version 3.18.9+ but keyboard and mouse weren't working. Then i tried to build and install modules on ext4 partition on SDCard. However command make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules works.

But sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install fails with error message 'arm-linux-gnueabihf-gcc:Command not found. Could not install modules on /mnt/ext4:Operation not permitted'. I tried to reset PATH variable to point to raspbian tools directory but that did not help. In nutshell, i wanted to understand what steps do i need to follow if i want to boot new kernel on Pi And an update for the new Pi B 2. When you look at the firmware repository and browse the code in the directory extra you will see several files including the number ' 7'. Module7.symvers, System7.map and uname_string7. These are files for the new version PI, the Pi B 2.

If you want to compile modules for the Pi B 2 instead of using the command make bcmrpi_defconfig to generate the.config file you will need to use the command make bcm2709_defconfig and instead of copying file Module.symvers to the linux directory you will need to copy the file Module7.symvers to file Module.symvers in the linux directory. Hope this helps you select the correct kernel and firmware version to compile your module and it now works. MrEngman HI MrEngman Thanks a ton for your detailed reply. It explained lot more things to me. However, i have few questions regarding booting Pi with newer kernel version.Could you please see my comment embed against your reply marked as [Shally].

Shallyverma wrote: [Shally] Now, i am successful in doing this. Now i could retrieve Kernel source code matching version 3.18.7+ on Pi and now can both build and load module by compiling on Pi itself and also through cross compiler.

Only key point is both cross compiler and pi must have same kernel source code. [Shally] Next i wanted to understand this. I tried to boot Pi through newer kernel code 3.18.9+. As per instructions on this page, I built kernel, copy /linux/arch/arm/boot/Image /boot/kernel.img and replug the SD card on board.

On console messages, it shows linux version 3.18.9+ but keyboard and mouse weren't working. Then i tried to build and install modules on ext4 partition on SDCard. However command make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules works. But sudo make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/mnt/ext4 modules_install fails with error message 'arm-linux-gnueabihf-gcc:Command not found. Could not install modules on /mnt/ext4:Operation not permitted'. I tried to reset PATH variable to point to raspbian tools directory but that did not help. In nutshell, i wanted to understand what steps do i need to follow if i want to boot new kernel on Pi HI MrEngman Thanks a ton for your detailed reply.

It explained lot more things to me. However, i have few questions regarding booting Pi with newer kernel version.Could you please see my comment embed against your reply marked as [Shally] Good to hear you have a working module. Personally I have never tried building and creating a new SD card that way so I have no idea what your problem now is. I would think there must be plenty of info in the forum somewhere so a google search of the forum may help you find some help, something like this - 'site:raspberrypi.org compiling new kernel'. I always update my kernel using command.

The ALFA AWUS036H adapter is based on the Realtek RTL8187 chipset. The drivers should be built into Ubuntu, but you may want to try installing the latest from Realtek: • Download the 'Linux driver for Kernel 3.0.0/3.1.0/3.2.0' from the Realtek website. • It will open in Archive Manager; extract the rtl8187L_linux_1041.0209.2012 folder to your Downloads folder. • Open a terminal with Ctrl+Alt+T, and type/paste the following, one line a time: sudo apt-get install build-essential linux-headers-`uname -r` cd Downloads/rtl8187L_linux_1041.0209.2012 make sudo make install Then reboot, and your AWUS036H should be detected.