I am experiencing a severe issue on my Asus TUF Gaming F15 running Fedora 42. Whenever I toggle the WiFi adapter to “On,” the entire system (UI, mouse, and keyboard) freezes instantly. Additionally, the system fails to shut down or reboot correctly at random times.
I want to update the system, but I don’t know how safe it is and how to do it the safest way.
alexbespik@fedora:~$ journalctl -b -1 -p 3
Feb 05 10:43:55 fedora kernel: x86/cpu: SGX disabled or unsupported by BIOS.
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol >
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_NOT_FOUND, During name lookup/cat>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
Feb 05 10:43:55 fedora kernel: ACPI BIOS Error (bug): Failure creating named ob>
Feb 05 10:43:55 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name looku>
lines 1-23
With regard to the wifi, the output you’ve posted is only the first 23 lines of error from the journal, and they are all harmless.
Open a terminal
Execute journalctl -f. You’ll see the last few lines of the current journal… you’re now following the end of the log, so any new entries will be displayed in that terminal in real time.
Toggle the Wifi, as you note in the description.
Hopefully you see some errors spewing out of the terminal - or at least something. There should be logging about the wifi going down, which you’d expect - is there anything else popped out which would give us a clue about why toggling wifi would cause the keyboard, mouse and from your description, the entire UI to lock up.
As for the upgrade, follow the upgrade instructions @theprogram posted and you should be fine.
Once you’re upgraded, post the output from inxi -Fzxx and we’ll work through the WiFi issue, if it is still a problem on F43.
There are a lot of threads on this forum about problems with that card and lack of support in linux.
The most often seen solution recommended is to replace it with a card that is supported. Intel wifi cards seem to almost always work OOTB.
On amazon those cards generally are only about $25
Feb 07 13:34:26 fedora systemd[1]: systemd-timedated.service: Deactivated successfully.
Feb 07 13:34:26 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 07 13:34:26 fedora audit: BPF prog-id=91 op=UNLOAD
Feb 07 13:34:26 fedora audit: BPF prog-id=90 op=UNLOAD
Feb 07 13:34:26 fedora audit: BPF prog-id=89 op=UNLOAD
Feb 07 13:34:28 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:29 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:30 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:30 fedora PackageKit[2544]: get-updates transaction /35084_cddebeda from uid 1000 finished with success after 339ms
Feb 07 13:34:31 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:32 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:32 fedora kernel: mt7921e 0000:04:00.0: chip reset failed
Feb 07 13:34:33 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:34 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:35 fedora PackageKit[2544]: get-updates transaction /35085_bcaeaecb from uid 1000 finished with success after 322ms
Feb 07 13:34:36 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:37 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:38 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:39 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:40 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:41 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:42 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:44 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:45 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:46 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:47 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:47 fedora systemd[1]: virtqemud.service: Deactivated successfully.
Feb 07 13:34:47 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=virtqemud comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 07 13:34:48 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:49 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:51 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:52 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:53 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:54 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:55 fedora kernel: mt7921e 0000:04:00.0: driver own failed
Feb 07 13:34:56 fedora kernel: mt7921e 0000:04:00.0: Timeout for driver own
Feb 07 13:34:56 fedora kernel: mt7921e 0000:04:00.0: chip reset failed
depending on your laptop model it could be easy. at worst are the models that have clips as well as screws, but its mostly confidence.
i remember when years ago i opened up my mac-mini and the instructions told me to get a paint scraper and shove it down in the machine. yours cant be worse than that!
if you do need another hand, ask around, you can get it done.
Is there a way to turn it off in the BIOS before it can cause a problem?
Currently I have a wireless conection and I don’t need Wifi. I also have usb wifi stick. Can I use it if I turn off the main wifi module?
Try booting with a kernel parameter pcie_aspm=off added.
You can do this as a one-off by hitting e at the grub screen and appending that pcie power management parameter to the kernel params. Stick it before rhgb quiet, then press F10 to boot that kernel with that parameter.
Once you get into the desktop, do your journalctl -f process again - do you still get the driver own failed messages and does your mouse/keyboard/system go into it’s locked solid state?
If that helps, we can add this permanently, but the sad truth is that many mediatek chipsets are just a bit crap on Linux and if you value your sanity, dropping a 20 euro on an intel chip or dongle is often the easiest and most reliable way to sanity.
