In message <2838567.hhqauc6...@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > Sorry I hadn't noticed this yesterday (so I could have repported it > > then), but after updating the "head" slice of my laptopp from: > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > r...@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > amd64 1400032 1400032 > > > > to: > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > r...@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > amd64 1400032 1400032 > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does not: > > the WLAN LED doesn't light up. > > I am also experiencing issues with wlan after my current update to > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > demonstrating the same behavior - wlan can not associate. > You can mitigate it by using security/wpa_supplicant from ports as replacemen > t > of wpa_supplicant in base. > > ..... > > > > I note that exactly the same hardware works OK in stable/12 and stable/13. > > > > Peace, > > david >
Can you grep wpa_supplicant in /var/log/messages? This will give us a clue. -- Cheers, Cy Schubert <cy.schub...@cschubert.com> FreeBSD UNIX: <c...@freebsd.org> Web: https://FreeBSD.org NTP: <c...@nwtime.org> Web: https://nwtime.org The need of the many outweighs the greed of the few. > >
