(UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+

[MrEngman]

Dear MrEngMan,

I found WiFi p2p seems only work at RTL v4.1.8_9499 driver. So I want to build driver myself for test.

My image is 3.12.22+, but when I checkout branch 3.12.y, it is 3.12.36+... so I got insmod 8188eu.ko failed due to Invalid module format. How can I switch the kernel to 3.12.22?

I found the commit id at https://github.com/raspberrypi/linux/co ... .y?page=58, but I cannot checkout it..
Thanks,
Danny

I have a clone of the raspberry pi Linux repo. I just need to run command git checkout 1981dde for 3.12.22+ #691 or git checkout 1981dde for 3.12.22+ #690 to get the necessary source.

What do you see when you try to checkout the commit for 3.12.22+?



MrEngman

[dannywu]

I clone full linux and firmware, now I can compile for 3.12.22+ now, Thanks alot! But I am building 4.1.13+ now, however, my build module is ARMv7 P2v8, it seems not correct... I check out 1f2ce4a2e7aea3a2123b17aff62a80553df31e21 to roll back 4.1.13+, when I build I cannot find bcmrpi_defconfig or bcm2709_defconfig at arch/arm/configs... so I copied it from git. That is weird...
--
Update: I clone full linux and firmware on my PC, and crosscompile it. But I build failed v4.1.8 8188 driver from http://dl.lazyzhu.com/file/RTL8188EU/. (I can compile v4.1.4 from lwfinger). How to compile it as 8188eu-20140616.tar.gz? Thanks.
/home/aaa/src/4.1.8/RTL8188EUS_RTL8189ES_linux_v4.1.8_9499.20131104/driver/rtl8188EUS_rtl8189ES_linux_v4.1.8_9499.20131104/os_dep/linux/os_intfs.c:359:3: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration]
rtw_proc=create_proc_entry(rtw_proc_name, S_IFDIR, init_net.proc_net);

So I commend these functions as lwfinger version, and build it. Is it right?

Thanks!
Danny

[utomsig]

Hi!
The strange thing was that wlan0 didn't show up (ifconfig) after an apt-get update today. Then I did a rpi-update, witch didn't help. I removed the 8188eu driver and tried the stock one. But it was as bad as last time, with slow connection. Why doesn't the raspberry team ship MrEngmans driver??
Anyway, I reinstalled 8188eu with the script install-8188eu.sh -k 834 . The #834 driver works great for me, and I'm running Linux raspberrypi 4.1.17v7+ #838 SMP Tue Feb 9 13:15:09 GMT 2016 armv7l GNU/Linux.
Thank you MrEngman!

[macmpi]

@MrEngman
I'm (desperately) trying to get my TL-WN725N V2 running on BerryBoot itself and a few images within it (like Raspbian Jessie Lite to start with ,Volumio, etc...).
I somehow get it "sort of working"under Raspbian Jessie Lite with kernel driver, but it does not always work: would like to test with your driver.

Interestingly I read your old post on BerryBoot gihbub where you built a driver version for previous berryboot-20140626.zip.

Would it be possible to build one for more recent berryboot-20160209 version (which now supports rpi0)?
Any guidance on how to install the resulting 8188eu.ko (and eventually unselect the kernel driver)?

Many thanks!

[stevewrightnz]

Looking for a driver update for Raspbain 4.1.17-v7+ #838 - this update broke my wifi

Steve

[MrEngman]

Looking for a driver update for Raspbain 4.1.17-v7+ #838 - this update broke my wifi

Steve

The driver for 4.1.17-v7+ #834 should work as far as I'm aware.

I'm away for 4 weeks, until about 10 Mar, so don't have access to my system for compiling drivers so the drivers will not be updated until I return home.


MrEngman

[MrEngman]

Hi everyone,

Just to let you know I've been able to update the 8188eu driver, so updated versions are available for 4.1.17(-v7)+ #838, #840, #841, #842, #843 and 4.1.18(-v7)+ #845.



MrEngman

[plasmasnake]

What's the difference between this driver and the one that comes included with Raspbian? And how about the manufacturer's (?) driver on github: https://github.com/lwfinger/rtl8188eu

I'm having trouble setting up hostapd with the default driver, so I'm just looking into my options... It seems a little tedious to have to update the driver after each and every kernel update?

[DougieLawson]

Hi MrEngman,

Can you make a version of your drivers available for the current BRANCH=next 4.4.2 # development kernel? I'm trying to get 4.4.2-v7+ #844 running.

Thanks.

[MrEngman]

Hi MrEngman,

Can you make a version of your drivers available for the current BRANCH=next 4.4.2 # development kernel? I'm trying to get 4.4.2-v7+ #844 running.

Thanks.

Hi Dougie,

Driver is now available.

Just had a slight problem doing the compile. As I'm away from home I didn't have the source patched for 4.4.x, however, I've managed to sort that and it appears to be running OK on my Pi 2 B I have with me.



MrEngman

[DougieLawson]

Hi MrEngman,

What's the date code for the 4.4.2+ drivers?

Thanks, I worked it out and now have the driver running on my 2B.

[skewlboy]

Mr Egnman you should make a sticky thread indexing your builds versus their kernel versions, it just saved my day!

I had been strugling with lwfinger 4.1.4 and 4.1.8: using modified hostapd it worked as AP, but as client it didn't show signal quality when scanning.

I then found online the links to http://dl.lazyzhu.com/file/RTL8188EU/ and compiled it for x64 without any issues and I was amazed to see it was compliant with standard hostapd (no more customized version) and also reported signal quality properly.

Then I moved to compile it in RPi and no luck (lwfinger was not an issue...). After some time googling I ended up in this thread and after half an hour looking for the build for 4.1.17 I have it working both for signal quality and without hacked hostapd, thank you!

Now, my request would be if you could make a guide on how you built it.
I tried building in my RPi2 (running jessie) as such:

Code: Select all

curl -O https://www.niksula.hut.fi/~mhiienka/Rpi/linux-headers-rpi/linux-headers-4.1.17-v7%2B_4.1.17-v7%2B-2_armhf.deb
apt-get -qq install dkms gcc-4.8
dpkg -i linux-headers-4.1.17-v7%2B_4.1.17-v7%2B-2_armhf.deb
curl -O http://dl.lazyzhu.com/file/RTL8188EU/RTL8188EUS_linux_v4.3.0.8_13968.20150417.zip
unzip RTL8188EUS_linux_v4.3.0.8_13968.20150417.zip
cd RTL8188EUS_linux_v4.3.0.8_13968.20150417
cd driver/
tar zxf rtl8188EUS_linux_v4.3.0.8_13968.20150417.tar.gz
cd rtl8188EUS_linux_v4.3.0.8_13968.20150417
make ARCH=arm

But I always end up getting an error in some module build.. Maybe I have to change something in configure? Or is this Makefile only for cross compiling? If so, can you write a few lines on the setup?

Thanks once again!

[bgofche]

Hello All,
I find solution for my Raspberry 2 and create script which can spend you a lot of time.
Please follow that post:

viewtopic.php?f=28&t=137346&p=913376#p913376

On the bottom you will find the script code.

Regards,
Kalin

[MrEngman]

There are several scripts available for installing the driver. Look at the OP.

I also have a script that will automatically install my 8188eu driver and also drivers for 8192eu, 8812au, mt7610 and mt7612 wifi modules that I compile.

You can download the script using

Code: Select all

wget https://dl.dropboxusercontent.com/u/80256631/install-wifi.tar.gz
tar xzf install-wifi.tar.gz

Run the command ./install-wifi -h to see what you can do with it.


MrEngman

[skewlboy]

There are several scripts available for installing the driver. Look at the OP.

I also have a script that will automatically install my 8188eu driver and also drivers for 8192eu, 8812au, mt7610 and mt7612 wifi modules that I compile.

You can download the script using

Code: Select all

wget https://dl.dropboxusercontent.com/u/80256631/install-wifi.tar.gz
tar xzf install-wifi.tar.gz

Run the command ./install-wifi -h to see what you can do with it.


MrEngman

Nice install script indeed, but could you please share your build setup for the drivers?

[mhsears1]

I am getting following error when trying to download latest drivers for wireless:
root@piaware:/usr# wget https://dl.dropboxusercontent.com/u/802 ... 219.tar.gz
--2016-02-28 11:37:46-- https://dl.dropboxusercontent.com/u/802 ... 219.tar.gz
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 146.112.61.106, ::ffff:146.112.61.106
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|146.112.61.106|:443... connected.
ERROR: The certificate of `dl.dropboxusercontent.com' is not trusted.
ERROR: The certificate of `dl.dropboxusercontent.com' hasn't got a known issuer.

I have tried updating certs; reinstalling certs and using the --nocheck command to no avail.
Please help...

[MrEngman]

I am getting following error when trying to download latest drivers for wireless:
root@piaware:/usr# wget https://dl.dropboxusercontent.com/u/802 ... 219.tar.gz
--2016-02-28 11:37:46-- https://dl.dropboxusercontent.com/u/802 ... 219.tar.gz
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 146.112.61.106, ::ffff:146.112.61.106
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|146.112.61.106|:443... connected.
ERROR: The certificate of `dl.dropboxusercontent.com' is not trusted.
ERROR: The certificate of `dl.dropboxusercontent.com' hasn't got a known issuer.

I have tried updating certs; reinstalling certs and using the --nocheck command to no avail.
Please help...

Just tried myself and I can download it OK, so no idea what your problem may be.

Are you using raspbian because, as you are logged in as root, it does not appear you are and the drivers are compiled for use with raspbian.



MrEngman

[mhsears1]

I am using a version of Rasbian for flightaware.com. I have used this site on the same build to upgrade my wifi drivers for the past year with no issues.

[svtgd]

Thanks for helping us with our TP-Link TL-WN725N devices.
Is it possible to use this wireless device as an access point?
I just updated to Linux raspberrypi 4.1.18-v7+ #846 .

Many thanks.
svtgd

[DougieLawson]

The most common problem with certificate failures is the date on the client machine not being set correctly.

[mhsears1]

well date/time are properly configured...

[calanor]

With the latest jessie raspbian 4.1.18+ #846 seems to work fine without this driver although dmesg warnings:

[ 15.534112] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
[ 15.598561] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_A_CUT_1T1R_RomVer(0)
[ 15.905793] usbcore: registered new interface driver r8188eu
[ 17.295800] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
[ 17.307523] systemd-journald[84]: Received request to flush runtime journal from PID 1
[ 19.246015] MAC Address = 64:66:b3:18:aa:aa
[ 19.250040] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 19.986238] cfg80211: Calling CRDA to update world regulatory domain
[ 23.122985] cfg80211: World regulatory domain updated:
[ 23.123018] cfg80211: DFS Master region: unset
[ 23.123030] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 23.123047] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 23.123062] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 23.123088] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 23.123105] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 23.123121] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 23.123134] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 23.123146] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 23.123159] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 33.242533] R8188EU: ERROR assoc success
[ 33.242747] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

And I don't see that the driver is your directory:

pi@raspberrypi:~ $ ls -l /lib/modules/4.1.18+/kernel/drivers/net/wireless/rtl818x/
total 4
drwxr-xr-x 2 root root 4096 Feb 26 01:03 rtl8187

Currently there seems to be no driver for 4.1.18+ #846 for PI Zero.
I leave it, or better wait for a new version of this driver?


Edit:
I correct. Exists driver for this version of kernel but with the last raspbian-jessie sems not necessari. Also, I put the 4.1.18+ # 845, # 848 - 8188eu-20160219.tar.gz

Thanks.

[geox]

Hi,

I've an TL-WN725N adapter (most probably v1 ? - the last letters on FCC ID are not V2, though the ID is listed as supported by the driver) and I'm using Volumio image on an RPi2.

Since the adapter was not recognized by the OS (errors) I found and followed your guide and installed the driver.

It works ok, though the adapter exhibits a strange behavior: the green led light on the adapter stays always ON.

After playing around I found out, with the help of ifconfig, that it stays always on when it has assigned inet AND inet6 addresses (eg. 192.168.1.11 and fe80::c66e::1fff::fe15::2e78/64). If I unplug the adapter and plug it in again it gets assigned an inet6 address only and blinks normally.

Any suggestions / thoughts? Is this normal (most probable and I'm missing something!) or a bug?

The lsusb output - the last entry is the WN725N adapter

Code: Select all

pi@volumio:~$ sudo lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast   Ethernet Adapter
Bus 001 Device 008: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 005: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 001 Device 010: ID 0bda:8179 Realtek Semiconductor Corp.

the uname output

Code: Select all

pi@volumio:~$ uname -a
Linux volumio 4.1.18-v7+ #848 SMP Mon Feb 29 14:19:45 GMT 2016 armv7l GNU/Linux

I've installed this version

Code: Select all

4.1.18-v7+ #845, #848 - 8188eu-v7-20160219.tar.gz

Thanks for your time and effort.

PS1. I'm NOT a Linux wizard! Show some understanding please!
PS2. I hope it is not considered an off-topic due to volumio...

[RogueDoctor]

Fantastic writeup for the drivers. Sadly, the driver I need is not in the correct format for my kernel. I am trying to use 8188eu-20150227.tar.gz on Adafruit's PiGrrl running RetroPi EmulationStation (kernel version 3.18.8+ #2 PREEMPT) on a model A+ which doesn't have an ethernet connection. This means that I can't run the auto install script or the compiler script as they both need internet access.

[Fredrik-s]

I have the following kernel:
3.18.0-20-rpi2 #21-Ubuntu arm

Allthough this isn´t listed in post #1. What should I use?