From owner-freebsd-current@freebsd.org Fri Jul 13 11:04:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1F1610341EC for ; Fri, 13 Jul 2018 11:04:12 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 574BF80666 for ; Fri, 13 Jul 2018 11:04:12 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 26DF6336; Fri, 13 Jul 2018 07:04:11 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 13 Jul 2018 07:04:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=s1eMMaVIydMvNqJZIjG4GT4XtZmY5 oUOW5s6zuUo6O0=; b=sjWYRDDjRHTvCzrvvxdWK6aQ08dbsZ/G69dk9uTB2mkHt lGtsDjktB6t9YZigmqJKbh/z3BrQ/ALPEKdRBKE51uZiyhT55MCdqYM9/ttB62L5 ykCZXnITudmNv/aqKKU7gts3+xKJK3Nif8o0QCC6NLRgf1ON77mdNlRPSL5vzjDo qoBJGjw4VMSHbx/wRBNxxiDm5viS62wOc+geoNeDrjQdsX0Sr+5QCsLxneQq9R/J hfrK8iaE0pSiCXhidjckauOmfriDr7BXi4ifIg2+hE0nk4qepEQUbKEdqac5fKLD VL9FwnPPDCVFjAcOMWFODFq02YcXZlHT82InBNXJg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=s1eMMa VIydMvNqJZIjG4GT4XtZmY5oUOW5s6zuUo6O0=; b=lp1rsYCBDJFjqx0Q/oU0S2 hm0JSqItspf6VoE/l6KLrZcnvE/ySL2b8qFONUmyyrf6AIOql4DabjEOKw0RBZ/m /VYKHtb+EQu/auLXAXmmG9lxizkTJwH0G7IH0ToT+L5x8p8AM2ajz0BfLBPFYO++ 8JKU2kd7Bh2r42MT4yl6SIPvHbScILlKj6jqvRyZwlSr4VslE8/NqJec/oKACQCV fkxdsM2ZykSYDdtUvfJ267HAKA0YEGtIqfzXG+jLykKRBHSQ+f3uYd2DUu8OBkRR uk3r/tKKIPJmgsb4K9cWHpcmfB6BuWLWm0AxYpitA2Y6O2VbGaj971/OGWwglEQQ == X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.2] (unknown [178.34.100.208]) by mail.messagingengine.com (Postfix) with ESMTPA id 1C919E49E9; Fri, 13 Jul 2018 07:04:08 -0400 (EDT) Subject: Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more From: Yuri Pankov To: Yuri , freebsd-current@freebsd.org References: <750df9db-ac02-a691-d091-7c34fe5ddb22@rawbw.com> Message-ID: <963c38fb-1c08-62bc-198d-309953c39eb1@yuripv.net> Date: Fri, 13 Jul 2018 14:04:08 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 11:04:13 -0000 Yuri Pankov wrote: > Yuri wrote: >> On 07/03/18 12:45, Yuri wrote: >>> I updated the laptop to r335884 last night, and 'service >>> wpa_supplicant start wlan0' doesn't succeed any more. >>> >>> kernel is supposed to create the network interface 'run0', but it >>> doesn't. This is the immediate reason why wpa_supplicant fails. >>> >>> The non-creation of 'run0' is a regression. I don't know of any >>> workaround. >>> >>> >>> The steps 'mergemaster -p' and 'mergemaster' were done during the >>> upgrade, so /etc is updated. >> >> >> Bug report for this problem: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229738 >> >> This is a very serious regression breaking WiFi. > > It's likely the switch from using usb.conf to devmatch.conf (see r329148). > > I can confirm the problem, inserting the ralink usb wifi dongle doesn't > do anything (I'm not using it anymore so I didn't notice the problem), > though the action in devmatch.conf is executed, so it might be the > problem somewhere below in devmatch(8). And looks like it's fixed in r335763 (for me, at least).