Wifi speed too slow after general update

Ask Fedora
, , ,
1

Hello, the wifi on my Fedora 36 laptop is painfully slow after a general system update. I have confirmed that this is not an ISP issue as the speed on my ethernet port works perfectly.

I am running Fedora on a Thinkpad E14 with Kernel 5.18.16-200.fc36.x86_64. Thinking it might be a kernel issue, I also tried an older kernel 5.18.5-200.fc36.x86_64 which did not work.

On Wifi,

> resolvectl query google.com
google.com: resolve call failed: No appropriate name servers or networks for name found
> resolvectl query google.com
google.com: resolve call failed: Lookup failed due to system error: No route to host

The same works on the ethernet port,

> resolvectl query google.com
google.com: 142.250.77.110                     -- link: enp2s0
            2404:6800:4009:828::200e           -- link: enp2s0

-- Information acquired via protocol DNS in 10.0ms.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: no
-- Data from: network

ifconfig output

br-7ccd4f24420d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.0.1  netmask 255.255.0.0  broadcast 172.19.255.255
        inet6 fe80::42:d3ff:fe86:a59  prefixlen 64  scopeid 0x20<link>
        ether 02:42:d3:86:0a:59  txqueuelen 0  (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

br-86800297cb10: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.6.1  netmask 255.255.255.0  broadcast 192.168.6.255
        ether 02:42:ae:81:d9:8a  txqueuelen 0  (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

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:35:68:df:1a  txqueuelen 0  (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

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.29.150  netmask 255.255.255.0  broadcast 192.168.29.255
        inet6 fe80::b77f:12b:57de:858f  prefixlen 64  scopeid 0x20<link>
        inet6 2405:201:d006:615c:31f6:c2b9:25e4:fbf2  prefixlen 64  scopeid 0x0<global>
        ether 90:2e:16:aa:7a:d0  txqueuelen 1000  (Ethernet)
        RX packets 55740  bytes 49577301 (47.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36314  bytes 11248347 (10.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 28558  bytes 5339939 (5.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 28558  bytes 5339939 (5.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth1337f9a: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::823:d3ff:feb5:1bfe  prefixlen 64  scopeid 0x20<link>
        ether 0a:23:d3:b5:1b:fe  txqueuelen 0  (Ethernet)
        RX packets 9625  bytes 1888624 (1.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8932  bytes 2074779 (1.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:8f:91:b4  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

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.29.46  netmask 255.255.255.0  broadcast 192.168.29.255
        inet6 fe80::afdd:4825:e10a:f5a0  prefixlen 64  scopeid 0x20<link>
        inet6 2405:201:d006:615c:390:15ef:7d45:5ebe  prefixlen 64  scopeid 0x0<global>
        ether f8:89:d2:c8:51:51  txqueuelen 1000  (Ethernet)
        RX packets 10235  bytes 3099953 (2.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6338  bytes 1079187 (1.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I looked around and found,

The Reddit link is suspiciously similar to what I am facing. The timeline matches. Is there any know bug?

I understand I may not be providing the required information. Please let me know what information I need to provide to help debug this issue. Thanks!

2

Do you have differing DNS settings active, comparing between

enp2s0

and

wlp3s0

??!

Please, show the output of:

ip addr

and

( nmcli dev list || nmcli dev show ) 2>/dev/null | grep DNS

3

adding to that show what are the packages you have updated in last update. dnf history it will help us know which packages were updated.
https://docs.fedoraproject.org/en-US/Fedora/24/html/System_Administrators_Guide/sec-DNF-Transaction_History.html

4

I have not set any DNS settings previously. Only when the issue occurred, for debugging purposed, I set the DNS to 8.8.8.8 and 1.1.1.1 for the Wifi point. However, I reverted that after testing.

Please, show the output of:

ip addr

and

( nmcli dev list || nmcli dev show ) 2>/dev/null | grep DNS

Please find the output below,

[krnekhelesh@nekhelesh-work etc]$ 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 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 90:2e:16:aa:7a:d0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.29.150/24 brd 192.168.29.255 scope global dynamic noprefixroute enp2s0
       valid_lft 28782sec preferred_lft 28782sec
    inet6 2405:201:d006:615c:31f6:c2b9:25e4:fbf2/64 scope global dynamic noprefixroute 
       valid_lft 3586sec preferred_lft 3586sec
    inet6 fe80::b77f:12b:57de:858f/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f8:89:d2:c8:51:51 brd ff:ff:ff:ff:ff:ff
    inet 192.168.29.46/24 brd 192.168.29.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 28781sec preferred_lft 28781sec
    inet6 2405:201:d006:615c:390:15ef:7d45:5ebe/64 scope global dynamic noprefixroute 
       valid_lft 3588sec preferred_lft 3588sec
    inet6 fe80::afdd:4825:e10a:f5a0/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:8f:91:b4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: br-86800297cb10: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:ae:81:d9:8a brd ff:ff:ff:ff:ff:ff
    inet 192.168.6.1/24 brd 192.168.6.255 scope global br-86800297cb10
       valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:35:68:df:1a brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
7: br-7ccd4f24420d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:d3:86:0a:59 brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-7ccd4f24420d
       valid_lft forever preferred_lft forever
    inet6 fe80::42:d3ff:fe86:a59/64 scope link 
       valid_lft forever preferred_lft forever
9: veth1337f9a@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-7ccd4f24420d state UP group default 
    link/ether 0a:23:d3:b5:1b:fe brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::823:d3ff:feb5:1bfe/64 scope link 
       valid_lft forever preferred_lft forever

[krnekhelesh@nekhelesh-work etc]$ ( nmcli dev list || nmcli dev show ) 2>/dev/null | grep DNS
IP4.DNS[1]:                             192.168.29.1
IP6.DNS[1]:                             2405:201:d006:615c::c0a8:1d01
IP4.DNS[1]:                             192.168.29.1
IP6.DNS[1]:                             2405:201:d006:615c::c0a8:1d01
5

Here’s the dnf history. The entries before that were from the previous month where things were working as expected.

I suspect id 41. How do I see which packages were installed in that particular transaction?

[krnekhelesh@nekhelesh-work etc]$ dnf history list
ID     | Command line                                                           | Date and time    | Action(s)      | Altered
-----------------------------------------------------------------------------------------------------------------------------
    44 |                                                                        | 2022-08-14 11:18 | Install        |    1   
    43 |                                                                        | 2022-08-14 09:14 | Upgrade        |   27  <
    42 |                                                                        | 2022-08-12 18:14 | Reinstall      |    1 ><
    41 | update                                                                 | 2022-08-12 18:10 | C, E, I, U     |  474 >E
6

dnf hist info 41 (everything’s documented in man dnf, press / type history and press enter, press n and Shift+n to jump to next and previous search result respectively).

7

also 43 we can have a look which might did this

8

Here you go. Output for dnf 41.

I noticed 15 Not supported unit type and 16 '/etc/resolv.conf' -> '../run/systemd/resolve/stub-resolv.conf' at the end of the output. Could this be the issue?

The entire output couldn’t be pasted here. I have used pastebin => DNF History - Pastebin.com

9

Here’s the history info for 43.

[krnekhelesh@nekhelesh-work etc]$ dnf hist info 43
Transaction ID : 43
Begin time     : Sun 14 Aug 2022 09:14:18 AM IST
Begin rpmdb    : bd76eb4b72f6e9bbfcdebb402631634283b47f221b0af588a61288c06f153411
End time       : Sun 14 Aug 2022 09:14:26 AM IST (8 seconds)
End rpmdb      : a543f548eb5b168c3e71b953e845736ae8cf4ba466f4ead65515a9999f0713b3
User           : root <root>
Return-Code    : Success
Releasever     : 
Command Line   : 
Comment        : 
Packages Altered:
    Upgrade  filesystem-3.18-2.fc36.x86_64            @updates
    Upgrade  gnome-shell-42.4-1.fc36.x86_64           @updates
    Upgrade  ibus-typing-booster-2.18.9-1.fc36.noarch @updates
    Upgrade  libnfsidmap-1:2.6.2-0.fc36.x86_64        @updates
    Upgrade  libtirpc-1.3.3-0.fc36.x86_64             @updates
    Upgrade  man-pages-5.13-4.fc36.noarch             @updates
    Upgrade  mesa-dri-drivers-22.1.6-1.fc36.x86_64    @updates
    Upgrade  mesa-filesystem-22.1.6-1.fc36.x86_64     @updates
    Upgrade  mesa-libEGL-22.1.6-1.fc36.x86_64         @updates
    Upgrade  mesa-libGL-22.1.6-1.fc36.x86_64          @updates
    Upgrade  mesa-libgbm-22.1.6-1.fc36.x86_64         @updates
    Upgrade  mesa-libglapi-22.1.6-1.fc36.x86_64       @updates
    Upgrade  mesa-libxatracker-22.1.6-1.fc36.x86_64   @updates
    Upgrade  mesa-vulkan-drivers-22.1.6-1.fc36.x86_64 @updates
    Upgrade  microcode_ctl-2:2.1-51.1.fc36.x86_64     @updates
    Upgrade  mutter-42.4-1.fc36.x86_64                @updates
    Upgrade  nfs-utils-1:2.6.2-0.fc36.x86_64          @updates
    Upgrade  openssl-pkcs11-0.4.12-2.fc36.x86_64      @updates
    Upgrade  python3-unbound-1.16.2-3.fc36.x86_64     @updates
    Upgrade  unbound-anchor-1.16.2-3.fc36.x86_64      @updates
    Upgrade  unbound-libs-1.16.2-3.fc36.x86_64        @updates
    Upgrade  vim-data-2:9.0.189-1.fc36.noarch         @updates
    Upgrade  vim-minimal-2:9.0.189-1.fc36.x86_64      @updates
    Upgrade  webkit2gtk3-2.36.6-2.fc36.x86_64         @updates
    Upgrade  webkit2gtk3-jsc-2.36.6-2.fc36.x86_64     @updates
    Upgrade  wpebackend-fdo-1.12.1-1.fc36.x86_64      @updates
    Upgrade  zfs-fuse-0.7.2.2-23.fc36.x86_64          @updates
    Upgraded filesystem-3.18-1.fc36.x86_64            @@System
    Upgraded gnome-shell-42.3.1-1.fc36.x86_64         @@System
    Upgraded ibus-typing-booster-2.18.7-1.fc36.noarch @@System
    Upgraded libnfsidmap-1:2.6.1-2.rc8.fc36.x86_64    @@System
    Upgraded libtirpc-1.3.2-1.rc4.fc36.x86_64         @@System
    Upgraded man-pages-5.13-2.fc36.noarch             @@System
    Upgraded mesa-dri-drivers-22.1.5-2.fc36.x86_64    @@System
    Upgraded mesa-filesystem-22.1.5-2.fc36.x86_64     @@System
    Upgraded mesa-libEGL-22.1.5-2.fc36.x86_64         @@System
    Upgraded mesa-libGL-22.1.5-2.fc36.x86_64          @@System
    Upgraded mesa-libgbm-22.1.5-2.fc36.x86_64         @@System
    Upgraded mesa-libglapi-22.1.5-2.fc36.x86_64       @@System
    Upgraded mesa-libxatracker-22.1.5-2.fc36.x86_64   @@System
    Upgraded mesa-vulkan-drivers-22.1.5-2.fc36.x86_64 @@System
    Upgraded microcode_ctl-2:2.1-51.fc36.x86_64       @@System
    Upgraded mutter-42.3-1.fc36.x86_64                @@System
    Upgraded nfs-utils-1:2.6.1-2.rc8.fc36.x86_64      @@System
    Upgraded openssl-pkcs11-0.4.12-1.fc36.x86_64      @@System
    Upgraded python3-unbound-1.16.0-5.fc36.x86_64     @@System
    Upgraded unbound-anchor-1.16.0-5.fc36.x86_64      @@System
    Upgraded unbound-libs-1.16.0-5.fc36.x86_64        @@System
    Upgraded vim-data-2:9.0.137-1.fc36.noarch         @@System
    Upgraded vim-minimal-2:9.0.137-1.fc36.x86_64      @@System
    Upgraded webkit2gtk3-2.36.6-1.fc36.x86_64         @@System
    Upgraded webkit2gtk3-jsc-2.36.6-1.fc36.x86_64     @@System
    Upgraded wpebackend-fdo-1.12.0-2.fc36.x86_64      @@System
    Upgraded zfs-fuse-0.7.2.2-21.fc36.x86_64          @@System
10

If you have both wifi and ethernet active on the same subnet (192.168.29.XXX/24) as it appears you do then they may be interfering with each other.
Try with just one connected and see what may happen with the change.

Both your posts here are showing both interfaces active at the same time.

1 Like
11

Try with just one connected and see what may happen with the change.

I typically only use a Wifi access point. I noticed that it doesn’t work even with no active ethernet connection. That was the motivation for me that nothing was wrong with my ISP.

Since the only way I can post here is with an internet connection, I had to connect to the ethernet port.

I explicitly disabled ethernet and tried with Wifi. Here is the output.

[krnekhelesh@nekhelesh-work etc]$ ( nmcli dev list || nmcli dev show ) 2>/dev/null | grep DNS
IP4.DNS[1]:                             192.168.29.1
[krnekhelesh@nekhelesh-work etc]$ 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 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 90:2e:16:aa:7a:d0 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f8:89:d2:c8:51:51 brd ff:ff:ff:ff:ff:ff
    inet 192.168.29.46/24 brd 192.168.29.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 28771sec preferred_lft 28771sec
    inet6 2405:201:d006:615c:390:15ef:7d45:5ebe/64 scope global dynamic noprefixroute 
       valid_lft 3601sec preferred_lft 3601sec
    inet6 fe80::afdd:4825:e10a:f5a0/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:8f:91:b4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: br-86800297cb10: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:ae:81:d9:8a brd ff:ff:ff:ff:ff:ff
    inet 192.168.6.1/24 brd 192.168.6.255 scope global br-86800297cb10
       valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:35:68:df:1a brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
7: br-7ccd4f24420d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:d3:86:0a:59 brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-7ccd4f24420d
       valid_lft forever preferred_lft forever
    inet6 fe80::42:d3ff:fe86:a59/64 scope link 
       valid_lft forever preferred_lft forever
9: veth1337f9a@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-7ccd4f24420d state UP group default 
    link/ether 0a:23:d3:b5:1b:fe brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::823:d3ff:feb5:1bfe/64 scope link 
       valid_lft forever preferred_lft forever
12

Please show us the output of ip route

13

Here you go,

[krnekhelesh@nekhelesh-work etc]$ ip route
default via 192.168.29.1 dev wlp3s0 proto dhcp src 192.168.29.46 metric 600 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
172.19.0.0/16 dev br-7ccd4f24420d proto kernel scope link src 172.19.0.1 
192.168.6.0/24 dev br-86800297cb10 proto kernel scope link src 192.168.6.1 linkdown 
192.168.29.0/24 dev wlp3s0 proto kernel scope link src 192.168.29.46 metric 600 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
14

That shows a valid default route via the wifi.
What defines the ‘too slow’ for you? Inherently wifi is usually slightly slower than wired ethernet, and it depends on what wifi protocol is in use what speed you are getting. The 2.4 GHz band is usually slower than the 5 GHz band, sometimes depending on signal strength.

Please run a speedtest at www.speedtest.net on wifi only and repeat it on wired only and post the results of each like below. I am only paying for the 15 Mbps bandwidth so mine is capped there.

a9391a28d9c43e7263dcd67109e35c53698fea11.png
a9391a28d9c43e7263dcd67109e35c53698fea11.png754×293 28.7 KB

15

Oh, by slow, I mean it is unable to load any webpage :sweat_smile: including google.com. I could have lived with slow speeds. I have the Gnome Shell Extension Vitals installed that reports speed in bytes. The same laptop before the update used to show a wifi speed of around 60 Mbps. My PC has a wifi speed of around 80 Mbps.

[krnekhelesh@nekhelesh-work etc]$ resolvectl query google.com
google.com: resolve call failed: Lookup failed due to system error: No route to host

Update 1: I connected to the 5 Ghz band and it all started working. However, after testing switching to another network and then back to the 5 Ghz band, the problem came back. I tried rebooting the system. I have other devices in the same network that seem to work without any issues. What’s going on?

Update 2: Tried connecting to my phone’s hotspot network. Issue persists.

16

Lets see some hardware and software details.

Please post the output of inxi -Fzx so we can tell what driver and hardware are in use.

17

Here you go,

[krnekhelesh@nekhelesh-work ~]$ inxi -Fzx
System:
  Kernel: 5.18.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-27.fc36 Desktop: GNOME v: 42.4
    Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Laptop System: LENOVO product: 20YDCTO1WW v: ThinkPad E14 Gen 3
    serial: <superuser required>
  Mobo: LENOVO model: 20YDCTO1WW serial: <superuser required> UEFI: LENOVO
    v: R1OET28W (1.07 ) date: 07/15/2021
Battery:
  ID-1: BAT0 charge: 36.0 Wh (87.4%) condition: 41.2/45.0 Wh (91.5%)
    volts: 12.0 min: 11.3 model: Celxpert 5B10X026 status: discharging
CPU:
  Info: 6-core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 2 rev: 1 cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB
  Speed (MHz): avg: 1498 high: 2628 min/max: 400/4056 boost: enabled cores:
    1: 2628 2: 1396 3: 1396 4: 1396 5: 1396 6: 1395 7: 1397 8: 1397 9: 1397
    10: 1397 11: 1396 12: 1396 bogomips: 50301
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel
    arch: GCN 5.1 bus-ID: 04:00.0
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-3:2
  Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: gpu: amdgpu resolution: 1920x1080~60Hz
  OpenGL:
    renderer: AMD RENOIR (LLVM 14.0.0 DRM 3.46 5.18.5-200.fc36.x86_64)
    v: 4.6 Mesa 22.1.6 direct render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 04:00.1
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo
    driver: N/A bus-ID: 04:00.5
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 04:00.6
  Sound Server-1: ALSA v: k5.18.5-200.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel port: 3000 bus-ID: 02:00.0
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    vendor: Lenovo driver: rtw_8822ce v: N/A port: 2000 bus-ID: 03:00.0
  IF: wlp3s0 state: up mac: <filter>
  IF-ID-1: br-7ccd4f24420d state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IF-ID-2: br-86800297cb10 state: down mac: <filter>
  IF-ID-3: docker0 state: down mac: <filter>
  IF-ID-4: veth004bafe state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-5: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 3-4:2
  Report: rfkill ID: hci0 rfk-id: 4 state: up address: see --recommends
Drives:
  Local Storage: total: 238.47 GiB used: 86.43 GiB (36.2%)
  ID-1: /dev/nvme0n1 vendor: Western Digital
    model: PC SN530 SDBPMPZ-256G-1001 size: 238.47 GiB temp: 31.9 C
Partition:
  ID-1: / size: 236.89 GiB used: 86.14 GiB (36.4%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 284.4 MiB (29.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 14 MiB (2.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 236.89 GiB used: 86.14 GiB (36.4%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A gpu: amdgpu temp: 41.0 C
  Fan Speeds (RPM): fan-1: 0 fan-2: 0
Info:
  Processes: 408 Uptime: 22m Memory: 14.46 GiB used: 3.51 GiB (24.3%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.1.1 Packages: 24
  note: see --pkg Shell: Bash v: 5.1.16 inxi: 3.3.19
18

I just did a dnf check-update and it gave the following updates. An update for NetworkManager is available. Should I try it out?

NetworkManager.x86_64                                                        1:1.38.4-1.fc36                                         updates
NetworkManager-adsl.x86_64                                                   1:1.38.4-1.fc36                                         updates
NetworkManager-bluetooth.x86_64                                              1:1.38.4-1.fc36                                         updates
NetworkManager-config-connectivity-fedora.noarch                             1:1.38.4-1.fc36                                         updates
NetworkManager-initscripts-ifcfg-rh.x86_64                                   1:1.38.4-1.fc36                                         updates
NetworkManager-initscripts-updown.noarch                                     1:1.38.4-1.fc36                                         updates
NetworkManager-libnm.x86_64                                                  1:1.38.4-1.fc36                                         updates
NetworkManager-ppp.x86_64                                                    1:1.38.4-1.fc36                                         updates
NetworkManager-team.x86_64                                                   1:1.38.4-1.fc36                                         updates
NetworkManager-wifi.x86_64                                                   1:1.38.4-1.fc36                                         updates
NetworkManager-wwan.x86_64                                                   1:1.38.4-1.fc36                                         updates
annobin-docs.noarch                                                          10.81-1.fc36                                            updates
annobin-plugin-gcc.x86_64                                                    10.81-1.fc36                                            updates
cups.x86_64                                                                  1:2.4.2-4.fc36                                          updates
cups-client.x86_64                                                           1:2.4.2-4.fc36                                          updates
cups-filesystem.noarch                                                       1:2.4.2-4.fc36                                          updates
cups-ipptool.x86_64                                                          1:2.4.2-4.fc36                                          updates
cups-libs.x86_64                                                             1:2.4.2-4.fc36                                          updates
distribution-gpg-keys.noarch                                                 1.76-1.fc36                                             updates
firefox.x86_64                                                               103.0.2-1.fc36                                          updates
git.x86_64                                                                   2.37.2-1.fc36                                           updates
git-core.x86_64                                                              2.37.2-1.fc36                                           updates
git-core-doc.noarch                                                          2.37.2-1.fc36                                           updates
ibus-libpinyin.x86_64                                                        1.12.92-1.fc36                                          updates
ipxe-roms-qemu.noarch                                                        20220210-1.git64113751.fc36                             updates
kernel.x86_64                                                                5.18.17-200.fc36                                        updates
kernel-core.x86_64                                                           5.18.17-200.fc36                                        updates
kernel-modules.x86_64                                                        5.18.17-200.fc36                                        updates
kernel-modules-extra.x86_64                                                  5.18.17-200.fc36                                        updates
libglvnd.x86_64                                                              1:1.4.0-4.fc36                                          updates
libglvnd-egl.x86_64                                                          1:1.4.0-4.fc36                                          updates
libglvnd-gles.x86_64                                                         1:1.4.0-4.fc36                                          updates
libglvnd-glx.x86_64                                                          1:1.4.0-4.fc36                                          updates
libglvnd-opengl.x86_64                                                       1:1.4.0-4.fc36                                          updates
perl-Git.noarch                                                              2.37.2-1.fc36                                           updates
perl-Scalar-List-Utils.x86_64                                                5:1.63-489.fc36                                         updates
python3-pytz.noarch                                                          2022.2-1.fc36                                           updates
zlib.i686                                                                    1.2.11-32.fc36                                          updates
zlib.x86_64                                                                  1.2.11-32.fc36                                          updates
zlib-devel.x86_64                                                            1.2.11-32.fc36                                          updates
19

You are way out of date on the kernel you are running (5.18.5) with the current at 5.18.17, as well as the other software you listed. I always suggest that the first step to trouble shooting is an update dnf upgrade --refresh followed by a reboot then test to see if the problem remains. Software updates are usually bug fixes and enhancements.

Others have had issues with the card you show but the update should be done first before going any further down that rabbit hole.

20

I am running Fedora on a Thinkpad E14 with Kernel 5.18.16-200.fc36.x86_64. Thinking it might be a kernel issue, I also tried an older kernel 5.18.5-200.fc36.x86_64 which did not work.

At the start of this post, I mentioned that the update took me to Kernel 5.18.16. Since the issue started here, I suspected a kernel regression. Hence I tried out an older kernel which used to work previously.

Anyways, I will try the latest kernel with all the updates applied and get back here.