Bug #3366
closedifconfig wlan0 scan - S:N is 0 with iwm0
0%
Description
When I scan for all access points, all their S:N (Signal to Noise Ratio) is reported as zero!
- /etc/rc.conf
wlans_iwm0="wlan0"
ifconfig_wlan0="DHCP WPA"
Doing a `ifconfig wlan0 scan` reports for example:
SSID/MESH ID BSSID CHAN RATE S:N INT CAPS
Bon House 7c:a1:07:12:86:c8 1 54M 0:0 200 EP HTCAP WPA RSN WME
Thang Long ... 6c:5a:b0:35:42:f9 1 54M 0:0 100 EPS RSN HTCAP WME ATH WPS
Quy's home c8:bf:4c:19:48:99 1 54M 0:0 100 EP WPA RSN WPS HTCAP WME
Long2003 a8:25:eb:20:c0:89 1 54M 0:0 100 EPS HTCAP WME ATH RSN WPA WPS
Redmi_Quyda... 88:c3:97:3a:f3:fa 1 54M 0:0 100 EP WPA RSN WPS HTCAP WME
DIRECT-6B-H... f6:39:09:5a:e4:6b 6 54M 0:0 100 EP RSN HTCAP WME WPS
DrayTek 16:49:bc:46:9c:84 6 54M 0:0 100 EPS RSN HTCAP WME
Tang 2 a8:02:db:f1:b6:2c 6 54M 0:0 100 EPS WPA RSN WPS HTCAP WME
0x54e1ba 50:0f:f5:35:9b:08 6 54M 0:0 100 EP HTCAP WPA RSN WME
Note that on FreeBSD 14.0, the S:N has proper values.
The iwm0 driver is recognized as:
iwm0: <Intel(R) Dual Band Wireless AC 8265> mem 0xdd100000-0xdd101fff at device 0.0 on pci58
iwm0: hw rev 0x230, fw ver 22.361476.0, address 98:2c:bc:36:61:e5
FYI, the fw version is identical to the one on FreeBSD 14 (different Laptop though).
I can connect to the network with iwm0. Just wondering if the access point selection might be sub-optimal
if S:N is unknown, or it might be just a "display" problem.
Tested it both on 6.4-STABLE and latest HEAD revision of master branch.
Updated by arcade@b1t.name 9 months ago
I know (have) this one, replaced AC6 Realtek with this one in my laptop as Realtek was totally unsupported:
Apr 1 10:52:49 slipper kernel: iwm0: <Intel(R) Dual Band Wireless AC 8265> mem 0xd0500000-0xd0501fff at device 0.0 on pci3
Apr 1 10:52:49 slipper kernel: iwm0: hw rev 0x230, fw ver 22.361476.0, address 04:cf:4b:6c:f5:61
Apr 1 10:52:50 slipper kernel: iwm0: need promiscuous mode update callback
Same problem here, I can't see s/n ratio for any station, though it connects fine. Mostly fine. Sometimes it just fails to connect to any station and can sit there for dozen minutes. `ifconfig wlan0 down; sleep 1; ifconfig wlan0 up` fixes the issue. Waiting 1 second before bringing interface up during boot has no effect.
Updated by mneumann 9 months ago
- Status changed from New to Resolved
I fixed the bug with commit https://gitweb.dragonflybsd.org/dragonfly.git/commit/796562b1e5843c4cc8963c19ab36cfac04182dcd
It's possible that this positively affects AP selection based on proper S:N values in case there are multiple APs with the same SSID, but that's just a rough
guess.