From nobody Tue Apr 01 11:51:07 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 4ZRmYC1143z5rPy0 for ; Tue, 01 Apr 2025 11:51:11 +0000 (UTC) (envelope-from ltning-freebsd-wireless@anduin.net) Received: from mail.anduin.net (mail.anduin.net [185.42.170.45]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZRmYB4Vjfz45Qd for ; Tue, 01 Apr 2025 11:51:10 +0000 (UTC) (envelope-from ltning-freebsd-wireless@anduin.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=anduin.net header.s=dkim2021 header.b=YZCJi2CV; dmarc=pass (policy=reject) header.from=anduin.net; spf=pass (mx1.freebsd.org: domain of ltning-freebsd-wireless@anduin.net designates 185.42.170.45 as permitted sender) smtp.mailfrom=ltning-freebsd-wireless@anduin.net DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anduin.net; s=dkim2021; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: To:Subject:From:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=9wK4gyYIsDupIiL3Npr8iioP/71hN96P6fn4N5Zhnn0=; t=1743508270; x=1744372270; b=YZCJi2CVNjaiPs2m11vcb9L2ZwJ8KFeZfEv3gdmZs0/vGk2ZdLvnxo7vZBCZEvVTVXbSBw0wWf6 LbIdDlFD+1A1+tgx2E219ySd9HoZrTyV96mEDHWgg5GrCECEAg2DlLlzLvmZU0YJp8s+4fT/xWIq8 RELbyTmU5mrpUEZ+fnef7chBpIGcA7h1YSmzEDDJlIsYAS+uMKhQVQILxsYPLOPBvTA8YVOVTpllj ZFf4HkKE8KnU2gMEjD6Wqcq2W4GsnuiYFT2vxc8T8GOkHhWnBXQGhQ9NueoXqrDPluegFm+DldF5Z SCmditfIHZfTFyUTJ/j9PSRaUfgxRmpS4UXg==; Received: by mail.anduin.net with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.97.1 (FreeBSD)) (envelope-from ) id 1tza95-00000000BZi-3Y3b for wireless@freebsd.org; Tue, 01 Apr 2025 11:51:09 +0000 Message-ID: Date: Tue, 1 Apr 2025 13:51:07 +0200 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 User-Agent: Mozilla Thunderbird From: ltning-freebsd-wireless@anduin.net Subject: Re: Intel Wi-Fi: scope of iwx(4) on FreeBSD To: wireless@freebsd.org References: <0e1690b9-1426-4ecd-a6f4-5185f00dc4ef@gmail.com> <20250401202322.433735a31ee9c9fb7adf3481@dec.sakura.ne.jp> Content-Language: en-US In-Reply-To: <20250401202322.433735a31ee9c9fb7adf3481@dec.sakura.ne.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-SA-Authenticated: Yes X-Spam-Score: -1.9 X-Spam-Level: - X-Spam-Report: host: mail.modirum.com | contact: hostmaster@modirum.com | scores: BAYES_00=-1.9,NO_RELAYS=-0.001 | autolearn=no autolearn_force=no, score=0 X-Spamd-Result: default: False [-4.83 / 15.00]; RBL_SENDERSCORE_REPUT_9(-1.00)[185.42.170.45:from]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.96)[-0.960]; NEURAL_HAM_SHORT(-0.87)[-0.872]; DMARC_POLICY_ALLOW(-0.50)[anduin.net,reject]; R_SPF_ALLOW(-0.20)[+ip4:185.42.170.45/32:c]; R_DKIM_ALLOW(-0.20)[anduin.net:s=dkim2021]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_NO_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62248, ipnet:185.42.170.0/24, country:EE]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[anduin.net:+] X-Rspamd-Queue-Id: 4ZRmYB4Vjfz45Qd X-Spamd-Bar: ---- Tested this on my Framework 13 (Intel) yesterday. Driver binds to the card but cannot find/load the firmware, despite iwlwifi firmwares being installed. On first try, it's clear that the file does not exist (checked /boot/firmware): iwx0: mem 0x7a200000-0x7a203fff at device 0.0 on pci2 iwlwifi-so-a0-gf-a0-77.ucode: could not load firmware image, error 2 iwx0: could not read firmware iwlwifi-so-a0-gf-a0-77.ucode iwx0: failed to load init firmware iwx0: failed to stop device I then copied the firmware from the OpenBSD package, and renamed to iwlwifi and added a .ucode suffix (no idea if it was the correct file): iwx0: mem 0x7a200000-0x7a203fff at device 0.0 on pci2 iwlwifi-so-a0-gf-a0-77.ucode: could not load firmware image, error 8 iwx0: could not load firmware, 35 iwx0: failed to load init firmware iwx0: failed to stop device After a few attempts at this, I gave up and reverted to iwlwifi (which gave me a whole new set of headaches since I can no longer disable HT/VHT, so I have to cold reboot every few hours to restore network). It's gotta get worse before it gets better, I'm told ;) /Eirik On 01.04.2025 13:23, Tomoaki AOKI wrote: > Hi. > > For firmwares, IIUC, iwx seems to be sharing them with iwlwifi, looking > into its commit messages. > > https://cgit.freebsd.org/ports/commit/net/wifi-firmware-iwlwifi-kmod?id=ef3fa2a325a592baa6573782a72cf0d833589ffa > > And looking into sys/dev/iwx/if_iwx.c in D49259, especially around the > definition of the array iwx_devices[] (struct iwx_devices) around line > 217 (198 through 238 including #define's), only AX200, 201 and 211 > including their variants seems to be supported. > > And I don't have AX series of WiFi chips/cards, so cannot test. > > > On Tue, 01 Apr 2025 10:40:20 +0000 > Jonathan Vasquez wrote: > >> Hey Graham, >> >> I haven't tested this but I see in the code review page that you need to grab and install openbsd's firmware for iwx. See if it works after installing them. >> >> https://reviews.freebsd.org/D49259 >> >> Jonathan Vasquez >> PGP: 34DA 858C 1447 509E C77A D49F FB85 90B7 C4CA 5279 >> Sent with ProtonMail Secure Email >> >> >> -------- Original Message -------- >> On 4/1/25 01:37, Graham Perrin wrote: >> >>> Yesterday's >>> >>> mentions support for many recent cards. >>> >>> Should we assume that all less recent hardware is out of scope? >>> >>> Alternatively, is my rc.conf file mis-configured? The wlan4 lines below. >>> >>> Thanks >>> >>> >>> root@mowa219-gjp4-zbook-freebsd:~ # sysrc devmatch_blocklist >>> devmatch_blocklist: i915kms if_iwlwifi iwm >>> root@mowa219-gjp4-zbook-freebsd:~ # kldload iwx >>> kldload: can't load iwx: No such file or directory >>> root@mowa219-gjp4-zbook-freebsd:~ # ls -hln /boot/kernel/*iwx* >>> -r--r--r--  1 0 0  227K Mar 31 22:01 /boot/kernel/if_iwx.ko >>> root@mowa219-gjp4-zbook-freebsd:~ # kldload if_iwx >>> kldload: can't load if_iwx: module already loaded or in kernel >>> root@mowa219-gjp4-zbook-freebsd:~ # ifconfig iwx0 >>> ifconfig: interface iwx0 does not exist >>> root@mowa219-gjp4-zbook-freebsd:~ # grep wlan4 /etc/rc.conf >>> wlans_iwx0="wlan4" >>> create_args_wlan4="wlanmode sta country GB regdomain etsi" >>> create_args_wlan4="country GB regdomain etsi" >>> ifconfig_wlan4="WPA DHCP" >>> root@mowa219-gjp4-zbook-freebsd:~ # uname -mvKU >>> FreeBSD 15.0-CURRENT main-n276197-680d34896c36 GENERIC-NODEBUG amd64 >>> 1500035 1500035 >>> root@mowa219-gjp4-zbook-freebsd:~ # grep SIOCIFCREATE /var/log/console.log >>> Apr  1 05:41:20 mowa219-gjp4-zbook-freebsd kernel: ifconfig: >>> SIOCIFCREATE2 (wlan4): Device not configured >>> root@mowa219-gjp4-zbook-freebsd:~ # apropos iwx >>> apropos: nothing appropriate >>> root@mowa219-gjp4-zbook-freebsd:~ # >>> >>> >>> iwx.4 in OpenBSD-current: > >