Rocky 9.6 No network stats for wifi device

Rocky Linux Help & Support
1

I just loaded Rocky 9 Mate desktop to my laptop which had CentOS8 on it previously and networking worked completely.

I have been trying to figure out why the system monitor network applet is not showing any network traffic and noticed that there are no wifi stats being collected…
Network is working but shows no traffic flowing

ifconfig

wlp0s20f3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.176  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 38:00:25:61:fa:21  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Looks like wifi is coming via the intel chipset

# lspci -vv -s 00:14.3
00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30)
	Subsystem: Intel Corporation Device 0034
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 174
	IOMMU group: 4
	Region 0: Memory at 6023104000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [c8] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee008b8  Data: 0000
	Capabilities: [40] Express (v2) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE- FLReset+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		DevCap2: Completion Timeout: Range B, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
	Capabilities: [80] MSI-X: Enable- Count=16 Masked-
		Vector table: BAR=0 offset=00002000
		PBA: BAR=0 offset=00003000
	Capabilities: [100 v0] Null
	Capabilities: [14c v1] Latency Tolerance Reporting
		Max snoop latency: 0ns
		Max no snoop latency: 0ns
	Capabilities: [164 v1] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

I have another laptop with Rock9.6 on it also but a different wifi chipset and stats work.
This used to work on CentOS8 on this laptop before the “upgrade”

Any pointers to getting stats working again ?

2

Where should this be written up as a bug ?

3

I would wait for the upcoming linux-firmware package update that might address this issue. This behavior can occur if there is a mismatch between the kernel drivers and firmware. If it does not resolve your issue, then we can look into opening a bug report upstream.

1 Like
4

thx will wait and say either way if new firmware fixes it.

5

Some more details…

Linux xxxxx 5.14.0-570.23.1.el9_6.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 26 19:29:53 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

I see Kernel driver loaded

/var/log/messages
kernel: iwlwifi 0000:00:14.3: loaded firmware version 46.7e3e4b69.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm

Checked kernel.org and grabbed, I think, the most current version from

DIFF’d the unxz /usr/lib/firmware/iwlwifi-9000-pu-b0-jf-b0-46.ucode.xz loaded on 9.6
against linux-firmware.git/tree/iwlwifi-9000-pu-b0-jf-b0-46.ucode and they appear to be the same file.

When I updated yesterday I saw a number of firmware updates but none that seemed to be the above firmware. But in anycase I rebooted and still have no stats

$ ifconfig wlp0s20f3
wlp0s20f3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.176  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 38:00:25:61:fa:21  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
6

This may be a statement of the obvious, but are you sure there actually IS traffic on that device?

If you have, say, another network connection on that computer then maybe all of the traffic is flowing through that.

7

Yup, I’m using the connection to post all of this. Only has a wifi connection hooked up. And a single wifi card.

8

Try this command:

ip stats show dev wlp0s20f3

If the stats are still empty then it would confirm a driver issue

9 
# ip stats show dev wlp0s20f3
3: wlp0s20f3: group offload subgroup hw_stats_info
    l3_stats off used off
3: wlp0s20f3: group xstats_slave subgroup bond suite 802.3ad
3: wlp0s20f3: group xstats_slave subgroup bridge suite mcast
3: wlp0s20f3: group xstats_slave subgroup bridge suite stp
3: wlp0s20f3: group xstats subgroup bond suite 802.3ad
3: wlp0s20f3: group xstats subgroup bridge suite mcast
3: wlp0s20f3: group xstats subgroup bridge suite stp
3: wlp0s20f3: group afstats subgroup mpls
3: wlp0s20f3: group offload subgroup l3_stats off used off
3: wlp0s20f3: group offload subgroup cpu_hit

3: wlp0s20f3: group link
    RX:  bytes packets errors dropped  missed   mcast           
             0       0      0       0       0       0 
    TX:  bytes packets errors dropped carrier collsns           
             0       0      0       7       0       0

Yeah I think I tried all the different commands that can show stats

10

Ok should I be writing a bug report ? Where ?

Its been a while, I’ve written them against CentOS, Redhat, and Fedora over the years. Sometimes the folks at each Dist. preferred to write them themselves after seeing the bug.

11

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.