Wifi disapered after installing updates

Ask Fedora
1

Im running fedora 40, and i chose to install some of the updates the system wanted (system updates) and now there is no wifi option.

lspci -k shows
00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01)
Subsystem: Intel Corporation Device 0090
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

dmesg | grep iwl
[ 5.151995] iwlwifi 0000:00:14.3: enabling device (0000 → 0002)
[ 5.204878] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id 0x80400 wfpm id 0x80000020
[ 5.204927] iwlwifi 0000:00:14.3: PCI dev 51f1/0090, rev=0x370, rfid=0x2010d000
[ 5.204930] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz
[ 5.257045] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.42
[ 5.257527] iwlwifi 0000:00:14.3: loaded firmware version 89.202a2f7b.0 so-a0-gf-a0-89.ucode op_mode iwlmvm
[ 5.578402] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 5.578450] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 5.578459] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[ 5.578468] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 5.579726] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[ 5.582242] iwlwifi 0000:00:14.3: loaded PNVM version 35148b80
[ 5.597697] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
[ 5.666804] iwlwifi 0000:00:14.3: base HW address: 60:45:2e:49:b3:03
[ 5.700178] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[ 57.387079] iwlwifi 0000:00:14.3: RF_KILL bit toggled to disable radio.
[ 57.387090] iwlwifi 0000:00:14.3: reporting RF_KILL (radio disabled)

ip a
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
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether fc:5c:ee:62:9d:82 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.158/24 brd 192.168.0.255 scope global dynamic noprefixroute enp0s31f6
valid_lft 179550sec preferred_lft 179550sec
inet6 fe80::8afd:d529:3732:216c/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 60:45:2e:49:b3:03 brd ff:ff:ff:ff:ff:ff

2

I wonder if the WiFi device is just turned off somehow? Sometimes this is a small physical switch on the side of the laptop. It can also be a BIOS setting or it can often be toggled using one of the keyboard function keys.

3

Along that line, @gravballe what do you get in return when you run rfkill list from a terminal window?

You should be able to use rfkill unblock if the wireless device is listed as being soft blocked.

2 Likes
4

yes i thought os myself. But i have not change anything in bios, and the only wifi option i could find is to disable wifi, if there is ethernet. disabling that did nothing. I cant see any shortcuts on the keyboard to disable wifi, and there are no switches on the side of the machine (lenovo thinkpad t14)… it happened after a sw update but i guess its possible that activated some function? the wierd thing is, bluetooth is there, and usaly thats the same module

5

its not, its listed as hard blocked?

0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

if i remove the ethernet cable it removes the hard block but it does not show up as a device in settings…

0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

the weird thing is, wifi is not displayed at all in the settings list, but if i search i can find it. but it just says there are no wifi enabled. turning airplane mode on and off does nothing.

942×498 26 KB

996×611 32.5 KB

6

That is absolutely strange. It’s almost as if there is an aggressive power management profile that is managed via the BIOS in conjuction with tlp or power-profiles-daemon or tuned power management profile software, since hard blocked is not handled through rkfill toggle or rfkill block if I recall correctly.

7

Have you tried booting the previous version of the kernel?

2 Likes
8

i dont get an option to do that at boot? (no grub boot screen?)

9

I think holding the shift key down while booting is supposed to get it to show, but I’m not sure.

10

cant get any grub boot screen… i will try to google a bit on it… but i think i only have one kernel as uname -r only shows one

uname -r
6.11.3-200.fc40.x86_64

11

Is this system dual booting with windows?
If so then it seems possible that windows is disabling the wifi and causes it to be hard blocked in fedora. If that is the case then the wifi would need to be enabled in windows AND windows would need to have the fast startup disabled. I think that some have said the fast startup in windows by itself may disable wifi in fedora.

12

even if i turn off so that it should not disable wifi if there is ethernet, it does not show up, and there is nothing else in bios about wifi and power management. i seen some had problems becaus there was some power saving profile on the wifi that could be enabled in bios, but it does not seem to have this option on my laptop. the weird thing is, it was working just fine until i installed the awaiting updates, so … i guess it activated some function somehow

13

no there is only fedora 40 on this computer.

14

That is possible, but if that is the case, then booting to the previous kernel version should revert that behavior. Also, it would be a bug that should be reported.

Edit: uname -r only shows the version of the kernel you are currently running. Use rpm -q kernel to list all the installed kernel versions.

Hiding that boot menu is one of the more annoying things that Fedora did. I hope they change that back so it shows by default someday. Apparently some users didn’t like being presented with choices during startup. :confused:

15

that gives me

rpm -q kernel
kernel-6.9.5-200.fc40.x86_64
kernel-6.10.12-200.fc40.x86_64
kernel-6.11.3-200.fc40.x86_64

i cant get the grub menu to show, should i just edit the grub boot config ? is there a way to edit grub2 conf and make grub always show?

16

Yes, changing the grub config would be an option (that is what I would do, short of switching to a different boot loader). Unfortunately, I switched to a different boot loader so long ago that I no longer remember most of grub’s machinations. I think the setting should be in /etc/default/grub. But @computersavvy probably knows for sure.

17

You can use grubby to change the default kernel by running:

sudo grubby --set-default /boot/vmlinuz-6.10.9-200.fc40.x86_64

Replace 6.10.9-200 with the kernel version that you want to use.

1 Like
18

Hopefully that won’t leave the user forever stuck with that kernel version as they update their system. What I was suggesting was to change the config so the boot menu would show.

19

You can easily make the grub menu show during boot with the following command.
sudo grub2-editenv - unset menu_auto_hide
To restore the menu to hidden
sudo grub2-editenv - set menu_auto_hide=1

2 Likes
20

When a new version comes out, the installer will update the grub kernel list and select the new version. If you want to lock the version of kernels installed and not install new versions, you would need to install python3-dnf-plugin-versionlock and run sudo dnf versionlock add against kernel and possibly kernel-module. I typically also lock kernel-modules-core and kernel-core as well.

That will prevent newer kernel versions to be installed. I’ve been dealing with a kworker issue that popped up sometime between 6.10.10 and 6.11.3, which required me to pin grub to use 6.10.9 and not install newer kernel versions.

1 Like