Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Jun 2025 11:27:53 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        current@freebsd.org
Subject:   Re: No wifi (iwn) after main-n278149-6b96e7a57317 -> main-n278156-b2ac169802eb
Message-ID:  <CAJ-VmomGs7D7n1-KRACiL-csrjphaB8VTnzb1NA15xdWLJPu4w@mail.gmail.com>
In-Reply-To: <aFmVZX-8i4BagBDf@albert.catwhisker.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
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 <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
>   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-0ee191f2f035
>   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
> “We 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.
>

[-- Attachment #2 --]
<div dir="ltr">yo!<div><br></div><div>I took a look, there&#39;s like 7? diffs between those two commits and none of them are obviously affecting wifi?</div><div><br></div><div>What&#39;s showing up in dmesg? Anything obviously weird?</div><div><br></div><div><br></div><div>-a</div><div><br></div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, 23 Jun 2025 at 10:57, David Wolfskill &lt;<a href="mailto:david@catwhisker.org">david@catwhisker.org</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">TL;DR: Wireless NIC iwn was working on my main laptop with<br>
main-n278149-6b96e7a57317; after updating (this morning) to<br>
main-n278156-b2ac169802eb, it did not.<br>
<br>
Some additional details:<br>
* For the last few weeks, I have only tested this at home (daily<br>
  updates/tracking head); this morning, the rebuild itself was done at<br>
  home, but by the time for the reboot after the update, I was on my way<br>
  to the office,  so I was on a commuter train (with WiFi that uses a<br>
  captive portal).<br>
* The &quot;wifi&quot; LEP on the laptop, which normally is on when the wiwif NIC<br>
  is enabled, was not on.  I tried issung &quot;service netif restart wlan0&quot;;<br>
  the wifi LED flickered briefly, then went out.<br>
* I rebooted to stable/14 (stable/14-n271780-0ee191f2f035) while still<br>
  on the same train, and was able to see the wifi NIC working.<br>
* The same laptop is presently running stable/14<br>
  (stable/14-n271780-0ee191f2f035), using wifi, in the office.  It had<br>
  also successfully used the wifi NIC under stable/14-n271780-0ee191f2f035<br>
  at home.<br>
* A different laptop (that I use for travel when I expect to need to<br>
  cross a country&#39;s border), and which normally uses its wired NIC (em0)<br>
  when it is at home came up under main-n278156-b2ac169802eb and<br>
  had no issues with the wored NIC.  (It&#39;s at home right now; I<br>
  can&#39;t readily flip the BIOS switch to tell it to activate the<br>
  wireless NIC from here.)<br>
<br>
I note that main-n278156-b2ac169802eb is just a couple of commits beyond<br>
the current &quot;stabweek&quot; point, so that may be something of which to be<br>
aware.<br>
<br>
Peace,<br>
david<br>
-- <br>
David H. Wolfskill                              <a href="mailto:david@catwhisker.org" target="_blank">david@catwhisker.org</a><br>
“We will measure our success not only by the battles we win, but also by<br>
the wars that we end, and perhaps most importantly, the wars we never<br>
get into.&quot;<br>
<br>
See <a href="https://www.catwhisker.org/~david/publickey.gpg" rel="noreferrer" target="_blank">https://www.catwhisker.org/~david/publickey.gpg</a>; for my public key.<br>
</blockquote></div>
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomGs7D7n1-KRACiL-csrjphaB8VTnzb1NA15xdWLJPu4w>