Re: [pfSense Support] [pfSense 0.88/0.90] Atheros card not bound to driver
I have heard reports that the newer HAL in later versions makes some ATH cards work that are not reliably probed. Please try: http://www.pfsense.com/~sullrich/?M=D Scott On 11/11/05, Marc A. Volovic [EMAIL PROTECTED] wrote: 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]
Re: [pfSense Support] [pfSense 0.88/0.90] Atheros card not bound to driver
On Fri, 2005-11-11 at 13:18 -0500, Scott Ullrich wrote: I have heard reports that the newer HAL in later versions makes some ATH cards work that are not reliably probed. Please try: http://www.pfsense.com/~sullrich/?M=D I am afraid the embedded version does not gunzip correctly, failson format error... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] [pfSense 0.88/0.90] Atheros card not bound to driver
It was uploading. Try downloading again. On 11/11/05, Marc A. Volovic [EMAIL PROTECTED] wrote: On Fri, 2005-11-11 at 13:18 -0500, Scott Ullrich wrote: I have heard reports that the newer HAL in later versions makes some ATH cards work that are not reliably probed. Please try: http://www.pfsense.com/~sullrich/?M=D I am afraid the embedded version does not gunzip correctly, failson format error... - 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]
RE: [pfSense Support] [pfSense 0.88/0.90] Atheros card not bound to driver
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]
RE: [pfSense Support] [pfSense 0.88/0.90] Atheros card not bound to driver
On Fri, 2005-11-11 at 22:44 +0100, Espen Johansen wrote: 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. Hi. Actually, version 0.90 also had the 0.9.16.3 HAL and the results are reproducible. 0.93 seem to be better (I have NOT been able to reproduce the failure) but I need to go over it in the office, with the full range of the itsy bits parts ;-). However, for whatever reason - the 0.93 seems to have the ath driver kicking in later than 0.88 and 0.90, possibly allowing the PCI subsystem to settle and allow the driver to successfully negotiate with the hardware? This is NOT fact, just a feeling. I need to compare the two outputs, which will happen on Sunday. Memo to self - learn to build OWN images of pfsense. G Marc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
