- #ASUS USB AC56 DRIVER UPDATE INSTALL#
- #ASUS USB AC56 DRIVER UPDATE PC#
- #ASUS USB AC56 DRIVER UPDATE DOWNLOAD#
Boot on the board, expand filesystem, reboot I've tried this both with the WUSB6300 removed and plugged in. I must've done the whole process about 10 times by now, and I'd really appreciate a helping hand, since I've absolutely no idea what's wrong with my setup.
#ASUS USB AC56 DRIVER UPDATE INSTALL#
cross-compile-805.sh compiles drivers 8188eu, 8192eu, 8812au and mt7601 drivers for the pi's A/A+/B/B+ and Pi 2B for 4.0.8(-v7)+ #805 and generates the tar.gz files with predefined install file and other files as needed.įor the last couple of hours, I've been trying (with little success) to get the Linksys WUSB6300 to work, both on a RPi B+ and a RPi 2. They also generate install files and a tar.gz containing the drivers and other files as necessary.
Wifi-compiler-test.sh and pi-wifi-compiler-test.sh are similar and are run defining the driver to compile and a hexxeh/rpi-firmware commit-id. Here's some pointers to some scripts I use. Regarding the error you get at the end of the module compile, I don't think I've seen that before and I don't know why it happens so I can't help there unfortunately. These are the same as used for cross-compiling but without the text ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- in each line My basic script uses the following to set up the kernel ready for compiling the modules for the Pi A/A+/B/B+Ĭode: Select all cd /home/pi/src/rtl8812au Specifying a particular commit-id will compile a specific module for both the A/A+/B/B+ and the 2B, otherwise it will compile modules for a list of commit-id's defined at the end of the script. I also have an alternative script which only uses the hexxeh/rpi-firmware commit-id and that is used to get the kernel version the modules are being built for and the necessary Module(7).symvers files as required. The script defines the basic kernel version and build used to generate the tar.gz driver filename the driver and install files are saved as, and uses the firmware and kernel commit-ids for the firmware and kernel version the modules are being compiled for. To compile I use a script which compiles all the drivers for a specific version/build of raspbian for both the Pi 2B and the previous versions of the Pi. I have also copied the module sources to the src directory so my directory tree looks something like:. home/richard/src/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
I added the tools directory tree to the $PATH so when compiling the modules it uses the compiler in the tools directory. I cloned the tools repo as this includes the version of gcc used to compile the raspberry pi kernels. I created a directory, src, in my home directory to hold the source files and I cloned the raspberrypi linux, firmware and tools repos. I've never been able to figure out why this happens. Cross-compiling and they don't cause the kernel to crash. I cross-compile because one or two of the modules crashes the kernel on a Pi 2B if they are compiled on the Pi depending on the wifi module being used.
#ASUS USB AC56 DRIVER UPDATE PC#
I now cross-compile my modules on a PC running Ubuntu 14.0.2 but compiling on a Pi is similar. I read your tutorial and to begin with was rather confused as I use a totally different method but after going through it several times it started to connect. The main issue as far as I'm concerned is getting the correct source. However, if you have the space cloning the whole repo can be rather more convenient. You could create a seperate directory for each branch and only clone the necessary depth for each branch saving a considerable amount of disk space. Cloning the current rpi-4.0.y branch can be done using git clone -depth 150 -b rpi-4.0.y linux-4.0 again downloading about 140MB.
It is possible to reduce the amount downloaded by specifying the branch to clone using the -b option and the -depth option.Īs an example to clone the current rpi-3.18.y branch you could use git clone -depth 500 -b rpi-3.18.y linux-3.18 and it downloads approx 140MB.
#ASUS USB AC56 DRIVER UPDATE DOWNLOAD#
To get round this you can clone the complete linux repo, but this does download a substantial amount of code. It seems as you've found using the -depth parameter limits the branch you can access to the main current branch, rpi-4.0.y currently. Sorry for not responding to your posts earlier.įirst the -depth option.