Ath works as module, not inkernel

[Adrian Chadd]

.. it should've produced output in dmesg.

Also try adding:

dev.ath.0.hal.debug=0x4

See if that helps?

Also, how the hell are you able to load a module for ath/hal if it's
compiled into your kernel? or is it failing to load it early on in the
single user boot, but then fine to load it in later?


Adrian

On 1 August 2011 23:24, richo <richo at psych0tik.net> wrote:
> On 01/08/11 23:07 +0800, Adrian Chadd wrote:
>>
>> Try adding
>>
>> hw.ath.hal.debug=0x4
>>
>> to /boot/loader.conf ; just to get some boot-time reset logging going.
>> I'd like to see what the exact condition is that's triggering that HAL
>> attach failure (it's either "can't wakeup chip" or "can't reset
>> chip".)
>>
>>
>> Adrian
>>
>
> I just booted with that option.. there's nothing extra in dmesg. Where does
> that produce logs?
>
> --
> richo || Today's excuse:
> Operators killed when huge stack of backup tapes fell over.
>