From nobody Tue Apr 08 21:26:29 2025 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ZXJzw1mlQz5ryYp for ; Tue, 08 Apr 2025 21:26:36 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZXJzw0Hbxz3RD1 for ; Tue, 08 Apr 2025 21:26:36 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1744147596; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=4kmNZJ3CoLbtkEeNoc0nBRfl0Gx62tP2kqhL17CM0xE=; b=aure5Q+Ips6Lg56s2jpPid6GoGcXwHpBuWHkF4rvoD9xfSdFDAB1KukoxKHxwaqhoIC63i /KsP/I+GlFIhzFUhM2EQa2XL3ZWHEPSzkDHxwpiV0bvfbtuTBvQZ8Y6yySwkmqZVTzj4CS 6wg9KBLgc/MRVM5xv3NatMSKskTP+gADG/XKPgtSTJOb2MUmFaxmlJOeJTRnVcWFqR0ted 33kuNhvBLZlMY6NTryfl9VzZedxgxfSLIrcNaghtrycuXjySOyg6sI8VzTybavp3zAy7wT 4m/k3870WVgEY7ZPOgVS2F8JUP8ULFqwVOnD2006X8tXCS5IlYZfQErcwRXdLA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1744147596; a=rsa-sha256; cv=none; b=rkUJ5kjeuQKBdSHu2ZPfrs6wNdJBJT+x8oxjGuLuA66sVUOVV/EAbAQKUV22B4iny6oGL+ tGhagUgoaoScSFrnlktExjsiG2bViXbrRFOIzlDoiNwkPvz5H0LQvv8pASXe7M9Y4/8EJ3 RWrtNJh4L98HYgYnQ6gYdRxXcUS8rR0ElKVanhrSA767IxI0eUIlIopYWellmeGbekzULo mCVrNfCFyCPmJ5WB+tPfGXRaHGgmZ5y1iMjxV0dQ47FBi0tPAKy0qiriwlkay4NfKfgWyL tUeSaFtRl+yGgiuxWF/u7Adcr9xBwQmXz1HaghBEJQgMcm/j4ab+kL9P2WJjlw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1744147596; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=4kmNZJ3CoLbtkEeNoc0nBRfl0Gx62tP2kqhL17CM0xE=; b=L2TipQEMDx1WKiz3RbWnq8K+8wszA2n8ZdSgRRMmtkChY+QqA/MiOYdOAlRwhY+TaZ3Pl1 wpi7QgYHJUwDrGWyBUg0953+RbNDP/mL9R7Ail1CysNiQeeFTe7tkCgACZK3OB+porT5ls u8PbaJJDTsQGT6SvkkTDzF5FHsRfmmwQwWMf2fXiD6WuFLu/41k6UrOkR8EBiciKjiU1UH 0XgaOTkwL+W/K6KmIwPqsjd0sovtv2QXQ3GR3NbyLblWhZxMydI3ETalIh3GoJ8xmIxARv ENB26Sm8k2xaTIXQDCGNEoU2CihQyBEZMI0bQpGhQNQaxmcne17F/1KZD28IzQ== Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mx-01.divo.sbone.de", Issuer "E5" (verified OK)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4ZXJzv56pgz1560 for ; Tue, 08 Apr 2025 21:26:35 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 310CBA64806 for ; Tue, 08 Apr 2025 21:26:28 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 859772D029E0 for ; Tue, 8 Apr 2025 21:26:31 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id nk0P3dqhg9Oy for ; Tue, 8 Apr 2025 21:26:30 +0000 (UTC) Received: from strong-rtwn0.sbone.de (strong-rtwn0.sbone.de [IPv6:fde9:577b:c1a9:4902:3e64:cfff:fe55:bc80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 142FF2D029D8 for ; Tue, 8 Apr 2025 21:26:30 +0000 (UTC) Date: Tue, 8 Apr 2025 21:26:29 +0000 (UTC) From: "Bjoern A. Zeeb" To: FreeBSD wireless mailing list Subject: iwlwifi 11n/11ac testing - and update Message-ID: <3qq1740s-po9n-8517-0103-s5948966p6q8@SerrOFQ.bet> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Hi everyone, a few things will come up soon and I figured I'll send an update about iwlwifi and 11n/11ac testing. As it goes with FreeBSD we often only hear about when things don't work but we'd also sometimes love to hear if things do start working. That's especially more important with the 14.3-RELEASE cycle starting this month. In short: run fwget(8) and you may get 11n and 11ac support on for iwlwifi AX200 and newer out of the box. Please report back either way! In Long: It's been 6-ish weeks since I sent out the initial request(s) for testing hw_crypto [1] and iwlwifi 11n/11ac [2]. As also announced [3] and now imminent pending review [4] firmware will be removed from main and stable/14 src.git the next days and everyone should run fwget(8) (or switch to ports based firmware if you build yourself) to get the firmware for their specfic chipset installed. If you ran fwget(8) in the past, pkg upgrade will give you the latest versions for you kernel at all times. You should only need to re-run fwget(8) if you change your hardware. 20240513._2 should be the current set (which also works for iwx(4)). If you do switch to package based firmware with fwget(8) you will now (on main and stable/14) get HW_CRYPTO (crypto acceleration offloading), HT (11n), and VHT (11ac) enabled automatically if your chipset is expected to be supported. Those would be the 22000, AX210 and BE200 chipset generations (roughly AX200 and newer). If things do not work, please see [5] or below on how to disable features so you can use 11a/b/g with basic rates still. The tunables (sysctls to check for the current status) to enable (=1)/disable (=0) the features are: compat.linuxkpi.80211.hw_crypto=0 compat.linuxkpi.iwlwifi_11n_disable=0 compat.linuxkpi.iwlwifi_disable_11ac=0 You will need to set these in /boot/loader.conf.local (create the file if needed). Again, you should only need to manually do anything about those in case something does not work and in that case you should definitively let us know. Some things don't work as expected yet for some people: - AX101 seems to have issues (pending me getting hardware to debug) - The "BT Coex" crash [6] is reported more often (I am working on that currently) - A panic on reboot due to inconsistent net80211 locking [7] - There's a firmware crash reported presumably when switching bands - WEP, TKIP are not working yet and came as a surprise but I am half way through the code (also preparing for other new cipher suit support) so should come soon too (famouse last words). - Ht/VHT support for older iwlwifi chipsets and rtw88 and rtw89 are also still TBD/to be finished. - For a full list of LinuxKPI based driver problems please see [8]. You can always search bugzilla before reporting a new problem but don't stop reporting! As I said, we know what doesn't work. Here's some more that I'd love to hear more about if it happens to you: - Vague rumors said some people failed to get onto 11a[c] but 11[bgn] worked fine. Please sned an email to the list if that happens to you. Please include the output of ifconfig -v wlan0 (or equivalent) and ifconfig -v wlan0 list scan as a first step. On the other hand if things do work please also have a look at: - When you are associated: sysctl compat.linuxkpi.80211.wlan0 it will report rx_beacon_signal_avg, rxrate, and txrate as seen by the firmware (and the values may change depending on how you are using wifi). This information will likely not match ifconfig output. That's a fun project for someone one day. I am running out of things and likely forgot some, but most importantly: thanks to everyone who has already given it a try, is patiently waiting for me to fix some of the above, and the FreeBSD Foundation. See their Laptop Project [9] for more interesting things, and check updates here and on the desktop mailing list. Looking forward to hear from you, I'll go back to code, Bjoern PS: anyone wants to test a new version of the driver(s) please stay tuned! [1] https://lists.freebsd.org/archives/freebsd-wireless/2025-February/002895.html [2] https://lists.freebsd.org/archives/freebsd-wireless/2025-February/002964.html [3] https://lists.freebsd.org/archives/freebsd-wireless/2025-March/003062.html [4] https://reviews.freebsd.org/D49713 [5] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285765#c1 [6] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280546 [7] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285729 [8] https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=273622&hide_resolved=1 [9] https://github.com/FreeBSDFoundation/proj-laptop -- Bjoern A. Zeeb r15:7