You are not logged in.

  1. Index
  2. » Basic Help & Support
  3. » [SOLVED] No (obvious) sign of wireless capability

Pages: 1

#1 2018-02-02 09:17:06

microcord
Member
Registered: 2017-06-21
Posts: 31

[SOLVED] No (obvious) sign of wireless capability

I have a one-day-old BL installation on a fortnight-old computer. Having followed Head_on_a_stick's advice in this thread to follow the recipe in this thread to upgrade the graphics stack, I can adjust the brightness of my LCD screen. And I also now have sound. What I didn't have before the upgrade and still don't have is wireless capability. I mean, I don't see any sign anywhere of wireless: no icon of four little bars next to the battery, volume and other icons at the top; nothing in the menu system I get when I press Superkey+Space; nada. (I'm now connected by ethernet cable.)

Here is some info that I believe ought to show me what's wrong. (Unfortunately, I am An Idiot, and therefore don't understand any of it.)

uname -rv

brings:

4.9.0-0.bpo.5-amd64 #1 SMP Debian 4.9.65-3+deb9u2~bpo8+1 (2017-01-05)

lspci -knn | grep -EiA2 net

brings:

04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)
    Subsystem: Lenovo Device [17aa:505b]
    Kernel driver in use: r8169
05:00.0 Network controller [0280]: Qualcomm Atheros Device [168c:0042] (rev 31)
    Subsystem: Lenovo Device [17aa:0901]
    Kernel driver in use: ath10k_pci
dmesg|grep -Ei 'wlan|firmw|dhc'

brings:

dmesg: read kernel buffer failed: Operation not permitted

(Should I worry?)

sudo cat /var/log/syslog | grep -Ei 'net|wpa|dhc'

brings [deep breath]:

Feb  2 14:00:45 bl-e470 systemd[1]: Stopping Network Manager...
Feb  2 14:07:30 bl-e470 systemd[1]: Starting LSB: Raise network interfaces....
Feb  2 14:07:30 bl-e470 networking[353]: Configuring network interfaces...done.
Feb  2 14:07:30 bl-e470 systemd[1]: Started LSB: Raise network interfaces..
Feb  2 14:07:30 bl-e470 systemd[1]: Starting Network.
Feb  2 14:07:30 bl-e470 systemd[1]: Reached target Network.
Feb  2 14:07:30 bl-e470 systemd[1]: Starting Network is Online.
Feb  2 14:07:30 bl-e470 systemd[1]: Reached target Network is Online.
Feb  2 14:07:30 bl-e470 systemd[1]: Starting Network Manager...
Feb  2 14:07:30 bl-e470 kernel: [    0.039633] Initializing cgroup subsys net_cls
Feb  2 14:07:30 bl-e470 kernel: [    0.039642] Initializing cgroup subsys net_prio
Feb  2 14:07:30 bl-e470 kernel: [    0.167341] NET: Registered protocol family 16
Feb  2 14:07:30 bl-e470 kernel: [    0.428136] NET: Registered protocol family 2
Feb  2 14:07:30 bl-e470 kernel: [    0.428821] NET: Registered protocol family 1
Feb  2 14:07:30 bl-e470 kernel: [    0.799503] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb  2 14:07:30 bl-e470 kernel: [    0.799913] audit: initializing netlink subsys (disabled)
Feb  2 14:07:30 bl-e470 kernel: [    0.821000] NET: Registered protocol family 10
Feb  2 14:07:30 bl-e470 kernel: [    0.821361] NET: Registered protocol family 17
Feb  2 14:07:30 bl-e470 kernel: [    0.852058] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Feb  2 14:07:30 bl-e470 kernel: [    0.853798] sdhci: Secure Digital Host Controller Interface driver
Feb  2 14:07:30 bl-e470 kernel: [    0.853800] sdhci: Copyright(c) Pierre Ossman
Feb  2 14:07:30 bl-e470 kernel: [    0.854154] sdhci-pci 0000:02:00.0: SDHCI controller found [1217:8621] (rev 1)
Feb  2 14:07:30 bl-e470 kernel: [    0.854251] sdhci-pci 0000:02:00.0: enabling device (0000 -> 0002)
Feb  2 14:07:30 bl-e470 kernel: [    0.854946] mmc0: SDHCI controller on PCI [0000:02:00.0] using ADMA
Feb  2 14:07:30 bl-e470 kernel: [    5.981362] NET: Registered protocol family 31
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> NetworkManager (version 0.9.10.0) is starting...
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> WEXT support is enabled
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> init!
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> update_system_hostname
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info>       interface-parser: parsing file /etc/network/interfaces
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info>       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <warn> interfaces file /etc/network/interfaces.d/* doesn't exist
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info>       interface-parser: finished parsing file /etc/network/interfaces
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> management mode: unmanaged
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:1d.2/0000:04:00.0/net/eth0, iface: eth0)
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> device added (path: /sys/devices/pci0000:00/0000:00:1d.2/0000:04:00.0/net/eth0, iface: eth0): no ifupdown configuration found.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> end _init.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (28198528) ... get_connections.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (28198528) ... get_connections (managed=false): return empty list.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> new connection /etc/NetworkManager/system-connections/Wired connection 1
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> get unmanaged devices count: 0
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> monitoring kernel firmware directory '/lib/firmware'.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> WiFi hardware radio set enabled
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> WWAN hardware radio set enabled
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> WiFi enabled by radio killswitch; enabled by state file
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> WWAN enabled by radio killswitch; enabled by state file
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> WiMAX enabled by radio killswitch; enabled by state file
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> Networking is enabled by state file
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (lo): link connected
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (lo): carrier is ON
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (eth0): carrier is OFF
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb  2 14:07:31 bl-e470 systemd[1]: Started Network Manager.
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> (eth0): preparing device
Feb  2 14:07:31 bl-e470 kernel: [   11.255619] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb  2 14:07:31 bl-e470 NetworkManager[485]: <info> ModemManager available in the bus
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> (eth0): link connected
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Auto-activating connection 'Wired connection 1'.
Feb  2 14:07:34 bl-e470 kernel: [   13.843787] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) starting connection 'Wired connection 1'
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> NetworkManager state is now CONNECTING
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> dhclient started with pid 639
Feb  2 14:07:34 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Feb  2 14:07:35 bl-e470 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Feb  2 14:07:35 bl-e470 dhclient: DHCPACK from 192.168.0.1
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> (eth0): DHCPv4 state changed preinit -> reboot
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   address 192.168.0.4
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   plen 24 (255.255.255.0)
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   gateway 192.168.0.1
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   server identifier 192.168.0.1
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   lease time 86400
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   nameserver '192.168.0.1'
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   domain name 'airport'
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info>   wins '192.168.0.1'
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> NetworkManager state is now CONNECTED_LOCAL
Feb  2 14:07:35 bl-e470 dhclient: bound to 192.168.0.4 -- renewal in 37601 seconds.
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> NetworkManager state is now CONNECTED_GLOBAL
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Feb  2 14:07:35 bl-e470 NetworkManager[485]: <info> Activation (eth0) successful, device activated.
Feb  2 14:07:35 bl-e470 systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb  2 14:07:35 bl-e470 systemd[1]: Started Network Manager Script Dispatcher Service.
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> Activation (eth0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> dhclient started with pid 677
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS.
Feb  2 14:07:36 bl-e470 dhclient: XMT: Info-Request on eth0, interval 970ms.
Feb  2 14:07:36 bl-e470 dhclient: RCV: Reply message on eth0 from fe80::21f:6cff:fe25:dac1.
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> (eth0): DHCPv6 state changed nbi -> renew6
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info>   nameserver '2404:1a8:7f01:b::3'
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info>   nameserver '2404:1a8:7f01:a::3'
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info>   domain search 'flets-east.jp.'
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info>   domain search 'iptvf.jp.'
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) scheduled...
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) started...
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) complete.
Feb  2 14:07:36 bl-e470 NetworkManager[485]: <info> (eth0): DHCPv6 client pid 677 exited with status 0
Feb  2 14:07:36 bl-e470 nm-dispatcher: Dispatching action 'dhcp6-change' for eth0
Feb  2 14:07:39 bl-e470 NetworkManager[485]: <info> startup complete
Feb  2 16:51:33 bl-e470 systemd[1]: Stopping Network Manager...
Feb  2 16:51:33 bl-e470 NetworkManager[485]: <info> caught signal 15, shutting down normally.
Feb  2 16:51:33 bl-e470 NetworkManager[485]: <info> exiting (success)
Feb  2 16:52:11 bl-e470 systemd[1]: Starting LSB: Raise network interfaces....
Feb  2 16:52:11 bl-e470 kernel: [    0.130574] NET: Registered protocol family 16
Feb  2 16:52:11 bl-e470 networking[380]: Configuring network interfaces...done.
Feb  2 16:52:11 bl-e470 systemd[1]: Started LSB: Raise network interfaces..
Feb  2 16:52:11 bl-e470 systemd[1]: Starting Network.
Feb  2 16:52:11 bl-e470 systemd[1]: Reached target Network.
Feb  2 16:52:11 bl-e470 systemd[1]: Starting Network is Online.
Feb  2 16:52:11 bl-e470 systemd[1]: Reached target Network is Online.
Feb  2 16:52:11 bl-e470 systemd[1]: Starting Network Manager...
Feb  2 16:52:11 bl-e470 kernel: [    0.367556] NET: Registered protocol family 2
Feb  2 16:52:11 bl-e470 kernel: [    0.367969] NET: Registered protocol family 1
Feb  2 16:52:11 bl-e470 kernel: [    0.788168] audit: initializing netlink subsys (disabled)
Feb  2 16:52:11 bl-e470 kernel: [    1.578442] NET: Registered protocol family 10
Feb  2 16:52:11 bl-e470 kernel: [    1.578717] NET: Registered protocol family 17
Feb  2 16:52:11 bl-e470 kernel: [    1.579208] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb  2 16:52:11 bl-e470 kernel: [    1.809896] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Feb  2 16:52:11 bl-e470 kernel: [    1.810287] sdhci: Secure Digital Host Controller Interface driver
Feb  2 16:52:11 bl-e470 kernel: [    1.810288] sdhci: Copyright(c) Pierre Ossman
Feb  2 16:52:11 bl-e470 kernel: [    1.810788] sdhci-pci 0000:02:00.0: SDHCI controller found [1217:8621] (rev 1)
Feb  2 16:52:11 bl-e470 kernel: [    1.810878] sdhci-pci 0000:02:00.0: enabling device (0000 -> 0002)
Feb  2 16:52:11 bl-e470 kernel: [    1.817062] mmc0: SDHCI controller on PCI [0000:02:00.0] using ADMA
Feb  2 16:52:11 bl-e470 kernel: [    7.637651] NET: Registered protocol family 31
Feb  2 16:52:11 bl-e470 kernel: [    8.564095] thinkpad_acpi: [url]http://ibm-acpi.sf.net/[/url]
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> NetworkManager (version 0.9.10.0) is starting...
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> WEXT support is enabled
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> init!
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> update_system_hostname
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info>       interface-parser: parsing file /etc/network/interfaces
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info>       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <warn> interfaces file /etc/network/interfaces.d/* doesn't exist
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info>       interface-parser: finished parsing file /etc/network/interfaces
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> management mode: unmanaged
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:1d.2/0000:04:00.0/net/eth0, iface: eth0)
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> device added (path: /sys/devices/pci0000:00/0000:00:1d.2/0000:04:00.0/net/eth0, iface: eth0): no ifupdown configuration found.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> end _init.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (8787584) ... get_connections.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (8787584) ... get_connections (managed=false): return empty list.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> new connection /etc/NetworkManager/system-connections/Wired connection 1
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> get unmanaged devices count: 0
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> monitoring kernel firmware directory '/lib/firmware'.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> WiFi hardware radio set enabled
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> WWAN hardware radio set enabled
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> WiFi enabled by radio killswitch; enabled by state file
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> WWAN enabled by radio killswitch; enabled by state file
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> WiMAX enabled by radio killswitch; enabled by state file
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> Networking is enabled by state file
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (lo): link connected
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (lo): carrier is ON
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (eth0): carrier is OFF
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb  2 16:52:12 bl-e470 systemd[1]: Started Network Manager.
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> (eth0): preparing device
Feb  2 16:52:12 bl-e470 NetworkManager[516]: <info> ModemManager available in the bus
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> (eth0): link connected
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Auto-activating connection 'Wired connection 1'.
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) starting connection 'Wired connection 1'
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> NetworkManager state is now CONNECTING
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> dhclient started with pid 652
Feb  2 16:52:15 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Feb  2 16:52:16 bl-e470 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Feb  2 16:52:16 bl-e470 dhclient: DHCPACK from 192.168.0.1
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv4 state changed preinit -> reboot
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   address 192.168.0.4
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   plen 24 (255.255.255.0)
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   gateway 192.168.0.1
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   server identifier 192.168.0.1
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   lease time 86400
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   nameserver '192.168.0.1'
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   domain name 'airport'
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info>   wins '192.168.0.1'
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> NetworkManager state is now CONNECTED_LOCAL
Feb  2 16:52:16 bl-e470 dhclient: bound to 192.168.0.4 -- renewal in 42622 seconds.
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> NetworkManager state is now CONNECTED_GLOBAL
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Feb  2 16:52:16 bl-e470 NetworkManager[516]: <info> Activation (eth0) successful, device activated.
Feb  2 16:52:16 bl-e470 systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb  2 16:52:16 bl-e470 systemd[1]: Started Network Manager Script Dispatcher Service.
Feb  2 16:52:17 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Feb  2 16:52:17 bl-e470 NetworkManager[516]: <info> Activation (eth0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Feb  2 16:52:17 bl-e470 NetworkManager[516]: <info> dhclient started with pid 689
Feb  2 16:52:18 bl-e470 dhclient: XMT: Info-Request on eth0, interval 1070ms.
Feb  2 16:52:18 bl-e470 dhclient: RCV: Reply message on eth0 from fe80::21f:6cff:fe25:dac1.
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv6 state changed nbi -> renew6
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info>   nameserver '2404:1a8:7f01:b::3'
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info>   nameserver '2404:1a8:7f01:a::3'
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info>   domain search 'flets-east.jp.'
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info>   domain search 'iptvf.jp.'
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) scheduled...
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) started...
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS.
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) complete.
Feb  2 16:52:18 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv6 client pid 689 exited with status 0
Feb  2 16:52:18 bl-e470 nm-dispatcher: Dispatching action 'dhcp6-change' for eth0
Feb  2 16:52:20 bl-e470 NetworkManager[516]: <info> startup complete
Feb  2 17:14:08 bl-e470 NetworkManager[516]: <info> (eth0): link disconnected (deferring action for 4 seconds)
Feb  2 17:14:12 bl-e470 NetworkManager[516]: <info> (eth0): link disconnected (calling deferred action)
Feb  2 17:14:12 bl-e470 NetworkManager[516]: <info> (eth0): device state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
Feb  2 17:14:12 bl-e470 NetworkManager[516]: <info> (eth0): deactivating device (reason 'carrier-changed') [40]
Feb  2 17:14:12 bl-e470 NetworkManager[516]: <info> (eth0): canceled DHCP transaction, DHCP client pid 652
Feb  2 17:14:12 bl-e470 NetworkManager[516]: <info> NetworkManager state is now CONNECTED_LOCAL
Feb  2 17:14:12 bl-e470 NetworkManager[516]: <info> NetworkManager state is now DISCONNECTED
Feb  2 17:14:12 bl-e470 systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb  2 17:14:12 bl-e470 systemd[1]: Started Network Manager Script Dispatcher Service.
Feb  2 17:18:01 bl-e470 NetworkManager[516]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Feb  2 17:18:01 bl-e470 NetworkManager[516]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (4) GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Feb  2 17:18:01 bl-e470 NetworkManager[516]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (2) GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.3 was not provided by any .service files
Feb  2 17:18:01 bl-e470 NetworkManager[516]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (2) GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.3 was not provided by any .service files
Feb  2 17:18:01 bl-e470 NetworkManager[516]: <info> caught signal 15, shutting down normally.
Feb  2 17:18:01 bl-e470 NetworkManager[516]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Feb  2 17:18:01 bl-e470 systemd[1]: Stopping Network Manager...
Feb  2 17:18:33 bl-e470 systemd[1]: Starting LSB: Raise network interfaces....
Feb  2 17:18:33 bl-e470 networking[381]: Configuring network interfaces...done.
Feb  2 17:18:33 bl-e470 systemd[1]: Started LSB: Raise network interfaces..
Feb  2 17:18:33 bl-e470 systemd[1]: Starting Network.
Feb  2 17:18:33 bl-e470 systemd[1]: Reached target Network.
Feb  2 17:18:33 bl-e470 systemd[1]: Starting Network is Online.
Feb  2 17:18:33 bl-e470 systemd[1]: Reached target Network is Online.
Feb  2 17:18:33 bl-e470 systemd[1]: Starting Network Manager...
Feb  2 17:18:33 bl-e470 kernel: [    0.134342] NET: Registered protocol family 16
Feb  2 17:18:33 bl-e470 kernel: [    0.363392] NET: Registered protocol family 2
Feb  2 17:18:33 bl-e470 kernel: [    0.363828] NET: Registered protocol family 1
Feb  2 17:18:33 bl-e470 kernel: [    0.784042] audit: initializing netlink subsys (disabled)
Feb  2 17:18:33 bl-e470 kernel: [    1.573554] NET: Registered protocol family 10
Feb  2 17:18:33 bl-e470 kernel: [    1.573817] NET: Registered protocol family 17
Feb  2 17:18:33 bl-e470 kernel: [    1.574114] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb  2 17:18:33 bl-e470 kernel: [    1.801767] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Feb  2 17:18:33 bl-e470 kernel: [    1.803093] sdhci: Secure Digital Host Controller Interface driver
Feb  2 17:18:33 bl-e470 kernel: [    1.803094] sdhci: Copyright(c) Pierre Ossman
Feb  2 17:18:33 bl-e470 kernel: [    1.803639] sdhci-pci 0000:02:00.0: SDHCI controller found [1217:8621] (rev 1)
Feb  2 17:18:33 bl-e470 kernel: [    1.803729] sdhci-pci 0000:02:00.0: enabling device (0000 -> 0002)
Feb  2 17:18:33 bl-e470 kernel: [    1.811650] mmc0: SDHCI controller on PCI [0000:02:00.0] using ADMA
Feb  2 17:18:33 bl-e470 kernel: [    7.805530] NET: Registered protocol family 31
Feb  2 17:18:33 bl-e470 kernel: [    8.355896] thinkpad_acpi: [url]http://ibm-acpi.sf.net/[/url]
Feb  2 17:18:34 bl-e470 NetworkManager[516]: <info> NetworkManager (version 0.9.10.0) is starting...
Feb  2 17:18:34 bl-e470 NetworkManager[516]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Feb  2 17:18:34 bl-e470 NetworkManager[516]: <info> WEXT support is enabled
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> init!
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> update_system_hostname
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info>       interface-parser: parsing file /etc/network/interfaces
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info>       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <warn> interfaces file /etc/network/interfaces.d/* doesn't exist
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info>       interface-parser: finished parsing file /etc/network/interfaces
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> management mode: unmanaged
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:1d.2/0000:04:00.0/net/eth0, iface: eth0)
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> device added (path: /sys/devices/pci0000:00/0000:00:1d.2/0000:04:00.0/net/eth0, iface: eth0): no ifupdown configuration found.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> end _init.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (23422592) ... get_connections.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (23422592) ... get_connections (managed=false): return empty list.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> new connection /etc/NetworkManager/system-connections/Wired connection 1
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> get unmanaged devices count: 0
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> monitoring kernel firmware directory '/lib/firmware'.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> WiFi hardware radio set enabled
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> WWAN hardware radio set enabled
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> WiFi enabled by radio killswitch; enabled by state file
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> WWAN enabled by radio killswitch; enabled by state file
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> WiMAX enabled by radio killswitch; enabled by state file
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> Networking is enabled by state file
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (lo): link connected
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (lo): carrier is ON
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (eth0): carrier is OFF
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb  2 17:18:35 bl-e470 systemd[1]: Started Network Manager.
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> (eth0): preparing device
Feb  2 17:18:35 bl-e470 NetworkManager[516]: <info> ModemManager available in the bus
Feb  2 17:18:40 bl-e470 NetworkManager[516]: <info> startup complete
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): link connected
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Auto-activating connection 'Wired connection 1'.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) starting connection 'Wired connection 1'
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> NetworkManager state is now CONNECTING
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> dhclient started with pid 837
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Feb  2 17:19:18 bl-e470 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Feb  2 17:19:18 bl-e470 dhclient: DHCPACK from 192.168.0.1
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv4 state changed preinit -> reboot
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   address 192.168.0.4
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   plen 24 (255.255.255.0)
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   gateway 192.168.0.1
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   server identifier 192.168.0.1
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   lease time 86400
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   nameserver '192.168.0.1'
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   domain name 'airport'
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info>   wins '192.168.0.1'
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> NetworkManager state is now CONNECTED_LOCAL
Feb  2 17:19:18 bl-e470 dhclient: bound to 192.168.0.4 -- renewal in 38753 seconds.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> NetworkManager state is now CONNECTED_GLOBAL
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Feb  2 17:19:18 bl-e470 NetworkManager[516]: <info> Activation (eth0) successful, device activated.
Feb  2 17:19:18 bl-e470 systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb  2 17:19:18 bl-e470 systemd[1]: Started Network Manager Script Dispatcher Service.
Feb  2 17:19:19 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Feb  2 17:19:19 bl-e470 NetworkManager[516]: <info> Activation (eth0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Feb  2 17:19:19 bl-e470 NetworkManager[516]: <info> dhclient started with pid 859
Feb  2 17:19:20 bl-e470 dhclient: XMT: Info-Request on eth0, interval 1070ms.
Feb  2 17:19:20 bl-e470 dhclient: RCV: Reply message on eth0 from fe80::21f:6cff:fe25:dac1.
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv6 state changed nbi -> renew6
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info>   nameserver '2404:1a8:7f01:b::3'
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info>   nameserver '2404:1a8:7f01:a::3'
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info>   domain search 'flets-east.jp.'
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info>   domain search 'iptvf.jp.'
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) scheduled...
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) started...
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS.
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) complete.
Feb  2 17:19:20 bl-e470 NetworkManager[516]: <info> (eth0): DHCPv6 client pid 859 exited with status 0
Feb  2 17:19:20 bl-e470 nm-dispatcher: Dispatching action 'dhcp6-change' for eth0

(Sorry about the length. In the instructions about BBcode, I don't see any way to put such material in a compact text box.)

sudo rfkill list

brings:

0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: no
    Hard blocked: no
ip link

brings:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 8c:16:45:17:c6:aa brd ff:ff:ff:ff:ff:ff

   
Incidentally (or relevantly?), while I was installing BL yesterday I was told that rtl_nic/rtl8168g-3.fw was missing. Not knowing what this meant or what I should do about it, I just ignored it; no further problems were apparent. Booting the system brings two error messages. There's "mmc0 Unknown controller version (3) / You may experience problems"; but I believe that this refers to the slot for SD cards (which I've come to expect won't work on any machine; I use a simple SD-into-USB adapter instead). And there's "kvm: disabled by BIOS"; sorry, but I can't figure out what "virtualization" means (I can't even make sense of the Wikipedia article about it). All I know is that no item I see anywhere in the BIOS menu mentions "wireless".

Last edited by microcord (2018-02-03 04:04:18)

Offline

#2 2018-02-02 10:02:47

ohnonot
...again
Registered: 2015-09-29
Posts: 5,592

Re: [SOLVED] No (obvious) sign of wireless capability

microcord wrote:

Incidentally (or relevantly?), while I was installing BL yesterday I was told that rtl_nic/rtl8168g-3.fw was missing.

interesting. the "rtl..." suggest realtek? is wired internet working ok?

from your lspci, i think the atheros could be the wireless.

try dmesg again with sudo.

if you still cannot find your wireless device (are you sure there is one?) you can also take a look at 

lsusb

yes, even internal devices can be usb.

Offline

#3 2018-02-02 12:55:53

microcord
Member
Registered: 2017-06-21
Posts: 31

Re: [SOLVED] No (obvious) sign of wireless capability

ohnonot wrote:

is wired internet working ok?

Yes, no complaints about wired internet. (It's what I'm using for these message threads.)

ohnonot wrote:

try dmesg again with sudo.

Duh! Even I should have thought of that. 

sudo dmesg|grep -Ei 'wlan|firmw|dhc'

brings:

[    0.186355] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    1.803093] sdhci: Secure Digital Host Controller Interface driver
[    1.803094] sdhci: Copyright(c) Pierre Ossman
[    1.803639] sdhci-pci 0000:02:00.0: SDHCI controller found [1217:8621] (rev 1)
[    1.803729] sdhci-pci 0000:02:00.0: enabling device (0000 -> 0002)
[    1.811650] mmc0: SDHCI controller on PCI [0000:02:00.0] using ADMA
[    7.019324] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
[    7.118930] [drm] GuC firmware load skipped
[    7.125644] i915 0000:00:02.0: firmware: failed to load i915/skl_dmc_ver1_26.bin (-2)
[    7.125649] i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1_26.bin failed with error -2
[    7.125651] i915 0000:00:02.0: Failed to load DMC firmware [[url]https://01.org/linuxgraphics/intel-linux-graphics-firmwares[/url]], disabling runtime power management.
[    8.089005] ath10k_pci 0000:05:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:05:00.0.bin (-2)
[    8.089008] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:05:00.0.bin failed with error -2
[    8.089021] ath10k_pci 0000:05:00.0: firmware: failed to load ath10k/cal-pci-0000:05:00.0.bin (-2)
[    8.089022] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/cal-pci-0000:05:00.0.bin failed with error -2
[    8.089033] ath10k_pci 0000:05:00.0: firmware: failed to load ath10k/QCA9377/hw1.0/firmware-5.bin (-2)
[    8.089034] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-5.bin failed with error -2
[    8.089038] ath10k_pci 0000:05:00.0: could not fetch firmware file 'ath10k/QCA9377/hw1.0/firmware-5.bin': -2
[    8.089047] ath10k_pci 0000:05:00.0: firmware: failed to load ath10k/QCA9377/hw1.0/firmware-4.bin (-2)
[    8.089049] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-4.bin failed with error -2
[    8.089051] ath10k_pci 0000:05:00.0: could not fetch firmware file 'ath10k/QCA9377/hw1.0/firmware-4.bin': -2
[    8.089061] ath10k_pci 0000:05:00.0: firmware: failed to load ath10k/QCA9377/hw1.0/firmware-3.bin (-2)
[    8.089062] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-3.bin failed with error -2
[    8.089064] ath10k_pci 0000:05:00.0: could not fetch firmware file 'ath10k/QCA9377/hw1.0/firmware-3.bin': -2
[    8.089074] ath10k_pci 0000:05:00.0: firmware: failed to load ath10k/QCA9377/hw1.0/firmware-2.bin (-2)
[    8.089075] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-2.bin failed with error -2
[    8.089077] ath10k_pci 0000:05:00.0: could not fetch firmware file 'ath10k/QCA9377/hw1.0/firmware-2.bin': -2
[    8.089079] ath10k_pci 0000:05:00.0: could not fetch firmware files (-2)
[   13.538354] r8169 0000:04:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-3.fw
[ 4434.140907] [drm] GuC firmware load skipped

Clearly there's a lot that it "could not fetch" or "failed to load"; I suppose something needs (re)installation, but that's the extent of my guesswork.

lsusb

brings

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04f2:b5c0 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
Bus 001 Device 002: ID 056e:00e3 Elecom Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

What I paid for was something with "IEEE 802.11ac/a/b/g/n ワイヤレスLAN (WiFi準拠)1x1 + Bluetooth 4.1", i.e. "IEEE 802.11ac/a/b/g/n wireless LAN (WiFi-conforming [?])1x1 + Bluetooth 4.1". (The label on the box is less informative: "WLAN 802.11AC BT 1X1 ROW".) Whatever this is, I'd hope that it's in my new toy, somewhere!

Last edited by Head_on_a_Stick (2018-02-02 18:22:54)

Offline

#4 2018-02-02 18:25:26

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] No (obvious) sign of wireless capability

@OP: this is silly, please just install our Helium-dev system.

You could get your wireless working with backports (just like with your graphics) but this is just flogging a dead horse (IMO).

EDIT: if you insist on pursuing this then try installing this .deb:

https://cdn-aws.deb.debian.org/debian/p … +1_all.deb

Last edited by Head_on_a_Stick (2018-02-02 18:37:58)

Para todos todo, para nosotros nada

Offline

#5 2018-02-03 01:26:56

microcord
Member
Registered: 2017-06-21
Posts: 31

Re: [SOLVED] No (obvious) sign of wireless capability

Head_on_a_Stick wrote:

@OP: this is silly, please just install our Helium-dev system.

Thank you for your patience, Head. Unfortunately I can't install Helium-dev, but that's a matter for a different message thread.

Thank you for your (somewhat reluctant) recommendation:

if you insist on pursuing this then try installing this .deb:

https://cdn-aws.deb.debian.org/debian/p … +1_all.deb

Getting close! I installed it, unplugged the ethernet wire, rebooted, and up at the top right of the screen was told "Wi-Fi networks available" -- exactly what I'd hoped to see. That message continued by asking me to pursue this via the network menu.

I only know of one network menu (Super+Space, "Network"), and ... there's no mention of wifi there. (All that's on offer are browsers, Filezilla, Transmission, remote filesystems, remote desktop, SSH, Dropbox.) What other recommended method is there?

Offline

#6 2018-02-03 03:01:23

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 12,681
Website

Re: [SOLVED] No (obvious) sign of wireless capability

^Try the system tray network manager icon.

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

Offline

#7 2018-02-03 04:01:29

microcord
Member
Registered: 2017-06-21
Posts: 31

Re: [SOLVED] No (obvious) sign of wireless capability

johnraff wrote:

^Try the system tray network manager icon.

Howls of derisive laughter (at myself). It works!

I did try that yesterday: nothing there. Today, somehow (shortage of sleep, mental retardation, whatever) I convinced myself that I ought to see two separate icons, one for wireless, the other for wired, so I didn't try it again. Duh.

Thank you!

(I think you will agree that I am the last person you want to be attempting to install Helium-dev, failing, and asking lots of stupid questions about it.)

Offline

Pages: 1

  1. Index
  2. » Basic Help & Support
  3. » [SOLVED] No (obvious) sign of wireless capability

Board footer

Powered by FluxBB