Arch Linux

symon

Member

Registered: 2014-06-25

Posts: 18

Network just "connecting" on ThinkPad x200s

Hi everyone,
I just reinstalled archlinux on my thinkpad x200s. I also installed gnome. Now this happens: When i plug in an ethernet cable network manager says connecting and then connected and everything works. When I try to connect via wireless it says connecting, then it is connected (but still says connecting) and once i loose the connection i can never connect again.
I have arch linux from another HDD on the same system up and running and no issues there (maybe that helps?!).

lsmod | grep wifi gives this (on both systems):

iwlwifi               156837  1 iwldvm
cfg80211              454161  3 iwlwifi,mac80211,iwldvm

The only difference I could see was the kernel:

Linux archbox 3.15.8-1-ARCH #1 SMP PREEMPT Fri Aug 1 08:51:42 CEST 2014 x86_64 GNU/Linux

and

Linux archbox 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux

(And the HDD, my new one is on SSD with LVM).

This is the end of journalctl -u NetworkManager.service while i am connected to the wifi but it seems like i am not:

Aug 16 18:14:50 archbox NetworkManager[287]: <info> Activation (wls1) Stage 2 of 5 (Device Configure) complete.
Aug 16 18:14:50 archbox NetworkManager[287]: <info> Config: set interface ap_scan to 1
Aug 16 18:14:50 archbox NetworkManager[287]: <info> (wls1): supplicant interface state: inactive -> scanning
Aug 16 18:14:54 archbox NetworkManager[287]: <info> (wls1): supplicant interface state: scanning -> authenticating
Aug 16 18:14:54 archbox NetworkManager[287]: <info> (wls1): supplicant interface state: authenticating -> associating
Aug 16 18:14:54 archbox NetworkManager[287]: <info> (wls1): supplicant interface state: associating -> 4-way handshake
Aug 16 18:14:54 archbox NetworkManager[287]: <info> (wls1): supplicant interface state: 4-way handshake -> completed
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wir
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1) Stage 3 of 5 (IP Configure Start) started...
Aug 16 18:14:54 archbox NetworkManager[287]: <info> (wls1): device state change: config -> ip-config (reason 'none') [50 70 0]
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Aug 16 18:14:54 archbox NetworkManager[287]: <info> dhcpcd started with pid 866
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1) Stage 3 of 5 (IP Configure Start) complete.
Aug 16 18:14:54 archbox NetworkManager[287]: dhcpcd[866]: sending commands to master dhcpcd process
Aug 16 18:14:54 archbox NetworkManager[287]: <info> (wls1): DHCPv4 client pid 866 exited with status 0
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1) Stage 4 of 5 (IPv4 Configure Timeout) started...
Aug 16 18:14:54 archbox NetworkManager[287]: <info> Activation (wls1) Stage 4 of 5 (IPv4 Configure Timeout) complete.

But downgrading did not help at all. I dunno if this is true but i have the feeling that the internet is really slow sometimes on this machine, when i get it to connect.
What also did not help was using wicd network manager.
Strange: Sometimes it works with wifi-menu. And the journalctl does not show any errors on that.

Can anyone help?
Thank you

Last edited by symon (2014-08-16 16:16:55)

symon

Member

Registered: 2014-06-25

Posts: 18

Re: Network just "connecting" on ThinkPad x200s

Hello again
i detected that somehow after the installation and _before_ the setup of gnome and services like "acpid, ntp, dbus, avahi, cups" wifi-menu works pretty fine.
I also detected that after the setup of this services I need to put wls1 down (via ip link set wls1 down) and then wifi-menu worked fine again. I also needed to do a dhcpcd manually but it went fine.

Does that help?
Thank You