Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jun 2008 21:40:37 +0300
From:      Manolis Kiagias <sonic2000gr@gmail.com>
To:        Alexander Sack <pisymbol@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Atheros (ath) MSI wireless embedded chipset fails to attach on 7.0-STABLE
Message-ID:  <48580525.8040207@gmail.com>
In-Reply-To: <3c0b01820806171123k4ceb8894hb5c889b86cebca24@mail.gmail.com>
References:  <3c0b01820806170757v5565b59ne0e9d5db06f26761@mail.gmail.com>	 <4857D8BB.1080901@gmail.com>	 <3c0b01820806170852t39a6346doa6d77a655469eed9@mail.gmail.com> <3c0b01820806171123k4ceb8894hb5c889b86cebca24@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Sack wrote:
> On Tue, Jun 17, 2008 at 11:52 AM, Alexander Sack <pisymbol@gmail.com> wrote:
>   
>> On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias <sonic2000gr@gmail.com> wrote:
>>     
>>> Alexander Sack wrote:
>>>       
>>>> Hello:
>>>>
>>>> I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 Turon based
>>>> notebook, a MSI-1710A (GX710Ax) which has a generic embedded
>>>> controller.  During boot up I notice that ATH complains with:
>>>>
>>>> ath_rate: version 1.2 <SampleRate bit-rate selection algorithm>
>>>> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
>>>> ath0: <Atheros 5424/2424> mem 0xfd7f0000-0xfd7fffff irq 16 at device 0.0
>>>> on pci2
>>>> ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfd7f0000
>>>> ath0: [MPSAFE]
>>>> ath0: [ITHREAD]
>>>> ath0: unable to attach hardware; HAL status 13
>>>> device_attach: ath0 attach returned 6
>>>>
>>>> HAL status 13 from the header file seems to indicate that the
>>>> 7.0-STABLE driver doesn't support my hardware revision.  Here is my
>>>> pciconf -l output:
>>>>
>>>>         
>>> Maybe you could try compiling a kernel with a newer hal. This is the kind of
>>> hack we use on the eeepc. Have a look at this:
>>>
>>> http://nighthack.org/wiki/EeeBSD
>>>       
>> Thank you SO much for this link.  That's EXACTLY what I want to do
>> because I realize that this is a HAL problem.  I've been searching
>> like MAD where I could get an updated binary HAL for this chipset
>> (PCIe based).
>>     
>
> Btw, is there any particular reason you chose the version you linked
> against what's the current stable release?  Also is this the only
> place to get updated ath HAL's?
>
> -aps
>
>   

Well, the linked page is not mine ;)  but I have successfully used newer 
editions of the madwifi driver on the eeepc, so don't let this stop you!



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48580525.8040207>