NDIS support: /boot/loader.conf vs kldload

[Alexander Renn]

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 Renn