LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 01-12-2021, 08:01 PM   #1
MdAyq
LQ Newbie
 
Registered: Jan 2020
Posts: 17

Rep: Reputation: 0
WiFi doesn't start on boot but only a few minutes later


Upon boot, the WiFi won't start. However, after a few minutes I get Internet. What to do? I tried to adapt some configuration files; no help.

Here are some bits of my configuration in the state before WiFi is obtained with comments stripped out for the sake of space:
Code:
root@PC:~# cat /etc/network/interfaces
source /etc/network/interfaces.d/*
auto lo 
iface lo inet loopback
allow-hotplug wlp179s0
iface wlp179s0 inet dhcp
iface wlp179s0 inet6 auto
        wpa-ssid AnonymizedSSID
        wpa-psk  AnonymizedWPA2Password
allow-hotplug enp6s0 enp7s0
auto wlp179s0
root@PC:~# ls -a /etc/network/interfaces.d
.  ..  setup
root@PC:~# cat /etc/network/interfaces.d/setup 
auto lo
iface lo inet loopback
root@PC:~# lshw -c network
  *-network
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:06:00.0
       logical name: enp6s0
       version: 03
       serial: d4:5d:64:ba:fb:0f
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.10.0-1-amd64 firmware=3.16, 0x80000513 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:18 memory:90600000-9067ffff ioport:3000(size=32) memory:90680000-90683fff
  *-network
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:07:00.0
       logical name: enp7s0
       version: 03
       serial: d4:5d:64:ba:fb:0e
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.10.0-1-amd64 firmware=3.16, 0x800004d7 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:19 memory:90500000-9057ffff ioport:2000(size=32) memory:90580000-90583fff
  *-network
       description: Wireless interface
       product: Wi-Fi 6 AX200
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:b3:00.0
       logical name: wlp179s0
       version: 1a
       serial: c8:e2:65:ff:9c:40
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=5.10.0-1-amd64 firmware=59.601f3a66.0 cc-a0-59.ucode latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:96 memory:fbe00000-fbe03fff
root@PC:~# lspci -nnk | grep -A 4 -i network
06:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)
        Subsystem: ASUSTeK Computer Inc. I210 Gigabit Network Connection [1043:8557]
        Kernel driver in use: igb
        Kernel modules: igb
07:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)
        Subsystem: ASUSTeK Computer Inc. I210 Gigabit Network Connection [1043:8557]
        Kernel driver in use: igb
        Kernel modules: igb
08:00.0 Multimedia video controller [0400]: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb [14f1:8880] (rev 04)
        Subsystem: Hauppauge computer works Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb [0070:f038]
--
b3:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX200 [8086:0084]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
root@PC:~# cat /etc/NetworkManager/NetworkManager.conf 
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false
root@PC:~# journalctl -b | egrep -C 2 "(dhclient)|(ifup)|(network)"
Jan 13 03:33:44 PC systemd[1]: Finished Set the console keyboard layout.
Jan 13 03:33:44 PC systemd[1]: Finished Coldplug All udev Devices.
Jan 13 03:33:44 PC systemd[1]: Starting Helper to synchronize boot up for ifupdown...
Jan 13 03:33:44 PC systemd[1]: Started Rule-based Manager for Device Events and Files.
Jan 13 03:33:44 PC systemd[1]: Starting Show Plymouth Boot Screen...
--
Jan 13 03:33:45 PC cron[685]: (CRON) INFO (Running @reboot jobs)
Jan 13 03:33:45 PC systemd[1]: Starting LSB: gpm sysv init script...
Jan 13 03:33:45 PC systemd[1]: Started ifup for wlp179s0.
Jan 13 03:33:45 PC systemd[1]: Starting Initialize hardware monitoring sensors...
Jan 13 03:33:45 PC systemd[1]: Starting LSB: Load kernel modules needed to enable cpufreq scaling...
--
Jan 13 03:33:45 PC smartd[700]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jan 13 03:33:45 PC polkitd[696]: started daemon version 0.105 using authority implementation `local' version `0.105'
Jan 13 03:33:45 PC dhclient[742]: Internet Systems Consortium DHCP Client 4.4.1
Jan 13 03:33:45 PC systemd[1]: e2scrub_reap.service: Succeeded.
Jan 13 03:33:45 PC sh[742]: Internet Systems Consortium DHCP Client 4.4.1
--
Jan 13 03:33:45 PC sh[742]: All rights reserved.
Jan 13 03:33:45 PC sh[742]: For info, please visit https://www.isc.org/software/dhcp/
Jan 13 03:33:45 PC dhclient[742]: Copyright 2004-2018 Internet Systems Consortium.
Jan 13 03:33:45 PC systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Jan 13 03:33:45 PC dhclient[742]: All rights reserved.
Jan 13 03:33:45 PC dhclient[742]: For info, please visit https://www.isc.org/software/dhcp/
Jan 13 03:33:45 PC dhclient[742]: 
Jan 13 03:33:45 PC accounts-daemon[681]: started daemon version 0.6.55
Jan 13 03:33:45 PC smartd[700]: Device: /dev/sda, type changed from 'scsi' to 'sat'
--
Jan 13 03:33:45 PC smartd[700]: Sending warning via /usr/share/smartmontools/smartd-runner to root ...
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.5486] manager[0x55666665e030]: monitoring kernel firmware directory '/lib/firmware'.
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.5486] monitoring ifupdown state file '/run/network/ifstate'.
Jan 13 03:33:45 PC dbus-daemon[686]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.8' (uid=0 pid=688 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 13 03:33:45 PC systemd[1]: Starting Hostname Service...
--
Jan 13 03:33:45 PC sensors[720]:                        (emerg = +135.0C, hyst =  +5.0C)
Jan 13 03:33:45 PC systemd[1]: Finished Initialize hardware monitoring sensors.
Jan 13 03:33:45 PC dhclient[742]: Listening on LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 03:33:45 PC sh[742]: Listening on LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 03:33:45 PC dhclient[742]: Sending on   LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 03:33:45 PC sh[742]: Sending on   LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 03:33:45 PC dhclient[742]: Sending on   Socket/fallback
Jan 13 03:33:45 PC sh[742]: Sending on   Socket/fallback
Jan 13 03:33:45 PC dhclient[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 5
Jan 13 03:33:45 PC sh[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 5
Jan 13 03:33:45 PC dbus-daemon[686]: [system] Successfully activated service 'org.freedesktop.hostname1'
--
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6578] manager: Networking is enabled by state file
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6578] dhcp-init: Using DHCP client 'internal'
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6583] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-settings-plugin-ifupdown.so")
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6584] settings: Loaded settings plugin: keyfile (internal)
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6584] ifupdown: management mode: unmanaged
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6584] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6584] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6584] ifupdown:       interface-parser: parsing file /etc/network/interfaces.d/setup
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6584] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces.d/setup
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6584] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6588] ifupdown: guessed connection type (wlp179s0) = 802-3-ethernet
Jan 13 03:33:45 PC dbus-daemon[686]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=688 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6593] ifupdown: guessed connection type (wlp179s0) = 802-11-wireless
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6593] ifupdown: update wireless settings (wlp179s0).
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6594] ifupdown: setting wpa ssid = 9
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6594] ifupdown: update wireless security settings (wlp179s0).
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6595] ifupdown: setting wpa security key: psk=<omitted>
Jan 13 03:33:45 PC udisksd[712]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jan 13 03:33:45 PC NetworkManager[688]: <info>  [1610505225.6603] device (lo): carrier: link connected
--
Jan 13 03:33:46 PC cpufrequtils[904]: CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...done.
Jan 13 03:33:46 PC systemd[1]: Started LSB: set CPUFreq kernel parameters.
Jan 13 03:33:46 PC systemd[1]: Finished Helper to synchronize boot up for ifupdown.
Jan 13 03:33:46 PC systemd[1]: Starting Raise network interfaces...
Jan 13 03:33:46 PC ifup[913]: ifup: waiting for lock on /run/network/ifstate.wlp179s0
Jan 13 03:33:47 PC ModemManager[803]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0': not supported by any plugin
Jan 13 03:33:47 PC ModemManager[803]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0': not supported by any plugin
Jan 13 03:33:47 PC ModemManager[803]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0': not supported by any plugin
Jan 13 03:33:50 PC systemd[1]: systemd-rfkill.service: Succeeded.
Jan 13 03:33:50 PC dhclient[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 11
Jan 13 03:33:50 PC sh[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 11
Jan 13 03:33:51 PC NetworkManager[688]: <info>  [1610505231.7343] manager: startup complete
Jan 13 03:33:51 PC systemd[1]: Finished Network Manager Wait Online.
Jan 13 03:33:55 PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 13 03:34:01 PC dhclient[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 7
Jan 13 03:34:01 PC sh[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 7
Jan 13 03:34:08 PC dhclient[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 15
Jan 13 03:34:08 PC sh[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 15
Jan 13 03:34:14 PC systemd[1]: systemd-fsckd.service: Succeeded.
Jan 13 03:34:15 PC systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 13 03:34:23 PC dhclient[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 16
Jan 13 03:34:23 PC sh[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 16
Jan 13 03:34:39 PC dhclient[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 7
Jan 13 03:34:39 PC sh[742]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 7
Jan 13 03:34:46 PC dhclient[742]: No DHCPOFFERS received.
Jan 13 03:34:46 PC sh[742]: No DHCPOFFERS received.
Jan 13 03:34:46 PC sh[742]: No working leases in persistent database - sleeping.
Jan 13 03:34:46 PC dhclient[742]: No working leases in persistent database - sleeping.
Jan 13 03:34:46 PC avahi-autoipd(wlp179s0)[964]: Found user 'avahi-autoipd' (UID 108) and group 'avahi-autoipd' (GID 117).
Jan 13 03:34:46 PC avahi-autoipd(wlp179s0)[964]: Successfully called chroot().
--
Jan 13 03:34:55 PC wpa_supplicant[1011]: Successfully initialized wpa_supplicant
Jan 13 03:34:56 PC sh[1060]: wlp179s0=wlp179s0
Jan 13 03:34:56 PC systemd[1]: Finished Raise network interfaces.
Jan 13 03:34:56 PC systemd[1]: Reached target Network.
Jan 13 03:34:56 PC systemd[1]: Reached target Network is Online.
--
Jan 13 03:34:56 PC systemd[1345]: Reached target Timers.
Jan 13 03:34:56 PC systemd[1345]: Starting D-Bus User Message Bus Socket.
Jan 13 03:34:56 PC systemd[1345]: Listening on GnuPG network certificate management daemon.
Jan 13 03:34:56 PC systemd[1345]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 13 03:34:56 PC systemd[1345]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
--
Jan 13 03:35:09 PC systemd[1832]: Reached target Timers.
Jan 13 03:35:09 PC systemd[1832]: Starting D-Bus User Message Bus Socket.
Jan 13 03:35:09 PC systemd[1832]: Listening on GnuPG network certificate management daemon.
Jan 13 03:35:09 PC systemd[1832]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 13 03:35:09 PC systemd[1832]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
--
Jan 13 03:35:11 PC pipewire[1857]: [E][000000091.766238][core.c:71 core_event_error()] core 0x55a484266fa0: proxy 0x55a4842864f0 id:4: bound:-1 seq:4 res:-2 (No such file or directory) msg:"can't create device: No such file or directory"
Jan 13 03:35:11 PC pipewire[1857]: [E][000000091.766252][media-session.c:1971 core_error()] error id:4 seq:4 res:-2 (No such file or directory): can't create device: No such file or directory
Jan 13 03:35:22 PC pulseaudio[1375]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 13 03:35:22 PC dbus-daemon[686]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jan 13 03:35:27 PC tracker-store[1517]: OK
I have a PCE-AX3000 card and use a freshly installed Debian Bullseye with packages linux-image-5.10.0-1-amd64 and firmware-iwlwifi.

Any ideas about who is the culprit and what to do next to get WiFi immediately upon boot?

Last edited by MdAyq; 01-13-2021 at 03:16 PM. Reason: lshw improved
 
Old 01-13-2021, 01:00 AM   #2
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 16,896
Blog Entries: 10

Rep: Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024
Quote:
Originally Posted by MdAyq View Post
Upon boot, the WiFi won't start. However, after a few minutes I get Internet.
journal entries from that time fram please.

BTW, in your lspci output you have the same ethernet device twice. What's that about?
 
Old 01-13-2021, 08:44 AM   #3
MdAyq
LQ Newbie
 
Registered: Jan 2020
Posts: 17

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ondoho View Post
journal entries from that time fram please.

BTW, in your lspci output you have the same ethernet device twice. What's that about?
The full journal boot log doesn't fit into the message. I'll post an excerpt.

As for the same Ethernet device twice: I have two Ethernet ports. This is (hopefully) unrelated to the issue.

If instead of the above I let NetworkManager handle the interface, the connection starts without problems. (But I'd like to have it without the NetworkManager.)

Last edited by MdAyq; 01-13-2021 at 09:35 AM.
 
Old 01-13-2021, 09:33 AM   #4
MdAyq
LQ Newbie
 
Registered: Jan 2020
Posts: 17

Original Poster
Rep: Reputation: 0
Here a part of the bootlog from now:
Code:
Jan 13 16:09:05 PC kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Jan 13 16:09:05 PC kernel: iwlwifi 0000:b3:00.0 wlp179s0: renamed from wlan0
Jan 13 16:09:05 PC systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 13 16:09:05 PC audit[671]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-soffice" pid=671 comm="apparmor_parser"
Jan 13 16:09:05 PC audit[671]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-soffice//gpg" pid=671 comm="apparmor_parser"
Jan 13 16:09:05 PC systemd[1]: Finished Load AppArmor profiles.
Jan 13 16:09:05 PC systemd[1]: Started Network Time Synchronization.
Jan 13 16:09:05 PC systemd[1]: Reached target System Initialization.
Jan 13 16:09:05 PC systemd[1]: Started ACPI Events Check.
Jan 13 16:09:05 PC systemd[1]: Started CUPS Scheduler.
Jan 13 16:09:05 PC systemd[1]: Started Daily Cleanup of Temporary Directories.
Jan 13 16:09:05 PC systemd[1]: Reached target Paths.
Jan 13 16:09:05 PC systemd[1]: Reached target System Time Set.
Jan 13 16:09:05 PC systemd[1]: Reached target System Time Synchronized.
Jan 13 16:09:05 PC systemd[1]: Started Trigger anacron every hour.
Jan 13 16:09:05 PC systemd[1]: Started Daily apt download activities.
Jan 13 16:09:05 PC systemd[1]: Started Daily apt upgrade and clean activities.
Jan 13 16:09:05 PC systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems.
Jan 13 16:09:05 PC systemd[1]: Started Daily exim4-base housekeeping.
Jan 13 16:09:05 PC systemd[1]: Started Discard unused blocks once a week.
Jan 13 16:09:05 PC systemd[1]: Started Refresh fwupd metadata regularly.
Jan 13 16:09:05 PC systemd[1]: Started Daily rotation of log files.
Jan 13 16:09:05 PC systemd[1]: Started Daily man-db regeneration.
Jan 13 16:09:05 PC systemd[1]: Started Run system activity accounting tool every 10 minutes.
Jan 13 16:09:05 PC systemd[1]: Started Generate summary of yesterday's process accounting.
Jan 13 16:09:05 PC systemd[1]: Reached target Timers.
Jan 13 16:09:05 PC systemd[1]: Listening on ACPID Listen Socket.
Jan 13 16:09:05 PC systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Jan 13 16:09:05 PC systemd[1]: Listening on CUPS Scheduler.
Jan 13 16:09:05 PC systemd[1]: Listening on D-Bus System Message Bus Socket.
Jan 13 16:09:05 PC systemd[1]: Listening on UUID daemon activation socket.
Jan 13 16:09:05 PC systemd[1]: Reached target Sockets.
Jan 13 16:09:05 PC systemd[1]: Reached target Basic System.
Jan 13 16:09:05 PC systemd[1]: Starting Accounts Service...
Jan 13 16:09:05 PC systemd[1]: Started Run anacron jobs.
Jan 13 16:09:05 PC systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Jan 13 16:09:05 PC anacron[683]: Anacron 2.3 started on 2021-01-13
Jan 13 16:09:05 PC systemd[1]: Starting LSB: start and stop cpufreqd...
Jan 13 16:09:05 PC systemd[1]: Started Regular background program processing daemon.
Jan 13 16:09:05 PC anacron[683]: Normal exit (0 jobs run)
Jan 13 16:09:05 PC systemd[1]: Started D-Bus System Message Bus.
Jan 13 16:09:05 PC cron[686]: (CRON) INFO (pidfile fd = 3)
Jan 13 16:09:05 PC cron[686]: (CRON) INFO (Running @reboot jobs)
Jan 13 16:09:05 PC avahi-daemon[684]: Found user 'avahi' (UID 112) and group 'avahi' (GID 119).
Jan 13 16:09:05 PC avahi-daemon[684]: Successfully dropped root privileges.
Jan 13 16:09:05 PC avahi-daemon[684]: avahi-daemon 0.8 starting up.
Jan 13 16:09:05 PC systemd[1]: Starting Network Manager...
Jan 13 16:09:05 PC systemd[1]: Starting Remove Stale Online ext4 Metadata Check Snapshots...
Jan 13 16:09:05 PC systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.
Jan 13 16:09:05 PC systemd[1]: Reached target Login Prompts.
Jan 13 16:09:05 PC systemd[1]: Starting LSB: gpm sysv init script...
Jan 13 16:09:05 PC systemd[1]: Starting Initialize hardware monitoring sensors...
Jan 13 16:09:05 PC systemd[1]: Starting LSB: Load kernel modules needed to enable cpufreq scaling...
Jan 13 16:09:05 PC systemd[1]: Starting Authorization Manager...
Jan 13 16:09:05 PC systemd[1]: Starting System Logging Service...
Jan 13 16:09:05 PC systemd[1]: Starting Self Monitoring and Reporting Technology (SMART) Daemon...
Jan 13 16:09:05 PC systemd[1]: Starting Switcheroo Control Proxy service...
Jan 13 16:09:05 PC systemd[1]: Starting Resets System Activity Logs...
Jan 13 16:09:05 PC systemd[1]: Starting User Login Management...
Jan 13 16:09:05 PC systemd[1]: Starting Disk Manager...
Jan 13 16:09:05 PC systemd[1]: Starting WPA supplicant...
Jan 13 16:09:05 PC systemd[1]: anacron.service: Succeeded.
Jan 13 16:09:05 PC rsyslogd[701]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.2012.0]
Jan 13 16:09:05 PC rsyslogd[701]: [origin software="rsyslogd" swVersion="8.2012.0" x-pid="701" x-info="https://www.rsyslog.com"] start
Jan 13 16:09:05 PC systemd[1]: Started System Logging Service.
Jan 13 16:09:05 PC systemd[1]: Finished Resets System Activity Logs.
Jan 13 16:09:05 PC avahi-daemon[684]: Successfully called chroot().
Jan 13 16:09:05 PC avahi-daemon[684]: Successfully dropped remaining capabilities.
Jan 13 16:09:05 PC avahi-daemon[684]: No service file found in /etc/avahi/services.
Jan 13 16:09:05 PC avahi-daemon[684]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Jan 13 16:09:05 PC avahi-daemon[684]: New relevant interface lo.IPv6 for mDNS.
Jan 13 16:09:05 PC avahi-daemon[684]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jan 13 16:09:05 PC avahi-daemon[684]: New relevant interface lo.IPv4 for mDNS.
Jan 13 16:09:05 PC avahi-daemon[684]: Network interface enumeration completed.
Jan 13 16:09:05 PC avahi-daemon[684]: Registering new address record for ::1 on lo.*.
Jan 13 16:09:05 PC avahi-daemon[684]: Registering new address record for 127.0.0.1 on lo.IPv4.
Jan 13 16:09:05 PC systemd[1]: e2scrub_reap.service: Succeeded.
Jan 13 16:09:05 PC systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Jan 13 16:09:05 PC polkitd[698]: started daemon version 0.105 using authority implementation `local' version `0.105'
Jan 13 16:09:05 PC udisksd[708]: udisks daemon version 2.9.1 starting
Jan 13 16:09:05 PC accounts-daemon[682]: started daemon version 0.6.55
Jan 13 16:09:05 PC wpa_supplicant[710]: Successfully initialized wpa_supplicant
Jan 13 16:09:05 PC systemd[1]: Started Authorization Manager.
Jan 13 16:09:05 PC systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jan 13 16:09:05 PC systemd[1]: Started Switcheroo Control Proxy service.
Jan 13 16:09:05 PC systemd[1]: Started Accounts Service.
Jan 13 16:09:05 PC systemd[1]: Started WPA supplicant.
Jan 13 16:09:05 PC systemd[1]: Starting Modem Manager...
Jan 13 16:09:05 PC systemd-udevd[433]: Using default interface naming scheme 'v247'.
Jan 13 16:09:05 PC systemd-udevd[433]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 13 16:09:05 PC systemd[1]: Condition check resulted in Manage Sound Card State (restore and store) being skipped.
Jan 13 16:09:05 PC systemd[1]: Starting Save/Restore Sound Card State...
Jan 13 16:09:05 PC systemd[1]: Found device Wi-Fi 6 AX200.
Jan 13 16:09:05 PC smartd[702]: smartd 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-1-amd64] (local build)
Jan 13 16:09:05 PC smartd[702]: Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Jan 13 16:09:05 PC smartd[702]: Opened configuration file /etc/smartd.conf
Jan 13 16:09:05 PC smartd[702]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Jan 13 16:09:05 PC smartd[702]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jan 13 16:09:05 PC systemd[1]: Started ifup for wlp179s0.
Jan 13 16:09:05 PC systemd[1]: Finished Save/Restore Sound Card State.
Jan 13 16:09:05 PC systemd[1]: Reached target Sound Card.
Jan 13 16:09:05 PC smartd[702]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Jan 13 16:09:05 PC smartd[702]: Device: /dev/sda [SAT], opened
Jan 13 16:09:05 PC smartd[702]: Device: /dev/sda [SAT], WDC WD20EFAX-68FB5N0, S/N:WD-WX82A30EH19E, WWN:5-0014ee-2128f4c30, FW:82.00A82, 2.00 TB
Jan 13 16:09:05 PC udisksd[708]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.3916] NetworkManager (version 1.28.0) is starting... (for the first time)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.3921] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Jan 13 16:09:05 PC udisksd[708]: Failed to load the 'mdraid' libblockdev plugin
Jan 13 16:09:05 PC smartd[702]: Device: /dev/sda [SAT], found in smartd database: Western Digital Red (SMR)
Jan 13 16:09:05 PC systemd[1]: Started Network Manager.
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.3939] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jan 13 16:09:05 PC systemd[1]: Starting Network Manager Wait Online...
Jan 13 16:09:05 PC systemd-logind[707]: New seat seat0.
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.3983] manager[0x55f6907c3010]: monitoring kernel firmware directory '/lib/firmware'.
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.3983] monitoring ifupdown state file '/run/network/ifstate'.
Jan 13 16:09:05 PC dbus-daemon[688]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.8' (uid=0 pid=692 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 13 16:09:05 PC systemd[1]: Starting Hostname Service...
Jan 13 16:09:05 PC systemd-logind[707]: Watching system buttons on /dev/input/event2 (Power Button)
Jan 13 16:09:05 PC systemd-logind[707]: Watching system buttons on /dev/input/event1 (Power Button)
Jan 13 16:09:05 PC systemd-logind[707]: Watching system buttons on /dev/input/event0 (Sleep Button)
Jan 13 16:09:05 PC systemd-logind[707]: Watching system buttons on /dev/input/event4 (LITEON Technology USB Keyboard)
Jan 13 16:09:05 PC systemd[1]: Started User Login Management.
Jan 13 16:09:05 PC dhclient[776]: Internet Systems Consortium DHCP Client 4.4.1
Jan 13 16:09:05 PC sh[776]: Internet Systems Consortium DHCP Client 4.4.1
Jan 13 16:09:05 PC sh[776]: Copyright 2004-2018 Internet Systems Consortium.
Jan 13 16:09:05 PC sh[776]: All rights reserved.
Jan 13 16:09:05 PC sh[776]: For info, please visit https://www.isc.org/software/dhcp/
Jan 13 16:09:05 PC dhclient[776]: Copyright 2004-2018 Internet Systems Consortium.
Jan 13 16:09:05 PC dhclient[776]: All rights reserved.
Jan 13 16:09:05 PC dhclient[776]: For info, please visit https://www.isc.org/software/dhcp/
Jan 13 16:09:05 PC dhclient[776]: 
Jan 13 16:09:05 PC ModemManager[736]: <info>  ModemManager (version 1.14.8) starting in system bus...
Jan 13 16:09:05 PC systemd[1]: Started Modem Manager.
Jan 13 16:09:05 PC smartd[702]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Jan 13 16:09:05 PC smartd[702]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD20EFAX_68FB5N0-WD_WX82A30EH19E.ata.state
Jan 13 16:09:05 PC smartd[702]: Device: /dev/nvme0, opened
Jan 13 16:09:05 PC smartd[702]: Device: /dev/nvme0, Samsung SSD 970 EVO 1TB, S/N:S5H9NS0NA99371X, FW:2B2QEXE7, 1.00 TB
Jan 13 16:09:05 PC smartd[702]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list.
Jan 13 16:09:05 PC smartd[702]: Device: /dev/nvme0, state read from /var/lib/smartmontools/smartd.Samsung_SSD_970_EVO_1TB-S5H9NS0NA99371X.nvme.state
Jan 13 16:09:05 PC smartd[702]: Monitoring 1 ATA/SATA, 0 SCSI/SAS and 1 NVMe devices
Jan 13 16:09:05 PC gpm[695]: Starting mouse interface server: gpm.
Jan 13 16:09:05 PC systemd[1]: Started LSB: gpm sysv init script.
Jan 13 16:09:05 PC /usr/sbin/gpm[818]: *** info [daemon/startup.c(131)]:
Jan 13 16:09:05 PC /usr/sbin/gpm[818]: Started gpm successfully. Entered daemon mode.
Jan 13 16:09:05 PC dbus-daemon[688]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 13 16:09:05 PC systemd[1]: Started Hostname Service.
Jan 13 16:09:05 PC smartd[702]: Device: /dev/nvme0, number of Error Log entries increased from 311 to 312
Jan 13 16:09:05 PC smartd[702]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD20EFAX_68FB5N0-WD_WX82A30EH19E.ata.state
Jan 13 16:09:05 PC smartd[702]: Device: /dev/nvme0, state written to /var/lib/smartmontools/smartd.Samsung_SSD_970_EVO_1TB-S5H9NS0NA99371X.nvme.state
Jan 13 16:09:05 PC systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5097] hostname: hostname: using hostnamed
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5097] hostname: hostname changed from (none) to "PC"
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5103] dns-mgr[0x55f69079c240]: init: dns=default,systemd-resolved rc-manager=symlink (auto)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5113] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5115] manager[0x55f6907c3010]: rfkill: Wi-Fi hardware radio set enabled
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5115] manager[0x55f6907c3010]: rfkill: WWAN hardware radio set enabled
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5179] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-team.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5213] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-wwan.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5232] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-bluetooth.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5237] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-adsl.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5248] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-wifi.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5252] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5254] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5255] manager: Networking is enabled by state file
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5256] dhcp-init: Using DHCP client 'internal'
Jan 13 16:09:05 PC dbus-daemon[688]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=692 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5266] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-settings-plugin-ifupdown.so")
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5266] settings: Loaded settings plugin: keyfile (internal)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5266] ifupdown: management mode: unmanaged
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5267] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5267] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5268] ifupdown:       interface-parser: parsing file /etc/network/interfaces.d/setup
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5268] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces.d/setup
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5268] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5273] ifupdown: guessed connection type (wlp179s0) = 802-3-ethernet
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5282] ifupdown: guessed connection type (wlp179s0) = 802-11-wireless
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5282] ifupdown: update wireless settings (wlp179s0).
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5284] ifupdown: setting wpa ssid = 9
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5284] ifupdown: update wireless security settings (wlp179s0).
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5285] ifupdown: setting wpa security key: psk=<omitted>
Jan 13 16:09:05 PC systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 13 16:09:05 PC dbus-daemon[688]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 13 16:09:05 PC systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 13 16:09:05 PC kernel: intel_rapl_common: Found RAPL domain package
Jan 13 16:09:05 PC cpufreqd[685]: Starting CPU Frequency daemon: cpufreqd.
Jan 13 16:09:05 PC systemd[1]: Started LSB: start and stop cpufreqd.
Jan 13 16:09:05 PC systemd[1]: Started ACPI event daemon.
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6064] device (lo): carrier: link connected
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6066] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6072] manager: (enp6s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6081] settings: (enp6s0): created default wired connection 'Kabelgebundene Verbindung 1'
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6084] device (enp6s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 13 16:09:05 PC sensors[712]: iwlwifi_1-virtual-0
Jan 13 16:09:05 PC sensors[712]: Adapter: Virtual device
Jan 13 16:09:05 PC sensors[712]: temp1:            N/A
Jan 13 16:09:05 PC sensors[712]: nvme-pci-0900
Jan 13 16:09:05 PC sensors[712]: Adapter: PCI adapter
Jan 13 16:09:05 PC sensors[712]: Composite:    +44.9C  (low  = -273.1C, high = +84.8C)
Jan 13 16:09:05 PC sensors[712]:                        (crit = +84.8C)
Jan 13 16:09:05 PC sensors[712]: Sensor 1:     +44.9C  (low  = -273.1C, high = +65261.8C)
Jan 13 16:09:05 PC sensors[712]: Sensor 2:     +52.9C  (low  = -273.1C, high = +65261.8C)
Jan 13 16:09:05 PC sensors[712]: coretemp-isa-0000
Jan 13 16:09:05 PC sensors[712]: Adapter: ISA adapter
Jan 13 16:09:05 PC sensors[712]: Package id 0:  +55.0C  (high = +90.0C, crit = +100.0C)
Jan 13 16:09:05 PC sensors[712]: Core 0:        +45.0C  (high = +90.0C, crit = +100.0C)
Jan 13 16:09:05 PC sensors[712]: Core 1:        +45.0C  (high = +90.0C, crit = +100.0C)
Jan 13 16:09:05 PC sensors[712]: Core 2:        +44.0C  (high = +90.0C, crit = +100.0C)
Jan 13 16:09:05 PC sensors[712]: Core 3:        +48.0C  (high = +90.0C, crit = +100.0C)
Jan 13 16:09:05 PC sensors[712]: Core 4:        +55.0C  (high = +90.0C, crit = +100.0C)
Jan 13 16:09:05 PC sensors[712]: Core 5:        +48.0C  (high = +90.0C, crit = +100.0C)
Jan 13 16:09:05 PC sensors[712]: nouveau-pci-6500
Jan 13 16:09:05 PC sensors[712]: Adapter: PCI adapter
Jan 13 16:09:05 PC sensors[712]: fan1:           0 RPM
Jan 13 16:09:05 PC sensors[712]: temp1:        +33.0C  (high = +95.0C, hyst =  +3.0C)
Jan 13 16:09:05 PC sensors[712]:                        (crit = +105.0C, hyst =  +5.0C)
Jan 13 16:09:05 PC sensors[712]:                        (emerg = +135.0C, hyst =  +5.0C)
Jan 13 16:09:05 PC systemd[1]: Finished Initialize hardware monitoring sensors.
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6352] manager: (enp7s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6361] settings: (enp7s0): created default wired connection 'Kabelgebundene Verbindung 2'
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6363] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6624] device (wlp179s0): driver supports Access Point (AP) mode
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6627] manager: (wlp179s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/4)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6631] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6654] modem-manager: ModemManager available
Jan 13 16:09:05 PC systemd[1]: Started Disk Manager.
Jan 13 16:09:05 PC udisksd[708]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jan 13 16:09:05 PC dhclient[776]: Listening on LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC sh[776]: Listening on LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC sh[776]: Sending on   LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC sh[776]: Sending on   Socket/fallback
Jan 13 16:09:05 PC sh[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
Jan 13 16:09:05 PC dhclient[776]: Sending on   LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC dhclient[776]: Sending on   Socket/fallback
Jan 13 16:09:05 PC dhclient[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
Jan 13 16:09:05 PC kernel: cx25840 22-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
Jan 13 16:09:05 PC loadcpufreq[697]: Loading cpufreq kernel modules...done (acpi-cpufreq).
Jan 13 16:09:05 PC systemd[1]: Started LSB: Load kernel modules needed to enable cpufreq scaling.
Jan 13 16:09:05 PC systemd[1]: Starting LSB: set CPUFreq kernel parameters...
Jan 13 16:09:05 PC cpufrequtils[873]: CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...done.
Jan 13 16:09:05 PC systemd[1]: Started LSB: set CPUFreq kernel parameters.
Jan 13 16:09:06 PC kernel: cx23885: cx23885[0]: registered device video2 [v4l2]
Jan 13 16:09:06 PC kernel: cx23885: cx23885[0]: registered device vbi0
Jan 13 16:09:06 PC kernel: cx23885: cx23885[0]: alsa: registered ALSA audio device
Jan 13 16:09:06 PC kernel: cx23885: cx23885_dvb_register() allocating 1 frontend(s)
Jan 13 16:09:06 PC kernel: cx23885: cx23885[0]: cx23885 based dvb card
Jan 13 16:09:06 PC kernel: i2c i2c-20: Added multiplexed i2c bus 23
Jan 13 16:09:06 PC kernel: a8293 20-000b: Allegro A8293 SEC successfully attached
Jan 13 16:09:06 PC acpid[836]: starting up with netlink and the input layer
Jan 13 16:09:06 PC acpid[836]: 0 rules loaded
Jan 13 16:09:06 PC acpid[836]: waiting for events: event logging is off
Jan 13 16:09:06 PC acpid[836]: client connected from 828[0:0]
Jan 13 16:09:06 PC acpid[836]: 1 client rule loaded
Jan 13 16:09:06 PC kernel: m88rs6000t 23-0021: chip_id=64
Jan 13 16:09:06 PC kernel: m88rs6000t 23-0021: Montage M88RS6000 internal tuner successfully identified
Jan 13 16:09:06 PC kernel: dvbdev: DVB: registering new adapter (cx23885[0])
Jan 13 16:09:06 PC kernel: cx23885 0000:08:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology M88RS6000)...
Jan 13 16:09:06 PC kernel: cx23885: cx23885_dvb_register() allocating 1 frontend(s)
Jan 13 16:09:06 PC kernel: cx23885: cx23885[0]: cx23885 based dvb card
Jan 13 16:09:06 PC kernel: i2c i2c-20: Added multiplexed i2c bus 24
Jan 13 16:09:06 PC kernel: si2168 20-0064: Silicon Labs Si2168-B40 successfully identified
Jan 13 16:09:06 PC kernel: si2168 20-0064: firmware version: B 4.0.2
Jan 13 16:09:06 PC kernel: si2157 21-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
Jan 13 16:09:06 PC kernel: dvbdev: DVB: registering new adapter (cx23885[0])
Jan 13 16:09:06 PC kernel: cx23885 0000:08:00.0: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)...
Jan 13 16:09:06 PC kernel: cx23885: cx23885_dev_checkrevision() Hardware revision = 0xd0
Jan 13 16:09:06 PC kernel: cx23885: cx23885[0]/0: found at 0000:08:00.0, rev: 4, irq: 16, latency: 0, mmio: 0x90200000
Jan 13 16:09:06 PC avahi-daemon[684]: Server startup complete. Host name is PC.local. Local service cookie is 1738663216.
Jan 13 16:09:06 PC systemd[1]: Finished Helper to synchronize boot up for ifupdown.
Jan 13 16:09:06 PC systemd[1]: Starting Raise network interfaces...
Jan 13 16:09:06 PC ifup[890]: ifup: waiting for lock on /run/network/ifstate.wlp179s0
Jan 13 16:09:07 PC ModemManager[736]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0': not supported by any plugin
Jan 13 16:09:07 PC ModemManager[736]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0': not supported by any plugin
Jan 13 16:09:07 PC ModemManager[736]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0': not supported by any plugin
Jan 13 16:09:10 PC systemd[1]: systemd-rfkill.service: Succeeded.
Jan 13 16:09:11 PC NetworkManager[692]: <info>  [1610550551.6623] manager: startup complete
Jan 13 16:09:11 PC systemd[1]: Finished Network Manager Wait Online.
Jan 13 16:09:12 PC dhclient[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
Jan 13 16:09:12 PC sh[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
Jan 13 16:09:15 PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 13 16:09:33 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 4
Jan 13 16:09:33 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 4
Jan 13 16:09:35 PC systemd[1]: systemd-fsckd.service: Succeeded.
Jan 13 16:09:35 PC systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 13 16:09:37 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 5
Jan 13 16:09:37 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 5
Jan 13 16:09:42 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
Jan 13 16:09:42 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
Jan 13 16:09:54 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
Jan 13 16:09:54 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
Jan 13 16:10:00 PC systemd[1]: Starting system activity accounting tool...
Jan 13 16:10:00 PC systemd[1]: sysstat-collect.service: Succeeded.
Jan 13 16:10:00 PC systemd[1]: Finished system activity accounting tool.
Jan 13 16:10:06 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:06 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:20 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:20 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:34 PC dhclient[776]: No DHCPOFFERS received.
Jan 13 16:10:34 PC sh[776]: No DHCPOFFERS received.
Jan 13 16:10:34 PC sh[776]: Trying recorded lease 192.168.1.229
Jan 13 16:10:34 PC dhclient[776]: Trying recorded lease 192.168.1.229
Jan 13 16:10:34 PC avahi-daemon[684]: Joining mDNS multicast group on interface wlp179s0.IPv4 with address 192.168.1.229.
Jan 13 16:10:34 PC avahi-daemon[684]: New relevant interface wlp179s0.IPv4 for mDNS.
Jan 13 16:10:34 PC avahi-daemon[684]: Registering new address record for 192.168.1.229 on wlp179s0.IPv4.
Jan 13 16:10:37 PC sh[940]: PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
Jan 13 16:10:37 PC sh[940]: --- 192.168.1.1 ping statistics ---
Jan 13 16:10:37 PC sh[940]: 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
Jan 13 16:10:37 PC avahi-daemon[684]: Withdrawing address record for 192.168.1.229 on wlp179s0.
Jan 13 16:10:37 PC avahi-daemon[684]: Leaving mDNS multicast group on interface wlp179s0.IPv4 with address 192.168.1.229.
Jan 13 16:10:37 PC avahi-daemon[684]: Interface wlp179s0.IPv4 no longer relevant for mDNS.
Jan 13 16:10:37 PC avahi-autoipd(wlp179s0)[945]: Found user 'avahi-autoipd' (UID 108) and group 'avahi-autoipd' (GID 117).
Jan 13 16:10:37 PC avahi-autoipd(wlp179s0)[945]: Successfully called chroot().
Jan 13 16:10:37 PC avahi-autoipd(wlp179s0)[945]: Successfully dropped root privileges.
Jan 13 16:10:37 PC avahi-autoipd(wlp179s0)[945]: Starting with address 169.254.13.68
Jan 13 16:10:43 PC avahi-autoipd(wlp179s0)[945]: Callout BIND, address 169.254.13.68 on interface wlp179s0
Jan 13 16:10:43 PC avahi-daemon[684]: Joining mDNS multicast group on interface wlp179s0.IPv4 with address 169.254.13.68.
Jan 13 16:10:43 PC avahi-daemon[684]: New relevant interface wlp179s0.IPv4 for mDNS.
Jan 13 16:10:43 PC avahi-daemon[684]: Registering new address record for 169.254.13.68 on wlp179s0.IPv4.
Jan 13 16:10:47 PC avahi-autoipd(wlp179s0)[945]: Successfully claimed IP address 169.254.13.68
Jan 13 16:10:47 PC dhclient[776]: No working leases in persistent database - sleeping.
Jan 13 16:10:47 PC sh[776]: No working leases in persistent database - sleeping.
Jan 13 16:10:47 PC root[957]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Jan 13 16:10:47 PC wpa_supplicant[991]: Successfully initialized wpa_supplicant
Jan 13 16:10:47 PC sh[1034]: wlp179s0=wlp179s0
Jan 13 16:10:47 PC systemd[1]: Finished Raise network interfaces.

Last edited by MdAyq; 01-13-2021 at 12:51 PM.
 
Old 01-13-2021, 12:08 PM   #5
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 16,896
Blog Entries: 10

Rep: Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024
Quote:
Originally Posted by MdAyq View Post
The full journal boot log doesn't fit into the message. I'll post an excerpt.
I didn't say "full", I said from the relevant time frame.
Please indicate that timeframe in your output.
 
Old 01-13-2021, 12:45 PM   #6
MdAyq
LQ Newbie
 
Registered: Jan 2020
Posts: 17

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ondoho View Post
I didn't say "full", I said from the relevant time frame.
Please indicate that timeframe in your output.
I am not quite sure which stuff is relevant. The except started at the first occurrence of "DHCP" and lasts till slightly after the fatal “No DHCPOFFERS received.” I believe it to be roughly relevant.

At the time the log was taken no Internet connection existed (“ping www.google.com” did not succeed). I've just now prepended as many lines to the top as I could without breaking the limit of the messages size.

Last edited by MdAyq; 01-13-2021 at 12:52 PM.
 
Old 01-13-2021, 01:44 PM   #7
boughtonp
Senior Member
 
Registered: Feb 2007
Location: UK
Distribution: Debian
Posts: 1,144

Rep: Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959Reputation: 959
Quote:
Originally Posted by MdAyq View Post
I've just now prepended as many lines to the top as I could without breaking the limit of the messages size.
This is what the attachment system is for - create a copy of the file with a .log or .txt extension, and you can upload files upto 256KB in size, which should be plenty.

(Speaking generally; there may or not be enough context in what you've now posted, but you'll need to wait for someone else to confirm that.)

 
Old 01-13-2021, 02:00 PM   #8
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 16,896
Blog Entries: 10

Rep: Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024
Cut out as instructed, cleaned up a little:
Code:
Jan 13 16:09:05 PC dhclient[776]: Internet Systems Consortium DHCP Client 4.4.1
Jan 13 16:09:05 PC sh[776]: Internet Systems Consortium DHCP Client 4.4.1
Jan 13 16:09:05 PC sh[776]: Copyright 2004-2018 Internet Systems Consortium.
Jan 13 16:09:05 PC sh[776]: All rights reserved.
Jan 13 16:09:05 PC sh[776]: For info, please visit https://www.isc.org/software/dhcp/
Jan 13 16:09:05 PC dhclient[776]: Copyright 2004-2018 Internet Systems Consortium.
Jan 13 16:09:05 PC dhclient[776]: All rights reserved.
Jan 13 16:09:05 PC dhclient[776]: For info, please visit https://www.isc.org/software/dhcp/
Jan 13 16:09:05 PC dhclient[776]: 
Jan 13 16:09:05 PC ModemManager[736]: <info>  ModemManager (version 1.14.8) starting in system bus...
Jan 13 16:09:05 PC systemd[1]: Started Modem Manager.
...
Jan 13 16:09:05 PC dbus-daemon[688]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 13 16:09:05 PC systemd[1]: Started Hostname Service.
...
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5097] hostname: hostname: using hostnamed
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5097] hostname: hostname changed from (none) to "PC"
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5103] dns-mgr[0x55f69079c240]: init: dns=default,systemd-resolved rc-manager=symlink (auto)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5113] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5115] manager[0x55f6907c3010]: rfkill: Wi-Fi hardware radio set enabled
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5115] manager[0x55f6907c3010]: rfkill: WWAN hardware radio set enabled
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5179] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-team.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5213] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-wwan.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5232] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-bluetooth.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5237] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-adsl.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5248] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-device-plugin-wifi.so)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5252] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5254] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5255] manager: Networking is enabled by state file
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5256] dhcp-init: Using DHCP client 'internal'
Jan 13 16:09:05 PC dbus-daemon[688]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=692 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5266] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.28.0/libnm-settings-plugin-ifupdown.so")
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5266] settings: Loaded settings plugin: keyfile (internal)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5266] ifupdown: management mode: unmanaged
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5267] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5267] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5268] ifupdown:       interface-parser: parsing file /etc/network/interfaces.d/setup
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5268] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces.d/setup
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5268] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5273] ifupdown: guessed connection type (wlp179s0) = 802-3-ethernet
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5282] ifupdown: guessed connection type (wlp179s0) = 802-11-wireless
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5282] ifupdown: update wireless settings (wlp179s0).
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5284] ifupdown: setting wpa ssid = 9
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5284] ifupdown: update wireless security settings (wlp179s0).
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.5285] ifupdown: setting wpa security key: psk=<omitted>
Jan 13 16:09:05 PC systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 13 16:09:05 PC dbus-daemon[688]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 13 16:09:05 PC systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 13 16:09:05 PC kernel: intel_rapl_common: Found RAPL domain package
...
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6064] device (lo): carrier: link connected
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6066] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6072] manager: (enp6s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6081] settings: (enp6s0): created default wired connection 'Kabelgebundene Verbindung 1'
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6084] device (enp6s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 13 16:09:05 PC sensors[712]: iwlwifi_1-virtual-0
Jan 13 16:09:05 PC sensors[712]: Adapter: Virtual device
Jan 13 16:09:05 PC sensors[712]: temp1:            N/A
...
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6352] manager: (enp7s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6361] settings: (enp7s0): created default wired connection 'Kabelgebundene Verbindung 2'
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6363] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6624] device (wlp179s0): driver supports Access Point (AP) mode
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6627] manager: (wlp179s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/4)
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6631] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 13 16:09:05 PC NetworkManager[692]: <info>  [1610550545.6654] modem-manager: ModemManager available
...
Jan 13 16:09:05 PC dhclient[776]: Listening on LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC sh[776]: Listening on LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC sh[776]: Sending on   LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC sh[776]: Sending on   Socket/fallback
Jan 13 16:09:05 PC sh[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
Jan 13 16:09:05 PC dhclient[776]: Sending on   LPF/wlp179s0/c8:e2:65:ff:9c:40
Jan 13 16:09:05 PC dhclient[776]: Sending on   Socket/fallback
Jan 13 16:09:05 PC dhclient[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
...
Jan 13 16:09:06 PC acpid[836]: starting up with netlink and the input layer
Jan 13 16:09:06 PC acpid[836]: 0 rules loaded
Jan 13 16:09:06 PC acpid[836]: waiting for events: event logging is off
Jan 13 16:09:06 PC acpid[836]: client connected from 828[0:0]
Jan 13 16:09:06 PC acpid[836]: 1 client rule loaded
...
Jan 13 16:09:06 PC avahi-daemon[684]: Server startup complete. Host name is PC.local. Local service cookie is 1738663216.
Jan 13 16:09:06 PC systemd[1]: Finished Helper to synchronize boot up for ifupdown.
Jan 13 16:09:06 PC systemd[1]: Starting Raise network interfaces...
Jan 13 16:09:06 PC ifup[890]: ifup: waiting for lock on /run/network/ifstate.wlp179s0
Jan 13 16:09:07 PC ModemManager[736]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0': not supported by any plugin
Jan 13 16:09:07 PC ModemManager[736]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0': not supported by any plugin
Jan 13 16:09:07 PC ModemManager[736]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:b2/0000:b2:00.0/0000:b3:00.0': not supported by any plugin
Jan 13 16:09:10 PC systemd[1]: systemd-rfkill.service: Succeeded.
Jan 13 16:09:11 PC NetworkManager[692]: <info>  [1610550551.6623] manager: startup complete
Jan 13 16:09:11 PC systemd[1]: Finished Network Manager Wait Online.
Jan 13 16:09:12 PC dhclient[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
Jan 13 16:09:12 PC sh[776]: DHCPREQUEST for 192.168.1.229 on wlp179s0 to 255.255.255.255 port 67
Jan 13 16:09:15 PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 13 16:09:33 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 4
Jan 13 16:09:33 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 4
Jan 13 16:09:35 PC systemd[1]: systemd-fsckd.service: Succeeded.
Jan 13 16:09:35 PC systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 13 16:09:37 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 5
Jan 13 16:09:37 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 5
Jan 13 16:09:42 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
Jan 13 16:09:42 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
Jan 13 16:09:54 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
Jan 13 16:09:54 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 12
...
Jan 13 16:10:06 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:06 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:20 PC dhclient[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:20 PC sh[776]: DHCPDISCOVER on wlp179s0 to 255.255.255.255 port 67 interval 14
Jan 13 16:10:34 PC dhclient[776]: No DHCPOFFERS received.
Jan 13 16:10:34 PC sh[776]: No DHCPOFFERS received.
Jan 13 16:10:34 PC sh[776]: Trying recorded lease 192.168.1.229
Jan 13 16:10:34 PC dhclient[776]: Trying recorded lease 192.168.1.229
Jan 13 16:10:34 PC avahi-daemon[684]: Joining mDNS multicast group on interface wlp179s0.IPv4 with address 192.168.1.229.
Jan 13 16:10:34 PC avahi-daemon[684]: New relevant interface wlp179s0.IPv4 for mDNS.
Jan 13 16:10:34 PC avahi-daemon[684]: Registering new address record for 192.168.1.229 on wlp179s0.IPv4.
Jan 13 16:10:37 PC sh[940]: PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
Jan 13 16:10:37 PC sh[940]: --- 192.168.1.1 ping statistics ---
Jan 13 16:10:37 PC sh[940]: 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
So the system boots at 16:09:05?
All this takes 1 m 30 s - hardly "after a few minutes".
Be that as it may, I can see what you're refering to, mostly everything that contains DHCP in capitals. But I'm not familiar with what it says.
But there's a few things that look positively weird to me.
A service called "sh"? Weird. And it seems to be mirroring everything dhclient does. And there's also a ifupdown service. None of those 3 exist on any of my machines.
I suspect your network configuration is very old, from a time before Debian fully switched to systemd? A major cleanup might be required. If you decide to keep NetworkManager, find a good installation tutorial, it should tell you what you need to remove/disable.
 
Old 01-13-2021, 02:14 PM   #9
MdAyq
LQ Newbie
 
Registered: Jan 2020
Posts: 17

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ondoho View Post
All this takes 1 m 30 s - hardly "after a few minutes".
The system starts booting around 16:09:04; aе 16:10:56 I was able to login at tty2 and then issue
Code:
journalctl -b
, from which you see an excerpt. Internet did not work at that time; I got connection around 4-5 minutes later or so.
Concerning „I suspect your network configuration is very old“: on the contrary, I performed a clean installation this year using the iso image from https://cdimage.debian.org/cdimage/u.../amd64/iso-dvd.

Last edited by MdAyq; 01-13-2021 at 03:14 PM.
 
Old 01-13-2021, 02:26 PM   #10
MdAyq
LQ Newbie
 
Registered: Jan 2020
Posts: 17

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by boughtonp View Post
This is what the attachment system is for
Ah, I completely missed this; thx! See the attachments.
Attached Files
File Type: log dmesg.log (109.5 KB, 3 views)
File Type: log iw_dev_wlp179s0_info.log (293 Bytes, 2 views)
File Type: log journalctl-b.log (199.9 KB, 5 views)
File Type: log lshw.log (2.0 KB, 2 views)
 
Old 01-14-2021, 11:50 PM   #11
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 16,896
Blog Entries: 10

Rep: Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024
Quote:
Originally Posted by MdAyq View Post
...from which you see an excerpt. Internet did not work at that time; I got connection around 4-5 minutes later or so.
I specifically asked to show us logs from the relevant time frame, according to your title: from boot until wifi starts working. So what we discussed still isn't the relevant timeframe.

Anyhow, I gave partial advice, I guess that still applies.
 
Old 01-15-2021, 11:55 AM   #12
cynwulf
Senior Member
 
Registered: Apr 2005
Posts: 2,594
Blog Entries: 7

Rep: Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064Reputation: 2064
I looks like you're attempting to configure the interface in multiple ways. Choose one method only. You may need to disable the networkmanager service, if you want to configure via the interfaces file. There is another duplicate in /etc/network/interfaces.d/ as well, which coukd be problematic.

The sh in the logs may indicate a script calling dhclient - which again points to multiple methods being used?

What guides/docs have you followed...?
 
Old 01-15-2021, 01:47 PM   #13
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 16,896
Blog Entries: 10

Rep: Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024Reputation: 5024
^ What I wrote in post #8 essentially...
 
Old 01-16-2021, 07:39 AM   #14
MdAyq
LQ Newbie
 
Registered: Jan 2020
Posts: 17

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by ondoho View Post
... until wifi starts working.
The time when WiFi starts working is mostly irrelevant. What is much more relevant is the time when WiFi attempts to start working but fails. I attached a larger log from today. The boot starts at around 12:52:51, the first attempt to connect fails IMHO at around 12:53:53, and the second attempt to connect succeeds IMHO at around 12:57:43.

As for the Network Manager, the line managed=false in
Code:
$ cat /etc/NetworkManager/NetworkManager.conf 
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false
ensures IMHO that the Network Manager does not interfere if we believe the manpage of NetworkManager.conf: “managed [...] If set to false, then any interface listed in /etc/network/interfaces will be ignored by NetworkManager.” As for the duplication of dhclient messages by the process sh (or the other way round), I really don't know what it means and how it is supposed to be.

What I originally had was a cleanly installed Debian bullseye, in which WiFi was used for the installation. After the installation, the symptoms were exactly the same as now: WiFi started working only after 4-5 minutes after boot. You have to believe me on that. (Alas, I cannot reproduce /etc/network/interfaces from that time from my memory precisely.)
Quote:
Originally Posted by cynwulf View Post
What guides/docs have you followed...?
After that, I tried to improve /etc/network/interfaces according to its manpage, but this changed nothing on the symptoms. (Of course, removing the references to wlp179s0 from /etc/network/interfaces made NetworkManager give us WiFi, but that's not what we try to do here in this very post. Here, we try to do it without NetworkManager.)

Quote:
Originally Posted by cynwulf View Post
You may need to disable the networkmanager service
How to do it in a way that survives reboots?

Quote:
Originally Posted by cynwulf View Post
There is another duplicate in /etc/network/interfaces.d/ as well, which coukd be problematic.
What exactly needs to be changed in /etc/network/interfaces and /etc/network/interfaces.d ?
Attached Files
File Type: log journalctl-b.log (194.9 KB, 1 views)

Last edited by MdAyq; 01-23-2021 at 04:51 AM.
 
  


Reply

Tags
debian, network confguration, network connectivity, wifi problem


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Power options: Selecting Never and it does not work, 10 minutes later must sign in again. Zandak411 Linux Mint 1 07-15-2016 06:05 AM
[SOLVED] wifi fails after a few minutes if I cold-boot into Slack pzognar Slackware 9 09-06-2015 11:11 AM
[SOLVED] X takes 1.5 minutes to start xterm and 3.5 minutes to start GNOME gregorian Linux - Newbie 16 12-25-2009 05:56 AM
LXer: Save a Web page for later with Read It Later extension LXer Syndicated Linux News 0 09-29-2008 11:50 AM
Installed fedora 9 and 10 minutes later problems jordyberg Linux - Newbie 2 06-16-2008 05:03 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 11:15 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration