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?
Thanks!
-Ken
On 2015-02-05 22:11, Larry Finger wrote:
> On 02/05/2015 12:56 AM, Ken D'Ambrosio wrote:
>
> Did the update to the troy branch of the rtlwifi_new repo fix the
> problem?
Sadly, no. Exact same errors. So I looked at your previous e-mail,
which I've pasted (and commented about), below:
> Do any ACPI warning messages appear in the early boot log?
> I found some mention of a module named thinkpad_acpi. Is it loaded?
There's a bunch of ACPI stuff, some of which seems related:
[ 8.548934] thinkpad_acpi: Unsupported brightness interface, please
contact [email protected]
[ 8.549028] thinkpad_acpi: radio switch found; radios are enabled
[ 8.549135] thinkpad_acpi: This ThinkPad has standard ACPI backlight
brightness control, supported by the ACPI video driver
[ 8.549137] thinkpad_acpi: Disabling thinkpad-acpi brightness events
by default...
[ 8.550374] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio
is unblocked
[ 8.551069] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is
unblocked
The lack of an "rfkill switch" for WiFi might be disconcerting at first,
until you read the corresponding kernel doc,
/usr/src/linux/Documentation/laptops/thinkpad-acpi.txt:
0x1005 0x04 FN+F5 Radio. Enables/disables
the internal Bluetooth hardware
and W-WAN card if left in control
of the firmware. Does not affect
the WLAN card.
Should be used to turn on/off all
radios (Bluetooth+W-WAN+WLAN),
really.
Additionally:
hotkey_radio_sw:
If the ThinkPad has a hardware radio switch, this
attribute will read 0 if the switch is in the "radios
disabled" position, and 1 if the switch is in the
"radios enabled" position.
A quick visit to /sys/devices/platform/thinkpad_acpi/hotkey_radio_sw
shows it with a value of "1", so, as far as I can tell, ACPI is not
blocking the WiFi radio.
> Sometimes this can be caused by some state left by Windows. Do you
> dual boot?
Perish the thought. While I haven't booted Windows, neither have I
blown away the partition; if you'd like me to boot into it and
initialize the card, I'd be willing to give that a try.
Lastly, however, is something weird that makes me think that the extreme
step of using Windows may not be required: the USB WiFi I use because my
internal WiFi isn't working is an RTL8188SU. If I leave both of them in
when I initialize, SOMETIMES I can get the 8192EE to work -- even after
I remove the 8188SU. But I haven't once gotten the 8192EE to work
without the 8188SU also inserted. And I can't reproduce this
functionality reliably.
-Ken
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.
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.
Larry
On 02/05/2015 12:56 AM, Ken D'Ambrosio wrote:
Did the update to the troy branch of the rtlwifi_new repo fix the problem?
Larry
On 02/06/2015 12:11 AM, Ken D'Ambrosio wrote:
> P.S. I'm sorry, I left this out: I only get the same errors during a manual
> module load. At boot time, things seem to go somewhat more smoothly -- though
> still fails to connect to anything. I've attached my dmesg text so you can
> parse it more fully.
That log is useful. You do not need to boot Windows. I have two things for you
to try.
1. Your wireless is authenticating and associating, but is being kicked off by
the watchdog timer. Please create a file named /etc/modprobe.d/50-rtl8192ee.conf
with one line in it that says "disable_watchdog=1". Then reboot to see if that
helps. Send me the dmesg output starting with
wlan0: send auth to c0:3f:0e:dd:30:98 (try 1/3)
wlan0: authenticated
wlan0: associate with c0:3f:0e:dd:30:98 (try 1/3)
wlan0: RX AssocResp from c0:3f:0e:dd:30:98 (capab=0x421 status=0 aid=3)
2. Reboot with your USB adapter in and send me the whole dmesg output.
Thanks,
Larry
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...
-Ken
P.S. I'm sorry, I left this out: I only get the same errors during a
manual module load. At boot time, things seem to go somewhat more
smoothly -- though still fails to connect to anything. I've attached my
dmesg text so you can parse it more fully.
-Ken
On 2015-02-06 00:57, Ken D'Ambrosio wrote:
> On 2015-02-05 22:11, Larry Finger wrote:
>> On 02/05/2015 12:56 AM, Ken D'Ambrosio wrote:
>>
>> Did the update to the troy branch of the rtlwifi_new repo fix the
>> problem?
>
> Sadly, no. Exact same errors. So I looked at your previous e-mail,
> which I've pasted (and commented about), below:
>
>> Do any ACPI warning messages appear in the early boot log?
>> I found some mention of a module named thinkpad_acpi. Is it loaded?
>
> There's a bunch of ACPI stuff, some of which seems related:
>
> [ 8.548934] thinkpad_acpi: Unsupported brightness interface, please
> contact [email protected]
> [ 8.549028] thinkpad_acpi: radio switch found; radios are enabled
> [ 8.549135] thinkpad_acpi: This ThinkPad has standard ACPI
> backlight brightness control, supported by the ACPI video driver
> [ 8.549137] thinkpad_acpi: Disabling thinkpad-acpi brightness
> events by default...
> [ 8.550374] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio
> is unblocked
> [ 8.551069] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is
> unblocked
>
> The lack of an "rfkill switch" for WiFi might be disconcerting at
> first, until you read the corresponding kernel doc,
> /usr/src/linux/Documentation/laptops/thinkpad-acpi.txt:
> 0x1005 0x04 FN+F5 Radio. Enables/disables
> the internal Bluetooth hardware
> and W-WAN card if left in control
> of the firmware. Does not affect
> the WLAN card.
> Should be used to turn on/off all
> radios (Bluetooth+W-WAN+WLAN),
> really.
> Additionally:
> hotkey_radio_sw:
> If the ThinkPad has a hardware radio switch, this
> attribute will read 0 if the switch is in the "radios
> disabled" position, and 1 if the switch is in the
> "radios enabled" position.
>
> A quick visit to /sys/devices/platform/thinkpad_acpi/hotkey_radio_sw
> shows it with a value of "1", so, as far as I can tell, ACPI is not
> blocking the WiFi radio.
>
>> Sometimes this can be caused by some state left by Windows. Do you
>> dual boot?
>
> Perish the thought. While I haven't booted Windows, neither have I
> blown away the partition; if you'd like me to boot into it and
> initialize the card, I'd be willing to give that a try.
>
> Lastly, however, is something weird that makes me think that the
> extreme step of using Windows may not be required: the USB WiFi I use
> because my internal WiFi isn't working is an RTL8188SU. If I leave
> both of them in when I initialize, SOMETIMES I can get the 8192EE to
> work -- even after I remove the 8188SU. But I haven't once gotten the
> 8192EE to work without the 8188SU also inserted. And I can't
> reproduce this functionality reliably.
>
> -Ken
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
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
On 02/05/2015 12:56 AM, Ken D'Ambrosio wrote:
> Feb 5 01:51:19 minasithil kernel: [ 3141.801171] rtl8192ee 0000:03:00.0:
> Refused to change power state, currently in D3
Above is the serious problem. The wifi device is not powering on. Sometimes this
can be caused by some state left by Windows. Do you dual boot?
Do any ACPI warning messages appear in the early boot log?
I found some mention of a module named thinkpad_acpi. Is it loaded?
I have asked the Realtek people if they have any suggestions.
Larry