I'm using a i686 Architecture on AMD E2-1800 APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux with linux 3.7.10. CONFIG_USB_DEBUG was allready set. I've used an USB 3.0 port previously and now rechecked everything with a USB2.0 port. The result is nearly the same: first connection succeeds (ping response), doing a manual reconnect to the AP leads to the same error. I've done several ifconfig down/ups at the end with no change. dmesg gives: http://bpaste.net/show/93912/ 2013/4/24 Larry Finger <Larry.Finger@xxxxxxxxxxxx>: > On 04/24/2013 11:20 AM, Michael Stahn wrote: >> >> I've just recompiled the kernel and executed the following procedure: >> modprobe rtl8192cu -> plugin in Wlan-Stick -> connect wlan via >> Networkmanager (no connection was established, credentials are >> correct) -> unplug Stick. Attachment contains the dmes-output. > > > Please do not drop the Cc to the Linux wireless mailing list unless you are > requested to send something of a sensitive nature. Always use "Reply to > all". > > [ 448.211707] rtl8192cu: MAC auto ON okay! > [ 448.248820] rtl8192cu: Tx queue select: 0x05 > [ 448.615206] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 464.990166] ehci_hcd 0000:00:16.2: detected XactErr len 0/15360 retry 1 > [ 464.990540] ehci_hcd 0000:00:16.2: detected XactErr len 0/15360 retry 2 > [ 464.990613] hub 3-0:1.0: state 7 ports 4 chg 0000 evt 0004 > [ 464.990642] ehci_hcd 0000:00:16.2: GetStatus port:2 status 001002 0 ACK > POWER sig=se0 CSC > [ 464.990661] hub 3-0:1.0: port 2, status 0100, change 0001, 12 Mb/s > [ 464.990672] usb 3-2: USB disconnect, device number 3 > > That error is something in the USB hub driver. What is your architecture? > > To get a little more detail, please rebuild your kernel with > CONFIG_USB_DEBUG set and post the full log on some paste site. I will likely > need to have the help of the USB expert on this matter, but we need more > details first. > > Larry > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
