Page 1 of 4 123 ... LastLast
Results 1 to 10 of 34

Thread: Wireless device not detected after kernel 5.12.12 update

  1. #1
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Wireless device not detected after kernel 5.12.12 update

    The wireless hw on this PC is not detected after updating from Kernel: 5.12.12-1-default x86_64

    No problems found on HP laptop with latest kernels

    Also on this PC Logilink usb wireless hw is detected and functions correctly


    details as follows,
    Code:
    nvme-120GB 2021-07-11 10:42 ~
    >... sudo lsusb
    Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 002: ID 04e8:341b Samsung Electronics Co., Ltd SCX-4200 series
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
    Bus 001 Device 003: ID 0250:3412 Genius Wireless Mouse
    Bus 001 Device 005: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
    Bus 001 Device 007: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    nvme-120GB 2021-07-11 10:45 ~
    
    information extracted from inxi -F
    
    2021-06-25 08:14:26
    System:    Kernel: 5.12.12-1-default x86_64 bits: 64 Desktop: KDE Plasma 5.22.1 Distro: openSUSE Tumbleweed 20210623 
    Machine:   Type: Desktop System: HP product: N/A v: N/A serial: <filter> 
               Mobo: HP model: 8433 v: 11 serial: <filter> UEFI-[Legacy]: AMI v: F.15 date: 07/24/2018 
    Network:   Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtl8821ce 
               IF: wlo1 state: down mac: <filter> 
               Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
               IF: enp46s0 state: up speed: 100 Mbps duplex: full mac: <filter>
               
    2021-07-02 17:49:41
    System:    Kernel: 5.12.13-1-default x86_64 bits: 64 Desktop: KDE Plasma 5.22.2 Distro: openSUSE Tumbleweed 20210629 
    Machine:   Type: Desktop System: HP product: N/A v: N/A serial: <filter> 
               Mobo: HP model: 8433 v: 11 serial: <filter> UEFI-[Legacy]: AMI v: F.15 date: 07/24/2018 
    Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
               IF: enp46s0 state: up speed: 100 Mbps duplex: full mac: <filter>
    Any comments appreciated

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,355

    Default AW: Wireless device not detected after kernel 5.12.12 update

    Please post:
    Code:
    /sbin/lspci -nnk | grep -iA3 net
    Code:
    uname -a
    Code:
    zypper se -si rtw rtl8821 kernel
    Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtl8821ce
    I think, this is the false one, should be rtw........

    But with kernel 5.12 it should work without any kmp.......
    Last edited by Sauerland; 11-Jul-2021 at 10:06.

  3. #3
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: Wireless device not detected after kernel 5.12.12 update

    thx for your reply

    since my first post I re-installed the old kernel and booting into it still no wifi detection

    as the bluetooth part is detected, I'm assuming a hw failure

    below is the requested outputs
    Code:
    nvme-120GB 2021-07-11 19:47 ~
    >... /sbin/lspci -nnk | grep -iA3 net
    2e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
            Subsystem: Hewlett-Packard Company Device [103c:8433]
            Kernel driver in use: r8169
            Kernel modules: r8169
    nvme-120GB 2021-07-11 19:49 ~
    >... uname -a
    Linux nvme-120GB 5.13.0-1-default #1 SMP Fri Jul 2 05:54:32 UTC 2021 (aa40472) x86_64 x86_64 x86_64 GNU/Linux
    nvme-120GB 2021-07-11 19:49 ~
    >... zypper se -si rtw rtl8821 kernel
    Loading repository data...
    Reading installed packages...
    
        | Name                             | Type   | Version                      | Arch  | Repository
    ---+--------------------------------+---------+----------------------------+--------+---------------------
    i+ | kernel-default                 | package | 5.13.0-1.2                 | x86_64 | tumbleweed-oss
    i+ | kernel-default                 | package | 5.12.12-1.1                | x86_64 | tumbleweed-history
    i+ | kernel-default-devel           | package | 5.13.0-1.2                 | x86_64 | tumbleweed-oss
    i+ | kernel-default-devel           | package | 5.12.12-1.1                | x86_64 | tumbleweed-history
    i+ | kernel-devel                   | package | 5.13.0-1.2                 | noarch | tumbleweed-oss
    i+ | kernel-devel                   | package | 5.12.12-1.1                | noarch | tumbleweed-history
    i+ | kernel-firmware-all            | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-all            | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-amdgpu         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-amdgpu         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-ath10k         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-ath10k         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-ath11k         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-ath11k         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-atheros        | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-atheros        | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-bluetooth      | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-bluetooth      | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-bnx2           | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-bnx2           | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-brcm           | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-brcm           | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-chelsio        | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-chelsio        | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-dpaa2          | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-dpaa2          | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-i915           | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-i915           | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-intel          | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-intel          | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-iwlwifi        | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-iwlwifi        | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-liquidio       | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-liquidio       | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-marvell        | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-marvell        | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-media          | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-media          | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-mediatek       | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-mediatek       | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-mellanox       | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-mellanox       | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-mwifiex        | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-mwifiex        | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-network        | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-network        | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-nfp            | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-nfp            | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-nvidia         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-nvidia         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-platform       | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-platform       | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-prestera       | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-prestera       | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-qcom           | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-qcom           | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-qlogic         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-qlogic         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-radeon         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-radeon         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-realtek        | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-realtek        | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-serial         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-serial         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-sound          | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-sound          | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-ti             | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-ti             | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-ueagle         | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-ueagle         | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-firmware-usb-network    | package | 20210609-1.1               | noarch | tumbleweed-oss
    i+ | kernel-firmware-usb-network    | package | 20210609-1.1               | noarch | tumbleweed-history
    i+ | kernel-macros                  | package | 5.13.0-1.2                 | noarch | tumbleweed-oss
    i+ | kernel-syms                    | package | 5.13.0-1.2                 | x86_64 | tumbleweed-oss
    i+ | kernel-syms                    | package | 5.12.12-1.1                | x86_64 | tumbleweed-history
    i+ | purge-kernels-service          | package | 0-8.1                      | noarch | tumbleweed-oss
    i+ | purge-kernels-service          | package | 0-8.1                      | noarch | tumbleweed-history
    i+ | rtl8821ce-blacklist-rtw_8821ce | package | git20210529-3.13           | x86_64 | tumbleweed-RTL8821CE
    i+ | rtl8821ce-kmp-default          | package | git20210529_k5.13.0_1-3.13 | x86_64 | tumbleweed-RTL8821CE
    nvme-120GB 2021-07-11 19:50 ~
    >...

  4. #4
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,355

    Default AW: Wireless device not detected after kernel 5.12.12 update

    Code:
    i+ | rtl8821ce-blacklist-rtw_8821ce | package | git20210529-3.13           | x86_64 | tumbleweed-RTL8821CE
    i+ | rtl8821ce-kmp-default          | package | git20210529_k5.13.0_1-3.13 | x86_64 | tumbleweed-RTL8821CE
    Delete these packages and restart.

    The Wlan should work with the kernels rtw module out of the box

  5. #5
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,355

    Default AW: Wireless device not detected after kernel 5.12.12 update

    PS:
    Code:
    /sbin/lspci -nnk | grep -iA3 net
    should also show the Wlan:
    Code:
    /sbin/lspci -nnk | grep -iA3 net
    01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
            Subsystem: Hewlett-Packard Company Device [103c:84a6]
            Kernel driver in use: r8169
            Kernel modules: r8169
    02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821]
            Subsystem: Hewlett-Packard Company Device [103c:831a]
            Kernel driver in use: rtw_8821ce
            Kernel modules: rtw88_8821ce, rtw_8821ce

  6. #6
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: Wireless device not detected after kernel 5.12.12 update

    thx again for the info

    on a laptop with the Realtek RTL8821CE wireless device the network was still accessible after deleting packages
    rtl8821ce-blacklist-rtw_8821ce
    rtl8821ce-kmp-default

    on this PC deleting those made no differnce, no wireless network

    output of commands lsusb, lspci and inxi -F still do not recognise the wireless card only Bluetooth
    Code:
    nvme-120GB 2021-07-12 00:28 ~/Downloads
    >... sudo journalctl -xb | grep 8821               
    [sudo] password for root: 
    Jul 12 00:12:47 nvme-120GB kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
    Jul 12 00:12:47 nvme-120GB kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
    Jul 12 00:12:47 nvme-120GB kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
    nvme-120GB 2021-07-12 00:31 ~/Downloads
    >...
    
    nvme-120GB 2021-07-12 00:31 ~/Downloads
    >... sudo /sbin/lspci -nnk | grep -iA3 net
    [sudo] password for root: 
    2e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
            Subsystem: Hewlett-Packard Company Device [103c:8433]
            Kernel driver in use: r8169
            Kernel modules: r8169
    nvme-120GB 2021-07-12 00:45 ~/Downloads
    >...

  7. #7
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,355

    Default AW: Wireless device not detected after kernel 5.12.12 update

    Is the wirelss deactivates:
    Code:
    rfkill list all
    Otherwise post:
    Code:
    journalctl -b | grep -Ei 'wlan|network|realtek|8821|rtl'

  8. #8
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: Wireless device not detected after kernel 5.12.12 update

    info as requested, first part
    Code:
    nvme-120GB 2021-07-12 09:20 ~/Downloads
    >... rfkill list all
    Absolute path to 'rfkill' is '/usr/sbin/rfkill', so running it may require superuser privileges (eg. root).
    nvme-120GB 2021-07-12 09:22 ~/Downloads
    >... sudo rfkill list all
    [sudo] password for root: 
    0: hci0: Bluetooth
            Soft blocked: yes
            Hard blocked: no
    nvme-120GB 2021-07-12 09:23 ~/Downloads
    >... sudo journalctl -b | grep -Ei 'wlan|network|realtek|8821|rtl'
    Jul 12 08:28:34 nvme-120GB kernel: drop_monitor: Initializing network drop monitor service
    Jul 12 08:28:35 nvme-120GB systemd[1]: Reached target Host and Network Name Lookups.
    Jul 12 08:28:35 nvme-120GB avahi-daemon[601]: Network interface enumeration completed.
    Jul 12 08:28:36 nvme-120GB kernel: r8169 0000:2e:00.0 eth0: RTL8168h/8111h, f4:39:09:31:95:35, XID 541, IRQ 72
    Jul 12 08:28:36 nvme-120GB kernel: usb 1-10: Manufacturer: Realtek 
    Jul 12 08:28:36 nvme-120GB systemd[1]: Reached target Network (Pre).
    Jul 12 08:28:36 nvme-120GB systemd[1]: Starting Network Manager...
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.4275] NetworkManager (version 1.32.2) is starting... (for the first time)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.4275] Read config: /etc/NetworkManager/NetworkManager.conf
    Jul 12 08:28:36 nvme-120GB systemd[1]: Started Network Manager.
    Jul 12 08:28:36 nvme-120GB systemd[1]: Reached target Network.
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.4306] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
    Jul 12 08:28:36 nvme-120GB systemd[1]: Starting Network Manager Wait Online...
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.4326] manager[0x55be6c8c9040]: monitoring kernel firmware directory '/lib/firmware'.
    Jul 12 08:28:36 nvme-120GB dbus-daemon[602]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/sbin/NetworkManager --no-daemon ")
    Jul 12 08:28:36 nvme-120GB systemd[1]: Finished Network Manager Wait Online.
    Jul 12 08:28:36 nvme-120GB systemd[1]: Reached target Network is Online.
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.4788] hostname: hostname: using hostnamed
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.4788] hostname: hostname changed from (none) to "nvme-120GB"
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.4791] dns-mgr[0x55be6c8ad220]: init: dns=default,systemd-resolved rc-manager=netconfig
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5061] manager[0x55be6c8c9040]: rfkill: Wi-Fi hardware radio set disabled
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5062] manager[0x55be6c8c9040]: rfkill: WWAN hardware radio set disabled
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5099] Loaded device plugin: NMOvsFactory (/usr/lib64/NetworkManager/1.32.2/libnm-device-plugin-ovs.so)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5123] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.2/libnm-device-plugin-bluetooth.so)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5164] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.32.2/libnm-device-plugin-team.so)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5170] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.32.2/libnm-device-plugin-wwan.so)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5177] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.32.2/libnm-device-plugin-wifi.so)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5181] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.32.2/libnm-device-plugin-adsl.so)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5184] manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5184] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5184] manager: Networking is enabled by state file
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5185] dhcp-init: Using DHCP client 'dhclient'
    Jul 12 08:28:36 nvme-120GB dbus-daemon[602]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/sbin/NetworkManager --no-daemon ")
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5188] settings: Loaded settings plugin: keyfile (internal)
    Jul 12 08:28:36 nvme-120GB systemd[1]: Starting Network Manager Script Dispatcher Service...
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5245] device (lo): carrier: link connected
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5247] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5252] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5268] ovsdb: Could not connect: No such file or directory
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5268] ovsdb: disconnected from ovsdb
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5289] modem-manager: ModemManager available
    Jul 12 08:28:36 nvme-120GB systemd[1]: Started Network Manager Script Dispatcher Service.
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC671: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs:
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0:      Headset Mic=0x18
    Jul 12 08:28:36 nvme-120GB kernel: snd_hda_codec_realtek hdaudioC1D0:      Line=0x1b
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.8049] device (eth0): interface index 2 renamed iface from 'eth0' to 'enp46s0'
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.8436] manager: startup complete
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.8436] device (enp46s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
    Jul 12 08:28:36 nvme-120GB kernel: Generic FE-GE Realtek PHY r8169-2e00:00: attached PHY driver (mii_bus:phy_addr=r8169-2e00:00, irq=MAC)
    Jul 12 08:28:37 nvme-120GB kernel: Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
    Jul 12 08:28:37 nvme-120GB kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
    Jul 12 08:28:37 nvme-120GB kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
    Jul 12 08:28:37 nvme-120GB kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
    Jul 12 08:28:37 nvme-120GB kernel: Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990
    Jul 12 08:28:38 nvme-120GB kernel: Bluetooth: hci0: RTL: fw version 0x829a7644
    Jul 12 08:28:38 nvme-120GB NetworkManager[705]: <info>  [1626071318.6977] device (enp46s0): carrier: link connected
    Jul 12 08:28:38 nvme-120GB NetworkManager[705]: <info>  [1626071318.6981] device (enp46s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
    Jul 12 08:28:47 nvme-120GB systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
    Jul 12 08:28:50 nvme-120GB NetworkManager[705]: <info>  [1626071330.6237] agent-manager: agent[8deeab0d2e271b0a,:1.30/org.kde.plasma.networkmanagement/1000]: agent registered
    Jul 12 08:28:50 nvme-120GB ksmserver[1273]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 08:28:54 nvme-120GB kdeinit5[1507]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4605] device (enp46s0): Activation: starting connection 'Wired connection 1' (9d71fe86-72aa-3a45-8d87-b7f0fb53c67a)
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4606] audit: op="connection-activate" uuid="9d71fe86-72aa-3a45-8d87-b7f0fb53c67a" name="Wired connection 1" pid=1281 uid=1000 result="success"
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4607] device (enp46s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4609] manager: NetworkManager state is now CONNECTING
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4610] device (enp46s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4700] device (enp46s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4707] dhcp4 (enp46s0): activation: beginning transaction (timeout in 45 seconds)
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.4726] dhcp4 (enp46s0): dhclient started with pid 2112
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.5113] dhcp4 (enp46s0):   address 192.168.178.101
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.5113] dhcp4 (enp46s0):   plen 24 (255.255.255.0)
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.5113] dhcp4 (enp46s0):   gateway 192.168.178.1
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.5114] dhcp4 (enp46s0):   lease time 864000
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.5114] dhcp4 (enp46s0):   nameserver '192.168.178.1'
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.5114] dhcp4 (enp46s0):   domain name 'fritz.box'
    Jul 12 08:32:18 nvme-120GB NetworkManager[705]: <info>  [1626071538.5114] dhcp4 (enp46s0): state changed unknown -> extended, address=192.168.178.101
    Jul 12 08:32:20 nvme-120GB NetworkManager[705]: <info>  [1626071540.3694] dhcp6 (enp46s0): activation: beginning transaction (timeout in 45 seconds)
    Jul 12 08:32:20 nvme-120GB NetworkManager[705]: <info>  [1626071540.3718] dhcp6 (enp46s0): dhclient started with pid 2125
    Jul 12 08:32:20 nvme-120GB NetworkManager[705]: <info>  [1626071540.9008] dhcp6 (enp46s0):   nameserver 'fd00::e228:6dff:fe62:7e52'
    Jul 12 08:32:20 nvme-120GB NetworkManager[705]: <info>  [1626071540.9008] dhcp6 (enp46s0): state changed unknown -> extended
    Jul 12 08:32:20 nvme-120GB NetworkManager[705]: <info>  [1626071540.9019] dhcp6 (enp46s0): client pid 2125 exited with status 0
    Jul 12 08:32:20 nvme-120GB NetworkManager[705]: <info>  [1626071540.9020] dhcp6 (enp46s0): state changed extended -> terminated
    Jul 12 08:32:20 nvme-120GB dbus-daemon[602]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/sbin/NetworkManager --no-daemon ")
    Jul 12 08:32:20 nvme-120GB systemd[1]: Starting Network Manager Script Dispatcher Service...
    Jul 12 08:32:20 nvme-120GB systemd[1]: Started Network Manager Script Dispatcher Service.
    Jul 12 08:32:21 nvme-120GB NetworkManager[705]: <info>  [1626071541.9595] device (enp46s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
    Jul 12 08:32:21 nvme-120GB NetworkManager[705]: <info>  [1626071541.9617] device (enp46s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
    Jul 12 08:32:21 nvme-120GB NetworkManager[705]: <info>  [1626071541.9619] device (enp46s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
    Jul 12 08:32:21 nvme-120GB NetworkManager[705]: <info>  [1626071541.9623] manager: NetworkManager state is now CONNECTED_LOCAL
    Jul 12 08:32:21 nvme-120GB NetworkManager[705]: <info>  [1626071541.9625] manager: NetworkManager state is now CONNECTED_SITE
    Jul 12 08:32:21 nvme-120GB NetworkManager[705]: <info>  [1626071541.9626] policy: set 'Wired connection 1' (enp46s0) as default for IPv4 routing and DNS
    Jul 12 08:32:21 nvme-120GB NetworkManager[705]: <info>  [1626071541.9627] policy: set 'Wired connection 1' (enp46s0) as default for IPv6 routing and DNS
    Jul 12 08:32:21 nvme-120GB dbus-daemon[602]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/sbin/NetworkManager --no-daemon ")
    Jul 12 08:32:22 nvme-120GB NetworkManager[705]: <info>  [1626071542.0643] device (enp46s0): Activation: successful, device activated.
    Jul 12 08:32:22 nvme-120GB NetworkManager[705]: <info>  [1626071542.0714] audit: op="statistics" interface="enp46s0" ifindex=2 args="2000" pid=1281 uid=1000 result="success"
    Jul 12 08:32:22 nvme-120GB NetworkManager[705]: <info>  [1626071542.1232] manager: NetworkManager state is now CONNECTED_GLOBAL
    Jul 12 08:32:27 nvme-120GB NetworkManager[705]: <info>  [1626071547.6981] audit: op="statistics" interface="enp46s0" ifindex=2 args="0" pid=1281 uid=1000 result="success"
    Jul 12 08:32:32 nvme-120GB systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
    Jul 12 08:47:08 nvme-120GB kdeinit5[4958]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 08:49:57 nvme-120GB NetworkManager[705]: <info>  [1626072597.0307] audit: op="statistics" interface="enp46s0" ifindex=2 args="2000" pid=1281 uid=1000 result="success"
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8224] device (enp46s0): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
    Jul 12 08:49:58 nvme-120GB dbus-daemon[602]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/sbin/NetworkManager --no-daemon ")
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8226] manager: NetworkManager state is now DISCONNECTING

  9. #9
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: Wireless device not detected after kernel 5.12.12 update

    info as requested, second part
    Code:
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8234] audit: op="device-disconnect" interface="enp46s0" ifindex=2 pid=1281 uid=1000 result="success"
    Jul 12 08:49:58 nvme-120GB systemd[1]: Starting Network Manager Script Dispatcher Service...
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8285] audit: op="statistics" interface="enp46s0" ifindex=2 args="0" pid=1281 uid=1000 result="success"
    Jul 12 08:49:58 nvme-120GB systemd[1]: Started Network Manager Script Dispatcher Service.
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8312] device (enp46s0): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8641] dhcp4 (enp46s0): canceled DHCP transaction, DHCP client pid 2112
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8641] dhcp4 (enp46s0): state changed extended -> terminated
    Jul 12 08:49:58 nvme-120GB NetworkManager[705]: <info>  [1626072598.8643] dhcp6 (enp46s0): canceled DHCP transaction
    Jul 12 08:49:59 nvme-120GB NetworkManager[705]: <info>  [1626072599.0633] manager: NetworkManager state is now DISCONNECTED
    Jul 12 08:50:09 nvme-120GB systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
    Jul 12 08:51:39 nvme-120GB kernel: ums-realtek 1-7:1.0: USB Mass Storage device detected
    Jul 12 08:51:39 nvme-120GB kernel: usbcore: registered new interface driver ums-realtek
    Jul 12 08:51:56 nvme-120GB kdeinit5[5933]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:02:18 nvme-120GB kdeinit5[6401]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:03:54 nvme-120GB kdeinit5[6552]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:04:28 nvme-120GB kdeinit5[6621]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:07:15 nvme-120GB kernel: ums-realtek 1-7:1.0: USB Mass Storage device detected
    Jul 12 09:07:48 nvme-120GB kdeinit5[6832]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:08:03 nvme-120GB kdeinit5[6864]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:08:06 nvme-120GB kdeinit5[6896]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:08:07 nvme-120GB kdeinit5[6916]: Qt: Session management error: networkIdsList argument is NULL
    Jul 12 09:10:49 nvme-120GB kernel: ums-realtek 1-7:1.0: USB Mass Storage device detected
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7020] device (enp46s0): Activation: starting connection 'Wired connection 1' (9d71fe86-72aa-3a45-8d87-b7f0fb53c67a)
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7021] audit: op="connection-activate" uuid="9d71fe86-72aa-3a45-8d87-b7f0fb53c67a" name="Wired connection 1" pid=6717 uid=1000 result="success"
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7022] device (enp46s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7024] manager: NetworkManager state is now CONNECTING
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7026] device (enp46s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7122] device (enp46s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7124] dhcp4 (enp46s0): activation: beginning transaction (timeout in 45 seconds)
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7138] dhcp4 (enp46s0): dhclient started with pid 7548
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7514] dhcp4 (enp46s0):   address 192.168.178.101
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7515] dhcp4 (enp46s0):   plen 24 (255.255.255.0)
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7515] dhcp4 (enp46s0):   gateway 192.168.178.1
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7515] dhcp4 (enp46s0):   lease time 864000
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7515] dhcp4 (enp46s0):   nameserver '192.168.178.1'
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7515] dhcp4 (enp46s0):   domain name 'fritz.box'
    Jul 12 09:16:03 nvme-120GB NetworkManager[705]: <info>  [1626074163.7515] dhcp4 (enp46s0): state changed unknown -> extended, address=192.168.178.101
    Jul 12 09:16:04 nvme-120GB NetworkManager[705]: <info>  [1626074164.8779] dhcp6 (enp46s0): activation: beginning transaction (timeout in 45 seconds)
    Jul 12 09:16:04 nvme-120GB NetworkManager[705]: <info>  [1626074164.8793] dhcp6 (enp46s0): dhclient started with pid 7558
    Jul 12 09:16:05 nvme-120GB NetworkManager[705]: <info>  [1626074165.8362] dhcp6 (enp46s0):   nameserver 'fd00::e228:6dff:fe62:7e52'
    Jul 12 09:16:05 nvme-120GB NetworkManager[705]: <info>  [1626074165.8362] dhcp6 (enp46s0): state changed unknown -> extended
    Jul 12 09:16:05 nvme-120GB dbus-daemon[602]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/sbin/NetworkManager --no-daemon ")
    Jul 12 09:16:05 nvme-120GB systemd[1]: Starting Network Manager Script Dispatcher Service...
    Jul 12 09:16:05 nvme-120GB NetworkManager[705]: <info>  [1626074165.8410] dhcp6 (enp46s0): client pid 7558 exited with status 0
    Jul 12 09:16:05 nvme-120GB NetworkManager[705]: <info>  [1626074165.8410] dhcp6 (enp46s0): state changed extended -> terminated
    Jul 12 09:16:05 nvme-120GB systemd[1]: Started Network Manager Script Dispatcher Service.
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.3073] device (enp46s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.3088] device (enp46s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.3090] device (enp46s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.3093] manager: NetworkManager state is now CONNECTED_LOCAL
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.3096] manager: NetworkManager state is now CONNECTED_SITE
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.3096] policy: set 'Wired connection 1' (enp46s0) as default for IPv4 routing and DNS
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.3097] policy: set 'Wired connection 1' (enp46s0) as default for IPv6 routing and DNS
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.4015] device (enp46s0): Activation: successful, device activated.
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.4072] audit: op="statistics" interface="enp46s0" ifindex=2 args="2000" pid=6717 uid=1000 result="success"
    Jul 12 09:16:06 nvme-120GB NetworkManager[705]: <info>  [1626074166.4564] manager: NetworkManager state is now CONNECTED_GLOBAL
    Jul 12 09:16:15 nvme-120GB NetworkManager[705]: <info>  [1626074175.2335] audit: op="statistics" interface="enp46s0" ifindex=2 args="0" pid=6717 uid=1000 result="success"
    Jul 12 09:16:17 nvme-120GB systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
    Jul 12 09:20:46 nvme-120GB NetworkManager[705]: <info>  [1626074446.7777] audit: op="statistics" interface="enp46s0" ifindex=2 args="2000" pid=6717 uid=1000 result="success"
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7076] device (enp46s0): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7078] manager: NetworkManager state is now DISCONNECTING
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7085] audit: op="device-disconnect" interface="enp46s0" ifindex=2 pid=6717 uid=1000 result="success"
    Jul 12 09:20:49 nvme-120GB dbus-daemon[602]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=705 comm="/usr/sbin/NetworkManager --no-daemon ")
    Jul 12 09:20:49 nvme-120GB systemd[1]: Starting Network Manager Script Dispatcher Service...
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7129] audit: op="statistics" interface="enp46s0" ifindex=2 args="0" pid=6717 uid=1000 result="success"
    Jul 12 09:20:49 nvme-120GB systemd[1]: Started Network Manager Script Dispatcher Service.
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7173] device (enp46s0): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7186] dhcp4 (enp46s0): canceled DHCP transaction, DHCP client pid 7548
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7186] dhcp4 (enp46s0): state changed extended -> terminated
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.7188] dhcp6 (enp46s0): canceled DHCP transaction
    Jul 12 09:20:49 nvme-120GB NetworkManager[705]: <info>  [1626074449.9107] manager: NetworkManager state is now DISCONNECTED
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8373] device (enp46s0): Activation: starting connection 'Wired connection 1' (9d71fe86-72aa-3a45-8d87-b7f0fb53c67a)
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8374] audit: op="connection-activate" uuid="9d71fe86-72aa-3a45-8d87-b7f0fb53c67a" name="Wired connection 1" pid=6717 uid=1000 result="success"
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8375] device (enp46s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8377] manager: NetworkManager state is now CONNECTING
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8378] device (enp46s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8441] device (enp46s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8443] dhcp4 (enp46s0): activation: beginning transaction (timeout in 45 seconds)
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8460] dhcp4 (enp46s0): dhclient started with pid 7979
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8720] dhcp4 (enp46s0):   address 192.168.178.101
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8721] dhcp4 (enp46s0):   plen 24 (255.255.255.0)
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8721] dhcp4 (enp46s0):   gateway 192.168.178.1
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8721] dhcp4 (enp46s0):   lease time 864000
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8721] dhcp4 (enp46s0):   nameserver '192.168.178.1'
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8721] dhcp4 (enp46s0):   domain name 'fritz.box'
    Jul 12 09:20:55 nvme-120GB NetworkManager[705]: <info>  [1626074455.8721] dhcp4 (enp46s0): state changed unknown -> extended, address=192.168.178.101
    Jul 12 09:20:56 nvme-120GB kded5[1237]: plasma-nm: Network connectivity limited, scheduling notification
    Jul 12 09:20:56 nvme-120GB NetworkManager[705]: <info>  [1626074456.9623] dhcp6 (enp46s0): activation: beginning transaction (timeout in 45 seconds)
    Jul 12 09:20:56 nvme-120GB NetworkManager[705]: <info>  [1626074456.9637] dhcp6 (enp46s0): dhclient started with pid 8012
    Jul 12 09:20:57 nvme-120GB NetworkManager[705]: <info>  [1626074457.6622] dhcp6 (enp46s0):   nameserver 'fd00::e228:6dff:fe62:7e52'
    Jul 12 09:20:57 nvme-120GB NetworkManager[705]: <info>  [1626074457.6622] dhcp6 (enp46s0): state changed unknown -> extended
    Jul 12 09:20:57 nvme-120GB NetworkManager[705]: <info>  [1626074457.6643] dhcp6 (enp46s0): client pid 8012 exited with status 0
    Jul 12 09:20:57 nvme-120GB NetworkManager[705]: <info>  [1626074457.6644] dhcp6 (enp46s0): state changed extended -> terminated
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.0513] device (enp46s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.0531] device (enp46s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.0533] device (enp46s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.0538] manager: NetworkManager state is now CONNECTED_GLOBAL
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.0540] policy: set 'Wired connection 1' (enp46s0) as default for IPv4 routing and DNS
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.0541] policy: set 'Wired connection 1' (enp46s0) as default for IPv6 routing and DNS
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.1470] device (enp46s0): Activation: successful, device activated.
    Jul 12 09:20:58 nvme-120GB NetworkManager[705]: <info>  [1626074458.1521] audit: op="statistics" interface="enp46s0" ifindex=2 args="2000" pid=6717 uid=1000 result="success"
    Jul 12 09:21:05 nvme-120GB NetworkManager[705]: <info>  [1626074465.0134] audit: op="statistics" interface="enp46s0" ifindex=2 args="0" pid=6717 uid=1000 result="success"
    Jul 12 09:21:08 nvme-120GB systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
    nvme-120GB 2021-07-12 09:23 ~/Downloads
    >...]

  10. #10
    Join Date
    Sep 2012
    Posts
    6,788

    Default Re: Wireless device not detected after kernel 5.12.12 update

    Quote Originally Posted by keellambert View Post
    Code:
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5184] manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
    Jul 12 08:28:36 nvme-120GB NetworkManager[705]: <info>  [1626071316.5184] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file
    So you need to enable wifi in NetworkManager.

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •