Re: [Madwifi-users] 2.4.20 / 2.4.21 - apm

[Sam L. <sa...@er...>]

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