From nobody Tue Sep 13 18:23:52 2022 X-Original-To: freebsd-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 4MRsL64bJSz4c56T for ; Tue, 13 Sep 2022 18:23:58 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MRsL63xHLz3TM5; Tue, 13 Sep 2022 18:23:58 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1663093438; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=40HP9hiY2VrThoyh3iiDqfZJ4V5R/THfqttKBWaFAkI=; b=yBjwXA6jSCczRxpQAO5sd6Z9vQSSGVbRnr9zmOLdyd/oo6eeNkg3sVknVZjmtUmf40dPs6 aRvnXvxdEYRrYR1cNQd5AuTdgGZFg4Fn6rGX0NgYNWSIwEBrODsBBS6s2C57ngEu3ohA2v H5FSqoh0rmg72K8mQKMSurtY7r4thBU2Ls7x56S3jXZ+sHOxNCHHPwrLhv2IY1xJVMwwUn DZeOb8sTbfVLWOB29Ip2OGSJIlc+b18jJ91fjWeARcGinf/vhnEBa6mZ5s2DZ5ZE0ssLKi XKp40NkFT+ineQb1+XGhcVhglnAhqsWVE0GdJT98l9jbmlypntLOYCO0l8SIuw== Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4MRsL61g0SzbXZ; Tue, 13 Sep 2022 18:23:58 +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.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id DB41D8D4A250; Tue, 13 Sep 2022 18:23:56 +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 C10A75C3A831; Tue, 13 Sep 2022 18:23:55 +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 1bXIVm1K1j8Q; Tue, 13 Sep 2022 18:23:53 +0000 (UTC) Received: from strong-aiccu0.sbone.de (strong-aiccu0.sbone.de [IPv6:fde9:577b:c1a9:f491::2]) (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 A34A55C3A82F; Tue, 13 Sep 2022 18:23:53 +0000 (UTC) Date: Tue, 13 Sep 2022 18:23:52 +0000 (UTC) From: "Bjoern A. Zeeb" To: "John J. Rushford" cc: freebsd-wireless@FreeBSD.org Subject: Re: wireless interface does not come up on boot In-Reply-To: Message-ID: References: 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: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1098556516-317704978-1663093433=:2997" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1663093438; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=40HP9hiY2VrThoyh3iiDqfZJ4V5R/THfqttKBWaFAkI=; b=FlwmS0B+h3VaqzX4GyMZn0OS8RXrnzKRbvueM0WAXZmZCieTYQLhdgee+lYqtVx4kl+17H +GyDDl5C1VaBOOlkEZoyz3vWKYj9540fh5hqphsZFOwTJiSTHUsnPgvepIHRad16GS/Y4N E4OY9x6dfC8k+vi6lN8oS1FMGw0lpsolG2AwJ2Fe8hwOALlrTaGbTrC6XVD4dTI/ULpW+q zTmZfQ0+vC4X+Tzzgqb2gx5CZ93VlunkO0ebkt78el4EuJWjyblZ+tPkzKAAeCS9FdaXEJ B7xnrQbzrVW1phd6qsnk2ZUjr+9/R/CzxFu4YWrVpeJhkDYRnQFGNu8FVWIjLA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1663093438; a=rsa-sha256; cv=none; b=w142rAyUtIjxxAYab70uljCgqi4IXxzaASaA2P7PEEYHebUSG239Py7UZy207/wOsnr6Mm JFSULAg8K9t24XCnrC9INOsFG0LfX3bImGhbQ8Mh2IHfatdqIAqSSzeN+a+TUHfEZJjcdm 8hdr34Y47PzvGC77dDAVHcx0vvaQ4OXzqVffboRuAZN8WhuuDzBLO0SVhwR6qutf0QoRVq 9halMV6jZ8tWHeoL6pimwmunHD9rpfu/youWr4gjv7WMYDAKkcOPiOUOGNjdvX07Rbc4eW Gw01JD8kI9wxsPYx4KqIhSMCh//hOteWWL8Er3diAeUlKlesylQoDAJ1BLKHDg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1098556516-317704978-1663093433=:2997 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 13 Sep 2022, John J. Rushford wrote: Hi, I am on travels so forgive if I miss things and will be selective with my reply. > I'm having trouble with my wireless interface on a FreeBSD 13.1-RELEASE > installed  Laptop.  The wlan0 interface that uses the iwlwifi driver does not > come up after booting.  I have to bring it up manually.  I was advised to > email this list as it is suspected to be some issue with the driver. > > I have a DELL XPS-13 9360 model laptop in which I've replaced the M2 slot > wifi adapter with a wifi 6e adapter using an AX210 chip, wise tiger is the > brand name.  I've properly configured wpa_supplicant to join an AP in my home > and I have the following options in /etc/rc.conf: > > wlans_iwlwifi0="wlan0" > ifconfig_iwlwifi0="WPA DHCP" > > The interface does not come up after booting the laptop.  In troubleshooting > I've found that I can manualy bring the interface up using the following > commands: > > > # ifconfig wlan0 up scan > > # wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & > > # dhclient wlan0 > > Once I bring up the interface, everything works as expected.  I'm composing > and sending this email from the machine now that I've manually brought up the > interface. > > I have no idea, why the interface does not come up automatically following a > boot.  I've noticed errors loading up firmware for the adapter and was > wondering if this could be throwing off the timing during boot? > > Here are the iwlwifi messages logged during boot: > > iwlwifi0: mem 0xdc100000-0xdc103fff at device 0.0 on pci2 > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-70.ucode' How do you load iwlwifi? You are not by any chance doing this from loader.conf? > iwlwifi0: File size way too small! > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-69.ucode' > iwlwifi0: File size way too small! > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0-68.ucode' > iwlwifi0: api flags index 2 larger than supported by driver > iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 > iwlwifi0: loaded firmware version 68.01d30b0c.0 ty-a0-gf-a0-68.ucode op_mode > iwlmvm > iwlwifi0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0.pnvm' > iwlwifi0: loaded PNVM version dda57f4f > iwlwifi0: Detected RF GF, rfid=0x10d000 > iwlwifi0: base HW address: 84:14:4d:04:e4:0d > iwlwifi0: mem 0xdc100000-0xdc103fff at device 0.0 on pci2 Why is it attaching a 2nd time? Is this the same boot or did you kldunload if_iwlwifi? > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-70.ucode' > iwlwifi0: File size way too small! > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-69.ucode' > iwlwifi0: File size way too small! > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0-68.ucode' > iwlwifi0: api flags index 2 larger than supported by driver > iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 > iwlwifi0: loaded firmware version 68.01d30b0c.0 ty-a0-gf-a0-68.ucode op_mode > iwlmvm > iwlwifi0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0.pnvm' > iwlwifi0: loaded PNVM version dda57f4f > iwlwifi0: Detected RF GF, rfid=0x10d000 > iwlwifi0: base HW address: 84:14:4d:04:e4:0d and again... > iwlwifi0: mem 0xdc100000-0xdc103fff at device 0.0 on pci2 > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-70.ucode' > iwlwifi0: File size way too small! > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-69.ucode' > iwlwifi0: File size way too small! > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0-68.ucode' > iwlwifi0: api flags index 2 larger than supported by driver > iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 > iwlwifi0: loaded firmware version 68.01d30b0c.0 ty-a0-gf-a0-68.ucode op_mode > iwlmvm > iwlwifi0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0.pnvm' > iwlwifi0: loaded PNVM version dda57f4f > iwlwifi0: Detected RF GF, rfid=0x10d000 > iwlwifi0: base HW address: 84:14:4d:04:e4:0d and again... > iwlwifi0: mem 0xdc100000-0xdc103fff at device 0.0 on pci2 > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-70.ucode' > iwlwifi0: File size way too small! > iwlwifi0: could not load firmware image 'iwlwifi-ty-a0-gf-a0-69.ucode' > iwlwifi0: File size way too small! > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0-68.ucode' > iwlwifi0: api flags index 2 larger than supported by driver > iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 > iwlwifi0: loaded firmware version 68.01d30b0c.0 ty-a0-gf-a0-68.ucode op_mode > iwlmvm > iwlwifi0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 > iwlwifi0: successfully loaded firmware image 'iwlwifi-ty-a0-gf-a0.pnvm' > iwlwifi0: loaded PNVM version dda57f4f > iwlwifi0: Detected RF GF, rfid=0x10d000 > iwlwifi0: base HW address: 84:14:4d:04:e4:0d These next three were problems mostly from the past... I have not seen them or heard from them in a while... > iwlwifi0: No beacon heard and the session protection is over already... > iwlwifi0: Not associated and the session protection is over already... > iwlwifi0: Not associated and the session protection is over already... > > I hope someone here can help me to resolve this issue. Most of these issues have been solved in main and (pending MFC for some) will be sorted in stable/13 for 13.2. So the 1st problem seems to be getting iwlwifi loaded and running and wlan0 created. The 2nd issue seems to be able to get wpa_supplicant to get it up and then dhclient to get you an address. Now the driver + LinuxKPI framework in 13.1-R (first release this shipped after not too much time of having started to work) are missing things and have bugs. The other thing is that wpa_supplicant also got changes since. You could try the port for that and see if it helps a bit but I fear you may have to switch to stable/13 more likely (especially after MFCs are done). You can probably try to search the archive here or check https://wiki.freebsd.org/WiFi/Iwlwifi if there were any good workarounds found at that time. I frankly have gone through too many details of all those to remember at the moment. hope this helps (at leats until next week), /bz -- Bjoern A. Zeeb r15:7 --1098556516-317704978-1663093433=:2997--