ndis panic HP pavilion ze4400 won't boot

[Glen Barber]

On Thu, Jan 8, 2009 at 5:20 PM, Glen Barber <glen.j.barber at gmail.com> wrote:
> On Thu, Jan 8, 2009 at 4:59 PM, Neal Hogan <nealhogan at gmail.com> wrote:
>>
>>
>> On Thu, Jan 8, 2009 at 3:37 PM, Glen Barber <glen.j.barber at gmail.com> wrote:
>>>
>>> On Thu, Jan 8, 2009 at 11:37 AM, Neal Hogan <nealhogan at gmail.com> wrote:
>>> > I'm father new to fBSD. I hope this is the appropriate list to send this
>>> > question to.
>>> >
>>> > I just installed 7.1-RELEASE on my HP pavilion and attempted to
>>> > configure my
>>> > Broadcom wlan card (BCM94309 version 4.10.40.0) using ndisgen. I cp'd
>>> > the
>>> > bcmwl5_sys.ko to /boot/kernel and added *bcmwl5_sys_load="YES"* to my
>>> > /boot/loader.conf. Now the machine will not boot. It crashes when it
>>> > reaches
>>> > the ndis0 line. I've tried booting in all the modes but they all fail to
>>> > boot. I can escape to prompt, but am unsure what, if anything, I can do
>>> > in
>>> > that mode to deal with the situation.
>>> >
>>> > With other releases (6.4 and 7.0) the machine would panick when I
>>> > attempted
>>> > to ifconfig ndis0. However, I was able to boot in single user mode and
>>> > temporarily move the rc.conf file so that I cound boot in the default
>>> > mode.
>>> > With 7.1, I don't appear to have that option.
>>> >
>>> > Is there anything I can do, short of a fresh install, to eliminate this
>>> > problem? I'm not too worried about getting the wifi up (although, I
>>> > won't
>>> > turn down any advice). I just want the machine to boot.
>>> >
>>>
>>> I discovered a wierd hack to resolve this.  Remove the line(s) from
>>> loader.conf, and create an /etc/rc.local file containing the
>>> following:
>>>
>>> /sbin/kldload /boot/modules/bcmwl5_sys.ko
>>>
>>> That should survive a reboot.
>>>
>>>
>> Glen,
>>
>>  I tried your suggestion (which I appreciate) and it did survive rebooting.
>> However, bcmwl5_sys.ko was not loaded because there was no ndis interface.
>> So, I change the rc.local to
>>
>> /sbin/kldload /boot/kernel/bcmwl5_sys.ko
>>
>> Upon reboot, the system panicked when it loaded the rc.local file.
>>
>> I don't know . . .
>>
>
> Any additional modules should be placed in /boot/modules, not
> /boot/kernel.  What happens if you manually load the module after the
> system is running?
>
>

After rethinking my last statement, with the module in /boot/kernel
*and* an entry in loader.conf you are loading the module twice.  Move
the module to /boot/modules where it should be.

-- 
Glen Barber