You are not logged in.
Hello,
I was waiting for Kernel 5.10.4 with ath11k module included with impatience to make wifi working in my DELL XPS 9500 (I9 version)... But it doesn't work...
For 2 months, I was waiting for the kernel version and the inclusion of ath11k module... I saw that on these articles :
https://medium.com/@tomas.heiskanen/del … f1c218e78a
https://askubuntu.com/questions/1280328 … rs-support
And this module is en 5.10.4 : https://lwn.net/Articles/841473/
Can anybody help me ?
Offline
Same with me. I have xps 9700 and atheros keller AX500-DBS. It worked for a while with kernel 5.10.1 and then it stopped again.
The kernel module ath11k_pci fails to load:
[ 5240.828931] ath11k_pci 0000:05:00.0: WARNING: ath11k PCI support is experimental!
[ 5240.829003] ath11k_pci 0000:05:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
[ 5240.829067] ath11k_pci 0000:05:00.0: failed to get 32 MSI vectors, only -28 available
[ 5240.829068] ath11k_pci 0000:05:00.0: failed to enable msi: -28
[ 5240.829080] ath11k_pci: probe of 0000:05:00.0 failed with error -28
I have also logged a bug a few days ago but but the holiday period would slow things down.
https://bugzilla.kernel.org/show_bug.cgi?id=210923
Also found this. Not sure if it is the same thing.
https://bugs.archlinux.org/task/69223
Offline
magare please try applying the patch from https://lore.kernel.org/ath11k/16051211 … urora.org/
Last edited by loqs (2021-01-06 06:09:06)
Offline
loqs, is it related to this patch ?
https://github.com/0day-ci/linux/commit … 21a4875e18
I would rather wait to get into the upstream and included in the next kernel rather than re-compiling the kernel every time there is a new kernel release.
Thanks.
Offline
Yes same patch. Sorry about that I linked to a response to the patch instead of the patch, fixed the link now.
If you test it and does not work for you, then you could report that rather than wait for the patch to be merged into 5.11 or 5.12 then back-ported only then to find it does not work for you.
You could also bisect backwards and find which commit caused the breakage.
Last edited by loqs (2021-01-06 06:10:23)
Offline
I also have problems with my XPS 9500 (i9) and the ath11k_pci driver. It sort of works (but with a slow connection) when I plug in a wifi dongle and then reboot; I can then remove the dongle and my QCA6390 works. Then it stops working after a suspend, and dmesg shows:
[51400.378622] ath11k_pci 0000:6c:00.0: wmi command 16387 timeout
[51400.378625] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[51400.378627] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-11
[...]
[174682.606130] ath11k_pci 0000:6c:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[174682.606136] ath11k_pci 0000:6c:00.0: failed to enable PMF QOS: (-108
Offline
Yes same patch. Sorry about that I linked to a response to the patch instead of the patch, fixed the link now.
If you test it and does not work for you, then you could report that rather than wait for the patch to be merged into 5.11 or 5.12 then back-ported only then to find it does not work for you.
You could also bisect backwards and find which commit caused the breakage.
Yep. Make sense. I will apply the patch and see if it works for me ..
Offline
Applying the patch did not fix the issue :-(
Offline
Same problem here. Thanks for testing! My workaround is to stay on 5.10.2 for now, which works most of the time.
Offline
That is not a solution though. The developers are too busy and nobody even looked at the bug I logged.
Unfortunately I don't believe this issue will be fixed in the next release 5.11.
Not sure what to do.
I love the laptop but I don't want to run Windows on it, so I will try to return it to DEL and get another one with a different WiFi card.
What a shame. Dell would normally support Linux but not this time .:-(
Offline
It works really fine on my XPS 9500 after a fresh boot. It only breaks after resuming from suspend, which is a shame but I hope it will get sorted soon.
Offline
That is not a solution though. The developers are too busy and nobody even looked at the bug I logged.
Unfortunately I don't believe this issue will be fixed in the next release 5.11.Not sure what to do.
ath11k is very new and 5.10 was the first kernel version that supports it. Therefore it is not surprising that the implementation is still buggy. I am very confident that the problems will be fixed in the next versions and it will work reliably in a few weeks or - bad case - months. It's annoying, but until then I can live with the old kernel version. I have a Dell XPS 9500 with i9 as well and I will definitely not return it.
Offline
Yes. I agree ath11k is still quite new and it will take some time to mature.I have been trying to make it work since November 2020 but I guess I need to be more patient.
Probably it will mature in kernel 5.12 for sure.
Beautiful laptop and I paid megabucks for it. Will keep it.
I will have to stick to Windowze meanwhile unfortunately.
Offline
After enabling Vt-D in BIOS and upgrading it to the latest version got a different error now
[ 2.267396] ath11k_pci 0000:05:00.0: WARNING: ath11k PCI support is experimental!
[ 2.267435] ath11k_pci 0000:05:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
[ 2.267455] ath11k_pci 0000:05:00.0: enabling device (0000 -> 0002)
[ 2.727171] ath11k_pci 0000:05:00.0: Respond mem req failed, result: 1, err: 0
[ 2.727172] ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-22
[ 7.880850] ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
[ 7.880859] ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
Not sure what is causing this, Probably not connected to the MSI vectors
Offline
Adding "memmap=12M\\\$20M" to the kernel fixed the issue as suggested by Kalle Valo
Last edited by magare (2021-01-27 03:33:07)
Offline
For those experiencing issues after suspending this can usually be worked around by writing a systemd service to unload your network components prior to suspending, then reload them after resuming. Hopefully that will make do for some users until the kernel catches up to this new adapter.
Offline
Yes I spent a few hours with this and got it working satisfactorily - previously I just had another USB Wifi adapter plugged in that did support resuming.
As #tbg says unloading/loading ath11k_pci before/after suspension will get it working most of the time. Following https://wiki.archlinux.org/index.php/Dell_XPS_13_(9310) and https://forum.endeavouros.com/t/cant-co … up/6294/14 gives you all the info you need. Key bits are making sure your laptop does indeed suspend (using the latest Manjaro 5.11 experimental kernel my 9700 hangs + needed hard reset. Downgraded back to 5.10) and also being aware that unloading ie modprobe -r ath11k_pci can take minutes...
When resuming the Dell sometimes can't reconnect/see the network so having a script that just bounces the ath11k_pci seems to help out with this too.
Last edited by smonty1 (2021-02-18 01:14:57)
Offline
I am not familiar with the new ath11k module(s). The ath10k driver uses 2 modules. They must be unloaded and loaded pre and post suspend in a specific order for the service to work properly.
Here is an example of a suspend service I wrote for the ath10k driver:
[Unit]
Description=Ath10k WiFi Restart Service
Before=sleep.target
StopWhenUnneeded=yes
[Service]
User=root
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/sudo -u $USER /bin/bash -lc 'nmcli networking off'
ExecStart=/usr/bin/sleep 1
ExecStart=/usr/bin/systemctl stop NetworkManager
ExecStart=/usr/bin/ip link set wlp3s0 down
ExecStart=/usr/bin/rmmod ath10k_pci
ExecStart=/usr/bin/sleep 1
ExecStartPost=/usr/bin/rmmod ath10k_core
ExecStop=/usr/bin/sleep 5
ExecStop=/usr/bin/modprobe ath10k_pci
ExecStop=/usr/bin/sleep 2
ExecStop=/usr/bin/modprobe ath10k_core
ExecStop=/usr/bin/sleep 2
ExecStop=/usr/bin/ip link set wlp3s0 up
ExecStop=/usr/bin/sleep 2
ExecStop=/usr/bin/systemctl start NetworkManager
ExecStop=/usr/bin/sleep 1
ExecStop=/usr/bin/sudo -u $USER /bin/bash -lc 'nmcli networking on'
ExecStop=/usr/bin/sleep 1
ExecStop=/usr/bin/sudo -u $USER /bin/bash -lc 'nmcli r wifi off'
ExecStop=/usr/bin/sleep 1
ExecStop=/usr/bin/sudo -u $USER /bin/bash -lc 'nmcli r wifi on'
[Install]
WantedBy=sleep.targetThis service was written for Manjaro users, so it is designed to stop/start Network Manager pre/post suspend as well. All the operations are contained within the service file itself (even though this really isn't best practice). It is written this way because many Manjaro users are novice and have no experience writing scripts to be called from the service. Regardless, these type of services usually work well, and will get the job done until a kernel update fixes this issue.
Obviously the service would need to be adapted to the network components you are using. If the ath11k driver also uses 2 modules, you will need to experiment to determine the proper order to unload/reload them. If the service mostly works, but fails occasionally it often helps to increase the seconds of sleep time between operations. This will delay the time it takes for the network to be brought back up after suspension, but will increase the services reliability.
Offline
Wifi seems broken again since 5.11.5 or so. Have you found any workaround?
Offline
Wifi seems broken again since 5.11.5 or so. Have you found any workaround?
I had to turn on vt-d in bios and add the kernel parameter. Mind you though that I have a qca6391 compex wlt639 wifi card not the kill ax500. But settings should be the same as the driver is the same. The issue I believe is that with vt-d on you can use the 32 msi vectors that the driver uses where as prior to January or the kernels used the single msi vector patch. I could be wrong on the reasoning. I have been doing my best to follow ath11k stuff closely.
intel_iommu=onI also have this for the memory issue.
memmap=12M$20MOffline
I have the Dell xps 17 9700 with an ax500, and I still can't get wifi to work reliably on 5.12.9.
This is the boot entry in my grub.cfg
linux /vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw cryptdevice=/dev/nvme0n1p3:volgroup0:allow-discards memmap=12M\$20M intel_iommu=on loglevel=3 quietBut I am using UEFI boot, and I read that the memmap isn't applied using a UEFI boot setup? So I'm not sure if this is working?
Here is the output of
dmesg | grep ath11k[ 11.731461] ath11k_pci 0000:04:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
[ 11.731488] ath11k_pci 0000:04:00.0: enabling device (0000 -> 0002)
[ 12.117731] ath11k_pci 0000:04:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
[ 12.117735] ath11k_pci 0000:04:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id
[ 12.298137] ath11k_pci 0000:04:00.0 wlp4s0: renamed from wlan0
[ 80.161557] Modules linked in: snd_soc_sof_sdw snd_soc_hdac_hdmi snd_soc_rt715 snd_soc_rt711 snd_soc_rt1308_sdw regmap_sdw nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) qrtr_mhi wl(POE) snd_soc_dmic snd_sof_pci_intel_cnl snd_sof_intel_hda_common hid_sensor_als hid_sensor_trigger soundwire_intel industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common soundwire_generic_allocation industrialio hid_sensor_custom soundwire_cadence hid_sensor_hub snd_sof_intel_hda snd_sof_pci cros_ec_ishtp snd_sof cros_ec intel_ishtp_loader intel_ishtp_hid joydev snd_sof_xtensa_dsp mousedev soundwire_bus snd_soc_skl hid_multitouch snd_soc_hdac_hda iTCO_wdt qrtr intel_pmc_bxt mei_hdcp ee1004 mei_wdt iTCO_vendor_support 8250_dw intel_rapl_msr ns dell_laptop snd_hda_ext_core dell_wmi_sysman dell_wmi ledtrig_audio ath11k_pci snd_soc_sst_ipc ucsi_ccg dell_smbios snd_soc_sst_dsp snd_soc_acpi_intel_match dcdbas snd_soc_acpi dell_wmi_descriptor wmi_bmof intel_wmi_thunderbolt dell_smm_hwmon ath11k snd_soc_core
[ 80.161688] ? ath11k_dp_rx_process_mon_rings+0x660/0x660 [ath11k]
[ 80.161699] ? ath11k_dp_rx_process_mon_rings+0x660/0x660 [ath11k]
[ 84.273667] ath11k_pci 0000:04:00.0: firmware crashed: MHI_CB_SYS_ERROR
[ 85.193633] ath11k_pci 0000:04:00.0: failed to synchronize setup for vdev 0 start: -110
[ 85.193645] ath11k_pci 0000:04:00.0: failed to start vdev 0 addr 9c:b6:d0:3f:54:20 on freq 5640: -110
[ 85.193652] ath11k_pci 0000:04:00.0: failed to delay vdev start: -110
[ 85.193661] ath11k_pci 0000:04:00.0: failed to send WMI_PEER_DELETE cmd
[ 85.193665] ath11k_pci 0000:04:00.0: failed to delete peer vdev_id 0 addr 3c:a6:2f:1e:e1:04 ret -108
[ 85.193670] ath11k_pci 0000:04:00.0: Failed to add station: 3c:a6:2f:1e:e1:04 for VDEV: 0
[ 85.220377] WARNING: CPU: 14 PID: 706 at drivers/net/wireless/ath/ath11k/mac.c:5514 ath11k_mac_op_unassign_vif_chanctx+0x182/0x280 [ath11k]
[ 85.220415] Modules linked in: michael_mic snd_soc_sof_sdw snd_soc_hdac_hdmi snd_soc_rt715 snd_soc_rt711 snd_soc_rt1308_sdw regmap_sdw nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) qrtr_mhi wl(POE) snd_soc_dmic snd_sof_pci_intel_cnl snd_sof_intel_hda_common hid_sensor_als hid_sensor_trigger soundwire_intel industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common soundwire_generic_allocation industrialio hid_sensor_custom soundwire_cadence hid_sensor_hub snd_sof_intel_hda snd_sof_pci cros_ec_ishtp snd_sof cros_ec intel_ishtp_loader intel_ishtp_hid joydev snd_sof_xtensa_dsp mousedev soundwire_bus snd_soc_skl hid_multitouch snd_soc_hdac_hda iTCO_wdt qrtr intel_pmc_bxt mei_hdcp ee1004 mei_wdt iTCO_vendor_support 8250_dw intel_rapl_msr ns dell_laptop snd_hda_ext_core dell_wmi_sysman dell_wmi ledtrig_audio ath11k_pci snd_soc_sst_ipc ucsi_ccg dell_smbios snd_soc_sst_dsp snd_soc_acpi_intel_match dcdbas snd_soc_acpi dell_wmi_descriptor wmi_bmof intel_wmi_thunderbolt dell_smm_hwmon ath11k
[ 85.220699] RIP: 0010:ath11k_mac_op_unassign_vif_chanctx+0x182/0x280 [ath11k]
[ 85.221544] ath11k_pci 0000:04:00.0: failed to submit WMI_VDEV_STOP cmd
[ 85.221553] ath11k_pci 0000:04:00.0: failed to stop WMI vdev 0: -108
[ 85.221557] ath11k_pci 0000:04:00.0: failed to stop vdev 0: -108
[ 89.327632] ath11k_warn: 8 callbacks suppressedI was able to get it to connect a few times, but mostly it crashed.
I have a combined 2.4GHz/5GHz Wireless network. The times the connection did succeed, it was to the 2.4GHz...
Not sure what else to try...
edit:
I was able to limit the connection band to 2.4GHz using the Advanced Network Configuration and it looks like my connection is stable now...
Last edited by avanderbergh (2021-06-05 18:08:31)
Offline