When you say “Wifi driver exist”, how do you infer that (nmcli, applet, …)? [meanwhile inxi post appeared, that’s the hardware side]
Also, since you have “disappeared” in the title: It it was present and being used before, what has changed then? Just a regular update or an upgrade F43->F44 for example?
I had update a while back but no issue were there, I had not used my laptop for just 3 days, I go to open it today, ran sudo dnf update -y and it updated mostly as usual but crashed at the end after, from where I also could not get in to tty.
Was working in after the f44 update.
So the update hadn’t quite finished yet before the crash? In that case I’d try to undo or redo that update, which requires networking, of course. Do you have a chance to get networking via LAN?
Does nmcli device show a wifi device wl…?
If yes, then running journalctl -f during a connection attempt can give you some clues.
Updating and loading repositories:
Repositories loaded.
Failed to resolve the transaction:
Problem: The operation would result in removing the following protected packages: systemd-udev
Greta that you have connectivity. dnf history list | head shows you the most recent updates. Is the crashed one the most recent? I’d try to dnf history undo <ID> that one, or redo .
I assume 103 and 104 are rescue attempts. What is the 105 without desciption? In any case, dnf history info <ID> can tell you more, and dnf history rollback 101 would try to undo everything after 101.
So 105 was dnf install inxi but was recorded without description. Given which packages dnf would uninstall during rollback, I assume that dnf meta-data is borked due to the crash. dnf check may give some info, and dnf clean is at least worth trying.
NetworkManager-1:1.56.0-1.fc44.x86_64
duplicate with "NetworkManager-1:1.56.1-1.fc44.x86_64"
NetworkManager-1:1.56.1-1.fc44.x86_64
duplicate with "NetworkManager-1:1.56.0-1.fc44.x86_64"
NetworkManager-libnm-1:1.56.0-1.fc44.x86_64
duplicate with "NetworkManager-libnm-1:1.56.1-1.fc44.x86_64"
NetworkManager-libnm-1:1.56.1-1.fc44.x86_64
duplicate with "NetworkManager-libnm-1:1.56.0-1.fc44.x86_64"
SDL3-0:3.4.10-1.fc44.x86_64
.......
Check discovered 168 problem(s) in 165 package(s)
Transaction Summary:
Installing: 12 packages
Upgrading: 260 packages
Replacing: 261 packages
Removing: 59 packages
Total size of inbound packages is 2 GiB. Need to download 2 GiB.
After this operation, 235 MiB will be freed (install 5 GiB, remove 6 GiB).
Is this ok [y/N]: N
Operation aborted by the user.
It was trying to remove a lot of core packages, so I Aborted.
Running transaction
Transaction failed: Rpm transaction failed.
- file /usr/share/doc/libusb1/AUTHORS from install of libusb1-1.0.30-1.fc44.i686 conflicts with file from package libusb1-1.0.29-5.fc44.x86_64
- file /usr/share/doc/libusb1/ChangeLog from install of libusb1-1.0.30-1.fc44.i686 conflicts with file from package libusb1-1.0.29-5.fc44.x86_64
- file /usr/share/doc/libusb1/README from install of libusb1-1.0.30-1.fc44.i686 conflicts with file from package libusb1-1.0.29-5.fc44.x86_64
[sudo] password for codechini:
Updating and loading repositories:
Repositories loaded.
Problem: The operation would result in removing the following protected packages: systemd
Nothing to do.
Unsatisfied dependencies for systemd-libs-259.6-1.fc44.x86_64:
systemd-shared < 259.6-1.fc44 conflicts with (installed) systemd-libs-259.6-1.fc44.x86_64
Unsatisfied dependencies for systemd-shared-259.6-1.fc44.x86_64:
systemd-libs < 259.6-1.fc44 conflicts with (installed) systemd-shared-259.6-1.fc44.x86_64
Unsatisfied dependencies for systemd-259.6-1.fc44.x86_64:
(systemd-rpm-macros = 259.6-1.fc44 if rpm-build) is needed by (installed) systemd-259.6-1.fc44.x86_64
Issue got Auto resolved, Shut off my Laptop for 2-3 hrs, came back and started and wifi was working again.
Probably Running previous set of commands might have fixed it. nmcli device
nmcli device
DEVICE TYPE STATE CONNECTION
wlp2s0 wifi connected XXXX-SSID
br-42e076a3b3a7 bridge connected (externally) br-42e076a3b3a7
lo loopback connected (externally) lo
br-a8248a121b52 bridge connected (externally) br-a8248a121b52
docker0 bridge connected (externally) docker0
veth46b395e ethernet unmanaged --
.