Hi,

The HAL and drivers are updated in version .92 and newer.
This should fix what you are seeing.
Just get .93 as soon as it hits the mirrors.

-lsf

> -----Original Message-----
> From: Marc A. Volovic [mailto:[EMAIL PROTECTED]
> Sent: 11. november 2005 17:35
> To: support@pfsense.com
> Cc: Marc A. Volovic
> Subject: [pfSense Support] [pfSense 0.88/0.90] Atheros card not bound to
> driver
> 
> Hello.
> 
>   I am experiencing a peculiar phenomenon - on a WRAP.1 board (BIOS 1.08),
> a TP-Link TL-WN660G card is NOT bound to driver on a cold boot (i.e. power
> cycle) - and therefore not used. The card IS detected, HAL is reported
> (version 0.9.14.9), but driver remains unbound and card is reported as
> "not
> claimed".
> 
>   On subsequent reboots (i.e. console/web ui generated boots), the card is
> detected but IS bound to the driver and is, therefore, usable.
> 
>   Initially, I suspected both the card and the WRAP. Subsequent tests,
> with
> other Mini-PCI Atheros cards and other WRAP boards (I have access to a
> number of both), proves that the behaviour is repeatable.
> 
>   Linux does not exhibit similar behavior, with HAL 0.9.16.3 being
> detected
> and driver (ath_pci 0.9.4.5) bound every boot, cold or warm, on the very
> same boards and the very same Atheri cards (plural of Atheros, how ;-)...
> 
>   Has anyone seen similar behaviour? What can cause this and how can I
> provide more pertinent information to check this issue. I readily admit
> that my BSD experience is dated (SunOS 4.1), and I am trying to bootstrap
> my memory into a more functional mode (among other stuff to be able to
> build local versions of the embedded images).
> 
>   Thanks!
> 
>   Marc
> 
> --
> ---MAV
> Marc A. Volovic                                         [EMAIL PROTECTED]
> Swiftouch, LTD                                             +972-544-676764
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to