[SOLVED] Networkmanager fails in WIFI on DHCPDISCOVER
Hello,
I have two computers running Arch. Each is up to date. When I use a WIFI usb key to connect to the same SSID, one is working fine and the other isn't.
*edit*
On second thought, there is no difference, I think drivers are to blame
Thank you!
Last edited by ivanoff (2015-04-11 16:13:15)
Problem inexplicably solved itself with an update over the past couple of days. Possibly a systemd or a kernel update?
Similar Messages
-
[SOLVED] NetworkManager failing to connect to wifi networks
Up until yesterday NetworkManager had been working fine on my network. Then yesterday it began dropping internet access (but still reporting that it was connected to the network) and eventually dropping the connection entirely. This has been happening whenever I attempt to connect to the network.
Now, nm will not even connect to the network, it appears to attempt authentication but fails. Ethernet however, works perfectly.
Here are some of my logs:
journalctl
dmesg
lspci
Last edited by tormund (2015-04-19 19:26:06)Xabre wrote:
Apr 19 11:52:22 tormund NetworkManager[352]: <info> (wlp1s0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Is ip-config available on your system?
ip-config isn't a program/package (on linux at least). This message just means that DHCP is timing out.
This thread may be relevant: https://bbs.archlinux.org/viewtopic.php?id=146261. You could also try a different dhcp client. -
[SOLVED] NetworkManager problem with WiFi
Hello,
I try to search on the forum, but I didn't find anythig.
The problem is this one: through NetworkManager I can connect to the wired net, but not to the wireless one. Through rfkill is all unblocked. If I try with che applet, nothing happen, through nmcli it remains pending doing nothig (no output).
I'm using Gnome ad desktop env.
What can I do to connect through the wifi?
Thank you.
Riccardo
Last edited by riccardo (2013-03-12 15:19:35)Output of nmcli con up uuid ***:
** (process:773): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/24: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
Errore: attivazione connessione non riuscita: Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/24/' failed in libnm-glib. -
[solved] Networkmanager failed on shutdown
Hi!
Second post
Well, I try to install quick-init but I have a lot of problems and when I uninstalled it and restore all (I hope so) I see that when I shutdown a FAIL on networkmanager, can anybody help me, please?
And tell me how can I give you more information about it?
Thanks a lot!
Last edited by thearcher (2010-05-17 07:31:33)For the first question, It happens everytime I shutdown the PC but everythings seems to runs well.
In my modules I don't know what cause I'm out of my office now but I think dbus is installed cause docky ask me for it when I installed it.
(excuse my poor english)
Edited: I connect with ssh and see this on my rc.conf: DAEMONS=(syslog-ng hal !network networkmanager @netfs @noip @sshd @crond @alsa @samba @smartd @fam @dnsmasq @preload)
My MODULES are this: MODULES=(!rt2800usb !rt2x00usb)
It's possibly to view a log for the networkmanager?
Thanks for the fast answers!
Last edited by thearcher (2010-05-14 13:39:23) -
Networkmanager failed dhcp on wifi
hi,
I installed archlinux on my laptop, and I prefere for control the connections to use network manager instead the normal way.
So i follow the wiki but networkmager failed to connect to wifi, but they recognize well the essid.
I don't understand where I wrong:
this is my rc.conf
# HARDWARE
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=(snd-hda-intel)
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
MODULES=(ac97_bus snd-mixer-oss snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-midi-event snd-seq snd-hwdep snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-ac97-codec snd-emu10k1 soundcore snd-util-mem fglrx)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
HOSTNAME="arch-laptop"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo !eth0 !eth1)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng dbus hal !network netfs ipw3945d dhcdbd networkmanager kdm)
# End of file
Any help?Hello,
Same problem here, when using NetworkManager for a wifi connection... The "association" with my wifi network is ok, but it seems not to send any dhcp request. I just need to use dhclient in command line but it's not really user-friendly (I mean, I need to open a console, log as root and then ask for the dhcp... ) -
[SOLVED] NetworkManager does not connect to WiFi networks
I'm using `networkmanager` to connect WiFi.
I have selected WiFi Name through `networkmanager`.
Next, enter WiFi Password.
But the problem is, `networkmanager` asks me about password again and again and over again and does not connect to WiFi never !!!!
I'm sure WiFi password that I entered is correct.
Last edited by kamrava (2014-02-22 05:46:37)orschiro wrote:Maybe not satisfying, but can you instead use Wicd?
My problem was solved. `wicd` was not installed on my system.
My Problem solved through :
I have Installed `wicd` and then NetworkManager works like a charm now
$ sudo pacman -S wicd wicd-gtk
Thank you all.
Last edited by kamrava (2014-02-21 11:29:17) -
[SOLVED] NetworkManager unable to enable Wifi
Edit: Finally solved. Disabling the "acer_wmi" module did the trick.
I've been using NetworkManager on my laptop for quite some time now, and it always did a good job... until now!
And in the middle of quite a busy week as well! Damn Murphy...
I noticed there was an update for it and Archer as I am, I of course updated from networkmanager-0.8.1-1-x86_64 and network-manager-applet-0.8.1-2-x86_64, to networkmanager-0.8.2-3-x86_64 and network-manager-applet-0.8.2-2-x86_64.
When updating I got a message that filesystem permissions of /var/lib/NetworkManager we're set to 755, and the package expected 700.
Should not be a problem, but I set the permissions to 700 for good measure.
Next boot, using the new version, I was unable to get NetworkManager to engage my Wifi. "Enable Wireless" just did nothing. It's not turning on my Wifi and nm-applet is not marking it as active either, no matter how many times I click it. I also tried disabling Networking and re-enabling it all, no luck.
Reloaded nm-applet a couple of times, no dice. Restarted the networkmanager deamon as well, still nothing.
nm-applet does not produce any error messages for me to check out, only things it tells me when I kill and start it:
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
It only talks about placing itself in the notification area, which is in working order.
My laptop is a Sony Vaio VPCY11S1E (know as Sony Vaio Y series, first model), Wifi card is an Atheros AR9285 (ath9k) and it runs up-to-date Arch x86_64. I run a hand configured -ck patched kernel and also the Arch regular kernel.
Come to think of it, I did not try the stock kernel yet, but I doubt it's the cause of the problem.
Because I reverted back to NetworkManager 0.8.1 and it's working like it always did again.
So I got working Wifi with NM 0.8.1, no working Wifi with 0.8.2.
Any pointers or insights you might have are greatly appreciated!
Last edited by Ultraman (2011-03-06 00:48:32)Oh sorry. I did do that, a bit.
I have a tail of the everything.log outputted to my desktop, and noticed NetworkManager is deactivating the Wifi (Reason 2).
I'm gonna check out what "Reason 2" might mean, and i'll see if I can post a nice snippet of the log here...
Log snippet
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> NetworkManager (version 0.8.2) is starting...
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Read config file /etc/NetworkManager/nm-system-settings.conf
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> trying to start the modem manager...
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> found WiFi radio killswitch rfkill1 (at /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0d/SNY5001:00/rfkill/rfkill1) (driver Sony Notebook Control Driver)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> found WiFi radio killswitch rfkill4 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill4) (driver <unknown>)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> found WiFi radio killswitch rfkill3 (at /sys/devices/platform/acer-wmi/rfkill/rfkill3) (driver acer-wmi)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WiFi disabled by radio killswitch; enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Networking is enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): carrier is OFF
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): new Ethernet device (driver: 'atl1c' ifindex: 2)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): now managed
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): device state change: 1 -> 2 (reason 2)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): bringing up device.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): preparing device.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): deactivating device (reason: 2).
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/eth0
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): now managed
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): bringing up device.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): deactivating device (reason: 2).
And that's where it ends.
What jumps out is: "Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WiFi disabled by radio killswitch; enabled by state file"
Which is incorrect, the switch is ON. I also tried switching it OFF and ON again (IT Crowd! ). No effect.
I also see it's seeing multiple killswitches, where I only have one. But that's not the real problem here.
Somehow NM 0.8.2 is thinking my Wifi killswitch is turned off when it isn't.
To see if NM 0.8.1 does anything different, I checked out it's log, which looks like this:
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> NetworkManager (version 0.8.1) is starting...
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Read config file /etc/NetworkManager/nm-system-settings.conf
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> trying to start the modem manager...
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> found WiFi radio killswitch rfkill1 (at /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0d/SNY5001:00/rfkill/rfkill1) (driver Sony Notebook Control Driver)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> found WiFi radio killswitch rfkill4 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill4) (driver <unknown>)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> found WiFi radio killswitch rfkill3 (at /sys/devices/platform/acer-wmi/rfkill/rfkill3) (driver acer-wmi)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> WiFi disabled by radio killswitch; enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Networking is enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): carrier is OFF
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): new Ethernet device (driver: 'atl1c' ifindex: 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): now managed
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): device state change: 1 -> 2 (reason 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): bringing up device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): preparing device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): deactivating device (reason: 2).
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/eth0
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): now managed
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): deactivating device (reason: 2).
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): supplicant interface state: starting -> ready
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) starting connection 'JoostenWL'
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
It's doing the exact same thing as NM 0.8.2 is it not?
Only it does bring up the interface by trying again by the looks of it.
Note the following behaviour of 0.8.1:
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): now managed
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): deactivating device (reason: 2).
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): supplicant interface state: starting -> ready
NM 0.8.2 stops after the message "deactivating the device (reason: 2)."
Last edited by Ultraman (2010-11-23 15:01:44) -
[SOLVED] NetworkManager dumped core
Symptoms: WiFi randomly drops out.
More specifically: NetworkManager core dumps and network-manager-applet stops (Gnome 3.8)
If anyone has suggestions, I'd be grateful. I'm at a loss, other than disabling NetworkManager and enabling netctl. Details follow below.
Thanks so much!
uname -r
3.9.0-2-ARCH
uname -m
x86_64
lspci -v
Network controller: Intel Corporation Centrino Advanced-N 6205
rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
iwconfig
enp0s25 no wireless extensions.
wlp3s0 IEEE 802.11abgn ESSID:"The Way 5GHz"
Mode:Managed Frequency:5.18 GHz Access Point: 00:26:F2:F2:E7:D5
Bit Rate=65 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=54/70 Signal level=-56 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:230 Invalid misc:113 Missed beacon:0
lo no wireless extensions.
journalctl -u NetworkManager --since=today
-- Reboot --
May 04 14:04:19 arch systemd[1]: Starting Network Manager...
May 04 14:04:20 arch NetworkManager[284]: <info> NetworkManager (version 0.9.8.0) is starting...
May 04 14:04:20 arch NetworkManager[284]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
May 04 14:04:20 arch NetworkManager[284]: <info> WEXT support is enabled
May 04 14:04:21 arch NetworkManager[284]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager ma
May 04 14:04:21 arch NetworkManager[284]: keyfile: parsing Auto The Way 5GHz ...
May 04 14:04:21 arch NetworkManager[284]: keyfile: read connection 'Auto The Way 5GHz'
May 04 14:04:21 arch NetworkManager[284]: <info> monitoring kernel firmware directory '/lib/firmware'.
May 04 14:04:21 arch NetworkManager[284]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi hardware radio set enabled
May 04 14:04:21 arch systemd[1]: Started Network Manager.
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WWAN enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WiMAX enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> Networking is enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <warn> failed to allocate link cache: (-10) Operation not supported
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): carrier is OFF
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): new Ethernet device (driver: 'e1000e' ifindex: 3)
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): exported as /org/freedesktop/NetworkManager/Devices/0
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/enp0
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): using nl80211 for WiFi device control
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): driver supports Access Point (AP) mode
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> error poking ModemManager: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop
May 04 14:04:21 arch NetworkManager[284]: <info> wpa_supplicant started
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:21 arch NetworkManager[284]: <warn> Trying to remove a non-existant call id.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: starting -> ready
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
May 04 14:04:25 arch NetworkManager[284]: <info> Auto-activating connection 'Auto The Way 5GHz'.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) starting connection 'Auto The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless): connection 'Auto The Way 5GHz' has security, and secrets exist. No new
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'ssid' value 'The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'scan_ssid' value '1'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'auth_alg' value 'OPEN'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'psk' value '<omitted>'
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Config: set interface ap_scan to 1
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: inactive -> scanning
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: scanning -> authenticating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associating -> associated
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associated -> completed
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless netwo
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 04 14:04:28 arch NetworkManager[284]: <info> dhcpcd started with pid 447
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning IP6 addrconf.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
May 04 14:04:28 arch dhcpcd[447]: version 5.6.8 starting
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:28 arch dhcpcd[447]: [color=#FF0000]wlp3s0: sendmsg: Cannot assign requested address[/color]
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: rebinding lease of 192.168.10.59
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: acknowledged 192.168.10.59 from 192.168.10.1
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: checking for 192.168.10.59
May 04 14:04:32 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:33 arch dhcpcd[447]: wlp3s0: leased 192.168.10.59 for 86400 seconds
May 04 14:04:33 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed preinit -> bound
May 04 14:04:33 arch NetworkManager[284]: <info> address 192.168.10.59
May 04 14:04:33 arch NetworkManager[284]: <info> prefix 24 (255.255.255.0)
May 04 14:04:33 arch NetworkManager[284]: <info> gateway 192.168.10.1
May 04 14:04:33 arch NetworkManager[284]: <info> nameserver '192.168.10.1'
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Policy set 'Auto The Way 5GHz' (wlp3s0) as default for IPv4 routing and DNS.
May 04 14:04:34 arch NetworkManager[284]: <info> Writing DNS information to /usr/sbin/resolvconf
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): roamed from BSSID 90:27:E4:5E:98:24 (The Way 5GHz) to 00:26:F2:F2:E7:D5 (The Way 5GHz)
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) successful, device activated.
May 04 14:04:36 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: no IPv6 Routers available
May 04 21:04:49 arch NetworkManager[284]: <info> (wlp3s0): IP6 addrconf timed out or failed.
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 04 21:04:50 arch systemd[1]: NetworkManager.service: main process exited, code=dumped, status=6/ABRT
May 04 21:04:50 arch systemd[1]: MESSAGE=Unit NetworkManager.service entered failed state.
May 04 21:04:50 arch systemd-coredump[1036]: [color=#FF0000]Process 284 (NetworkManager) dumped core.[/color]
journalctl -u wpa_supplicant --since=today
-- Reboot --
May 04 14:04:21 arch systemd[1]: Starting WPA supplicant...
See dmesg at Pastebin
[edited May 7, 2013]
I'm marking this topic SOLVED, though more accurately, I should say that I've worked around the problem.
I achieved a stable wireless connection by changing APs, which leads me to believe that the underlying problem is upstream. Specifically, the problem is most likely that NetworkManager is not compatible with all APs. In my case, when I connect to a Netgear NDR3700v1 running dd-wrt, NetworkManager and nn-applet crashed randomly and frequently. However, after changing to an Apple Airport AP, I achieved a stable connection without crashes.
Bottomline: if you experience wireless connection troubles with NetworkManager and nm-applet, the problem may be that NetworkManager is not "compatible" with your AP hardware.
Last edited by hcra (2013-05-07 20:50:36)b1tgl0w wrote:Is it normal for crond to run as the root user?
Completely normal. I'd be asking the question "was I hacked" if I found cron NOT running as root.
I'd say your computer just crashed. -
NetworkManager fails multiple times to connect to wirless network
Hello Arch-Community!
I run a Dell Vostro V131 and a Dell XPS 13 with an up to date Arch Linux with Gnome Shell as desktop enviroment. My internet connection is established by an AVM Fritzbox 7490 over wireless lan. The WLAN connection works with a windows pc and my android devices absolutely stable. As soon I get into the reach of wlan, my smartphone connects without any issues.
With Arch I've got the following problem: After a restart or standby mode, the NetworkManager tries to connect to my wireless lan. After about 30 seconds it fails and the icon vanishes out of the notification bar. After a short moment it tries again, it fails, it tries, it fails... until it magically works and the computer is logged into my wireless network.
To get some logs i killed the NetworkManager task and restarted it by hand. In the following log you see NetworkManager starting and failing a couple of logins with the message "association took too long, failing activation". At the end NetworkManager reports "Activation (wlp18s0) successful, device activated" and wlan works... I didn't change a thing.
I would be very thankful if someone might be able to help me figure out what might go wrong.
Thanks!
Christoph
$ sudo /usr/bin/NetworkManager --no-daemon
NetworkManager[3251]: <info> NetworkManager (version 0.9.8.10) is starting...
NetworkManager[3251]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
NetworkManager[3251]: <info> WEXT support is enabled
NetworkManager[3251]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
NetworkManager[3251]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
NetworkManager[3251]: keyfile: parsing KIT-OPENVPN ...
NetworkManager[3251]: keyfile: read connection 'KIT-OPENVPN'
NetworkManager[3251]: keyfile: parsing Littlehelper ...
NetworkManager[3251]: keyfile: read connection 'Littlehelper'
NetworkManager[3251]: keyfile: parsing Santa ...
NetworkManager[3251]: keyfile: read connection 'Santa'
NetworkManager[3251]: <info> monitoring kernel firmware directory '/lib/firmware'.
NetworkManager[3251]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:12:00.0/ieee80211/phy0/rfkill0) (driver ath9k)
NetworkManager[3251]: <info> WiFi hardware radio set enabled
NetworkManager[3251]: <info> WiFi enabled by radio killswitch; enabled by state file
NetworkManager[3251]: <info> WWAN enabled by radio killswitch; enabled by state file
NetworkManager[3251]: <info> WiMAX enabled by radio killswitch; enabled by state file
NetworkManager[3251]: <info> Networking is enabled by state file
NetworkManager[3251]: <info> (wlp18s0): using nl80211 for WiFi device control
NetworkManager[3251]: <info> (wlp18s0): driver supports Access Point (AP) mode
NetworkManager[3251]: <info> (wlp18s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 4)
NetworkManager[3251]: <info> (wlp18s0): exported as /org/freedesktop/NetworkManager/Devices/0
NetworkManager[3251]: <info> (wlp18s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[3251]: <info> (wlp18s0): bringing up device.
NetworkManager[3251]: <info> (wlp18s0): preparing device.
NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'managed') [2]
NetworkManager[3251]: <warn> failed to allocate link cache: (-26) Protocol mismatch
NetworkManager[3251]: <info> (enp19s0): carrier is OFF
NetworkManager[3251]: <info> (enp19s0): new Ethernet device (driver: 'r8169' ifindex: 2)
NetworkManager[3251]: <info> (enp19s0): exported as /org/freedesktop/NetworkManager/Devices/1
NetworkManager[3251]: <info> (enp19s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
NetworkManager[3251]: <info> (enp19s0): bringing up device.
NetworkManager[3251]: <info> (enp19s0): preparing device.
NetworkManager[3251]: <info> (enp19s0): deactivating device (reason 'managed') [2]
NetworkManager[3251]: <info> Added default wired connection 'Kabelgebundene Verbindung 1' for /sys/devices/pci0000:00/0000:00:1c.2/0000:13:00.0/net/enp19s0
NetworkManager[3251]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
NetworkManager[3251]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
NetworkManager[3251]: <info> (wlp18s0) supports 4 scan SSIDs
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: starting -> ready
NetworkManager[3251]: <info> (wlp18s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
NetworkManager[3251]: <warn> Trying to remove a non-existant call id.
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: ready -> disconnected
NetworkManager[3251]: <info> (wlp18s0) supports 4 scan SSIDs
NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> inactive
NetworkManager[3251]: <info> Config: set interface ap_scan to 1
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
NetworkManager[3251]: <warn> Activation (wlp18s0/wireless): association took too long, failing activation.
NetworkManager[3251]: <info> (wlp18s0): device state change: config -> failed (reason 'SSID not found') [50 120 53]
NetworkManager[3251]: <info> NetworkManager state is now DISCONNECTED
NetworkManager[3251]: <warn> Activation (wlp18s0) failed for connection 'Santa'
NetworkManager[3251]: <info> (wlp18s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'none') [0]
NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> inactive
NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3251]: <info> Activation (wlp18s0/wireless): access point 'Santa' has security, but secrets are required.
NetworkManager[3251]: <info> (wlp18s0): device state change: config -> need-auth (reason 'none') [50 60 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3251]: <info> (wlp18s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3251]: <info> Config: set interface ap_scan to 1
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
NetworkManager[3251]: <warn> Activation (wlp18s0/wireless): association took too long, failing activation.
NetworkManager[3251]: <info> (wlp18s0): device state change: config -> failed (reason 'SSID not found') [50 120 53]
NetworkManager[3251]: <info> NetworkManager state is now DISCONNECTED
NetworkManager[3251]: <warn> Activation (wlp18s0) failed for connection 'Santa'
NetworkManager[3251]: <info> (wlp18s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'none') [0]
NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> inactive
NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3251]: <info> Activation (wlp18s0/wireless): access point 'Santa' has security, but secrets are required.
NetworkManager[3251]: <info> (wlp18s0): device state change: config -> need-auth (reason 'none') [50 60 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3251]: <info> (wlp18s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3251]: <info> Config: set interface ap_scan to 1
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
NetworkManager[3251]: <warn> Activation (wlp18s0/wireless): association took too long, failing activation.
NetworkManager[3251]: <info> (wlp18s0): device state change: config -> failed (reason 'SSID not found') [50 120 53]
NetworkManager[3251]: <info> NetworkManager state is now DISCONNECTED
NetworkManager[3251]: <warn> Activation (wlp18s0) failed for connection 'Santa'
NetworkManager[3251]: <info> (wlp18s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[3251]: <info> (wlp18s0): deactivating device (reason 'none') [0]
NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
NetworkManager[3251]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> inactive
NetworkManager[3251]: <info> Auto-activating connection 'Santa'.
NetworkManager[3251]: <info> Activation (wlp18s0) starting connection 'Santa'
NetworkManager[3251]: <info> (wlp18s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[3251]: <info> NetworkManager state is now CONNECTING
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3251]: <info> Activation (wlp18s0/wireless): access point 'Santa' has security, but secrets are required.
NetworkManager[3251]: <info> (wlp18s0): device state change: config -> need-auth (reason 'none') [50 60 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[3251]: <info> (wlp18s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[3251]: <info> (wlp18s0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[3251]: <info> Activation (wlp18s0/wireless): connection 'Santa' has security, and secrets exist. No new secrets needed.
NetworkManager[3251]: <info> Config: added 'ssid' value 'Santa'
NetworkManager[3251]: <info> Config: added 'scan_ssid' value '1'
NetworkManager[3251]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[3251]: <info> Config: added 'auth_alg' value 'OPEN'
NetworkManager[3251]: <info> Config: added 'psk' value '<omitted>'
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[3251]: <info> Config: set interface ap_scan to 1
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: inactive -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> disconnected
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: disconnected -> scanning
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: scanning -> authenticating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: authenticating -> associating
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: associating -> associated
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: associated -> 4-way handshake
NetworkManager[3251]: <info> (wlp18s0): supplicant interface state: 4-way handshake -> completed
NetworkManager[3251]: <info> Activation (wlp18s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Santa'.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager[3251]: <info> (wlp18s0): device state change: config -> ip-config (reason 'none') [50 70 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
NetworkManager[3251]: <info> dhcpcd started with pid 3261
NetworkManager[3251]: <info> Activation (wlp18s0) Beginning IP6 addrconf.
dhcpcd[3261]: version 6.4.0 starting
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 3 of 5 (IP Configure Start) complete.
dhcpcd[3261]: wlp18s0: adding address fe80::e0b1:110:f1ea:b935
dhcpcd[3261]: DUID 00:01:00:01:1b:3e:cd:f2:78:2b:cb:cf:a1:ab
dhcpcd[3261]: wlp18s0: IAID 4e:93:d0:c9
NetworkManager[3251]: <info> (wlp18s0): DHCPv4 state changed nbi -> preinit
dhcpcd[3261]: wlp18s0: rebinding lease of 192.168.178.49
dhcpcd[3261]: wlp18s0: soliciting an IPv6 router
dhcpcd[3261]: wlp18s0: leased 192.168.178.49 for 864000 seconds
dhcpcd[3261]: wlp18s0: adding route to 192.168.178.0/24
NetworkManager[3251]: <info> (wlp18s0): DHCPv4 state changed preinit -> reboot
NetworkManager[3251]: <info> address 192.168.178.49
NetworkManager[3251]: <info> prefix 24 (255.255.255.0)
NetworkManager[3251]: <info> gateway 192.168.178.1
NetworkManager[3251]: <info> nameserver '192.168.178.1'
NetworkManager[3251]: <info> domain name 'fritz.box'
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 5 of 5 (IPv4 Commit) started...
dhcpcd[3261]: wlp18s0: removing route to 192.168.178.0/24
NetworkManager[3251]: <info> (wlp18s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
NetworkManager[3251]: <info> Activation (wlp18s0) Stage 5 of 5 (IPv4 Commit) complete.
NetworkManager[3251]: <info> (wlp18s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
NetworkManager[3251]: <info> NetworkManager state is now CONNECTED_GLOBAL
NetworkManager[3251]: <info> Policy set 'Santa' (wlp18s0) as default for IPv4 routing and DNS.
NetworkManager[3251]: <info> Writing DNS information to /usr/bin/resolvconf
NetworkManager[3251]: <info> Activation (wlp18s0) successful, device activated.Thanks for your reply.
We use classes12 because we had no needs to upgrade, like TIMESTAMP...
Maybe we could try change driver.
And nothing in the code loop to try that many times. Like written in the example code we made a little sample page just to test the connection. That's all.
I don't have any control of the pool connection. But the people that are doing it says to me that there is no settings configured to attempt connection 200 times. -
[SOLVED] networkmanager.service and accounts-daemon.service take slow
Hello everyone!
I have noticed that my laptop booting is slow, then I read the wiki and google around but there seems no answer for me.
It seems that this all because of the NetworkManager, so I post it here.
This is my basic information:
$ uname -a [3:03:07]
Linux hp 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
And
$ systemd-analyze [3:04:25]
Startup finished in 3.363s (firmware) + 1.382s (loader) + 2.824s (kernel) + 24.506s (userspace) = 32.077s
And
$ systemd-analyze blame [3:04:12]
13.456s NetworkManager.service
11.414s accounts-daemon.service
3.289s libvirtd.service
2.205s gdm.service
1.094s polkit.service
1.048s systemd-vconsole-setup.service
981ms wpa_supplicant.service
958ms alsa-restore.service
852ms boot.mount
636ms systemd-remount-fs.service
634ms sys-kernel-debug.mount
609ms dev-hugepages.mount
569ms sys-kernel-config.mount
520ms dev-mqueue.mount
508ms systemd-tmpfiles-setup-dev.service
506ms tmp.mount
476ms systemd-udev-trigger.service
420ms systemd-journal-flush.service
358ms kmod-static-nodes.service
268ms systemd-timesyncd.service
260ms colord.service
240ms systemd-backlight@backlight:intel_backlight.service
236ms systemd-update-utmp.service
And
$ systemd-analyze critical-chain [3:07:05]
graphical.target @24.506s
└─multi-user.target @24.506s
└─libvirtd.service @21.216s +3.289s
└─network.target @21.142s
└─NetworkManager.service @7.685s +13.456s
└─basic.target @7.684s
└─timers.target @7.683s
└─systemd-tmpfiles-clean.timer @7.683s
└─sysinit.target @7.652s
└─swap.target @7.652s
└─dev-disk-by\x2duuid-7006949a\x2d4625\x2d4d7e\x2db101\x2dbe714c525296.swap @7.458s +191ms
└─dev-disk-by\x2duuid-7006949a\x2d4625\x2d4d7e\x2db101\x2dbe714c525296.device @7.457s
And
$ journalctl _SYSTEMD_UNIT=accounts-daemon.service
8月 24 02:49:20 hp accounts-daemon[264]: started daemon version 0.6.37
And
$ journalctl _SYSTEMD_UNIT=NetworkManager.service [3:04:39]
8月 24 02:49:12 hp NetworkManager[258]: <info> NetworkManager (version 0.9.10.1) is starting...
8月 24 02:49:12 hp NetworkManager[258]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
8月 24 02:49:12 hp NetworkManager[258]: <info> WEXT support is enabled
8月 24 02:49:12 hp NetworkManager[258]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
8月 24 02:49:20 hp NetworkManager[258]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the Netw
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_5D05CE
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_5D05CE 1
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_1244B0 1
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_1244B0
8月 24 02:49:20 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/9
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/UCWiFi-77777
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/130
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/yangmafu
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/Hotspot
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/TP-LINK_281E42
8月 24 02:49:21 hp NetworkManager[258]: <info> new connection /etc/NetworkManager/system-connections/NewStar
8月 24 02:49:21 hp NetworkManager[258]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
8月 24 02:49:21 hp NetworkManager[258]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:07:00
8月 24 02:49:21 hp NetworkManager[258]: <info> WiFi hardware radio set enabled
8月 24 02:49:21 hp NetworkManager[258]: <info> WWAN hardware radio set enabled
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
8月 24 02:49:21 hp NetworkManager[258]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
8月 24 02:49:21 hp NetworkManager[258]: <info> WiFi enabled by radio killswitch; enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> WWAN enabled by radio killswitch; enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> WiMAX enabled by radio killswitch; enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> Networking is enabled by state file
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): link connected
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): carrier is ON
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
8月 24 02:49:21 hp NetworkManager[258]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): carrier is OFF
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): new Ethernet device (driver: 'r8169' ifindex: 2)
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): exported as /org/freedesktop/NetworkManager/Devices/1
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): preparing device
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): created default wired connection 'Wired connection 1'
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): using nl80211 for WiFi device control
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): driver supports Access Point (AP) mode
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): new 802.11 WiFi device (driver: 'rt2800pci' ifindex: 3)
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): exported as /org/freedesktop/NetworkManager/Devices/2
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): preparing device
8月 24 02:49:23 hp NetworkManager[258]: <info> wpa_supplicant started
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: starting -> ready
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): device state change: unavailable -> disconnected (reason 'supplicant-available')
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: ready -> disconnected
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: disconnected -> inactive
8月 24 02:49:25 hp NetworkManager[258]: <info> Auto-activating connection 'NewStar'.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) started...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTING
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) complete.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) starting...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: prepare -> config (reason 'none') [40 50 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1/wireless): connection 'NewStar' has security, and secrets exist. No ne
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): exported as /org/freedesktop/NetworkManager/Devices/1
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): preparing device
8月 24 02:49:22 hp NetworkManager[258]: <info> (eno1): created default wired connection 'Wired connection 1'
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): using nl80211 for WiFi device control
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): driver supports Access Point (AP) mode
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): new 802.11 WiFi device (driver: 'rt2800pci' ifindex: 3)
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): exported as /org/freedesktop/NetworkManager/Devices/2
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:22 hp NetworkManager[258]: <info> (wlo1): preparing device
8月 24 02:49:23 hp NetworkManager[258]: <info> wpa_supplicant started
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: starting -> ready
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): device state change: unavailable -> disconnected (reason 'supplicant-available')
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: ready -> disconnected
8月 24 02:49:23 hp NetworkManager[258]: <info> (wlo1) supports 4 scan SSIDs
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: disconnected -> inactive
8月 24 02:49:25 hp NetworkManager[258]: <info> Auto-activating connection 'NewStar'.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) starting connection 'NewStar'
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) started...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTING
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) scheduled...
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 1 of 5 (Device Prepare) complete.
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) starting...
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): device state change: prepare -> config (reason 'none') [40 50 0]
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1/wireless): connection 'NewStar' has security, and secrets exist. No ne
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'ssid' value 'NewStar'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'scan_ssid' value '1'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'auth_alg' value 'OPEN'
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: added 'psk' value '<omitted>'
8月 24 02:49:25 hp NetworkManager[258]: <info> Activation (wlo1) Stage 2 of 5 (Device Configure) complete.
8月 24 02:49:25 hp NetworkManager[258]: <info> Config: set interface ap_scan to 1
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: inactive -> authenticating
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: authenticating -> associating
8月 24 02:49:25 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: associating -> associated
8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: associated -> 4-way handshake
8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wir
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) scheduled.
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) started...
8月 24 02:49:26 hp NetworkManager[258]: <info> (wlo1): device state change: config -> ip-config (reason 'none') [50 70 0]
8月 24 02:49:26 hp NetworkManager[258]: <info> Activation (wlo1) Beginning DHCPv4 transaction (timeout in 45 seconds)
8月 24 02:49:27 hp NetworkManager[258]: <info> dhcpcd started with pid 346
8月 24 02:49:27 hp NetworkManager[258]: <info> Activation (wlo1) Stage 3 of 5 (IP Configure Start) complete.
8月 24 02:49:27 hp dhcpcd[346]: version 6.4.3 starting
8月 24 02:49:27 hp NetworkManager[258]: <info> (wlo1): DHCPv4 state changed nbi -> preinit
8月 24 02:49:27 hp dhcpcd[346]: DUID 00:01:00:01:1b:84:72:e9:b8:76:3f:39:7c:5b
8月 24 02:49:27 hp dhcpcd[346]: wlo1: IAID 3f:39:7c:5b
8月 24 02:49:27 hp dhcpcd[346]: wlo1: soliciting an IPv6 router
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: version 6.4.3 starting
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: DUID 00:01:00:01:1b:84:72:e9:b8:76:3f:39:7c:5b
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: IAID 3f:39:7c:5b
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: soliciting an IPv6 router
8月 24 02:49:28 hp dhcpcd[346]: wlo1: rebinding lease of 192.168.1.100
8月 24 02:49:28 hp NetworkManager[258]: dhcpcd[346]: wlo1: rebinding lease of 192.168.1.100
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): carrier is OFF
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): new Bridge device (driver: 'bridge' ifindex: 4)
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): exported as /org/freedesktop/NetworkManager/Devices/3
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): preparing device
8月 24 02:49:28 hp NetworkManager[258]: <info> (virbr0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
8月 24 02:49:32 hp dhcpcd[346]: wlo1: leased 192.168.1.100 for 7200 seconds
8月 24 02:49:32 hp dhcpcd[346]: wlo1: adding route to 192.168.1.0/24
8月 24 02:49:32 hp NetworkManager[258]: dhcpcd[346]: wlo1: leased 192.168.1.100 for 7200 seconds
8月 24 02:49:32 hp NetworkManager[258]: dhcpcd[346]: wlo1: adding route to 192.168.1.0/24
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): DHCPv4 state changed preinit -> reboot
8月 24 02:49:33 hp NetworkManager[258]: <info> address 192.168.1.100
8月 24 02:49:33 hp NetworkManager[258]: <info> plen 24 (255.255.255.0)
8月 24 02:49:33 hp NetworkManager[258]: <info> gateway 192.168.1.1
8月 24 02:49:33 hp NetworkManager[258]: <info> server identifier 192.168.1.1
8月 24 02:49:33 hp NetworkManager[258]: <info> lease time 7200
8月 24 02:49:33 hp NetworkManager[258]: <info> nameserver '192.168.1.1'
8月 24 02:49:33 hp NetworkManager[258]: nm_ip4_config_add_nameserver: assertion 'new != 0' failed
8月 24 02:49:33 hp NetworkManager[258]: <info> nameserver '0.0.0.0'
8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) started...
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
8月 24 02:49:33 hp NetworkManager[258]: <info> Activation (wlo1) Stage 5 of 5 (IPv4 Commit) complete.
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
8月 24 02:49:33 hp NetworkManager[258]: <info> (wlo1): device state change: secondaries -> activated (reason 'none') [90 100 0]
8月 24 02:49:33 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTED_LOCAL
8月 24 02:49:34 hp NetworkManager[258]: <info> NetworkManager state is now CONNECTED_GLOBAL
8月 24 02:49:34 hp NetworkManager[258]: <info> Policy set 'NewStar' (wlo1) as default for IPv4 routing and DNS.
8月 24 02:49:34 hp NetworkManager[258]: <info> Writing DNS information to /usr/bin/resolvconf
8月 24 02:49:35 hp NetworkManager[258]: <info> Activation (wlo1) successful, device activated.
8月 24 02:49:35 hp NetworkManager[258]: <info> startup complete
8月 24 02:49:40 hp dhcpcd[346]: wlo1: no IPv6 Routers available
8月 24 02:49:40 hp NetworkManager[258]: dhcpcd[346]: wlo1: no IPv6 Routers available
Last edited by callofdutyops (2014-08-26 14:48:22)ooo wrote:
callofdutyops wrote:But I wonder whether there's some improvement?
Do you mean why there's an improvement after removing the journal files?
first of all, I hope that you know what systemd journal is, and what files you just deleted.
systemd journal stores all system logs in database files in /var/log/journal/
every time you boot up your system, journald will log the entire boot process and stores in its database (and continue logging of course).
over time the journal will get huge (unless you limit its size) and fragmented, which could slow down reading and writing from the it greatly.
so, if writing the log during the boot process slows down greatly, it will certainly have an detrimental effect on overall boot speed.
I hope that makes sense
I think I saw this mentioned on some systemd TODO list, so developers should aware of this and possibly trying to figure out some workaround.
In the meantime limiting journal size is probably a good idea.
If you happened to be using btrfs, disabling COW for files in /var/log/journal and 'autodefrag' mount option may also help some.
also defragmenting the files in /var/log/journal if your file system supports it
First of all, thanks to your very clear explanation!
English is not my mother tongue, so I think I express me in a wrong way.Sorry for this!
What I exactly want to mean is that is it possible to make booting more faster? -
[SOLVED] NetworkManager doesn't connect Wifi at boot
Hi all,
I am again here with a new problem.
I setup my arch box to boot into console where i login and do startx to open DE.
The problem is, NetworkManager doesn't connect to WiFi on boot.
However it is working absolutely fine under DE (KDE). As soon as DE opens, KdeWallet ask for password and then WiFi connected.
But i want to connect to WiFi in console (without X). It is quite annoying to fire DE just to do a wget.
I checked, NetworkManager service is enabled and running.
Here is output of different commands that may help
dmesg | grep wlp3s0
[ 5.798296] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[ 9.970511] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 9.970615] bridge-wlp3s0: device is wireless, enabling SMAC
[ 9.970617] bridge-wlp3s0: up
[ 9.970620] bridge-wlp3s0: attached
[ 9.970645] bridge-wlp3s0: disabling the bridge
[ 9.983966] bridge-wlp3s0: down
[ 9.983972] bridge-wlp3s0: detached
systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Thu 2014-12-18 20:33:26 IST; 1min 35s ago
Main PID: 341 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─341 /usr/bin/NetworkManager --no-daemon
systemctl --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
bluetooth.service loaded active running Bluetooth service
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
kmod-static-nodes.service loaded active exited Create list of required static device nodes for the current kernel
NetworkManager.service loaded active running Network Manager
polkit.service loaded active running Authorization Manager
systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:acpi_video0
systemd-fsck@dev-disk-by\x2duuid-696f8115\x2d2fed\x2d4b28\x2d9fab\x2d834f9c40ece4.service loaded active exited File System Check on /dev/disk/by-uuid/696f8115-2fed-4b28-9fab-834f9c40ece4
systemd-fsck@dev-disk-by\x2duuid-af474e61\x2d31bb\x2d484d\x2db12f\x2d2923fc9cd4f5.service loaded active exited File System Check on /dev/disk/by-uuid/af474e61-31bb-484d-b12f-2923fc9cd4f5
systemd-journal-flush.service loaded active exited Trigger Flushing of Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
[email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill0
[email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill1
[email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill2
[email protected] loaded active exited Load/Save RF Kill Switch Status of rfkill3
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
[email protected] loaded active running User Manager for UID 1000
vmware.service loaded active exited VMware daemon
vnstat.service loaded active running vnStat network traffic monitor
wpa_supplicant.service loaded active running WPA supplicant
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
30 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Can someone guide me?
Last edited by samtech09 (2014-12-19 14:06:05)Hi since no one else was able to help yet I will share this which I see from the Wiki:
Once the NetworkManager daemon is started, it will automatically connect to any available "system connections" that have already been configured. Any "user connections" or unconfigured connections will need nmcli or an applet to configure and connect.
Do you have system level connections defined with the necessary keys as opposed to just user connections? Sorry I don't have specifics as on my laptop I always just used the kde applet and my desktop is wired.
edit: to add if you have the authentication info stored in your wallet I don't think networkmanager has any way to get to it until you start KDE. I could be wrong. Look for another way to define it at the system level perhaps? Just a guess.
Last edited by davidm (2014-12-18 20:57:07) -
[solved] NetworkManager does not see the wifi channel 13
Hello!
I have a problem that NetworkManager did not see the wifi network, which broadcasts on channel 13. How to install the drivers for the network to be visible?
Last edited by ghsaehas (2015-01-18 16:57:39)Install and configure crda:
https://www.archlinux.org/packages/core/x86_64/crda/
http://wireless.kernel.org/en/developer … atory/CRDA -
[SOLVED] Problem with Networkmanager and two WiFi cards
I have two WiFi cards, one onboard my laptop, one USB. I use the USB one since gets a stronger signal, but the other one tries to connect.
Is there a way of stoping that.
I don't want to cancel the possibility of using it, just when I plug the USB antenna.
Thank you
Last edited by Frezeeer (2013-02-10 20:41:24)progandy wrote:Is there an entry for your onboard wifi in rfkill? Then block it when pluggin in the usb stick and unblock it lateron.
Thanks for the reply.
This is what I get:
$ rfkill list
0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: samsung-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
4: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
If I try to "block" either number 2 or number 4. The WiFi disconects. It's as if they were the same card.
Any ideas?
Once again thank you -
[SOLVED] Wireless fails after suspending (Realtek 8192se)
This problem is already solved on the first post: I spent so long trying to solve it that I thought people should know the solution.
I have a Lenovo X100e with a Realtek 8192SE wireless card. I'm running kernel 3.0. The machine has, since upgrading to the 3.0 kernel had the annoying problem of failing wireless connections after suspending: I'll have a running wireless connection, then suspend the machine, and then wake the machine up and the machine cannot connect to any wireless network (perhaps the same one I was connected to before, in the same place).
Things that did not work:
Installing the Realtek drivers from their website
Downgrading the kernel from 3.1 to 3.0
Using wicd instead of networkmanager
Walking around
Other distributions
The solution was to put an entry in /etc/pm/config.d/config:
SUSPEND_MODULES="rtl8192se rtlwifi mac80211 cfg80211"
Now the machine reconnects with no problems.
This may be the solution to the other big problem I was having with the 3.1 kernel: I would suspend the machine by any means and the screen goes black and the machine becomes non-responsive without actually suspending. I may try upgrading to the 3.1 kernel and adding radeon to the SUSPEND_MODULES list above.Found out more which might be significant for madwifi users:
According to the wiki I loaded the following modules in rc.conf: ath-hal, ath9k, wlan
Beside this one line in the modprobe.conf should be added: alias ath0 ath_pci. This way wicd as well as networkmanager used ath0 for connecting to wireless.
After the update I noticed that there is another wifi device in ifconfig listed: wlan0. So I suspected that 2 devices pointing at the same hardware may cause the instability, but de-activating one by ifconfig didn't help. Now I noticed by loading the modules one by one that the new ath9k is already defining wlan0 and the wireless starts working without loading the module wlan. It looks stable so far, but if I should be right I'm impossibly the only one having this trouble.
Confirmation would be nice, but I will mark this thread "solved" now. -
Lenovo Flex2 15: NetworkManager issue with WiFi in Gnome3 & battery
I've installed Arch on a Lenovo Flex2 15 and most of the things are working nicely. However 1 issue with NetworkManager is driving me nuts.
I have the following system in use:
Gnome 3.14.1 overview:
Memory 7.7GiB
Processor Intel Core i3-4010U CPU @ 1.70GHz x 4
Graphics Intel Hasswell Mobile
Base system Arch Linux 64-bit
Disk 329.0GB
[dennisf@hossman ~]$ uname -a
Linux hossman 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64 GNU/Linux
[dennisf@hossman ~]$ screenfetch
-`
.o+` dennisf@hossman
`ooo/ OS: Arch Linux
`+oooo: Kernel: x86_64 Linux 3.16.4-1-ARCH
`+oooooo: Uptime: 1h 39m
-+oooooo+: Packages: 765
`/:-:++oooo+: Shell: bash 4.3.30
`/++++/+++++++: Resolution: 1920x1080
`/++++++++++++++: WM: GNOME Shell
`/+++ooooooooooooo/` WM Theme: Adwaita
./ooosssso++osssssso+` GTK Theme: Not Found [GTK2], Not Found [GTK3]
.oossssso-````/ossssss+` Icon Theme: Not Found
-osssssso. :ssssssso. Font: Not Found
:osssssss/ osssso+++. CPU: Intel Core i3-4010U CPU @ 1.7GHz
/ossssssss/ +ssssooo/- RAM: 1096MB / 7897MB
`/ossssso+/:- -:/+osssso+-
`+sso+:-` `.-/+oso:
`++:. `-/+/
.` `/
Whenever I connect to a wireless network with the network applet in the top right of the screen, it keeps "connecting" even though it has already connected. This does not happen when I disable WiFi and use the cable. The connected cable icon is show properly.
http://snag.gy/DVj9Z.jpg
I have disabled netctl
$ sudo systemctl disable netctl
How can I make the applet show that the connection has been succesfully established?
Bonus question is that on Windows the laptop can run for hours, but in Arch it's drained considerably faster. I also have a Dell XPS L502x and since Linux was installed the battery died pretty quickly because it drained so fast and we had to charge it constantly. That laptop is left with a 15 minute charge at 100%. The new Lenovo somehow takes 3 hours to charge from 0 to 100% and drains in about the same time. The same applet in the top right also keeps saying "Estimating...". I have installed PowerTOP and ran a diagnostics. Is it save enough to apply everything suggested?
Last edited by InFerYes (2014-10-23 08:43:43)The Red cross usually appears when the battery has failed.
If you already tried the hard reset and the drivers update, then there doesn't seem to be much that you can do.
Get it repaired from Lenovo while you are still in warranty, that would be my suggestion.
Current System - Lenovo Y510P, GT755M SLI, 8GB RAM, 1TB HDD + 24GB SSD
When your plans fail, your Real Story begins!!
Maybe you are looking for
-
How to fill forms in adobe reader with lithuanian fonts?
How to fill forms in adobe reader with lithuanian fonts? when i switch on my pc alt+shift to lithuanian language i can only use 2 lithuanian fonts, for other lithuanian fonts i get only blank could someone help me to solve this case?
-
Hi, I recently bought AT200 from Germany. It works well except that I don't know how to connect it to PC for file exchanging. I used Acer tablet before and it worked in a wink. I tried to install all drivers, the MTP USB shows that it fails. My OS is
-
i´ve found a site with a lot of bios and drivers for nvidia vga card series. http://whitebunny.demon.nl/hardware/chipset_nvidia.html
-
I put together a simple DVD with one button pointing to a movie. I marked the disolve transition using the button info (inspector window). The resulting burn did not render the disolve - garbage breakup in the video. I changed to fade through black a
-
Disk read error whilst trying to install vista
Bios Techy help needed here. I'm using a pentium e6300 dual core with a P35 neo-F. I've tried to load the drivers disk after attempting to set the bios. At each time after saving bios and attempt to load those drivers for vista and raid a message is