From: Flaminigo <sunnyiez@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: rtl8192ce.ko doesn't work with 802.11n?
Date: Wed, 11 May 2011 14:29:06 -0500 [thread overview]
Message-ID: <BANLkTikOw0j8hLBRf6m1p7REpJvNf3mqCw@mail.gmail.com> (raw)
MY university deployed 802.11n wireless LAN. However, my new T420
cannot connect to the network under ubuntu 11.04. I found the driver
for realtek 8188CE is rtl8192ce.ko, rtlwifi. I asked network
administrator to help me. They told me my wireless adapter didn't work
well with the 802.11n network. Is this because of the driver? The
following are the wpa_supplicant output. FYI
------------------
Trying to authenticate with 00:0b:85:97:33:0c (SSID='tamulink-wpa'
freq=2462 MHz)
Trying to associate with 00:0b:85:97:33:0c (SSID='tamulink-wpa' freq=2462 MHz)
Associated with 00:0b:85:97:33:0c
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-FAILURE EAP authentication failed
CTRL-EVENT-DISCONNECTED bssid=00:0b:85:97:33:0c reason=7
Authentication with 00:00:00:00:00:00 timed out.
Failed to initiate AP scan.
Trying to authenticate with 00:24:6c:d0:48:42 (SSID='tamulink-wpa'
freq=2462 MHz)
Trying to associate with 00:24:6c:d0:48:42 (SSID='tamulink-wpa' freq=2462 MHz)
Associated with 00:24:6c:d0:48:42
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=26 -> NAK
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
CTRL-EVENT-EAP-PEER-CERT depth=3 subject='/L=ValiCert Validation
Network/O=ValiCert, Inc./OU=ValiCert Class 2 Policy Validation
Authority/CN=http://www.valicert.com//emailAddress=info@valicert.com'
CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=The Go Daddy Group,
Inc./OU=Go Daddy Class 2 Certification Authority'
CTRL-EVENT-EAP-PEER-CERT depth=1
subject='/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com,
Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure
Certification Authority/serialNumber=07969287'
CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/O=net.tamu.edu/OU=Domain
Control Validated/CN=net.tamu.edu'
EAP-MSCHAPV2: Authentication succeeded
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
WPA: Key negotiation completed with 00:24:6c:d0:48:42 [PTK=CCMP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:24:6c:d0:48:42 completed
(auth) [id=0 id_str=]
Michael MIC failure detected
WPA: Sending EAPOL-Key Request (error=1 pairwise=0 ptk_set=1 len=99)
Michael MIC failure detected
WPA: Sending EAPOL-Key Request (error=1 pairwise=0 ptk_set=1 len=99)
TKIP countermeasures started
CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=14
^CCTRL-EVENT-TERMINATING - signal 2 received
--
Regards
sunny
next reply other threads:[~2011-05-11 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 19:29 Flaminigo [this message]
2011-05-12 1:55 ` rtl8192ce.ko doesn't work with 802.11n? James
2011-05-12 13:57 ` Songgang Xu
2011-05-12 13:59 ` Flaminigo
2011-05-12 14:57 ` Larry Finger
2011-05-14 15:20 ` Larry Finger
2011-05-15 1:23 ` Flaminigo
2011-05-15 21:32 ` Flaminigo
2011-05-15 22:19 ` Larry Finger
2011-05-16 13:48 ` Flaminigo
2011-05-16 14:54 ` Larry Finger
2011-05-16 15:20 ` Flaminigo
2011-05-16 20:15 ` Gábor Stefanik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikOw0j8hLBRf6m1p7REpJvNf3mqCw@mail.gmail.com \
--to=sunnyiez@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).