Date: Mon, 10 Nov 2008 10:24:09 +0200 From: "Alexander Renn" <alexander.renn@gmail.com> To: freebsd-drivers@freebsd.org Subject: NDIS support: /boot/loader.conf vs kldload Message-ID: <cc2a6eec0811100024p7d2cfb87q267274e54cd00689@mail.gmail.com>
index | next in thread | raw e-mail
Hello, I'm running the NDIS driver on WLAN chip 0x431514e4 (Broadcom) and it works only if I load it from /boot/loader.conf. First attempt to load it using kldload succeeds but it does not detect the chip. The second attempt to load the driver using kldload triggers kernel panic. The problem is that the chip becomes unusable after resuming the system from suspend and I cannot use kldload to re-load the driver again (system panics). What is the difference in loading the driver using /boot/loader.conf and using the kldload after the system bootup? I tried to change the dev.ndis sysctls but it did not seem to solve the problem with non-working driver when resumed after suspend. -- Best regards, Alexander Rennhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cc2a6eec0811100024p7d2cfb87q267274e54cd00689>