All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ken D'Ambrosio <ken@jots.org>
Cc: linux-wireless@vger.kernel.org, Larry Finger <larry.finger@gmail.com>
Subject: Re: rtl8192ee (Thinkpad T440s)
Date: Thu, 05 Feb 2015 01:38:20 -0600	[thread overview]
Message-ID: <54D31DEC.9030002@lwfinger.net> (raw)
In-Reply-To: <8f26bf9461a88199ef8d8c86f7ee98f9@webmail.jots.org>

On 02/05/2015 12:56 AM, Ken D'Ambrosio wrote:
> Hi!  Want to thank you for the reply.  Gave it a shot; no dice.  See comments
> below.
>
> On 2015-02-02 19:00, Larry Finger wrote:
>> On 02/02/2015 05:24 PM, Ken D'Ambrosio wrote:
>>> Hi, all.  Just got a new Thinkpad, and needless to say, tried to fire it up on
>>> the network.  Ubuntu 14.04 didn't have the driver, so I tried 14.10, which did.
>>> I thought I was good until I tried to connect; the laptop would see all the
>>> advertised WAPs, but wouldn't connect to any of them (including my security-free
>>> ones).  I then downloaded the 3.19 RC and tried that -- same deal.  I see a few
>>> extra git commits in -next; any idea if that will be of any assistance?  Is
>>> there anything I can dig through in my logs to help flesh out what the
>>> problem is?
>>
>> Logs are always helpful. As some of us do not use Ubuntu, a kernel
>> version as shown by 'uname -r' is a lot more helpful that what version
>> of Ubuntu you are using.
>
> Sorry; I'll be more specific going forward.  Current kernel I'm using is
> 3.19.0-rc7-next-20150204.  The included driver did not work:
>
> ------------------------ cut here ----------------------------------------------
>
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation (wlan0)
> starting connection 'whateveryouwant'
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> (wlan0): device state
> change: disconnected -> prepare (reason 'none') [30 40 0]
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> NetworkManager state is
> now CONNECTING
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation (wlan0) Stage
> 1 of 5 (Device Prepare) scheduled...
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation (wlan0) Stage
> 1 of 5 (Device Prepare) started...
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation (wlan0) Stage
> 2 of 5 (Device Configure) scheduled...
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation (wlan0) Stage
> 1 of 5 (Device Prepare) complete.
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation (wlan0) Stage
> 2 of 5 (Device Configure) starting...
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> (wlan0): device state
> change: prepare -> config (reason 'none') [40 50 0]
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation
> (wlan0/wireless): connection 'whateveryouwant' requires no security.  No secrets
> needed.
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Config: added 'ssid'
> value 'whateveryouwant'
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Config: added 'scan_ssid'
> value '1'
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Config: added 'key_mgmt'
> value 'NONE'
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Activation (wlan0) Stage
> 2 of 5 (Device Configure) complete.
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> Config: set interface
> ap_scan to 1
> Feb  5 01:05:21 minasithil NetworkManager[864]: <info> (wlan0): supplicant
> interface state: disconnected -> scanning
> Feb  5 01:05:46 minasithil NetworkManager[864]: <warn> Activation
> (wlan0/wireless): association took too long, failing activation.
> Feb  5 01:05:46 minasithil NetworkManager[864]: <info> (wlan0): device state
> change: config -> failed (reason 'SSID not found') [50 120 53]
> Feb  5 01:05:46 minasithil NetworkManager[864]: <info> NetworkManager state is
> now DISCONNECTED
> Feb  5 01:05:46 minasithil NetworkManager[864]: <warn> Activation (wlan0) failed
> for connection 'whateveryouwant'
> Feb  5 01:05:46 minasithil NetworkManager[864]: <info> (wlan0): device state
> change: failed -> disconnected (reason 'none') [120 30 0]
> Feb  5 01:05:46 minasithil NetworkManager[864]: <info> (wlan0): deactivating
> device (reason 'none') [0]
> Feb  5 01:05:46 minasithil NetworkManager[864]: <info> (wlan0): supplicant
> interface state: scanning -> disconnected
> Feb  5 01:05:46 minasithil NetworkManager[864]: <warn> Couldn't disconnect
> supplicant interface: This interface is not connected.
>
> ------------------------ cut here ----------------------------------------------
>
>> Kernel 3.19-rc4 from the wireless-drivers repo contains all those
>> commits in -next, and it works fine here. At this point, I have been
>> connected for 27 hours with a WPA2 connection.
>>
>> You can also try the repo at
>> http://github.com/lwfinger/rtlwifi-new.git. The master branch should
>> be OK. If not, try the troy branch.
>
> I tried both branches; they both failed identically:
> Feb  5 01:51:19 minasithil kernel: [ 3141.801171] rtl8192ee 0000:03:00.0:
> Refused to change power state, currently in D3
> Feb  5 01:51:19 minasithil kernel: [ 3141.801349]
> rtl8192ee:_rtl92ee_read_adapter_info():<0-0> RTL819X Not boot from eeprom, check
> it !!
> Feb  5 01:51:19 minasithil kernel: [ 3141.801375] Using firmware
> rtlwifi/rtl8192eefw_new.bin
> Feb  5 01:51:19 minasithil kernel: [ 3141.803189] ieee80211 phy2: Selected rate
> control algorithm 'rtl_rc'
> Feb  5 01:51:19 minasithil kernel: [ 3141.803855] rtlwifi: wireless switch is on
> Feb  5 01:51:19 minasithil kernel: [ 3141.825219] rtl8192ee 0000:03:00.0 wlan8:
> renamed from wlan0
> Feb  5 01:51:19 minasithil kernel: [ 3141.899361]
> rtl8192ee:rtl92ee_hw_init():<0-0> Init MAC failed
> Feb  5 01:51:19 minasithil kernel: [ 3141.977804]
> rtl8192ee:rtl92ee_hw_init():<0-0> Init MAC failed
> [repeat ad nauseum until module is removed]
> Feb  5 01:51:26 minasithil kernel: [ 3148.373955] IPv6: ADDRCONF(NETDEV_UP):
> wlan8: link is not ready
>
> Thanks for any insights...

I heard from the Realtek engineer already, and he reminded me that we know of 
this problem. One pin of the PCI interface is not correctly powered, and that 
causes a boot from efuse to fail. The troy branch has code to work around this 
condition; however it was not turned on. If you pull again, this option is now 
enabled. See https://github.com/lwfinger/rtlwifi_new/issues/3 to read what has 
previously been posted.

Larry


  parent reply	other threads:[~2015-02-05  7:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 23:24 rtl8192ee (Thinkpad T440s) Ken D'Ambrosio
2015-02-03  0:00 ` Larry Finger
2015-02-05  6:56   ` Ken D'Ambrosio
2015-02-05  7:24     ` Larry Finger
2015-02-05  7:38     ` Larry Finger [this message]
2015-02-06  3:11     ` Larry Finger
2015-02-06  5:57       ` Ken D'Ambrosio
2015-02-06  6:11         ` Ken D'Ambrosio
2015-02-06 15:11           ` Larry Finger

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=54D31DEC.9030002@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=ken@jots.org \
    --cc=larry.finger@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.