No wifi or wifi instability: xps 13 9380

I am having an issue with my wifi after upgrading to Fedora 38.

any help please


inxi -Fzxx
System:
  Kernel: 6.2.13-300.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.39-9.fc38 Desktop: GNOME v: 44.1 tk: GTK v: 3.24.37 wm: gnome-shell dm:
    1: GDM 2: SDDM note: stopped Distro: Fedora release 38 (Thirty Eight)
Machine:
  Type: Laptop System: Dell product: XPS 13 9380 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0KTW76 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.24.0 date: 03/13/2023
Battery:
  ID-1: BAT0 charge: 5.2 Wh (98.1%) condition: 5.3/52.0 Wh (10.1%) volts: 8.8
    min: 7.6 model: LGC-LGC6.73 DELL H754V96 serial: <filter> status: charging
CPU:
  Info: quad core model: Intel Core i7-8565U bits: 64 type: MT MCP
    arch: Comet/Whiskey Lake note: check rev: C cache: L1: 256 KiB L2: 1024 KiB
    L3: 8 MiB
  Speed (MHz): avg: 1193 high: 2000 min/max: 400/4600 cores: 1: 700 2: 2000
    3: 700 4: 746 5: 703 6: 700 7: 2000 8: 2000 bogomips: 31999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell
    driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1
    empty: DP-1,DP-2,DP-3 bus-ID: 00:02.0 chip-ID: 8086:3ea0
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-5:2 chip-ID: 0c45:6723
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 res: 3840x2160 size: N/A
  API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel UHD Graphics 620 (WHL
    GT2) direct-render: Yes
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9dc8
  API: ALSA v: k6.2.13-300.fc38.x86_64 status: kernel-api
  Server-1: PipeWire v: 0.3.70 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: Rivet Networks Killer 1435 Wireless-AC driver: ath10k_pci v: kernel
    pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:003e
  IF: wlp1s0 state: down mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: enp0s20f0u6 state: unknown speed: -1 duplex: half mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai type: USB driver: btusb v: 0.8 bus-ID: 1-7:3
    chip-ID: 0489:e0a2
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 358.02 GiB (75.1%)
  ID-1: /dev/nvme0n1 vendor: Toshiba model: KXG60ZNV512G NVMe 512GB
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 49.9 C
Partition:
  ID-1: / size: 475.35 GiB used: 357.66 GiB (75.2%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 296.4 MiB (30.4%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 76.6 MiB (12.8%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 475.35 GiB used: 357.66 GiB (75.2%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 64.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 396 Uptime: 37m Memory: 15.38 GiB used: 6.61 GiB (43.0%)
  Init: systemd v: 253 target: graphical (5) default: graphical Compilers:
  gcc: 13.1.1 clang: 16.0.1 Packages: pm: rpm pkgs: N/A note: see --rpm
  pm: flatpak pkgs: 2 Shell: Bash v: 5.2.15 running-in: terminator
  inxi: 3.3.26

and my rfkill shows

 rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 wlan      phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked


Linux Hardware probe 5bb7561235 has some probes for recent disto versions, but not all working:

Driver is not found or not configured. The device is supported by kernel versions 4.0 and newer. You are [SIC] probably need to configure system for the device to work properly (modify kernel config, install firmware, etc.).

The probe has the full device id as pci%3A168c-003e-1a56-143a. This card should be supported by the ath10k_pci module and would use firmware found under /lib/firmware/ath10k/. Use logctrl to see if there are errors attempting to load ath10k_pci. Dell Killer Wireless Firmware Update Guide suggests:

Open /lib/firmware/ath10k/QCA6174/HW3.0 and rename file: firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 To: firmware-4.bin

I would only try this if an error message indicated that firmware-4.bin was not found.

Github ath10k-firmware has links to support resources.

Thanks
for some strange reason, the file firmware-4.bin.xz was not decompressed in /lib/firmware/ath10k/QCA6174/HW3.0 . so I just decompressed it with a xz -d firmware-4.bin.xz and the wifi started working.

Glad you got it working. Compress Kernel Firmware in Fedora indicates that the kernel should handle .xz compressed files so a bug report is in order.

I realized it just connect for 30 min then disconnect again :frowning:
is it supposed to come as .xz file ?

]$ cd /lib/firmware/at
ath10k/    ath11k/    ath6k/     ath9k_htc/ atmel/     atusb/     
[ Desktop]$ cd /lib/firmware/ath10k/
[ath10k]$ ls
QCA4019  QCA6174  QCA9377  QCA9887  QCA9888  QCA988X  QCA9984  QCA99X0  WCN3990
[ath10k]$ cd QCA6174/
[QCA6174]$ ls 
hw2.1  hw3.0
[QCA6174]$ cd hw3.0/
[hw3.0]$ ls
board-2.bin.xz  board.bin.xz  firmware-4.bin.xz  firmware-6.bin.xz  firmware-sdio-6.bin.xz  notice_ath10k_firmware-4.txt.xz  notice_ath10k_firmware-6.txt.xz  notice_ath10k_firmware-sdio-6.txt.xz
[ hw3.0]$ 

All drivers now come .xz compressed, but the uncompressed version should also work. It appears that something else is causing wifi to fail. You need to look carefully in journalctl for error messages associated with wifi or ath10k.

Were you using the computer before wifi went away? Linux now defaults to settings that minimize power consumption when the system is idle. If wifi was shut off to save power that should appear in journalctl, but doesn’t explain why if has been failing at boot time.

Yes, my dmesg -w returns

[38429.780799] RSP: 0018:ffffbb148043f998 EFLAGS: 00010246
[38429.780801] RAX: 0000000000000000 RBX: ffff9af3bbad08e0 RCX: ffff9af3bbad1c88
[38429.780802] RDX: 0000000080000000 RSI: ffff9af3f973acc0 RDI: ffff9af3bbad08e0
[38429.780803] RBP: ffff9af3f973acc0 R08: ffff9af3f973acf0 R09: ffffbb148043f7e0
[38429.780804] R10: 0000000000000003 R11: ffffffffb51447c8 R12: ffff9af3b5e0d860
[38429.780806] R13: ffff9af3f973ad18 R14: ffff9af3bbad1b10 R15: ffff9af3b5e0c9c0
[38429.780807] FS:  0000000000000000(0000) GS:ffff9af71e440000(0000) knlGS:0000000000000000
[38429.780808] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[38429.780810] CR2: 00007f8255825000 CR3: 0000000395010005 CR4: 00000000003706e0
[38429.780811] Call Trace:
[38429.780812]  <TASK>
[38429.780813]  ieee80211_free_chanctx+0x91/0xc0 [mac80211]
[38429.780879]  __ieee80211_link_release_channel+0xea/0x120 [mac80211]
[38429.780944]  ieee80211_link_release_channel+0x3b/0x50 [mac80211]
[38429.781008]  ieee80211_set_disassoc+0x38e/0x620 [mac80211]
[38429.781079]  ieee80211_mgd_deauth+0x13b/0x3d0 [mac80211]
[38429.781143]  ? __pfx_ieee80211_deauth+0x10/0x10 [mac80211]
[38429.781199]  cfg80211_mlme_deauth+0xb6/0x1d0 [cfg80211]
[38429.781251]  cfg80211_mlme_down+0x61/0x80 [cfg80211]
[38429.781303]  cfg80211_disconnect+0x17c/0x1f0 [cfg80211]
[38429.781356]  cfg80211_netdev_notifier_call+0x13d/0x4b0 [cfg80211]
[38429.781393]  ? vprintk_emit+0x11d/0x290
[38429.781397]  ? _printk+0x60/0x80
[38429.781400]  ? drv_remove_interface+0x110/0x120 [mac80211]
[38429.781442]  ? __warn+0x97/0x130
[38429.781445]  ? drv_remove_interface+0x110/0x120 [mac80211]
[38429.781487]  ? report_bug+0x18d/0x1c0
[38429.781490]  ? prb_read_valid+0x17/0x20
[38429.781492]  ? ieee80211_iter_chan_contexts_atomic+0x23/0x60 [mac80211]
[38429.781557]  ? common_interrupt+0xc6/0xd0
[38429.781560]  ? asm_common_interrupt+0x22/0x40
[38429.781563]  ? rtnl_is_locked+0x11/0x20
[38429.781566]  ? inetdev_event+0x39/0x670
[38429.781568]  ? _raw_spin_lock_irqsave+0x23/0x50
[38429.781571]  ? _raw_spin_unlock_irqrestore+0x23/0x40
[38429.781574]  raw_notifier_call_chain+0x41/0x60
[38429.781576]  __dev_close_many+0x5f/0x110
[38429.781580]  dev_close_many+0x8b/0x140
[38429.781583]  dev_close+0x7f/0xb0
[38429.781585]  cfg80211_shutdown_all_interfaces+0x49/0xf0 [cfg80211]
[38429.781623]  ieee80211_restart_work+0x11c/0x150 [mac80211]
[38429.781663]  process_one_work+0x1c4/0x3d0
[38429.781667]  worker_thread+0x4d/0x380
[38429.781671]  ? __pfx_worker_thread+0x10/0x10
[38429.781674]  kthread+0xe6/0x110
[38429.781676]  ? __pfx_kthread+0x10/0x10
[38429.781679]  ret_from_fork+0x29/0x50
[38429.781683]  </TASK>
[38429.781684] ---[ end trace 0000000000000000 ]---
[38429.781697] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5)
[38432.925871] ath10k_pci 0000:01:00.0: failed to read firmware dump area: -16
[38432.925877] ath10k_pci 0000:01:00.0: Copy Engine register dump:
[38433.050900] ath10k_pci 0000:01:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[38433.175586] ath10k_pci 0000:01:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[38433.300250] ath10k_pci 0000:01:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[38433.362606] ath10k_warn: 153 callbacks suppressed
[38433.362611] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035044: -110
[38433.393796] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035040: -110
[38433.424997] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035048: -110
[38433.424999] ath10k_pci 0000:01:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[38433.456175] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x0003543c: -110
[38433.487353] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035444: -110
[38433.518524] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035440: -110
[38433.549684] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035448: -110
[38433.549686] ath10k_pci 0000:01:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[38433.580850] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x0003583c: -110
[38433.612015] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035844: -110
[38433.643178] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x00035840: -110
[38433.674340] ath10k_pci 0000:01:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[38433.799042] ath10k_pci 0000:01:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[38433.923703] ath10k_pci 0000:01:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[38433.927530] ------------[ cut here ]------------
[38433.927534] WARNING: CPU: 1 PID: 92 at net/mac80211/driver-ops.c:38 drv_stop+0xf1/0x100 [mac80211]

I think there is a bug somewhere

Did a kernel upgrade and everything seems to work well so far

sudo dnf -y copr enable @kernel-vanilla/mainline
sudo dnf upgrade 'kernel*'

Please tell us what kernel release was installed that now works.

It worked for a short time then went off. I think it s a Dell issue
or the Rivet Networks Killer 1435 Wireless-AC is not well maintained at the moment
so I lost hope probably will get a more reliable laptop

It won’t be easy to improve on your current model. Prices on new ultraportables are good now because many of us don’t have much spare cash, but it often takes a year or two to have mature linux drivers. PC Mag Review said: "Earning our highest recommendation and a rare five-star rating, the XPS 13 (9380) is, indisputably, the best ultraportable laptop you can buy. "

Your specs have:

inxi -Fzxx
[...]
Battery:
  ID-1: BAT0 charge: 5.2 Wh (98.1%) condition: 5.3/52.0 Wh (10.1%) volts: 8.8
    min: 7.6 model: LGC-LGC6.73 DELL H754V96 serial: <filter> status: charging

[...]
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Rivet Networks Killer 1435 Wireless-AC driver: ath10k_pci v: kernel
    pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:003e
[...]

Some  9380 models have Killer 1435-S model wifi (Intel 9260).      

Your battery seems to be at 10%, but battery performance is complicated and older batteries often have high internal resistance that causes voltage drops during load spikes, nad would explain your issue.  A weak battery may cause glitches when wifi
starts, even if AC power is connected, especially with the smaller AC adapters supplied
with ultraportables.  

Ultraportables weaknesses are batteries and the ability to upgrade wifi, memory, and storage.   Ifixit calls replacing the battery and SSD replacement an "easy" update, while replacing the wifi card is "moderately" difficult.

[quote="Jules I., post:1, topic:81810, username:julesbs"]

vendor: Rivet Networks Killer 1435 Wireless-AC driver: ath10k_pci v: kernel
pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:003e

[/quote]

Dell's manual says:
> The memory modules are integrated on the system board. If the memory modules are malfunctioning and need to be replaced, a replacement of the system board is necessary. 

> The 2280 and 2230 [128GB] solid-state-drives each have a unique thermal plate. The thermal plates cannot be interchanged. 

If you started with 128GB, you could be encountering a cooling issue with your SSD.

Thanks for the reply, I am thinking of purchasing a USB wifi card most compatible with Linux :slight_smile: Any advise on one

There are several sites that collect information on devices running in Linux. You need to consider your use case. Which of the bands: 2.4 GHz, 5 GHz and 6 GHz (WiFi 6E) do you need? USB adapters range from those with big antennas so you can connect to a distant access point to a tiny cheap 2.4 GHz dongle for low-bandwidth, short-distance connections.

https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md

You can cross check these against reports at the level of not-detected, not working, and working for some definition of “working” at https://linux-hardware.org.

https://wiki.debian.org/WiFi#Availability_of_compatible_WiFi_chipsets

Beware of cheap USB dongles that don’t specify the chipset – some vendors sell multiple chipsets under the same model name.

2 Likes

Thanks George,
I am purchasing one of those dongle as a back up but

I finally got the wireless working by downgrading to Fedora 37 and downgrading the kernel to 6.0.7

from now on I will exclude any kernel update :slight_smile:

You could miss the update that fixes your wifi, but I suspect the majority of 9380 linux users opted for Intel wifi or there would be more users with the issue. There are some many changes going into linux that it is hard to find out when an issue that affects your gets fixed.

You could try a f38 LTS 6.1 kernel from Fedora Vanilla Repositories.

I think it is just my laptop getting old cause with the old kernel the wireless worked for like an hour then go back to not working so I decided to purchase an external card :slight_smile: atlast