Is there anything I can try to get this working? Any debug information I =
can
provide or what not?

- John Schieferle Uhlenbrock



-----Original Message-----
From: current-users-owner@NetBSD.org =
[mailto:current-users-owner@NetBSD.org]
On Behalf Of Sam Leffler
Sent: Freitag, 20. Februar 2004 07:01
To: Greg Troxel
Cc: current-users@NetBSD.org; John Schieferle Uhlenbrock
Subject: Re: Atheros - Status?



On Feb 19, 2004, at 6:18 AM, Greg Troxel wrote:

>   ath0 at pci0 dev 10 function 0
>   ath0: interrupting at irq 12
>   ath0: unable to attach hardware; HAL status 3
>
> I haven't tried code in the last few months, but I got a number of=20
> atheros cards (4 I think) to work.  I got messages that look like this =

> when my cardbus memory space mappings were messed up (IBM TP600E,=20
> needs RBUS_MIN_START bashing).  So I would first check that you can=20
> use other cardbus cards.

This error is likely related to h/w setup:

typedef enum {
         HAL_OK          =3D 0,    /* No error */
         HAL_ENXIO       =3D 1,    /* No hardware present */
         HAL_ENOMEM      =3D 2,    /* Memory allocation failed */
         HAL_EIO         =3D 3,    /* Hardware didn't respond as =
expected=20
*/
         HAL_EEMAGIC     =3D 4,    /* EEPROM magic number invalid */
         HAL_EEVERSION   =3D 5,    /* EEPROM version invalid */
         HAL_EELOCKED    =3D 6,    /* EEPROM unreadable */
         HAL_EEBADSUM    =3D 7,    /* EEPROM checksum invalid */
         HAL_EEREAD      =3D 8,    /* EEPROM read problem */
         HAL_EEBADMAC    =3D 9,    /* EEPROM mac address invalid */
         HAL_EESIZE      =3D 10,   /* EEPROM size not supported */
         HAL_EEWRITE     =3D 11,   /* Attempt to change write-locked=20
EEPROM */
         HAL_EINVAL      =3D 12,   /* Invalid parameter to function */
         HAL_ENOTSUPP    =3D 13,   /* Hardware revision not supported */
         HAL_ESELFTEST   =3D 14,   /* Hardware self-test failed */
         HAL_EINPROGRESS =3D 15,   /* Operation incomplete */
} HAL_STATUS;

(i.e. 3 =3D=3D HAL_EIO which means basically the HAL couldn't talk to =
the=20
hardware).

>
> Also, I think there is only HAL support for i386 at the moment, but=20
> presumably that would have been a compile failure if you are on=20
> another arch.

There's actually support for many non-x86 architectures; look on=20
sourceforge (the madwifi project).

	Sam