Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Mar 2008 20:09:16 -0400
From:      Yousif Hassan <yousif@alumni.jmu.edu>
To:        Benjamin Close <Benjamin.Close@clearchain.com>
Cc:        freebsd-net@freebsd.org, Mel <fbsd.questions@rachie.is-a-geek.net>, Alphons Fonz van Werven <a.j.werven@student.utwente.nl>, freebsd-mobile@freebsd.org
Subject:   Re: [Wireless] Can't connect to wlan
Message-ID:  <1205366956.2082.13.camel@localhost>
In-Reply-To: <47D6FB5B.3020107@clearchain.com>
References:  <47C078EC.4020907@student.utwente.nl> <200802241730.13328.fbsd.questions@rachie.is-a-geek.net> <47D63A65.8010507@clearchain.com> <200803111356.00400.fbsd.questions@rachie.is-a-geek.net> <47D68808.5060709@student.utwente.nl> <47D6FB5B.3020107@clearchain.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote:
> Alphons "Fonz" van Werven wrote:
> > Mel wrote:
> >
> >>>     Do the recent patches by Andrew make a difference?
> >>>
> >>> http://people.freebsd.org/~thompsa/wpi_head.diff
> >>> http://people.freebsd.org/~thompsa/wpi_releng7.diff
> >

(ccing freebsd-net)

Ben,

I had a go with this patch today on top of 7.0-RELEASE.

The good:
- Switching off the radio and back on finally works - nice work.
- Scanning seems faster (but see caveat below)
- Association is MUCH faster (mind you, I don't use an encrypted AP).
- The "failed to align memory" stuff when the driver loads up - fixed. 
- The fact that it reloaded in the kernel even if I manually kldunloaded
if_wpi.ko - fixed

The slightly wonky:
- As reported by someone else:
  wpi0: timeout resetting Tx ring 1
  wpi0: timeout resetting Tx ring 3
  wpi0: timeout resetting Tx ring 4
appear on startup and occasionally on kldload - however they don't
appear to adversely affect too much

The ugly:
- I can only do an ifconfig wpi0 scan every OTHER time - in between
  successful attempts, I get
  wpi0: fatal firmware error
  wpi0: timeout resetting Tx ring (or: timeout resetting Tx ring 0)
  wpi0: link state changed to DOWN

  This wouldn't be so bad since it works every other time, but the
problem is that every time I do a scan, it sets the link state down,
causing the connection to drop - doesn't seem normal.  Of course then it
comes right back up but the network interruption is not so great.

Hmm - what else?  The whole thing seems - livelier.  I need to run some
throughput benchmarks but traffic to/from the card on my local network
seems faster and more responsive.  Hopefully this isn't the placebo
effect. ;)

Great work to you & rest of team on this patch... it's more than usable
at this point!

--Yousif




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1205366956.2082.13.camel>