Cannot access internet on WiFi connection

I’m running Fedora 41 on an Acer Spin 7 laptop.

At some point (I cannot think of any discernible cause) I started having problems accessing the internet over my home WiFi network. If I boot my laptop (or wake it from suspension), it can connect to the router with no issues, but it often fails to access the internet over the connection (indicated by the question mark over the signal strength bars). Other devices connected to WiFi have no issues what so ever.

I can temporarily “solve” the problem by forgetting the network and reconnecting to it, although this doesn’t work consistently. Sometimes the problem suddenly “fixes” itself after a while, and internet access is restored. Then everything works fine until I shut down or suspend my laptop.

I tried troubleshooting this issue relying on online guides, but I’m not sure what point is since everything works fine when it is working, and simply doesn’t when it isn’t. There doesn’t seem to be any logic to it.

Any help will be much appreciated.

Post the output from an inxi -Fzxx so we can see your specs and what kind of networking chipset you are using. (Stick it in pre-formatted text block` so it’s easy to read and gets indexed nicely for other people dealing with similar issues.)

Then we can try disabling power management for the Wi-Fi card and see if we can stabilise things somewhat.

I would also suggest checking you have the latest firmware installed via fwupdmgr just in case there’s a known issue with your Wi-Fi chipset.

Thanks for your reply.

I put the output of inxi -Fzxx below.

I set the Power Mode to “Performance”, not sure if that’s what you meant with disabling power management .

Checking with fwupdmgr gives no available firmware updates.

System:
  Kernel: 6.12.7-200.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-5.fc41
  Desktop: GNOME v: 47.2 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 41 (Workstation Edition)
Machine:
  Type: Laptop System: Acer product: Spin SP714-51 v: V1.12
    serial: <superuser required>
  Mobo: Acer model: Dino_KL v: V1.12 serial: <superuser required>
    part-nu: Spin SP714-51_1138_1.12 UEFI-[Legacy]: Insyde v: 1.12
    date: 04/05/2017
Battery:
  ID-1: BAT1 charge: 15.0 Wh (49.8%) condition: 30.1/42.7 Wh (70.6%)
    volts: 16.5 min: 15.4 model: SIMPLO T99N serial: <filter> status: charging
CPU:
  Info: dual core model: Intel Core i7-7Y75 bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
    L3: 4 MiB
  Speed (MHz): avg: 3597 min/max: 400/3600 cores: 1: 3597 2: 3597 3: 3597
    4: 3597 bogomips: 12799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 615 vendor: Acer Incorporated ALI driver: i915
    v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1 bus-ID: 00:02.0
    chip-ID: 8086:591e
  Device-2: Chicony HD WebCam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-7:3 chip-ID: 04f2:b5d0
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0x323d res: 1920x1080 dpi: 158
    diag: 354mm (13.9")
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.3.2 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel HD Graphics 615 (KBL GT2)
    device-ID: 8086:591e display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
  API: ALSA v: k6.12.7-200.fc41.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Lite-On driver: ath10k_pci v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 01:00.0 chip-ID: 168c:003e temp: 47.0 C
  IF: wlp1s0 state: up mac: <filter>
Bluetooth:
  Device-1: Lite-On driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-9:4 chip-ID: 04ca:3016
  Report: btmgmt ID: hci0 rfk-id: 4 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 238.47 GiB used: 48.46 GiB (20.3%)
  ID-1: /dev/sda vendor: LITE-ON model: CV3-SD256 size: 238.47 GiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 237.47 GiB used: 48.16 GiB (20.3%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 973.4 MiB used: 309 MiB (31.7%) fs: ext4 dev: /dev/sda2
  ID-3: /home size: 237.47 GiB used: 48.16 GiB (20.3%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 7.62 GiB used: 17.2 MiB (0.2%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 58.0 C pch: 48.5 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.62 GiB used: 5.31 GiB (69.7%)
  Processes: 313 Power: uptime: 2h 41m wakeups: 1 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 8
    Compilers: N/A Shell: Bash v: 5.2.32 running-in: gnome-terminal inxi: 3.3.36

I would expect BIOS updates since 2017 — check the vendor’s site. There have been similar issues with linux wifi when other systems on the same access point were configured for “quality of service” to support streaming video.

You may get useful details using journalctl —no-hostname -b -g wifi|cat.

I was more angling towards turning off power saving for the wifi device itself - given that it apparently works and then ceases to work I’m guessing it’s power saving shutting down the device or putting it into a low power state which it struggles to recover from.

This is temporary, so you can try it to see if it makes any difference to your situation, given that it’s tricky for you to replicate the issue consistently. A reboot will reset whatever the powersave state is for this device, so bear that in mind.

Your device name will likely be different to mine, but here’s the sequence of commands I’ve just used on my desktop (and I don’t use wifi on here at all, so YMMV

╰─λ iw dev wlp6s0 get power_save
Power save: on

 ╭─steve@lurcher in ~ took 1ms
[⚡] × sudo iw dev wlp6s0 set power_save off
[sudo] password for steve: 

╭─steve@lurcher in ~ took 1ms
 ╰─λ iw dev wlp6s0 get power_save
Power save: off

Obviously, setting the power_save state back to on can be achieved with the relevant command.

ip link will give you the name of the device you can use with the iw command. So will iw of course but ip is easier to read I find.

GIve it a try, run some experiments, if you note no difference we can probably rule out power management and power saving from the mix