From owner-freebsd-net@FreeBSD.ORG Thu Sep 13 15:34:42 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 38661106564A; Thu, 13 Sep 2012 15:34:42 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 1FF4C8FC08; Thu, 13 Sep 2012 15:34:41 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q8DFYfYv011864; Thu, 13 Sep 2012 08:34:41 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <5051FD10.8040204@rawbw.com> Date: Thu, 13 Sep 2012 08:34:40 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Glen Barber References: <505136E8.6010708@rawbw.com> <20120913015904.GC1341@glenbarber.us> <50514BCC.3010607@rawbw.com> <20120913030153.GH1341@glenbarber.us> In-Reply-To: <20120913030153.GH1341@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 15:34:42 -0000 On 09/12/2012 20:01, Glen Barber wrote: > It would be helpful if you would at least try my cron(8) suggestion. 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 Firstly, for some reason, this method fails to load bcmwl5_sys.ko with the error message: KLD bcmwl5_sys.ko: depends on ndis - not available or version mismatch However, command 'kldload /boot/modules/bcmwl5_sys.ko' typed manually after boot succeeds without any messages. This is a mystery to me, why one way to run it produces this message and another one doesn't. And '/etc/rc.d/netif start' still doesn't start wifi even though all kernel modules were loaded after kernel boot. Yuri