As always, thank you for your hard work, Bjoern.
Will test the mentioned stuff as soon as I am able to, hopefully I can get it
built in STABLE/13.
--- Original Message ---
On Friday, April 1st, 2022 at 2:32 AM, Bjoern A. Zeeb wrote:
> Hi,
>
> I've just pushed Realtek's rtw88 driver in
On Sat, 26 Mar 2022, Krzysztof Piecuch wrote:
bad things:
That's the stuff I need to know ;-)
- the wifi interface would go up -> down -> up on boot? Not sure if I'm
reading dmesg correctly, please double-check it.
Can be, check wpa_supplicant log for deauth/deassoc. It's likely
iwlwifi
On Sat, 26 Mar 2022, J.R. Oldroyd wrote:
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 po
On Sat, 26 Mar 2022, Simple wrote:
Write the following section to /etc/rc.conf.
kld_list="if_iwlwifi"
No longer needed on an up-to-date system.
wlans_iwlwifi0="wlan0"
wlandebug_wlan0="+state +crypto +node +auth +assoc +dot1xsm +wpa"
You can probably drop the wlandebug_wlan0 as well, unle
On Sat, 26 Mar 2022, Takashi Inoue wrote:
Hi,
Thanks for your report.
Because I use 13 stable and cannot test the current,
your report is very useful to me.
I'm using ThinkPad X1 nano which has a AX201.
I have some questions.
Do we need the 'if_iwlwifi_load="YES"' line
in addition to the 'kl
On Thu, 31 Mar 2022, Eirik Øverby wrote:
Hi,
On Sun, 2022-03-27 at 23:40 +, Bjoern A. Zeeb wrote:
good news for everyne tracking stable/13. The changes are in as of
an hour or two ago and you can update now as well to test and
hopefully get a bit more stability.
Hi,
thanks for your har
On Mon, 28 Mar 2022, Kevin Oberman wrote:
Updated to table/13-n250140-4cf0cc507f3 and the network seems good.
A couple of oddities:
First, the network is quite slow to start. The driver is loaded from
rc.conf and seems to be up in about the same time as before the update. The
That should no
On Tue, 29 Mar 2022, Oleksandr Kryvulia wrote:
iwm(4) is likely compiled into the kernel... forgive me. You can proabbly
try
hint.iwm.disabled="1"
or
hint.iwm.0.disabled="1"
in loader.conf and see if that helps or compile a kernel without iwm
and iwmfw to test.
Ok, boot with iwm disabled:
ro
On Thu, 31 Mar 2022, Patrick Mackinlay wrote:
I switched to the latest stable (004da2d51f8427745c0d1287781d5ba546b19000
2022-03-31 11:09:07 +).
Seems to work fine. Connects quickly and switches to a new access point
quickly when I turn off the one its connected to. Will only connect at
Hi,
I've just pushed Realtek's rtw88 driver into the tree along with
firmware to support it and man pages. Station mode only.
CAVEAT-0: Even though the MFC reminder is set, I'll probably not
merge it this quickly into the stable/13 branch (see CAVEAT-1).
If you want to do so yourself, you cur
I switched to the latest stable
(004da2d51f8427745c0d1287781d5ba546b19000 2022-03-31 11:09:07 +).
Seems to work fine. Connects quickly and switches to a new access point
quickly when I turn off the one its connected to. Will only connect at
the slower 11g, but I think thats expected at t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262150
--- Comment #12 from Ed Maste ---
(In reply to Tomoaki AOKI from comment #9)
My WIP is a umber of build options, userland changes, etc., but if you want to
try exactly what I ran on the framework it is available in my GitHub repo at
https:/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262150
--- Comment #11 from Tomoaki AOKI ---
Created attachment 232845
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232845&action=edit
Full dmesg from start
Full dmesg with replacing serial No.s and MAC addresses with '*'.
Last 3 or
Hi,
A day later (the 27th of March), bz pushed a lot of stuff. You might want to
consider updating to at least 6663718bb49635deac3f5dc55fa6f0f7cba593ba
I am rolling with an Intel AX201 as well and had similar problems as you are
describing. After updating to that commit these symptoms seem to h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262150
--- Comment #10 from Bjoern A. Zeeb ---
(In reply to Tomoaki AOKI from comment #9)
Your problem from above seems different; can you show the lines before the
error from dmesg? And we should probably not do that here as it's not related
t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262150
--- Comment #9 from Tomoaki AOKI ---
(In reply to Ed Maste from comment #7)
Unfortunately, I still have the same issue as stable/13 on main git
342056fa1c7a36d90feafd593fb980f98563f32c, which is newer than the one you
pointed.
So possibly
Interesting...
I was just about to drop a message here telling you guys that this is the most
stable iwlwifi experience I've had so far on my Lenovo ThinkPad X1 Gen9 (Intel
AX201).
Prior to these latest updates I had a lot of problems connecting to networks.
It was basically a 1-out-of-10 situa
I am using a matebook pro x 2021 (AX201) with FreeBSD 13 stable
(60338b80693000ed0f9812b90ca54d35fd077cd0 Sat Mar 26 11:04:36 2022 +0100).
Sometimes the iwlwifi driver does not attach, I get the message
device_attach: iwlwifi0 attach returned 60
Even if I unload the module and reload I get the
On Sun, 2022-03-27 at 23:40 +, Bjoern A. Zeeb wrote:
> good news for everyne tracking stable/13. The changes are in as of
> an hour or two ago and you can update now as well to test and
> hopefully get a bit more stability.
Hi,
thanks for your hard work!
Sadly, I tested this and I get no ne
19 matches
Mail list logo