Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Aug 2007 17:19:37 +1000
From:      "Jacob Hart" <jacob.hart+freebsd-current@gmail.com>
To:        "Sam Leffler" <sam@errno.com>, freebsd-current@freebsd.org
Subject:   Re: Atheros AR5006 abg minipci
Message-ID:  <139a3a1b0708180019n183eeda6j493b0ca8eec2c4b4@mail.gmail.com>
In-Reply-To: <46C664D0.3060906@errno.com>
References:  <632825b40708171855u155d0195udb6994999de12d15@mail.gmail.com> <46C664D0.3060906@errno.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Sam,

I'm using the 0.9.30.3 hal on a recently built -CURRENT, and my
wireless is detected as shown:

ath0: <Atheros 5418> mem 0x90100000-0x9010ffff irq 17 at device 0.0 on pci2
ath0: [ITHREAD]
ath0: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:17:f2:e9:64:19
ath0: mac 12.10 phy 8.1 radio 12.0

In my quest for a quieter notebook I've been experimenting with
powerd.  The wireless connection works reliably if
debug.cpufreq.lowest sysctl is set to restrict the CPU frequency to
1.16GHz or greater (it is a 2GHz core2 duo using the est driver), but
anything under that it begins to show some instability.

At 1GHz and 875MHz the wireless connection will intermittently freeze.
 I can usually resurrect the connection by forcing wpa_supplicant to
reassociate with the AP (from wpa_cli) or, if not, by restarting the
ath0 interface via /etc/rc.d/netif restart.

At 750MHz I experience the same problem as above, but occasionally the
if_ath module must be unloaded and re-loaded, then the ath0 interface
brought back up before the driver will be able to associate with an
AP.

At 500MHz i must always unload and reload the if_ath module.  Scanning
usually works, but association with an AP is not guaranteed at this
speed; i'd estimate it works about 25% of the time.  At speeds below
500Mhz, it is not possible to scan or associate with an AP.

Is this a known known issue with the driver or is it specific to my
system?  Further, is there anything I can do to help track down the
problem?

-j

On 8/18/07, Sam Leffler <sam@errno.com> wrote:
> William Grzybowski wrote:
> > Hi,
> >
> > I got wireless minipci atheros ar5006 with -CURRENT.
> > Cant use it even with if_ndis and i didnt tried on stable/release yet.
> > dmesg:
> >
> > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
> > ath0: <Atheros 5424/2424> mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on
> > pci3
> > ath0: [ITHREAD]
> > ath0: unable to attach hardware; HAL status 13
> > device_attach: ath0 attach returned 6
> >
> > I tried to search about it on the history without success, does it means
> > this card isn't supported yey? could i do anything providing info to help?
> > Should I forward this message to another list?
>
> You can try the test hal in http://www.freebsd.org/~sam.  Beware it is
> not a release (has not undergone full testing and has known issues).  If
> the 0.9.30.3 hal doesn't work then your part is probably a 2425.
> Support for that part has been blocked waiting on Atheros for >1 month.
>  No idea when it might show up.
>
>         Sam
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>



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