Date: Thu, 19 Aug 2010 21:37:40 +0100 From: Peter Harrison <peter.piggybox@virgin.net> To: Yuri <yuri@rawbw.com> Cc: Glen Barber <glen.j.barber@gmail.com>, freebsd-questions@freebsd.org Subject: Re: Why network doesn't get initialized on system startup? Message-ID: <20100819203740.GA1285@ideapad.piggybox> In-Reply-To: <4C6D56F5.2090504@rawbw.com> References: <4C6CC879.8000509@rawbw.com> <4C6D02FA.2090201@gmail.com> <4C6D56F5.2090504@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thursday, 19 August 2010 at 9:08:21 -0700, Yuri said: > On 08/19/2010 03:10, Glen Barber wrote: > >Are you loading the ndis(4) kernel module at boot via loader.conf? > > > > Yes, all ndis-related drivers (ndis.ko, if_ndis.ko and actual ndis > driver converted from windows one) are loaded from loader.conf. > When system comes up ndis0 is fully functional and I can initialize it > by hand fine. It just doesn't happen on startup. I can't remember where I saw this, but when you're using ndis you need to use SYNCDHCP instead of DHCP in ifconfig/rc.conf. Works for me no problem with a broadcom chip using ndis. Regards, Peter Harrison. > > Yuri > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100819203740.GA1285>