diederikdehaas
commented
8 years ago Hoi @yborges
Did you happen to use the instruction I wrote a while back on my 'cknow.org' repo?
If so, that shouldn't be needed anymore as there is finally a kernel-headers package and you should install and use that one.
After you've installed that, clone this repo (if you haven't already), cd into the folder and make the following change to the Makefile:
CONFIG_PLATFORM_I386_PC = y
CONFIG_PLATFORM_ARM_RPI = nto
CONFIG_PLATFORM_I386_PC = n
CONFIG_PLATFORM_ARM_RPI = yAnd then it should be as simple as running make and (as root or with sudo) make install.
ThijsWithaar
Hallo Diederick! Alvast heel erg bedankt voor de tijd die je in dit project steekt!
I have bought a rapsberry pi 3 and an alfa AWUS036AC. It has chipset 8812au.
On the raspberry pi 3 I have the latest version of the raspbian image(2016-09-23) from raspberrypi.org.
From the release notes:
This firmware points to commit (https://github.com/raspberrypi/linux/commit/2d31cd571e6f2ac61a3eda273d973058e1bb1f58)
uname -a gives: Linux raspberrypi 4.4.21-v7+ #911 SMP Thu Sep 15 14:22:38 BST 2016 armv7l GNU/Linux
I have used .config from "modprobe configs", and Module7.sysvers as Module.sysvers to "make modules_prepare" and I changed the target to the ARM architecture in the Makefile of the module before executing "make" for the module. Furthermore I compiled the modules on debian x64 using the tools also available on the GitHub account of raspberrypi.
I tried first to compile the module from gnab. I'm not sure anymore where I compiled it, but at the end the compilation went well and the driver was the most stable. The problem is that it doesn't see the network I'm interested in. In fact is sees much few networks compared to when I'm using the device with your drivers. I tried both version 4.3.14 and version 4.3.22-beta of your drivers. I'm not very acquainted with module development or wireless in linux so now I'm speaking like a user: when I turn on the RP3 half of the times it will connect to the network I'm interested in - which is very far - otherwise the device isn't available not even for a "iw wlan0 scan" from the command line. So I have to restart the RP3 again and hope it works.
I'm not sure what's wrong. For version 4.3.14 I got this message:
I'm very much willing to test whatever you tell me to test and give you the results. Also, I'm using network manager and have erased everything in the file /etc/networking/interfaces.