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


1153 posts   Page 1 of 47   1, 2, 3, 4, 5 ... 47
by MrEngman » Mon Dec 02, 2013 10:22 pm
Driver files available for the TP-LINK TL-WN725N V2 and similar wifi dongles using the 8188eu driver module for systems using the Raspbian image.

LAST UPDATED: 05/07/2016

MAJOR UPDATE:-

I have changed the filename format which now makes it unnecessary to list the files as the filename uses data from command uname -a to create the filename. Use command uname -a to find the kernel version and build for the kernel you are using and the wifi driver filename is now formed using those values like 8188eu-kernel-build.tar.gz. Drivers for kernel versions 3.18, 4.1 and 4.4 are available using this new filename format.

For example, for the Pi 2 B or 3 B, if uname -a shows Linux raspberrypi 4.4.8-v7+ #881 SMP Sat Apr 30 12:16:50 BST 2016 armv7l GNU/Linux the file to download is 8188eu-4.4.8-v7-881.tar.gz.

Download and install using commands
Code: Select all
wget https://dl.dropboxusercontent.com/u/80256631/8188eu-4.4.8-v7-881.tar.gz
tar xzf 8188eu-4.4.8-v7-881.tar.gz
./install.sh

For example, for older versions of the Pi A/A+,B,B+, or the Pi Zero, if uname -a shows Linux raspberrypi 4.4.8+ #881 SMP Sat Apr 30 12:10:24 BST 2016 armv6l GNU/Linux with the kernel version without "-v7" the file to download is 8188eu-4.4.8-881.tar.gz.

Download and install using commands
Code: Select all
wget https://dl.dropboxusercontent.com/u/80256631/8188eu-4.4.8-881.tar.gz
tar xzf 8188eu-4.4.8-881.tar.gz
./install.sh

If you update the kernel version use uname -a to find the new kernel version and build and download the new driver using the new kernel version and build to create the new driver filename.

Also I have made a script which will automatically install the right driver version if it is available. The script can be downloaded using
Code: Select all
wget https://dl.dropboxusercontent.com/u/80256631/install-wifi.tar.gz
tar xzf install-wifi.tar.gz
Use command ./install-wifi -h for details on how you can use it to download or update the wifi driver. This script will automatically determine the wifi you are using and search for the correct driver to download for the kernel version you are using. The script can also install wifi drivers for wifi modules using 8192eu, 8812au, mt7610 or mt7612 drivers.

End of update

IMPORTANT: First check the version of Linux you have. Use the command uname -a to find the version of Linux.
Code: Select all
pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.10.24+ #614 PREEMPT Thu Dec 19 20:38:42 GMT 2013 armv6l GNU/Linux
pi@raspberrypi ~ $
The important part is 3.10.24+ #614. This is just an example and your version may be different. Select the right driver for the version you have from the list below.

This driver supports wifi modules with the following USB IDs
Code: Select all
ID 2001:3310
ID 2001:330F
ID 07B8:8179
ID 0BDA:0179
ID 0BDA:8179

and for 3.12.28+ and newer the additional devices:

ID 056E:4008
ID 2001:3311
ID 0DF6:0076
With the wifi dongle connected to your Pi use command lsusb to show a list of USB devices connected to your Pi. You should see your wifi module in the list and the USB ID of the device which you can check is in the list above. If it is read on to find the device driver you need and how to install it.


rtl8188eu drivers for 3.6.11+
Code: Select all
3.6.11+ #371 up to #520 inclusive    - 8188eu-20130209.tar.gz
3.6.11+ #524, #528, #532             - 8188eu-20130815.tar.gz
3.6.11+ #538, #541, #545, #551, #557 - 8188eu-20130830.tar.gz

rtl8188eu drivers for 3.10.18+ to 3.10.38+
Code: Select all
3.10.18+ #577       - 8188eu-20131105.tar.gz
3.10.18+ #579, #585 - 8188eu-20131106.tar.gz
3.10.18+ #587       - 8188eu-20131110.tar.gz
3.10.18+ #590, #592 - 8188eu-20131111.tar.gz
3.10.18+ #594, #596 - 8188eu-20131113.tar.gz

3.10.19+ #600       - 8188eu-20131113.tar.gz

3.10.21+ #602, #604 - 8188eu-20131113.tar.gz

3.10.22+ #606       - 8188eu-20131206.tar.gz

3.10.23+ #608       - 8188eu-20131209.tar.gz
Code: Select all
3.10.24+ #610       - 8188eu-20131209.tar.gz
3.10.24+ #614       - 8188eu-20131219.tar.gz

3.10.25+ #616, #618 - 8188eu-20131219.tar.gz
3.10.25+ #622, #624 - 8188eu-20131219.tar.gz

3.10.26+ #628       - 8188eu-20140110.tar.gz

3.10.27+ #630       - 8188eu-20140117.tar.gz

3.10.28+ #632, #634 - 8188eu-20140117.tar.gz

3.10.29+ #636, #638 - 8188eu-20140117.tar.gz
Code: Select all
3.10.30+ #640, #642 - 8188eu-20140117.tar.gz

3.10.32+ #646, #648 - 8188eu-20140117.tar.gz

3.10.33+ #654, #656 - 8188eu-20140117.tar.gz
3.10.33+ #658       - 8188eu-20140117.tar.gz

3.10.34+ #660, #661 - 8188eu-20140117.tar.gz

3.10.36+ #662, #664 - 8188eu-20140117.tar.gz
3.10.36+ #665, #666 - 8188eu-20140117.tar.gz

3.10.37+ #667, #669 - 8188eu-20140117.tar.gz
Code: Select all
3.10.38+ #675       - 8188eu-20140117.tar.gz
rtl8188eu drivers for 3.12.xx
Code: Select all
3.12.18+ #673, #677 - 8188eu-20140425.tar.gz
3.12.18+ #679, #680 - 8188eu-20140501.tar.gz

3.12.19+ #681, #682 - 8188eu-20140509.tar.gz
3.12.19+ #684       - 8188eu-20140509.tar.gz

3.12.20+ #685, #686 - 8188eu-20140509.tar.gz
3.12.20+ #687       - 8188eu-20140509.tar.gz

3.12.21+ #688, #689 - 8188eu-20140509.tar.gz

3.12.22+ #690, #691 - 8188eu-20140616.tar.gz
Code: Select all
3.12.23+ #692       - 8188eu-20140626.tar.gz

3.12.24+ #693, #694 - 8188eu-20140705.tar.gz

3.12.25+ #698, #700 - 8188eu-20140705.tar.gz
3.12.25+ #701       - 8188eu-20140705.tar.gz

3.12.26+ #702, #703 - 8188eu-20140705.tar.gz
3.12.26+ #704, #707 - 8188eu-20140705.tar.gz
3.12.26+ #708       - 8188eu-20140705.tar.gz

3.12.28+ #709, #710 - 8188eu-20140908.tar.gz
3.12.28+ #712, #713 - 8188eu-20140908.tar.gz
Code: Select all
3.12.29+ #714, #715 - 8188eu-20140908.tar.gz

3.12.30+ #717       - 8188eu-20141017.tar.gz

3.12.31+ #718, #720 - 8188eu-20141026.tar.gz

3.12.32+ #721       - 8188eu-20141107.tar.gz

3.12.33+ #722, #724 - 8188eu-20141107.tar.gz

3.12.34+ #725, #727 - 8188eu-20141107.tar.gz

3.12.35+ #730, #733 - 8188eu-20141107.tar.gz
Code: Select all
3.12.36+ #737       - 8188eu-20150114.tar.gz

rtl8188eu drivers for 3.18.xx+. There are separate drivers for the Pi 2, see separate list below for the Pi 2.
See note below for installing 3.18.xx+ and 3.18.xx-v7+ drivers
Code: Select all
3.18.3+ #739, #740 - 8188eu-20150120.tar.gz
3.18.3+ #741, #742 - 8188eu-20150120.tar.gz

3.18.5+ #744, #746 - 8188eu-20150130.tar.gz
3.18.5+ #748       - 8188eu-20150130.tar.gz

3.18.6+ #753, #754 - 8188eu-20150208.tar.gz

3.18.7+ #755, #756 - 8188eu-20150212.tar.gz
3.18.7+ #757       - 8188eu-20150212.tar.gz

3.18.7+ #758, #759 - 8188eu-20150223.tar.gz
Code: Select all
3.18.8+ #761, #763 - 8188eu-20150227.tar.gz
3.18.8+ #764, #765 - 8188eu-20150227.tar.gz

3.18.9+ #767, #768 - 8188eu-20150307.tar.gz
3.18.9+ #772       - 8188eu-20150307.tar.gz

3.18.10+ #774, #775 - 8188eu-20150325.tar.gz

3.18.11+ #776, #777 - 8188eu-20150406.tar.gz
3.18.11+ #780, #781 - 8188eu-20150406.tar.gz

3.18.12+ #782, #783 - 8188eu-20150428.tar.gz
Code: Select all
3.18.13+ #784, #785 - 8188eu-20150509.tar.gz

3.18.14+ #792, #793 - 8188eu-20150523.tar.gz
3.18.14+ #794       - 8188eu-20150523.tar.gz

3.18.16+ #795       - 8188eu-20150617.tar.gz

3.18.16+ #796       - 8188eu-20150619.tar.gz
rtl8188eu drivers for 4.0.xx+.
Code: Select all
4.0.5+ #797       - 8188eu-20150621.tar.gz

4.0.6+ #798, #799 - 8188eu-20150623.tar.gz

4.0.7+ #801, #802 - 8188eu-20150630.tar.gz

4.0.8+ #803, #804 - 8188eu-20150713.tar.gz
4.0.8+ #805       - 8188eu-20150713.tar.gz

4.0.9+ #807       - 8188eu-20150724.tar.gz
rtl8188eu drivers for 4.1.xx+.
Code: Select all
4.1.4+ #808       - 8188eu-20150806.tar.gz

4.1.5+ #809       - 8188eu-20150813.tar.gz

4.1.6+ #810       - 8188eu-20150818.tar.gz
4.1.6+ #811, #812 - 8188eu-20150818.tar.gz

4.1.7+ #813, #815 - 8188eu-20150914.tar.gz
4.1.7+ #817       - 8188eu-20150914.tar.gz

4.1.8+ #818       - 8188eu-20150929.tar.gz

4.1.9+ #819       - 8188eu-20151002.tar.gz
Code: Select all
4.1.10+ #820, #821 - 8188eu-20151004.tar.gz

4.1.11+ #822       - 8188eu-20151023.tar.gz

4.1.12+ #824, #825 - 8188eu-20151028.tar.gz

4.1.13+ #826, #827 - 8188eu-20151113.tar.gz

4.1.14+ #828       - 8188eu-20151210.tar.gz

4.1.15+ #829       - 8188eu-20151215a.tar.gz

4.1.15+ #830, #831 - 8188eu-20151215.tar.gz
Code: Select all
4.1.16+ #832, #833 - 8188eu-20160124.tar.gz

4.1.17+ #834, #838 - 8188eu-20160201.tar.gz
4.1.17+ #840, #841 - 8188eu-20160201.tar.gz
4.1.17+ #842, #843 - 8188eu-20160201.tar.gz

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

4.1.19+ #851, #852 - 8188eu-20160305.tar.gz
4.1.19+ #853, #858 - 8188eu-20160305.tar.gz

4.1.20+ #862, #865 - 8188eu-20160319.tar.gz
Code: Select all
4.1.20+ #867       - 8188eu-20160319.tar.gz

4.1.21+ #872, #873 - 8188eu-20160406.tar.gz
For newer kernel versions see MAJOR UPDATE:- at the start of this post.

Pi 2 driver files.

Drivers for 3.18.xx-v7+.
Code: Select all
3.18.5-v7+ #746, #748 - 8188eu-v7-20150202.tar.gz

3.18.6-v7+ #753, #754 - 8188eu-v7-20150208.tar.gz

3.18.7-v7+ #755, #756 - 8188eu-v7-20150212.tar.gz
3.18.7-v7+ #757       - 8188eu-v7-20150212.tar.gz

3.18.7-v7+ #758, #759 - 8188eu-v7-20150223.tar.gz

3.18.8-v7+ #761, #763 - 8188eu-v7-20150227.tar.gz
3.18.8-v7+ #764, #765 - 8188eu-v7-20150227.tar.gz

3.18.9-v7+ #767, #768 - 8188eu-v7-20150307.tar.gz
Code: Select all
3.18.9-v7+ #772       - 8188eu-v7-20150307.tar.gz

3.18.10-v7+ #774, #775 - 8188eu-v7-20150325.tar.gz

3.18.11-v7+ #776, #777 - 8188eu-v7-20150406.tar.gz
3.18.11-v7+ #780, #781 - 8188eu-v7-20150406.tar.gz

3.18.12-v7+ #782, #783 - 8188eu-v7-20150428.tar.gz

3.18.13-v7+ #784, #785 - 8188eu-v7-20150509.tar.gz

3.18.14-v7+ #792, #793 - 8188eu-v7-20150523.tar.gz
3.18.14-v7+ #794       - 8188eu-v7-20150523.tar.gz
Code: Select all
3.18.16-v7+ #795       - 8188eu-v7-20150617.tar.gz

3.18.16-v7+ #796       - 8188eu-v7-20150619.tar.gz
rtl8188eu drivers for 4.0.xx-v7+.
Code: Select all
4.0.5-v7+ #797       - 8188eu-v7-20150621.tar.gz

4.0.6-v7+ #798, #799 - 8188eu-v7-20150623.tar.gz

4.0.7-v7+ #801, #802 - 8188eu-v7-20150630.tar.gz

4.0.8-v7+ #803, #804 - 8188eu-v7-20150713.tar.gz
4.0.8-v7+ #805       - 8188eu-v7-20150713.tar.gz

4.0.9-v7+ #807       - 8188eu-v7-20150724.tar.gz
rtl8188eu drivers for 4.1.xx-v7+.
Code: Select all
4.1.4-v7+ #808       - 8188eu-v7-20150806.tar.gz

4.1.5-v7+ #809       - 8188eu-v7-20150813.tar.gz

4.1.6-v7+ #810       - 8188eu-v7-20150818.tar.gz
4.1.6-v7+ #811, #812 - 8188eu-v7-20150818.tar.gz

4.1.7-v7+ #813, #815 - 8188eu-v7-20150914.tar.gz
4.1.7-v7+ #817       - 8188eu-v7-20150914.tar.gz

4.1.8-v7+ #818       - 8188eu-v7-20150929.tar.gz

4.1.9-v7+ #819       - 8188eu-v7-20151002.tar.gz
Code: Select all
4.1.10-v7+ #820, #821 - 8188eu-v7-20151004.tar.gz

4.1.11-v7+ #822       - 8188eu-v7-20151023.tar.gz

4.1.12-v7+ #824, #825 - 8188eu-v7-20151028.tar.gz

4.1.13-v7+ #826, #827 - 8188eu-v7-20151113.tar.gz

4.1.14-v7+ #828       - 8188eu-v7-20151210.tar.gz

4.1.15-v7+ #829       - 8188eu-v7-20151215a.tar.gz

4.1.15-v7+ #830, #831 - 8188eu-v7-20151215.tar.gz
Code: Select all
4.1.16-v7+ #832, #833 - 8188eu-v7-20160124.tar.gz

4.1.17-v7+ #834, #838 - 8188eu-v7-20160201.tar.gz
4.1.17-v7+ #840, #841 - 8188eu-v7-20160201.tar.gz
4.1.17-v7+ #842, #843 - 8188eu-v7-20160201.tar.gz

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

4.1.19-v7+ #851, #852 - 8188eu-v7-20160305.tar.gz
4.1.19-v7+ #853, #858 - 8188eu-v7-20160305.tar.gz

4.1.20-v7+ #862, #865 - 8188eu-v7-20160319.tar.gz
Code: Select all
4.1.20-v7+ #867       - 8188eu-v7-20160319.tar.gz

4.1.21-v7+ #872, #873 - 8188eu-v7-20160406.tar.gz
For newer kernel versions see MAJOR UPDATE:- at the start of this post.

NOTE: the driver files for 3.18.xx+ and 3.18.xx-v7+ and newer versions contain two additional files, install.sh and 8188eu.conf. Download the driver file selecting the right driver for your kernel version from the list above then to install the 3.18 drivers first untar the tar.gz driver file and then run the install.sh command.eg. For the Pi 1 (A, A+, B, B+) use
Code: Select all
wget https://dl.dropboxusercontent.com/u/80256631/8188eu-2015yyzz.tar.gz
tar xzf 8188eu-2015yyzz.tar.gz
./install.sh
and for the Pi 2 the filename includes an additional "-v7" so use
Code: Select all
wget https://dl.dropboxusercontent.com/u/80256631/8188eu-v7-2015yyzz.tar.gz
tar xzf 8188eu-v7-2015yyzz.tar.gz
./install.sh
change yyzz in the wget and tar commands to select the right driver file. install.sh will install the driver file and copy the file 8188eu.conf to directory /etc/modprobe.d. The 8188eu.conf file will disable power management for the 8188eu driver and disable the inbuilt driver version r8188eu.


The link to driver files for kernel versions 3.6, 3.10 and 3.12 is as follows - use the date code from the list above to download the required driver
Code: Select all
https://dl.dropboxusercontent.com/u/80256631/8188eu-201xyyzz.tar.gz
Replace xyyzz with the last 5 digits of the date code of the filename for the driver for your kernel version.


NOTE: If updating firmware revisions, say from 3.10.23+ to 3.10.24+, and they use the same driver, in this case 8188eu-20131209.tar.gz, you will still need to reinstall the driver on the newer version of Linux, even though the driver has not changed as it will be loaded from a different directory by the new Linux revision and you need to install it in the new directory.

The driver installation instructions expect you to be using Raspbian, either installed from a basic raspbian image or installed using NOOBS. The instructions are based on running from a Command Line Terminal, not a GUI (Graphical User Interface). If you are running using the GUI you will need to open a terminal window and run the commands from the terminal window but I can't guarantee they will work.

If you have a wired internet connection install the driver with the following commands
Code: Select all
wget https://dl.dropboxusercontent.com/u/80256631/8188eu-201xyyzz.tar.gz <--set data code for driver version above
tar -zxvf 8188eu-201xyyzz.tar.gz                                         <--set data code for driver version above
sudo install -p -m 644 8188eu.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless
sudo insmod /lib/modules/$(uname -r)/kernel/drivers/net/wireless/8188eu.ko
sudo depmod -a

If you do not have an internet connection the driver file will need to be downloaded on another computer and copied to the SD card. I use a Windows laptop and will use that as an example of how to copy and install the wifi driver.

Open a web browser on your Windows computer and download the driver. Check the name of the driver file before saving it and correct it if necessary. I have sometimes found Windows tries to save the driver file as 8188eu-201xyyzz.tar.tar when it should be 8188eu-201xyyzz.tar.gz. Substitute the correct file name for "xyyzz".

Take the SD card and load it into an SD card reader on your Windows computer. Copy the driver file, 8188eu-201xyyzz.tar.gz, from your Windows computer to the SD card. Safely remove the SD card from the card reader by clicking the safe removal icon in the task bar and install the SD card in your Raspberry Pi and power on and login.

After logging in you will need to copy the driver file to your home directory. How you do this is dependent on whether you installed rasbian using NOOBS or directly from a Rasbian image. If you are running raspbian installed using NOOBS you need to run the following commands to copy the driver file to your home directory
Code: Select all
sudo mount /dev/mmcblk0p1 /mnt
sudo mv /mnt/8188eu-201xyyzz.tar.gz .
sudo umount /dev/mmcblk0p1
You will need the period, full stop (.), after the filename in the sudo mv command. The mount/umount commands are required as the driver file is in the NOOBS boot directory, not the rasbian boot directory, so the NOOBS boot directory needs mounting and accessing to get to the driver file.

If you installed raspbian directly from a rasbian image use the following command to copy the driver file to your home directory
Code: Select all
sudo mv /boot/8188eu-201xyyzz.tar.gz .

Now the driver file has been moved to your home directory the driver installation can be completed using the following commands
Code: Select all
tar -zxvf 8188eu-201xyyzz.tar.gz                                         <--set data code for driver version above
sudo install -p -m 644 8188eu.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless
sudo insmod /lib/modules/$(uname -r)/kernel/drivers/net/wireless/8188eu.ko
sudo depmod -a

Once the driver is loaded you will need to configure the network set up so the Pi will connect to your wifi network if it is not already done. There are some basic details on how to do that available here.

To help in installing or updating the driver @LaFambe has produced a very simple script available here which will automatically select and install the correct version of the driver for the version of Raspbian being used. I was quite impressed by it and it really does make life much simpler. You will need an internet connection for the script to work.

Thank you very much, LaFambe.


MrEngman
Last edited by MrEngman on Tue Jul 05, 2016 1:16 am, edited 176 times in total.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by poogle » Tue Dec 03, 2013 11:01 am
Thank you so much for posting this. The driver seems to work fine.

Have you tried running the Pi as an access point with this chip? I cannot get it to work with hostapd (have tried all kinds of versions including compiling the version from realtek). I'm getting the following error when running hostapd:
Code: Select all
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Posts: 2
Joined: Tue Nov 26, 2013 8:16 am
by MrEngman » Tue Dec 03, 2013 9:14 pm
poogle wrote:Thank you so much for posting this. The driver seems to work fine.

Have you tried running the Pi as an access point with this chip? I cannot get it to work with hostapd (have tried all kinds of versions including compiling the version from realtek). I'm getting the following error when running hostapd:
Code: Select all
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported

I tried with the latest version 3.10.21 and can't get it working as AP. Also tried with EW-7811Un wifi and can't get that working either. With the WN725 I cannot see any AP, but with the EW7811Un I can see an AP but cannot connect. Had previously tried with 3.6.11+ some time ago and the EW-7811Un worked and I'm pretty certain the TL-WN725 also worked as well.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by MrEngman » Fri Dec 06, 2013 3:03 pm
Updated 8188eu.ko driver now available for 3.10.22+

See here


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by bob1122 » Sun Dec 08, 2013 4:33 pm
Howdy MrEngman,
EDIT: Added more info, I think may be useful.
I enjoyed great speeds with the 3.6.11 release and these wireless drivers, however I rpi-update 'd my Pi, and then installed these updated drivers (and copied firmware file you specified) and now I've noticed quite a bit of lag with the 3.10.22+ release, specifically with SSH.

I typically get pings (to the 725v2 RPi) from various machines on the local network ranging from 6000ms-200ms, nothing consistent.

I used wireshark to sniff network traffic because I had suspected the RPi was sending out excessive broadcast packets, searching for dns, or something that may hindernetwork performance.. but there isn't any traffic other then my pings, and SSH connections.

On LAN only connection I have no issues, the pings are 1ms, and SSH / VNC work flawlessly (almost... too fast). I would like to note however, If I boot up with LAN and Wifi, the wifi seems to have no issues whatsoever, it seems to be that I have issues when I boot solely on Wifi, I didn't have these issues before updating to 3.10.22 and update the wifi drivers

Would you happen to have any suggestions?
Thanks in advanced, and thanks for your work!
Posts: 6
Joined: Sun Dec 08, 2013 4:24 pm
by MrEngman » Sun Dec 08, 2013 5:23 pm
Hi,

I've noticed several people have a similar issue. I'm not sure why. I see the following pinging from my Pi
Code: Select all
pi@raspberrypi ~ $ ping -c 5 192.168.16.2
PING 192.168.16.2 (192.168.16.2) 56(84) bytes of data.  <-- local gateway/server/router
64 bytes from 192.168.16.2: icmp_req=1 ttl=128 time=6.02 ms
64 bytes from 192.168.16.2: icmp_req=2 ttl=128 time=4.68 ms
64 bytes from 192.168.16.2: icmp_req=3 ttl=128 time=4.64 ms
64 bytes from 192.168.16.2: icmp_req=4 ttl=128 time=4.74 ms
64 bytes from 192.168.16.2: icmp_req=5 ttl=128 time=4.78 ms

--- 192.168.16.2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 4.649/4.976/6.023/0.529 ms
pi@raspberrypi ~ $ ping -c 5 192.168.16.19
PING 192.168.16.19 (192.168.16.19) 56(84) bytes of data.  <-- local W7 laptop
64 bytes from 192.168.16.19: icmp_req=1 ttl=64 time=2.96 ms
64 bytes from 192.168.16.19: icmp_req=2 ttl=64 time=2.16 ms
64 bytes from 192.168.16.19: icmp_req=3 ttl=64 time=2.01 ms
64 bytes from 192.168.16.19: icmp_req=4 ttl=64 time=2.03 ms
64 bytes from 192.168.16.19: icmp_req=5 ttl=64 time=2.03 ms

--- 192.168.16.19 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 2.012/2.243/2.968/0.369 ms
pi@raspberrypi ~ $ ping -c 5 ntp0.zen.co.uk
PING ntp0.zen.co.uk (212.23.8.6) 56(84) bytes of data.  <-- ISP's time server
64 bytes from ntp0.admin.zen.net.uk (212.23.8.6): icmp_req=1 ttl=54 time=43.3 ms
64 bytes from ntp0.admin.zen.net.uk (212.23.8.6): icmp_req=2 ttl=54 time=43.4 ms
64 bytes from ntp0.admin.zen.net.uk (212.23.8.6): icmp_req=3 ttl=54 time=43.3 ms
64 bytes from ntp0.admin.zen.net.uk (212.23.8.6): icmp_req=4 ttl=54 time=41.5 ms
64 bytes from ntp0.admin.zen.net.uk (212.23.8.6): icmp_req=5 ttl=54 time=40.8 ms

--- ntp0.zen.co.uk ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 40.802/42.515/43.453/1.124 ms
pi@raspberrypi ~ $

Pinging from my W7 laptop gives the following
Code: Select all
C:\Users\>ping -n 5 192.168.16.2

Pinging 192.168.16.2 with 32 bytes of data:  <-- local gateway/server/router
Reply from 192.168.16.2: bytes=32 time=6ms TTL=128
Reply from 192.168.16.2: bytes=32 time=7ms TTL=128
Reply from 192.168.16.2: bytes=32 time=5ms TTL=128
Reply from 192.168.16.2: bytes=32 time=4ms TTL=128
Reply from 192.168.16.2: bytes=32 time=4ms TTL=128

Ping statistics for 192.168.16.2:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 7ms, Average = 5ms

C:\Users\>ping -n 5 192.168.16.15

Pinging 192.168.16.15 with 32 bytes of data:  <-- my Raspberry Pi
Reply from 192.168.16.15: bytes=32 time=98ms TTL=64
Reply from 192.168.16.15: bytes=32 time=2ms TTL=64
Reply from 192.168.16.15: bytes=32 time=2ms TTL=64
Reply from 192.168.16.15: bytes=32 time=2ms TTL=64
Reply from 192.168.16.15: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.16.15:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 98ms, Average = 21ms

C:\Users\>ping -n 5 ntp0.zen.co.uk

Pinging ntp0.zen.co.uk [212.23.8.6] with 32 bytes of data:  <-- ISP's time server
Reply from 212.23.8.6: bytes=32 time=41ms TTL=54
Reply from 212.23.8.6: bytes=32 time=42ms TTL=54
Reply from 212.23.8.6: bytes=32 time=41ms TTL=54
Reply from 212.23.8.6: bytes=32 time=43ms TTL=54
Reply from 212.23.8.6: bytes=32 time=42ms TTL=54

Ping statistics for 212.23.8.6:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 41ms, Maximum = 43ms, Average = 41ms

C:\Users\>

Results are very similar. Personally I've never seen any problems with transfer rates to/from the Pi. Could be down to whatever code is running on the Pi and whether you are using a GUI (using startx) or not. Data transfers for upload/download to/from the internet are usually around 700-800KB/s. Transfer rates are similar if I use a wired connection.

I do not use a GUI and communicate with my Pi using SSH from my W7 laptop.

One setting I always use and that is to make the memory split as small as possible (16MB) as I don't use a GUI. Haven't checked if that makes any difference though.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by MrEngman » Sun Dec 08, 2013 6:05 pm
bob1122 wrote:Howdy MrEngman,
EDIT: Added more info, I think may be useful.

On LAN only connection I have no issues, the pings are 1ms, and SSH / VNC work flawlessly (almost... too fast). I would like to note however, If I boot up with LAN and Wifi, the wifi seems to have no issues whatsoever, it seems to be that I have issues when I boot solely on Wifi, I didn't have these issues before updating to 3.10.22 and update the wifi drivers

Would you happen to have any suggestions?
Thanks in advanced, and thanks for your work!

If you boot with both LAN and wifi connected then I think the data for either interface will generally be transferred via the wired interface whether you SSH to eth0 or wlan0.

If I boot the Pi with both eth and wlan connected I can SSH into either but if I then unplug eth0, then I loose both connections, eth permanently of course, and wlan for maybe upto a minute or so. wlan will then come alive again and I can then continue to SSH via wifi but have NO connection to the internet, only to the local network. To get a connection to the wider internet I then need to unplug and plug back in the wifi adaptor. I can then continue the SSH connection and can access the internet via wifi.

Just done a test. Booted with just wifi connected and SSHd in, then plugged in Ethernet cable and connected with SSH to the eth interface. Then tried a download from the internet from the eth SSH terminal. The wifi is flashing as though the data is being transfer via the wifi connection even though I was using the SSH terminal to the eth port. Tried a second download and during the download unplugged the wifi and the download failed.



MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by bob1122 » Sun Dec 08, 2013 7:11 pm
There are a couple things I'd like to attempt before ruling out anything in particular, such as;


A couple things I'd like to mention, it's a clean install, I wanted to have network connectivity working consistently before running any code, the only thing I've done is updated, rpi-update, and finally of course 725v2 10.22 driver install.

Secondly, all of my testing is done immediately after boot, on the pi it is at the login screen. Essentially I want to ensure I have a headless setup (should be no need to login on the pi to SSH it). I achieved this with 3.6.11 however I'm running into various issues trying to get this to work on 10.22.

This is rather important for my future application of the pi, because I cannot get the USB -TTL to function properly on my RPi, so as a result I'm going to do everything I need to do via SSH. (Plus SSH is obviously better if you have network connectivity). At the end of the day, in my application, running Ethernet cable is not possible.

I apologize as I cannot test many of these things at the moment as I am studying for certification exams, but later on this evening (I'm in the EST zone) I will try a completely clean install of Raspbian->upgrade/update->rpi-update then of course install 725v2 10.22 drivers and see if I still have issues.

I too notice that my wifi adapter even though I can't pick up any network traffic, is doing something because the lights certainly are flashing on and off intermittently.
Oh I'd also like to note, the amount of bandwidth the Pi has isn't even measurable, SSH isn't just slow, but it takes about 10-40seconds between each character being pressed for it to be displayed, on ethernet there is no delay of any form.

Hopefully I can resolve this... anything that has changed since 3.6.11 that may result in this sort of issue?

Thanks again
Posts: 6
Joined: Sun Dec 08, 2013 4:24 pm
by MrEngman » Sun Dec 08, 2013 9:28 pm
OK that makes things much clearer. Unfortunately I can think of nothing specific to cause your problem but it's certainly really odd.

I run my Pi in exactly the same way, headless, and SSH in from my W7 laptop. I also specifically look for updates for rpi-update so I can update the wifi driver as and when necessary. I then store the compiled drivers on DropBox for anyone else to use.

On the current SD card I'm using I've probably made an update using rpi-update about 50 times although it could be many more as I'm just not sure of the original image I installed. I've seen issues with rpi-update only a very few times due to problems with the software loaded with the updates. Last time I think was back in July then at the beginning of May and another with a couple of updates in March.

I always also normally only use the raw Raspbian image. My wifi adaptor is connected directly to the Pi using a USB extension cable - A-plug to A-socket. This allows me to hot plug the adaptor without resetting the Pi without needing a hub.

What does the output of command ifconfig wlan0 show? I presume your wifi adaptor is plugged directly into your Pi. Have you tried changing USB sockets just in case there's a possible hardware issue?


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by bob1122 » Sun Dec 08, 2013 9:46 pm
I will test out a clean install before I decide to revert to 3.6.11, however I must ask out of inherent obligation... what advantages, changes, or benefits exist from using 3.10.22?
Posts: 6
Joined: Sun Dec 08, 2013 4:24 pm
by MrEngman » Sun Dec 08, 2013 10:07 pm
bob1122 wrote:I will test out a clean install before I decide to revert to 3.6.11, however I must ask out of inherent obligation... what advantages, changes, or benefits exist from using 3.10.22?

As for specifics I can't say, but there are various fixes usually applied. However, if you find a particular revision supports what you need then there is probably little point in updating. As I said I run updates to make sure I have working versions of the driver for the updated code.

Would be interesting to see the output of ifconfig wlan0 to see what errors are reported if any. Also have you checked the output of dmesg for errors. May provide a clue to what is happening.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by bob1122 » Mon Dec 09, 2013 4:39 pm
I joyously hate to say it; but it's working fine now, flawlessly in fact. Sorry to bombard your clean and tidy post with my issues of evident insignificance. Not certain why I was having issues initially.

Perhaps the Pi needed a break, or perhaps the Pi realized in it's infinite wisdom that I did indeed need a break so it naturally impeded me from dedicating more time to it, as if it knew I had more important things to focus upon, either way, she's working fine now.

Thanks Mr.Engman.
P.S. Could you reference me to where found instructions to compiling the drivers? [lwfinger ?] I'd like to investigate further when I have the chance, and will report back with any suggestions to prevent future issues.
You can PM if you prefer, thanks!
Posts: 6
Joined: Sun Dec 08, 2013 4:24 pm
by MrEngman » Tue Dec 10, 2013 1:24 am
Updated 8188eu.ko driver now available for 3.10.23+

See here


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by MrEngman » Tue Dec 10, 2013 6:44 pm
Hi Bob1122,

Don't know if it all makes sense but this is what I use to compile drivers.
Code: Select all
# Compile driver for 3.10.y version of kernel. To compile for an older version you will need
# to set up the correct commits of linux and firmware to comply with the version of linux you
# need the driver for.

# Compiles 8188eu driver for 3.10.y without needing to compile the whole linux kernel. Requires
# driver firmware, rtl8188eufw.bin, which can be found in the driver source tree.


# Initialise kernel and driver source code for the first time for compiling drivers
-----------------------------------------------------------------------------------

# jump to home directory - /home/pi
cd
 
# make directory to hold source data
mkdir src

# enter source directory - /home/pi/src
cd src

# clone rtl8188eu source code repository - this will automatically generate a
# directory "rtl8188eu" at /home/pi/src/rtl8188eu.
git clone git://github.com/lwfinger/rtl8188eu.git

# clone Raspberry Pi firmware repository - this will automatically generate a
# directory "firmware" at /home/pi/src/firmware - setting depth avoids downloading
# the whole repository but allows reverting to some previous revisions if necessary.
# Do not use git clone if it has already been used - use git pull to update the code.
git clone --depth 10 git://github.com/raspberrypi/firmware.git

# clone Raspberry Pi linux source code - this will automatically generate a
# directory "linux" at /home/pi/src/linux -  setting depth avoids downloading
# the whole repository but allows reverting to some previous revisions if
# necessary. Do not use git clone if it has already been used - use git pull
# to update the code.
git clone --depth 235 git:github.com/raspberrypi/linux.git


# Updating source code for compiling drivers if code is already installed and
# newer code is available
-----------------------------------------------------------------------------

# if rtl8188eu directory has already been generated it can be update with the
# latest code using git pull. enter rtl8188eu directory, run command then revert
# back to src directory
cd rtl8188eu
git pull
cd ../

# if firmware directory has already been generated it can be update with the
# latest code using git pull enter firmware directory, run command then revert
# back to src directory. Use depth option or git pull may load the whole of
# the repository from way back 2011 or whenever
cd firmware
git pull --depth 2
cd ../

# if linux directory has already been generated it can be update with the latest
# code using git pull. enter linux directory, run command then revert back to
# src directory. Use depth option or git pull may load the whole of the repository
# from way back 2011 or whenever ~ 3 Million+ files
cd linux
git pull --depth 2
cd ../


# Select a specific version of linux/firmware to compile driver for if required
-------------------------------------------------------------------------------

# adjust firmware version required for kernel version driver is to be used with
# view commit ID's at https://github.com/raspberrypi/firmware/commits/master
# not required if driver is being compiled for most recent version kernel
# unless it has previously been set to use an older version of code
cd firmware
git checkout "branch"
git checkout "commit ID"
cd ../

# enter linux source directory and adjust linux code version to use
# adjust to version required for kernel version driver is to be used with
# view commit ID's at https://github.com/raspberrypi/linux/commits/
# not required if driver being compiled for most recent version kernel
cd linux
git checkout "branch"
git checkout "commit ID"
cd ../


# To compile for latest code I use the following commands
---------------------------------------------------------

# enter linux source directory
cd linux

# clean linux source directory tree
make mrproper

# generate .config using bcmrpi_defconfig which can be used to make .config for any
# version of linux without requiring to copying .config from a working version of code
# as suggested in many tutorials making life a little easier.
make bcmrpi_defconfig

# prepare source for module compile
make modules_prepare

# copy Module.symvers file from firmware tree to linux directory
cp ../firmware/extra/Module.symvers .

# enter 8188eu driver source directory
cd ../rtl8188eu

# clean rtl8188eu source directory tree
make clean

# compile driver file 8188eu.ko
CONFIG_RTL8188EU=m make -C /home/pi/src/linux M=`pwd`

# Install the driver
--------------------

# install driver firmware if not already installed, install driver and reboot
sudo cp rtl8188eufw.bin /lib/firmware/rtlwifi
sudo install -p -m 644 8188eu.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless

# insmod command should run without any error response if driver module is compiled OK
sudo insmod /lib/modules/$(uname -r)/kernel/drivers/net/wireless/8188eu.ko
sudo depmod -a
sudo reboot

Hope this makes sense
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by martinahoj » Thu Dec 12, 2013 12:58 pm
I hate to say it, but I'm having a weird problem with last few versions (3.10.23, 3.10.22, 3.10.20). For some reason it keeps connectiong and disconnection every cca 20s and I'm sure with clean Raspberian Wheezy it worked fine. I'm using wicd network manager. This is what it looks like when I ping my RPi.
Code: Select all
64 bytes from 192.168.0.107: icmp_seq=0 ttl=64 time=109.983 ms
64 bytes from 192.168.0.107: icmp_seq=1 ttl=64 time=19.629 ms
64 bytes from 192.168.0.107: icmp_seq=2 ttl=64 time=8.761 ms
64 bytes from 192.168.0.107: icmp_seq=3 ttl=64 time=14.978 ms
64 bytes from 192.168.0.107: icmp_seq=4 ttl=64 time=2.832 ms
64 bytes from 192.168.0.107: icmp_seq=5 ttl=64 time=4.754 ms
64 bytes from 192.168.0.107: icmp_seq=6 ttl=64 time=48.291 ms
64 bytes from 192.168.0.107: icmp_seq=7 ttl=64 time=12.713 ms
64 bytes from 192.168.0.107: icmp_seq=8 ttl=64 time=6.062 ms
64 bytes from 192.168.0.107: icmp_seq=9 ttl=64 time=2.636 ms
64 bytes from 192.168.0.107: icmp_seq=10 ttl=64 time=9.447 ms
64 bytes from 192.168.0.107: icmp_seq=11 ttl=64 time=2.920 ms
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
64 bytes from 192.168.0.107: icmp_seq=42 ttl=64 time=107.040 ms
64 bytes from 192.168.0.107: icmp_seq=43 ttl=64 time=48.828 ms
64 bytes from 192.168.0.107: icmp_seq=44 ttl=64 time=5.504 ms
64 bytes from 192.168.0.107: icmp_seq=45 ttl=64 time=7.116 ms
64 bytes from 192.168.0.107: icmp_seq=46 ttl=64 time=6.706 ms
64 bytes from 192.168.0.107: icmp_seq=47 ttl=64 time=4.426 ms
64 bytes from 192.168.0.107: icmp_seq=48 ttl=64 time=5.399 ms
64 bytes from 192.168.0.107: icmp_seq=49 ttl=64 time=6.073 ms
64 bytes from 192.168.0.107: icmp_seq=50 ttl=64 time=25.729 ms
64 bytes from 192.168.0.107: icmp_seq=51 ttl=64 time=6.100 ms
64 bytes from 192.168.0.107: icmp_seq=52 ttl=64 time=6.255 ms
64 bytes from 192.168.0.107: icmp_seq=53 ttl=64 time=6.347 ms
64 bytes from 192.168.0.107: icmp_seq=54 ttl=64 time=9.725 ms
64 bytes from 192.168.0.107: icmp_seq=55 ttl=64 time=6.231 ms
64 bytes from 192.168.0.107: icmp_seq=56 ttl=64 time=16.880 ms
64 bytes from 192.168.0.107: icmp_seq=57 ttl=64 time=5.697 ms
64 bytes from 192.168.0.107: icmp_seq=58 ttl=64 time=7.097 ms
64 bytes from 192.168.0.107: icmp_seq=59 ttl=64 time=5.562 ms
Request timeout for icmp_seq 60
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62
Request timeout for icmp_seq 63
Request timeout for icmp_seq 64
Request timeout for icmp_seq 65
Request timeout for icmp_seq 66
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
Request timeout for icmp_seq 73
Request timeout for icmp_seq 74
Request timeout for icmp_seq 75
Request timeout for icmp_seq 76
Request timeout for icmp_seq 77
Request timeout for icmp_seq 78
Request timeout for icmp_seq 79
Request timeout for icmp_seq 80
Request timeout for icmp_seq 81
Request timeout for icmp_seq 82
Request timeout for icmp_seq 83
Request timeout for icmp_seq 84
Request timeout for icmp_seq 85
Request timeout for icmp_seq 86
Request timeout for icmp_seq 87
Request timeout for icmp_seq 88
Request timeout for icmp_seq 89
Request timeout for icmp_seq 90
Request timeout for icmp_seq 91
Request timeout for icmp_seq 92
Request timeout for icmp_seq 93
Request timeout for icmp_seq 94
Request timeout for icmp_seq 95
Request timeout for icmp_seq 96
Request timeout for icmp_seq 97
Request timeout for icmp_seq 98
Request timeout for icmp_seq 99
Request timeout for icmp_seq 100
64 bytes from 192.168.0.107: icmp_seq=101 ttl=64 time=73.622 ms
64 bytes from 192.168.0.107: icmp_seq=102 ttl=64 time=52.785 ms
64 bytes from 192.168.0.107: icmp_seq=103 ttl=64 time=5.372 ms
64 bytes from 192.168.0.107: icmp_seq=104 ttl=64 time=6.572 ms
64 bytes from 192.168.0.107: icmp_seq=105 ttl=64 time=2.741 ms
64 bytes from 192.168.0.107: icmp_seq=106 ttl=64 time=5.399 ms
64 bytes from 192.168.0.107: icmp_seq=107 ttl=64 time=5.389 ms
64 bytes from 192.168.0.107: icmp_seq=108 ttl=64 time=2.680 ms
64 bytes from 192.168.0.107: icmp_seq=109 ttl=64 time=6.017 ms
64 bytes from 192.168.0.107: icmp_seq=110 ttl=64 time=21.945 ms
64 bytes from 192.168.0.107: icmp_seq=111 ttl=64 time=6.081 ms
64 bytes from 192.168.0.107: icmp_seq=112 ttl=64 time=6.321 ms
64 bytes from 192.168.0.107: icmp_seq=113 ttl=64 time=5.503 ms
64 bytes from 192.168.0.107: icmp_seq=114 ttl=64 time=3.377 ms
64 bytes from 192.168.0.107: icmp_seq=115 ttl=64 time=6.648 ms
64 bytes from 192.168.0.107: icmp_seq=116 ttl=64 time=6.187 ms
64 bytes from 192.168.0.107: icmp_seq=117 ttl=64 time=6.238 ms
64 bytes from 192.168.0.107: icmp_seq=118 ttl=64 time=3.833 ms
64 bytes from 192.168.0.107: icmp_seq=119 ttl=64 time=15.038 ms
Request timeout for icmp_seq 120
Request timeout for icmp_seq 121
Request timeout for icmp_seq 122
Request timeout for icmp_seq 123
Request timeout for icmp_seq 124
Request timeout for icmp_seq 125
Request timeout for icmp_seq 126
Request timeout for icmp_seq 127
Request timeout for icmp_seq 128
Request timeout for icmp_seq 129
Request timeout for icmp_seq 130
Request timeout for icmp_seq 131
Request timeout for icmp_seq 132
Request timeout for icmp_seq 133
Request timeout for icmp_seq 134
Request timeout for icmp_seq 135
Request timeout for icmp_seq 136
Request timeout for icmp_seq 137
Request timeout for icmp_seq 138
Request timeout for icmp_seq 139
Request timeout for icmp_seq 140
Do you have any idea what's wrong? I had to upgrade to more recent kernel because I need newer version of raspistill.
Posts: 2
Joined: Fri Dec 06, 2013 3:40 pm
by MrEngman » Thu Dec 12, 2013 2:07 pm
Hi martinahoj,

Very odd. I've not seen anything like that myself. Is there some software running that could interfere with the wifi/usb somehow? The command top will show the running programs. Use Cntl-C to exit. Have you checked the log files or dmesg for any errors. May give a clue.

I have never tried wicd. I prefer using /etc/network/interfaces to configure my wifi. Much less complicated :? :D

e.g. for wpa/wpa2
Code: Select all
auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-ssid "network-name"
wpa-psk "network-password"


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by bob1122 » Thu Dec 12, 2013 4:20 pm
martinahoj wrote:I hate to say it, but I'm having a weird problem with last few versions (3.10.23, 3.10.22, 3.10.20). For some reason it keeps connectiong and disconnection every cca 20s and I'm sure with clean Raspberian Wheezy it worked fine. I'm using wicd network manager. This is what it looks like when I ping my RPi.
Code: Select all
64 bytes from 192.168.0.107: icmp_seq=0 ttl=64 time=109.983 ms
64 bytes from 192.168.0.107: icmp_seq=1 ttl=64 time=19.629 ms
64 bytes from 192.168.0.107: icmp_seq=2 ttl=64 time=8.761 ms
64 bytes from 192.168.0.107: icmp_seq=3 ttl=64 time=14.978 ms
64 bytes from 192.168.0.107: icmp_seq=4 ttl=64 time=2.832 ms
64 bytes from 192.168.0.107: icmp_seq=5 ttl=64 time=4.754 ms
64 bytes from 192.168.0.107: icmp_seq=6 ttl=64 time=48.291 ms
64 bytes from 192.168.0.107: icmp_seq=7 ttl=64 time=12.713 ms
64 bytes from 192.168.0.107: icmp_seq=8 ttl=64 time=6.062 ms
64 bytes from 192.168.0.107: icmp_seq=9 ttl=64 time=2.636 ms
64 bytes from 192.168.0.107: icmp_seq=10 ttl=64 time=9.447 ms
64 bytes from 192.168.0.107: icmp_seq=11 ttl=64 time=2.920 ms
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
64 bytes from 192.168.0.107: icmp_seq=42 ttl=64 time=107.040 ms
64 bytes from 192.168.0.107: icmp_seq=43 ttl=64 time=48.828 ms
64 bytes from 192.168.0.107: icmp_seq=44 ttl=64 time=5.504 ms
64 bytes from 192.168.0.107: icmp_seq=45 ttl=64 time=7.116 ms
64 bytes from 192.168.0.107: icmp_seq=46 ttl=64 time=6.706 ms
64 bytes from 192.168.0.107: icmp_seq=47 ttl=64 time=4.426 ms
64 bytes from 192.168.0.107: icmp_seq=48 ttl=64 time=5.399 ms
64 bytes from 192.168.0.107: icmp_seq=49 ttl=64 time=6.073 ms
64 bytes from 192.168.0.107: icmp_seq=50 ttl=64 time=25.729 ms
64 bytes from 192.168.0.107: icmp_seq=51 ttl=64 time=6.100 ms
64 bytes from 192.168.0.107: icmp_seq=52 ttl=64 time=6.255 ms
64 bytes from 192.168.0.107: icmp_seq=53 ttl=64 time=6.347 ms
64 bytes from 192.168.0.107: icmp_seq=54 ttl=64 time=9.725 ms
64 bytes from 192.168.0.107: icmp_seq=55 ttl=64 time=6.231 ms
64 bytes from 192.168.0.107: icmp_seq=56 ttl=64 time=16.880 ms
64 bytes from 192.168.0.107: icmp_seq=57 ttl=64 time=5.697 ms
64 bytes from 192.168.0.107: icmp_seq=58 ttl=64 time=7.097 ms
64 bytes from 192.168.0.107: icmp_seq=59 ttl=64 time=5.562 ms
Request timeout for icmp_seq 60
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62
Request timeout for icmp_seq 63
Request timeout for icmp_seq 64
Request timeout for icmp_seq 65
Request timeout for icmp_seq 66
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
Request timeout for icmp_seq 73
Request timeout for icmp_seq 74
Request timeout for icmp_seq 75
Request timeout for icmp_seq 76
Request timeout for icmp_seq 77
Request timeout for icmp_seq 78
Request timeout for icmp_seq 79
Request timeout for icmp_seq 80
Request timeout for icmp_seq 81
Request timeout for icmp_seq 82
Request timeout for icmp_seq 83
Request timeout for icmp_seq 84
Request timeout for icmp_seq 85
Request timeout for icmp_seq 86
Request timeout for icmp_seq 87
Request timeout for icmp_seq 88
Request timeout for icmp_seq 89
Request timeout for icmp_seq 90
Request timeout for icmp_seq 91
Request timeout for icmp_seq 92
Request timeout for icmp_seq 93
Request timeout for icmp_seq 94
Request timeout for icmp_seq 95
Request timeout for icmp_seq 96
Request timeout for icmp_seq 97
Request timeout for icmp_seq 98
Request timeout for icmp_seq 99
Request timeout for icmp_seq 100
64 bytes from 192.168.0.107: icmp_seq=101 ttl=64 time=73.622 ms
64 bytes from 192.168.0.107: icmp_seq=102 ttl=64 time=52.785 ms
64 bytes from 192.168.0.107: icmp_seq=103 ttl=64 time=5.372 ms
64 bytes from 192.168.0.107: icmp_seq=104 ttl=64 time=6.572 ms
64 bytes from 192.168.0.107: icmp_seq=105 ttl=64 time=2.741 ms
64 bytes from 192.168.0.107: icmp_seq=106 ttl=64 time=5.399 ms
64 bytes from 192.168.0.107: icmp_seq=107 ttl=64 time=5.389 ms
64 bytes from 192.168.0.107: icmp_seq=108 ttl=64 time=2.680 ms
64 bytes from 192.168.0.107: icmp_seq=109 ttl=64 time=6.017 ms
64 bytes from 192.168.0.107: icmp_seq=110 ttl=64 time=21.945 ms
64 bytes from 192.168.0.107: icmp_seq=111 ttl=64 time=6.081 ms
64 bytes from 192.168.0.107: icmp_seq=112 ttl=64 time=6.321 ms
64 bytes from 192.168.0.107: icmp_seq=113 ttl=64 time=5.503 ms
64 bytes from 192.168.0.107: icmp_seq=114 ttl=64 time=3.377 ms
64 bytes from 192.168.0.107: icmp_seq=115 ttl=64 time=6.648 ms
64 bytes from 192.168.0.107: icmp_seq=116 ttl=64 time=6.187 ms
64 bytes from 192.168.0.107: icmp_seq=117 ttl=64 time=6.238 ms
64 bytes from 192.168.0.107: icmp_seq=118 ttl=64 time=3.833 ms
64 bytes from 192.168.0.107: icmp_seq=119 ttl=64 time=15.038 ms
Request timeout for icmp_seq 120
Request timeout for icmp_seq 121
Request timeout for icmp_seq 122
Request timeout for icmp_seq 123
Request timeout for icmp_seq 124
Request timeout for icmp_seq 125
Request timeout for icmp_seq 126
Request timeout for icmp_seq 127
Request timeout for icmp_seq 128
Request timeout for icmp_seq 129
Request timeout for icmp_seq 130
Request timeout for icmp_seq 131
Request timeout for icmp_seq 132
Request timeout for icmp_seq 133
Request timeout for icmp_seq 134
Request timeout for icmp_seq 135
Request timeout for icmp_seq 136
Request timeout for icmp_seq 137
Request timeout for icmp_seq 138
Request timeout for icmp_seq 139
Request timeout for icmp_seq 140
Do you have any idea what's wrong? I had to upgrade to more recent kernel because I need newer version of raspistill.


Please post dmesg [run dmesg from bash]
Posts: 6
Joined: Sun Dec 08, 2013 4:24 pm
by MrEngman » Thu Dec 12, 2013 5:13 pm
Hi everyone,

The latest raspbian code loaded with rpi-update has changed the Linux revision to 3.10.24+. The new version appears to run OK with the 8188eu driver from 3.10.23+. https://dl.dropboxusercontent.com/u/80256631/8188eu-20131209.tar.gz

See here for full details


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by speedy901990 » Thu Dec 12, 2013 7:51 pm
I also have problem with this driver. It works when I want to connect to wireless network. But it fails when I turn my Raspberry into AccessPoint mode. The hostapd cannot start. There is the log below.
Code: Select all
pi@raspberrypi ~ $ sudo hostapd -dd /etc/hostapd/hostapd.conf
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
drv->ifindex=3
l2_sock_recv==l2_sock_xmit=0x0xb1d638
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=12 freq=2467 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=13 freq=2472 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=52 freq=5260 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=56 freq=5280 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=60 freq=5300 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=64 freq=5320 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=100 freq=5500 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=104 freq=5520 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=108 freq=5540 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=112 freq=5560 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=116 freq=5580 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=120 freq=5600 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=124 freq=5620 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=128 freq=5640 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=132 freq=5660 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=136 freq=5680 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=140 freq=5700 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=0 dBm
Completing interface initialization
Mode: IEEE 802.11g  Channel: 6  Frequency: 2437 MHz
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x1
RATE[3] rate=110 flags=0x1
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
Flushing old station entries
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Could not connect to kernel driver.
Deauthenticate all stations
+rtl871x_sta_deauth_ops, ff:ff:ff:ff:ff:ff is deauth, reason=2
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=0)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=1)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=2)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=3)
Using interface wlan0 with hwaddr 64:66:b3:25:dc:2f and ssid 'Pi_AP'
Deriving WPA PSK based on passphrase
SSID - hexdump_ascii(len=5):
     50 69 5f 41 50                                    Pi_AP
PSK (ASCII passphrase) - hexdump_ascii(len=9): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
rtl871x_set_wps_assoc_resp_ie
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
random: Got 20/20 bytes from /dev/random
Get randomness: len=32 entropy=0
GMK - hexdump(len=32): [REMOVED]
Get randomness: len=32 entropy=0
Key Counter - hexdump(len=32): [REMOVED]
WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
Get randomness: len=16 entropy=0
GTK - hexdump(len=16): [REMOVED]
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
rtl871x_set_beacon_ops
rtl871x_set_hidden_ssid_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set beacon head/tail or DTIM period
wlan0: Setup of interface done.

Can you help me solve this problem ?
Posts: 2
Joined: Wed Oct 24, 2012 8:56 pm
by bob1122 » Thu Dec 12, 2013 11:03 pm
speedy901990 wrote:I also have problem with this driver. It works when I want to connect to wireless network. But it fails when I turn my Raspberry into AccessPoint mode. The hostapd cannot start. There is the log below.
Code: Select all
pi@raspberrypi ~ $ sudo hostapd -dd /etc/hostapd/hostapd.conf
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
drv->ifindex=3
l2_sock_recv==l2_sock_xmit=0x0xb1d638
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=12 freq=2467 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=13 freq=2472 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=52 freq=5260 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=56 freq=5280 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=60 freq=5300 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=64 freq=5320 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=100 freq=5500 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=104 freq=5520 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=108 freq=5540 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=112 freq=5560 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=116 freq=5580 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=120 freq=5600 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=124 freq=5620 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=128 freq=5640 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=132 freq=5660 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=136 freq=5680 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=140 freq=5700 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=0 dBm
Completing interface initialization
Mode: IEEE 802.11g  Channel: 6  Frequency: 2437 MHz
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x1
RATE[3] rate=110 flags=0x1
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
Flushing old station entries
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Could not connect to kernel driver.
Deauthenticate all stations
+rtl871x_sta_deauth_ops, ff:ff:ff:ff:ff:ff is deauth, reason=2
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=0)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=1)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=2)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
Failed to clear default encryption keys (ifname=wlan0 keyidx=3)
Using interface wlan0 with hwaddr 64:66:b3:25:dc:2f and ssid 'Pi_AP'
Deriving WPA PSK based on passphrase
SSID - hexdump_ascii(len=5):
     50 69 5f 41 50                                    Pi_AP
PSK (ASCII passphrase) - hexdump_ascii(len=9): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
rtl871x_set_wps_assoc_resp_ie
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
random: Got 20/20 bytes from /dev/random
Get randomness: len=32 entropy=0
GMK - hexdump(len=32): [REMOVED]
Get randomness: len=32 entropy=0
Key Counter - hexdump(len=32): [REMOVED]
WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
Get randomness: len=16 entropy=0
GTK - hexdump(len=16): [REMOVED]
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
rtl871x_set_key_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
rtl871x_set_beacon_ops
rtl871x_set_hidden_ssid_ops
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
ioctl[RTL_IOCTL_HOSTAPD]: Operation not supported
Failed to set beacon head/tail or DTIM period
wlan0: Setup of interface done.

Can you help me solve this problem ?


I apologize if I'm incorrectly assessing things, but it may be difficult to get help for a rtl871 based device in a thread for TL725v2 Drivers (which uses 8188eu based drivers). Either you've got the wrong drivers installed, or your asking in a completely wrong place (Mind you, they're both TPLink adapters)
Posts: 6
Joined: Sun Dec 08, 2013 4:24 pm
by MrEngman » Thu Dec 12, 2013 11:24 pm
speedy901990 wrote:I also have problem with this driver. It works when I want to connect to wireless network. But it fails when I turn my Raspberry into AccessPoint mode.

What does command lsusb show for your wifi adaptor.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by speedy901990 » Thu Dec 12, 2013 11:39 pm
I have downloaded drivers that @MrEngman recomended.
Result of lsusb:
Code: Select all
pi@raspberrypi ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 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.
Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp.
Posts: 2
Joined: Wed Oct 24, 2012 8:56 pm
by MrEngman » Fri Dec 13, 2013 12:14 am
speedy901990 wrote:I have downloaded drivers that @MrEngman recomended.
Result of lsusb:
Code: Select all
pi@raspberrypi ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 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.
Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp.

So the wifi is the TL-WN725N V2. I tried setting up an AP just over a week ago and wasn't successful. The Realtek wifi adaptors have been used for APs but need the hostapd included in the Linux image replacing with one from the driver source code.

I based my set up on this tutorial although it is for the EW7811Un (rtl8188cus driver) but is similar for the 8188eu driver. The source for hostapd is included in the 8188eu driver source code.

I will have to try again and see what happens. I will let you know if I can get it working.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by freefish » Fri Dec 13, 2013 12:33 am
Thank you very much for this driver.
Could help me to solve the problem of another device driver?
Please see the below link.
viewtopic.php?f=28&t=63157

I've been trying to compile another device driver, but I still can not add in the driver's version number "+", resulting in not properly inserted in the drive. How to add compile the driver when in the driver's version number symbol "+"?
Posts: 16
Joined: Mon Apr 01, 2013 2:02 am
by MrEngman » Fri Dec 13, 2013 12:48 am
freefish wrote:Thank you very much for this driver.
Could help me to solve the problem of another device driver?
Please see the below link.
viewtopic.php?f=28&t=63157

I've been trying to compile another device driver, but I still can not add in the driver's version number "+", resulting in not properly inserted in the drive. How to add compile the driver when in the driver's version number symbol "+"?

Not sure what the problem is here. Can you post the output of command uname -a to show which version of Linux you are using. You will need the Module.symvers file for the version of Linux you want to use the driver with. Using the wrong one will cause problems and it may not load like you have found. Where can I find the driver source code?


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 3192
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK