Bug 203271 - Wi-Fi no longer driven on some hardware with 11.0-CURRENT
Summary: Wi-Fi no longer driven on some hardware with 11.0-CURRENT
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-wireless (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2015-09-22 21:27 UTC by Graham Perrin
Modified: 2015-12-20 03:12 UTC (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin freebsd_committer freebsd_triage 2015-09-22 21:27:35 UTC
Originally reported as https://bugs.pcbsd.org/issues/11598 then I was advised that the problem is not specific to PC-BSD. 

Affected hardware includes Toshiba Satellite Pro C50-A-1E6 (part PSCG7E-02D042EN). https://forums.pcbsd.org/thread-20234-post-111879.html#pid111879 notes that a change of branch, down to 10.2-RELEASE, allowed all affected computers to recognise the Wi-Fi hardware.
Comment 1 Adrian Chadd freebsd_committer freebsd_triage 2015-09-22 21:32:05 UTC
Hi,

I need more information than this. Can you post more of the kernel panic? Can you get a kernel corefile or the dumpfile in /var/crash/XXX.core.txt (the text file!) with all the relevant information?

Thanks!
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2015-09-23 00:46:35 UTC
No kernel panic. 

The OS simply behaves as if there's no Wi-Fi hardware. 

It'll be a few hours before I can regain access to any of the affected Toshiba notebooks and then change branch up to 11.0-CURRENTSEPT2015. 

Will it be useful to get PC-BSD diagnostic files before and after the change of branch? 

Any other hints for before and after the change?
Comment 3 Andrey V. Elsukov freebsd_committer freebsd_triage 2015-09-23 23:41:51 UTC
Do you see your lost device in the output of sysctl net.wlan.devices?
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2015-09-25 17:04:10 UTC
Thanks for the hint. I'm away from the Toshiba computers for a few days, out of town. Aiming to review this report in around a week.
Comment 5 Ben Lavery-Griffiths 2015-09-30 13:00:08 UTC
To add…

I’m running 11.0-CURRENTSEPT2015 (PC-BSD) on a Lenovo ThinkPad T440 with an Intel 7260ac.

Here is some sample output:
# sysctl net.wlan.devices
net.wlan.devices:
# cd /boot/kernel
# kldload iwm7260fw.ko
# kldload if_iwm.ko
# sysctl net.wlan.devices
net.wlan.devices: iwm0

Only my ethernet (em0) is present in “PC-BSD Network Manager”.  The only devices shown with `ifconfig -a` are em0 and lo0.
This thread shows more of my setup and is what lead me to this bug report: https://forums.pcbsd.org/thread-20252.html
Comment 6 Ben Woods freebsd_committer freebsd_triage 2015-09-30 13:18:55 UTC
(In reply to Ben Lavery from comment #5)
> Only my ethernet (em0) is present in “PC-BSD Network Manager”.  The only devices shown with `ifconfig -a` are em0 and lo0.

I am not convinced that is actually a regression in current. I believe it could be the result of a recent change in current to make it such that wireless "parent interfaces" are no longer listed in the output of ifconfig(8), but instead they are listed in the output of "sysctl net.wlan.devices". Other than that there is no change to the configuration required to bring up wireless devices. We are waiting on the bug reporter to confirm this is the case, and that there is no regression.

The change that brought this difference in behaviour was committed to current on 20150827 in r287197:
https://svnweb.freebsd.org/base?view=revision&revision=287197

It may be that the PC-BSD tools have not yet been updated to reflect this change in current when running the PC-BSD EDGE branch.

Copying in Kris Moore from PC-BSD in case he has any comment on the PC-BSD tools.(In reply to Ben Lavery from comment #5)
Comment 7 Juan Ramón Molina Menor 2015-09-30 15:06:44 UTC
(In reply to Ben Lavery from comment #5)

Here, with similar hardware, a ThinkPad S440 with an Intel AC 7260, and CURRENT (not PC-BSD) at r288108 (Sep 22), I don’t have this issue:

% sysctl net.wlan.devices
net.wlan.devices: iwm0

% ifconfig -a
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether f0:76:1c:04:33:26
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (none)
        status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether f8:16:54:df:f6:b5
        inet 192.168.1.30 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
        status: associated
        ssid SFR_24A0 channel 1 (2412 MHz 11g) bssid 24:95:04:f2:24:a4
        regdomain ETSI country FR authmode WPA privacy ON deftxkey UNDEF
        TKIP 2:128-bit txpower 30 bmiss 10 scanvalid 60 protmode CTS wme
        roaming MANUAL
        groups: wlan
Comment 8 Ben Woods freebsd_committer freebsd_triage 2015-10-13 14:34:07 UTC
(In reply to Graham Perrin from comment #4)
> Thanks for the hint. I'm away from the Toshiba computers for a few days, out of town.
> Aiming to review this report in around a week.

Hi Graham,
Have you had a chance to look into this yet to see if your wireless devices are correctly shown in "sysctl net.wlan.devices"?
Thanks,
Ben
Comment 9 Graham Perrin freebsd_committer freebsd_triage 2015-10-17 10:13:56 UTC
Apologies: I no longer work in the area where the Toshiba notebooks were stored, and I suspect that other users' requirements would have led to writing over the installations of PC-BSD.

If I do find myself with an affected notebook, again, I'll add another comment.
Comment 10 Graham Perrin freebsd_committer freebsd_triage 2015-10-24 19:25:56 UTC
I had symptoms of what may be the same bug on a different machine, an Ergo Vista 621 https://forums.pcbsd.org/thread-20235.html and in this case, the GUI to the Wi-Fi adapter was: 

* present with 11.0-CURRENTOCT2015 updated from an earlier version of the OS

* not present with a clean installation of 11.0-CURRENTOCT2015

Following advice from LooX in irc://chat.freenode.net/#pcbsd I added a line to 
/etc/rc.conf

wlans_wpi0="wlan0"

– then a restart of the OS, and then Wi-Fi was configurable. 

Now: 

$ date ; freebsd-version ; uname -a ; cat /etc/rc.conf
Sat 24 Oct 2015 20:17:54 BST
11.0-CURRENTOCT2015
FreeBSD cces3-gjp4-pc-bsd-ergovista621.university.brighton.ac.uk 11.0-CURRENTOCT2015 FreeBSD 11.0-CURRENTOCT2015 #1 9551f87(master): Fri Sep 25 21:43:02 UTC 2015     root@devastator:/usr/obj/net/executor/builds/git/freebsd-11-current/sys/GENERIC  amd64
# Auto-Enabled NICs from pc-sysinstall
ifconfig_re0="DHCP"
# Auto-Enabled NICs from pc-sysinstall
ifconfig_re0_ipv6="inet6 accept_rtadv"
hostname="cces3-gjp4-pc-bsd-ergovista621.university.brighton.ac.uk"
pcsysconfig_enable="YES"
zfs_enable="YES"
sshd_enable="YES"
# https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203271 and advice from LooX
wlans_wpi0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"
$
Comment 11 Graham Perrin freebsd_committer freebsd_triage 2015-11-22 04:56:43 UTC
https://github.com/pcbsd/pcbsd/commit/9dc6aa26de2508b50dec6054edeee2d67998ad73 (2015-11-16)

>  When we boot PC-BSD desktop, check for new wireless devices which are missing /etc/rc.conf wlans_<device> entries.
> 
> This fixes a problem where the GUI tools don't see any wireless devices
anymore on -CURRENT
Comment 12 Graham Perrin freebsd_committer freebsd_triage 2015-12-20 03:12:17 UTC
At <http://lists.pcbsd.org/pipermail/testing/2015-December/010319.html> Kris confirms that the 2015-11-16 commit (thanks) was a fix for what was reported here.