Wifi disapered after installing updates

computersavvy · October 17, 2024, 3:33pm

The command you suggest would leave the user with that kernel as default forever (or at least until grubby was used to change the default again)

This is why using the grub boot menu is a much better choice for most users.

theqlp · October 17, 2024, 3:34pm

It gets overriden when new versions of the kernel packages are installed. I’ve been dealing with that for a separate issue, so I know that from experience.

computersavvy · October 17, 2024, 3:40pm

I think you are mistaken.
Having a default set by using the exact file name remains and does not change.
Having a default index set does allow new kernel updates to be bumped in the index sequence.

I will try using your method with the next kernel update to verify my understanding.

gravballe · October 17, 2024, 3:40pm

i managed to boot from a 6.9 kernel with the grub command. thanks for that. sadley the isue is still there. Im gonna try booting from a live usb when i have put the kids to bed, and see if the isue is there.

glb · October 17, 2024, 3:45pm

If you haven’t done too many updates since this problem appeared, the next thing you could try is inspecting dnf history and using dnf history rollback to try to completely undo the update transaction that created the problem. I think you have to enable a non-standard repo for that to work (but I don’t remember how to do that off-hand). Also, you should take note of the list of package updates that are being reverted and, at some point, try to figure out which package is causing the problem and report it so it will get fixed. @computersavvy, can you provide instructions for how to run a dnf rollback?

Edit: Beyond that, it might be a firmware bug or a hardware failure. You can check your laptop vendor’s website for firmware updates. Booting from a live image might work to test if the hardware is the problem; especially if you have a live image that you know worked in the past.

theqlp · October 17, 2024, 4:06pm

On a test laptop that had been running 6.11.3, I used grubby to boot to 6.10.12, rebooted, saw that it was booting using 6.10.12, removed and re-installed kernel packages for 6.11.3, rebooted without running grubby to change anything, it was booting using 6.11.3.

gravballe · October 17, 2024, 4:12pm

i made a new usb with a fedora 40 on and used that as a live usb. wifi is working fine from that usb. so i guess that rules out any hidden bios options or switches i cant find on the machine

i will try and look through dnf history later when the kids are in bed. BUt im close to just take a backup of my .config folder and reinstall…

this is my dnf history

dnf history
ID | Command line | Date and time | Action(s) | Altered

20 |                           | 2024-10-16 23:44 | I, U           |   57   
19 |                           | 2024-10-16 23:12 | E, I, U        |  252  <
18 |                           | 2024-10-09 22:18 | E, I, U        |  461 ><
17 |                           | 2024-10-09 21:51 | E, I, U        |  700 >#
16 | install ulauncher         | 2024-07-10 13:04 | Install        |   10   
15 | remove sway               | 2024-07-10 12:40 | Removed        |   22   
14 |                           | 2024-07-10 12:33 | Install        |    1   
13 | install sway              | 2024-07-10 11:12 | Install        |   22   
12 |                           | 2024-07-10 11:02 | Install        |    8   
11 |                           | 2024-07-10 10:35 | Install        |    3   
10 | install dmenu             | 2024-07-10 10:31 | Install        |    1   
 9 | install snapd             | 2024-07-01 11:10 | Install        |    4 EE
 8 | install zsh               | 2024-07-01 08:40 | Install        |    1   
 7 | install pass              | 2024-06-28 14:36 | Install        |    4   
 6 |                           | 2024-06-27 13:41 | E, I, U        |  194   
 5 | install gnome-firmware    | 2024-06-27 08:53 | Install        |    1   
 4 | -y install --nogpgcheck - | 2024-06-27 08:50 | Install        |    1   
 3 | install displaylink       | 2024-06-27 08:49 | Install        |   65 E<
 2 |                           | 2024-06-23 22:07 | E, I, U        |  717 ><
 1 |                           | 2024-04-15 00:56 | Install        | 1952 >E

my guess is it happened either 10-09 or 10-16

glb · October 17, 2024, 4:21pm

dnf history info 20 should list what packages were updated on 2024-10-16. Take note of that somewhere, then try sudo dnf history rollback 20. If it says it cannot find some packages (likely), then you’ll need to install that archive repo first. Ideally, you should run the dnf rollback command from a virtual terminal while booted into a non-graphical mode (systemd calls it “multi-user.target” these days). But you will likely get away with running the rollback from GUI mode if you don’t feel up to booting to multi-user mode.

Edit: I’ve only use the rollback command once ever, so beware that I’m trying to guide you through a process that I’m not all that familiar with myself.

Edit2: I just glanced at some of the documentation for dnf history rollback, and I see that there are two variations – dnf history rollback <transaction#> and dnf history undo <transaction#>. Apparently rollback undoes all the transactions that were done between your current system state and the specified transaction whereas undo only undoes the specified transaction. You might need to use dnf history undo 20 after you’ve installed that archive repo to avoid uninstalling that archive repo as part of your package rollback.

Edit3: Here is some documentation that includes how to install that fedora-repos-archive: Fedora - dnf history with fedora-repos-archive | JOURNAL.ROBBI.MY

computersavvy · October 17, 2024, 4:50pm

I believe rollbacks can be done with the command you provided and enabling the updates-archive repo if not already enabled.
sudo dnf history rollback <transaction id> --enablerepo updates-archive
The command dnf repolist --all should show if the updates-archive repo is already installed and if it is disabled or enabled.

gravballe · October 17, 2024, 5:07pm

thanks for this… the history info 20 shows these packages

Packages Altered:
Install kernel-6.11.3-200.fc40.x86_64 Install kernel-core-6.11.3-200.fc40.x86_64 Install kernel-devel-6.11.3-200.fc40.x86_64 Install kernel-modules-6.11.3-200.fc40.x86_64 Install kernel-modules-core-6.11.3-200.fc40.x86_64 Install kernel-modules-extra-6.11.3-200.fc40.x86_64 Upgrade chrony-4.6.1-1.fc40.x86_64 Upgrade criu-4.0-1.fc40.x86_64 Upgrade criu-libs-4.0-1.fc40.x86_64 Upgrade epiphany-runtime-1:46.4-1.fc40.x86_64 Upgrade ethtool-2:6.11-1.fc40.x86_64 Upgrade firefox-131.0.2-1.fc40.x86_64 Upgrade firefox-langpacks-131.0.2-1.fc40.x86_64 Upgrade fmt-10.2.1-5.fc40.x86_64 Upgrade git-2.47.0-1.fc40.x86_64 Upgrade git-core-2.47.0-1.fc40.x86_64 Upgrade git-core-doc-2.47.0-1.fc40.noarch Upgrade kernel-devel-matched-6.11.3-200.fc40.x86_64 Upgrade kernel-headers-6.11.3-200.fc40.x86_64 Upgrade libblkid-2.40.2-1.fc40.x86_64 Upgrade libfdisk-2.40.2-1.fc40.x86_64 Upgrade libgsf-1.14.53-1.fc40.x86_64 Upgrade libgweather-4.4.4-1.fc40.x86_64 Upgrade libmount-2.40.2-1.fc40.x86_64 Upgrade libmysofa-1.3.2-3.20240917git2297 Upgrade libnbd-1.20.3-1.fc40.x86_64 Upgrade libopenmpt-0.7.10-1.fc40.x86_64 Upgrade libsmartcols-2.40.2-1.fc40.x86_64 Upgrade libuuid-2.40.2-1.fc40.x86_64 Upgrade libwnck3-43.1-1.fc40.x86_64 Upgrade mtools-4.0.45-1.fc40.x86_64 Upgrade nbdkit-1.38.5-1.fc40.x86_64 Upgrade nbdkit-basic-filters-1.38.5-1.fc40.x86_64 Upgrade nbdkit-basic-plugins-1.38.5-1.fc40.x86_64 Upgrade nbdkit-curl-plugin-1.38.5-1.fc40.x86_64 Upgrade nbdkit-selinux-1.38.5-1.fc40.noarch Upgrade nbdkit-server-1.38.5-1.fc40.x86_64 Upgrade nbdkit-ssh-plugin-1.38.5-1.fc40.x86_64 Upgrade perl-Git-2.47.0-1.fc40.noarch Upgrade python3-boto3-1.35.37-1.fc40.noarch Upgrade python3-botocore-1.35.37-1.fc40.noarch Upgrade python3-libmount-2.40.2-1.fc40.x86_64 Upgrade python3-s3transfer-0.10.3-1.fc40.noarch Upgrade systemd-255.13-1.fc40.x86_64 Upgrade systemd-container-255.13-1.fc40.x86_64 Upgrade systemd-libs-255.13-1.fc40.x86_64 Upgrade systemd-networkd-255.13-1.fc40.x86_64 Upgrade systemd-oomd-defaults-255.13-1.fc40.noarch Upgrade systemd-pam-255.13-1.fc40.x86_64 Upgrade systemd-resolved-255.13-1.fc40.x86_64 Upgrade systemd-rpm-macros-255.13-1.fc40.noarch Upgrade systemd-udev-255.13-1.fc40.x86_64 Upgrade toolbox-0.0.99.6-1.fc40.x86_64 Upgrade util-linux-2.40.2-1.fc40.x86_64 Upgrade util-linux-core-2.40.2-1.fc40.x86_64 Upgrade xen-libs-4.18.3-2.fc40.x86_64 Upgrade xen-licenses-4.18.3-2.fc40.x86_64 Upgraded kernel-6.8.5-301.fc40.x86_64 Upgraded kernel-core-6.8.5-301.fc40.x86_64 Upgraded kernel-modules-6.8.5-301.fc40.x86_64 Upgraded kernel-modules-core-6.8.5-301.fc40.x86_64 Upgraded kernel-modules-extra-6.8.5-301.fc40.x86_64 Upgraded chrony-4.6-1.fc40.x86_64 Upgraded criu-3.19-4.fc40.x86_64 Upgraded criu-libs-3.19-4.fc40.x86_64 Upgraded epiphany-runtime-1:46.3-1.fc40.x86_64 Upgraded ethtool-2:6.9-1.fc40.x86_64 Upgraded ethtool-2:6.10-1.fc40.x86_64 Upgraded firefox-131.0-2.fc40.x86_64 Upgraded firefox-langpacks-131.0-2.fc40.x86_64 Upgraded fmt-10.2.1-4.fc40.x86_64 Upgraded git-2.45.2-2.fc40.x86_64 Upgraded git-2.46.2-1.fc40.x86_64 Upgraded git-core-2.45.2-2.fc40.x86_64 Upgraded git-core-2.46.2-1.fc40.x86_64 Upgraded git-core-doc-2.45.2-2.fc40.noarch Upgraded git-core-doc-2.46.2-1.fc40.noarch Upgraded kernel-devel-matched-6.10.12-200.fc40.x86_64 Upgraded kernel-headers-6.9.4-200.fc40.x86_64 Upgraded kernel-headers-6.10.3-200.fc40.x86_64 Upgraded libblkid-2.40.1-1.fc40.x86_64 Upgraded libfdisk-2.40.1-1.fc40.x86_64 Upgraded libgsf-1.14.51-4.fc40.x86_64 Upgraded libgweather-4.4.2-1.fc40.x86_64 Upgraded libmount-2.40.1-1.fc40.x86_64 Upgraded libmysofa-1.2.1-7.fc40.x86_64 Upgraded libnbd-1.20.2-1.fc40.x86_64 Upgraded libopenmpt-0.7.8-1.fc40.x86_64 Upgraded libsmartcols-2.40.1-1.fc40.x86_64 Upgraded libuuid-2.40.1-1.fc40.x86_64 Upgraded libwnck3-43.0-8.fc40.x86_64 Upgraded mtools-4.0.44-1.fc40.x86_64 Upgraded nbdkit-1.38.4-1.fc40.x86_64 Upgraded nbdkit-basic-filters-1.38.2-1.fc40.x86_64 Upgraded nbdkit-basic-filters-1.38.4-1.fc40.x86_64 Upgraded nbdkit-basic-plugins-1.38.2-1.fc40.x86_64 Upgraded nbdkit-basic-plugins-1.38.4-1.fc40.x86_64 Upgraded nbdkit-curl-plugin-1.38.2-1.fc40.x86_64 Upgraded nbdkit-curl-plugin-1.38.4-1.fc40.x86_64 Upgraded nbdkit-selinux-1.38.4-1.fc40.noarch Upgraded nbdkit-server-1.38.2-1.fc40.x86_64 Upgraded nbdkit-server-1.38.4-1.fc40.x86_64 Upgraded nbdkit-ssh-plugin-1.38.2-1.fc40.x86_64 Upgraded nbdkit-ssh-plugin-1.38.4-1.fc40.x86_64 Upgraded perl-Git-2.45.2-2.fc40.noarch Upgraded perl-Git-2.46.2-1.fc40.noarch Upgraded python3-boto3-1.34.128-1.fc40.noarch Upgraded python3-boto3-1.35.29-1.fc40.noarch Upgraded python3-botocore-1.34.128-1.fc40.noarch Upgraded python3-botocore-1.35.29-1.fc40.noarch Upgraded python3-libmount-2.40.1-1.fc40.x86_64 Upgraded python3-s3transfer-0.10.1-1.fc40.noarch Upgraded python3-s3transfer-0.10.2-1.fc40.noarch Upgraded systemd-255.7-1.fc40.x86_64 Upgraded systemd-255.12-1.fc40.x86_64 Upgraded systemd-container-255.7-1.fc40.x86_64 Upgraded systemd-container-255.12-1.fc40.x86_64 Upgraded systemd-libs-255.7-1.fc40.x86_64 Upgraded systemd-libs-255.12-1.fc40.x86_64 Upgraded systemd-networkd-255.7-1.fc40.x86_64 Upgraded systemd-networkd-255.12-1.fc40.x86_64 Upgraded systemd-oomd-defaults-255.12-1.fc40.noarch Upgraded systemd-pam-255.7-1.fc40.x86_64 Upgraded systemd-pam-255.12-1.fc40.x86_64 Upgraded systemd-resolved-255.7-1.fc40.x86_64 Upgraded systemd-resolved-255.12-1.fc40.x86_64 Upgraded systemd-rpm-macros-255.7-1.fc40.noarch Upgraded systemd-udev-255.7-1.fc40.x86_64 Upgraded systemd-udev-255.12-1.fc40.x86_64 Upgraded toolbox-0.0.99.5-11.fc40.x86_64 Upgraded util-linux-2.40.1-1.fc40.x86_64 Upgraded util-linux-core-2.40.1-1.fc40.x86_64 Upgraded xen-libs-4.18.2-1.fc40.x86_64 Upgraded xen-libs-4.18.3-1.fc40.x86_64 Upgraded xen-licenses-4.18.2-1.fc40.x86_64 Upgraded xen-licenses-4.18.3-1.fc40.x86_64 @updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
dd8.fc40.x86_64 @updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@updates
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System
@@System

so i think with all those kernel ones i think it could be the one…

but when i try to do the role back with the repo added i get error

sudo dnf history rollback 20 --enablerepo updates-archive
Error: Unknown repo: ‘updates-archive’
sudo dnf history rollback 20 --enablerepo fedora-repos-archive
Error: Unknown repo: ‘fedora-repos-archive’

if i do it without it just says ok

sudo dnf history rollback 20
Last metadata expiration check: 0:08:40 ago on Thu 17 Oct 2024 06:58:40 PM CEST.
Dependencies resolved.
Nothing to do.
Complete!

glb · October 17, 2024, 5:24pm

The ethtool package might also be something that could cause the problem you are seeing.

If you don’t have that fedora-repos-archive package installed, try sudo dnf install fedora-repos-archive.

Especially since systemd is in the list of packages to be reverted, I would recommend doing the rollback from a VT and rebooting immediately after it finishes (really, you should always do package management that way, but some packages are more prone to problems than others and systemd is one of them). Use Ctrl+Alt+F3 (or F4, etc if something is already running on VT3). Sign in as root, then run runlevel to get a pair of values. The first value is the previous runlevel (or N if you haven’t switched runlevels since you booted). The second number is your current “runlevel” (they aren’t really runlevels anymore, but some of the terminology has carried over from earlier times). The second number is likely 5 in your case, which means that a GUI environment is running on your system (you can also see this in the output of systemctl status which will list all the programs that are running in the background). Run init 3 to switch to the multi-user target. If you re-run that runlevel command now, you should see 5 3, showing that your current “runlevel” is 3 and that the GUI software stack is no longer running in the background (you can also verify this with systemctl status). Once you are at a root prompt in multi-user mode, it will be safe to run the dnf history rollback command and then reboot the system. Note that your PC will likely “jump” back to VT1 after you run init 3. Just press Ctrl+Alt+F3 again to switch back to VT3 (or you could sign in on VT1 as root to complete the commands).

gravballe · October 17, 2024, 5:32pm

thanks that solved it, but doing roleback to 20, only removed the now added repo

sudo dnf history rollback 20
Last metadata expiration check: 0:01:03 ago on Thu 17 Oct 2024 07:29:32 PM CEST.
Dependencies resolved.
==============================================================================================================================================================================================================================================
Package Architecture Version Repository Size
==============================================================================================================================================================================================================================================
Removing:
fedora-repos-archive noarch 40-2 @updates 986

Transaction Summary

Remove 1 Package

doing one earlier i get error:

sudo dnf install fedora-repos-archive
Last metadata expiration check: 0:02:59 ago on Thu 17 Oct 2024 07:29:32 PM CEST.
Package fedora-repos-archive-40-2.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
sudo dnf history rollback 19
Last metadata expiration check: 0:03:01 ago on Thu 17 Oct 2024 07:29:32 PM CEST.
Error:
Problem 1: package nbdkit-basic-filters-1.38.4-1.fc40.x86_64 from updates-archive requires nbdkit-server(x86-64) = 1.38.4-1.fc40, but none of the providers can be installed

conflicting requests
Problem 2: package nbdkit-1.38.4-1.fc40.x86_64 from updates-archive requires nbdkit-basic-plugins(x86-64) = 1.38.4-1.fc40, but none of the providers can be installed
conflicting requests
Problem 3: package systemd-networkd-255.12-1.fc40.x86_64 from updates-archive requires systemd(x86-64) = 255.12-1.fc40, but none of the providers can be installed
package systemd-networkd-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so()(64bit), but none of the providers can be installed
package systemd-networkd-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so(SD_SHARED)(64bit), but none of the providers can be installed
conflicting requests
Problem 4: package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires systemd(x86-64) = 255.12-1.fc40, but none of the providers can be installed
package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so()(64bit), but none of the providers can be installed
package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so(SD_SHARED)(64bit), but none of the providers can be installed
package systemd-255.12-1.fc40.x86_64 from updates-archive requires systemd-libs(x86-64) = 255.12-1.fc40, but none of the providers can be installed
conflicting requests
Problem 5: package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires systemd(x86-64) = 255.12-1.fc40, but none of the providers can be installed
package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so()(64bit), but none of the providers can be installed
package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so(SD_SHARED)(64bit), but none of the providers can be installed
package systemd-255.12-1.fc40.x86_64 from updates-archive requires systemd-pam(x86-64) = 255.12-1.fc40, but none of the providers can be installed
package systemd-oomd-defaults-255.12-1.fc40.noarch from updates-archive requires systemd-udev = 255.12-1.fc40, but none of the providers can be installed
conflicting requests
Problem 6: package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires systemd(x86-64) = 255.12-1.fc40, but none of the providers can be installed
package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so()(64bit), but none of the providers can be installed
package systemd-udev-255.12-1.fc40.x86_64 from updates-archive requires libsystemd-shared-255.12-1.fc40.so(SD_SHARED)(64bit), but none of the providers can be installed
cannot install both systemd-255.7-1.fc40.x86_64 from updates-archive and systemd-255.12-1.fc40.x86_64 from updates-archive
package firefox-131.0-2.fc40.x86_64 from updates-archive requires u2f-hidraw-policy, but none of the providers can be installed
conflicting requests
(try to add ‘–allowerasing’ to command line to replace conflicting packages or ‘–skip-broken’ to skip uninstallable packages)

gravballe · October 17, 2024, 6:02pm

had to use
sudo dnf history rollback 19 --skip-broken

to get it to remove stuff… it made 100 changes, but wifi is still not working. I cant seem to go further back as im getting:

sudo dnf history rollback 17 --skip-broken

sudo dnf history rollback 17 --skip-broken
Last metadata expiration check: 1:02:20 ago on Thu 17 Oct 2024 06:58:40 PM CEST.
Transaction history is incomplete, before 19.
Transaction history is incomplete, after 18.
Error:
Problem: The operation would result in removing the following protected packages: kernel-core

so i guess its just easier to take a copy of .config and set everything up again. Kinda disapointed it could just kill wifi like that, as i was hoping i could use fedora 40 as my daily driver for work… is there a more suited desktop linux os if you cant afford these kinds of problems? without im to far behind in packages?

glb · October 17, 2024, 6:05pm

You might try dnf downgrade ethtool and a reboot first just to see if that package is the problem. Otherwise, yeah, sorry. Personally, I set my system up to take automatic snapshots of the root filesystem just after every kernel update. Unfortunately, setting that up is a complicated procedure. Maybe Fedora will ship that configuration someday.

You can use dnf downgrade <packagename> for any other packages that you think might be suspect as well. The dnf downgrade command reverts to the package versions that are in the original fedora repo (basically what versions were available when your version of Fedora Linux was released). It doesn’t depend on the archives repo.

glb · October 17, 2024, 6:12pm

That is sort of the tradeoff. On important server systems that I run, I tend to hold back to the previous release of Fedora Linux (currently 39). Fedora “backports” important security updates to their N-1 release, so it is safe to run, and you might find that the N-1 release is a little more stable because it won’t receive as many potentially-breaking feature updates. (Though it is always possible that a security patch will break something.)

Also, on my server systems, I have configured automatic snapshots so I can easily and confidently revert things in case an update does have problems. But I installed everything on ZFS to get that. I have a script for installing Fedora Linux on ZFS. But it is designed for systems with multiple drives (generally not laptops). One of ZFS’s features is that it protects you from a disk failure by mirroring the data across multiple hard drives.

gravballe · October 17, 2024, 6:18pm

dnf downgrade ethtool did not solve it

we are mostly running redhat servers, and i hate manage them through windows and wsl, due to how hard the org has locked down the windows machines. So i got a laptop i could install fedora 40 on, as a prof of concept. Now that laptop has nuked its wificard during an update…

On our servers, i have set it up to do snapshot before everyupdate, but this is not a server. Its supposed to be a laptop for work… any way im just fustrated … Im thankfull for the time you guys spent helping… even though it seems it was wasted.

Topic		Replies	Views
Wi-Fi issues after updating from Fedora Workstation 41 to 42 Ask Fedora intel-wifi-card , wifi , intel , f42	16	1714	April 29, 2025
Wifi not showing any networks after an update a week ago Ask Fedora broadcom , wifi , macbook	5	405	December 27, 2024
Only after restart: Wlan connected but no Internet Ask Fedora f37 , networking , wifi	12	1476	March 30, 2023
Missing Intel(R) Wireless WiFi driver for Linux Ask Fedora	2	194	March 19, 2025
Wifi adapter not found after upgrade from 40 to 41 Ask Fedora f41	4	2096	December 16, 2024

Wifi disapered after installing updates

dnf history ID | Command line | Date and time | Action(s) | Altered

Transaction Summary

Related topics

dnf history
ID | Command line | Date and time | Action(s) | Altered