Re: iwlwifi/LinuxKPI 802.11 update

2022-03-24 Thread J.R. Oldroyd
On Thu, 24 Mar 2022 19:17:36 + (UTC) "Bjoern A. Zeeb" wrote: > > I haven't heard much good or bad from people on main since. I've > comitted a further number of changes to main in order to support other > drivers (more in a separate email probably tomorrow). > Hi Bjørn, I just compiled ma

Re: iwlwifi/LinuxKPI 802.11 update

2022-03-24 Thread J.R. Oldroyd
On Thu, 24 Mar 2022 15:48:55 -0400 "J.R. Oldroyd" wrote: > > [ report re iwlwifi on 8265 ] I also see this in the log: Mar 24 15:28:08 susauq kernel: iwlwifi0: No beacon heard and the time event is over already... Mar 24 15:28:37 susauq kernel: iwlwifi0: iwl_trans_send_cmd bad

wifimgr with iwlwifi

2022-03-26 Thread J.R. Oldroyd
On Sat, 26 Mar 2022 09:58:12 -0700 Kevin Oberman wrote: > > On Sat, Mar 26, 2022 at 3:28 AM Takashi Inoue > wrote: > > > Do you use "wifimgr" which is a GUI tool to select AP. > > When I use "if_iwlfiwi.ko", wave strength displayed > > in wifimgr is 0 for all access point. > > Do you see this ph

Re: 8265 / 9560 problems

2022-04-08 Thread J.R. Oldroyd
On Thu, 7 Apr 2022 17:14:26 + (UTC) "Bjoern A. Zeeb" wrote: > > Hi, > > I have reports from at least three people saying that atfer the March 27 > update associating has become hard and they see firmware crashes. > > These were on 8265 / 9560 chipsets. Some of you tried to gather data > fo

Re: 8265 / 9560 problems + 7260 + AX200

2022-04-15 Thread J.R. Oldroyd
On Fri, 15 Apr 2022 06:24:48 +0900 Tomoaki AOKI wrote: > > On Thu, 14 Apr 2022 13:03:00 -0700 > Chris wrote: > > > On 2022-04-14 11:12, Bjoern A. Zeeb wrote: > > > On Mon, 11 Apr 2022, Chris wrote: > > > > > >> However. After login, if I send a > > >> service netif restart > > >> everythin

Re: 8265 / 9560 problems + 7260 + AX200

2022-04-15 Thread J.R. Oldroyd
On Fri, 15 Apr 2022 09:55:30 + (UTC) "Bjoern A. Zeeb" wrote: > > On Fri, 15 Apr 2022, J.R. Oldroyd wrote: > > > I see that iwl_drv_stop() -- which I presume gets called when the interface > > goes down -- it unloads the firmware and then iwl_drv_start() call

Re: Intel iwlwifi driver & firmware update in CURRENT

2022-05-22 Thread J.R. Oldroyd
On Sun, 22 May 2022 12:08:23 + jbo@insane.engineer wrote: > > > Hey, > > If you can tell me the hashes of commits to cherry-pick for stable/13 I might > be able to do a build tonight on my AX201 (no promises tho). > You can find all of Björn's commits like this... https://cgit.freebsd.org

Re: Intel iwlwifi driver & firmware update in CURRENT

2022-05-22 Thread J.R. Oldroyd
On Sun, 22 May 2022 14:27:33 + jbo@insane.engineer wrote: > > > You can find all of Björn's commits like this... > > > > https://cgit.freebsd.org/src/log/?qt=committer&q=bz%40freebsd.org > > > > -jr > > Thanks! > My main concern is not necessarily locating Björn's commits but rather > knowi

Re: New iwlwifi firmware for testing in main

2022-08-08 Thread J.R. Oldroyd
On Mon, 8 Aug 2022 02:46:25 + (UTC) "Bjoern A. Zeeb" wrote: > > > Thanks for confirming this! > Björn, Back on 7/13 at 09:33 UTC, I sent you an email also showing a panic. It may be similar as it also involves lkpi_sta_auth_to_scan() and then lkpi_lsta_remove(). In my case, it was trigge