Date: Wed, 12 Sep 2012 23:01:53 -0400 From: Glen Barber <gjb@FreeBSD.org> To: Yuri <yuri@rawbw.com> Cc: freebsd-net@freebsd.org Subject: Re: Why wpa_supplicant doesn't start with ndis0 interface? Message-ID: <20120913030153.GH1341@glenbarber.us> In-Reply-To: <50514BCC.3010607@rawbw.com> References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120913030153.GH1341>