Date: Tue, 29 Jun 2004 15:07:37 +0000 From: Sahil R Cooner <cooner@cs.fsu.edu> To: Andrey Smirnov <smir@delit.net> Cc: freebsd-current@freebsd.org Subject: Re: if_ndis kernel crashing Message-ID: <40E185B9.2090008@cs.fsu.edu> In-Reply-To: <40E18430.6010600@delit.net> References: <200406272331.41594.matt@fruitsalad.org> <200406291433.47505.jhugo@icomtek.csir.co.za> <40E18430.6010600@delit.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I believe you are right, have to load the modules once the system has boot, and also make sure to unload the modules before you shutdown otherwise you might get a kernel panic like I do ... just adding my $0.03, sai Andrey Smirnov wrote: > Johann Hugo wrote: > >> On Sunday 27 June 2004 23:31, Matt Douhan wrote: >> >>> Hi >>> >>> I am using if_ndis to get wlan support for my broadcom chipset wireless >>> card, since 3 days trying to build a new kernel it panics after >>> if_ndis is >>> installed. >>> >> >> >> I've had a similar experience, but with a ndis driver for an atheros >> wifi card. If the kld's (ndis + if_ndis) are loaded from >> /boot/loader.conf is crashes every time I boots up. >> >> If I do a normal boot (without loader.conf) and then do a kldload >> ndis + if_ndis by hand then it works fine. >> >> Kernel = 5-20040625-CURRENT > > ndis usually needs access to files under /compat/ndis. So, it should > be loaded _after_ root filesystem is mounted. So it should be loaded > via scripts. Something like /etc/ifstart_ndis0. > > Just my $0.02, > Andrey. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40E185B9.2090008>