From nobody Mon Jun 23 18:27:53 2025 X-Original-To: current@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 4bQxQz60pbz5yd3S for ; Mon, 23 Jun 2025 18:28:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bQxQz2g9tz3h3F for ; Mon, 23 Jun 2025 18:28:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f41.google.com with SMTP id 2adb3069b0e04-553e5df44f8so3066868e87.3 for ; Mon, 23 Jun 2025 11:28:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750703289; x=1751308089; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nKOLfsQErJw3jTar0X/A+o8m6RNiq91jgbTqa24JvEE=; b=uY+yNMSeECGeAYZ89+YiySJc8xc2XEhVbLjWHI6cWs2jXIA+YKUA8QQ+MiAjj9ndqe muZl0ZjlpDSSuggFgN+gDe5HomIvqlM9dfBmjwrm/6x7PsMUZOS5yExCoJ/JhAi5ppMK OPBf1pWQFwok0ZPxzt2BQFP5MoPv9XEragRFQFjZkAIvI/KgZdnnkDgWaFuKNQE80B0f SgkuEHRkGyuiHZsIkUS32QqIqIPNfGv1U/rir3epyC1dWofnZdK2i1I9zzd4twYqLDj9 qLC2PWUt7wjBVfMCj9aFYcA2E1b6jSofnshBQTgt8SYn9QbSGzDEYVHdffqPCUWezWNp hQQg== X-Gm-Message-State: AOJu0YzRg2CvK6ESEDhpE1MD50/FGv+R5CrwQ+hFdbL6e19Zsnr11jxY lEYXkuZsGc9P5X92rD+ENSEMAVf0qN0onA+64bHke2d76o6/vdW3UBMp547kTN2iPqrSHtknQWj mxdXZsCj0oqOa/dqnA7k3stKeXcwGCJbepw== X-Gm-Gg: ASbGncs0n+sggd8AgjBzr51u5p2Zmd9hx7bCls7OEZ0UMaKpioupOLSehB+rTjmtEyS N2GkAYfsUKPwBDIl71jwplcURRMQGg54UqFdehypgUxY/lKUC0kIKrYfZlUxNi/gaurIndz+Cul PgUBIyUSkwkltEdDrGEDahMA3ek9enTa2LmiH5UjVf7UxX X-Google-Smtp-Source: AGHT+IEzVWqo9dYfGpPDUYsRthM2cHVNWvrPDGS6v291zhAwhWZofkqs9lBaFT4YeryjZJahmwpnK1As5HMAgpsYhCs= X-Received: by 2002:a05:6512:3d10:b0:553:cf38:5e89 with SMTP id 2adb3069b0e04-553e3ba9194mr3832013e87.20.1750703288543; Mon, 23 Jun 2025 11:28:08 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Mon, 23 Jun 2025 11:27:53 -0700 X-Gm-Features: AX0GCFt7bPuDKzpRXt8oLG6D-ISTiPhGm6bQUaDW3YuZQptnF-li3hHQnxuuD3o Message-ID: Subject: Re: No wifi (iwn) after main-n278149-6b96e7a57317 -> main-n278156-b2ac169802eb To: current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000009ef2c60638415fdc" X-Rspamd-Queue-Id: 4bQxQz2g9tz3h3F X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] --0000000000009ef2c60638415fdc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable yo! I took a look, there's like 7? diffs between those two commits and none of them are obviously affecting wifi? What's showing up in dmesg? Anything obviously weird? -a On Mon, 23 Jun 2025 at 10:57, David Wolfskill wrote: > TL;DR: Wireless NIC iwn was working on my main laptop with > main-n278149-6b96e7a57317; after updating (this morning) to > main-n278156-b2ac169802eb, it did not. > > Some additional details: > * For the last few weeks, I have only tested this at home (daily > updates/tracking head); this morning, the rebuild itself was done at > home, but by the time for the reboot after the update, I was on my way > to the office, so I was on a commuter train (with WiFi that uses a > captive portal). > * The "wifi" LEP on the laptop, which normally is on when the wiwif NIC > is enabled, was not on. I tried issung "service netif restart wlan0"; > the wifi LED flickered briefly, then went out. > * I rebooted to stable/14 (stable/14-n271780-0ee191f2f035) while still > on the same train, and was able to see the wifi NIC working. > * The same laptop is presently running stable/14 > (stable/14-n271780-0ee191f2f035), using wifi, in the office. It had > also successfully used the wifi NIC under stable/14-n271780-0ee191f2f03= 5 > at home. > * A different laptop (that I use for travel when I expect to need to > cross a country's border), and which normally uses its wired NIC (em0) > when it is at home came up under main-n278156-b2ac169802eb and > had no issues with the wored NIC. (It's at home right now; I > can't readily flip the BIOS switch to tell it to activate the > wireless NIC from here.) > > I note that main-n278156-b2ac169802eb is just a couple of commits beyond > the current "stabweek" point, so that may be something of which to be > aware. > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > =E2=80=9CWe will measure our success not only by the battles we win, but = also by > the wars that we end, and perhaps most importantly, the wars we never > get into." > > See https://www.catwhisker.org/~david/publickey.gpg for my public key. > --0000000000009ef2c60638415fdc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
yo!

I took a look, there's like 7? = diffs between those two commits and none of them are obviously affecting wi= fi?

What's showing up in dmesg? Anything obvio= usly weird?


-a

=


<= div dir=3D"ltr" class=3D"gmail_attr">On Mon, 23 Jun 2025 at 10:57, David Wo= lfskill <david@catwhisker.org> wrote:
TL;= DR: Wireless NIC iwn was working on my main laptop with
main-n278149-6b96e7a57317; after updating (this morning) to
main-n278156-b2ac169802eb, it did not.

Some additional details:
* For the last few weeks, I have only tested this at home (daily
=C2=A0 updates/tracking head); this morning, the rebuild itself was done at=
=C2=A0 home, but by the time for the reboot after the update, I was on my w= ay
=C2=A0 to the office,=C2=A0 so I was on a commuter train (with WiFi that us= es a
=C2=A0 captive portal).
* The "wifi" LEP on the laptop, which normally is on when the wiw= if NIC
=C2=A0 is enabled, was not on.=C2=A0 I tried issung "service netif res= tart wlan0";
=C2=A0 the wifi LED flickered briefly, then went out.
* I rebooted to stable/14 (stable/14-n271780-0ee191f2f035) while still
=C2=A0 on the same train, and was able to see the wifi NIC working.
* The same laptop is presently running stable/14
=C2=A0 (stable/14-n271780-0ee191f2f035), using wifi, in the office.=C2=A0 I= t had
=C2=A0 also successfully used the wifi NIC under stable/14-n271780-0ee191f2= f035
=C2=A0 at home.
* A different laptop (that I use for travel when I expect to need to
=C2=A0 cross a country's border), and which normally uses its wired NIC= (em0)
=C2=A0 when it is at home came up under main-n278156-b2ac169802eb and
=C2=A0 had no issues with the wored NIC.=C2=A0 (It's at home right now;= I
=C2=A0 can't readily flip the BIOS switch to tell it to activate the =C2=A0 wireless NIC from here.)

I note that main-n278156-b2ac169802eb is just a couple of commits beyond the current "stabweek" point, so that may be something of which t= o be
aware.

Peace,
david
--
David H. Wolfskill=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 david@catwhisker.org
=E2=80=9CWe will measure our success not only by the battles we win, but al= so by
the wars that we end, and perhaps most importantly, the wars we never
get into."

See https://www.catwhisker.org/~david/publickey.gpg for my public key.
--0000000000009ef2c60638415fdc--