0

EDIT: requested diagnostic info from script in linked issue is at https://termbin.com/ml49

sudo journalctl -b 0 -u NetworkManager output: https://termbin.com/uyn7

$ service NetworkManager status
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
     Active: active (running) since Sat 2025-02-15 16:47:25 GMT; 6h ago
       Docs: man:NetworkManager(8)
   Main PID: 1147 (NetworkManager)
      Tasks: 4 (limit: 76527)
     Memory: 17.4M (peak: 34.1M)
        CPU: 1.447s
     CGroup: /system.slice/NetworkManager.service
             └─1147 /usr/sbin/NetworkManager --no-daemon

Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.2010] dhcp4 (enp4s0): state changed new lease, address=192.168.1.118, acd pending Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.3695] dhcp4 (enp4s0): state changed new lease, address=192.168.1.118 Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.3697] policy: set 'netplan-enp4s0' (enp4s0) as default for IPv4 routing and DNS Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.3797] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.3805] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.3806] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.3807] manager: NetworkManager state is now CONNECTED_SITE Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.3808] device (enp4s0): Activation: successful, device activated. Feb 15 22:45:21 Bowzer4 NetworkManager[1147]: <info> [1739659521.5490] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 15 22:45:29 Bowzer4 NetworkManager[1147]: <info> [1739659529.6465] agent-manager: agent[b5556812dba186f3,:1.80/org.gnome.Shell.NetworkAgent/1000]: agent registered

Original Question:

Having worked fine with 22.04 for a couple of years, my Wi-Fi stopped working a week or so ago (I assume due to an update, I'm not sure). I attempted an upgrade to see if newer drivers would help but it didn't go well, and I ultimately started over with a fresh 24.04 (wiped hard disk). But the Wi-Fi still doesn't work - wireless settings UI shows No Wi-Fi Adapter Found.

I tried making sure the Realtek device had an appropriate driver, installing r8168-dkms but it didn't help - so I'm not certain whether it's functioning correctly. But to me, looking at the inxi an lshw output, the Intel device looks more like it's in a bad state.

$ uname -r
6.11.0-17-generic
$ iwconfig
lo        no wireless extensions.

enp4s0 no wireless extensions.

dkms status
r8168/8.052.01, 6.11.0-17-generic, x86_64: installed
$ inxi -Nz
Network:
  Device-1: Intel Raptor Lake PCH CNVi WiFi driver: N/A
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8168
sudo lshw -C network
  *-network UNCLAIMED       
       description: Network controller
       product: Raptor Lake PCH CNVi WiFi
       vendor: Intel Corporation
       physical id: 14.3
       bus info: pci@0000:00:14.3
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix cap_list
       configuration: latency=0
       resources: iomemory:620-61f memory:6203144000-6203147fff
  *-network
       description: Ethernet interface
       product: RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: enp4s0
       version: 15
       serial: b0:25:aa:63:60:c9
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.053.00-NAPI duplex=full ip=192.168.1.118 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:19 ioport:3000(size=256) memory:82204000-82204fff memory:82200000-82203fff
$ lspci -k
[...]
00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01)
    DeviceName: Onboard - Ethernet
    Subsystem: Intel Corporation Raptor Lake PCH CNVi WiFi
    Kernel modules: iwlwifi
[...]
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
    Subsystem: Tongfang Hongkong Limited RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
    Kernel driver in use: r8168
    Kernel modules: r8168

$ sudo dmesg | grep iwlwifi gives no output

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
6: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b0:25:aa:63:60:c9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.118/24 brd 192.168.1.255 scope global dynamic noprefixroute enp4s0
       valid_lft 83251sec preferred_lft 83251sec
    inet6 2a00:23c6:6221:8801:c288:bc75:6b23:b3b5/64 scope global temporary dynamic 
       valid_lft 297sec preferred_lft 117sec
    inet6 2a00:23c6:6221:8801:b225:aaff:fe63:60c9/64 scope global dynamic mngtmpaddr 
       valid_lft 297sec preferred_lft 117sec
    inet6 fe80::b225:aaff:fe63:60c9/64 scope link 
       valid_lft forever preferred_lft forever

Any suggestions for next steps to diagnose/fix the issue?

Many thanks

1 Answers1

1

One way or another, after installing updates, the issue is resolved.

I bought a cheap USB WiFi device in the meantime as a stop-gap, which worked fine.