F38 is acting strange. ( wifi disappears, can't power off from gui, multiple error msgs after force power off and etc)

Wi-Fi disappears after a while when I run Scp:sl (steam, proton 7.0-6) game. When I press the power button from the menu nothing happens. When I try to press that button again, it suddenly disappears along with the Wi-Fi. The only thing left is the logout button, which doesn’t work.

Sometimes my system completely freezes and I’m left with no other choice but force reboot.
After that, everything seems to be fine except lots of unexpected system errors popping in


first i thought issue was in nvidia drivers. So i tried to update by the recommended way, but it doesn’t solve the issue…

output from journalctl -b -k

Jun 07 23:44:15 ainpc kernel: iwlwifi 0000:00:14.3: base HW address: 8c:55:4a:37:ef:a1
Jun 07 23:44:16 ainpc kernel: iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
Jun 07 23:44:16 ainpc kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jun 07 23:44:16 ainpc kernel: Bluetooth: BNEP filters: protocol multicast
Jun 07 23:44:16 ainpc kernel: Bluetooth: BNEP socket layer initialized
Jun 07 23:44:16 ainpc kernel: NET: Registered PF_QIPCRTR protocol family
Jun 07 23:44:16 ainpc kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Jun 07 23:44:17 ainpc kernel: RPC: Registered named UNIX socket transport module.
Jun 07 23:44:17 ainpc kernel: RPC: Registered udp transport module.
Jun 07 23:44:17 ainpc kernel: RPC: Registered tcp transport module.
Jun 07 23:44:17 ainpc kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jun 07 23:44:17 ainpc kernel: nvidia: loading out-of-tree module taints kernel.
Jun 07 23:44:17 ainpc kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 07 23:44:17 ainpc kernel: Disabling lock debugging due to kernel taint
Jun 07 23:44:17 ainpc kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Waiting for firmware download to complete
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Firmware loaded in 1610304 usecs
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Waiting for device to boot
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Device booted in 14613 usecs
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Jun 07 23:44:17 ainpc kernel: Bluetooth: hci0: Firmware revision 0.4 build 144 week 11 2023
Jun 07 23:44:17 ainpc kernel: Bluetooth: MGMT ver 1.22
Jun 07 23:44:17 ainpc kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 510
Jun 07 23:44:17 ainpc kernel: 
Jun 07 23:44:17 ainpc kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
Jun 07 23:44:17 ainpc kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
Jun 07 23:44:17 ainpc kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  530.41.03  Thu Mar 16 19:48:20 UTC 2023
Jun 07 23:44:17 ainpc kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Jun 07 23:44:17 ainpc kernel: nvidia-uvm: Loaded the UVM driver, major device number 508.
Jun 07 23:44:17 ainpc kernel: Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
Jun 07 23:44:17 ainpc kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  530.41.03  Thu Mar 16 19:23:04 UTC 2023
Jun 07 23:44:17 ainpc kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Jun 07 23:44:17 ainpc kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20221020/nsarguments-61)
Jun 07 23:44:17 ainpc kernel: r8169 0000:03:00.0 enp3s0: Link is Down
Jun 07 23:44:18 ainpc kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
Jun 07 23:44:19 ainpc kernel: rfkill: input handler disabled
Jun 07 23:44:20 ainpc kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 07 23:44:20 ainpc kernel: Bluetooth: RFCOMM socket layer initialized
Jun 07 23:44:20 ainpc kernel: Bluetooth: RFCOMM ver 1.11
Jun 07 23:44:22 ainpc kernel: wlo1: authenticate with a4:81:7a:25:e1:69
Jun 07 23:44:22 ainpc kernel: wlo1: 80 MHz not supported, disabling VHT
Jun 07 23:44:22 ainpc kernel: wlo1: send auth to a4:81:7a:25:e1:69 (try 1/3)
Jun 07 23:44:22 ainpc kernel: wlo1: authenticated
Jun 07 23:44:22 ainpc kernel: wlo1: associate with a4:81:7a:25:e1:69 (try 1/3)
Jun 07 23:44:22 ainpc kernel: wlo1: RX AssocResp from a4:81:7a:25:e1:69 (capab=0x1411 status=0 aid=1)
Jun 07 23:44:22 ainpc kernel: wlo1: associated
Jun 07 23:44:22 ainpc kernel: wlo1: Limiting TX power to 20 (20 - 0) dBm as advertised by a4:81:7a:25:e1:69
Jun 07 23:44:22 ainpc kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
Jun 07 23:44:33 ainpc systemd-journald[592]: File /var/log/journal/189f3d96b6184a1cb456afd839c009f8/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
Jun 07 23:44:33 ainpc kernel: rfkill: input handler enabled
Jun 07 23:44:35 ainpc kernel: warning: `pool-gnome-shel' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Jun 07 23:44:35 ainpc kernel: rfkill: input handler disabled

output from inxi -Fx

System:
  Host: ainpc Kernel: 6.3.5-200.fc38.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 2.39-9.fc38 Desktop: GNOME v: 44.1 Distro: Fedora release
    38 (Thirty Eight)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming F15 FX506LI_FX506LI
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FX506LI v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: FX506LI.310 date: 11/26/2021
Battery:
  ID-1: BAT1 charge: 41.3 Wh (100.0%) condition: 41.3/48.2 Wh (85.6%)
    volts: 12.6 min: 11.9 model: ASUS A32-K55 status: full
CPU:
  Info: quad core model: Intel Core i5-10300H bits: 64 type: MT MCP
    arch: Comet Lake rev: 2 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 2300 high: 2500 min/max: 800/4500 cores: 1: 2500 2: 2500
    3: 2500 4: 900 5: 2500 6: 2500 7: 2500 8: 2500 bogomips: 39999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: ASUSTeK driver: i915
    v: kernel arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: ASUSTeK
    driver: nvidia v: 530.41.03 arch: Turing bus-ID: 01:00.0
  Device-3: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    bus-ID: 1-7:4
  Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: dri: iris gpu: i915
    resolution: 1920x1080~144Hz
  API: OpenGL v: 4.6 Mesa 23.1.1 renderer: Mesa Intel UHD Graphics (CML GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3
  Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 01:00.1
  Device-3: C-Media USB Audio Device
    driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 1-2:3
  API: ALSA v: k6.3.5-200.fc38.x86_64 status: kernel-api
  Server-1: PipeWire v: 0.3.71 status: active
Network:
  Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3
  IF: wlo1 state: up mac: 8c:55:4a:37:ef:a1
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 03:00.0
  IF: enp3s0 state: down mac: f0:2f:74:9f:61:84
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB
    bus-ID: 1-14:5
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 62.45 GiB (13.1%)
  ID-1: /dev/nvme0n1 vendor: Micron model: 2210 MTFDHBA512QFD
    size: 476.94 GiB temp: 38.9 C
Partition:
  ID-1: / size: 475.35 GiB used: 62.14 GiB (13.1%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 302.4 MiB (31.1%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 475.35 GiB used: 62.14 GiB (13.1%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 7.58 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 50.0 C pch: 59.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 351 Uptime: 15m Memory: available: 7.58 GiB
  used: 2.72 GiB (35.9%) Init: systemd target: graphical (5) Compilers:
  gcc: 13.1.1 Packages: 39 note: see --rpm Shell: Bash v: 5.2.15 inxi: 3.3.27

output from lspci | grep VGA

00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1)

output from modinfo -F version nvidia

530.41.03

Sorry if i’ve made some mistakes. This is first time i’m troubleshooting about system error. So i tried to provide as much necessary info as possible. Thanks for patience :smiley:

Of course at this point nothing can be said for sure. But what you elaborate sounds to me like two different problems (GNOME buttons / Freezes). I cannot help with GNOME.


Generally, have the issues appeared at the same time? For how long do you have them? Are there any other links / correlations between the two issues?


At least concerning the freezes:

Kernel 6.3.6 has been pushed to stable a few hours ago and should be in your daily updates soon. Can you please update to kernel 6.3.6 and check if the problem persists?

It contains fixes with regards to nvidia. Maybe this already solves at least the freezing issues.

If you want to test 6.3.6 immediately, you can already do that now by following my explanation here: Fedora hangs on boot after upgrading to kernel 6.3.4 - #37 by py0xc3 . Otherwise, just wait a day or two. Then, it should be in your daily updates.

Additionally, if 6.3.6 does not help, please provide the output of journalctl --boot=-1 immediately after you had a freeze (the -1 is important to get the logs of the then-last boot, so the frozen boot). Feel free to anonymize data you consider private (usernames, MAC/IP addresses, …)

Thanks for your response. :smiley: I’ve updated my system via dnf update and so far it seems like it solved the issue!

Happy to hear that :wink: kernel 6.3.6 was already pushed to stable, so I guess it was already contained in your updates. It would have been interesting to know what the actual origin of the issue was (and which update(s) it actually solved), but if it works now, I guess we can close the topic with dnf update.

Feel free to mark a solution for other users.