Re: ath0: unable to attach hardware

Hi,

attached to this e-mail you find the output of dmesg. What I guess the most relevant lines could be is:

ath0: <Atheros 5413> mem 0xfdee0000-0xfdeeffff irq 16 at device 4.0 on pci2
ar5212ChipTest: address test failed addr: 0x00008000 - wr:0x00000000 != rd:0xffffffff
ar5212Attach: hardware self-test failed
ath0: unable to attach hardware; HAL status 14
device_attach: ath0 attach returned 6

I read the registers 4004 and 4010 again to make sure the values still are the same, which indeed they are.

I hope this helps.

Thanks!

On Donnerstag, 13. Dezember 2012 at 10:18 PM, "Adrian Chadd" <adrian_at_freebsd.org> wrote:
>
>On 13 December 2012 13:11,  <husyh_at_hush.com> wrote:
>> Hello everyone,
>>
>> I'm afraid I still don't know what exactly BAR is, or how I get 
>its value that I'm supposed to plug into the line John provided:
>> dd if=/dev/mem bs=4 iseek=((start of bar + reg offset)/4) 
>count=1 | hd
>>
>> I assumed that "start of bar" is 0xfdee0000 in my case, since 
>dmesg reports
>> ath0: <Atheros 5413> mem 0xfdee0000-0xfdeeffff irq 16 at device 
>4.0 on pci2
>
>Yup.
>
>> This is what I get:
>> # dd if=/dev/mem bs=4 iseek=`echo "ibase=16; (FDEE0000+4004)/4" 
>| bc` count=1 | hd
>> 00 00 01 00
>> # dd if=/dev/mem bs=4 iseek=`echo "ibase=16; (FDEE0000+4010)/4" 
>| bc` count=1 | hd
>> 14 00 01 00
>>
>> Please correct me if my assumption about "start of bar" was 
>wrong and/or I made some other mistake.
>> Also, please don't hesitate to ask me to do anything else that 
>might help you during debugging.
>>
>> Thank you very much for the effort.
>
>Hm. Wait, what's the rest of the ath0: output?
>
>
>
>Adrian