Re: [Madwifi-users] D-Link, DWL-G520, Atheros Chipset AR5212A

[Tom M. <to...@ho...>]

=2E. also, check your syslog for error messages from the driver.  I usually
see a bunch of "hardware error, resetting" messages.

On Fri, Oct 03, 2003 at 03:58:17PM -0700, Tom Marshall wrote:
> Looks like you have plenty of SNR (I assume this is the default signal
> reporting, not using my patch).
>=20
> I've had problems with .11g mode when talking to an AP that has a Broadcom
> chip.  Do you know what wireless chip is in your AP and/or what brand and
> model it is?  Does the problem go away when you force .11b mode?  Use the
> command "iwpriv ath0 mode 2" and verify you are in .11b mode with iwconfi=
g.
>=20
> On Fri, Oct 03, 2003 at 06:24:13PM -0500, Tony VanScoy wrote:
> > IMHO the whole blinking lights sucks.  Oh well.
> >=20
> > I checked my cordless phone and its 900Mhz, so I don't think that's wha=
ts interfering. I don't have anything else around that wireless.  My connec=
tion is so bad that I can barely send this email out.  Is there any tool th=
at I can use to see how good my connection to the AP is?
> >=20
> > Info...
> > # iwconfig ath0
> > ath0    IEEE 802.11-OFDM  ESSID:"scoy_net" =20
> >         Mode:Managed  Frequency:2.437GHz  Access Point:00:0D:88:89:30:71
> >         Bit Rate=3D54Mb/s   Tx-Power:off   Sensitivity=3D0/3 =20
> >         Retry:off   RTS thr:off   Fragment thr:off
> >         Encryption key:off
> >         Power Management:off
> >         Link Quality:0/92  Signal level:32/154  Noise level:0/154
> >         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >         Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>=20
> --=20
> What we wish, that we readily believe.
>         -- Demosthenes