2357:0100 TP-Link 8200ND USB Wireless adapter won't authenticate [rtl812cu]

[Shiki]

This device uses an rtl8192cu Realtek driver.

Authentication fails with a WPA2 router, with:
# wlan1: authenticate with .:.:.:.:..
# wlan1: direct probe to ... (try 1/3)
# wlan1: direct probe to ... (try 2/3)
# wlan1: direct probe to ... (try 3/3)
# authentication with ... timed out.

And this goes on and on. No other messages, just this one. Twice, every time I try to connect with it.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: x 1480 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=4ed9b60b-f3d5-446f-87de-f8fc28e2eee6
InstallationDate: Installed on 2013-05-31 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO 208252G
MarkForUpload: True
Package: linux 3.8.0.23.39
PackageArchitecture: amd64
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=7a476825-8d9e-4c9e-b8a8-28d1ae9b258b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-23-generic N/A
 linux-backports-modules-3.8.0-23-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/14/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET92WW (3.22 )
dmi.board.name: 208252G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn208252G:pvrThinkPadT500:rvnLENOVO:rn208252G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 208252G
dmi.product.version: ThinkPad T500
mi.sys.vendor: LENOVO

[Shiki (shiki)]

Attached my dmesg since boot. It contains the problem too.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1186253/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1186253

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc3-saucy/

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

apport information

[Shiki (shiki)]

Sorry for the many logs, I ran apport as requested.
(For some weird reason I didn't have python-apport/launchpad installed. I used the proper 13.04 amd64 image, that I even double checked).

Anyway, installing the kernel, and let's see if something happens. :)

[Shiki (shiki)]

(Sorry about the wifi name, couldn't modify the log files before apport submitted them.
Also: Notice that I enabled iwlwifi later on after I couldn't connect with the USB device!)

[Shiki (shiki)]

Installed the 3.10rc kernel from the URL, but nothing changed.
I do run the new kernel, uname confirms that:
x@x-ThinkPad-T500:~$ uname -a
Linux x-ThinkPad-T500 3.10.0-031000rc3-generic #201305261935 SMP Sun May 26 23:35:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

It's the same issue. Timeout.

[Shiki (shiki)]

I use an openwrt (latest stable) on my router.
So I could even use that to find out the exact problem/find a fix.

What command should I run or which log should I attach?
(It's a TP-Link 1043ND)

[Shiki (shiki)]

I have created a wifi hotspot with my Android phone, with no password and WPA too.
It's the same message, nothing changes. (Thought the "authentication" got something to do with the password... but nope.)

[penalvch (penalvch)]

Shiki, could you please unplug all USB devices, plug in just the problematic USB devices, and then immediately place the following in a terminal and attach the results:
lsusb -v > lsusb-v.log

[Shiki (shiki)]

The bug exists with 3.11rc1 too. I talked with the wifi guys meanwhlie.
Larry Finger (ralink maintainer) bought a device, but no news ever since.

[Shiki (shiki)]

Here is the output.

[Julian Wiedmann (jwiedmann)]

Should be fixed in current -proposed (3.8.0-28.41) with

rtlwifi: rtl8192cu: Add new USB ID for TP-Link TL-WN8200ND

[Shiki (shiki)]

Nope. Does not work. I'll attach my new lsusb and dmesg.
I'm running the new proposed kernel. Larry sent me this fix weeks ago, and it only inits the device.

Like the LED shows up and you can see it in NetworkManager.
But you still cannot connect, as the authentication will time out.

Thanks for your effort, I hope this bug will get fixed one day.

[Shiki (shiki)]

Attaching dmesg. Same auth error can be seen, except I don't have to issue the new ID command by hand.

[Julian Wiedmann (jwiedmann)]

Right, two different bugs. With the device table fixed in -proposed, let's use this bug to track the authentication issue.

[Shiki (shiki)]

You are right. And thanks for keeping track of my bug / fixing the ID one.

[crys (schaefec)]

Any news on that subject? I am facing exactly the same problem.

[penalvch (penalvch)]

crys, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[penalvch (penalvch)]

Shiki, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (3.23). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[Shiki (shiki)]

@Christopher: Sorry I didn't update my bug, only posted on AskUbuntu.

"End of my story? Larry never found the time to investigate the issue. I returned the item as it dropped connection sometimes on Windows as well. They just refunded it and that's it. So yeah. This is a terrible chip, no one should buy a device equipped with such."

Of course the bug is a bug, so if anyone is willing to help investigate matters further, feel free.
I didn't ask for a refund, they just did, without any notice. Not like I mind.
(Time for a "free" N wifi. Which I bet will be this bad, too. hah.)

[penalvch (penalvch)]

Shiki, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1186253/comments/38 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[moloo (netzwerk-7)]

I confirm to have this Bug and have the Hardware, so i changed the Status to Confirmed.

If this is not the right procedure please tell me .. I am relatively new to this system.

[penalvch (penalvch)]

moloo, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[moloo (netzwerk-7)]

it shows an dialog, witch says
"Problem in linux-image-3-13.0-32-generic

The problem cannot be reported:

This is not an official Ubuntu package. Please remove any third party package and try again."

I just installed a fresh version of Ubuntu, to get an clean system. I did nothing to the installation!
and now this!?
What should I do from now?

[penalvch (penalvch)]

moloo, please use https://bugs.launchpad.net/ubuntu/+source/linux/+filebug , and subscribe me to it.