Thanks everyone for all the info here!
I'm having a problem after the kernel upgrade from 3.10.25 to 3.10.27. I have the TP-Link TL-WN723N V3 adapter. I had to go through a little song-and-dance (rebuild the driver I think, I didn't take good enough notes) to get this adapter to work on 3.10.25 but it was working great for
a week until I got the bright idea to update the kernel. I've read through 90% of this treat (and others). I downloaded ...20140177 and installed without error per instructions. As you can see in the dmesg I get some errors. Also if I ifup wlan0 I get errors. You can see in iwconfig that the adapter comes up and associates, but then it drops the connection after ~10 sec. When it's up I can ssh in from my PC, ping in/out, whatever. I can watch it pop up in wifi-config gui and then disappear after a few seconds. If I ifdown wlan0, then ifup wlan0 it comes up again, but drops out once more. Help me please!! THANKS!

(sorry, I can't figure how everyone's getting nice screen captures so I had to >> outputs and edit)

Update:
After some additional testing is seems like the adapter will continue to work as long as I'm using it. I removed it from the pi and installed it in the side of my monitor (hub of unknown power). It started working, but then I stopped accessing it for a a minute or so and it stopped again. Thinking it might be a power issue I plugged it into a powered hub. It was working, I started X and browsed, did a speed test, etc. everything was fine for several minutes. I started doing something else on my PC and when I looked at it it had stopped again -- the lights went out. Doing a ifdown/ifup always brings it back, but with the above indicated errors. Is it possible that there is some power saving mode where it shuts off after some period of inactivity?

Sadly I am having issues with the latest version of the driver, any idea what this may cause?
I am able to get it up and running, but wlan0 freezes frequently after various timeframes.
If connected via eth the pi is still accessible, therefore it must be something with the wifi.

I got frustrated and ordered the Edimax EW-07811UN as it was only a few bucks. When I plug it in I get exactly the same symptoms as described above. Can someone please tell me how to rip out the old driver and breath life into this thing? I was under the impression that the Edimax was supposed to work out of the box. ...I guess this means that the adapter is not the problem? Must be something else..

Hi beliaz, it's great to see it's working as an AP for you, giving me at least some hope after all the days spent without any success. I've tried the kernels 3.10.25+, .26+ and .27+, none working with hostapd - always failing with:

I am absolutely new to the r-pi. I have some absolute basic understanding of ubuntu etc. and now I am stuck with the wifi. It is frustrating. My main problem is actually that I have the feeling that my version is a bit strange?!

I am absolutely new to the r-pi. I have some absolute basic understanding of ubuntu etc. and now I am stuck with the wifi. It is frustrating. My main problem is actually that I have the feeling that my version is a bit strange?!

am I doing something wrong? I tried to update everything.. but somehow I am not getting anywhere.
Thank you!!

You appear to have RaspBMC installed. The driver versions I have compiled are for Raspbian. You will need to find a driver compiled for use with RaspBMC to get your wifi working unless it is already included in the linux image.

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

Your new version of the driver has apparently cured all the funky issues I had on my setup. Wifi link is now very stable, iwconfig displays correct quality indicators, random unassoc and related issues are gone. No more random clicks in audio, no more random usb-stick errors, no more DUPs, and driver unloads as expected. Are you using a new code base ?

Your new version of the driver has apparently cured all the funky issues I had on my setup. Wifi link is now very stable, iwconfig displays correct quality indicators, random unassoc and related issues are gone. No more random clicks in audio, no more random usb-stick errors, no more DUPs, and driver unloads as expected. Are you using a new code base ?

1. When compiled directly on the Pi, which is how I normally compile drivers, the module appeared to work OK but could not unload for some reason. File /proc/modules showed it marked as permanent - presumably permanently loaded. This occurred with all versions of 3.10.xx I tried. This also occurred with some other modules I tried.

2. popcornmix suggested I update gcc. I updated gcc to gcc-4.7 and the module compiled OK and would then load and unload OK but I then found it would only keep running for a few hundred seconds and sometimes much less before shutting down the connection. This was even if the power management options were disabled. The driver just kept shutting down randomly even when permanently busy. Prior to this I'd been able to run it 24/7 without any random disconnections.

I have now tried the new(different) source and it appears to have no problems at all. And no need for separate firmware files either. Not a single unexpected disconnect even when left idle for extended periods. Had to patch it to get it to compile. Patch details here.

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

LaFambe wrote:Do you know which version of the driver source is eventually going to end-up in the standard kernel ? I was under the impression that lwfinger's code base was already in staging for 3.12.

Unfortunately probably lwfinger's. Why the original Realtek drivers cannot be used I don't know. I find it particularly annoying that it requires a separate firmware file. Doesn't make life easy when trying to include the driver in images like Berryboot. I'm still stuck trying to figure out how to get the firmware automatically installed.

Rather like the situation with the rtl8188cus driver. Back in the early days of RPi there was a driver that did not work and still doesn't as far as I know. I started compiling the official Realtek driver and made it available via dropbox. Finally someone saw sense and included that in the RPi linux source and it is still in use and working fine as far as I know for most people today.

MrEngman

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

I have installed the driver manually and using LaFambe's script but the dongle either freezes(LED stops flashing) or shuts off(LED turns off) at random times but it always seem to be less than a few minutes. Is there anything I can do to correct this problem? What information can I provide you with?

I would suggest running command sudo rpi-update which will update raspbian to 3.10.28+ #634 and then install the latest driver, 8188eu-20140128.tar.gz.

MrEngman

Edit: snortoise, I have updated the driver for 3.10.27+ #630 which should fix the problems you found with the older version. So if you haven't updated to 3.10.28+ install the updated driver for 3.10.27+ and you should find it works OK now.

Last edited by MrEngman on Thu Feb 06, 2014 12:40 am, edited 1 time in total.

Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

Hi MrEngman and thank you for all you do,
The adaptater works well when I did manually the driver's updated but when I reboot the RPi, I loose all what I did before.
When I reboot, it appears in the loading's script :
"8188eu : disagrees about version of symbol module_layout"
I tried to use the LaFambe´s shell script and reinstall the driver and the RPi answer that the exec format is not good.
Then I reinstall it manually and it works again.

Do you have idea about what to do that the RPi keep the memory of the driver ?
Thanks a lot for your answer.