Network Manager Fails on Boot

I'm not too sure exactly what is going on. I am quite new to arch. When I boot, and start my WM (i3), I have to disable and then reenable Network manager before it will work. I use the nm-applet, and just right click "Disable Networking" and then enable it. I'm not at all sure where to start to figure it out. I have another laptop, exact same setup, exact same installation. And network Manager starts on boot no problem. Any help would be appreciated, thanks.

What is in the journal and what does `systemctl status...` tell you?

Similar Messages

  • Network Manager fails to detect unsecured network.

    My current laptop uses a clean install of Arch Linux with the latest gnome-shell release. NetworkManager has no problem connecting to the wireless networks at home, but the problem I have is at college.
    My college has an open wireless network; sometimes it fails to show in network-manager-applet. That's the first problem. The second problem, If it does show, it'll fail to connect. In order for me to connect, I had to install the iw package and type sudo iw eth1 connect <network-name> after it fails. Only then will it connect.
    How do I fix this so that NetworkManager will stop acting up?
    Here's the wireless adapter installed and the driver it's using. (I use AUR's broadcom-wl package because it can detect more networks and doesn't act up for me.)
    [dbdii407@laptop ~]$ lspci | grep Broadcom
    07:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
    [dbdii407@laptop ~]$ lsmod | grep wl
    wl                          2558087  0
    lib80211                3949       2    wl,lib80211_crypt_tkip
    cfg80211              177058    1    wl
    After connecting through iw
    Thank you very much!
    Last edited by dbdii407 (2012-10-31 18:55:47)

    Maybe it is a "mixed interface issue", if that's the case, then you should read this: https://wiki.archlinux.org/index.php/Ud … ork_device
    Hope it helps.
    Last edited by RozenTensai (2012-12-09 18:40:33)

  • Network Manager fails to connect with Huawei E3276 modem after upgrade

    Hi,
    I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
    I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
    I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
    Error: failed to connect modem: Only IPv4 is supported by this modem.
    I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
    Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
    I would be grateful for any advice.
    After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
    Before upgrade (KDE 4.14)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
    mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
    mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
    mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    Linux Mint 17.1 KDE (works the same like Arch before update)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
    May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
    May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
    May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
    May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
    May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
    May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Last edited by Shocker (2015-05-07 19:18:43)

    This week, after update, modem works again.
    However, there's a new bug in the kernel, which was not there before:
    kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    but the modem works and connects to the network.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
    may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

  • Network Manager fails to connect with Sierra Wireless 3G/4G modem

    Hi,
    I have three Asus Laptops running with Arch (Asus N56VZ, Asus F3JC, Asus UL80VS). All laptops work with Cinnamon Desktop. Everything works fine except 3G Modem in Network Manager. I have two USB modems: Sierra Wireless AirCard 310U and Sierra Wireless AirCard 320U.
    Modems had worked fine in end of year 2012, when NetworkManager version was 0.9.6.4 and ModemManager 0.6.0.0. After update (NM >0.8.X.X, MM >0.7.X. - when the ModemManager.service appeared) until now, I can't connect to the internet on all Asus laptops. Since 2013 I have to use wvdial, because in wvdial modems works fine. It is Arch problem, because in Linux Mint 15 I can connect with NetworkManager.
    Sierra AirCard 310U - When I'm connecting to the internet, modem reboots itself.
    Sierra AirCard 320U - When I'm connecting to the internet, Network Manager can't obtain DHCP address.
    I would be grateful for any help.
    Sierra Wireless AirCard 310U (USB 3G Modem) log:
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) starting connection 'Orange PL'
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect started...
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Simple connect state (3/8): Enable
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    aug 22 13:41:35 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    aug 22 13:41:35 AsusN56VZ ModemManager[308]: <warn> (ttyUSB2): port attributes not fully set
    aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    aug 22 13:41:38 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:41:39 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:41:40 AsusN56VZ kernel: usb 3-2: USB disconnect, device number 3
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: mm_serial_port_close: assertion `priv->open_count > 0' failed
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (4/8): Wait to get fully enabled
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (5/8): Register
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> (tty/ttyUSB2): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
    aug 22 13:41:40 AsusN56VZ ModemManager[308]: <info> Simple connect state (6/8): Bearer
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB0: Sierra USB modem converter now disconnected from ttyUSB0
    aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.0: device disconnected
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: resubmit read urb failed.(-19)
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB1: Sierra USB modem converter now disconnected from ttyUSB1
    aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.1: device disconnected
    aug 22 13:41:40 AsusN56VZ kernel: sierra ttyUSB2: Sierra USB modem converter now disconnected from ttyUSB2
    aug 22 13:41:40 AsusN56VZ kernel: sierra 3-2:1.3: device disconnected
    aug 22 13:41:40 AsusN56VZ kernel: sierra_net 3-2:1.7 wwp0s20u2i7: unregister 'sierra_net' usb-0000:00:14.0-2, Sierra Wireless USB-to-WWAN Modem
    aug 22 13:41:40 AsusN56VZ kernel: ModemManager[308]: segfault at 28 ip 0000000000433350 sp 00007ffff409e088 error 4 in ModemManager[400000+e0000]
    aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service: main process exited, code=dumped, status=11/SEGV
    aug 22 13:41:40 AsusN56VZ systemd[1]: Unit ModemManager.service entered failed state.
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> ModemManager disappeared from bus
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): device state change: prepare -> unmanaged (reason 'removed') [40 10 36]
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): deactivating device (reason 'removed') [36]
    aug 22 13:41:40 AsusN56VZ laptop-mode[2414]: Laptop mode
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): cleaning up...
    aug 22 13:41:40 AsusN56VZ NetworkManager[309]: <info> (ttyUSB2): taking down device.
    aug 22 13:41:40 AsusN56VZ laptop-mode[2415]: enabled, not active
    aug 22 13:41:40 AsusN56VZ systemd-coredump[2336]: Process 308 (ModemManager) dumped core.
    aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
    aug 22 13:41:40 AsusN56VZ systemd[1]: ModemManager.service holdoff time over, scheduling restart.
    aug 22 13:41:40 AsusN56VZ systemd[1]: Stopping Modem Manager...
    aug 22 13:41:40 AsusN56VZ systemd[1]: Starting Modem Manager...
    aug 22 13:41:43 AsusN56VZ kernel: sierra_net 3-2:1.7 (unregistered net_device): usb_control_msg failed, status -19
    Sierra Wireless AirCard 320U (3G/4G Modem) log:
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) starting connection 'Orange PL'
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) scheduled...
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) started...
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) complete.
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect started...
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Simple connect state (3/8): Enable
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling)
    aug 22 13:48:02 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB3): port attributes not fully set
    aug 22 13:48:02 AsusN56VZ ModemManager[314]: <warn> (ttyUSB4): port attributes not fully set
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering)
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home)
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '0', MNC: '0', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:48:05 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP location updated (MCC: '260', MNC: '3', Location area code: '4FB9', Cell ID: '9C65539')
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (4/8): Wait to get fully enabled
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (5/8): Register
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (6/8): Bearer
    aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> WWAN now enabled by management service
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Simple connect state (7/8): Connect
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (registered -> connecting)
    aug 22 13:48:06 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
    aug 22 13:48:06 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: access technology changed (unknown -> hsdpa, hsupa)
    aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connecting -> connected)
    aug 22 13:48:09 AsusN56VZ ModemManager[314]: <info> Simple connect state (8/8): All done
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) scheduled...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) starting...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: prepare -> config (reason 'none') [40 50 0]
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): bringing up device.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) successful.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) scheduled.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 2 of 5 (Device Configure) complete.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) started...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: config -> ip-config (reason 'none') [50 70 0]
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (wwp0s20u2i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
    aug 22 13:48:09 AsusN56VZ kernel: IPv6: ADDRCONF(NETDEV_UP): wwp0s20u2i7: link is not ready
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> dhclient started with pid 2351
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) complete.
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) started...
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Internet Systems Consortium DHCP Client 4.2.5-P1
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Copyright 2004-2013 Internet Systems Consortium.
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: All rights reserved.
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: For info, please visit https://www.isc.org/software/dhcp/
    aug 22 13:48:09 AsusN56VZ dhclient[2351]:
    aug 22 13:48:09 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): DHCPv4 state changed nbi -> preinit
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Listening on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on LPF/wwp0s20u2i7/8e:1d:fe:e0:02:07
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: Sending on Socket/fallback
    aug 22 13:48:09 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
    aug 22 13:48:14 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 5
    aug 22 13:48:19 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
    aug 22 13:48:26 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
    aug 22 13:48:33 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 7
    aug 22 13:48:36 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: signal quality updated (40)
    aug 22 13:48:40 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 10
    aug 22 13:48:50 AsusN56VZ dhclient[2351]: DHCPDISCOVER on wwp0s20u2i7 to 255.255.255.255 port 67 interval 17
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> (wwp0s20u2i7): DHCPv4 request timed out.
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (wwp0s20u2i7): canceled DHCP transaction, DHCP client pid 2351
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) started...
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <warn> Activation (ttyUSB3) failed for connection 'Orange PL'
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> Activation (ttyUSB3) Stage 4 of 5 (IPv4 Configure Timeout) complete.
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): device state change: failed -> disconnected (reason 'none') [120 30 0]
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3): deactivating device (reason 'none') [0]
    aug 22 13:48:54 AsusN56VZ ModemManager[314]: <info> Modem /org/freedesktop/ModemManager1/Modem/1: state changed (connected -> disconnecting)
    aug 22 13:48:54 AsusN56VZ NetworkManager[315]: <info> (ttyUSB3) modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
    Last edited by Shocker (2013-09-14 20:08:08)

    Shocker wrote:I don't think it's kernel problem, because Linux Mint 15 have kernel 3.8 and there is everything fine. Maybe systemd (Fedora & Arch have systemd, but Mint sysvinit..), maybe version of dhcpcd, I have no idea...
    To test, I downgraded my kernel
    ~ ᐅ uname -r
    3.9.5-301.fc19.x86_64.debug
    And now I see in messages
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) starting connection 'Telstra'
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) scheduled...
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) started...
    Sep 15 09:46:17 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 1 of 5 (Device Prepare) complete.
    Sep 15 09:46:17 localhost modem-manager[757]: <info> (ttyUSB2) opening serial port...
    Sep 15 09:46:17 localhost modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
    Sep 15 09:46:17 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
    Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2) opening serial port...
    Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <warn> (ttyUSB2): port attributes not fully set
    Sep 15 09:46:17 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled -> enabling)
    Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
    Sep 15 09:46:18 localhost modem-manager[757]: <info> (ttyUSB2): using PDU mode for SMS
    Sep 15 09:46:18 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
    Sep 15 09:46:18 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling -> enabled)
    Sep 15 09:46:18 localhost NetworkManager[724]: <info> WWAN now enabled by management service
    Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
    Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabled -> registered)
    Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
    Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
    Sep 15 09:46:19 localhost dbus-daemon[618]: modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
    Sep 15 09:46:19 localhost modem-manager[757]: <info> Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> connected)
    Sep 15 09:46:19 localhost kernel: [ 5056.773068] IPv6: ADDRCONF(NETDEV_UP): wwp0s29u1u1i7: link is not ready
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) scheduled...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) starting...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: prepare -> config (reason 'none') [40 50 0]
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): bringing up device.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) successful.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 2 of 5 (Device Configure) complete.
    Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for fe80::c0c3:a2ff:fe4a:207 on wwp0s29u1u1i7.*.
    Sep 15 09:46:19 localhost kernel: [ 5056.876750] IPv6: ADDRCONF(NETDEV_CHANGE): wwp0s29u1u1i7: link becomes ready
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) scheduled.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) started...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: config -> ip-config (reason 'none') [50 70 0]
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> dhclient started with pid 10376
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 3 of 5 (IP Configure Start) complete.
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Sep 15 09:46:19 localhost dhclient[10376]: Internet Systems Consortium DHCP Client 4.2.5
    Sep 15 09:46:19 localhost dhclient[10376]: Copyright 2004-2013 Internet Systems Consortium.
    Sep 15 09:46:19 localhost dhclient[10376]: All rights reserved.
    Sep 15 09:46:19 localhost dhclient[10376]: For info, please visit https://www.isc.org/software/dhcp/
    Sep 15 09:46:19 localhost dhclient[10376]:
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed nbi -> preinit
    Sep 15 09:46:19 localhost dhclient[10376]: Listening on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
    Sep 15 09:46:19 localhost dhclient[10376]: Sending on LPF/wwp0s29u1u1i7/c2:c3:a2:4a:02:07
    Sep 15 09:46:19 localhost dhclient[10376]: Sending on Socket/fallback
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0x6e8c90b2)
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPNAK from 10.102.67.253 (xid=0x6e8c90b2)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> expire
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPDISCOVER on wwp0s29u1u1i7 to 255.255.255.255 port 67 interval 6 (xid=0xae2cec8)
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPREQUEST on wwp0s29u1u1i7 to 255.255.255.255 port 67 (xid=0xae2cec8)
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPOFFER from 10.102.67.253
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed expire -> preinit
    Sep 15 09:46:19 localhost dhclient[10376]: DHCPACK from 10.102.67.253 (xid=0xae2cec8)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): DHCPv4 state changed preinit -> bound
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> address 10.102.67.12
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> prefix 24 (255.255.255.0)
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> gateway 10.102.67.12
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.81.103'
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> nameserver '10.4.182.20'
    Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
    Sep 15 09:46:19 localhost NetworkManager[724]: nm_ip4_config_add_wins: assertion `wins > 0' failed
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> wins '0.0.0.0'
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    Sep 15 09:46:19 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) started...
    Sep 15 09:46:19 localhost avahi-daemon[607]: Joining mDNS multicast group on interface wwp0s29u1u1i7.IPv4 with address 10.102.67.12.
    Sep 15 09:46:19 localhost avahi-daemon[607]: New relevant interface wwp0s29u1u1i7.IPv4 for mDNS.
    Sep 15 09:46:19 localhost avahi-daemon[607]: Registering new address record for 10.102.67.12 on wwp0s29u1u1i7.IPv4.
    Sep 15 09:46:19 localhost dhclient[10376]: bound to 10.102.67.12 -- renewal in 97473 seconds.
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) Stage 5 of 5 (IPv4 Commit) complete.
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> (wwp0s29u1u1i7): device state change: secondaries -> activated (reason 'none') [90 100 0]
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> Policy set 'Telstra' (wwp0s29u1u1i7) as default for IPv4 routing and DNS.
    Sep 15 09:46:20 localhost NetworkManager[724]: <info> Activation (wwp0s29u1u1i7) successful, device activated.
    I'm going to ask on #fedora and see how i can best diagnose what's going on. At least I now have it working, albeit on an older kernel.
    Last edited by qnm (2013-09-14 23:48:05)

  • [SOLVED] Network Manager not working after disabling GDM daemon

    Morning All,
      1st post so go easy on me.
    I have recently setup Arch on a Samsung Q320 notebook, using GNOME DE and enabling gdm. Everything is working fine installed network manager no probs it connects to wireless network each time I login, really impressed with the distro. However I have been playing around with it a bit and when a disable the 'gdm' daemon by prefixing it with '!' in /etc/rc.conf, then reboot then login in with username & pw,  and 'startx'  GNOME DE starts fine however network manager fails to start, it is still located in the preferences menu I can open it and see the networks I have created previously however cannot join any of them. Can shed any light on the situation.
    Cheers
    Chris
    Last edited by phatrat (2010-03-12 21:24:49)

    just add in ~/.xinitrc
    exec ck-launch-session gnome-session

  • Network Manager doesnt detect tty/ACM0 for Broadband Network

    Hi all,
    I have just installed Arch Linux and slowly getting acquainted to it. I have a mobile broadband connection via GPRS. Previously I was using Zenwalk OS and the Network Manager used to detect my device as soon as it was connected (provided the kernel module cdc_acm was enabled and 'dialout' group was added for that user).
    I tried the same in Arch linux, but the Network manager though has options for connecting to Mobile Broadband, doesn't detect my device.
    Somehow, I am using the Mobile broadband by using wvdial (had to do trial and error to fix it), but I am interested to know, why the Network Manager failed and hence think about fixing the issue.
    Can anyone please guide me regarding this issue and help me out to sort the problem ?
    Thanks in advance
    With regards,
    Ajay Kumar G

    Welcome to the Arch forums!
    Your post does a good job providing a very basic idea of what is going on, but unfortunately not much more than that.  More information is required in order to properly diagnose this issue.  You should check if there are error messages in the journal, or any other indications as to why things might be failing.  Your computer typically makes an attempt at telling you what is going wrong.
    From what you have posted though, it kind of sounds like you are trying to use two network management services at the same time.  If you use wifi-menu, you are essentially using the ncurses front end to netctl.  Netctl is basically just a collection of scripts that wrap the most basic networking tools.  If this is in use, then networkmanager is bound to fail as you then have two services competing (and likely failing) to control that hardware.
    Check to see if you have more than one service trying to handle things.  You can run systemctl with no arguments to see everything that systemd wants to start.  Though if you use systemctl --type=service then you can have it tell you only about services (as opposed to all unit types, like mount, automount, device, socket files and more).

  • Windows 8.1 not booting : "Boot manager failed to find OS loader"

    Hello all,
    I know this question came up before, but I have being trying to fix this for many days now, without luck and I feel I need some new ideas...
    The short story:
    My Windows 8.1 is not booting, and gets trapped in cycle of Boot Manager until I tell the UEFI to boot from disk or USB
    I can boot up from external CD or USB Windows RE, from which I can get to prompt line
    In the log file in C:\Windows\System 32\LogFiles\Srt\SrtTrail.txt I read: 
    Boot manager failed to find OS loader
    Repair Action File Repair à Failed (err code 0x4001)
    Repair Action Boot Config Data Store Repair à Failed (err code 0x2)
       4. My disk is GPT partitioned, with UEFI Bios
       5. I tried the typical Bootrec commands: FixMbr, FixBoot, ScanOs, RebuildBCD but I always get the error:
    Identified Windows install:0
        6. I tried Bcdedit but I get:
    the boot configuration data (BCD) store could not be opened
        7. I tried to create a new BCD store in the FAT32 partition (temporarily named "v:\") with  
    bcdboot c:\Windows  /l en-gb  /s  v: /f ALL
    but I get:
    Failure when attempted to copy boot files
        8. Finally, I noticed that in
      C:\Windows\System32\
    I DO NOT have the file  winload.efi
    while in: ESP\EFI\Microsoft\Boot\
    I DO have the file   Bootmgfw.efi
       One question I have is: Is it possible to copy a "healthy" winload.efi from somewhere in my PC into C:\Windows\System32\ ?
    Where (which path) could I find it?
    Any other ideas? Please help !!!!
    Many thanks!! This is literarily driving me crazy because I really don't want to reinstall windows....

    Hello Kermit_70,
    What is your current situation?
    Please try the suggestion as aw00t mentioned.
    Additionally, please try to use Automatic Repair to fix problems that keep Windows from loading.
    For more information, please take a look at the following article.
    http://www.eightforums.com/tutorials/2269-system-recovery-options-boot-windows-8-a.html
    Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Best regards,
    Fangzhou CHEN
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • [SOLVED] Network Manager systemd unit fails after update

    EDIT: Reinstalling libnm-glib resolved this issue
    After updating to the latest version of NetworkManager (networkmanager-0.9.8.10-3), the systemd unit fails to start. It works fine after downgrading back to the previous version though (networkmanager-0.9.8.10-1). I'm not sure if this is a bug or an error on my end; since the previous package works I've just dowgraded for the time being.  For the update that doesn't work, here is the output of "systemctl status" and the systemd journal:
    >>sudo systemctl daemon-reload
    >> sudo systemctl status NetworkManager
    ● NetworkManager.service - Network Manager
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
    Active: failed (Result: exit-code) since Wed 2014-06-11 15:28:25 EDT; 10s ago
    Process: 24073 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=127)
    Main PID: 24073 (code=exited, status=127)
    Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
    Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
    Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
    >> journalctl -xn
    -- Logs begin at Tue 2014-06-10 12:47:19 EDT, end at Wed 2014-06-11 15:28:36 EDT. --
    Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
    Jun 11 15:28:25 kyle systemd[1]: Starting Network Manager...
    -- Subject: Unit NetworkManager.service has begun with start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit NetworkManager.service has begun starting up.
    Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
    Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
    -- Subject: Unit NetworkManager.service has failed
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit NetworkManager.service has failed.
    -- The result is failed.
    Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
    Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session closed for user root
    Jun 11 15:28:28 kyle dbus[489]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
    Jun 11 15:28:36 kyle sudo[24075]: kyle : TTY=pts/2 ; PWD=/var/cache/pacman/pkg ; USER=root ; COMMAND=/usr/bin/systemctl status NetworkManager
    Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
    Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session closed for user root
    Last edited by T0k3n (2014-07-03 15:18:01)

    Check the changes:
    https://projects.archlinux.org/svntogit … e192881dc5
    https://projects.archlinux.org/svntogit … ee906b6c44
    When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
    like this
    It makes the code more readable and - in case of longer listings - more convenient to scroll through.

  • "Boot Manager failed to find OS loader" - Windows XP

    Hello, I'm new in this community.
    That being said, I have a problem with my Thinkpad SL410. Two nights ago I shut down my laptop. It was working fine at that point. I clicked on shut down, but I think it went to "update and shut down". BAD idea, since now, its stuck on a loop.
    When I try and boot up the laptop, it only brings me to R&R4. Then, after it scans and tries to "fix" the problem, it gives me a message. Unfortunately, the message is in chinese since I bought this laptop in china, so with my rough translation skills, I was able to determine that "Boot Manager failed to find OS loader".
    You would think that that would be easy to fix. I go grab a windows recovery ISO, and put it onto my bootable USB. Problem is, R&R is almost getting in the way of recovery console. When I boot from the usb, there is a black screen with the message "To boot rescue and recovery environment, press f11". I have tried to press f11 and I have tried to wait, but no matter what, it takes me to the thinkvantage rescue and recovery, as opposed to the windows console.
    Essentially, I cannot access the console to type in:
    -fixboot
    -fixmbr
    I have painstakingly translated much of the R&R page (The one that gives you 3 options; restore, backup, reset to factory settings). I don't think there is a way to get to recovery console via that rescue and recovery page. So I do what is most logical. I try and restore to a backup. Technology doesn't seem to like me because after waiting for 30 mins, its at 93% done and there is a message saying something along the lines of "C: doesnt have enough space".
    Great. What other options do I have? I know the hard drive isn't corrupted and my files are still there, since going into "backup" shows me all the files (pictures, documents, etc...). I can't back them all up and factory reset since not only would it take forever, but it would take up wayy too many gigs of space, and I simply can't get my hands on a massive storage system atm.
    This is very frustrating since I only started using this computer after my dell laptop had a hard drive failure. It's a pain trying to get through dell support, only to have my situation a whole lot  more complicated since it was a gift from china, and already registered to someone. Then a perfectly good working computer fails on me again, and this time I can't analyze the problem correctly since the computer is in chinese.
    TL;DR 
    "Boot manager failed to find OS loader error. When I try booting from Windows XP ISO, R&R gets in the way. I also can't do a restore to backup since my C drive apparently doesn't have enough space.

    Hi dizscez, welcome to the forums,
    I can't promise, but something which has worked for me in similar situations is explained in the following KB article. Basically you would be doing the same as running a system restore to a previous point under Windows
    http://forums.lenovo.com/t5/Windows-XP-and-Vista-discussion/XP-System-Restore-When-Normal-And-Safe-M...
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • [SOLVED]Network Manager Applet and nmcli failing after GCC upgrade

    Hi All,
    So I went to update my system today and there were only like 8 or 9 updates. Like many other people I had an issue with gcc and pacman. To fix this I ran
    pacman -S gcc
    Then I ran:
    pacman -Su
    which updated pacman itself. On reboot though I noticed network manager applet was unable to find any of my network devices despite the fact that network manager was running and I had an IP address. I killed nm-applet and re-ran it and it spewed errors about not being able to connect to network manager. I tried running nmcli and it did the same thing. However, when I run nmcli as root it works. Looking at the arch wiki they suggest you be a part of the wheel and network group which I made sure I was. Everything was working up until I ran those two updates though. Anyone else have this happen or have any idea what is wrong?
    Thanks,
    Hemmar
    EDIT: Never mind - a patch was released for consolekit which fixes the problem.
    Last edited by hemmar (2012-04-13 00:36:49)

    Hi guz46
    I have already tried removing the ! and the same thing happened ... but I realised today that I was being automatically connected to "Auto eth0" despite there being no cable present. When automatic connection was disabled on "Auto eth0" my 3G connection (ppp0) connected fine.
    Could you clarify that the preferred set-up in the /etc/rc.conf for the interfaces is without the !. The Wiki for networkmanager says to disable them, but then states that some may need to be reenabled with no explanation. The purpose of this confuses me!
    Thanks for you help anyways,
    Scott
    EDIT:
    I appear to have fixed my problem with the auto connection on the various interfaces by updating my /etc/rc.conf file to:
    #Static IP example
    #eth0="dhcp"
    ppp0="dhcp"
    wlan0="dhcp"
    eth0="dhcp"
    INTERFACES=(ppp0 wlan0 eth0)
    Thus ensuring that I can connect in order of preference.
    Last edited by ScottArch (2009-11-03 18:48:47)

  • If zfs manages /etc in a separate ZFS filesystem it fails to boot

    In my most recent installation I wanted to keep /ect in a separed ZFS filesystem to keep it with a higher compression.
    But Arch fails to boot, it seems dbus needs the /etc directory mounted before the zfs daemon actually mounts it.
    Do anyone had this problem? It is possible to mount the partitions before?
    Thanks
    Last edited by ezzetabi (2013-02-17 15:29:23)

    It happened to me ...
    And he does not serve doing a RESET to her BIOS, you must take out the battery for some ten minutes, in my case, I tried with half hour and it worked.
    Try with that and you tell us.

  • Dhcpcd-based network fails during boot

    Hi,
    My fully updated Arch_X86-64/KDE is connected to the Internet router via (on-board wired) eth1, and is configured to get an auto IP address.
    This has worked flawlessly for years till two days ago.
    Ever since,  eth1 service fails during boot, and requires several manual dhcpcd command to finally kick in. The same applies after waking from sleep mode. (see terminal output below)
    As can be seen the system is configured to load the (correct) r8169 mode.
    Please advise.
    Thanks
    Miki Badt
    ---------copy of respective commands---------------
    # journalctl -b | grep eth
    Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth1.device...
    Sep 15 15:50:17 Miki_Arch systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
    Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: RTL8168d/8111d at 0xffffc900119d2000, 6c:f0:49:ed:b3:e9, XID 083000c0 IRQ 49
    Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:05:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
    Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: RTL8168d/8111d at 0xffffc900119e6000, 6c:f0:49:ed:b3:eb, XID 083000c0 IRQ 50
    Sep 15 15:50:17 Miki_Arch kernel: r8169 0000:06:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
    Sep 15 15:50:23 Miki_Arch dhcpcd[339]: eth1: waiting for carrier
    Sep 15 15:50:23 Miki_Arch dhcpcd[336]: eth0: waiting for carrier
    Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
    Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:06:00.0 eth1: link down
    Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    Sep 15 15:50:29 Miki_Arch kernel: r8169 0000:05:00.0 eth0: link down
    Sep 15 15:50:29 Miki_Arch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    Sep 15 15:50:53 Miki_Arch systemd[1]: [email protected]: control process exited, code=exited status=1
    Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth0.
    Sep 15 15:50:53 Miki_Arch systemd[1]: Unit [email protected] entered failed state.
    Sep 15 15:50:53 Miki_Arch systemd[1]: [email protected]: control process exited, code=exited status=1
    Sep 15 15:50:53 Miki_Arch systemd[1]: Failed to start dhcpcd on eth1.
    Sep 15 15:50:53 Miki_Arch systemd[1]: Unit [email protected] entered failed state.
    #manual commands
    [root@Miki_Arch miki]# dhcpcd eth1
    dhcpcd[1039]: version 6.0.5 starting
    dhcpcd[1039]: eth1: waiting for carrier
    dhcpcd[1039]: timed out
    dhcpcd[1039]: exited
    [root@Miki_Arch miki]# ping www.ynet.co.il
    ping: unknown host www.ynet.co.il
    [root@Miki_Arch miki]# dhcpcd eth1
    dhcpcd[1046]: version 6.0.5 starting
    dhcpcd[1046]: eth1: soliciting an IPv6 router
    dhcpcd[1046]: eth1: rebinding lease of 192.168.1.13
    dhcpcd[1046]: eth1: leased 192.168.1.13 for 3600 seconds
    dhcpcd[1046]: eth1: adding host route to 192.168.1.13 via 127.0.0.1
    dhcpcd[1046]: eth1: adding route to 192.168.1.0/24
    dhcpcd[1046]: eth1: adding default route via 192.168.1.1
    lspci -v | grep Ethernet
    05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
    06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
    lspci -k
    05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
    Subsystem: Gigabyte Technology Co., Ltd Motherboard
    Kernel driver in use: r8169
    Kernel modules: r8169
    06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
    Subsystem: Gigabyte Technology Co., Ltd Motherboard
    Kernel driver in use: r8169
    Kernel modules: r8169
    cat /etc/modules-load.d/realtek.conf
    r8169
    Last edited by mibadt (2013-09-15 13:29:25)

    Hi,
    I've some errors with the new dhcpcd, you should downgrade.
    https://wiki.archlinux.org/index.php/Do … g_Packages

  • Grub-BIOS UUID-base Arch/LXDE fails to boot completly 2/3 of times

    Hi,
    I have a GRUB-BIOS systemd based Arch/LXDE fresh installation (latest 2/2013 image).
    About 2 out of 3 times I boot the system freezes after  displaying that the  /dev/sda2 (my root) is clean.
    Yet, about 1 out of 3 trials, boot completes without problems.
    In either case I don't add any parameters, and just wait for Grub's timeout.
    The same happen with the Linux fallback as well.
    This is a single drive (sda) netbook installation.
    From the journalctl (see below) it seems to me that the alleged stuck boot almost completed!
    I'd appreciate any help!
    Below please find:
    1. Output of journalctl relating to the last two boots: the 17:33 boot got stuck, whereas I'm writing now after successfully rebooting at 17:36
    2. Copy of my fstab
    3. Copy of grub.cfg
    Thanks a lot!
    ----------copy of journalctl of last 2 boots (sorry, it's long)--------------------
    -- Logs begin at Sat 2013-02-16 11:47:04 IST, end at Sat 2013-02-23 17:36:36 IST. --
    [1;39m-- Reboot --[0m
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Allowing runtime journal files to grow to 100.3M.
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpuset
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpu
    Feb 23 17:33:34 miki_netbook kernel: Linux version 3.7.9-1-ARCH (nobody@foutrelis) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Feb 18 02:27:20 EET 2013
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: e820: BIOS-provided physical RAM map:
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007f375fff] usable
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f376000-0x000000007f3befff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f3bf000-0x000000007f46cfff] ACPI data
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f46d000-0x000000007f4befff] ACPI NVS
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f4bf000-0x000000007f4fffff] ACPI data
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x000000007f500000-0x000000007fffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Feb 23 17:33:34 miki_netbook kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
    Feb 23 17:33:34 miki_netbook kernel: Notice: NX (Execute Disable) protection missing in CPU!
    Feb 23 17:33:34 miki_netbook kernel: SMBIOS 2.4 present.
    Feb 23 17:33:34 miki_netbook kernel: DMI: Quanta UW1/Base Board Product Name, BIOS Q3A51 2/05/2009
    Feb 23 17:33:34 miki_netbook kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Feb 23 17:33:34 miki_netbook kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Feb 23 17:33:34 miki_netbook kernel: e820: last_pfn = 0x7f376 max_arch_pfn = 0x100000
    Feb 23 17:33:34 miki_netbook kernel: MTRR default type: uncachable
    Feb 23 17:33:34 miki_netbook kernel: MTRR fixed ranges enabled:
    Feb 23 17:33:34 miki_netbook kernel: 00000-9FFFF write-back
    Feb 23 17:33:34 miki_netbook kernel: A0000-BFFFF uncachable
    Feb 23 17:33:34 miki_netbook kernel: C0000-C7FFF write-protect
    Feb 23 17:33:34 miki_netbook kernel: C8000-EFFFF uncachable
    Feb 23 17:33:34 miki_netbook kernel: F0000-FFFFF write-protect
    Feb 23 17:33:34 miki_netbook kernel: MTRR variable ranges enabled:
    Feb 23 17:33:34 miki_netbook kernel: 0 base 0FFFE0000 mask 0FFFE0000 write-protect
    Feb 23 17:33:34 miki_netbook kernel: 1 base 0FFFC0000 mask 0FFFE0000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 2 base 000000000 mask 0C0000000 write-back
    Feb 23 17:33:34 miki_netbook kernel: 3 base 040000000 mask 0C0000000 write-back
    Feb 23 17:33:34 miki_netbook kernel: 4 base 07F800000 mask 0FF800000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 5 base 07F600000 mask 0FFE00000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 6 base 07F500000 mask 0FFF00000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: 7 base 000000000 mask 0FFFE0000 uncachable
    Feb 23 17:33:34 miki_netbook kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Feb 23 17:33:34 miki_netbook kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]
    Feb 23 17:33:34 miki_netbook kernel: Base memory trampoline at [c009b000] 9b000 size 16384
    Feb 23 17:33:34 miki_netbook kernel: init_memory_mapping: [mem 0x00000000-0x377fdfff]
    Feb 23 17:33:34 miki_netbook kernel: [mem 0x00000000-0x377fdfff] page 4k
    Feb 23 17:33:34 miki_netbook kernel: kernel direct mapping tables up to 0x377fdfff @ [mem 0x01b1f000-0x01bfffff]
    Feb 23 17:33:34 miki_netbook kernel: RAMDISK: [mem 0x37a72000-0x37d30fff]
    Feb 23 17:33:34 miki_netbook kernel: Allocated new RAMDISK: [mem 0x3753f000-0x377fd99b]
    Feb 23 17:33:34 miki_netbook kernel: Move RAMDISK from [mem 0x37a72000-0x37d3099b] to [mem 0x3753f000-0x377fd99b]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: RSDP 000fe020 00024 (v02 haier)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: XSDT 7f4fe120 00064 (v01 haier computer 00000001 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: FACP 7f4fc000 000F4 (v04 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: DSDT 7f4f3000 04DDE (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: FACS 7f488000 00040
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f4fd000 004C4 (v02 PmRef CpuPm 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: HPET 7f4fb000 00038 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: APIC 7f4fa000 00068 (v02 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: MCFG 7f4f9000 0003C (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: ASF! 7f4f8000 000A5 (v32 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SLIC 7f4f2000 00180 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: BOOT 7f4f1000 00028 (v01 haier computer 00000001 MSFT 01000013)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Local APIC address 0xfee00000
    Feb 23 17:33:34 miki_netbook kernel: 1147MB HIGHMEM available.
    Feb 23 17:33:34 miki_netbook kernel: 887MB LOWMEM available.
    Feb 23 17:33:34 miki_netbook kernel: mapped low ram: 0 - 377fe000
    Feb 23 17:33:34 miki_netbook kernel: low ram: 0 - 377fe000
    Feb 23 17:33:34 miki_netbook kernel: Zone ranges:
    Feb 23 17:33:34 miki_netbook kernel: DMA [mem 0x00010000-0x00ffffff]
    Feb 23 17:33:34 miki_netbook kernel: Normal [mem 0x01000000-0x377fdfff]
    Feb 23 17:33:34 miki_netbook kernel: HighMem [mem 0x377fe000-0x7f375fff]
    Feb 23 17:33:34 miki_netbook kernel: Movable zone start for each node
    Feb 23 17:33:34 miki_netbook kernel: Early memory node ranges
    Feb 23 17:33:34 miki_netbook kernel: node 0: [mem 0x00010000-0x0009efff]
    Feb 23 17:33:34 miki_netbook kernel: node 0: [mem 0x00100000-0x7f375fff]
    Feb 23 17:33:34 miki_netbook kernel: On node 0 totalpages: 520965
    Feb 23 17:33:34 miki_netbook kernel: free_area_init_node: node 0, pgdat c158d880, node_mem_map f6556200
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 32 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 0 pages reserved
    Feb 23 17:33:34 miki_netbook kernel: DMA zone: 3951 pages, LIFO batch:0
    Feb 23 17:33:34 miki_netbook kernel: Normal zone: 1744 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: Normal zone: 221486 pages, LIFO batch:31
    Feb 23 17:33:34 miki_netbook kernel: HighMem zone: 2295 pages used for memmap
    Feb 23 17:33:34 miki_netbook kernel: HighMem zone: 291457 pages, LIFO batch:31
    Feb 23 17:33:34 miki_netbook kernel: Using APIC driver default
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PM-Timer IO Port: 0x408
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Local APIC address 0xfee00000
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    Feb 23 17:33:34 miki_netbook kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    Feb 23 17:33:34 miki_netbook kernel: IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
    Feb 23 17:33:34 miki_netbook kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ0 used by override.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ2 used by override.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: IRQ9 used by override.
    Feb 23 17:33:34 miki_netbook kernel: Using ACPI (MADT) for SMP configuration information
    Feb 23 17:33:34 miki_netbook kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Allowing 2 CPUs, 0 hotplug CPUs
    Feb 23 17:33:34 miki_netbook kernel: nr_irqs_gsi: 40
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    Feb 23 17:33:34 miki_netbook kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    Feb 23 17:33:34 miki_netbook kernel: e820: [mem 0x80000000-0xdfffffff] available for PCI devices
    Feb 23 17:33:34 miki_netbook kernel: Booting paravirtualized kernel on bare hardware
    Feb 23 17:33:34 miki_netbook kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
    Feb 23 17:33:34 miki_netbook kernel: PERCPU: Embedded 13 pages/cpu @f6530000 s32448 r0 d20800 u53248
    Feb 23 17:33:34 miki_netbook kernel: pcpu-alloc: s32448 r0 d20800 u53248 alloc=13*4096
    Feb 23 17:33:34 miki_netbook kernel: pcpu-alloc: [0] 0 [0] 1
    Feb 23 17:33:34 miki_netbook kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 516894
    Feb 23 17:33:34 miki_netbook kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677 ro quiet
    Feb 23 17:33:34 miki_netbook kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Feb 23 17:33:34 miki_netbook kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Feb 23 17:33:34 miki_netbook kernel: __ex_table already sorted, skipping sort
    Feb 23 17:33:34 miki_netbook kernel: Initializing CPU#0
    Feb 23 17:33:34 miki_netbook kernel: allocated 4168496 bytes of page_cgroup
    Feb 23 17:33:34 miki_netbook kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Feb 23 17:33:34 miki_netbook kernel: Initializing HighMem for node 0 (000377fe:0007f376)
    Feb 23 17:33:34 miki_netbook kernel: Memory: 2051608k/2084312k available (4099k kernel code, 32252k reserved, 1644k data, 556k init, 1175008k highmem)
    Feb 23 17:33:34 miki_netbook kernel: [379B blob data]
    Feb 23 17:33:34 miki_netbook kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
    Feb 23 17:33:34 miki_netbook kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Feb 23 17:33:34 miki_netbook kernel: Preemptible hierarchical RCU implementation.
    Feb 23 17:33:34 miki_netbook kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Feb 23 17:33:34 miki_netbook kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Feb 23 17:33:34 miki_netbook kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
    Feb 23 17:33:34 miki_netbook kernel: NR_IRQS:2304 nr_irqs:512 16
    Feb 23 17:33:34 miki_netbook kernel: CPU 0 irqstacks, hard=f5c08000 soft=f5c0a000
    Feb 23 17:33:34 miki_netbook kernel: Console: colour dummy device 80x25
    Feb 23 17:33:34 miki_netbook kernel: console [tty0] enabled
    Feb 23 17:33:34 miki_netbook kernel: hpet clockevent registered
    Feb 23 17:33:34 miki_netbook kernel: tsc: Fast TSC calibration failed
    Feb 23 17:33:34 miki_netbook kernel: tsc: PIT calibration matches HPET. 1 loops
    Feb 23 17:33:34 miki_netbook kernel: tsc: Detected 1595.989 MHz processor
    Feb 23 17:33:34 miki_netbook kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3193.97 BogoMIPS (lpj=5319963)
    Feb 23 17:33:34 miki_netbook kernel: pid_max: default: 32768 minimum: 301
    Feb 23 17:33:34 miki_netbook kernel: Security Framework initialized
    Feb 23 17:33:34 miki_netbook kernel: AppArmor: AppArmor disabled by boot time parameter
    Feb 23 17:33:34 miki_netbook kernel: Mount-cache hash table entries: 512
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys cpuacct
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys memory
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys devices
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys freezer
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys net_cls
    Feb 23 17:33:34 miki_netbook kernel: Initializing cgroup subsys blkio
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: CPU: Physical Processor ID: 0
    Feb 23 17:33:34 miki_netbook kernel: CPU: Processor Core ID: 0
    Feb 23 17:33:34 miki_netbook kernel: mce: CPU supports 5 MCE banks
    Feb 23 17:33:34 miki_netbook kernel: CPU0: Thermal monitoring enabled (TM2)
    Feb 23 17:33:34 miki_netbook kernel: process: using mwait in idle threads
    Feb 23 17:33:34 miki_netbook kernel: [113B blob data]
    Feb 23 17:33:34 miki_netbook kernel: Freeing SMP alternatives: 16k freed
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Core revision 20120913
    Feb 23 17:33:34 miki_netbook kernel: ftrace: allocating 17730 entries in 35 pages
    Feb 23 17:33:34 miki_netbook kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
    Feb 23 17:33:34 miki_netbook kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Feb 23 17:33:34 miki_netbook kernel: smpboot: CPU0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (fam: 06, model: 1c, stepping: 02)
    Feb 23 17:33:34 miki_netbook kernel: Performance Events: PEBS fmt0+, LBR disabled due to erratumAtom events, Intel PMU driver.
    Feb 23 17:33:34 miki_netbook kernel: ... version: 3
    Feb 23 17:33:34 miki_netbook kernel: ... bit width: 40
    Feb 23 17:33:34 miki_netbook kernel: ... generic registers: 2
    Feb 23 17:33:34 miki_netbook kernel: ... value mask: 000000ffffffffff
    Feb 23 17:33:34 miki_netbook kernel: ... max period: 000000007fffffff
    Feb 23 17:33:34 miki_netbook kernel: ... fixed-purpose events: 3
    Feb 23 17:33:34 miki_netbook kernel: ... event mask: 0000000700000003
    Feb 23 17:33:34 miki_netbook kernel: CPU 1 irqstacks, hard=f5cc0000 soft=f5cc2000
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Booting Node 0, Processors #1 OK
    Feb 23 17:33:34 miki_netbook kernel: Initializing CPU#1
    Feb 23 17:33:34 miki_netbook kernel: Atom PSE erratum detected, BIOS microcode update recommended
    Feb 23 17:33:34 miki_netbook kernel: Disabled fast string operations
    Feb 23 17:33:34 miki_netbook kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Feb 23 17:33:34 miki_netbook kernel: Brought up 2 CPUs
    Feb 23 17:33:34 miki_netbook kernel: smpboot: Total of 2 processors activated (6386.95 BogoMIPS)
    Feb 23 17:33:34 miki_netbook kernel: devtmpfs: initialized
    Feb 23 17:33:34 miki_netbook kernel: PM: Registering ACPI NVS region [mem 0x7f46d000-0x7f4befff] (335872 bytes)
    Feb 23 17:33:34 miki_netbook kernel: RTC time: 15:33:30, date: 02/23/13
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 16
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type pci registered
    Feb 23 17:33:34 miki_netbook kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    Feb 23 17:33:34 miki_netbook kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using MMCONFIG for extended config space
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using configuration type 1 for base access
    Feb 23 17:33:34 miki_netbook kernel: bio: create slab <bio-0> at 0
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Module Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Processor Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: EC: Look up EC in DSDT
    Feb 23 17:33:34 miki_netbook kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f380c90 00239 (v02 PmRef Cpu0Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 00239 (v02 PmRef Cpu0Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f37fe10 001C7 (v02 PmRef Cpu0Cst 00003001 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 001C7 (v02 PmRef Cpu0Cst 00003001 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f380f10 000D0 (v02 PmRef Cpu1Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 000D0 (v02 PmRef Cpu1Ist 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT 7f37ef10 00083 (v02 PmRef Cpu1Cst 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Dynamic OEM Table Load:
    Feb 23 17:33:34 miki_netbook kernel: ACPI: SSDT (null) 00083 (v02 PmRef Cpu1Cst 00003000 INTL 20051117)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Interpreter enabled
    Feb 23 17:33:34 miki_netbook kernel: ACPI: (supports S0 S3 S4 S5)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Using IOAPIC for interrupt routing
    Feb 23 17:33:34 miki_netbook kernel: ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
    Feb 23 17:33:34 miki_netbook kernel: ACPI: No dock devices found.
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20120913/dsfield-211)
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f5c26dc8), AE_ALREADY_EXISTS (20120913/psparse-536)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Feb 23 17:33:34 miki_netbook kernel: PCI host bridge to bus 0000:00
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: root bus resource [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:00.0: [8086:27ac] type 00 class 0x060000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: [8086:27ae] type 00 class 0x030000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 10: [mem 0x94280000-0x942fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 14: [io 0x40c0-0x40c7]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 18: [mem 0x80000000-0x8fffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: reg 1c: [mem 0x94300000-0x9433ffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.1: [8086:27a6] type 00 class 0x038000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.1: reg 10: [mem 0x94200000-0x9427ffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: reg 10: [mem 0x94340000-0x94343fff 64bit]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.0: reg 20: [io 0x4080-0x409f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.1: reg 20: [io 0x4060-0x407f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.2: reg 20: [io 0x4040-0x405f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.3: reg 20: [io 0x4020-0x403f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: reg 10: [mem 0x94344400-0x943447ff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.0: [8086:27b9] type 00 class 0x060100
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0068 (mask 0007)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: [8086:27c4] type 00 class 0x010180
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 10: [io 0x0000-0x0007]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 14: [io 0x0000-0x0003]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 18: [io 0x0000-0x0007]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 1c: [io 0x0000-0x0003]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: reg 20: [io 0x40a0-0x40af]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1f.3: reg 20: [io 0x4000-0x401f]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: [10ec:8136] type 00 class 0x020000
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 10: [io 0x1000-0x10ff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 18: [mem 0x91010000-0x91010fff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 20: [mem 0x91000000-0x9100ffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: reg 30: [mem 0xffff0000-0xffffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: supports D1 D2
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: PCI bridge to [bus 03] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: bridge window [mem 0x80000000-0xfebfffff] (subtractive decode)
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: on NUMA node 0
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20120913/dsfield-211)
    Feb 23 17:33:34 miki_netbook kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f5c26dc8), AE_ALREADY_EXISTS (20120913/psparse-536)
    Feb 23 17:33:34 miki_netbook kernel: pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    Feb 23 17:33:34 miki_netbook kernel: pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: loaded
    Feb 23 17:33:34 miki_netbook kernel: vgaarb: bridge control possible 0000:00:02.0
    Feb 23 17:33:34 miki_netbook kernel: PCI: Using ACPI for IRQ routing
    Feb 23 17:33:34 miki_netbook kernel: PCI: pci_cache_line_size set to 64 bytes
    Feb 23 17:33:34 miki_netbook kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    Feb 23 17:33:34 miki_netbook kernel: e820: reserve RAM buffer [mem 0x7f376000-0x7fffffff]
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: Initializing
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: domain hash size = 128
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Feb 23 17:33:34 miki_netbook kernel: NetLabel: unlabeled traffic allowed by default
    Feb 23 17:33:34 miki_netbook kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Feb 23 17:33:34 miki_netbook kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Feb 23 17:33:34 miki_netbook kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Feb 23 17:33:34 miki_netbook kernel: Switching to clocksource hpet
    Feb 23 17:33:34 miki_netbook kernel: pnp: PnP ACPI init
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type pnp registered
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [bus 00-ff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0000-0x0cf7 window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0cf8-0x0cff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [io 0x0d00-0xffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c0000-0x000c3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c4000-0x000c7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000c8000-0x000cbfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000cc000-0x000cffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d0000-0x000d3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d4000-0x000d7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000d8000-0x000dbfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000dc000-0x000dffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e0000-0x000e3fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e4000-0x000e7fff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000e8000-0x000ebfff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000ec000-0x000effff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x000f0000-0x000fffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: [mem 0x80000000-0xfebfffff window]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x002e-0x002f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0068-0x006f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0200-0x020f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0061]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0070]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0080]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0092]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x00b2-0x00b3]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0063]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0065]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0067]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0600-0x060f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0610]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0800-0x080f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0400-0x047f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [io 0x0500-0x053f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xe0000000-0xefffffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed1c000-0xfed1ffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed14000-0xfed17fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed18000-0xfed18fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfed19000-0xfed19fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfec00000-0xfec00fff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:01: [mem 0xfee00000-0xfee00fff]
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0200-0x020f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0600-0x060f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0610] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0800-0x080f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0400-0x047f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [io 0x0500-0x053f] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed14000-0xfed17fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: [mem 0xfee00000-0xfee00fff] has been reserved
    Feb 23 17:33:34 miki_netbook kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0000-0x001f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0081-0x0091]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x0093-0x009f]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [io 0x00c0-0x00df]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: [dma 4]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:03: [io 0x0070-0x0077]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [irq 0 disabled]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [irq 8]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: [mem 0xfed00000-0xfed003ff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0103 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: [io 0x00f0]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: [irq 13]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:06: [mem 0xff800000-0xffffffff]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:06: Plug and Play ACPI device, IDs INT0800 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [io 0x0060]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [io 0x0064]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: [irq 1]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:08: [irq 12]
    Feb 23 17:33:34 miki_netbook kernel: pnp 00:08: Plug and Play ACPI device, IDs SYN102c SYN1000 SYN0002 PNP0f13 (active)
    Feb 23 17:33:34 miki_netbook kernel: pnp: PnP ACPI: found 9 devices
    Feb 23 17:33:34 miki_netbook kernel: ACPI: ACPI bus type pnp unregistered
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: no compatible bridge window for [mem 0xffff0000-0xffffffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.0: bridge window [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0x91020000-0x9102ffff pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1c.1: bridge window [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: PCI bridge to [bus 03]
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:1e.0: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:00: resource 7 [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 0 [io 0x3000-0x3fff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 1 [mem 0x93100000-0x941fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:01: resource 2 [mem 0x90000000-0x90ffffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x2fff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 1 [mem 0x92100000-0x930fffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:02: resource 2 [mem 0x91000000-0x920fffff 64bit pref]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 4 [io 0x0000-0x0cf7]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 5 [io 0x0d00-0xffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 6 [mem 0x000a0000-0x000bffff]
    Feb 23 17:33:34 miki_netbook kernel: pci_bus 0000:03: resource 7 [mem 0x80000000-0xfebfffff]
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 2
    Feb 23 17:33:34 miki_netbook kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    Feb 23 17:33:34 miki_netbook kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    Feb 23 17:33:34 miki_netbook kernel: TCP: Hash tables configured (established 131072 bind 65536)
    Feb 23 17:33:34 miki_netbook kernel: TCP: reno registered
    Feb 23 17:33:34 miki_netbook kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 1
    Feb 23 17:33:34 miki_netbook kernel: pci 0000:00:02.0: Boot video device
    Feb 23 17:33:34 miki_netbook kernel: PCI: CLS 0 bytes, default 64
    Feb 23 17:33:34 miki_netbook kernel: Unpacking initramfs...
    Feb 23 17:33:34 miki_netbook kernel: Freeing initrd memory: 2812k freed
    Feb 23 17:33:34 miki_netbook kernel: Simple Boot Flag value 0x5 read from CMOS RAM was invalid
    Feb 23 17:33:34 miki_netbook kernel: Simple Boot Flag at 0x44 set to 0x1
    Feb 23 17:33:34 miki_netbook kernel: apm: BIOS not found.
    Feb 23 17:33:34 miki_netbook kernel: audit: initializing netlink socket (disabled)
    Feb 23 17:33:34 miki_netbook kernel: type=2000 audit(1361633610.386:1): initialized
    Feb 23 17:33:34 miki_netbook kernel: bounce pool size: 64 pages
    Feb 23 17:33:34 miki_netbook kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
    Feb 23 17:33:34 miki_netbook kernel: VFS: Disk quotas dquot_6.5.2
    Feb 23 17:33:34 miki_netbook kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    Feb 23 17:33:34 miki_netbook kernel: msgmni has been set to 1717
    Feb 23 17:33:34 miki_netbook kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Feb 23 17:33:34 miki_netbook kernel: io scheduler noop registered
    Feb 23 17:33:34 miki_netbook kernel: io scheduler deadline registered
    Feb 23 17:33:34 miki_netbook kernel: io scheduler cfq registered (default)
    Feb 23 17:33:34 miki_netbook kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
    Feb 23 17:33:34 miki_netbook kernel: pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
    Feb 23 17:33:34 miki_netbook kernel: vesafb: mode is 640x480x32, linelength=2560, pages=0
    Feb 23 17:33:34 miki_netbook kernel: vesafb: scrolling: redraw
    Feb 23 17:33:34 miki_netbook kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Feb 23 17:33:34 miki_netbook kernel: vesafb: framebuffer at 0x80000000, mapped to 0xf8080000, using 1216k, total 1216k
    Feb 23 17:33:34 miki_netbook kernel: Console: switching to colour frame buffer device 80x30
    Feb 23 17:33:34 miki_netbook kernel: fb0: VESA VGA frame buffer device
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: MWAIT substates: 0x20220
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: v0.4 model 0x1C
    Feb 23 17:33:34 miki_netbook kernel: intel_idle: lapic_timer_reliable_states 0x2
    Feb 23 17:33:34 miki_netbook kernel: tsc: Marking TSC unstable due to TSC halts in idle states deeper than C2
    Feb 23 17:33:34 miki_netbook kernel: GHES: HEST is not enabled!
    Feb 23 17:33:34 miki_netbook kernel: isapnp: Scanning for PnP cards...
    Feb 23 17:33:34 miki_netbook kernel: isapnp: No Plug & Play device found
    Feb 23 17:33:34 miki_netbook kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Feb 23 17:33:34 miki_netbook kernel: i8042: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUE] at 0x60,0x64 irq 1,12
    Feb 23 17:33:34 miki_netbook kernel: i8042: Warning: Keylock active
    Feb 23 17:33:34 miki_netbook kernel: i8042: Detected active multiplexing controller, rev 1.1
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
    Feb 23 17:33:34 miki_netbook kernel: mousedev: PS/2 mouse device common for all mice
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: RTC can wake from S4
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    Feb 23 17:33:34 miki_netbook kernel: rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
    Feb 23 17:33:34 miki_netbook kernel: cpuidle: using governor ladder
    Feb 23 17:33:34 miki_netbook kernel: cpuidle: using governor menu
    Feb 23 17:33:34 miki_netbook kernel: EFI Variables Facility v0.08 2004-May-17
    Feb 23 17:33:34 miki_netbook kernel: drop_monitor: Initializing network drop monitor service
    Feb 23 17:33:34 miki_netbook kernel: TCP: cubic registered
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 10
    Feb 23 17:33:34 miki_netbook kernel: NET: Registered protocol family 17
    Feb 23 17:33:34 miki_netbook kernel: Key type dns_resolver registered
    Feb 23 17:33:34 miki_netbook kernel: Using IPI No-Shortcut mode
    Feb 23 17:33:34 miki_netbook kernel: PM: Hibernation image not present or could not be loaded.
    Feb 23 17:33:34 miki_netbook kernel: registered taskstats version 1
    Feb 23 17:33:34 miki_netbook kernel: Magic number: 1:324:589
    Feb 23 17:33:34 miki_netbook kernel: rtc_cmos 00:03: setting system clock to 2013-02-23 15:33:31 UTC (1361633611)
    Feb 23 17:33:34 miki_netbook kernel: Freeing unused kernel memory: 556k freed
    Feb 23 17:33:34 miki_netbook kernel: Write protecting the kernel text: 4100k
    Feb 23 17:33:34 miki_netbook kernel: Write protecting the kernel read-only data: 1256k
    Feb 23 17:33:34 miki_netbook kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Feb 23 17:33:34 miki_netbook systemd-udevd[44]: starting version 197
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type usb registered
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new interface driver usbfs
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new interface driver hub
    Feb 23 17:33:34 miki_netbook kernel: usbcore: registered new device driver usb
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: debug port 1
    Feb 23 17:33:34 miki_netbook kernel: SCSI subsystem initialized
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: irq 16, io mem 0x94344400
    Feb 23 17:33:34 miki_netbook kernel: ACPI: bus type scsi registered
    Feb 23 17:33:34 miki_netbook kernel: libata version 3.00 loaded.
    Feb 23 17:33:34 miki_netbook kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Feb 23 17:33:34 miki_netbook kernel: hub 1-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 1-0:1.0: 8 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: version 2.13
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: MAP [
    Feb 23 17:33:34 miki_netbook kernel: P0 P2 IDE IDE ]
    Feb 23 17:33:34 miki_netbook kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: scsi0 : ata_piix
    Feb 23 17:33:34 miki_netbook kernel: scsi1 : ata_piix
    Feb 23 17:33:34 miki_netbook kernel: ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x40a0 irq 14
    Feb 23 17:33:34 miki_netbook kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x40a8 irq 15
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.0: irq 16, io base 0x00004080
    Feb 23 17:33:34 miki_netbook kernel: hub 2-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 2-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.1: irq 17, io base 0x00004060
    Feb 23 17:33:34 miki_netbook kernel: hub 3-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 3-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x00004040
    Feb 23 17:33:34 miki_netbook kernel: hub 4-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 4-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
    Feb 23 17:33:34 miki_netbook kernel: uhci_hcd 0000:00:1d.3: irq 19, io base 0x00004020
    Feb 23 17:33:34 miki_netbook kernel: hub 5-0:1.0: USB hub found
    Feb 23 17:33:34 miki_netbook kernel: hub 5-0:1.0: 2 ports detected
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: ATA-8: SAMSUNG HM251JI, 2SS00_01, max UDMA7
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Feb 23 17:33:34 miki_netbook kernel: ata1.00: configured for UDMA/133
    Feb 23 17:33:34 miki_netbook kernel: scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM251JI 2SS0 PQ: 0 ANSI: 5
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Write Protect is off
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb 23 17:33:34 miki_netbook kernel: sda: sda1 sda2 sda3 sda4
    Feb 23 17:33:34 miki_netbook kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Feb 23 17:33:34 miki_netbook kernel: usb 1-5: new high-speed USB device number 3 using ehci_hcd
    Feb 23 17:33:34 miki_netbook kernel: usb 1-7: new high-speed USB device number 4 using ehci_hcd
    Feb 23 17:33:34 miki_netbook kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    Feb 23 17:33:34 miki_netbook kernel: usb 2-1: new low-speed USB device number 2 using uhci_hcd
    Feb 23 17:33:34 miki_netbook systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Feb 23 17:33:34 miki_netbook systemd[1]: Set hostname to <miki_netbook>.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Remote File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Remote File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Delayed Shutdown Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Delayed Shutdown Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Device-mapper event daemon FIFOs.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Device-mapper event daemon FIFOs.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting LVM2 metadata daemon socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on LVM2 metadata daemon socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Encrypted Volumes.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Encrypted Volumes.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Feb 23 17:33:34 miki_netbook systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Kernel Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on udev Kernel Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Control Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on udev Control Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Feb 23 17:33:34 miki_netbook systemd[1]: Expecting device dev-disk-by\x2duuid-9501e2aa\x2d4efe\x2d4497\x2d9b55\x2ddb7ebc7afe5d.device...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Journal Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Listening on Journal Socket.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started File System Check on Root Device.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Remount Root and Kernel File Systems...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Debug File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting POSIX Message Queue File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Load Kernel Modules.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted FUSE Control File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Setup Virtual Console...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Kernel Device Manager...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Apply Kernel Variables...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting udev Coldplug all Devices...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Configuration File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Huge Pages File System...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Set Up Additional Binary Formats.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Journal Service...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Journal Service.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounting Temporary Directory...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting home.automount.
    Feb 23 17:33:34 miki_netbook systemd[1]: Set up automount home.automount.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Setup Virtual Console.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Apply Kernel Variables.
    Feb 23 17:33:34 miki_netbook systemd-udevd[111]: starting version 197
    Feb 23 17:33:34 miki_netbook kernel: EXT4-fs (sda2): re-mounted. Opts: (null)
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Journal started
    Feb 23 17:33:34 miki_netbook systemd[1]: Started udev Kernel Device Manager.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Remount Root and Kernel File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Debug File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted POSIX Message Queue File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Configuration File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Huge Pages File System.
    Feb 23 17:33:34 miki_netbook systemd[1]: Mounted Temporary Directory.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Local File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Reached target Local File Systems.
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Recreate Volatile Files and Directories...
    Feb 23 17:33:34 miki_netbook systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
    Feb 23 17:33:34 miki_netbook systemd[1]: Started udev Coldplug all Devices.
    Feb 23 17:33:34 miki_netbook systemd-journal[119]: Allowing system journal files to grow to 1.4G.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Load Random Seed.
    Feb 23 17:33:34 miki_netbook systemd[1]: Started Recreate Volatile Files and Directories.
    Feb 23 17:33:37 miki_netbook systemd[1]: Starting Sound Card.
    Feb 23 17:33:37 miki_netbook systemd[1]: Reached target Sound Card.
    Feb 23 17:33:39 miki_netbook systemd[1]: Found device SAMSUNG_HM251JI.
    Feb 23 17:33:39 miki_netbook systemd[1]: Activating swap /dev/disk/by-uuid/9501e2aa-4efe-4497-9b55-db7ebc7afe5d...
    Feb 23 17:33:39 miki_netbook systemd[1]: Activated swap /dev/disk/by-uuid/9501e2aa-4efe-4497-9b55-db7ebc7afe5d.
    Feb 23 17:33:39 miki_netbook systemd[1]: Starting Swap.
    Feb 23 17:33:39 miki_netbook systemd[1]: Reached target Swap.
    Feb 23 17:33:39 miki_netbook systemd[1]: Starting System Initialization.
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> NetworkManager (version 0.9.6.4) is starting...
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    Feb 23 17:33:41 miki_netbook NetworkManager[229]: <info> WEXT support is enabled
    Feb 23 17:33:41 miki_netbook dbus[231]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Feb 23 17:33:41 miki_netbook polkitd[241]: Started polkitd version 0.109
    Feb 23 17:33:42 miki_netbook polkitd[241]: Loading rules from directory /etc/polkit-1/rules.d
    Feb 23 17:33:42 miki_netbook polkitd[241]: Loading rules from directory /usr/share/polkit-1/rules.d
    Feb 23 17:33:42 miki_netbook polkitd[241]: Finished loading, compiling and executing 1 rules
    Feb 23 17:33:42 miki_netbook dbus[231]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Feb 23 17:33:42 miki_netbook polkitd[241]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    Feb 23 17:33:42 miki_netbook NetworkManager[229]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    Feb 23 17:33:45 miki_netbook NetworkManager[229]: keyfile: parsing default ...
    Feb 23 17:33:45 miki_netbook NetworkManager[229]: keyfile: read connection 'default'
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: keyfile: parsing Badt ...
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: keyfile: read connection 'Badt'
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> trying to start the modem manager...
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> monitoring kernel firmware directory '/lib/firmware'.
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory
    Feb 23 17:33:46 miki_netbook NetworkManager[229]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/ieee80211/phy0/rfkill0) (driver rtl8187)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WiFi enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WWAN enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> WiMAX enabled by radio killswitch; enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> Networking is enabled by state file
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <warn> failed to allocate link cache: (-10) Operation not supported
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): carrier is OFF
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): exported as /org/freedesktop/NetworkManager/Devices/0
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): now managed
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): bringing up device.
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): preparing device.
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (enp2s0): deactivating device (reason 'managed') [2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/enp2s0
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): using nl80211 for WiFi device control
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): new 802.11 WiFi device (driver: 'rtl8187' ifindex: 3)
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): exported as /org/freedesktop/NetworkManager/Devices/1
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): now managed
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Feb 23 17:33:47 miki_netbook NetworkManager[229]: <info> (wlp0s29f7u7): bringing up device.
    Feb 23 17:33:47 miki_netbook kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Network Manager.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Network.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Network.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Network Time Service...
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Power Button [PWRB]
    Feb 23 17:33:47 miki_netbook kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Lid Switch [LID0]
    Feb 23 17:33:47 miki_netbook kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
    Feb 23 17:33:47 miki_netbook dbus-daemon[231]: dbus[231]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    Feb 23 17:33:47 miki_netbook dbus-daemon[231]: dbus[231]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Sleep Button [SLPB]
    Feb 23 17:33:47 miki_netbook kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Power Button [PWRF]
    Feb 23 17:33:47 miki_netbook kernel: intel_rng: FWH not detected
    Feb 23 17:33:47 miki_netbook kernel: ACPI: AC Adapter [ACAD] (on-line)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Requesting acpi_cpufreq
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Video Device [OVGA] (multi-head: yes rom: yes post: no)
    Feb 23 17:33:47 miki_netbook kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
    Feb 23 17:33:47 miki_netbook kernel: thermal LNXTHERM:00: registered as thermal_zone0
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Thermal Zone [THRM] (56 C)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Battery Slot [BAT1] (battery present)
    Feb 23 17:33:47 miki_netbook kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
    Feb 23 17:33:47 miki_netbook kernel: ACPI: Invalid Power Resource to register!
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning:
    Feb 23 17:33:47 miki_netbook kernel: 0x00000428-0x0000042f SystemIO conflicts with Region \PMBA 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning: 0x00000530-0x0000053f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: ACPI Warning: 0x00000500-0x0000052f SystemIO conflicts with Region \GPIO 1 (20120913/utaddress-251)
    Feb 23 17:33:47 miki_netbook kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    Feb 23 17:33:47 miki_netbook kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
    Feb 23 17:33:47 miki_netbook kernel: leds_ss4200: no LED devices found
    Feb 23 17:33:47 miki_netbook kernel: iTCO_vendor_support: vendor-support=0
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x0460)
    Feb 23 17:33:47 miki_netbook kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    Feb 23 17:33:47 miki_netbook kernel: microcode: CPU0 sig=0x106c2, pf=0x4, revision=0x208
    Feb 23 17:33:47 miki_netbook kernel: microcode: CPU1 sig=0x106c2, pf=0x4, revision=0x208
    Feb 23 17:33:47 miki_netbook kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    Feb 23 17:33:47 miki_netbook kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    Feb 23 17:33:47 miki_netbook kernel: r8169 0000:02:00.0: irq 42 for MSI/MSI-X
    Feb 23 17:33:47 miki_netbook kernel: r8169 0000:02:00.0 eth0: RTL8102e at 0xf8814000, 00:23:8b:85:d8:aa, XID 04a00000 IRQ 42
    Feb 23 17:33:47 miki_netbook kernel: Linux agpgart interface v0.103
    Feb 23 17:33:47 miki_netbook kernel: cfg80211: Calling CRDA to update world regulatory domain
    Feb 23 17:33:47 miki_netbook kernel: [drm] Initialized drm 1.1.0 20060810
    Feb 23 17:33:47 miki_netbook kernel: usbcore: registered new interface driver usbhid
    Feb 23 17:33:47 miki_netbook kernel: usbhid: USB HID core driver
    Feb 23 17:33:47 miki_netbook kernel: media: Linux media interface: v0.10
    Feb 23 17:33:47 miki_netbook systemd-udevd[137]: renamed network interface eth0 to enp2s0
    Feb 23 17:33:47 miki_netbook kernel: Linux video capture interface: v2.00
    Feb 23 17:33:47 miki_netbook kernel: i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
    Feb 23 17:33:47 miki_netbook kernel: uvcvideo: Found UVC 1.00 device USB 2.0 Camera (064e:a127)
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: Intel 945GME Chipset
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: detected gtt size: 262144K total, 262144K mappable
    Feb 23 17:33:47 miki_netbook ntpd[253]: ntpd [email protected] Tue Dec 18 22:49:50 UTC 2012 (1)
    Feb 23 17:33:47 miki_netbook ntpd[254]: proto: precision = 1.955 usec
    Feb 23 17:33:47 miki_netbook ntpd[254]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Feb 23 17:33:47 miki_netbook ntpd[254]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Feb 23 17:33:47 miki_netbook ntpd[254]: Listen and drop on 1 v6wildcard :: UDP 123
    Feb 23 17:33:47 miki_netbook kernel: agpgart-intel 0000:00:00.0: detected 8192K stolen memory
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Network Time Service.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Multi-User.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Multi-User.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Graphical Interface.
    Feb 23 17:33:47 miki_netbook systemd[1]: Reached target Graphical Interface.
    Feb 23 17:33:47 miki_netbook systemd[1]: Starting Update UTMP about System Runlevel Changes...
    Feb 23 17:33:47 miki_netbook systemd[1]: Started Update UTMP about System Runlevel Changes.
    Feb 23 17:33:47 miki_netbook systemd[1]: Startup finished in 2s 641ms 739us (kernel) + 14s 238ms 5

    I had the exact same problem. For me the problem was the user groups. Apparently usergroups is not necessary for most use cases with systemd. And my user was in a lot of groups :-) . So I backed up my /etc/group and removed my username from almost every group.
    Hope it solves your problem!

  • [SOLVED] Network Manager confusion on reading WiKi

    I have installed KDE DE...I am unable to start the network through NM...
    On going thru Arch Wiki , https://wiki.archlinux.org/index.php/NetworkManager
    I understand that there are 2 NMs available..One is for GNOME but works in all DE (backend), Other is "Knetworkmanager" which is for KDE.(backend)...
    The frontend GUI is Gnome- applet and KDEplasme-applet
    It is stated under KDE 3.5 , that Knetworkmanager is not supported but available in AUR...
    My doubt is as follows
    1. What should I install for KDE backend? --- Gnome Networkmanager or Knetworkmanager (Is the version for 4.4 & above supported?, wiki is silent on this)?
    2. For Frontend should I install the Plasma widget or the GNOME applet?
    3. If backend is GNOME network manager will it work with KDE plasma widget (front end) ?
    4. In /etc/rc.conf , in "DAEMONS = " should I give "knetworkmanager" or "networkmanager" If I install the KDE version?
    I had installed WIcd to test my settings...It was working initially after typing
    modprobe b43 <for bcm chipset>
    /etc/rc.d/network start
    /etc/rc.d/dbus restart
    /etc/rc.d/wicd start
    ifconfig wlan0 up
    dhcpcd wlan0
    wicd-curses
    Then I typed the network pwd and booted my interface.
    i wanted to go in for network manager as it would save me the typing time..(Currently I installed pacman -S networkmanager (GNOME version) and KDE plasma "the one with the icon similar to "m")But on selecting the interface it goes thru Activating Interface and then says "Network Connection failed"
    Now I am also not able to get wicd up
    Any pointers?
    EDIT ---The title says Graphical Front end managers, So I guess there is only one backend....In that case , why is my Network not working??All the wireless are detected ,so there is no problem with firmware....I have also enabled dhcpc (automatic)...So it shld fetch an IP address....dunno what the problem is..
    Last edited by vikrang (2011-04-29 10:11:02)

    vikrang wrote:1. What should I install for KDE backend? --- Gnome Networkmanager or Knetworkmanager (Is the version for 4.4 & above supported?, wiki is silent on this)?
    2. For Frontend should I install the Plasma widget or the GNOME applet?
    3. If backend is GNOME network manager will it work with KDE plasma widget (front end) ?
    4. In /etc/rc.conf , in "DAEMONS = " should I give "knetworkmanager" or "networkmanager" If I install the KDE version?
    1. there is just one, networkmanager. network-manager-applet and kdeplasma-applets-networkmanagement are just front-ends to networkmanager.
    2. https://wiki.archlinux.org/index.php/Ne … nager#KDE4 , but https://wiki.archlinux.org/index.php/Ne … ager#GNOME will work too. I use network-manager-applet on KDE 'cause the KDE front-end can't set a system connection.
    3. I won't even bother to answer to this.
    4. networkmanager!!!
    vikrang wrote:I have also enabled dhcpc (automatic)...So it shld fetch an IP address....dunno what the problem is..
    if you are using networkmanager you must the networkmanager daemon, not network. replace network with networkmanager in rc.conf in DAEMONS array.
    Last edited by JokerBoy (2011-04-27 08:59:42)

  • [SOLVED] Network Manager Applet

    One of the things I got used to from Ubuntu is the network manager applet, which allows managing connections with ease. As instructed in the Wiki, I tried installing it with the following commands:
    pacman -S networkmanager
    pacman -S network-manager-applet
    And then launched it by typing
    nm-applet
    But this comes up in the terminal:
    (nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_red_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
    (nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_green_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
    (nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_blue_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
    ** Message: applet now removed from the notification area
    (nm-applet:1518): libnotify-WARNING **: Failed to connect to proxy
    ** (nm-applet:1518): WARNING **: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1.
    ** (nm-applet:1518): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.
    ** (nm-applet:1518): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown return code 1
    ** Message: applet now embedded in the notification area
    ** Message: applet now removed from the notification area
    In the notification area the icon looked like it was going to show up, but it's removed immediately.
    I'm not even sure if I can connect to a wireless connection without this, can I? I wouldn't mind using a different method for connecting to my wireless connection, just as long as it works and it automatically connects when I login. So if anyone has got a better idea, please share it with me. In the mean time, what would I need to do to fix this and have the network manager applet working?
    Last edited by faviouz (2011-09-15 15:52:50)

    faviouz wrote:
    Thanks for the quick reply dodo3773!
    It worked excellently! I also added networkmanager to the daemons array and it loads on boot now, which is great.
    No problem. Glad to help. As karol said the wiki has many tips and tricks for almost anything that you need to get your system up and running. Make sure to read through the rest of the networkmanager one in regards to  gnome-keyring, groups, etc.. Take care and welcome to Arch Linux Forums.

Maybe you are looking for

  • Can't receive mail and lost mail

    Just went to mail and found existing mail  had disappeared. Not receiving new mail. Where do i find it? Receiving on iphone & ipad. The stored mail & received mail on iphone & ipad. Just got a problem with the imac.

  • Gr/ir clearance a/c

    Hi guys, How to clear a GR/IR account manually?  Our requirement is that we have already arranged the payment to vendor by JV.  We want to clear this balance amount from GR/IR a/c. thanks in advance chintu

  • Why does my 12" Powerbook run 18˚C hotter than my 15" iBook?

    Both computers have 1.33ghz G4 processors in them, and 1.25gb of ram. Both have OS 10.4.8. The iBook runs at 44˚ C according to Temperature Monitor. The PowerBook runs at 62˚C if not higher. I recently had the PowerBook's internal power input replace

  • How do I set up a periodic job to run only if the previous period job ran

    I want to sent up a process that will run on the second work day of the month that will run program A.  If program A runs successfully, then I want to run program B.  If B is successful, then program C. I tried to setup A to run on the second work da

  • SetBindValue() not binding.

    I am using the setBindValue() method on the XSU to avoid re-parsing my query. However, when looking at the parse/execute ratio, I noticed it is 1. It is parsing for every execution. Here is my code: --Determine the correct number of transitions to re