Re: [Madwifi-users] 2.4.20 / 2.4.21 - apm and HAL status 3

[Jean L. <lo...@cl...>]

Hi all !

I get lots of hal status 3 or status 14 when I try to use
an atheros card (5211 or 5212) in a PCI-to-Cardbus bridge
after a cold boot (not directly related to your issue though).
The only way I have found it to work is to enable "reset ESCD"
in the BIOS. Eeverything works fine afterwards including resetting
the computer, but not power off (-> need to reset ESCD again after
power on). I suppose there is something misbehaving in the
cardbus bridge initialization that requires the bios to set it
up properly in first place... Maybe you should try to play with
CONFIG_APM_DO_ENABLE or CONFIG_APM_ALLOW_INTS. Please note that
this is purely suppositions. Could you explain your hardware
setup (laptop brand, cardbus bridge model, and so on...) and maybe
give some lspci -vv output, before suspend and after, as well as
syslog output related to suspend/resume.

Regards

Jean

Sam Leffler wrote:
> On Monday 27 October 2003 01:11 am, Patrik Weiskircher wrote:
> 
>>>What......!?!  You posted to the list without first trying the
>>>CVS.......!?! Did you even read the FAQ .....!?!
>>>
>>>;0)
>>>
>>>The FAQ is here:
>>>http://www.mattfoster.clara.co.uk/madwifi-faq.htm
>>>
>>>and yes you should try the cvs.  ;0)
>>
>>Thanks :)
>>I did so today.
>>
>>But the problem doesn't go away :(
>>On APM-Resume it still says:
>>ath0: unable to reset hardware: hal status 3
>>
>>using the anonymous cvs checkout from today.
>>
>>What is hal status 3?
>>
> 
> 
> HAL_EIO, from ah.h
> 
> typedef enum {
>         HAL_OK = 0,             /* No error */
>         HAL_ENXIO,              /* No hardware present */
>         HAL_ENOMEM,             /* Memory allocation failed */
>         HAL_EIO,                /* Hardware didn't respond as expected */
>         HAL_EEMAGIC,            /* EEPROM magic number invalid */
>         HAL_EEVERSION,          /* EEPROM version invalid */
>         HAL_EELOCKED,           /* EEPROM unreadable */
>         HAL_EEBADSUM,           /* EEPROM checksum invalid */
>         HAL_EEREAD,             /* EEPROM read problem */
>         HAL_EEBADMAC,           /* EEPROM mac address invalid */
>         HAL_EESIZE,             /* EEPROM size not supported */
>         HAL_EEWRITE,            /* Attempt to change write-locked EEPROM */
>         HAL_EINVAL,             /* Invalid parameter to function */
>         HAL_ENOTSUPP,           /* Hardware revision not supported */
>         HAL_ESELFTEST,          /* Hardware self-test failed */
>         HAL_EINPROGRESS,        /* Operation incomplete */
> } HAL_STATUS;
> 
> (count from 0 to find the enum).
> 
> 
>>Anything I could try?
> 
> 
> Don't know; sounds the APM resume didn't setup enough h/w state for the driver 
> to bring the part back up.  Of course that assumes the driver got called.
> 
> 	Sam
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: The SF.net Donation Program.
> Do you like what SourceForge.net is doing for the Open
> Source Community?  Make a contribution, and help us add new
> features and functionality. Click here: http://sourceforge.net/donate/
> _______________________________________________
> Madwifi-users mailing list
> Mad...@li...
> https://lists.sourceforge.net/lists/listinfo/madwifi-users
>