To z wczoraj, wkrótce po tym, jak przestało działać i zrobiłam restart:
May 4 20:28:53 mad-pc2pr4 whoopsie[703]: [20:28:53] Could not get the Network Manager state:
May 4 20:28:53 mad-pc2pr4 whoopsie[703]: [20:28:53] Could not get the Network Manager state:
May 4 20:28:53 mad-pc2pr4 whoopsie[703]: [20:28:53] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
May 4 20:28:53 mad-pc2pr4 whoopsie[703]: [20:28:53] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.3513] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.3988] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.3988] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.5062] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.5062] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
May 4 20:28:59 mad-pc2pr4 ModemManager[734]: <info> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0': not supported by any plugin
May 4 20:28:59 mad-pc2pr4 ModemManager[734]: <info> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0': not supported by any plugin
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.6454] settings: (enp7s0): created default wired connection 'Połączenie przewodowe 1'
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.6454] settings: (enp7s0): created default wired connection 'Połączenie przewodowe 1'
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.6463] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.6463] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.111588] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.111693] r8169 0000:07:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.111696] r8169 0000:07:00.0 enp7s0: unable to load firmware patch rtl_nic/rtl8106e-1.fw (-2)
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.111588] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.111693] r8169 0000:07:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.111696] r8169 0000:07:00.0 enp7s0: unable to load firmware patch rtl_nic/rtl8106e-1.fw (-2)
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.7786] device (lo): link connected
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.7786] device (lo): link connected
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.7790] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
May 4 20:28:59 mad-pc2pr4 NetworkManager[820]: <info> [1493922539.7790] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.242847] r8169 0000:07:00.0 enp7s0: link down
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.242911] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.242847] r8169 0000:07:00.0 enp7s0: link down
May 4 20:28:59 mad-pc2pr4 kernel: [ 33.242911] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra_defrtr'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4308] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra_rtr_pref'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4308] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4308] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/disable_ipv6'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4308] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4308] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/hop_limit'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4308] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4308] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/use_tempaddr'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra_defrtr'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra_pinfo'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra_pinfo'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra_rtr_pref'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra_rtr_pref'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/use_tempaddr'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/use_tempaddr'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/accept_ra'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <error> [1493922540.4309] Failed asserting path component: "hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D"
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/use_tempaddr'
May 4 20:29:00 mad-pc2pr4 NetworkManager[820]: <warn> [1493922540.4309] IPv6 property path is too long: '/proc/sys/net/ipv6/conf/hfp/org/bluez/hci0/dev_24_4B_81_00_95_4D/use_tempaddr'
I dzisiaj przy uruchamianiu:
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6831] device (lo): link connected
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6831] device (lo): link connected
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6840] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/0)
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6840] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/0)
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6856] manager: (enp7s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6856] manager: (enp7s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6868] keyfile: add connection in-memory (323c1118-9c5c-39aa-86a4-5d3509d2fab1,"Połączenie przewodowe 1")
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6868] keyfile: add connection in-memory (323c1118-9c5c-39aa-86a4-5d3509d2fab1,"Połączenie przewodowe 1")
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6874] settings: (enp7s0): created default wired connection 'Połączenie przewodowe 1'
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6874] settings: (enp7s0): created default wired connection 'Połączenie przewodowe 1'
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6888] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 5 13:44:16 mad-pc2pr4 NetworkManager[882]: <info> [1493984656.6888] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.154689] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.154844] r8169 0000:07:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.154848] r8169 0000:07:00.0 enp7s0: unable to load firmware patch rtl_nic/rtl8106e-1.fw (-2)
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.154689] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.154844] r8169 0000:07:00.0: Direct firmware load for rtl_nic/rtl8106e-1.fw failed with error -2
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.154848] r8169 0000:07:00.0 enp7s0: unable to load firmware patch rtl_nic/rtl8106e-1.fw (-2)
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.287423] r8169 0000:07:00.0 enp7s0: link down
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.287485] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.287423] r8169 0000:07:00.0 enp7s0: link down
May 5 13:44:16 mad-pc2pr4 kernel: [ 38.287485] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
To jest w syslog, jak dotąd w innych miejscach nic nie znalazłam. Nie jestem pewna, czy o to chodziło.
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
Subsystem: Dell Broadwell-U Host Bridge -OPI
Kernel driver in use: bdw_uncore
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
Subsystem: Dell Broadwell-U Integrated Graphics
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
Subsystem: Dell Broadwell-U Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
Subsystem: Dell Wildcat Point-LP USB xHCI Controller
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
Subsystem: Dell Wildcat Point-LP MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
Subsystem: Dell Wildcat Point-LP High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
Subsystem: Dell Wildcat Point-LP USB EHCI Controller
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
Subsystem: Dell Wildcat Point-LP LPC Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
Subsystem: Dell Wildcat Point-LP SATA Controller [AHCI Mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
Subsystem: Dell Wildcat Point-LP SMBus Controller
Kernel modules: i2c_i801
06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
Subsystem: Intel Corporation Dual Band Wireless AC 3160
Kernel modules: iwlwifi
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07)
Subsystem: Dell RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
Kernel driver in use: r8169
Kernel modules: r8169
08:00.0 3D controller: NVIDIA Corporation GK208M [GeForce 920M] (rev a1)
Subsystem: Dell GK208M [GeForce 920M]
Kernel driver in use: nouveau
Kernel modules: nouveau
Na chwilę obecną to w przeważającej części jest coś pomiędzy Ubuntu, Mintem a Zorinem, w prawie jednej trzeciej Debian testing. Debianowe odruchy zapewne jeszcze ma.
Ściągnęłam to. Przy tym musiałam pobrać jeszcze jedną rzecz i razem to pomogło. Bardzo dziękuję.