Bug 229738 - [regression] [CURRENT] USB WiFi cards don't create wlan interfaces
Summary: [regression] [CURRENT] USB WiFi cards don't create wlan interfaces
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2018-07-12 17:59 UTC by Yuri Victorovich
Modified: 2018-09-24 18:17 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer freebsd_triage 2018-07-12 17:59:08 UTC 
Beginning with some change a few weeks ago, wlan0 device doesn't get created when the card is inserted. As a result, WiFi can't be used in a normal way, without running an interface creation command manually. devd is supposed to create the wlan interface.

Running 'service netif restart' helps.

Verified the problem with 'run' and 'urtwn' WiFi devices.

I reported this problem on the current@ ML arounf July 4th, but the problem is still unfixed.
Comment 1 Warner Losh freebsd_committer freebsd_triage 2018-07-13 11:04:40 UTC 
does everything work if you do kldload if_run?
Comment 2 Warner Losh freebsd_committer freebsd_triage 2018-07-13 11:36:54 UTC 
This appears to be fallout from the devd arg quoting I fixed in r335763
Comment 3 Yuri Victorovich freebsd_committer freebsd_triage 2018-07-13 15:49:39 UTC 
(In reply to Warner Losh from comment #1)

No, the problem exists in case of pre-loaded if_run. Also, kernel modules were also loaded by devd.
Comment 4 Yuri Victorovich freebsd_committer freebsd_triage 2018-07-17 18:37:19 UTC 
r336271 still has the problem.
Comment 5 Yuri Pankov 2018-09-23 12:01:18 UTC 
Should be fixed in bug #231441.
Comment 6 Yuri Victorovich freebsd_committer freebsd_triage 2018-09-24 18:17:31 UTC 
(In reply to Yuri Pankov from comment #5)

Yes, it is fixed now. Thank you.