From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 03:01:58 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 116AD106564A; Thu, 13 Sep 2012 03:01:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id DF49A8FC1B; Thu, 13 Sep 2012 03:01:57 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id B023823F6D9; Wed, 12 Sep 2012 23:01:56 -0400 (EDT) Date: Wed, 12 Sep 2012 23:01:53 -0400 From: Glen Barber To: Yuri Message-ID: <20120913030153.GH1341@glenbarber.us> References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bygAmIonOAIqBxQB" Content-Disposition: inline In-Reply-To: <50514BCC.3010607@rawbw.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 03:01:58 -0000 --bygAmIonOAIqBxQB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 12, 2012 at 07:58:20PM -0700, Yuri wrote: > > I'm surprised you can have ndis(4) load during boot. Recent machines I > > tried to do that have panic'd during boot. >=20 > I have these lines in /boot/loader.conf and if_ndis and ndis(4) based=20 > driver load fine: I understand that. > What you are suggesting is for the case when loading if_ndis causes=20 > panic during boot. > In my case it loads fine during boot, but it's not clear why=20 > '/etc/rc.d/netif' doesn't activate it. > network works fine once all commands are run manually. ndis(4) is buggy on SMP-enabled kernels. It would be helpful if you would at least try my cron(8) suggestion. Glen --bygAmIonOAIqBxQB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQUUyhAAoJEFJPDDeguUajPOwH/iGk1R5ZCYfRVnOAobusHoPS GpfsjqpXdzsxf4DYU29o8HJ98wtd/P5muipZKQl0RdYVjYgGsZTLomi6wVn++ztw Y/2gcdSc0q+m3iWXwT9jb0HTJSn2zs9EVXzFicknKyjPHQ0r/JsAu+RYRc4Q/uIN FQ5Z+aAiZiIjC6Pai/JjksUnqP9dEONctAhlyhYnCHGIOeYPjVuUwX+e637ld6Wh 7LTgiT0LAynZ5jePc8fq+ClnVlHQymzNLxVnHAPCa2PUAdAehRW77d0LH/4CaxRP XBwtYqTigXhgCADsaGtczUFjpFw69CdwGt8DwQ0XHiE0cG/jVtF27y9ILSOEnN8= =V+5K -----END PGP SIGNATURE----- --bygAmIonOAIqBxQB--