From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 16:51:16 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61CE71065673; Thu, 13 Sep 2012 16:51:16 +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 2D8338FC0C; Thu, 13 Sep 2012 16:51:16 +0000 (UTC) Received: from glenbarber.us (75-146-225-65-Philadelphia.hfc.comcastbusiness.net [75.146.225.65]) (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 AB97123F6D9; Thu, 13 Sep 2012 12:51:13 -0400 (EDT) Date: Thu, 13 Sep 2012 12:51:12 -0400 From: Glen Barber To: Yuri Message-ID: <20120913165111.GA2436@glenbarber.us> References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> <5051FD10.8040204@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <5051FD10.8040204@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 16:51:16 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 13, 2012 at 08:34:40AM -0700, Yuri wrote: > On 09/12/2012 20:01, Glen Barber wrote: > > It would be helpful if you would at least try my cron(8) suggestion. >=20 > So I tried adding the lines into crontab: > @reboot root /sbin/kldload /boot/kernel/if_ndis.ko >/dev/null 2>&1 > @reboot root /sbin/kldload /boot/modules/bcmwl5_sys.ko >/dev/null 2>&1 >=20 > Firstly, for some reason, this method fails to load bcmwl5_sys.ko with=20 > the error message: > KLD bcmwl5_sys.ko: depends on ndis - not available or version mismatch >=20 Hmm. This should also be loading ndis.ko. If not, add that to the cron line as well. If that is the problem, sorry, that was my mistake. Also, are your kernel and userland in sync? And is this module built on the kernel you are currently running? Glen > However, command 'kldload /boot/modules/bcmwl5_sys.ko' typed manually=20 > after boot succeeds without any messages. This is a mystery to me, why=20 > one way to run it produces this message and another one doesn't. >=20 > And '/etc/rc.d/netif start' still doesn't start wifi even though all=20 > kernel modules were loaded after kernel boot. >=20 --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQUg7/AAoJEFJPDDeguUajpg8H/223JVHiDZWEUufXbC2Vogif z0aDQzjU4VDZ0DwakFDeVYVPdBLqbFKMGgGMcBtk9g2/M93efw2YyZESq6doWVqz u+zsX2rjYpfqtla+rK3d7TmijlyAUwEggt+fPtF5Hcpf6XFvvh3TES1cmunhWqiQ Zy42LvcDLnOkJ0Yve0UgWmXV5+gR1jbjZch4Mhryb7K9mMnmBuSOaMn2wEBpC24W 0u7W+D6rEIe+2WHb4WaxMAGuD4+FE/JT2eBvDLnbFOVIYj3sgdvQqgnNmH7kawLo f4p0plhvU37AUCARzgYiiX1O9uj42Nc7017ur15HI0vYZBcX8pakIX01mWqInY8= =xToo -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5--